Error signing into /admin (The redirect_uri MUST match the registered callback URL for this application.)

I followed the steps to install this repository under a netlify site.
This is what my Github OAuth Application's settings look like.

(The Authorization callback URL setting was filled automatically by GitHub, unfortunately appending /admin to that value doesn't causes the error to go away)
So basically I went to netlify and added the authentification provider.
Everything good so far.
Now, when hitting the /admin page of my site I see this beautiful big button...

And it opens a modal... But here an error appears.
This is the screen of the modal

Not only I did not sign in, I get the error that can be seen clearly in the URL of the opened pop-up:
https://jockey-stabilization-30351.netlify.com/?error=redirect_uri_mismatch&error_description=The+redirect_uri+MUST+match+the+registered+callback+URL+for+this+application.&error_uri=https%3A%2F%2Fdeveloper.github.com%2Fv3%2Foauth%2F%23redirect-uri-mismatch&state=59331cb8a700c409d17d003c
error:redirect_uri_mismatch
error_description:The redirect_uri MUST match the registered callback URL for this application.
error_uri:https://developer.github.com/v3/oauth/#redirect-uri-mismatch
state:59331cb8a700c409d17d003c

I'm pretty sure I'm not fully understanding what to put in the OAuth App configuration, but maybe I simply failed while doing something else. Any help would be appreciated.

The CMS quick start guide provides instructions for setting up OAuth: https://www.netlifycms.org/docs/quick-start/
Your callback url should be https://api.netlify.com/auth/done.


Not picking up FedEx package as in transit

V0.07, installed via HACS using latest version of documentation
HomeAssistant version - 0.105.3
Got an email notification from FedEx from<EMAIL_ADDRESS>with title:
FedEx Shipment 45280775XXXX: Your package is on its way
(Number redacted, but if you need it give me a way to DM you.)
But no state change on sensor.packages_in_transit or sensor.mail_fedex_packages.
Link to email (address/package number redacted): https://drive.google.com/file/d/1foXa0mYWvv71c2C_vMgr256dzyXCt3YG/view?usp=sharing
Expected behavior:  Sensors would increase from 0 to 1 in at least packages in transit.

The sensor doesn't look at or keep track of tracking numbers. Is this the only email you received about this package delivery? Did you get any with "Delivery scheduled for today" in the subject line?

The sensor doesn't look at or keep track of tracking numbers.

I know that.  I was speaking about the email link I posted.  I wanted you to know that it was edited to show as REDACTED in the text in case you saw it or used it in parsing while testing.

Is this the only email you received about this package delivery?

Yes, so far.

Did you get any with "Delivery scheduled for today" in the subject line?

No, the delivery is scheduled for Tuesday, two days away.   Does it only parse delivery day messages?  I was under the impression that since there was a sensor.mail_fedex_delivering that this would be fed by in transit emails.  Am I misunderstanding it's function?

Yes, it is only looking at current day in transit or delivered email messages. We have seen vendors adding additional emails subjects lines and using multiple subject lines for the same type of notification. There is not way of us knowing until a users reports or we receive a message that is different so we can add it to the subject line search for a particular package vendor.
Enhancement:
Fedex
Email Address: Same
new subject line for in transit count 'Your package is on its way'

I had a feeling I might have misunderstood; thanks for clearing that up for me.  I really appreciate the hard work you, @firstof9 and @FuzzyMistborn have put into this; it's a great solution.  The updated docs as so much clearer now as well.  Thanks to all and to you for your help.

I'm thinking a regex like:
FedEx Shipment /^[0-9]{15}$/: Your package is on its way for these types of email.

The subject I got today for an incoming delivery was identical to the above, but the tracking is 12 digits. According to Stack Overflow Fedex can be 12, 15 or 20 digits. So maybe a range of 12-20
`FedEx Shipment /^[0-9]{12,20}$/: Your package is on its way

Maybe it would be easier, and long term sustainable, if it matching if contains ‘Your package is on its way’ instead of accounting to the entire headline?

Well, now I am totally confused.  Today I got a FedEX email with the subject "FedEx Shipment 45280775XXXX: Your package is scheduled for delivery today" but still nothing showing in the sensors.  In fact nothing on ANY of the sensors.
Now I recently reinstalled everything because in another issue, I was told that the sensor templates in the old package install version was deprecated and no longer necessary.  So I commented everything out, moved my old /custom_components/mail_and_packages folder to a safe location and reinstalled everything from the latest doc instructions.
I didn't have any mail for a few days so I didn't think anything was wrong.  But today I have USPS mail and nothing was showing up at all.  Even the sensors weren't there.  So I reversed my procedures and uncommented out my previous template sensors and my mail is showing again, as is the camera image and all my other sensors.  But FedEx sensors are still showing zero states.
So while I am glad I've got USPS mail/packages showing properly, I am thoroughly confused about what the proper procedures/code versions are.  What am I doing wrong here?

@rpitera, If you are using the current files in the repository you will find in Home Assistant  going to 'Developer Tools' > 'States' that if you type in mail_ in the filter entities field you should see all of the entities the custom component is creating, below.

sensor.mail_fedex_delivered
sensor.mail_fedex_delivering
sensor.mail_fedex_packages
sensor.mail_packages_delivered
sensor.mail_packages_in_transit
sensor.mail_updated
sensor.mail_ups_delivered
sensor.mail_ups_delivering
sensor.mail_ups_packages
sensor.mail_usps_delivered
sensor.mail_usps_delivering
sensor.mail_usps_mail
sensor.mail_usps_packages

If you do not see all of these, there is something wrong. The the front end card, the previously included Lovelace card is depreciated and is no longer supported. The readme for this repository provides three options for adding the sensors to the front end. Option 3 doesn't require any additional customization of HASS and was recently updated to correct a few mistakes.

@firstof9 I think the subject line search does match with 'contains' because originally I only had 'Your package has been delivered' as the subject to match and I have had the sensor count them. All my fedex emails subjects have the tracking number in the beginning.

Reviewing the code, there is still a mismatch in the subject line
We are looking for FEDEX_Delivering_Subject = 'Delivery scheduled for today' which is what the subjects were for most of 2019.
'Your package is on its way' is for future deliveries and we won't track this.
'Your package is scheduled for delivery today' seems to be the new subject starting end of November/December 2019. There is no way of telling if they changes all day of subject lines to this or if they are testing it. We'll have to add this in addition to the old one.
This will solve then issue of the day of notification not being counted.

If you do not see all of these, there is something wrong.

Yes, I agree.  But after following all the instructions step by step I'm at a loss as to what is the problem.
Here is the steps that I took when I reinstalled from using the 'deprecated' method:

Commented out all of the template sensors I had originally created.  Added the one template sensor for the mail deliveries message above the commented code.
Moved the deprecated version folder of /custom_components/mail_and_packages/ from my HA server to a safe location on my PC.  (This left me with no mail_and_packages folder in custom_components, by design since using the HACS install should replace it.) Did the same with the contents of /www/mail_and_packages, reserving my originals in the same safe location just in case.
Added the camera entity to my cameras.yaml and the automation.
Removed my previous integration entry and restarted HA
Went to integrations, added mail and packages.  Altered the path to reflect the proper one for a HASS.IO (now HomeAssistant) installation.  Received a successful integration message.
Pasted code from first example (after fixing the indents) into my test page in Lovelace.  For good measure, one last restart of HA.

Do you guys see anything I missed or did incorrectly?  I'd be glad to try again - I've saved everything so I can go back - all I know is that it didn't work and no sensors seemed to be created.  I checked the folder structure and it looks correct - and I am using the latest version of HACS so the folders bug can't be at fault here.  The card displayed just fine; it's the sensor creation that seems to be at issue in my case.
In the meantime reverting back to the deprecated method at least is giving me sensors and USPS mail correctly (including the camera) so I can be sure that my other configurations (mail setup for each service and the imap host setup using gmail) is correct, so that can be ruled out.
I'm open to suggestion and testing.  And since I still have the mail in there today, there's something to test against.

Can you update the logger portion of your configuration.yaml (or wherever you have logger defined in your configuration) and supply the output?
logger:
default: warning
logs:
custom_components.mail_and_packages: debug
homeassistant.components.sensor: debug
I am not familiar with the HACS installation method. Is the /www/mail_and_packages/ folder created and filled with any files after the integration is setup?

Can you update the logger portion of your configuration.yaml (or wherever you have logger defined in your configuration) and supply the output?

I'll have to remove the deprecated version first and reinstall but I'd be glad to.

I am not familiar with the HACS installation method. Is the /www/mail_and_packages/ folder created and filled with any files after the integration is setup?

It must, because the vertical stack in card option 1 showed the no mail.gif file properly.  I could just as easily reinstall this using the manual method though if you prefer.

One this is that the first option for Lovelace does require a custom card is also added to Home Assistant.

Yeah, I think you may not be getting me here - the card displayed fine.  I use custom cards all the time and already had vertical-stack-in-card installed.  I'm way past the basics.  I use a LOT of custom cards and custom CSS in my Lovelace card styling.  I've also been at this since 2013 so I know my way around... ;-)  Also do a lot of beta testing for other devs.
When I say I didn't see the sensors, I'm talking about dev > states where the actual sensor entities would be found. (I'm sorry if this wasn't clear; I just assumed you knew where I was looking for sensors.)  Using the previous installation method I laid out in steps, I didn't have any sensors from mail & packages at all.  They should have been created around line 64 in sensor.py but never were.  Hopefully reinstalling and running debug mode for the integration will reveal more.
I'm going to try uninstalling from HACS and just going manual this time.   I'll reclone the repo and make sure I have all the latest.  Will update you soon.

Made real progress here.  I now have sensors in dev > states AND the fedex sensors are showing with values for in transit and delivered.  I think I will have to modify the deliveries sentence template a bit to include FedEx and UPS though; it seems somehow wrong to me that the sentence doesn't account for them.
Manual seems to be the way to go; maybe something wrong with the HACS install json?  My structure seemed fine and comparable to the current working version I just installed, but given that it is the only real difference between the two attempts, hacs.json is suspect.  It is also a viable reason my previous deprecated version 'worked' as it was also manually installed.  (I say 'worked' because that version didn't have any values for the fedex sensors like I have now.)
I only chose it because it was the "highly recommended" method.

Note for the regex here:
^FedEx Shipment [0-9]{12,20}:.*$
Should match anything after the tracking #

I don't think it is needed. Pretty sure it the search counts subjects that contain our phrase not exact matches.

BTW, until I can get a chance to work out the templating for a delivery sentence for FedEX/UPS I just added a glance card to the stack and styled it a bit.  I'll share it here in case you can use it...
  - type: custom:vertical-stack-in-card
    title: Mail & Package Tracking
    cards:
      - type: picture-glance
        camera_image: camera.mail_usps
        entities: []
      - type: entity-filter
        state_filter:
          - operator: ">"
            value: '0'
        entities:
          - entity: sensor.mail_usps_mail
            name: "Today's Mail"
          - entity: sensor.mail_packages_in_transit
            name: "Today's Package Delivery"
          - entity: sensor.mail_usps_delivering
            icon: 'mdi:package-variant-closed'
            name: USPS
          - entity: sensor.mail_fedex_delivering
            icon: 'mdi:package-variant-closed'
            name: FedEx
          - entity: sensor.mail_ups_delivering
            icon: 'mdi:package-variant-closed'
            name: UPS
          - entity: sensor.mail_updated
            state_filter:
              - operator: "regex"
                value: 20
      - type: entities
        entities:
          - entity: sensor.mail_deliveries_message
            icon: mdi:bullhorn
            name: ' '
      - type: glance
        title: ━━ UPS/FedEX ━━━━━━━━━━━━
        style: |
          ha-card {
            font-size: .80em;
          }
          ha-card div.card-header {
            font-size: 1.5em;
            color: cyan;
          }
        columns: 3
        entities:
          - entity: sensor.mail_ups_delivering
            name: UPS In Transit
          - entity: sensor.mail_ups_delivered
            name: UPS Delivered
          - entity: sensor.mail_ups_packages
            name: All UPS Packages

          - entity: sensor.mail_fedex_delivering
            name: FedEX in transit
          - entity: sensor.mail_fedex_delivered
            name: FedEX Delivered
          - entity: sensor.mail_fedex_packages
            name: All FedEX Packages


Proxy and tenant restrictions configuration is not listed here

This page should also include the details about tenant restrictions and proxy configuration that another page lists:
https://docs.microsoft.com/en-us/azure/active-directory/devices/hybrid-azuread-join-managed-domains#prerequisites
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 72cdc251-618a-e84e-f40d-960b0ac69f99
Version Independent ID: 8cbaba3c-e883-2c71-28fb-f88db3fcaf7d
Content: Plan hybrid Azure Active Directory join - Azure Active Directory
Content Source: articles/active-directory/devices/hybrid-azuread-join-plan.md
Service: active-directory
Sub-service: devices
GitHub Login: @MicrosoftGuyJFlo
Microsoft Alias: joflore

@hpsin Thank you for suggesting the same. We will have this reviewed with the content team and get this updated.

@hpsin
Thanks for your feedback! I've assigned this issue to the author who will investigate and update as appropriate.

This has been addressed. Pls close

#please-close


Incremental support (IPASIR)

Hello,
Many solvers support incremental solving and build a static library for interfacing with the solver. For example, Cadical emits an ipasir.o object file as per the makefile here:

https://github.com/arminbiere/cadical/blob/c622a490ec3d9a1a1e998b08120c9b8d0b67a123/makefile.in#L72

Given you've done a tremendous job compiling all these solvers, would it be possible to make it so an application can call these IPASIR static libraries easily?
The only way I can think to do this is to compile/link the incremental application inside the container alongside the solver. Therefore, I think a sensible approach might be to introduce a convention where the ipasir static library is placed in a specific location on the filesystem in the docker container. Then there could be some command-line flags to simplify this process of compiling and linking an application. For example:
$ satex list --supports-incremental

This ^ command could filter the list of solvers so that only those supporting incrementality are listed.
$ satex run cadical:2019 --application my_app

This ^ command could copy the my_app/ directory into the docker container and run make && make run - or something along those lines.
Obviously, there's a lot to be figured out, but I think this could be a useful feature that's broadly inline with the aims of the SAT Heritage project, to make a vast number of solvers easily available.
Thanks

Hi,
Cool feature indeed :-) I have the feeling it could be more suited for the satex build command: the idea would be to build your own docker image. Something like this for instance:
$ satex build cadical:2019 --ipasir my_app

which would build an image cadical:2019-my_app, and could be use with satex run cadical:2019-my_app or even directly with docker.
Do you have an example of my_app I can test with?

Sure, here's a barebones app:
my_app.zip
You can compile and run the app with make && make run.
I've included a version of libipasir I compiled on my Mac but that would need to be replaced with the one from the Docker image. You can set the -L switch in the makefile to search a filesystem path for it.
Thanks


Remove import from Core

Core.ts is deprecated. Remove its use from this project.

Fixed in 1cdc929145f5e46ba4d97724e55c19b222fb43b2


chore(docs): address old requests

Release Note
chore(docs): address old requests

No need to run checks, only docs changes.


no longer works

please update the bindings!!

Goofball

attempt to index global 'steamworks' (a nil value)
I hate to break this to you, but it doesn't work for me either. Tested using a dedicated server on Windows, both 32- and 64-bit binaries/branches…
… Goofball
I might try to figure out how to compile your project, but I've got one of my own I'm working my head around at the moment.

Obviously, it could be my turn to be the goofball, but maybe there is something wrong(?)

You need to require("workshop")

So it was my turn after all. Sorry to bother you. Definitely couldn't be doing what I'm doing without you.

So I did actually try that first before commenting here, but the project I'm working on is written in Teal, and the way we've got it set up has the build scripts set to run every time we save a file, but require works differently in Teal, and it caused an error. Consequently, the build script didn't complete, and the Lua didn't update. A goofy situation.


feat(cdk-text-field): Add row-wise error indicators for textarea.

Feature Description
myStackblitz
rowwise error/ success indicators are something I was looking for. It would be a nice acompany to cdkTextareaAutosize.
Is this something the cdk has an interest to further research and elaborate ?

this is just my first draft (no tests, no optimizations). I want to create a library if this is not interesting for the cdk.

Use Case
Have a lintable UX if bulk data is provided in a textarea.

Thanks for the proposal- we don't have any plans to add a feature like this


Unknown action buyrambytes in contract eosio with v20

Version of EOSJS
v20.0.0
Describe the bug
I'm unable to execute buyrambytes with v20. I have working examples with v16 and the same docker container, so I'm really not sure what's going on.
Error I receive is: "Unknown action buyrambytes in contract eosio" but I don't believe it's related to bootstrapping because:

I can run EOSJS v16 against the same docker container and successfully execute:

await this.eos.transaction(tr => {
        tr.newaccount({
            creator: this.accountsCreator.name,
            name: account.name,
            owner: account.publicKey,
            active: account.publicKey
        });

        tr.buyrambytes({
            payer: this.accountsCreator.name,
            receiver: account.name,
            bytes: 8192
        });

        tr.delegatebw({
            from: this.accountsCreator.name,
            receiver: account.name,
            stake_net_quantity: '10.0000 SYS',
            stake_cpu_quantity: '10.0000 SYS',
            transfer: 0
        });
    })

I can use cleos and create a new account just fine.

To Reproduce
Steps to reproduce the behavior:

Use EOSJS with eos in this setup: https://github.com/EOSIO/eosio-project-boilerplate-simple
Try to execute the following JS with the setup from the readme:

eos.transact(
{
	actions: [
		{
			account: 'eosio',
			name: 'newaccount',
			authorization: [
				{
					actor: creator.name,
					permission: 'active',
				},
			],
			data: {
				creator: creator.name,
				name: account.name,
				owner: {
					threshold: 1,
					keys: [
						{
							key: account.publicKey,
							weight: 1,
						},
					],
					accounts: [],
					waits: [],
				},
				active: {
					threshold: 1,
					keys: [
						{
							key: account.publicKey,
							weight: 1,
						},
					],
					accounts: [],
					waits: [],
				},
			},
		},
		{
			account: 'eosio',
			name: 'buyrambytes',
			authorization: [
				{
					actor: creator.name,
					permission: 'active',
				},
			],
			data: {
				payer: creator.name,
				receiver: account,
				bytes: 8192,
			},
		},
		{
			account: 'eosio',
			name: 'delegatebw',
			authorization: [
				{
					actor: creator.name,
					permission: 'active',
				},
			],
			data: {
				from: creator.name,
				receiver: account.name,
				stake_net_quantity: '10.0000 SYS',
				stake_cpu_quantity: '10.0000 SYS',
				transfer: false,
			},
		},
	],
},
{
	blocksBehind: 3,
	expireSeconds: 30,
}
);

Expected behavior
Expected success
Actual behaviour
Error: Unknown action buyrambytes in contract eosio
      at serializeActionData (/[project folder]/eosjs/src/eosjs-serialize.ts:1065:15)
      at Object.serializeAction ([project folder]/eosjs/src/eosjs-serialize.ts:1080:15)
      at Api.<anonymous> ([project folder]/eosjs/src/eosjs-api.ts:179:24)
      at step ([project folder]/eosjs/dist/eosjs-api.js:47:23)
      at Object.next ([project folder]/eosjs/dist/eosjs-api.js:28:53)
      at fulfilled ([project folder]/eosjs/dist/eosjs-api.js:19:58)
      at process._tickCallback (internal/process/next_tick.js:68:7)

Desktop (please complete the following information):

OS: Mac OS X 10.14.4
Browser: No browser involved
Runtime: Node v10.15.3

Context
Is there any good way to get nodeos to log out the transactions it receives exactly so I can see what the difference is between the two versions?

eosio-project-boilerplate-simple doesn't install the system contract. buyrambytes doesn't exist without it; all accounts have unlimited ram. eosjs 16 blindly assumed buyrambytes existed without checking; the result was a no-op.

Is there any good way to get nodeos to log out the transactions it receives exactly so I can see what the difference is between the two versions?

The closest is to use /v1/get_block. Decoding the action data will fail on the transaction generated by eosjs 16.

@thekevinbrown The project using eosjs v16 should not be "working" either, just failing silently.  I'm going to close this, but I'll open an issue in the boilerplate to install the system contracts so no one else has issues with this.


bug: Lack of guidance to users wrt debugging

Describe the bug
Some of the executables that users use have command line flags for turning up debugging, and these are documented.  But there is no high level guidance about using those.  More importantly, there is no other guidance about how users can debug problems.
Many systems have a "must-gather" script that gathers standard evidence (logs, config files, whatever) to include in a bug report.  Less automated systems have a document telling users what to gather and include in a bug report.
A user who tries to dive into one of the log files produced by kcp or KubeStellar is on their own.  There is no guidance for how to understand what is in those log files.  Many of them contain alarming error messages that are really just noise because they are reporting on a transient problem and there is no corresponding message (at the same verbosity level, thus usually not actually appearing) indicating that the problem has gone away.  And there is #671 (which #866 is likely to greatly mitigate or eliminate).
Steps To Reproduce
Hear from a user trying to debug a problem.
Expected Behavior
Users are not totally helpless.
Additional Context
No response

@eaepstein


Unknown field "serviceAnnotations" with last CRD

Bug Report
The deployment of the example command line breaks.
kubectl create -n nifi -f config/samples/simplenificluster.yaml

Kubernetes cluster kind:  GKE

Client Version: version.Info{Major:"1", Minor:"22", GitVersion:"v1.22.7", GitCommit:"b56e432f2191419647a6a13b9f5867801850f969", GitTreeState:"clean", BuildDate:"2022-02-16T11:50:27Z", GoVersion:"go1.16.14", Compiler:"gc", Platform:"darwin/amd64"}
Server Version: version.Info{Major:"1", Minor:"21", GitVersion:"v1.21.10-gke.2000", GitCommit:"0823380786b063c3f71d5e7c76826a972e30550d", GitTreeState:"clean", BuildDate:"2022-03-17T09:22:22Z", GoVersion:"go1.16.14b7", Compiler:"gc", Platform:"linux/amd64"}
➜  nifikop git:(master) kubectl create -n nifi -f config/samples/simplenificluster.yaml I0505 21:55:30.757329   63607 versioner.go:58] no Auth Provider found for name "gcp" error: error validating "config/samples/simplenificluster.yaml": error validating data: [ValidationError(NifiCluster.spec.externalServices[1]): unknown field "serviceAnnotations" in com.konpyutaika.nifi.v1alpha1.NifiCluster.spec.externalServices, ValidationError(NifiCluster.spec.externalServices[2]): unknown field "serviceAnnotations" in com.konpyutaika.nifi.v1alpha1.NifiCluster.spec.externalServices]; if you choose to ignore these errors, turn validation off with --validate=false
To solve I need to remove the serviceAnnotations but it is strange. I think the problem is elsewhere because it runs the creation but no way to use Nifi after.
Thanks a lot,
Best regards

The example is incorrect, the serviceAnnotations field is not present any more. It has been replaced by a metadata field.
I will update the sample.


host: Change Matrix password requirements

This changes to only requiring eight characters, as NIST has observed that symbol and number requirements result in predictable use of ! and 1, which doesn’t increase security.
I also removed a test that appeared redundant to me.

NIST does recommend having other checks though, like filtering on dictionary words - currently "password" is a validly complex password for us.

indeed, I was originally going to use that to drive the failing tests and then realised it wouldn’t fail 😬 I did a brief search on npm packages that would support this and they either seem abandoned or overly complex. But I think this is something we should improve before any wider release, thanks!


update gohlslib

Codecov Report

Merging #1565 (d12959a) into main (45727a6) will increase coverage by 0.19%.
The diff coverage is 60.00%.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
@@            Coverage Diff             @@
##             main    #1565      +/-   ##
==========================================
+ Coverage   64.97%   65.16%   +0.19%
==========================================
  Files          86       86
  Lines        9408     9408
==========================================
+ Hits         6113     6131      +18
+ Misses       2848     2829      -19
- Partials      447      448       +1

Impacted Files
Coverage Δ

internal/core/hls_muxer.go
51.05% <50.00%> (+0.35%)
:arrow_up:

internal/core/hls_server.go
76.54% <66.66%> (-0.10%)
:arrow_down:

... and 3 files with indirect coverage changes
:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


if.bind is not refreshed

Hi,
I have a custom element "nav-bar", please see snippet below. I would like to hide any items that I can't navigate to. That fact is determined by a (dependency injected) service that checks that based upon the route settings (also see snippet below:
Of course that changes if the for instance the user is logged-in (also done via the userService). It works for the initial page load, only showing items that require no authentication (auth:false).
The nav-bar doesn't change after the user has logged in (ergo, the binding 'doesn't see' the fact that the result of a userService.canNavigateTo() has changed. I would like to prevent from using a signaller that is on a setInterval loop... Feels kinda dirty to me. Is this a bug? Of would you recommend a solution that I haven't thought of maybe?
Thank you!!!!
example route:
{ route: 'users', name: 'users', moduleId: './pages/users', nav: true, title: 'Users', settings: { auth: true, role: ['admin'] } }

nav-bar template snippet:

	${route.title} ${userService.canNavigateTo(route.settings)}

BTW, I've "solved" this by exposing the (previously private) user object from the userService, add an "updated" date field to it, modify the if.bind clause to "if.bind="userService.user.updated && userService.canNavigateTo(route.settings)" and changing the updated date on successful login... But still feels a bit tricky/hacky though.....

I recommend restructuring things a little bit: http://stackoverflow.com/a/38743867/725866
Make the User something you can @inject. Nothing should need to inject the UserService, except for your login logic.
With those changes in place your code might change to something like this:
user
export class User {
  role = 'anonymous';
  isLoggedIn = false;
  name = 'Anonymous';
}

user-service
@inject(User)
export class UserService {
  constructor(user) {
    this.user = user;
  }

  login(username, password) {
    return http.post(....)
      .then(result => {
        if (result.something...) {
           this.user.role = result.role;
           this.user.name = result.name;
           this.user.isLoggedIn = true;
        });
  }
}

nav-bar:
@inject(User)
export class NavBar
  constructor(user) {
    this.user = user;
  }

<template>

    ${route.title}

</template>

Other links that might be helpful:

http://stackoverflow.com/questions/35019879/rebuilding-routes-after-refresh
http://stackoverflow.com/questions/33458274/how-to-switch-between-login-page-and-app-with-aurelia/33458652#33458652

Thanks!!! Really helpful. Nice one.


Update core to v14.2.0-12-g95c6efce8

Update realm-core to v14.2.0-12-g95c6efce8
Update Changelog

Included some cleanup of .gitignore and .pubignore I spotted along the way


Software design updates

Updated the software design documents (PlantUML source code) to reflect current architecture.
Renamed some class variables to be more descriptive and to use dunder notation (if private).
Added the interface for the SolarSensorDecoder module and wrote skeleton code in main.py for implementation.
Unit tests all pass for the QuadCellDecoder module.
Need to verify that all changes will work on the Pi before merging.

Taking a look at this now. Probably won't merge until tmr morning tho

@John0b1000 Out of curiosity, how many bits is the adc we're using?

Arduino has 10-bit ADC (0-1023 range). No rush on the merge

@John0b1000 you need to approve it too before we can merge. It looks good on my end tho.


comment and review styles are broken

The styles associated with product reviews are not good.

branch was named wrong. issue 24 is the branch head.
also, the star reviews are missing as a result of ripping out bootstrap. That needs to be restored.

All fixed.


Text Extractor: Accent marks

Description of the new feature / enhancement
This feature is awesome but with accent marks works pretty bad it changes
Scenario when this would be used?
When the feature does an OCR over Spanish characters
Supporting information
Examples
Result => correct
6 => ó
å => á

Thanks for your message. This is a Duplicate of an other issue. Additional comments may be added there. /dup #20899


Server can "forget" Agent after reconnect

Reported by @christoph-hamm.
Current Behavior
The server keeps a map from agent name to connection. This map is used to send messages to specific agents. If an agent connects with name, already known to the server, the server will replace the old connection with the new connection in the map. If the connection to an agent is interrupted, the server will remove this agent from the map.
This will or can lead to the new agent not getting messages in the following scenario:
Steps to Reproduce

Agent A connects to the server => Agent A is added to the map
Agent A crashes completley, not terminating the TCP connection (e.g. the machine/VM crashes) => nothing, the Server is not aware of Agent A has crashed
Agent A restarts and connects to the server => the old Agent A connection is replaced with the new one in the map
The TCP connection if the first Agent A times out => the Agent A connection is removed from the map

In the end Agent A is still connected to the Server, but its connection is not stored in the map. If a message needs to be sent to Agent A, the Server is not able to do this.

We should take care to stop the task handling the old connection before creating a new one.

I have tried to simulate the error scenario as follows:
--- startup-config.yaml
workloads:
  nginx:
    runtime: podman
    agent: agent_A
    restart: true
    updateStrategy: AT_MOST_ONCE
    accessRights:
      allow: []
      deny: []
    tags:
      - key: owner
        value: Ankaios team
    runtimeConfig: |
      image: docker.io/nginx:latest
      ports:
      - containerPort: 80
        hostPort: 8081

Ankaios is up and running

Ankaios agent is up and running (nginx workload is in ExecRunning); The agent server grpc connection is intact at default port 25551!

Add the rule to the iptables to drop all tcp incoming messages on port 25551 with sudo iptables -A INPUT -p tcp --dport 25551 -j DROP in order to simulate the "crash" of the agent.

Stop the running agent. Note: The server does not notice that the agent is not running anymore, because the connection is still intact!

Restart Ankaios agent again, it tries to connect to the server

Remove the rule to drop all tcp incoming messages on port 25551 from the iptables with sudo iptables -D INPUT -p tcp --dport 25551 -j DROP in order enable the grpc connection again.

Ankaios server receives a 'hello' message from the restarted Ankaios agent via a new grpc connection and detects that an agent with the same exists already in the map, so that it replaces the entry in the map with the restarted agent. While dropping the old entry from the map, the old background task is automatically closed through the grpc connection error send by the system which is handled by the old background task!

So with this it is proved that the described issue is already handled properly by the current Ankaios implementation -> No fix needed!


Please update XenForo add-on

The XenForo add-on was not updated until 2012.
https://xenforo.com/community/resources/customisable-browser-update-org-widget.764/history
It's quite old...

Okay, the developer of the add-on does not want to update it.
See https://xenforo.com/community/threads/customisable-browser-update-org-widget.32090/#post-953144


[FIX] isEqualOrSubPath function

Added better description discussed in #972
Stopp using the normalize function discussed in #1033

@ronzulu what I am doing wrong? I run npm run changelog

Hi @4Source.
There are actually a few different issues here:

How updates to the change log should be done for a PR
Incorrect updating of references within Major reworking of the documentation #1032(my fault)
Auto generation of the change log

Updating the change log in a PR
I don't think we can use auto generation of the change log whilst working on a PR as it generates the change log based on what has already been merged into master (I believe).
So I've always just manually updated the change log as described in "Add your change to the [Unreleased] section of the changelog" in https://www.stephenmwangi.com/obsidian-spaced-repetition/contributing/#code.
So I think that's probably what needs to happen now with your PR.
Incorrect updating of references (my fault)
Background
With the major reworking of the documentation https://github.com/st3v3nmw/obsidian-spaced-repetition/pull/1032, I created a test vault for taking screenshots for the user documentation.
I tried to create this under the existing directory structure, i.e. under /docs. But I can find a way to stop mkdocs from including those files within the generated static website.
So my solution was to create a new level in the directory structure, as:

I tried to change all references, but I didn't catch all, including the reference in file (root level) /changelog.md.
I have fixed this now on the documentation branch.
Auto generation of the change log
Out of curiosity I ran pnpm run changelog to update the change log automatically (something I've never needed to do).
For some reason even though docs/docs/changelog.md is specified in the command auto-changelog --template=compact --package && npx prettier --write docs/docs/changelog.md (package.json), the change log was generated at /changelog.md.
This seems to also be the case in what happened with you… /changelog.md got updated rather than docs/changelog.md.

Auto generation of the change log
Out of curiosity I ran pnpm run changelog to update the change log automatically (something I've never needed to do).
For some reason even though docs/docs/changelog.md is specified in the command auto-changelog --template=compact --package && npx prettier --write docs/docs/changelog.md (package.json), the change log was generated at /changelog.md.
This seems to also be the case in what happened with you… /changelog.md got updated rather than docs/changelog.md.

I think this should be possible to auto generate the unreleased section with actions

This seems to also be the case in what happened with you… /changelog.md got updated rather than docs/changelog.md.

changelog.md is a symbolic link to docs/changelog.md. It mostly works okay but gets all messed up on a non-unix OS.

Because of the conflicts we've been having with the changelog.md file, we can stop updating the file within the PRs and only do it during releases. I'll update the docs..


[csharp] Verify codegen

The code gen is running but isn't being verified.  This builds the source in the same way as the other languages.
It fixes the stub code so it uses the stub functions not just creating a class so that the code generated can compile.
It uses the CI work enabled in #718, so will rebase after that is in.

There is not enough space on the disk.

Seems like the builds for dotnet take up lots of space 🤔

There is not enough space on the disk.

Seems like the builds for dotnet take up lots of space 🤔

Yes, its unfortunate.  Do we need to ask for more space?

The only option for getting more space is moving to the Enterprise or custom runners :-/  Interestingly it seems that some times we get a drive with 100GB+  and that's why it passed once.
I think we have a few options:

Clean up the project after build - Trying this out first
use the C: drive for build outputs - not technically supported but seems that other projects have done this (https://github.com/actions/runner-images/issues/1341#issuecomment-669204383)
refactor the project builds so they happen on different jobs - I think this is probably the right choice longer time which will also speed up CI and can look at it later

I would very much recommend using C: for output. Enough projects are depending on that that I have a hard time seeing GH just break it. And even if they do, we can solve it then instead of preemptively trying to solve a problem we might never have :)


Support proxy

Is your feature request related to a problem? Please describe.
Sometimes (for webscrapping tools, for example) it's helpful to have an option to have the ability to pass proxy
Describe the solution you'd like
I'd like proxy (in requests library way) as an argument for 'filings' function
proxies = {      'http': 'http://<IP_ADDRESS>:80',      'https': 'https://<IP_ADDRESS>:8080', }
So:
my_filings = filings(cik_lookup="V",                      filing_type=FilingType.FILING_10K<EMAIL_ADDRESS>                     proxies=proxies)

This is possible. Would you want to create a pull request to implement this? I think all you would need to do is add the ability to the fetch method in client.py and then change a few things downstream to accept the kwargs. The more general way would be to make it so that any keyword arguments can be passed to the session you are using via aiohttp when running session.get.
@staticmethod
async def fetch(link, session, **aiohttp_kwargs):
    """Asynchronous get request.

    Args:
        link (str): URL to fetch.
        session (aiohttp.ClientSession): Asynchronous client session to use to perform
            get request.

    Returns:
        Content: Contents of response from get request.
    """
    async with await session.get(link, **aiohttp_kwargs) as response:
        contents = await response.read()
    return contents


Sending AT commands

Hello, I need your help for configuring the module.
I'm trying to connect to the module with an usb to serial adapter and a terminal program but it does not work.
Is there a pin to enable the module to receive AT commands?
I can change the frequency over bluetooth but i do not recive audio.
I'm using the FT8CN software.
mni tnx es 73 de Frederico

have you tried AT commands with or without the "\r\n"?

It does not work with and without, it looks like I got some fake modules.
I have create my own PCB with the BT-401 Module and it works fine
73 Frederico.

thanks

BT401 is my next target.


[33] ResizableImage improvement

For #33
This PR removes the KingFisher dependency in favour of AsyncImage and improves upon how we handle async images.
Removed hardcoded sizing for images fetched from URLs. Removed hardcoded contentMode for images. ( Now defaulting to .aspectFit). ResizableImage now take a generic view for the placeholder view when loading an async image. The default placeholder is an empty LoadingView.
Due to the usage of generics, I created a LocalResizableImage typealias for any non-async ResizableImage that is now being referenced in places that depend on ResizableImages. This causes NiceButtons left/right images to now only support local images.  This is a constraint I don't believe should affect us at the moment, but is worth being aware of and addressed in the future.
https://user-images.githubusercontent.com/17748596/184031790-7a3551dd-a8c5-4581-a3f9-293dd72f466b.MP4

AsyncImage does handle caching https://www.avanderlee.com/swiftui/downloading-caching-images/#:~:text=AsyncImage would be enough for,more advanced image processing options

AsyncImage does handle caching https://www.avanderlee.com/swiftui/downloading-caching-images/#:~:text=AsyncImage would be enough for,more advanced image processing options

Upon looking further into this, it looks like we may want to stick with Kingfisher anyway just to have a better caching mechanism / not have to rely on URLCache. The tradeoff being we have a third party dependency, but KF is one of the more reliable libraries out there so shouldn't be a problem.


fix(charts): Fix chart load task error handling

SUMMARY

The exceptions raised within this task are given internationalised messages (flask-babel), which means when the task tries to serialise the exception message to mark the job as failed, it needs to make sure they're rendered first. Cast to str to make that happen.
The underlying issue was using lazy_gettext when just using gettext would make more sense, so I've also adjusted the import in a couple of obvious places directly impacting this task to fix it at both ends.
I've left in the str cast fix as it'd require a much deeper dive to determine if any other edge cases would still result in a lazy message given the complexity of the task.
TESTING INSTRUCTIONS
See associated issue for full details.

Configure GLOBAL_ASYNC_QUERIES
Create a virtual dataset from any query
Edit the dataset to have invalid SQL, e.g. a syntax error
Click through to the charts page

ADDITIONAL INFORMATION

Fixes #24446

[x] Has associated issue: #24446
[x] Required feature flags:
[ ] Changes UI
[ ] Includes DB Migration (follow approval process in SIP-59)

[ ] Migration is atomic, supports rollback & is backwards-compatible
[ ] Confirm DB migration upgrade and downgrade tested
[ ] Runtime estimates and downtime expectations provided

[ ] Introduces new feature or API
[ ] Removes existing feature or API

Thanks @giftig. Would you mind adding a unit test as well? This helps both with reviewing the PR and ensures we don't regress in the future.

@john-bodley yeah I see there's currently no coverage of this task at all; I'll take a look at writing something simple to cover this.

I've added a unit test covering the failure scenario specifically using lazy_gettext in the exception as that's a worst-case scenario, but it passes ok with gettext or a plain string too (I thought parametrize would be a bit excessive coverage here)


gateway-api: Skip reconciliation for non-matching controller routes

This commit is to make sure that only gateways matching cilium pre-defined controller are re-queued for reconciliation.
Testing was done with the below spec, the expected behavior is no-op as the controllerName of GatewayClass of Gateway of underlying HTTPRoute is not same as pre-defined cilium controller name value (e.g. io.cilium-gateway-controller)
apiVersion: gateway.networking.k8s.io/v1beta1
kind: GatewayClass
metadata:
  name: cilium
spec:
  controllerName: io.cilium/gateway-controller-non-matching
---
apiVersion: gateway.networking.k8s.io/v1beta1
kind: Gateway
metadata:
  name: my-gateway
spec:
  gatewayClassName: cilium
  listeners:
  - protocol: HTTP
    port: 80
    name: prod-web-gw
    allowedRoutes:
      namespaces:
        from: Same
---
apiVersion: gateway.networking.k8s.io/v1beta1
kind: HTTPRoute
metadata:
  name: http-app-1
spec:
  parentRefs:
  - name: my-gateway
    namespace: default
  rules:
  - matches:
    - path:
        type: PathPrefix
        value: /details
    backendRefs:
    - name: details
      port: 9080

Status of resources
# Ignore Gateway as it's not matching controller name in cilium
$ kg gateway my-gateway -o json | jqs
{
  "conditions": [
    {
      "lastTransitionTime": "1970-01-01T00:00:00Z",
      "message": "Waiting for controller",
      "reason": "NotReconciled",
      "status": "Unknown",
      "type": "Accepted"
    }
  ]
}

# Ignore HTTP Route as it's under cilium controller
$ kg httproute http-app-1 -o json | jqs
null

```

/test

/test-runtime

/test-1.26-net-next

/mlh new-flake Cilium-PR-K8s-1.26-kernel-net-next


[NVIDIA] Use custom grad accumulation for FP8 params

This PR is based on the https://github.com/google/flax/pull/3623 to use the custom grad accumulation for the FP8 params.

cc. @nluehr @reedwm @zhangqiaorjc

Also, cc. @mingxu1067


[W6.1h][W14-B4] Jiang Chunhui

@Adoby7
Comments given. Check and acknowledge and close the PR thereafter. Good effort!


Edited summary

Added description for this class.

Docs Build status updates of commit dfb5fa4:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

sharepoint-server/xml/Microsoft.SharePoint.Administration/SPDatabase.xml
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


As a cloud.gov operator, I need to be able to remove an IDP.

Needed to fulfill support ticket: https://cloud-gov.zendesk.com/agent/tickets/2410

https://github.com/cloud-gov/cg-scripts/pull/129
https://github.com/cloud-gov/cg-site/pull/1668


Socket client disconnect

Hi guys,
There seems to be no websocket reconnect mechanism implemented and the hearbeat interval is not respected here.
To reproduce on Mac please start your app, wait until it is loaded and turn WiFi off for a second. Client greys out and the following is found in the console:
WebSocket network error: The operation couldn’t be completed. Socket is not connected
TypeError: null is not an object (evaluating ‘this.$socket.readyState’)

I was wondering if there are settings to workaround this? If not, is it possible to introduce a time out setting for websocket connection or implement a reconnect mechanism?
This would be very useful, for example, when running on mobile where websocket connection is closed when the phone is locked.
The issue was also submitted as a question on
openanalytics forum
Many thanks!

Hi again,
I ended up implementing a workaround using  session$allowReconnect.
But still, it would be great if this was fixed on shinyproxy side.

Thanks for the detailed report, @mikiril

Hi @mikiril
Automatically reconnecting the websocket connection is part of ShinyProxy 2.6.0 (ContainerProxy 0.8.10) which we just released.
Note that this isn't a magic feature: your R Shiny app still has to support the reconnecting mechanism, but it can now be controlled from within ShinyProxy. See our docs for more information: https://shinyproxy.io/documentation/ui/#automatically-reconnecting-websockets
Since this is quite a complex feature with many little details, I'm looking forward to your experience with it. Don't hesitate to report any positive or negative experience with it, thanks :)


error 502

every time i try to use it i get error 502 here is a screen shot for proof which i thought you might want

Oh, that means you are using an outdated link.
Join https://discord.gg/BMxe6D9CKv for new links every day.

Solution given


Change images paths

Hi.
My images are neither in /public/img nor in /storage/images. How do I set up custom paths?

Hey!
You should have a look at this file:
vendor\shawnsandy\img-fly\src\Classes\ImgFly.php
/**
 * Display images from public/img
 *
 * @param [string] $image_str
 * @param string $dir
 * @return void
 */
public function imgPublic($image_str, $dir = 'img')
{
    return $this->loadImg("public/$dir", $image_str);
}

I hope I helped you!

Can we make the package more versatile and allow us to determine what is the prefix to put in place instead of /public?

I used the undocumented method Imgfly::loadImg($path, $image_str);


Add check for input parameter being null.

Fixes #20175.

If this is never going to happen in practice, it should be a DEBUG_ASSERT rather than an error (imo); the master version itself was apparently just adding in a useless check for nullptr.

I agree that it should never happen, but in general, we have been trying to limit the asserts in our code.  This code isn't something that gets called in the fastpath, so I don't mind the overhead of the extra error handling.

If an assert is the problem, then so is the if check. Why not just delete the check altogether?

Null is a common sentinel value.  There's not much we can do to protect against other invalid values (e.g., arbitrary memory corruption), but I think it's not unreasonable to check for null.

Known issues: #20095 #20198
The objc ios test failure is an infrastructure timeout.


Julia 1.6 support

Why require Julia 1.7?
Could even Julia 1.0 be supported?

All of the collections in this package require mutating GC-managed objects atomically. Unfortunately, this was simply not possible to do before Julia 1.7.


Bump Elasticsearch 6.8.22 -> 6.8.23

Elasticsearch 6.8.23 updates to log4j 2.17.1 which addresses CVE-2021-44832

Fixed in #6609


Bad minimum agent version on MSBuild, PublishSymbols and VSBuild tasks

Hi,
in the latest version of MSBuild, PublishSymbols and VSBuild, the action handlers specified use node and/or powershell3. But the minimum agent version is the json file is 1.83.0. This is wrong since this agent doesn't have a powershell3 handler.

https://github.com/Microsoft/vso-agent-tasks/pull/1457

fixed


One shot AWS deploy script broken

The one shot aws deploy script is now broken with the latest changes to the AWS deploy command. We should either fix this or remove the one shot script from the docs:
sudo -E ./aws.sh
...
...
...
+ cmd=(pachctl deploy amazon ${BUCKET_NAME} "${AWS_ID}" "${AWS_KEY}" " " ${AWS_REGION} ${STORAGE_SIZE} --dynamic-etcd-nodes=3)
+ [[ false == \t\r\u\e ]]
+ [[ true == \f\a\l\s\e ]]
+ pachctl deploy amazon 21116-pachyderm-store blah blah ' ' us-east-1 100 --dynamic-etcd-nodes=3
expected 3 arguments, got 6

Usage:
  pachctl deploy amazon <S3 bucket> <region> <size of volumes (in GB)> [flags]

Flags:
      --cloudfront-distribution string   Deploying on AWS with cloudfront is currently an alpha feature. No security restrictions have beenapplied to cloudfront, making all data public (obscured but not secured)
      --credentials string               Use the format '--credentials=<id>,<secret>,<token>'
<id>, <secret>, and <token> are session token details, used for authorization. You can get these by running 'aws sts get-session-token'
      --iam-role string                  Use the given IAM role for authorization, as opposed to using static credentials.  The nodes on which Pachyderm is deployed needs to have the given IAM role.

Global Flags:
      --block-cache-size string       Size of pachd's in-memory cache for PFS files. Size is specified in bytes, with allowed SI suffixes (M, K, G, Mi, Ki, Gi, etc).
      --dash-image string             Image URL for pachyderm dashboard (default "pachyderm/dash:0.5.9")
      --dashboard                     Deploy the Pachyderm UI along with Pachyderm (experimental). After deployment, run "pachctl port-forward" to connect
      --dashboard-only                Only deploy the Pachyderm UI (experimental), without the rest of pachyderm. This is for launching the UI adjacent to an existing Pachyderm cluster. After deployment, run "pachctl port-forward" to connect
      --dry-run                       Don't actually deploy pachyderm to Kubernetes, instead just print the manifest.
      --dynamic-etcd-nodes int        Deploy etcd as a StatefulSet with the given number of pods.  The persistent volumes used by these pods are provisioned dynamically.  Note that StatefulSet is currently a beta kubernetes feature, which might be unavailable in older versions of kubernetes.
      --etcd-cpu-request string       (rarely set) The size of etcd's CPU request, which we give to Kubernetes. Size is in cores (with partial cores allowed and encouraged).
      --etcd-memory-request string    (rarely set) The size of etcd's memory request. Size is in bytes, with SI suffixes (M, K, G, Mi, Ki, Gi, etc).
      --log-level string              The level of log messages to print options are, from least to most verbose: "error", "info", "debug". (default "info")
      --no-metrics                    Don't report user metrics for this command
      --pachd-cpu-request string      (rarely set) The size of Pachd's CPU request, which we give to Kubernetes. Size is in cores (with partial cores allowed and encouraged).
      --pachd-memory-request string   (rarely set) The size of PachD's memory request in addition to its block cache (set via --block-cache-size). Size is in bytes, with SI suffixes (M, K, G, Mi, Ki, Gi, etc).
      --shards int                    (rarely set) The maximum number of pachd nodes allowed in the cluster; increasing this number blindly can result in degraded performance. (default 16)
      --static-etcd-volume string     Deploy etcd as a ReplicationController with one pod.  The pod uses the given persistent volume.
  -v, --verbose                       Output verbose logs
etc...

@sjezewski I assume this will be getting fixed soon, because we use it in tests?

Also, it appears that there is a DNS related issue:
W1003 10:59:13.800685   13140 executor.go:109] error running task "DNSZone/kubernetes.com" (9m59s remaining to succeed): error associating VPC with hosted zone "kubernetes.com": LimitsExceeded: Limits Exceeded: Cannot associate more VPCs to hosted zone.
        status code: 400, request id: 6b39e841-a84b-11e7-a5d2-09d8d35a3b4f
I1003 10:59:13.800787   13140 executor.go:91] Tasks: 43 done / 63 total; 16 can run
I1003 10:59:19.453050   13140 launchconfiguration.go:320] waiting for IAM instance profile "nodes.616db8c8-pachydermcluster.kubernetes.com" to be ready
I1003 10:59:19.461799   13140 launchconfiguration.go:320] waiting for IAM instance profile "masters.616db8c8-pachydermcluster.kubernetes.com" to be ready
W1003 10:59:29.946099   13140 executor.go:109] error running task "DNSZone/kubernetes.com" (9m43s remaining to succeed): error associating VPC with hosted zone "kubernetes.com": LimitsExceeded: Limits Exceeded: Cannot associate more VPCs to hosted zone.
        status code: 400, request id: 6be03a21-a84b-11e7-a516-d97526d8e4a7
I1003 10:59:29.946172   13140 executor.go:91] Tasks: 58 done / 63 total; 3 can run
W1003 10:59:30.450248   13140 executor.go:109] error running task "DNSZone/kubernetes.com" (9m42s remaining to succeed): error associating VPC with hosted zone "kubernetes.com": LimitsExceeded: Limits Exceeded: Cannot associate more VPCs to hosted zone.
        status code: 400, request id: 753d3b56-a84b-11e7-a5d2-09d8d35a3b4f
I1003 10:59:30.450360   13140 executor.go:91] Tasks: 60 done / 63 total; 1 can run
W1003 10:59:30.807324   13140 executor.go:109] error running task "DNSZone/kubernetes.com" (9m42s remaining to succeed): error associating VPC with hosted zone "kubernetes.com": LimitsExceeded: Limits Exceeded: Cannot associate more VPCs to hosted zone.
        status code: 400, request id: 7593bf38-a84b-11e7-a5d2-09d8d35a3b4f
I1003 10:59:30.807430   13140 executor.go:124] No progress made, sleeping before retrying 1 failed task(s)
I1003 10:59:40.807676   13140 executor.go:91] Tasks: 60 done / 63 total; 1 can run
W1003 10:59:41.142839   13140 executor.go:109] error running task "DNSZone/kubernetes.com" (9m31s remaining to succeed): error associating VPC with hosted zone "kubernetes.com": LimitsExceeded: Limits Exceeded: Cannot associate more VPCs to hosted zone.
        status code: 400, request id: 7bb93bb9-a84b-11e7-a516-d97526d8e4a7
I1003 10:59:41.143043   13140 executor.go:124] No progress made, sleeping before retrying 1 failed task(s)
I1003 10:59:51.143542   13140 executor.go:91] Tasks: 60 done / 63 total; 1 can run
W1003 10:59:51.492270   13140 executor.go:109] error running task "DNSZone/kubernetes.com" (9m21s remaining to succeed): error associating VPC with hosted zone "kubernetes.com": LimitsExceeded: Limits Exceeded: Cannot associate more VPCs to hosted zone.
        status code: 400, request id: 81e34c22-a84b-11e7-9f9f-d19c06ccfd46
I1003 10:59:51.492358   13140 executor.go:124] No progress made, sleeping before retrying 1 failed task(s)

I believe the 2nd issue isn't DNS ... its a limit on the VPCs in that region ... you have to delete a few.


CCSD(T) Densities

Description
This PR will add CCSD(T) one- and two-electron densities to PyCC.
Todos

[X] Add an "inverted" triples driver to cctriples.py.
[X] Add dertype option – though gradients will not be fully implemented yet, and I may decide on a different workflow.
[ ] Add and debug densities.
[ ] Add a test case.

Status

[ ] Ready to go

Codecov Report

Merging #53 (9073fbc) into main (3378688) will decrease coverage by 1.73%.
The diff coverage is 12.32%.


Affordance for keyboard shortcuts for Streams

This may take the form of an overlay triggered via a keyboard shortcut and/or via a context menu item.
There is a suggestion to add the keyboard shortcut tiddler to the sidebar, however this implies a dependency on the default layout.

https://user-images.githubusercontent.com/68092/125172088-dabcc080-e1b7-11eb-87a7-34503abb9bf1.mp4


Pretrained model weights

Hello all,
The pretrained model link is not working, any idea ?

We upload a new one here: https://drive.google.com/file/d/1dPJo2maIZijCsUlwOeV0WPb83KbGhiY4/view?usp=drive_link


Open Recent entries order change even on "save the changes" dialog cancel

Hi everybody,
This is my first post so a great thanks to the devs for this great editor !
Here is my submission :

VSCode Version: 1.19.3
OS Version: Linux Ubuntu 16.04

Steps to Reproduce:

Have some Open Recent entries (> 1)
Open a project
Modifiy one of your project file but do not save it !
Open the last project in the File => Open Recent list
Click on the Cancel button of the "Do you want to save blablabla" dialog
Look at the File => Open Recent list, the order changes even if you do not open any project

@jeanpul what is the "project file"?

@bpasero any project repository

Oh yeah I can reproduce.


pip package missing json file

I try to execute following cnn_pred_explain notebook on Colab.
https://github.com/microsoft/tensorwatch/blob/master/notebooks/cnn_pred_explain.ipynb
But I failed to execute it, because following error appeared.
---------------------------------------------------------------------------
FileNotFoundError                         Traceback (most recent call last)
<ipython-input-5-b08090dd95a6> in <module>()
     10 image_utils.show_image(img)
     11 probabilities = imagenet_utils.predict(model=model, images=[img])
---> 12 imagenet_utils.probabilities2classes(probabilities, topk=5)
     13 input_tensor = imagenet_utils.image2batch(img)
     14 prediction_tensor = pytorch_utils.int2tensor(239)

2 frames
/usr/local/lib/python3.6/dist-packages/tensorwatch/imagenet_utils.py in __init__(self, json_path)
     54         json_path = json_path or os.path.join(os.path.dirname(__file__), 'imagenet_class_index.json')
     55
---> 56         with open(os.path.abspath(json_path), "r") as read_file:
     57             class_json = json.load(read_file)
     58             self._idx2label = [class_json[str(k)][1] for k in range(len(class_json))]

FileNotFoundError: [Errno 2] No such file or directory: '/usr/local/lib/python3.6/dist-packages/tensorwatch/imagenet_class_index.json'

In my guess, python pip package misses json file inclusion.
Reference
A Simple Guide for Python Packaging
https://medium.com/small-things-about-python/lets-talk-about-python-packaging-6d84b81f1bb5

On Colab, I execute following script. image_data should be include on python package.
Then following git clone command will be removed.
!pip install tensorwatch
!pip install lime
!git clone http://github.com/microsoft/tensorwatch
!cp -r tensorwatch/data ..
%matplotlib inline
from tensorwatch.saliency import saliency
from tensorwatch import image_utils, imagenet_utils, pytorch_utils
model = pytorch_utils.get_model('resnet50')
img = image_utils.open_image('../data/test_images/dogs.png', convert_mode='RGB')
image_utils.show_image(img)
probabilities = imagenet_utils.predict(model=model, images=[img])
imagenet_utils.probabilities2classes(probabilities, topk=5)
input_tensor = imagenet_utils.image2batch(img)
prediction_tensor = pytorch_utils.int2tensor(239)
results = saliency.get_image_saliency_results(model, img, input_tensor, prediction_tensor)
figure = saliency.get_image_saliency_plot(results)

Thanks for reporting the issue. We have modified setup.py to include the missing file and other issues. So if you do
pip install tensorwatch --upgrade

then you should be good to go!
I also created Colab Notebook but for some reason it is erroring out in last step. This is not reproducible in my local box with either PyTorch 1.0 or 1.1 so its strange...

Thank you, It works fine for Colab.
But I cannot comment on your local machine behavior.


Path generation for ygot.OrderedMap nodes

Sample name: Root().RoutingPolicy().PolicyDefinition().StatementAll()
example helper function signature:
func (n *RoutingPolicy_PolicyDefinition_StatementPath) Config() ygnmi.ConfigQuery[*oc.RoutingPolicy_PolicyDefinition_Statement_OrderedMap]

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

32 of 36 (88.89%)  changed or added relevant lines in 3 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.1%) to 83.844%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

pathgen/pathgen.go
28
32
87.5%

Totals

Change from base Build<PHONE_NUMBER>:
0.1%

Covered Lines:
1723

Relevant Lines:
2055

💛  - Coveralls


Activitypub / Profile Grid Conflict

Hi there,
I have built a Wordpress website using Profile Grid and have recently added ActivityPub in order to publish the unrestricted content to followers on the Fediverse. However, I am unable to find my profile/site from within Mastodon. When I navigate to the appropriate .well-known/webfinger address in my browser to check the resource, I find that the code there includes the address of the associated Profile Grid profile page ( ending in /my-profile/?uid=13 ) rather than the address of the associated wordpress author page as I believe is required.
I consulted a friend online, who said the following...
"From what I can see, ActivityPub plugin uses WordPress's built-in function get_author_posts_url I'm guessing that ProfileGrid somewhere intercepts that function call and rewrites it to use its own profile link."
Is there a work-around for this?
It may also be worth mentioning that while some of the content on the site (including each Profile Grid profile page) is restricted to logged in members, the author page I'm currently trying to follow in Mastodon displays just fine to unregistered site visitors.
All help greatly appreciated!
Many thanks,
Sam

Puuh... This is a hard one 😳
I have no idea of a simple "work-around" yet. But I will think about a solution.

Thanks Matthias. Much appreciated. Would be a shame to start over but I am keen to include federation at some level. I should mention that when users of my site post user blogs they are able to set privacy levels, determining whether their post is visible only to logged in members, friends on the site, or visible to everyone.
Technically, as every user has an associated identifier, Activity Pub should Federate their unrestricted posts. I can see that there is a User Blogs check box in the settings to allow for this. I'm not sure how this extra level of permissions might affect things but thought I should mention it.
Look forward to hearing your suggestions.
Many thanks,
Sam
Sent from ProtonMail mobile
-------- Original Message --------
On 7 Oct 2019, 14:48, Matthias Pfefferle wrote:

Puuh... This is a hard one 😳
I have no idea of a simple "work-around" yet. But I will think about a solution.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.


Making tag size larger

Hey,
Thanks for the awesome work! Is there any way to resize the tags (make them larger)?

Try changing the font-size of .bootstrap-tagsinput .tag inside your CSS

Thanks! Should have thought of it! ;)


Inaccurate logo in ASCII representation

The ASCII representation of the Docker whaletainership is missing a container:

vs

Proposed solution: Add ## to whale.

:heart: best issue of the day!

Ping @steeve :D

:laughing:


Corrected DTR ceiling

[ ] closes #xxxx
[x] tests added / passed
[ ] docs reflect changes
[x] entry in CHANGELOG.md

This corrects a mistake introduced by https://github.com/ClimateImpactLab/dodola/pull/163. The functionality to cap non-polar DTR values had an error in its implementation that lead all polar values to be modified. The tests couldn't catch this because they were also wrong, using == to compare xarray.Dataset objects.
This PR :

Corrects the boolean condition expression in the cap function to preserve polar values
Corrects the cap function test by making use of xarray.testing.assert_equals and adds an additional test case to verify that values that should not be capped (because those are not out of range) are indeed not capped.

When this merges @emileten, do you want to take this for a test with dodola:dev on larger data or should we turn around a new patched release?

@brews thanks for the review. I'd like to test it first.


iOS: Unable to select text when article is in full screen mode

To reproduce:

Open an article;
Tap the top bar to hide toolbars;

then

double-tapping to select text doesn't work; and,
long-pressing text opens up the article context menu

This is a known behavior. This is a side effect of using the context menu. I'm open to suggestions to change the behavior if you have any.

My preference would be that the text selection behaviour remains the same regardless of whether the toolbars are present.

The context menu was a requirement from @brentsimmons. I think it was the right call. I frequently use the context menu when in full screen.

The counter argument is that the context menu interferes with the system-wide text selection gestures—both double-tap and long-press.
Is it possible to keep double-tap to select text? It doesn't appear to do anything just now.

I think this is just how WKWebKit works. All we are doing is adding a UIContextMenuInteraction to it. I'd love for you to dig into it and prove me wrong.

Been thinking about this...
Maybe we could remove the context menu if we added an ellipsis (hamburger) menu in the top left. It would make the actions more discoverable and you could select text again.


teamspeak_client: specify a custom, nonfree license

Motivation for this change
It is reasonable to expect that specifying allowUnfree = false is sufficient to ensure a system comprising only libre software.  Previously, teamspeak_client would happily build even though it is clearly unfree per the usual definition, however.
cc @Jookia raised this issue on IRC.

Good point, thanks for the patch. It looks good to me.
Reminds me that the client could use a small version bump. :)


Multi Cluster runtime

This PR adds runtime support for multi-cluster systems like Occamy
Changelog

occamy: add new startup routine for occamy
bootdata: add information about number of cluster, tcdm size & offset
occamy: stack for each cluster is calculated based on cluster_id
barrier: add software barrier for cluster and global synchronization
occamy: trap manager core 0 in bootrom
test: modify printf_fmt.c test for multicluster
test: add new multi-cluster.c test
barrier: move barrier_reg_ptr to team struct
runtime: align runtime for snitch_cluster and occamy, currently named start_occamy.[c|S]
occamy: auto-generate bootdata.cc from config file

@fischeti if you agree with the changes in d115508 we can merge +1

LGTM! Let's merge it


fix(region): fix change config forecast

这个 PR 实现什么功能/修复什么问题:
fix(region): fix change config forecast

是否需要 backport 到之前的 release 分支:
release/3.6
/cc @zexi
/area region

Codecov Report

Merging #9486 (2dc5b47) into master (15e1058) will decrease coverage by 1.94%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master   #9486       +/-   ##
==========================================
- Coverage    5.92%   3.97%    -1.95%
==========================================
  Files         842     170      -672
  Lines      130667   25463   -105204
==========================================
- Hits         7736    1012     -6724
+ Misses     122231   24337    -97894
+ Partials      700     114      -586

Flag
Coverage Δ

aFlag
3.97% <ø> (-1.95%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

pkg/multicloud/aws/resource_tag.go

pkg/compute/models/networkresource.go

pkg/monitor/models/helper.go

pkg/compute/guestdrivers/google.go

pkg/multicloud/aws/vpc.go

pkg/mcclient/modules/monitor/suggestsysrule.go

pkg/compute/models/guest_queries.go

pkg/apis/input.go

pkg/compute/models/dbinstance_secgroups.go

pkg/appsrv/send.go

... and 661 more

Continue to review full report at Codecov.

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

/lgtm
/approve


Set User Class on Boot

For most of the Rails boot process, an app running solidus_auth_devise believes that its user class is whatever is configured in the config/spree.rb initializer. However, if solidus_auth_devise is installed, that is changed after most things have been configured.
It need not be this way: If we want this gem to set a default, we should set it really early on, not in one of the last initializers to run (they also run alphabetically, so solidus_auth_devise initializers run quite late).
Specifically, for using the new patch mechanism in https://github.com/friendlycart/flickwerk, Spree.user_class needs to be correct by the time the Rails finisher runs (when the setup_main_autoloader initializer runs).
Checklist
Check out our PR guidelines for more details.
The following are mandatory for all PRs:

[x] I have written a thorough PR description.
[x] I have kept my commits small and atomic.
[x] I have used clear, explanatory commit messages.

The following are not always needed:

📖 I have updated the README to account for my changes.
📑 I have documented new code with YARD.
🛣 I have opened a PR to update the guides.
✅ I have added automated tests to cover my changes.
📸 I have attached screenshots to demo visual changes.

Specs fixed by https://github.com/solidusio/solidus_auth_devise/pull/253


Revert "[6.0 🍒][Dependency Scanning] Specify Source Locations For Missing Module Dependencies"

Reverts apple/swift#73819. Speculative revert---we have been seeing failures since this landed and I want to determine if it's triggering the issue.

@swift-ci please test

I don't think we'll need this, because I believe I found this issue (https://github.com/apple/swift-driver/pull/1620 wasn't merged but is needed).

We don't need those


"Preset" codemods that aren't tied to a specific module or version.

Skip a test sounds like a good idea. But Remove white space is already done by eslint and prettier, do we really need them?

Hey @rajasegar! Hahah probably not, these are just examples from the top of my head!
I'm thinking this will realistically be codemods that are generic in that they can be applied to any code base and organised into thematic groups like for example "imports" might have "sort imports", "require-to-import" something like that. But that's not to say I'm going to build them, but more so that I want to provide a way for these codemods to be publishable with this project 😄.
Hope that makes sense! Thanks for showing interest!

This functionality is available in 0.2.1


Fix two bugs found in preprod provisoning

/etc/sv directory is not being created, or not being created in the right order, causing the runit install to fail.

the bendo dternity share for the proper environment needs to be parametize- see also JIRA
https://jira.library.nd.edu/browse/BENDO-3

Also set the cache size to something larger than the 100MB default. Maybe 50 GB? I don't know how much space is on the drive. Use the --cache-size command line option.

Actually, 50 GB is for staging. For pprd, maybe 500 GB. I would like a few TB for production, whenever we get there.

But we only have 60 GB or so in fedora at the moment.

set bendo_cache_to 50000 MB (50GB) staging
500000 MB (500GB) preprod
1500000 MB (1.5 TB) prod


RC2 adding/appending header in middleware throws exception

This line of code
context.Response.Headers.Add("TestHeader", "true");

in this file is throwing this exception:
Exception thrown: 'System.InvalidOperationException' in Microsoft.AspNetCore.Server.Kestrel.dll

Simplified Example

Where is the real exception and the stack trace? You can't add to the headers after the response has been written to (that's the thing you're likely running into).

Ahh, you are correct once again haha!
I guess I was a bit confused as this exact middleware works in the "old" stack, and I think it may have worked in older versions of dotnet core since this guide writes essentially the same middleware and calls the await _next.Invoke(context) line in the same place as I was doing.
By moving the line await _next.Invoke(context) to after the code where I update the headers, it now works.
My only concern is that now my middleware may not have "final say" as to what the header values are since it may not be the last to update them.

@Sharpiro you can work around this by handling OnStarting in your middleware: https://github.com/aspnet/HttpAbstractions/blob/dev/src/Microsoft.AspNetCore.Http.Abstractions/HttpResponse.cs#L73.
That way you get a chance to handle it no matter when the response gets flushed. The cookie middleware uses this to set cookie headers at the "right" time (before the response is flushed).
ASP.NET 4.x used to buffer the entire response body and we don't do that anymore.

thanks, this worked well.


previous_def without args simply forwards local variables with the same name as the args

def foo(z)
  z
end
def foo(z)
  ->(z : Int32) { z + previous_def }
end
p foo(2).call(3)

I expect it to output 5 but it prints 6. As the second z variable is simply shadowing the method argument, instead of really editing it. previous_def should really take the arguments, even if there is no syntax to access them at the current scope.

Indeed, though the workaround is very simple so I'll probably take my time to fix this :-)

However... https://carc.in/#/r/12ae
This is Ruby:
class Foo
  def foo(x)
    p x
  end
end

class Bar < Foo
  def foo(x)
    x = 10
    super
  end
end

Bar.new.foo(20)

It prints 10, which means that super effectively forwards the changed x, not the original x. If Ruby does it there must be a reason (maybe simplicity, to not have to store a copy of every method argument). Or maybe do you can change one argument and forward them all, with just one changed.
So now I feel inclined not to change this behavior.

But
class Foo
  def foo(x)
    p x
  end
end

class Bar < Foo
  def foo(x)
    [10].each do |x|
      super
    end
  end
end

Bar.new.foo(20)

prints 20. In your sample @asterite the scope is not changed so 10 is the right answer.

Hmmm... then I think it's really hard to implement with syntax sugar. We'd have to store the arguments in a separate, temporary variable, and every assignment to it, that isn't shadowed by a block variable, needs to be reassigned as well. And then super passes those args.
I'd prefer to simply say that super inserts the arguments, for example super(x) in the case above, and if x was reassigned or shadowed then, well, it gets that value. In any case the workaround (or the proper way to do it) is to use other variable names to avoid confusion.

In any case the workaround (or the proper way to do it) is to use other variable names to avoid confusion.

Can we have the parser spit out some sort of warning in those cases when compiling? That way it will not be a surprise.
Thanks :smile:

@luislavena I don't believe warnings are useful, and the compiler has none right now. We have these options:

Disallow shadowing
Force the user to explicitly forward arguments in super and previous_def
Leave things as they are

We could do 2, I don't think super and previous_def are used that much so explicitly forwarding args will be a bit more cumbersome, but always explicit. Otherwise I'd do 3 :-)

I think explicitness wins over magic on what-the-heck moments. Of course,
that might be tedious to some. So will shut up on my personal taste for now
😁
Sorry for top posting, sent from mobile.
On Jun 24, 2016 17:11, "Ary Borenszweig"<EMAIL_ADDRESS>wrote:

@luislavena https://github.com/luislavena I don't believe warnings are
useful, and the compiler has none right now. We have these options:

Disallow shadowing
Force the user to explicitly forward arguments in super and
previous_def
Leave things as they are

We could do 2, I don't think super and previous_def are used that much so
explicitly forwarding args will be a bit more cumbersome, but always
explicit. Otherwise I'd do 3 :-)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/crystal-lang/crystal/issues/2894#issuecomment-228372594,
or mute the thread
https://github.com/notifications/unsubscribe/AAAQVuz-sGQwc1guKshCk2goQGQKGO-Dks5qO_OkgaJpZM4I7wGE
.

IMO, always pass the same argument (not changed) while super and previous_def got no arguments is better.
and it will be like this
def foo(z)
  z
end
def foo(z)
  ->(z : Int32) { z + previous_def }
end
p foo(2).call(3) #=> 5

class Foo
  def foo(x)
    p x
  end
end

class Bar < Foo
  def foo(x)
    x = 10
    super
  end
end

class Bar2 < Foo
  def foo(x)
    [10].each do |x|
      super
    end
  end
end

Bar.new.foo(20) #=> 20
Bar2.new.foo(20) #=> 20

And if we want new value to be argument in @asterite's code, we can pass new variable manually
class Bar < Foo
  def foo(x)
    x = 10
    super x
  end
end

Bar.new.foo(20) #=> 10

Even though I like the idea of static analysis to help out in the form of warnings (though perhaps only when passing "--gimme-warnings" or such. I think @asterite proposition (2) - require explicit forwarding is the cleanest in the long run.
Another, but very breaking option, is that args-variables are always non-assignable, so if you'd like a modified value you'd use a new local variable at all times.

Revisit, after lots of sleeping on it. My bet is definitely on 2.

Closing stale discussion. There where some votes for solution 2. But the absence of any activity in the last 4+ years shows a lack of interest in changing this. Apparently, it does not pose a relevant problem in practice. Otherwise there would have been more complaints by now. It's probably fine to accept the somewhat surprising behaviour for the few practical sitations where this appears. The alternative would be a huge annoyance for every usage of super and previous_def.


re-revert #4170 to prepare next major

reverts #4170 again, as discussed in https://github.com/symplify/symplify/issues/4169#issuecomment-1154143239

You can replace the single usage by  "parent" string.

args. I guess our own checks bite us :-).
could you push it over the finishing line?


[Removal]: Application for removal of restrictions

Hotspot Name
Acrobatic Cloud Butterfly
Hotspot b58 Address
112Mf9KqCXf9Zug6nexTWgvv7xUUaXWdKpfts7pvaeVUva3Uphv
Discord Handle
No response
Hotspot Manufacturer
bobcat
Removal Reason
Real deployment, please remove
Modifications
No
Extra forwarders
No
Extra antennas
No
Additional Information
Application for removal of restrictions
why no one handles the delete request ，
I have been really deploying since the beginning. Please check my activation date. No one knew about cheating at that time. Please remove it

denied in
https://github.com/helium/denylist/issues/7318
https://github.com/helium/denylist/issues/7427

在#7318 #7427中被拒绝

All connected to this hotspot are real deployments. Please delete them from the blacklist.
Don't misunderstand me again

112Mf9KqCXf9Zug6nexTWgvv7xUUaXWdKpfts7pvaeVUva3Uphv

This photo matches to the satellite photo of the asserted location

https://www.google.com/maps/@30.2205288,120.4931105,1389m/data=!3m1!1e3

So, 2 out of 3 that you've provided so far I can make a match with (3rd is unclear as per comment in that issue).
I'll have a look at the whole cluster and if necessary recommend for wider removal.

You have has flagged up 3 hotspots for removal, which were denied in Cluster A in
https://github.com/helium/denylist/issues/7318
all 3 are owned by the wallet 14ZFCCAxjR4TYjZevCRR1xoWTPB9exmcr1nciTH6HDBR5bLLmix
this wallet has 16 hotspots that were denied in #7318
Of the 3 flagged up with photos provided, 2 out of 3 have a verified match to the asserted location (in this issue and #7318  - suggesting they really are located where they are asserted. 1 out of 3 is unclear.
Given 2 are verified by photo, UNdenying the whole cluster could be considered. However, there are a few strange things:

At 3 witness hops, the cluster only witnesses a few around it and another tight cluster further away. In that, it does not witness any of the other hotspots asserted in the city. It is likely that many of these are spoofed however, but all of them?

8 of that wallet's hotspots are listed on nearly sequential IP addresses, which can be an indicator of gaming.

So, I recommend UNdenylisting the two that have verified locations via photo:
11QBgLhX9VubL5Mkppn2MDA96CUTNiemaBwzV5LZazoyvM3Mraa
112Mf9KqCXf9Zug6nexTWgvv7xUUaXWdKpfts7pvaeVUva3Uphv
Others could be considered if more evidence is provided.

您已标记 3 个要删除的热点，这些热点在 #7318的集群 A 中被拒绝
所有 3 个都归钱包 14ZFCCAxjR4TYjZevCRR1xoWTPB9exmcr1nciTH6HDBR5bLLmix 所有
这个钱包有 16 个热点，在#7318中被拒绝
在标记了提供照片的 3 个中，3 个中的 2 个与断言的位置（在本期和#7318 中 - 表明它们确实位于它们断言的位置）经过验证匹配。三分之一的位置不清楚。
鉴于 2 已通过照片验证，可以考虑不否认整个集群。但是，有一些奇怪的事情：

在 3 个见证跃点处，集群只见证了它周围的几个，而另一个紧密的集群则更远。在那方面，它没有看到该市声称的任何其他热点。然而，其中许多可能是被欺骗的，但所有这些都是？

该钱包的 8 个热点列在几乎连续的 IP 地址上，这可能是游戏的一个指标。

因此，我建议将已通过照片验证的两个位置取消拒绝： 11QBgLhX9VubL5Mkppn2MDA96CUTNiemaBwzV5LZazoyvM3Mraa 112Mf9KqCXf9Zug6nexTWgvv7xUUaXWdKpfts7pvaeVUva3Uphv
如果提供更多证据，可以考虑其他人。

您已标记 3 个要删除的热点，这些热点在 #7318的集群 A 中被拒绝
所有 3 个都归钱包 14ZFCCAxjR4TYjZevCRR1xoWTPB9exmcr1nciTH6HDBR5bLLmix 所有
这个钱包有 16 个热点，在#7318中被拒绝
在标记了提供照片的 3 个中，3 个中的 2 个与断言的位置（在本期和#7318 中 - 表明它们确实位于它们断言的位置）经过验证匹配。三分之一的位置不清楚。
鉴于 2 已通过照片验证，可以考虑不否认整个集群。但是，有一些奇怪的事情：

在 3 个见证跃点处，集群只见证了它周围的几个，而另一个紧密的集群则更远。在那方面，它没有看到该市声称的任何其他热点。然而，其中许多可能是被欺骗的，但所有这些都是？

该钱包的 8 个热点列在几乎连续的 IP 地址上，这可能是游戏的一个指标。

因此，我建议将已通过照片验证的两个位置取消拒绝： 11QBgLhX9VubL5Mkppn2MDA96CUTNiemaBwzV5LZazoyvM3Mraa 112Mf9KqCXf9Zug6nexTWgvv7xUUaXWdKpfts7pvaeVUva3Uphv
如果提供更多证据，可以考虑其他人。

You have has flagged up 3 hotspots for removal, which were denied in Cluster A in #7318
all 3 are owned by the wallet 14ZFCCAxjR4TYjZevCRR1xoWTPB9exmcr1nciTH6HDBR5bLLmix
this wallet has 16 hotspots that were denied in #7318
Of the 3 flagged up with photos provided, 2 out of 3 have a verified match to the asserted location (in this issue and #7318 - suggesting they really are located where they are asserted. 1 out of 3 is unclear.
Given 2 are verified by photo, UNdenying the whole cluster could be considered. However, there are a few strange things:

At 3 witness hops, the cluster only witnesses a few around it and another tight cluster further away. In that, it does not witness any of the other hotspots asserted in the city. It is likely that many of these are spoofed however, but all of them?

8 of that wallet's hotspots are listed on nearly sequential IP addresses, which can be an indicator of gaming.

So, I recommend UNdenylisting the two that have verified locations via photo: 11QBgLhX9VubL5Mkppn2MDA96CUTNiemaBwzV5LZazoyvM3Mraa 112Mf9KqCXf9Zug6nexTWgvv7xUUaXWdKpfts7pvaeVUva3Uphv
Others could be considered if more evidence is provided.

Continuous IP does not mean cheating. Since independent IP was required to provide better coverage in the past, I asked network providers to install the network at the same time, so their issued IP is continuous, and these IPs are deployed on the spot，
Why do you have questions? And the remote witness you mentioned, which doesn't really mean that it is also a real deployment. What I want to say is that this distance can really witness each other. You can check the satellite address of each other. If you don't believe me, I invite you to Hangzhou, China, and I will show you the real deployment,

Old Champagne Porcupine #7660
Amusing Brunette Perch#7676
Sweet Umber Newt#7660
I have already provided five. What's wrong with these three? Please hurry up. If there are so many real deployments for several clusters, do you still need to confirm this?

For the IP question you mentioned, I will provide you with a picture. The one circled is the independent IP router of the network provider. As long as it is available, it will be installed separately in each place. Although the IP is continuous, it is provided by the supplier, and each IP is deployed in the real location. Therefore, the continuous IP can not prove that it cheats, which is not a problem at all
Therefore, please remove the entire mutual witness cluster from the blacklist # 7318 Cluster A as soon as possible, so as not to cause innocent losses to me and other fans of the real deployment, and not to make helium fans sad

You have has flagged up 3 hotspots for removal, which were denied in Cluster A in #7318
all 3 are owned by the wallet 14ZFCCAxjR4TYjZevCRR1xoWTPB9exmcr1nciTH6HDBR5bLLmix
this wallet has 16 hotspots that were denied in #7318
Of the 3 flagged up with photos provided, 2 out of 3 have a verified match to the asserted location (in this issue and #7318 - suggesting they really are located where they are asserted. 1 out of 3 is unclear.
Given 2 are verified by photo, UNdenying the whole cluster could be considered. However, there are a few strange things:

At 3 witness hops, the cluster only witnesses a few around it and another tight cluster further away. In that, it does not witness any of the other hotspots asserted in the city. It is likely that many of these are spoofed however, but all of them?

8 of that wallet's hotspots are listed on nearly sequential IP addresses, which can be an indicator of gaming.

So, I recommend UNdenylisting the two that have verified locations via photo: 11QBgLhX9VubL5Mkppn2MDA96CUTNiemaBwzV5LZazoyvM3Mraa 112Mf9KqCXf9Zug6nexTWgvv7xUUaXWdKpfts7pvaeVUva3Uphv
Others could be considered if more evidence is provided.

I can confirm that this cluster should be a real deployment. I can witness with it that this cluster is also a victim. Although this cluster is not mine, you can also check it together

These two
11QBgLhX9VubL5Mkppn2MDA96CUTNiemaBwzV5LZazoyvM3Mraa
112Mf9KqCXf9Zug6nexTWgvv7xUUaXWdKpfts7pvaeVUva3Uphv
11nWxXU88YQrgBsiTMc7W4NdcDLgDttmrvC1ychZYvfLA4tGXVR (#7660 )
are matched and I'd recommend for UNdenying
As I said in #7318
11iV4gUCQGkWorQvmaUeGxySqh2tQzCwXwQs3KndmYqgYnpRPGz
Old Champagne Porcupine
The photo is unclear - it is hard to match it to the satellite photo
But overall, I think this is probably good enough to undeny cluster A.
That there are so few other hotspots your cluster witnesses is strange, but could be that you are the only real hotspots in the city.


Enphase multiple batteries - jq: too many results

Describe the bug
After installing 3 enphase solar batteries and reconfiguring evcc with the new controller, I see all the solar production and consumption data, but the battery SOC is not available. Checking through the logs, I can see evcc polls and receives the battery data from the IQ controller (GET https://<IP_ADDRESS>/ivp/ensemble/inventory), but it looks like evcc is expecting to see only 1 battery, producing the following error logs:
[site  ] ERROR 2024/11/14 16:41:29 battery 1 soc: jq: too many results
[site  ] DEBUG 2024/11/14 16:41:29 battery soc: 0%
[site  ] DEBUG 2024/11/14 16:41:29 battery power: 0W
Steps to reproduce

configure enphase batter meter
configure site meters
restart evcc

...
Configuration details
network:
  schema: http
  host: evcc.local
  port: 7070

interval: 60s # control cycle interval

sponsortoken: <snip>

log: debug
levels:
  site: debug
  lp-1: debug
  lp-2: debug
  cache: error
  db: error

meters:
  - name: enphase_pv
    type: template
    template: enphase
    usage: pv
    host: <IP_ADDRESS>
    token: <snip>
  - name: enphase_grid
    type: template
    template: enphase
    usage: grid
    host: <IP_ADDRESS>
    token: <snip>
  - name: enphase_battery
    type: template
    template: enphase
    usage: battery
    host: <IP_ADDRESS>
    token: <snip>
    capacity: 15

chargers:
  - name: TeslaCharger
    type: template # Wallbe charger
    template: twc3
    host: <IP_ADDRESS>

vehicles:
  - name: ZROGAS
    type: template
    template: tesla
    icon: car
    commandProxy: http://<IP_ADDRESS>:8080
    accessToken: <snip>
    refreshToken: <snip>
    capacity: 78 # kWh
    vin: <snip>
    mode: pv

site:
  title: Home # display name for UI
  meters:
    grid: enphase_grid # grid meter
    pv: enphase_pv
    battery: enphase_battery
  residualPower: 0
  maxGridSupplyWhileBatteryCharging: 0

loadpoints:
  - title: Garage # display name for UI
    charger: TeslaCharger # charger
    mode: pv
    vehicle: ZROGAS
    phases: 3
    minCurrent: 6
    maxCurrent: 16
    priority: 0
    soc:
      poll:
        mode: connected
        interval: 5m
      estimate: true
    enable:
      delay: 5m
      threshold: 0
    disable:
      delay: 3m
      threshold: 0
    guardDuration: 5m

tariffs:
  currency: AUD
  grid:
    type: fixed
    price: 0.3828 # EUR/kWh
    zones:
      - days: Mo-Fr
        hours: 0-6
        price: 0.0799
      - days: Mo-Fr
        hours: 11-14
        price: 0.00
      - days: Mo-Fr
        hours: 15-21
        price: 0.75
      - days: Sa,So
        hours: 0-6
        price: 0.0799
      - days: Sa,So
        hours: 11-14
        price: 0.00
  feedin:
    type: fixed
    price: 0.03 # EUR/kWh

  co2:
    type: template
    template: electricitymaps-free
    token: <snip>
    zone: AU-NSW

mqtt:
  broker: <IP_ADDRESS>:1883
  topic: evcc
  user: evcc
  password: <snip>

influx:
  url: http://<IP_ADDRESS>:8086
  database: evcc
  user: evcc
  password: <snip>

  services:

Log details
[main  ] INFO 2024/11/14 17:13:56 evcc 0.131.5 (6836749c)
[main  ] INFO 2024/11/14 17:13:56 using config file: /etc/evcc.yaml
[db    ] INFO 2024/11/14 17:13:56 using sqlite database: /var/lib/evcc/evcc.db
[mqtt  ] INFO 2024/11/14 17:13:57 connecting evcc-829667239 at tcp://<IP_ADDRESS>:1883
[mqtt  ] DEBUG 2024/11/14 17:13:57 tcp://<IP_ADDRESS>:1883 connected
[main  ] INFO 2024/11/14 17:13:57 listening at :7070
[lp-1  ] WARN 2024/11/14 17:13:58 poll mode '{connected 5m0s}' may deplete your battery or lead to API misuse.
Linux
Nightly build

[X] I have verified that the issue is reproducible with the latest nightly build

Version
evcc version 0.131.5 (6836749c)

The template's jq query needs be updated and a battery number added. Happy to take a PR.

Could the issue be the 2 top level arrays of ENPOWER and ENCHARGE? Both return devices, only ENCHARGE is will return percentFull values.
Is the intended bahaviour to average the percentFull values? I'm curious as the log files seems to indicate battery numbers"
ERROR 2024/11/14 17:14:05 **battery 1 soc**: jq: too many results [site  ] DEBUG 2024/11/14 17:14:05 battery soc: 0% [site  ] DEBUG 2024/11/14 17:14:05 battery power: 0W
I'll try playing around with a custom meter and the jq

Fixed in a custom meter with:
jq: '[.[].devices[] | select(.percentFull != null) | .percentFull] | add / length'

Every battery unit should be added as own device for configuration. evcc will sum up the measurands internally where required.

Bitte nicht komplizierter machen als notwendig.

Hier fehlt nämlich derzeit die Kapazität der einzelnen Module, so dass der SoC bei unterschiedlichen Speichereinheiten falsch wäre.

Darum geht es hier aber nicht. Bitte nicht alles durcheinander mischen. Bei Stapelspeichern passt das wunderbar.

Das sind mwn. alles einzelne Speichereinheiten mit AC-Anschluss, keine gestapelten DC-Module.

Yep, hat mit diesem Issue aber trotzdem nix zu tun 😉

Struggling to follow, maybe there is 2 things here:
#1 is the bug/enhancement I've seen and the solution to the problem - working on a PR for this.
#2 is a feature request to record, track and report on each battery individually. I see this as a benefit too given I have 3 batteries connected to 3 different phases that all discharge at separate rates based on which household circuits are connected to each phase.
Happy to support and contribute to the latter, in the mean time I believe I've identified a solution for the first issues and will request PR.

Closed in a9d9565e62c05842c097a983bf8901423fc4d55f


Going 'back in time'

Just getting my head around this package, its great!
Is it easy enough to recreate a state at a certain point in time? Eg using the bank example is there a simple way to show an account balance on xxx date?

The way I solved this for my simple task list app was to make a new "HistoryProjector" which will only process events up to a certain point. It's not perfect, but it works for what I wanted it to do: https://github.com/36864/Event-Sourced-Task-Lists/blob/master/app/Projectors/HistoryProjector.php
Earlier I had made a PR here to pass an upper limit to ReplayEvents, but issues surfaced regarding user interaction with an application in "history" mode.

Cool - I'll have a play with that approach.
Thank you.


Move illustration of Bayer & Luetticke invocation of DCT & fixed copula to DemARK repository

See discussion in PR #344 for context.

Actually, it should move to REMARK, because it needs a file structure (and because it is about reproducing the results of someone else's paper)

closing as duplicate of #531