Introduce specialized smart agents

The agents auto-update themselves and can calculate their velocities. This keeps the user from having to create an update_agent function. It can also save the user from having to keep track of and update velocities at all by using the provided apply_steering method.
It leads to smaller code that can boil down to:
func _physics_process(delta: float) -> void:
    behavior.calculate_steering(accel)
    agent.apply_steering(accel, delta)

Would like a review and feedback, since they are fairly comprehensive classes.

Could you remove the reference from here? In general, I don't think we should have it in the project and repo - it's only to generate the ref, e.g. for the website.

If we're going to get to the point where we modify the JSON file manually to add special tags that aren't in the code, it'd count as a piece of the source code, no? Or at least, it'll need to be committed somewhere.
At least, that's my reasoning for keeping it in, but I can also remove it.

If we're going to get to the point where we modify the JSON file manually to add special tags that aren't in the code, it'd count as a piece of the source code, no? Or at least, it'll need to be committed somewhere.

Yes, good call.

For the reference, then, could we update it outside of PRs? With new releases. I could setup a hook so it auto-updates the reference and the docs on the website when we make a new release tag.

Yeah, doing it on-release is probably smarter. I'll revert the file for now.

You can delete it and git commit --amend && git push -f

The commit message should be clear enough, I didn't do any major changes to the code, just some cosmetic stuff I'd say, apart from rewriting the constructor to include MovementType as well and yield() on ready.
Really nice addon to the steering toolkit. It's starting to get more complicated with moving parts that affect state directly on the nodes, we'll have to see how to be careful with these.

@Razoric480 You can go ahead and revert or make more changes

Are we good to merge at this point?

Also, are we good to make a 1.0 release of the tool at this point? Seems we have about everything.

Yes, and yes.

Please don't merge your own PRs, I was actually rebasing the branch that had some issues in the commits

Oh... Sorry =(
I'll refrain from now on.

No, reverting creates a revert commit, it makes even more of a mess. It's no big deal, just as a rule of thumb, the person who does a PR shouldn't merge their own branch. One of the reviewers should merge when the PR passed review


Sync: identical file downloaded/uploaded when only modification time differs

I tried to synchronize a DropBox directory to local and vice versa. For some files --dry-run reported "Not updating modification time as --dry-run" but then real "sync" started transferring the file, even though the content was already identical, just to update the modification time. I can understand that possibly a cloud service API might not allow setting just mtime, but local filesystem certainly does.

What is your rclone version (eg output from rclone -V)

rclone v1.38
- os/arch: darwin/amd64
- go version: go1.9

Which OS you are using and how many bits (eg Windows 7, 64 bit)

OS X El Capitan

Which cloud storage system are you using? (eg Google Drive)

DropBox

The command you were trying to run (eg rclone copy /tmp remote:tmp)

rclone sync -v dropbox:some/path/ /Volumes/external_disk/some/path/

A log from the command with the -vv flag (eg output from rclone -vv copy /tmp remote:tmp)

Can you paste a log with -vv of the problem?

OK. Probably I wrongly observed the behavior. For dropbox -> local it now modified the mtime without download. For local -> dropbox it said it can't update mtime so it reuploaded it.
Same mtime:
$ rclone sync -vv dropbox:tmp/rclone-1798/ .
2017/11/05 21:10:27 DEBUG : Using config file from "/Users/bzamecnik/.rclone.conf"
2017/11/05 21:10:27 DEBUG : rclone: Version "v1.38" starting with parameters ["rclone" "sync" "-vv" "dropbox:tmp/rclone-1798/" "."]
2017/11/05 21:10:28 INFO  : Local file system at /Users/bzamecnik/tmp/rclone-1798: Modify window is 1s
2017/11/05 21:10:29 DEBUG : J.S.Bach - Tocata - D Moll.mp3: Size and modification time the same (differ by 0s, within tolerance 1s)
2017/11/05 21:10:29 DEBUG : J.S.Bach - Tocata - D Moll.mp3: Unchanged skipping
2017/11/05 21:10:29 INFO  : Local file system at /Users/bzamecnik/tmp/rclone-1798: Waiting for checks to finish
2017/11/05 21:10:29 INFO  : Local file system at /Users/bzamecnik/tmp/rclone-1798: Waiting for transfers to finish
2017/11/05 21:10:29 INFO  : Waiting for deletions to finish
2017/11/05 21:10:29 INFO  :
Transferred:      0 Bytes (0 Bytes/s)
Errors:                 0
Checks:                 1
Transferred:            0
Elapsed time:        1.3s

After touch:
$ touch J.S.Bach\ -\ Tocata\ -\ D\ Moll.mp3
$ rclone sync -vv dropbox:tmp/rclone-1798/ .
2017/11/05 21:10:47 DEBUG : Using config file from "/Users/bzamecnik/.rclone.conf"
2017/11/05 21:10:47 DEBUG : rclone: Version "v1.38" starting with parameters ["rclone" "sync" "-vv" "dropbox:tmp/rclone-1798/" "."]
2017/11/05 21:10:48 INFO  : Local file system at /Users/bzamecnik/tmp/rclone-1798: Modify window is 1s
2017/11/05 21:10:48 INFO  : Local file system at /Users/bzamecnik/tmp/rclone-1798: Waiting for checks to finish
2017/11/05 21:10:48 DEBUG : J.S.Bach - Tocata - D Moll.mp3: Modification times differ by 45820h18m9s: 2012-08-14 15:52:34 +0000 UTC, 2017-11-05 21:10:43 +0100 CET
2017/11/05 21:10:48 INFO  : J.S.Bach - Tocata - D Moll.mp3: Updated modification time in destination
2017/11/05 21:10:48 DEBUG : J.S.Bach - Tocata - D Moll.mp3: Unchanged skipping
2017/11/05 21:10:48 INFO  : Local file system at /Users/bzamecnik/tmp/rclone-1798: Waiting for transfers to finish
2017/11/05 21:10:48 INFO  : Waiting for deletions to finish
2017/11/05 21:10:48 INFO  :
Transferred:      0 Bytes (0 Bytes/s)
Errors:                 0
Checks:                 1
Transferred:            0
Elapsed time:        1.2s

Dropbox -> local:
$ touch J.S.Bach\ -\ Tocata\ -\ D\ Moll.mp3
$ rclone sync -vv .  dropbox:tmp/rclone-1798/
2017/11/05 21:11:08 DEBUG : Using config file from "/Users/bzamecnik/.rclone.conf"
2017/11/05 21:11:08 DEBUG : rclone: Version "v1.38" starting with parameters ["rclone" "sync" "-vv" "." "dropbox:tmp/rclone-1798/"]
2017/11/05 21:11:09 INFO  : Dropbox root 'tmp/rclone-1798': Modify window is 1s
2017/11/05 21:11:09 INFO  : Dropbox root 'tmp/rclone-1798': Waiting for checks to finish
2017/11/05 21:11:09 DEBUG : J.S.Bach - Tocata - D Moll.mp3: Modification times differ by -45820h18m30s: 2017-11-05 21:11:04 +0100 CET, 2012-08-14 15:52:34 +0000 UTC
2017/11/05 21:11:09 DEBUG : J.S.Bach - Tocata - D Moll.mp3: src and dst identical but can't set mod time without deleting and re-uploading
2017/11/05 21:11:11 INFO  : Dropbox root 'tmp/rclone-1798': Waiting for transfers to finish
2017/11/05 21:11:13 INFO  : J.S.Bach - Tocata - D Moll.mp3: Copied (replaced existing)
2017/11/05 21:11:13 INFO  : Waiting for deletions to finish
2017/11/05 21:11:13 INFO  :
Transferred:   2.354 MBytes (456.104 kBytes/s)
Errors:                 0
Checks:                 1
Transferred:            1
Elapsed time:        5.2s

What I needed was to add the --no-update-modtime argument:
$ touch J.S.Bach\ -\ Tocata\ -\ D\ Moll.mp3
$ rclone sync --no-update-modtime -vv .  dropbox:tmp/rclone-1798/
2017/11/05 21:15:42 DEBUG : Using config file from "/Users/bzamecnik/.rclone.conf"
2017/11/05 21:15:42 DEBUG : rclone: Version "v1.38" starting with parameters ["rclone" "sync" "--no-update-modtime" "-vv" "." "dropbox:tmp/rclone-1798/"]
2017/11/05 21:15:42 INFO  : Dropbox root 'tmp/rclone-1798': Modify window is 1s
2017/11/05 21:15:43 INFO  : Dropbox root 'tmp/rclone-1798': Waiting for checks to finish
2017/11/05 21:15:43 DEBUG : J.S.Bach - Tocata - D Moll.mp3: Modification times differ by -4m31s: 2017-11-05 21:15:35 +0100 CET, 2017-11-05 20:11:04 +0000 UTC
2017/11/05 21:15:43 DEBUG : J.S.Bach - Tocata - D Moll.mp3: Unchanged skipping
2017/11/05 21:15:43 INFO  : Dropbox root 'tmp/rclone-1798': Waiting for transfers to finish
2017/11/05 21:15:43 INFO  : Waiting for deletions to finish
2017/11/05 21:15:43 INFO  :
Transferred:      0 Bytes (0 Bytes/s)
Errors:                 0
Checks:                 1
Transferred:            0
Elapsed time:        1.2s

2017/11/05 21:15:43 DEBUG : Go routines at exit 4
2017/11/05 21:15:43 DEBUG : rclone: Version "v1.38" finishing with parameters ["rclone" "sync" "--no-update-modtime" "-vv" "." "dropbox:tmp/rclone-1798/"]

Thanks.

Yes, it is a bit annoying that you can't change the modtime of a file without re-uploading it, but your --no-update-modtime is a good workaround.

rclone helped a lot when uploading data from my external drive to Dropbox. Today after a lot of searching I found odrive service and it's synchronization seems to work really well and without pain and fear of losing files even for two-way merge. Anyway rclone is still great eg. for disk usage.


support tcp NO_DELAY

export  noDelay option ,it can enable TCP NO_DELAY(disable Nagle algorithm)

Coverage remained the same at 93.734% when pulling c387f4ed1d05eaae0300e6b3e6df015f96d2895d on leonlau:master into 46e275c407f81c44dd9aad419b6e861d8a936580 on mzabriskie:master.

Closed due to the repository has been removed. And in favor of #2808.


Neovim: migrate to another comment plugin

I want to migrate to https://github.com/JoosepAlviste/nvim-ts-context-commentstring

This is not a migration, just adding a bit of functionality.


not able to recover pulumi source code resources

Hello,
Have created the pulumi azure typescript project and somehow lost the source code (files like index.ts etc.) . By searching the doc, have found the following steps to recover the configuration.
Recovering Configuration
Deleting this stack or this stack's resources requires that you have a Pulumi.yaml file in the same directory.
# Pulumi.yaml
echo "name: azure_cloud_proj" > Pulumi.yaml
echo "runtime: nodejs" >> Pulumi.yaml

# Pulumi.dev.yaml
pulumi stack select azure_cloud_infra/azure_cloud_proj/dev
pulumi config refresh

the issue is , the doc is not bit clear.   should we create the same directory as previous and run above commands OR any directory would do ?
further, just created the same directory as previous and ran the command . got the following error : please suggest

C:\azure_cloud_infra>pulumi stack select azure_cloud_infra/azure_cloud_proj/dev
error: could not get cloud url: could not load current project: yaml: unmarshal errors:
  line 1: cannot unmarshal !!str `name: a...` into workspace.Project

C:\azure_cloud_infra>

please suggest

@joeduffy : can you please suggest ?

@joeduffy : can you please suggest ?

Any directory should do. I agree this is a bit unfortunate, I think we have a bug tracking the idea of being able to destroy without a working directory, but that would require slight changes to the way configuration works. @justinvp Is that right?
As to the latest error, it appears maybe there's a problem with the YAML unmarshaling. Provided there isn't anything sensitive in there, would you mind sharing the contents of your Pulumi.yaml file?

Thanks.
this is what we have in pulumi.yaml. please suggest
"name: azure_cloud_proj"
"runtime: nodejs"

@joeduffy : please suggest

I think you can remove the quotes and it should work:
name: azure_cloud_proj
runtime: nodejs

Can you give this a try?
If so, and assuming you found those echo instructions that led to the quotes on our website, could you share a link to it so we can fix the problem with the documentation?

@joeduffy : Thanks . it worked.
however, pulumi up command is not working. following is the error we are getting.

C:\azure_cloud_infra>pulumi up
Previewing update (azure_cloud_infra/dev)
View Live: https://app.pulumi.com/azure_cloud_infra/azure_cloud_proj/dev/previews/f059b778-9587-4d46-ba52-b1989356677a
 Type                 Name                  Plan     Info
 pulumi:pulumi:Stack  azure_cloud_proj-dev           1 message

Diagnostics:
pulumi:pulumi:Stack (azure_cloud_proj-dev):
error: could not find node on the $PATH: exec: "node": executable file not found in %PATH%
error: failed to load language plugin nodejs: could not read plugin [C:\ProgramData\chocolatey\lib\pulumi\tools\Pulumi\bin\pulumi-language-nodejs.exe] stdout: EOF
C:\azure_cloud_infra>

is this expected ? if so, what is the recommended steps to recover all typescripts files along with state so that we can run "pulumi up" command. Thanks

@joeduffy : any update ?

@joeduffy : any update please ? this is blocker for us . if you are busy , can you assign any one of your engineer to work on this ?
I feel it is very simple but unnecessary getting streched.

It looks like Node.js might not be installed? That is a required dependency for Pulumi projects that use Node.js as the language runtime. Instructions for how to install are available at https://www.pulumi.com/docs/get-started/azure/begin/#install-language-runtime

@joeduffy : after installing node.js , now complaining for some pulumi SDK

C:\azure_cloud_infra>pulumi up
Previewing update (azure_cloud_infra/dev)
View Live: https://app.pulumi.com/azure_cloud_infra/azure_cloud_proj/dev/previews/0810ca6d-adc0-4bd6-817a-d2104c9893d1
 Type                 Name                  Plan     Info
 pulumi:pulumi:Stack  azure_cloud_proj-dev           1 message

Diagnostics:
pulumi:pulumi:Stack (azure_cloud_proj-dev):
error: It looks like the Pulumi SDK has not been installed. Have you run npm install or yarn install?
warning: A new version of Pulumi is available. To upgrade from version '3.5.1' to '3.6.0', visit https://pulumi.com/docs/reference/install/ for manual instructions and release notes.
error: failed to load language plugin nodejs: could not read plugin [C:\ProgramData\chocolatey\lib\pulumi\tools\Pulumi\bin\pulumi-language-nodejs.exe] stdout: EOF

after googling , haven't found any good link which says how to install pulumi SDK

Installation instructions are here: https://www.pulumi.com/docs/get-started/install/. You would need to npm install @pulumi/pulumi to get the SDK. However, I thought you were just trying to destroy a stack -- if you don't have the source code, pulumi up isn't going to work. To destroy, you can run pulumi destroy, which shouldn't require the SDK.

@joeduffy : the sole purpose of this ticket is to : "how to recover the deleted source code of pulumi resources"
I am not just trying to destroy the stack but trying to understand how to recover all typescripts source code which got deleted accidently.
please suggest

@joeduffy : please suggest

@joeduffy : any update please ? this is blocker

There were a few questions in this thread, and I don't feel like I have understanding of what this issue is tracking at this point. Since it's 2 years old, I'll go ahead and close it. Please open a new issue for any remaining problem.


Improve implementation of Secret Management in Adaptive Authentication Scripts

Describe the issue:
Focuses on integrating a secret management system within adaptive authentication scripts. The key enhancement involves writing a JavaScript wrapper function to facilitate passing resolved secrets directly within the adaptive authentication scripts. This change aims to unify secret management across WSO2 Identity Server, enhancing security and simplifying script development.

Developer Testing

Create an application and add the following in the login flow.

First Factor - Username & Password
Second Factor - Passkey

Add the following script

var url = "https://token3.free.beeceptor.com/token3";

var authConfig = {
    "type": "clientcredential",
    "properties": {
        consumerKey: secrets.clientId,
        consumerSecret: secrets.clientSecret,
        tokenEndpoint: "https://api.asgardeo.io/t/suborg4/oauth2/token"
    }
};

var requestHeaders = {
    "accept": "application/json"
};

var secretTest1 = secrets.test1;

var groupsToStepUp = ['manager', 'employee'];
Log.info('Secret test2 : ' + secrets.test2);

var onLoginRequest = function(context) {
    Log.info('Secret test3 : ' + secrets.test3);
    executeStep(1, {
        onSuccess: function(context) {

            var payload = {
                ip: context.request.ip
            }

            Log.info('Secret test4 : ' + secrets.test4);

            httpPost(url, payload, requestHeaders, authConfig, {
                onSuccess: function(context, data) {
                    Log.info('Received risk:' + data.hasRisk);
                    Log.info('Secret test7 : ' + secrets.test7);
                    if (data.hasRisk === true) {
                        Log.info('Secret test6 : ' + secrets.test6);
                        // Prompt the second authentication factor if the hasRisk is true.
                        executeStep(2, {
                            onSuccess: function(context) {
                                Log.info('Secret test1 : ' + secretTest1);
                                Log.info('Secret test5 : ' + secrets.test5);
                            }
                        });
                    }
                }
            });
        }
    });
};

Add the following secrets

clientId: ""
clientSecret: "client secret of the choreo created app"
test1: "secretValTest1"
test2: "secretValTest2"
test3: "secretValTest3"
test4: "secretValTest4"
test5: "secretValTest5"
test6: "secretValTest6"
test7: "secretValTest7"

Log in with a user and check the terminal logs for the secrets

Verified on the latest pack as per 30/10/2024


Can't change volume on call without a dedicated pattern?

Is there a way to let the volume buttons do their default behavior (change call volume on call, media otherwise) without making one pattern for media and another for calling? As a temporary fix, I'm using down for media and up for calling, but I don't think that is a good long-term solution.
Thank you for any assistance!

You can use volume current

Works great! Thank you :)


Cannot cast spells through staff, claims "Not enough slots"/Staff has too many charges

Trying to cast a spell granted by a staff just gives a yellow "Cannot cast [spell] at [level], not enough spell slots". This happens regardless of how many charges are left on the staff

Any character sheet modules? What version of the PF2e Staves do you have installed?

To my knowledge, the only other module I have that affects the character sheet is PF2e Workbench, though I had that previously and the Staves worked fine. I have version 1.1.2 of PF2e Staves, which Foundry tells me is the latest. I believe it stopped working upon upgrading to this version, or it broke when the pf2e system itself updated

Gotcha, I'll take a look. Do you have libWrapper installed and enabled? That was a new requirement in the latest version of the module.

I had it installed, but apparently didn't have it enabled. Enabling it fixed the problem.
While I'm here, I have a different issue as well. The number of charges you get is supposed to be equal to the level of your highest spell slot, but my level 3 wizard (with druid archetype) is getting 9 charges.

Can I get a screenshot of the spells tab of the character sheet?

Lots of spell fields so it's spread across 2 screenshots

Hm, I'm not able to reproduce on my end. Would you be able to export the actor JSON file and attach it here?

GitHub doesn't support sending json files, is there somewhere else I can send it to?

you can email it to me<EMAIL_ADDRESS>

Sent

Staves get a number of charges based on the character's highest available spell slot level. For some reason, the "School Spells" spellcasting entry on this character has slots up to level 9, which is why staves get 9 charges. My guess is at some point a 9th level spell was on this entry and then removed, but the slots weren't fixed.
I would try deleting and recreating this spell slot entry.


Word: strange bar appearing on cover page

Not sure why this is happening. This is a regression from a bundle update yesterday. This doesn't seem to show on Windows (I'm on a Mac), and only shows on Print/Web views.
Print view (shows strange bar):

Draft view (no issue):

I get this periodically, and I haven't been able to work out why, though it might be related to XHTML formatting errors in the print page.

I think I've worked it out.
The grey bar is triggered by the presence of an explicit <br style="mso-break-type:section-break"/>, i.e. the HTML representation of a Word section break. It does not happen all the time: the trigger appears to be that the previous paragraph has either text-align:right, or font-weight:bold. (Of course, there may well be other triggers.) That's why this is only happening on title pages.
The problem is, this is what happens in the IEEE template with the title at the start of the main section, and the grey bar does not show up there, even when I save the Word MHT and read it back in from HTML. So there are other conditions at play, which I have not been able to work out.
The only remedy I can apply appears is to interpolate a default, Normal style paragraph between any styled title paragraphs and the section break. It introduces an extra line into IEEE line numbering (the section break ends up on a blank line), but frankly, that's the least of our problems, and I will make that line zero-height.

In fact, @ronaldtse, I've just remembered:
I have put a placeholder empty carriage return at the end of all title pages, which prevents this behaviour.
Which  you, @ronaldtse, demanded I remove in DIS: https://github.com/metanorma/metanorma-iso/issues/674
I have spent 2 hours trying to work out what else is causing this behaviour, and I can't. By making me remove a harmless blank line, you have introduced this behaviour where it did not appear before. You either accept the blank line, or you accept the grey bar. Your call.

Let's accept the gray bar for now. I just found out that other ISO DIS/PRF word documents see the same gray bar! (On macOS only, not on Windows)

It is a systematic thing in ISO DIS/PRF: the line before the section break on the cover page is right aligned, and that is a trigger for this behaviour.


ServiceExportReconciler keep re registering instances in aws cloudmap

Hi,
We are running v0.3.1 of aws-cloud-map-mcs-controller to register services to aws cloudmap. we have another application looks up cloudmap for service discovery. we have a requirement to populate some custom attributes for cloud map instances.
is there a way to define custom attributes in ServiceExport definition of kubernates object?. currently its defined like this.
kind: ServiceExport
apiVersion: multicluster.x-k8s.io/v1alpha1
metadata:
namespace: namespace1
name: service-name
currently we are using a lambda trigger in aws to populate these custom attributes. this is causing an issue with ServiceExportReconciler , its keep re registering instances in aws cloudmap as endpoint/instance definition is different in aws cloudmap to what controller desires . is there a way to stop this re register from happening?.
Thank you.

Hi Akash,
Many thanks for your response,
we are trying to understand what change is triggering the re registrations. in kubernates the app exposed by the service hasnt restarted for last 16 hours means the ip shouldnt change, also the port 8080 stays constant.
$ date
Thu Dec  7 09:55:51 UTC 2023
$ kubectl get po rest-api-develop-fc4d7778c-pqss5  -n participant1-develop -o wide
NAME                               READY   STATUS    RESTARTS   AGE   IP               NODE                             NOMINATED NODE   READINESS GATES
rest-api-develop-fc4d7778c-pqss5   1/1     Running   0          16h   <IP_ADDRESS>   ip-172-24-126-165.ec2.internal
this is kubernates service config.
$ kubectl describe svc rest-api-develop -n participant1-develop
Name:                     rest-api-develop
Namespace:                participant1-develop
Labels:                   app.kubernetes.io/instance=rest-api-develop
app.kubernetes.io/managed-by=Helm
app.kubernetes.io/name=rest-api
app.kubernetes.io/version=1.16.0
helm.sh/chart=rest-api-0.1.0
Annotations:              meta.helm.sh/release-name: rest-api-develop
meta.helm.sh/release-namespace: participant1-develop
Selector:                 app.kubernetes.io/instance=rest-api-develop,app.kubernetes.io/name=rest-api
Type:                     NodePort
IP Family Policy:         SingleStack
IP Families:              IPv4
IP:                       <IP_ADDRESS>
IPs:                      <IP_ADDRESS>
Port:                     ra-main  8080/TCP
TargetPort:               8080/TCP
NodePort:                 ra-main  30679/TCP
Endpoints:                <IP_ADDRESS>:8080
Session Affinity:         None
External Traffic Policy:  Cluster
Events:
below are logs of two occurrences of endpoint re registration for namespace participant1-develop, service rest-api-develop. as you see its registering instances/endpoints to cloudmap with same ip(ip didnt change), ideally we expect it shouldnt update cloudmap as there is no change.  i have attached full logs of controller for your reference.
--
{"level":"info","ts":1701931995.9447143,"logger":"controllers.ServiceExportReconciler","msg":"updating Cloud Map service","namespace":"participant1-develop","name":"rest-api-develop"}
{"level":"info","ts":1701931995.9447424,"logger":"cloudmap.client","msg":"fetching a service","namespace":"participant1-develop","name":"rest-api-develop"}
{"level":"info","ts":1701931995.9447896,"logger":"cloudmap.client","msg":"registering endpoints","namespaceName":"participant1-develop","serviceName":"rest-api-develop","endpoints":[{"Id":"tcp-172_24_126_21
9-8080","IP":"<IP_ADDRESS>","EndpointPort":{"Name":"ra-main","Port":8080,"TargetPort":"","Protocol":"TCP"},"ServicePort":{"Name":"ra-main","Port":8080,"TargetPort":"8080","Protocol":"TCP"},"ClusterId":"1s
ource-develop","ClusterSetId":"1source","ServiceType":"ClusterSetIP","ServiceExportCreationTimestamp":1694697956000,"Ready":true,"Hostname":"","Nodename":"ip-172-24-126-165.ec2.internal","Attributes":{"K8S_
CONTROLLER":"aws-cloud-map-mcs-controller-for-k8s 887737e (887737e)"}}]}
{"level":"info","ts":1701937389.3627253,"logger":"controllers.ServiceExportReconciler","msg":"updating Cloud Map service","namespace":"participant1-develop","name":"rest-api-develop"}
{"level":"info","ts":1701937389.3627617,"logger":"cloudmap.client","msg":"fetching a service","namespace":"participant1-develop","name":"rest-api-develop"}
{"level":"info","ts":1701937389.3628213,"logger":"cloudmap.client","msg":"registering endpoints","namespaceName":"participant1-develop","serviceName":"rest-api-develop","endpoints":[{"Id":"tcp-172_24_126_21
9-8080","IP":"<IP_ADDRESS>","EndpointPort":{"Name":"ra-main","Port":8080,"TargetPort":"","Protocol":"TCP"},"ServicePort":{"Name":"ra-main","Port":8080,"TargetPort":"8080","Protocol":"TCP"},"ClusterId":"1s
ource-develop","ClusterSetId":"1source","ServiceType":"ClusterSetIP","ServiceExportCreationTimestamp":1694697956000,"Ready":true,"Hostname":"","Nodename":"ip-172-24-126-165.ec2.internal","Attributes":{"K8S_
CONTROLLER":"aws-cloud-map-mcs-controller-for-k8s 887737e (887737e)"}}]}
would you help us understand what change is triggering the update?.
cloud-map-mcs-controller.log
is there a way to increase logging level and to change timestamp format to human readable? (we are running the controller using command kubectl apply -k "mcs-controller/controller_install_release" after downloading everything from https://github.com/aws/aws-cloud-map-mcs-controller-for-k8s/tree/main/config locally, we can change this file config/default/manager_auth_proxy_patch.yaml to add additional arg here if you tell us what it should be to increase tracing and change time format).

name: manager
args:
- "--health-probe-bind-address=:8081"
- "--metrics-bind-address=<IP_ADDRESS>:8080"
- "--leader-elect"

Regards
Shekhar

cloud-map-mcs-controller.log

You can use this reference to customize the logging https://sdk.operatorframework.io/docs/building-operators/golang/references/logging/

Hi,
Thank you for that we changed loglevel to debug(--zap-log-level debug), and captured the logs when re registration of endpoints happened. looking at logs it is not clear why this happened, as the endpoint app did not restart and endpoint ips did not change.
here is the full log.
mcs-controlller-debug.log
log snippet when re registering endpoints.
sterSetId":"1source"}
2023-12-08T16:35:56.058213089Z stderr F {"level":"debug","ts":1702053356.0581286,"logger":"controllers.ServiceExportReconciler","msg":"reconciling ServiceExport","Namespace":"participant1-develo
p","Name":{"namespace":"participant1-develop","name":"rest-api-develop"}}
2023-12-08T16:35:56.058251185Z stderr F {"level":"info","ts":1702053356.0581875,"logger":"controllers.ServiceExportReconciler","msg":"updating Cloud Map service","namespace":"participant1-develo
p","name":"rest-api-develop"}
2023-12-08T16:35:56.05827025Z stderr F {"level":"info","ts":1702053356.058198,"logger":"cloudmap.client","msg":"fetching a service","namespace":"participant1-develop","name":"rest-api-develop"}
2023-12-08T16:35:56.058335948Z stderr F {"level":"info","ts":1702053356.0582664,"logger":"cloudmap.client","msg":"registering endpoints","namespaceName":"participant1-develop","serviceName":"res
t-api-develop","endpoints":[{"Id":"tcp-172_24_126_204-8080","IP":"<IP_ADDRESS>","EndpointPort":{"Name":"ra-main","Port":8080,"TargetPort":"","Protocol":"TCP"},"ServicePort":{"Name":"ra-main","
Port":8080,"TargetPort":"8080","Protocol":"TCP"},"ClusterId":"1source-develop","ClusterSetId":"1source","ServiceType":"ClusterSetIP","ServiceExportCreationTimestamp":1694697956000,"Ready":false,
"Hostname":"","Nodename":"ip-172-24-126-165.ec2.internal","Attributes":{"K8S_CONTROLLER":"aws-cloud-map-mcs-controller-for-k8s 887737e (887737e)"}},{"Id":"tcp-172_24_126_219-8080","IP":"172.24.1
26.219","EndpointPort":{"Name":"ra-main","Port":8080,"TargetPort":"","Protocol":"TCP"},"ServicePort":{"Name":"ra-main","Port":8080,"TargetPort":"8080","Protocol":"TCP"},"ClusterId":"1source-deve
lop","ClusterSetId":"1source","ServiceType":"ClusterSetIP","ServiceExportCreationTimestamp":1694697956000,"Ready":true,"Hostname":"","Nodename":"ip-172-24-126-165.ec2.internal","Attributes":{"K8
S_CONTROLLER":"aws-cloud-map-mcs-controller-for-k8s 887737e (887737e)"}}]}
2023-12-08T16:35:57.981590837Z stderr F {"level":"debug","ts":1702053357.9814687,"logger":"controllers.CloudmapReconciler","msg":"clusterProperties found","ClusterId":"1source-develop","ClusterS
etId":"1source"}
2023-12-08T16:35:57.981632268Z stderr F {"level":"debug","ts":1702053357.9815843,"logger":"controllers.CloudmapReconciler","msg":"syncing namespace","namespace":"participant1-develop"}
2023-12-08T16:35:57.988809874Z stderr F {"level":"debug","ts":1702053357.98873,"logger":"controllers.CloudmapReconciler","msg":"syncing service","namespace":"participant1-develop","service":"res
t-api-develop"}
2023-12-08T16:35:57.98900082Z stderr F {"level":"debug","ts":1702053357.9889314,"logger":"controllers.CloudmapReconciler","msg":"updating EndpointSlice","namespace":"participant1-develop","name"
:"imported-vonhveonrv-m6dsh"}
2023-12-08T16:35:57.997397891Z stderr F {"level":"debug","ts":1702053357.9972944,"logger":"controllers.ServiceExportReconciler","msg":"clusterProperties found","ClusterId":"1source-develop","Clu
sterSetId":"1source"}
2023-12-08T16:35:57.998135175Z stderr F {"level":"debug","ts":1702053357.998055,"logger":"controllers.CloudmapReconciler","msg":"syncing namespace","namespace":"participant2-develop"}
2023-12-08T16:35:58.002388689Z stderr F {"level":"debug","ts":1702053358.0023232,"logger":"controllers.CloudmapReconciler","msg":"syncing service","namespace":"participant2-develop","service":"r
est-api-develop"}

we have 3 service export objects in kubernates, when re registration happens it happens for all 3 services.

we are seeing this re registration behavior happening every few hours and we are unclear what is triggering this. each occurrence of this issue results in few seconds of service outage.

would you help us how to prevent this happening?,

Thank you Regards
Shekhar

On reviewing the ServiceExport controller code, it seems we are exporting the endpoints based on the k8s events on the Service and EndpointSlice. Updating metadata will trigger the k8s events, thus it's getting overridden.

Hi Akash,
we compared Service, EndpointSlice k8s objects definitions for effected endpoints before and after the occurrence of the problem and they are exactly identical, we do not see any metadata difference (command ran kubectl describe endpointslices rest-api-staging-xkqrz -n participant1-staging).
here is an example endpoint slice.
endpointslices_p1_10-12.txt
also we captured kubernates events for last 24 hours of namespace the service is in , we do not see any k8s event at exact time the problem occurs. are we missing anything?.
On a side note we created service export objects for 2 new services(just to test) within same cluster yesterday.  we did not see the problem occurred for the new services. however for original service it occurred 8 to 10 times in last 24 hours.  1 of test service runs on same k8s node(ec2) and other runs on different node. interestingly the only difference between the test services and live service is the custom attributes we populated in cloudmap for the instances using a lambda.
Would you help us to get to the bottom of this issue, please let us know if you need any information from our side.
Regards
Shekhar

Hi Akash,
we captured all k8s events in the cluster for last few hours, attached the events dump file.  also attaching mcs controller log.
mcs_controller_log_20231212.txt
events_log_20231212.txt
as we see in mcs controller log  controller is re reregistering instance tcp-172_24_125_249-8080 at 2023-12-12T11:45:55.
Name":{"namespace":"participant1-qar","name":"rest-api-qar"}}
2023-12-12T11:45:55.611488108Z stderr F {"level":"info","ts":1702381555.6114109,"logger":"controllers.ServiceExportReconciler","msg":"updating Cloud Map service","namespace":"participant1-qar","
name":"rest-api-qar"}
2023-12-12T11:45:55.611498026Z stderr F {"level":"info","ts":1702381555.6114464,"logger":"cloudmap.client","msg":"fetching a service","namespace":"participant1-qar","name":"rest-api-qar"}
2023-12-12T11:45:55.617349345Z stderr F {"level":"info","ts":1702381555.6172726,"logger":"cloudmap.client","msg":"registering endpoints","namespaceName":"participant1-qar","serviceName":"rest-ap
i-qar","endpoints":[{"Id":"tcp-172_24_125_249-8080","IP":"<IP_ADDRESS>","EndpointPort":{"Name":"ra-main","Port":8080,"TargetPort":"","Protocol":"TCP"},"ServicePort":{"Name":"ra-main","Port":80
80,"TargetPort":"8080","Protocol":"TCP"},"ClusterId":"1source-qar","ClusterSetId":"1source","ServiceType":"ClusterSetIP","ServiceExportCreationTimestamp":1700579083000,"Ready":true,"Hostname":""
,"Nodename":"ip-172-24-125-8.ec2.internal","Attributes":{"K8S_CONTROLLER":"aws-cloud-map-mcs-controller-for-k8s 887737e (887737e)"}}]}

we do not see any K8s events at this time. we see some events at 2023-12-12T11:40:42(5 minutes before the issue) of type SuccessfullyReconciled for targetGroupBinding,
.[0K4.
6","resourceVersion":"32067978","creationTimestamp":"2023-12-12T11:40:42Z","managedFields":[{"manager":"controller","operation":"Update","apiVersion":"v1","time":"2023-12-12T11:40:42Z"}]},"invol
.[0Kv.
edObject":{"kind":"TargetGroupBinding","namespace":"participant3-qar","name":"rest-api-qar","uid":"ac1dd5d8-ae3c-4023-a087-8b7ce140f3ad","apiVersion":"elbv2.k8s.aws/v1beta1","resourceVersion":"2
.[0K4.
208797"},"reason":"SuccessfullyReconciled","message":"Successfully reconciled","source":{"component":"targetGroupBinding"},"firstTimestamp":"2023-12-11T06:47:40Z","lastTimestamp":"2023-12-12T11:
.[0K4.
0:42Z","count":28,"type":"Normal","eventTime":null,"reportingComponent":"","reportingInstance":""}}.[0K.

we can confirm these events wont update service/endpointslices meta data as we captured and compared service/endpointslices k8s objects before and after the issue and they are identical.
also these k8s events gets generated exactly once every hour and we are not seeing the issue happening every hour.
would you be able to help us to identify which event is causing the controller to re register the endpoints.

Hi,
Just to update on this,
We are still not sure what is triggering this change. however we are sure that the issue only occurs to instances to which we add custom attributes in aws cloudmap.
we have 4 similar applications running on same K8s node, the issue happens to 3 instances (around same time), for 1 it wont happen. the 1 instance being the one for which we are not altering aws cloudmap attributes. we we added custom attribute to this instance in cloudmap the issue started happening.
Regards
Shekhar.

Hello,
There is no code logic within the controller that triggers the re-registration. The controller subscribes to kubernetes updates events for the kind ServiceExport, Service, EndpointSlice and ClusterProperty. Unfortunately we don't have enough observability to say what kind-of update is triggering an event.
You can choose to fork the controller and implement the attributes reconciliation. The way to approach this will be to add the instance attributes as ServiceExport object annotations
kind: ServiceExport
apiVersion: multicluster.x-k8s.io/v1alpha1
metadata:
  namespace: example
  name: my-service
  annotations:
    attr1: val1
    attr2: val2

And then update the serviceexport_controller.go to export the annotations as attributes.
You can push the change as a PR, and we can review the code.

And a disclaimer that the mcs controller is in alpha stage. Should be used in production system with caution.


Filter user date

New facet for CollectionObject filter page.
New class methods of User:

User.get_user_id(user) to get one specific user, accepts String, User, Integer, requires exact match if string is used (name or email)
User.get_user_ids(user, user, user, ...) to get array of Ids, accepts String, User, Integer, uses partial string match (name or email)

New helper for users:

project_users_select_tag(user_element, default_name = nil): Select of all users in the current project, returns 'All users' or id of selected user, If default id is not supplied, 'All users' is selected.
user_select_tag(user_element, user_id_list, default_name = nil): As project_users_select_tag, but not limited to current project users.

@TuckerJD can you resolve the pack-lock issue?

@TuckerJD Added some things to tweak.  Most critically, thou shalt not use $ constants, get rid of them please.

I think I hit all the issues...

Coverage increased (+0.05%) to 67.094% when pulling da9687f100325743babc50057ba430ee483b083a on filter_user_date into fb96a31315780aeefe117a43a8eeb48708f99691 on development.

Coverage increased (+0.07%) to 67.112% when pulling 9ad78d09d801f34a066a4548615612f32939652c on filter_user_date into fb96a31315780aeefe117a43a8eeb48708f99691 on development.


Correction to current wavelength and UB matrix calculation.

In the example notebooks, it is stated that:

The compute_UB() method uses the current wavelength.

This is not correct.  The correct text should identify that the current wavelength is used when each reflection is added, via: Diffractometer.calc.sample.add_reflection().  It is possible to calculate UB from two orientation reflections, each with a different wavelength.
This association is handled (now) by the libhkl support library.

This change will cause a merge conflict with PR #190 unless this one line is changed as part of that PR.

only one file is affected:
(base) prjemian@zap:~/.../Bluesky/hklpy$ git grep "uses the current wavelength"
examples/geo_e4cv.ipynb:    "The `compute_UB()` method uses the current wavelength.  It always returns 1.  Ignore it."

revised text:

The add_reflection() method uses the current wavelength at the time it is called.  (To add reflections at different wavelengths, change the wavelength before calling add_reflection() each time.)  The compute_UB() method returns the computed UB matrix.  Ignore it here.


Standardize message timestamp naming

Taking approach 1 from #406.

Require all DWN message to have messageTimestamp
dateCreated is a method specific property, ie. in RecordsWrite.
Remove/rename all other variant of date related properties accordingly.

In RecordsWrite, RecordsDelete, and ProtocolsConfigure: dateModified -> messageTimestamp.
RecordsWrite retains the dateCreated field, which refers to the time that the record was created.
In RecordsRead: date -> messageTimestamp
EventsGet and MessagesGet do not have timestamps of any kind.
In all other DWN messages, dateCreated -> messageTimestamp

@diehuxx, everything looks great, though I think we should also add timestamp for MessageGet and EventGet to prevent replay. What do you think? Obviously we'd need to add more checks, but that can be done in a future PR.

add timestamp for MessageGet and EventGet to prevent replay

I don't see any reason why not, but not sure if I understand the reason. What do you mean by replay? Also, does the timestamp have any significance if we aren't storing the MessagesGet or EventsGet messages and we aren't using the timestamp for filtering purposes?

I don't see any reason why not, but not sure if I understand the reason. What do you mean by replay? Also, does the timestamp have any significance if we aren't storing the MessagesGet or EventsGet messages and we aren't using the timestamp for filtering purposes?

Imagine if a bad actor got hold of a legit (signed) MessageGet message. They can just send this message to a DWN to get the message back any time in the future (assuming no key rotation).

we aren't using the timestamp for filtering purposes?

Yeah... that's the "we'd need to add more checks, but that can be done in a future PR" part I was referring to, as in, check the timestamp against the current server time, if it's outside of the acceptable "server time drift" range, ignore. This applies to all fetch-type messages that we have including RecordsQuery and RecordsRead.

Imagine if a bad actor got hold of a legit (signed) MessageGet message. They can just send this message to a DWN to get the message back any time in the future (assuming no key rotation).

Ahhh okay I see. Thanks for the explanation :). Just pushed a commit adding timestamp to EventsGet and MessagesGet.


typo: unkown -> unknown

Should I update the changelog for this mission-critical PR? :laughing:
My contribs are unstoppable this week.
I didn't actually find that myself:
reazem@cranberry:~/git/debian-pkg/build-area$ lintian *.deb
N: Using profile debian/main.
N: Setting up lab in /tmp/temp-lintian-lab-eTEqeb5ewT ...
N: Unpacking packages in group influxdb/<IP_ADDRESS>+dfsg1-1
N: ----
N: Processing binary package golang-github-influxdb-influxdb-dev (version <IP_ADDRESS>+dfsg1-1, arch all) ...
N: ----
N: Processing binary package influxdb (version <IP_ADDRESS>+dfsg1-1, arch amd64) ...
I: influxdb: spelling-error-in-binary usr/bin/influxd unkown unknown
N: ----
N: Processing binary package influxdb-dev (version <IP_ADDRESS>+dfsg1-1, arch all) ...
N: ----
N: Processing binary package influxdb-client (version <IP_ADDRESS>+dfsg1-1, arch amd64) ...
N: 2 tags overridden (2 warnings)

Thanks @aviau
Cosmetic change only, merging now.


File preparation speedup

Just a note to say we have parallelized the file preparation (which takes the longest by far) from the current serial approach.
We use SLURM sbatch concurrently and a wait mechanism to wait for all jobs to complete.
raspir itself is still run in serial, but doesn't take long.
Code:
https://github.com/MHH-RCUG/Wochenende/blob/master/raspir/run_SLURM_file_prep.sh
and in wochenende_postprocess
https://github.com/MHH-RCUG/Wochenende/blob/177b99fda6abcaafe9a744c80f7b4efc92105ef1/wochenende_postprocess.sh#L359
cheers

It looks great! Thank you for using and incorporating raspir into the Wochenende pipeline!


Error: Images not loading when using --livereload

Images are not shown because of file access restrictions when using livereload.

#161 resolves this issue.

Closed with #161


[ASTMangler] Add support for mangling generic typealiases.

rdar://problem/39915946
Conflicts:
test/Demangle/Inputs/manglings.txt

@swift-ci please nominate
Explanation: Lack of mangling for generic typealiases causes a crash in the debugger when trying to reconstruct them.
Scope: The mangling is mainly for DWARF, so, presumably, only -g is affected.
Radar (and possibly SR Issue): rdar://problem/39915946
Risk: Relatively-low. We lived with a broken mangling for generic typealiases for a while, but only recently we started crashing. I'm really not familiar with the mangling code, so somebody more familiar than me might consider looking at this change more carefully and make a call.
Testing: Testing has been done in CI and locally

@swift-ci please test


Emit an automatic event when the browser is hitting an unknown tag or style (suggestion)

One of the biggest pains with creating HTML5 applications is that the standard is not completely finalized and hence some of the tags and styles are not always supported on all browsers. Can the AI SDK emit an automatic event when the browser is hitting an unknown tag or style? It would be interesting for a developer to know how many users are getting a sub-optimal experience due to this common problem.

I've removed the enhancement tag and I'm going to mark as stale as I think this would probably be better as a (v2) "add-on" which would either be injected with an appInsights instance or would look for the global.
Either way, based on the age and backlog items I don't believe that we will get to this at any time soon (if ever -- TBH)


KAFKA-9748: Extend Streams integration tests for EOS beta

The original PR was only considering EosIntegrationTest. However, there are actually a few more integration test with eos-alpha enabled that we missed to update.
Call for review @abbccdda @guozhangwang

Both Jenkins runs passed. Magic!

Build failed with
23:01:46 [ant:checkstyle] [ERROR] /home/jenkins/jenkins-slave/workspace/kafka-pr-jdk11-scala2.13@2/clients/src/main/java/org/apache/kafka/clients/consumer/internals/ConsumerCoordinator.java:332:5: NPath Complexity is 588 (max allowed is 500). [NPathComplexity]

Seems to be fixed via #8447
Can retest after more reviews.

Retest this please.

Java 8 passed.
Java 11: kafka.api.ConsumerBounceTest.testRollingBrokerRestartsWithSmallerMaxGroupSizeConfigDisruptsBigGroup
Retest this please.

Java 8 passed.
Java 11: kafka.api.SaslGssapiSslEndToEndAuthorizationTest.testNoDescribeProduceOrConsumeWithoutTopicDescribeAcl
Different test as before. Also run the tests locally multiple times without issues. Merging this.


Added functionality to change the syslog server's ip address at runtime

One of 388526's acceptance criteria was to set the syslog network backend's IP address at runtime. This is the PR that accomplishes that task as it wasn't already supported in Zephyr. What was supported is the ability to set the IP address at compile time through CONFIG_LOG_BACKEND_NET_SERVER.
I'm submitting a PR here as I intend to also submit that PR upstream and I'd like another level of review as this will be my first submission to the Zephyr Project.

Looks good to me, although you should probably leave out the comment fix in the BLE backend.
Suggestion: Add log backend net shell command to set the IP address.

Oops missed that one. I'm not used to seeing requests here.
I think I will hold off on that one. Although it is a very good idea.


How work blazor on iOS version 9?

iOS11+  It's work.
iOS10+ and  Blazor.Polyfill.js   It's work.
iOS9 Is't not work.

Apple should have fixed the safari issue that is blocking ios 11 in the upcoming version 12 (hopefully). Accordingly to “can I use” webassembly support in ios is present starting with version 10.3 https://caniuse.com/#feat=wasm

@ghidello thanks.

@ghidello Thanks for answering!
@treenew As we get farther along with the Blazor project we'll publish clearer statement on exactly which browser versions are supported. Right now we're focused on getting basic functionality working.


use go.{mod} instead of Gopkg.{toml,lock}

Now go modules have been widely used in lots of projects. Also the kubebuilder has used go modules in its project repo and also used go modules in its generated codes. So I recommend change dep into go modules both in this project and the generated codes.
By using go modules, the vendor.tar.gz may be no need to be packaged into the release tar.gz since go modules supports a go mod vendor to generate vendor dir.

yeah, tho am a bit surprised kubebuilder has completed migrated to gomod instead of keep them in parallel for several releases. this repo will always be following up actions of kubebuilder so i see the ponit valid to me. will consider this at 1.17.x releases. and btw this requires this repo to follow semver taggings which is a prerequisite action item

I think that following semver taggings is valid. I guess the current version v1.16.alpha.0 means that it may match kubernetes-1.16.0. This version match may be unnecessary, for we can get kubernetes version in scripts/print-workspace-status.sh or using a better way.

I guess the current version v1.16.alpha.0 means that it may match kubernetes-1.16.0.

the major and minor bits will be following the kubernetes' version while the patch version doesnt have to align. it will increment per releases starting from 0.
i will file a new release this week or next. that makes it v1.16.alpha.1

hey guys,
I saw there are a couple of PRs related to supporting go modules in this project.
@yue9944882 when do you expect to release this functionality?

@VitaliyShevchenko moving completely to go mod is planned in the very next release i.e. v1.17.0. but this will make bring some break changes to the command-line toolings. e.g. the //+go:generate go run ./vendor/.../ annotations wont work any more. additionally the lastest release v.1.16.2 is already supporting go mod in a way.

Great! It is nice to read that.
@yue9944882 if you need some help, you can ping me :)


Develop UI concept for auto-completion of backup phrase

When the user restores their seed phrase from backup (paper or photo):

they have to type the seed back into the app. The word choices are limited to a standard set of 2048 words, which can be in any language.
When user types the words, it would be very helpful to have an auto-complete taken from the choice of 2048 words, for example the user types 'vo' and they have this list of choices:
vocal
voice
void
volcano
volume
vote
voyage
then they type 'l' and they have:
volcano
volume
until usually they'll get their word within 3 or 4 characters.
This is all very well for English however for Chinese we have a list of 2048 single characters eg:
同
工
也
能
It's not clear to how auto complete would work; perhaps use pinyin and give a choice based on the pinyin which narrows the more of the word they type until there's only a small number of characters.
For Spanish it's also not straightforward as Spanish has accented characters:
bambú
banco
banda
baño
The goal is to make it as painless as possible for the user to type their seed back in.


[Crosswalk-14][usecase] Add test for upgradelib

Add upgrade test
Update test description for DownloadUsage/res/downloadsimul

Impacted TCs num(approved): New 1, Update 0, Delete 0
Unit test Platform: Android
Android test result summary: Pass 1, Fail 0, Block 0

LGTM


Try adding "--replay-blockchain --hard-replay-blockchain".
If it still does not work and you are working on your own test environment use --delete-all-blocks.

Would you provide your log when --hard-replay not work?

use --replay-blockchain --hard-replay-blockchain in product env
2018-09-13T04:33:34.699 thread-0   chain_plugin.cpp:317          plugin_initialize    ] initializing chain plugin
2018-09-13T04:33:34.699 thread-0   chain_plugin.cpp:462          plugin_initialize    ] Hard replay requested: deleting state database
2018-09-13T04:33:34.699 thread-0   block_log.cpp:325             repair_log           ] Recovering Block Log...
2018-09-13T04:33:34.700 thread-0   block_log.cpp:345             repair_log           ] Moved existing blocks directory to backup location: '/mnt/dev/data/blocks-2018-09-13T04:33:34.699'
2018-09-13T04:33:34.700 thread-0   block_log.cpp:350             repair_log           ] Reconstructing '/mnt/dev/data/blocks/blocks.log' from backed up block log
2018-09-13T04:39:37.745 thread-0   block_log.cpp:460             repair_log           ] Existing block log was undamaged. Recovered all irreversible blocks up to block number 10885144.
2018-09-13T04:39:37.952 thread-0   chain_plugin.cpp:472          plugin_initialize    ] Reversible blocks database was not corrupted. Copying from backup to blocks directory.
2018-09-13T04:39:40.349 thread-0   chain_plugin.cpp:632          plugin_initialize    ] 3110006 plugin_config_exception: Incorrect plugin configuration
Genesis state can only be set on a fresh blockchain.
    {}
    thread-0  chain_plugin.cpp:522 plugin_initialize
2018-09-13T04:39:40.349 thread-0   main.cpp:125                  main                 ] 3110006 plugin_config_exception: Incorrect plugin configuration
Genesis state can only be set on a fresh blockchain.
    {}
    thread-0  chain_plugin.cpp:522 plugin_initialize
rethrow
    {}
    thread-0  chain_plugin.cpp:632 plugin_initialize

So on the line, the environment must never stop.

@helperShang And do not use the --genesis-json argument after a chain has been established.  It is only used once, when synchronization first begins.

Answered by @jgiszczak. I'm closing this issue.
If you still have the problem and wish to discuss further, please post it in https://eosio.stackexchange.com. To keep things organized, Github issues are intended for bugs reporting and features tracking, and Stack Exchange is the right place for any technical support discussions. Thanks!


Select with external button

Hi,
Is there a way to add an extra button to the bottom of the dropdown? Also disable/cancel somehow the selection of the dropdown item by clicking on it? I would like to use the external button to accept my selection.
Thanks

Could you please comment if you still need this feature? This is something that is implementable but a lot of work. If you haven't responded in 2 weeks, I'll close this issue

Hi,
It would nice if this extra button could call a custom function, for example to update the "options" attribute and show more items updating this array/object.


159447316 delete entry

What does this PR do?
This PR implements the delete functionality in the front-end of the diary app
Description of Task to be completed?
As a user, once I am logged in, I should be able to delete an entry
How should this be manually tested?
This method can be tested on the frontend by a logged in user
What are the relevant pivotal tracker stories?
#159447316

Pull Request Test Coverage Report for Build 28

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 90.732%

Totals

Change from base Build 26:
0.0%

Covered Lines:
186

Relevant Lines:
205

💛  - Coveralls


Created modal tutorial for react

@munsterlander Thanks! Looks like we forgot to make this one :sweat_smile:
I made some modifications to the modal, it now uses renderModal prop.

No problem.  As you know, react is not my forte, so I just copied the popover and modified it.  It worked so that was my first react project! :)


Add vscode-json-languageserver-bin node package

Motivation for this change
Make the JSON language server available
Things done
Added vscode-json-languageserver-bin to node-packages

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

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

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] 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)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

Needs a rebase. It'd make sense for this change to be in two commits; one for node-packages.json and one for regenerating the package set. The latter isn't just about adding this package, but updates everything iirc.

@roberth Done

Thank you!

[x] reproduced the generated file
[x] built the package.


Run code in else block if ruby tag is standalone

This fixes the bug described in this issue https://github.com/nebulab/erb-formatter/issues/51 opened by @AliOsm
The problem is that some tags are standalone, with no body or end tags
Like yield and next statements
This PR runs the same code written in the else block of the switch statement if the tags are standalone

@elia

@IbraheemTuffaha thanks for fixing this!
I added some fixtures to avoid regressions.


Make reporting consistent for all geo operations

Now operations using ogr versus gpd have a slightly different way of reporting progress...

sometimes more than 60 seconds in the reporting?


Allow search based on annotation color

This is a duplicate of informatics-isi-edu/rbk-project#146


Add pagination to index function at controller by default.

You can use /users and /users?page=1&offset=12 or /users?page=none&limit=5&skip=5

Add pagination to index function at controller by default.
You can use /users and /users?page=1&offset=12 or /users?page=none&limit=5&skip=5

@bsaqqa Please resolve conflict.

Closing due to major refactoring conflict. Also, I think we already support limit and offset parameters. Please put a PR again with latest templates with more description.


Workaround for RH 7 variants

Small workaround to fix the module running on RH 7 variants, detailed in issue 27
Provide a new custom fact that will only execute on RH 7 variants with SELinux enabled, and use that to determine the policy in module.pp if the default selinux_config_policy fact is not either 'targeted' or 'strict'.

Is it possible to merge this pull request? ;-)

@crashcover Sure! There you go!


Yii2 extension repository

Continued from http://www.yiiframework.com/forum/index.php/topic/39669-composer-support/
@qiangxue @samdark @cebe What are your plans regarding http://www.yiiframework.com/extensions/ for Yii2?
Theoretically this could be done via the Packagist API, just by filtering type=yii2-extension but there are some limitations at the moment (eg. limited search, fuzzy matching), which would have to be solved on the packagist side.
Or will you maintain a copy of this data or your even own data?

its unclear to me what needs to be done here. If this still is an important issue or feature request, please open a new ticket with a proper description.

It will be part of https://github.com/yiisoft-contrib/yiiframework.com/ so could be tracked there.


Is it possible to make 2 rows layout with a shift?

Hi!
I would like to make this layout http://take.ms/vPEp0
to be shifted like this http://take.ms/E3wci
is it possible to achieve with swiper settings or I should write a custom css for this?
Link to reproduce:
https://github.com/surmon-china/vue-awesome-swiper/blob/master/examples/17-slides-per-column.vue
Actual result:
columns are not shifted http://take.ms/vPEp0
Expected result:
second row is shifted horizontally by a half image http://take.ms/E3wci

you can try to modify its CSS. Inspect it and overide it.


~ tilde operator not working as expected (and as it did before)

🐞 Bug report
Command (mark with an x)

- [ ] new
- [ ] build
- [x] serve
- [ ] test
- [ ] e2e
- [ ] generate
- [ ] add
- [ ] update
- [ ] lint
- [ ] xi18n
- [ ] run
- [ ] config
- [ ] help
- [ ] version
- [ ] doc

Is this a regression?

 Yes, the previous version in which this bug was not present was: ....
Yes. This used to work in cli 1.7.4
Description
 A clear and concise description of the problem...
In my SCSS files I have something like this:
@import "~scss/some-style";
This code used to look for styles starting from the src folder and worked just fine.
Now I found out that I can use something like this
@import "~src/scss/some-style";
But although my IDE sees the correct path, when I run ng serve I get an error and the compile fails.
🔬 Minimal Reproduction

To reproduce just put the following line in any component's scss:
@import "~scss/some-style";
Be sure that some-style.scss exists under the src/scss folder
🔥 Exception or Error

Module build failed (from ./node_modules/sass-loader/lib/loader.js):

@import "~src/scss/some-style";

🌍 Your Environment

Angular CLI: 7.2.2
Node: 10.14.2
OS: win32 x64
Angular: 7.2.2
... animations, cli, common, compiler, compiler-cli, core, forms
... language-service, platform-browser, platform-browser-dynamic
... router

Package                           Version
-----------------------------------------------------------
@angular-devkit/architect         0.12.4
@angular-devkit/build-angular     0.12.4
@angular-devkit/build-optimizer   0.12.4
@angular-devkit/build-webpack     0.12.4
@angular-devkit/core              7.2.4
@angular-devkit/schematics        7.2.2
@angular/cdk                      7.3.7
@angular/flex-layout              7.0.0-beta.19
@angular/material                 7.3.7
@ngtools/json-schema              1.1.0
@ngtools/webpack                  7.2.4
@schematics/angular               7.2.2
@schematics/update                0.12.2
ng-packagr                        4.7.1
rxjs                              6.5.1
typescript                        3.2.2
webpack                           4.28.4

Anything else relevant?

I'm using sass-loader v 7.1.0
may be this lines relevant?
in sass-loader/lib/importsToResolve:

function importsToResolve(url) {
    const request = utils.urlToRequest(url);
    ...

in loader-utils/lib/urlToRequest.js

function urlToRequest(url, root) {
    ...
    if(root !== undefined && root !== false && /^\//.test(url)) {
    ....

If root was passed

I just noticed that in my angular.json I have

    "my-project": {
      "root": "",
      ...
    }

If I change root value to src
I can use in my scss files ~scss/some-style as I did before...

I think I might have solved the issue and now both the IDE and the cli work as expected.
Just not sure if everything's correct:
angular.json:

...
"root": "src",
"sourceRoot": "src",
....

tsconfig.json and src/tsconfig.app.json

...
"compilerOptions": {
    "baseUrl": "",
      ...
}
....

Hi @tonysamperi, thanks for reaching out.
The problem with the above is that sourceRoot is not part of the listed modules entries
https://github.com/angular/angular-cli/blob/master/packages/angular_devkit/build_angular/src/angular-cli-files/models/webpack-configs/common.ts#L331
That being said, I would strongly advice against using ~ especially for local imports, as this is quite a Webpack specific feature and it's not guaranteed that this behaviour will continue to work in the future, there are 2 options which are natively available in sass compiler that one should prefer.

Relative paths
Include paths

@clydin, can you chime in if we should address the above?

Hi @alan-agius4 thanks for your reply.
I guess the best option is the stylePreprocessorOptions (as you say, include paths).
I'm too lazy!!! :)
Luckily I only have one folder I use this way!
Should I close this issue?


predicting bulk RNA-seq

Hi,
I have trained scaden on a .h5ad file I produced.
I am looking to run scaden predict on bulk RNA-seq data if possible.
Could you tell me what format the bulk RNA-seq data would need to be in?
Regards
Jon8991

Hi Jon,
sure, please also have a look at the documentation:
https://scaden.readthedocs.io/en/latest/usage/
If you look under 'Usage' and scroll down to file formats, you can find an explanation.
Basically what you need is a tab-separated file with genes as rows and samples as columns.
The expression values should not be on a logarithmic scale.
You can leave the column name for the first row, so your gene names, free - just put a tab in there.
So something like this:
sample1 sample2 sample 4
gene1      234        34             333
gene1         1            3               3
gene3
Let me know if you get any other issues.
Cheers,
Kevin

Brilliant.
That helps a great deal. :)
Thank you for the quick reply
Have a good day
Jon8991


Snapshots during retries cause errors

The problem
playwright supports retries but when a snapshot is taken in a retry, we get an error:

Error: The name of each snapshot must be unique, and this name already exists in the build: 'foo' -- You can fix this by passing a 'name' param when creating the snapshot. See the docs for more info on identifying snapshots for your specific client: https://percy.io/docs

Environment

Node version:
@percy/cli version: 1.0.0-beta.70
Version of Percy SDK you’re using: percy/playwright 1.0.1
If needed, a build or snapshot ID: n/a
OS version: n/a
Type of shell command-line [interface]: n/a

Details
It looks like there is work that was merged into core related to this but I don't think the sdk supports using this functionality?
Other related discussions:

https://github.com/percy/cli/issues/281
https://github.com/meinaart/cypress-plugin-snapshots/pull/141

Code to reproduce issue
in playwright.config add retries: 2
in a test.spec.ts:
test('foo', async (page) => {
  snapshot(page, 'foo')
 throw new Error('run retry')
})

@JackCA I think you should consider creating a separate visual testing profile with retries disabled. I've been doing visual testing for 3 years and now create multiple e2e profiles: one for CI and one for Visual Tests

@JackCA I think you should consider creating a separate visual testing profile with retries disabled. I've been doing visual testing for 3 years and now create multiple e2e profiles: one for CI and one for Visual Tests

Definitely agree with you there -- I'm doing my best to prevent even needing retries. However, I still think this would be a valuable feature and think the opportunity is there because of the upstream changes made to core.

Hey @JackCA! Going to close this out since the CLI ticket you linked to is the right place to track it. We'll be shipping retry support after 1.x in early 2022.

great, thanks @Robdel12


Feature suggestion: model and dataset versioning with HuggingFace

Hi dear Brain-Score Team!
While thinking on my own experiments, reading papers and talking to people, I can’t get rid of a feeling that we (as a field) assume that we understand ML methods better than we actually do.
I mostly speak about not controlling for many of the lower-level ML specifics that could contribute largely to the differences in final performance: interactions between optimizers, batch sizes, different subsets of the same dataset, operation precisions, hyper-parameters specific to architectures, and so on. These are not well understood by the ML community itself, and many of the choices are left as heuristics. Reproducibility is a known issue in modern ML.
I think BrainScore is in a position to bring neuroscientist the best practices from CS community and thus accelerate the progress through reproducibility and unification of tools.
One step towards this would be to manage model and dataset versioning with something like huggingface for example.

We will be able to extend the model cards that we provide now (which answer very little questions about what the model actually is) with a link to HF repo with exact weights and hyper-parameters.
The same thing is possible for datasets and their subsets
Since interactions with HF are standard and well integrated with many libraries, this would also make life easier for those, who want to take the best model from BrainScore and use it in further applications.

This way we not only (1) solve reproducibility and clarity of results but also (2) collect a lot of additional (meta)data that we could later analyze to find/build best alignment models and (3) allow users to do a search for models with their preferred settings.

Hi @narekvslife - thanks for opening an issue and this is a great suggestion. We have talked previously in the past with linking models directly to our Github (for our "Brain Models", like CORnet-S for example), and HF for "Base Models", i.e. standard models like resnet-50 or MobileNets. We hope to add this soon as part of a refactoring of the way we are storing models.


test: fix path separator

Replace this paragraph with a description of your changes and rationale. Provide links to external references/discussions if appropriate.

Resolves SR-NNNN.

CC: @davidungar

@swift-ci please smoke test

@swift-ci please smoke test Windows platform

@swift-ci please test Windows platform

@swift-ci please smoke test Linux platform


SwiftCoAP + LWM2M?

Hi Stuffrabbit,
I like your CoAP implementation of Swift and it seems to work fine when trying out your CoAP server implementation together with this CoAP client in the Firefox webbrowser:
https://addons.mozilla.org/en-US/firefox/addon/oma-lwm2m-devkit/
Now my questioN:

Have you made any integrations with LWM2M with your CoAP library?

LWM2M implementations:
https://github.com/eclipse/wakaama (Implemented in C)
https://github.com/FlowM2M/AwaLWM2M (Implemented in C)
https://github.com/eclipse/leshan (Implemented in Java)
according to:
https://en.wikipedia.org/wiki/OMA_LWM2M
Maybe you've built wakamaa as a iOS-library (so its still C code), but with integration to SwiftCoAP?

and/or maybe you have started to port some parts of Wakamaa or Leshan to Swift? I.e some of the client or server LWM2M-parts?

Hi Stuffrabbit,
you had very quick answers on my other 2 questions, do you have an answer on this question too?

Hey mlindstedt,
sorry for the late answer. To be short: No have not implemented any LWM2M integrations till now. Maybe you can start a fork? :)

Hi stuffrabbit,
I actually started on a LWM2M integration, for REGISTER / DEREGISTER and they worked fine. However when I implemented READ, then I ran into severe problems in SwiftCoap-code and I was doing lot of debugging in your code to try to find problem, the bits and bytes on Coap-level doesn't seem to be sent correctly. After several days of debugging, and not being able to make it work, I unfortunately had to abandon, and instead decided to go with Wakamaa implementation:
https://github.com/eclipse/wakaama
Even though Wakamaa is written in C, I managed to integrate the library into my Swift app.
Afterwards it has come to my attention that Firefox web browser:
https://addons.mozilla.org/en-US/firefox/addon/oma-lwm2m-devkit/
used PUT and not POST for LWM2M READ and that might be the reason why it didn't work..

Hi mlindstedt,
good to hear that you were able to find a solution for your problem. So you mean that there is a bug inside the CoAP-message parsing of SwiftCoAP? Or what were these severe problems about?

It seems to me that there is a bug, but I only put in 4 debug working days, before I gave up. Like I said, when I implemented LWM2M register and deregister on top of SwiftCoap in my iOS app, then SwiftCoap worked fine, but when I implemented LWM2M read or execute, then SwiftCoap didn't make other side trigger on what it sent, so either the problem was in SwiftCoap or in the other end (LWM2M client).
In my case I used Firefox web browser with a plugin, to use it as LWM2M client, whilst the iOS app with SwiftCoap was LWM2M server.
However, later on it turned out, that Firefox plugin was not correctly implemented, it followed old LWM2M standard which made it use PUT and not POST for LWM2M read, which might be reason why it didn't work.
But, I also tried Wakamaa as LWM2M client towards my iOS app and it had same problem, so my suggestion is that you try to implement some parts of the upper layer, i.e LWM2M on top of SwiftCoap, to see if you can make it work. REGISTER and READ should be enough for you to see if you can get same problem.


Add Blazor topics

Fixes #10825
Internal Review Topics:

Blazor Overview
Blazor: Get started
Razor Components Overview
Razor Components: Get started
Build your first app

Notes:

Can't name both RC and Blazor samps with the same name, so I went with "Razor Components" and "Blazor" as the app names ... super-obvious that way when readers look in the tutorial's samples folder.
Still needs work on the intro paragraphs of each of the introduction (Overview/index.md) topics. Blazor intro needs the list of main features. If you need to make big layout changes, I recommend that you edit these directly here, then I'll do a style+grammar pass afterward.
Made sense to jettison the "hosting models" sections now that these intro topics are entirely dedicated to either RC or Blazor. I retain a brief remark at the end of each about the converse approach (RC mentions Blazor and Blazor mentions RC) with a cross-link.
Dan, your recommendations worked well. I 🖖 u on those calls.

@tdykstra You can make it a quickie look (I'd like to merge and get right back into these topics with an updated master) ... we'll be back here for Preview 3 making a final pass. I'm mostly concerned about your approval of the TOC bits.
@scottaddie We'll have time for u to :eye: it for Preview 3 ..... you should be dug out ⛄ by then I hope.

@tdykstra These TOC updates sound fine to me, although I would prefer to have Razor Components in first position, and then SPA second under client-side dev.

A bunch of TOC nodes under Razor Components 404 -- is that expected at this point?

I'm not getting that here. No RC topics 404 here. Which ones are 404'ing there?

delete Overview under Single Page Apps (it 404s)

It loads here as https://docs.microsoft.com/aspnet/core/client-side/spa/
I'll work a commit along the suggestions provided.

@tdykstra @danroth27

Pointed the Client-side Overview to the Razor Components Overview. You said Blazor, but RC is the supported tech at this point. Blazor is the first link tho under SPA. I perhaps guessed wrong, so let me know.
Moved RC to the top of the node.
Moved LibMan under RC.

No RC topics 404 here. Which ones are 404'ing there?

They're working now.

It loads here as https://docs.microsoft.com/aspnet/core/client-side/spa/

That one works now too.  It's one of those duplicate-the-toc files, how about delete and redirect to Blazor since we don't have a real SPA overview?

@tdykstra Done on the last commit ... see how that looks.

... but I only deleted. If you still want "Overview" but linked to the Blazor Overview, I still need to do that.

Feel free to edit directly, of course for what you want.

OK, editing TOC now, a couple of tweaks.  Also, the /aspnet/core/client-side/spa/index shows the page now but is disconnected from the TOC.  Need to redirect the URL to Blazor

Yes, :+1: redirect entry. Let me know if u want me to add that or if you're going to do it.

@tdykstra Try that redirect ... see if that looks good. :point_up:

Thanks! -- if the TOC changes build OK I think we're good.

Looks like we need a client-side/index redirect, too. I'll add that next.

That might† work.
†might ... if the :pray: server gods :pray: are happy with us.

@tdykstra Look at it this way .......
...... if this all goes to heck in a handbasket ........
I hear Apple docs ARE HIRING! 😀😀😀😀🙈:smile:
@danroth27 ... look good to you? ... I'll get this merged and on to the Blazor TOC/INCLUDE updates next.

It wasn't too pleased with the file left on the repo, so I 🔪 the file on the last commit.

I agree that LibMan should appear in the ToC before Gulp and Grunt. We do own that product, after all.

:shipit:


update and add new github templates

👍

Coverage remained the same at 89.796% when pulling cbb1428390097e4a73b44826252fbb2a74892f8b on 130-update-github-templates into e3f2a65714f200421dc21051236be8907bdb0239 on master.

Coverage remained the same at 89.796% when pulling e5584a603a55fa34c788c0389a5d701d83366494 on 130-update-github-templates into e3f2a65714f200421dc21051236be8907bdb0239 on master.

:+1:


Add zensummoning documentation

This is mostly autogenerated, and I'm not sure what else needs to be added for sidebar and i18n support.

For the examples, can you just add a little "The following script will do: <explain what it does", just so people know what they are looking at.
Otherwise it looks great!


GetRouteDirections failing due to coordinates being formated with commas in certain cultures

The truck does not correctly process commands to go to specific customer due to culture-specfic formatting of the coordinates. GetRouteDirections returns an error message:
The provided coordinates in query are invalid, out of range, or not in the expected format
Current code - depends on CurrentCulture - coordinates are incorrectly formatted as numbers with comma (,) as decimal separator
var req = new RouteRequestDirections
    {
        Query = $"{currentLat},{currentLon}:{destinationLat},{destinationLon}"
    };

Corrected code - depends on InvariantCulture - coordinates are formatted as numbers with dot (.) as decimal separator
var req = new RouteRequestDirections
    {
        Query = FormattableString.Invariant($"{currentLat},{currentLon}:{destinationLat},{destinationLon}")
    };

Same here. Thanks for the hint!
@PeterTurcan PR #2 from @darenm will resolve this issue.
Can you may review and merge it?


Broken url link: coreos clair document page 404

README.md
Documentation
The latest stable documentation can be found on the CoreOS website. Documentation for the current branch can be found inside the Documentation directory at the root of the project's source code.
returns 404

Thanks, I believe the correct address is; https://tectonic.com/quay-enterprise/docs/latest/clair.html

This link will be fixed the next time that CoreOS.com synchronizes its documentation with the Clair repository. Until then, use the link posted by @alekssaul

This is no longer broken.


[YUNIKORN-216] Fixed helm chart link in deployment doc

The UT failure was because a race: https://issues.apache.org/jira/browse/YUNIKORN-221. The doc fix looks good.


Added removeAllWidgets method

Simply adds a method called removeAllWidgets that allows clearing all the Widgets that are stored inside a layout.

@nihal111 / @SkySom: Be careful with changes like these, specifically adding new non-default methods to interfaces covered by @API - they are technically API violations requiring a new major engine release :-)
In this case I found that it broke the EventualSkills module, which had a related UI class without the new method. Unsure if it might be in use elsewhere so I submitted #3063 as a general fix. I'm liking the utility of default methods although I fear I am growing to enjoy a dangerous tool ... :D


Add property to run energy consumers at the best time

Implementation suggestion for #54.  This would need to be paired with a PR to HomeAssistant to expose the new property as a sensor.

@klaasnicolaas shall I go ahead and add tests, or did you have a different direction in mind here?

Have one last request, your new data feature is still missing in the readme. Could you add to the listed list in chapter data?

Codecov Report
Patch coverage: 100.00% and no project coverage change.

Comparison is base (92ff863) 100.00% compared to head (b75f718) 100.00%.

Additional details and impacted files
@@            Coverage Diff            @@
##              main       #55   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files            5         5
  Lines          199       207    +8
  Branches        18        20    +2
=========================================
+ Hits           199       207    +8

Impacted Files
Coverage Δ

easyenergy/models.py
100.00% <100.00%> (ø)

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Any Questions? slide of intro wizard is incomplete

We should add a link to our marketing site, our names, link to the repo, and any other information we think would make sense to be displayed here.

@diegonetto Are you talking about hybridcollective.org ?  Is that the name we should register ?  Any body else have any thoughts on this ?
I think Troy reserved trendicity.com.

Troy reserved trendicity.io  I think this should be used for the marketing url for the app itself.

Closed by 20bfc3aae2cd8afd44015d1bf83cbbae397d8c1d

Thanks, it is actually trendicity.co.
We will get that going.
--Troy

Troy reserved trendicity.io I think this should be used for the
marketing url for the app itself.
—
Reply to this email directly or view it on GitHub
https://github.com/trendicity/trendicity/issues/58#issuecomment-74447529.


Please make a release

It would be great being able to download a recent version from PyPI. 🥇

I do not currently have this ability. I am aware that people like libraries to release new versions when there are new features. If I am ever able to, I will make a new release.

@davidism If @crast and @prencher are not available to grant you PyPI maintainer privileges, I'm thinking it might be an idea to open an "abandoned"-ticket with the Package Index? https://www.python.org/dev/peps/pep-0541/#continued-maintenance-of-an-abandoned-project
In the meanwhile, I uploaded my fork with a ...
pip install twine && twine upload

It's located here: https://pypi.python.org/pypi/WTForms-fork-20180213/3.0.dev0
If you disagree with this, feel free removing it. And if I can help somehow, I'm happy to assist. I love this project! 💝

I can't remove forks, but please, please don't do that. People can already install from master through GitHub, and unless you're planning to keep that up to date and properly notify users, they will never get updates if any happen.
@lepture and I are talking about something, but I have other projects to focus on in the immediate future.
It doesn't matter if I get control of RTD and PyPI, I have no permissions for the org on GitHub, so have no control over most of the infrastructure being used.

I now have access.

Fwiw, wtforms just got removed from Debian testing (buster) because of this bug, along with everything that depends on it.
I uploaded a patched version now, but this should really be fixed upstream.


Upgrade: go-bt to v2 (when stable)

If there are breaking changes, create a v1/v2 of go-bitcoin.
If there are zero breaking changes, create a new major version.
https://github.com/libsv/go-bt/releases

This is almost complete by @icellan


implement CLGs for connection CRUD operations

This issue should be addressed before https://github.com/xh3b4sd/anna/issues/238.

[ ] 1. Add a new connection between two given peers.
[ ] 2. Get all peers that are connected with a given peer.
[ ] 3. Update the score of a connection of two given peers.
[ ] 4. Remove a connection between two given peers.
[ ] 5. Document more about the ideas and concepts of the connection space. See the example below.

Each peer within the connection space is a label. That means that peers are labeled by their connections. The location of peers within the connection space is represented by coordinates. Coordinates are peers within the connection space itself. Thus, a coordinate that represents the location of a peer, labels this specific peer, by being connected to it. This results in a coordinate network which can be seen as separate dimension within the connection space. This dimension reflects the semantic connections within the connection space exactly one to one, because each connection has a coordinate attached to it.


HBASE-28860 Add a metric of the amount of data written to WAL to determine the pressure of replication

Add a metric of the amount of data written to WAL to determine the pressure of replication.
Combined with the replication shipped size metric, the user can determine how many RegionServers are needed to meet the data(WAL) writing requirements, that is to achieve the goal of no replication lag.
In the postAppend method of ReplicationSourceWALActionListener, the amount of WAL data that needs to be replicated is counted, and the filter logic in replication is reused.
Alos add a hbase.replication.walAppendsize.metric.enable=false config to disable this metric, if it has some side effect.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 28s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  0s

codespell was not available.

+0 :ok:
detsecrets
0m  0s

detect-secrets was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

+1 :green_heart:
hbaseanti
0m  0s

Patch does not have any anti-patterns.

_ master Compile Tests _

+0 :ok:
mvndep
0m 11s

Maven dependency ordering for branch

+1 :green_heart:
mvninstall
3m 16s

master passed

+1 :green_heart:
compile
4m  9s

master passed

+1 :green_heart:
checkstyle
0m 59s

master passed

+1 :green_heart:
spotbugs
2m 29s

master passed

+1 :green_heart:
spotless
0m 47s

branch has no errors when running spotless:check.

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 11s

Maven dependency ordering for patch

+1 :green_heart:
mvninstall
3m 14s

the patch passed

+1 :green_heart:
compile
4m  6s

the patch passed

+1 :green_heart:
javac
4m  6s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
checkstyle
0m 58s

the patch passed

+1 :green_heart:
spotbugs
2m 50s

the patch passed

+1 :green_heart:
hadoopcheck
11m 46s

Patch does not cause any errors with Hadoop 3.3.6 3.4.0.

+1 :green_heart:
spotless
0m 45s

patch has no errors when running spotless:check.

_ Other Tests _

+1 :green_heart:
asflicense
0m 26s

The patch does not generate ASF License warnings.

44m 16s

Subsystem
Report/Notes

Docker
ClientAPI=1.43 ServerAPI=1.43 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6260/1/artifact/yetus-general-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/6260

Optional Tests
dupname asflicense javac spotbugs checkstyle codespell detsecrets compile hadoopcheck hbaseanti spotless

uname
Linux 30d8b6c28edb 5.4.0-1103-aws #111~18.04.1-Ubuntu SMP Tue May 23 20:04:10 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / 1efb868d740c874d071b97c1b14470f391f7d6e8

Default Java
Eclipse Adoptium-17.0.11+9

Max. process+thread count
84 (vs. ulimit of 30000)

modules
C: hbase-common hbase-hadoop-compat hbase-server U: .

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 12s

Maven dependency ordering for patch

+1 :green_heart:
mvninstall
3m  6s

the patch passed

+1 :green_heart:
compile
1m 37s

the patch passed

+1 :green_heart:
javac
1m 37s

the patch passed

+1 :green_heart:
javadoc
1m  4s

the patch passed

+1 :green_heart:
shadedjars
5m 23s

patch has no errors when building our shaded downstream artifacts.

_ Other Tests _

+1 :green_heart:
unit
2m 20s

hbase-common in the patch passed.

+1 :green_heart:
unit
0m 46s

hbase-hadoop-compat in the patch passed.

-1 :x:
unit
256m 13s
/patch-unit-hbase-server.txt
hbase-server in the patch failed.

289m 22s

Subsystem
Report/Notes

Docker
ClientAPI=1.47 ServerAPI=1.47 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6260/1/artifact/yetus-jdk17-hadoop3-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/6260

Optional Tests
javac javadoc unit compile shadedjars

uname
Linux 4c1f093d9dbb 5.4.0-192-generic #212-Ubuntu SMP Fri Jul 5 09:47:39 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / 1efb868d740c874d071b97c1b14470f391f7d6e8

Default Java
Eclipse Adoptium-17.0.11+9

Test Results
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6260/1/testReport/

Max. process+thread count
4904 (vs. ulimit of 30000)

modules
C: hbase-common hbase-hadoop-compat hbase-server U: .

Console output
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6260/1/console

versions
git=2.34.1 maven=3.9.8

Powered by
Apache Yetus 0.15.0 https://yetus.apache.org

This message was automatically generated.


Make sensor groups inverter model aware

Make sensor groups inverter model aware. Some grid and battery sensor names differ between 1ph, 3ph and 3ph HV models.
Gets rid of annoying messages about missing sensors.
sunsynk-1  | 19:37:45 ERROR   Unknown sensor specified: aux_power
sunsynk-1  | 19:37:45 ERROR   Unknown sensor specified: essential_power
sunsynk-1  | 19:37:45 ERROR   Unknown sensor specified: grid_voltage
sunsynk-1  | 19:37:45 ERROR   Unknown sensor specified: inverter_current
sunsynk-1  | 19:37:45 ERROR   Unknown sensor specified: load_frequency
sunsynk-1  | 19:37:45 ERROR   Unknown sensor specified: non_essential_power

Thanks @rixxxx
I made some changes in 2db1d0d which should stop the warnings being issued if sensors in a group is not part of the current definitions. At also adds an "all" group.
Mayb you can extend the definitions further to include all the 3PH sensors?

Sure, I'll have a look.

Now I get:
sunsynk-1  | 17:00:14 ERROR   Your config includes deprecated sensors. Replace battery_current with battery_1_current
sunsynk-1  | 17:00:14 ERROR   Your config includes deprecated sensors. Replace battery_power with battery_1_power
sunsynk-1  | 17:00:14 ERROR   Your config includes deprecated sensors. Replace battery_soc with battery_1_soc
battery_current, battery_power and battery_soc get pulled in by power_flow_card. My intention with this PR was to load unnumbered battery sensors only for 1PH and 3PH LV.

https://github.com/kellerza/sunsynk/commit/b86cdf17d22197f23ddfb6ec2574004595b83857

:clap:


Invisible recaptcha - support

Please, add invisible recaptcha support

I really need your help.
I'm too busy with new project.
:-\

@anhtuank7c, Thanks for the answer, the other day I'm trying to achieve a work effect and publish

You can refer to this package: https://github.com/mosaxiv/cakephp-invisible-recaptcha
It can help you integrate invisible recaptcha to your projects more efficiently!

It's here :)
https://github.com/mosaxiv/cakephp-invisible-recaptcha

@mosaxiv Thank you.
I choosedReactJS, React Native, nodejs to work and abandoned PHP as well.
Thank for your help ;)


virtualenv: error: argument --creator: invalid choice: 'venv' (choose from 'builtin', 'cpython2-posix')

Issue description
pipenv check fails or actually everything fails; it does install the python version correctly however.
Expected result
it to work, obviously ;)
Actual result
/usr/local/py-utils/venvs/pipenv/lib/python3.11/site-packages/pipenv/vendor/attr/_make.py:876: RuntimeWarning: Running interpreter doesn't sufficiently support code object introspection.  Some features like bare super() or accessing __class__ will not work with slotted classes.
  set_closure_cell(cell, cls)
/usr/local/py-utils/venvs/pipenv/lib/python3.11/site-packages/pipenv/vendor/attr/_make.py:876: RuntimeWarning: Running interpreter doesn't sufficiently support code object introspection.  Some features like bare super() or accessing __class__ will not work with slotted classes.
  set_closure_cell(cell, cls)
/usr/local/py-utils/venvs/pipenv/lib/python3.11/site-packages/pipenv/vendor/attr/_make.py:876: RuntimeWarning: Running interpreter doesn't sufficiently support code object introspection.  Some features like bare super() or accessing __class__ will not work with slotted classes.
  set_closure_cell(cell, cls)
Creating a virtualenv for this project...
Pipfile: /workspaces/backend/Pipfile
Using /home/vscode/.pyenv/versions/2.7.18/bin/python2.7 (2.7.18) to create virtualenv...
⠙ Creating virtual environment...SystemExit: 2

✘ Failed creating virtual environment
[pipenv.exceptions.VirtualenvCreationException]: usage: virtualenv [--version] [--with-traceback] [-v | -q] [--read-only-app-data] [--app-data APP_DATA] [--reset-app-data] [--upgrade-embed-wheels] [--discovery {builtin}] [-p py] [--try-first-with py_exe]
                  [--creator {builtin,cpython2-posix}] [--seeder {app-data,pip}] [--no-seed] [--activators comma_sep_list]
virtualenv: error: argument --creator: invalid choice: 'venv' (choose from 'builtin', 'cpython2-posix')

Failed to create virtual environment.

When possible, provide the verbose output (--verbose), especially for locking and dependencies resolving issues.
Steps to replicate
Provide the steps to replicate (which usually at least includes the commands and the Pipfile).
Pipfile:
[[source]]
name = "pypi"
url = "https://pypi.org/simple"
verify_ssl = true

pipenv check already fails

https://pastebin.com/USh8htgX
due to size limitations here is the pipenv --support output

@f0o We don't have support for python 3.11 yet

That explains it; closing

@f0o Actually though I am wondering if this has nothing to do with 3.11 -- Did you by chance install virtualenv from apt?   If so, could you uninstall that and try installing it from pypi using pip?  https://stackoverflow.com/questions/70583980/i-am-unable-to-create-a-new-virtualenv-in-ubuntu

May I Bring this up again?
Having the same issue using 3.10.6.
removing virtualenv installed from apt made no difference.
pipx installations and bare pip installation behave the same.

Hi @matteius ! Thank your for the reply :)
Have installed 2022.11.1.dev0 from main branch but no luck, unfortunately
Error read as follows:

Haven't got an opportunity to check pipenv version on work PC which handles such cases without problems.

Works fine on 2022.6.7