How to interpret single JSON object as an array with one element?

In Sonic how to handle the json format like below with one struct?
Format A (JSON array with two element):
{"name":"xiao","address":["road1","road2"]}

Format B (JSON object, yes I know it looks "wrong" but it's what I'm given):
{"name":"xiao","address":"road1"}

Example code:
package main

import (
	"fmt"
	"strings"

	"github.com/bytedance/sonic/decoder"
)

type Person struct {
	Name    string
	Address []string
}

func testDecode1() {
	var o Person
	var r = strings.NewReader(`{"name":"xiao","address":["road1","road2"]}`)
	var dec = decoder.NewStreamDecoder(r)
	dec.Decode(&o)
	fmt.Printf("%+v\n", o) // {Name:xiao Address:[road1 road2]}
}

func testDecode2() {
	var o Person
	var r = strings.NewReader(`{"name":"xiao","address":"road1"}`)
	var dec = decoder.NewStreamDecoder(r)
	dec.Decode(&o)
	// expected resoult: {Name:xiao Address:[road1]}
	// actual resoult: {Name:xiao Address:[]}
	fmt.Printf("%+v\n", o)
}

func main() {
	testDecode1()
	testDecode2()
}

similar like : https://stackoverflow.com/questions/17003823/make-jackson-interpret-single-json-object-as-array-with-one-element

not supported by std. But u can implement a work-around logic through json.Unmarshaler:

Define a type ObjectOrSlice
Implement ObjectOrSlice.UnmarshalJSON() like this: when the first received byte is [, calling Unmarshal(input, &ObjectOrSlice); when is not [, calling unmarshal(input, &Object[0])


Add mqtt support

Hello! Would it be possible to add mqtt support for us that use something other than home assist?

ESPHome has an extensive support for MQTT so it is absolutely possible to configure the p1-reader to publish MQTT events instead of using the Home Assistant API. This would not require any changes to the code, only configuration changes in the yaml file: https://esphome.io/components/mqtt.html

Sounds awesome! Will have a look.

@calania Please let us know your findings! I'm using openhab so I'm also very interested in this 😁

@ulfwin Sadly I haven't received my meter yet but I will report back once I get it!


Add support for Apple WatchOS

Hi, I am hoping to add Apple WatchOS compile targets and these are prerequisite changes.
Many thanks!
Vlad.

Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @Amanieu (or someone else) soon.
Please see the contribution instructions for more information.

This is the main PR: https://github.com/rust-lang/rust/pull/94736

@Amanieu updated as you suggested, sorry for the delay.

@bors r+

:pushpin: Commit 68c988ff64041b3a431d50e41d9dd1bab972b945 has been approved by Amanieu

:hourglass: Testing commit 68c988ff64041b3a431d50e41d9dd1bab972b945 with merge f0f4b689906862bf74297042022c20ada7274b71...

:sunny: Test successful - checks-actions, checks-cirrus-freebsd-11, checks-cirrus-freebsd-12, checks-cirrus-freebsd-13
Approved by: Amanieu
Pushing f0f4b689906862bf74297042022c20ada7274b71 to master...


swagger-ui.html not available in when caching of static resources disabled in dev mode

In a way it is similar to #1460
Everything works fine when I am using default (prod) profile for application, however in development mode I would like to prevent static resources from being cached and want to see changes the moment I made them. So, in application-dev.properties file I specify
spring.resources.static-locations=file://${user.dir}/src/main/resources/static/
spring.resources.cache-period=0
endpoints.sensitive=false
Then swagger-ui.html become unavailable which is inconvenient.
Is there a way to continue serving swagger-ui.html while disabling caching for static resources?

Its not serving it because you explicitly told it not to serve it. Not because of caching
spring.resources.static-locations=file://${user.dir}/src/main/resources/static/ is incorrect. It overrides the default behavior to only serve files in that location. So the swagger-ui web jar will be ignored.


Expose only the parser

Hey man, it gonna be great if I can just pass the Linkedin HTML to your code and it return the page parsed.
I already have all the puppeteer stuff in another microservice, you know?
Thanks.

great idea, the API needs to change soon anyway due to the addition of company parsing, let's put that idea on the roadmap as well, thanks!


Change comments on Redshift

🚀 Deployed on https://62e1b861f61e0e005d57b1f5--cozy-fox-0defec.netlify.app


Proposed method "FindDevicesByProduct"

Hi, first of all congratulations for the project.
I'm using it right now and I miss a method to search devices by product (string). In my opinion, it will be great for the API have such facilitator method.
If you agree, I can personality take care of this :smile:

I didn't need it yet but if you can provide some code I'll be happy to merge it (Though I'm not 100% sure that all three OS will provide the same strings.)
Thanks for the feedback.

PR created #7

Merged ;)


[blocked] get boolean schemas working

Boolean schemas only work for additionalProperties due to a bug in swagger parser
I filed a bug with the swagger parser project on it here: https://github.com/swagger-api/swagger-parser/issues/1770
Paths forward:

wait until the bug is fixed
preprocess all schemas in the openapi spec and replace booleans with expanded schemas with the same meaning

this is difficult, I do not plan on doing it at this time

Closing this because it is stale


[device support request]  Support for Smartmi Radiant Heater Smart Version (zhimi.heater.za2)

Hello.
Is it possible to use miio with zhimi.heater.za2 ?
https://xiaomi-mi.com/news-and-actions/review-zhimi-smartmi-electric-heater-/
I have tried to follow the instrucctions here, https://github.com/aholstenson/miio/blob/master/docs/protocol.md to sniff the trafic, but wireshark doesnt get udp trafic from the heater.
I have retreived the token, and the miio inpect return this:
Device ID: 124088314
Model info: zhimi.heater.za2
Address: <IP_ADDRESS>
Token: ---------- via stored token
Support: At least generic
Type info: miio
Capabilities:
Firmware version: 2.0.5
Hardware version: esp32
MCU firmware version: 0020
WiFi firmware version: v3.1.4-56-g8ffb04960
Remote access (Mi Home App): Maybe

miio protocol call idOrIp bin .......................


[INTG-1664] Config-path flag is not working

I'm still unable to figure out the exact reason why it is not working with the previous code.

I'm still unable to figure out the exact reason why it is not working with the previous code.

was it working before you made your change?

I'm still unable to figure out the exact reason why it is not working with the previous code.

was it working before you made your change?

No. It was not working.

No. It was not working.

Maybe it was missing the change you made 😄


Where should models, geometry, and other assets be installed?

This has come up because it's not clear that, on Macs, models, geometry, and example scripts belong inside the /Applications/OpenSim... folder. We have previously discussed potentially putting these resources/assets in ~/Documents.
Some thoughts from #26:

Geometry & Models now live in top level, could go into Assets folder or follow layout per James or ...
We need to decide if assets are kept read only or hidden from users and they need to make a copy to modify Scripts, should they go with assets or into sdk folder along with API programs?

We should also consider consistency between Macs and Windows.

@chrisdembia Do you think this should be figured out before public Beta?

Getting this right might require some user testing, so perhaps it would be ideal to include this in the beta but I feel like that would delay the beta too much. My sense is that this would take some time to implement, and I think there is still some discussion required to figure out the right way to do this.

Agreed. I think we should try the beta with what we have now until we find out the shortcomings so we have a good sense of the issues involved. I'll remove the Beta label but leave as 4.0 milestone if you agree.

Sounds good.

Fixed by PR #504, verify and close on next Mac build

This is fixed on my mac ... closing


dont work

CAN by Sandeep Mistry work fine! But your does not

But your does not

Good day @DxrMorgan
Could you clarify what exactly doesn't work in your case?
The code doesn't compile or there is no sending to the CAN bus or the sending goes, but the frame is incorrect?
I also have some difficulties with the operation of this code on the STM32F411 and am looking for possible solutions.


node_modules_local folder is not respected

Description
I'm using Kotlin to compile a react-native application to javascript. Currently, the application is outputting several javascript files/libs to a folder in the react-native project folder.
The compiled js files find the other files/libs that it outputs by using common js, i.e. require('<lib name>)'. I was solving this with metro, by adding local modules in the node_modules_local folder, via something that looks like this:
./node_modules_local/kotlin/package.json
{
  "main": "../../lib/kotlin.js",
  "name": "kotlin",
  "version": "1.0.0"
}

It appears though that haul is only looking for modules inside of the node_modules folder, and by copying that local module there, it works.
Is this a bug, or is there a way that I should be telling webpack to look in that folder for modules as well?

It's a Webpack thing. You need to tell webpack where your modules will be: https://webpack.js.org/configuration/resolve/#resolvemodules
Use transform function in haul.config.js to modify webpack config.


:sparkles: dismissal of incidents

Tried to capture the changes across the projects, keeping the logic for dismissal in the analyzer and adding the UI/UX for how a user could use this feature

I'm genuinely curious how much value we would "lose" by simply allowing users to dismiss at the rule level. This may be a declaration of ignorance but it isn't immediately obvious scenarios where a particular rule generates issues that must be fixed at the same time as ones that don't need to be addressed.

You know, this is a good question that I don't know if I have an answer too.
One thing that I was thinking of is work at the lowest level to give users the most flexability, and we could add a "bulk" update based on ruleID as a follow up. Now this doesn't mean that it is correct by any stretch of the imagination.
Something that I was thinking about was a use case like local-storage. They are mandatory issues, that tell you to fix something, but let's say you have two use cases for local storage. In one use case, you are using a local file for configuration, this would most likely be a configmap in k8s and still use local storage. But let's say that you are also using a cache of data over local storage, this probably should be solved.
So for the tackle test app case, you probably across the entire portfolio want to disable that particular incident for the application config, because you plan to solve that with a configmap across the entire portfolio.
Just a thought though, wondering if that even makes sense.

I wonder if we could perform the dismissing/filtering as a post-analysis step. My argument for this perspective is that I view this concern as a purely presentation layer concern. That is, at the analyzer level, these are absolutely still incidents; they just happen to be ones we don't want to see in analysis reports in the Konveyor UI or static-report.

I agree they are still incidents, but because we have two layers (and potentially more with the specific language builds) doing this, I figured two things:

That adding it into the analyzer means a single implementation that everyone gets to use.
Making it a first class citizen (like we did with insights for instance) gives the output of the analyzer more structure to get what you really want. Think about the Kai case, where they really just use the output of the analyzer. If in a company they want to ignore certain specific incidents (say similar to the local storage outlined above) then you probably want this to live in the analyzer.

The analyzer could do this as a post process OR it could just add a field on the incidents instead of making a whole new list. I leaned to the whole new list because it "feels" like something you would want to see at the top level. I could be convinced that it should be at the lower level and just be a field on the incident, but I can't think of a compelling reason at the moment.
Does that make sense? Should I add any of this to the enhancement?


Cannot find module 'react-dom'

Hello folks, when I install this package and run my project (react 0.13.3) I get the following error:

module.js:474
throw err;
^
Error: Cannot find module 'react-dom'
at Function.Module._resolveFilename (module.js:472:15)
at Function.Module._load (module.js:420:25)
at Module.require (module.js:500:17)
at require (internal/module.js:20:19)

I guess line 15 of the google_map.js file is causing this:
var _reactDom = require('react-dom');
Any clues how I should fix this? Thanks!

It's on you to install react and react-dom npm packages.
Also looks like it's needed to add react-dom into peer dependencies in this lib https://github.com/istarkov/google-map-react/blob/master/package.json#L40

Thanks. I understand that I may be doing something silly here, and I have of course installed react-dom, but nothing seems to work. I have actually tried all the fixes that I could come up with (e.g. adding packages, deleting node_modules and re-running npm install, etc.), but I always get a module-related error.
In particular, I am not sure why npm install google-map-react --save doesn't automatically install of all its dependencies (including react-dom).
FYI, after manually installing react-dom:
npm install react-dom --save
I get this error:
module.js:474
throw err;
^
Error: Cannot find module 'react/lib/ReactComponentTreeHook'
at Function.Module._resolveFilename (module.js:472:15)
at Function.Module._load (module.js:420:25)
at Module.require (module.js:500:17)
at require (internal/module.js:20:19)


Surveys: Add role to allow multiple survey owners

@rovats This change will add/dupe the owner_id field from survey_run onto survey_instance.  We'll also be adding a owning_role column to survey_instance.
This will allow us to use custom roles to allow for multiple administrators for surveys.  Moving this kind of permission to the instance allows us to have finer control and also helps us to 'un-link' survey instances and run (which we've talked about elsewhere).
Don't foresee this causing any major problems for you, but wanted to give you a heads up.


Issue with Restarts during Failure

Hi, I'm seeing a weird issue with the latest build (this was not the case before) where jobs are retrying not just 3 times, but continuously after a failure. It doesn't stop until you delete the job or disable the job.
I've added the parameter --failure_retry 120000, but looks like its not honoring this parameter.
Any other parameter to control the number of retries on failure? I'm creating the job through chronos UI.
Another issue is with the delay on the UI for publishing the status of the job.
Are there any parameters to control this behavior?

hi @smboy, I replied through the mailing list: "Retries should be default = 2. Did you try setting the retries parameter? Also, what is your job schedule? If you have a repeating job schedule, it will run the job according to the schedule specification."

the same exception occur in my chronos (using mesosphere deb source, 2.3.3) .
when task failed, sometimes it will retry at once and can not stop util delete the job.
here's my chronos post json content:
{
"name": "SAMPLE_JOB1",
"epsilon": "PT15M",
"command": "exit 1",
"owner"<EMAIL_ADDRESS>"async": false
}
@ another question  appeal to for hot-hearted buddys, when retry normal after task failed,  the retried task would be running after one minute,  any flag or envirment can  adjust the retry interval ? thanks a lot.

normal retry scheduler: task named  ct:1432665568732:0:SAMPLE_JOB1:, ct:1432665568732:1:SAMPLE_JOB1:, ct:1432665568732:2:SAMPLE_JOB1:
exception retry scheduler: task named always ct:1432665568732:0:SAMPLE_JOB1:.

Ah, the issue  here is now clear. If you create your job without a schedule, it will repeat infinitely. See the following code. https://github.com/mesos/chronos/blob/302a96b55cb854cc144bd0b525b975e7596340cd/src/main/scala/org/apache/mesos/chronos/scheduler/jobs/Iso8601Expressions.scala#L32:L44
Please set up your schedule with the repeat interval you would like.

For some reason, I see this happening when you setup a job through UI, but when created through command line, we don't see this issue. I'm not sure if this adds any value, but thats just an observation that I made.

@elingg when input is a empty string, parse will return None, not " -1 for infinity"?

Ah, yes, you are correct. R would give you -1, R1 should be repeating once so not setting the schedule should be fine. Very strange. This is most likely a UI bug related to how the job schedule is created through the UI.


[VS Code] [Audio] StartCall

Error:
StartCall
Steps to Reproduce:

Version Data

extensionName
VSLS-Audio

extensionVersion
0.1.32

applicationName
VSCode

applicationVersion
1.27.1

platformName
Linux

platformVersion
4.4.0-135-generic

@antaresgeo Thanks for reporting this! Did you get this error after attempting to start a call? Also, which Linux distro are you using? We haven't seen this issue before, so we'd like to make sure we fully understand the repro to investigate. Thanks!


Import Ensembl databases Error

When I run the following command to import Ensembl databases, it occurs error like this:
Command:
docker run --rm \
             --name genomehubs-ensembl \
             --network genomehubs-network \
             -v ~/genomehubs/v1/ensembl/conf:/ensembl/conf:ro \
             genomehubs/easy-mirror:19.05 /ensembl/scripts/database.sh /ensembl/conf/database.ini

Error:
awk: cannot open /ensembl/conf/database.ini (No such file or directory)
awk: cannot open /ensembl/conf/database.ini (No such file or directory)
awk: cannot open /ensembl/conf/database.ini (No such file or directory)
/ensembl/scripts/database.sh: line 14: [: =: unary operator expected
awk: cannot open /ensembl/conf/database.ini (No such file or directory)
awk: cannot open /ensembl/conf/database.ini (No such file or directory)
awk: cannot open /ensembl/conf/database.ini (No such file or directory)
awk: cannot open /ensembl/conf/database.ini (No such file or directory)
awk: cannot open /ensembl/conf/database.ini (No such file or directory)
awk: cannot open /ensembl/conf/database.ini (No such file or directory)
awk: cannot open /ensembl/conf/database.ini (No such file or directory)
awk: cannot open /ensembl/conf/database.ini (No such file or directory)
awk: cannot open /ensembl/conf/database.ini (No such file or directory)
ERROR: Unable to connect to mysql server as root.
       Check connection settings in /ensembl/conf/database.ini

So, is there something bug with the Dockerfile?

It looks like the problem here is that it can't find the INI configuration file for the database import. This should be mounted from ~/genomehubs/v1/ensembl/conf.
Can you check that you have a database.ini file in this directory?

But the database.ini file is just in the ~/genomehubs/v1/ensembl/conf.

I'm not sure what is happening here, if awk cannot open the file then it seems like it must be a problem with mounting the /ensembl/conf directory. Could you try a command like:
ls -al ~/genomehubs/v1/ensembl/conf

to check the the file and directory permissions make sense and
docker run --rm \
                   --name filetest \
                   -v ~/genomehubs/v1/ensembl/conf:/ensembl/conf:ro \
                   genomehubs/easy-mirror:19.05 ls -l /ensembl/conf/database.ini

to check whether the file is visible inside the container.

The permission of ~/genomehubs/v1/ensembl/conf like this:
total 8
drwxr-xr-x 1 root root 4096 Dec  3 17:54 .
drwxr-xr-x 1 root root 4096 Dec  1 15:38 ..
-rwxr-xr-x 1 root root  960 Dec  3 17:54 database.ini
-rw-r--r-- 1 root root 1454 Dec  1 15:38 setup.ini

But the file maybe not visible in the docker.
ls: cannot access '/ensembl/conf/database.ini': No such file or directory

I think this must be a permissions issue, then. The only ways I can reproduce it is to mount a directory that I don't have read access to, or to mount a directory that doesn't exist (by mis-spelling the path), both of which give a No such file or directory message from inside the container like you are getting. What I don't understand is that you are able to ls the directory before it is mounted so you clearly do have read permissions outside the container.
I note that the files are owned by root, but processes inside the container run with a UID of 1000. you can run processes as a different user by adding -u 1000:1000 to the docker run command to see if this helps. Generally it is best not to run docker containers as root so probably better to try setting this up as and making sure files are owned by a non-privileged user, rather than forcing the container to run as root. I usually run this on servers where I have UID 1000 but it should also be fine with higher UID numbers.
Depending how your system is configured it is possible that there is also user namespace remapping to consider (but only likely if you are running this on a shared system managed by someone else).
It may be worth trying to mount a different directory to see if you can access it from inside the container (e.g. making a directory in /tmp to make sure there is no difficulty caused by user directory permissions.

I have tried as you say, but it did not work!

OK, could you try this with a different container to see if the problem is specific to this container or a more general docker directory mounting issue:
docker run --rm \
           -v ~/genomehubs/v1/ensembl/conf:/ensembl/conf:ro \
           ubuntu:latest ls -l /ensembl/conf/database.ini

Yeah, I have tried as you said on two PCs, but they all do not work with the same error. So, maybe it's a more general docker directory mounting issue. I think I need to install the easy mirror on my local PC according to the Dockerfile.

I've only tested this on linux. As you mention PCs, I wonder if this Windows-related behaviour may be relevant: github.com/docker/machine/issues/2253. Seems like it has been causing problems with docker mounts for a few years.


Feature Request: Better APIM Integration

Is your feature request related to a problem? Please describe.
Our current solution is ACA with managed VNET, traffic is going through APIM (Dev SKU) and being funneled into 1 Container App with an IP Restriction. This works but I am worried about SNAT port exhaustion from the APIM as well as having the request go through the Internet before resolving back into the Microsoft network.
Describe the solution you'd like.
A better solution for APIM integration with ACA especially with non-custom VNET, perhaps something in the Portal that allows us to link the APIM to an ACA environment where the APIM can access all the container apps natively, perhaps some private link or vnet peering behind the scenes.
Describe alternatives you've considered.

A workaround I've considered is to manually shard the Container App that manages the input traffic from APIM then load balance through that, but that requires additional Container Apps to actually be created.
Restart from scratch and make a custom VNET for both APIM and ACA, not possible at the moment as we have this in prod it would be incredibly disruptive.
Put a NAT gateway in the APIM VNET, not able to do this, VNET is only available for APIM Premium SKU.

Thanks for the feedback @alexbot89. If you're using APIM and ACA in the same region, the traffic will stay within Azure infrastructure. However, if you need a more private connection, you will need to use a custom VNet. We don't currently have plans to allow private integration with a non-custom VNet.


Refactor name_description_integration_test for Capybara

Coverage: 93.674%. Remained the same when pulling 5390d04a705d7842d67a4e91f4504b46fb4126f7 on nimmo-refactor-post-observation-test-capybara into a24e3d001bd24fe13b97d0258888d52b4b298e25 on main.


Added tests for PR #224

Basic tests to validate allowance approval functions.
Refs PR #224

Awesome @rudygodoy! Thanks.


Hide remaining households hot water geothermal node

The table Final demand heating and hot water in residences showed a duplicate entry for Ambient heat (for hot water) as shown in the screenshot below. This entry was not affected by any of the sliders in the relevant section of the model. Further inspection showed that it represented the gquery geothermal_used_for_hot_water_in_households. The other geothermal gquery in output_element_series was set to always hidden so I've updated this gquery to match it.

Nice catch @mabijkerk!


When creating new reservation, pressing Enter in description causes a page reload

Reported by kpillay:
I typed a “Description” and hit enter. The description disappears and “Held for: XX” starts counting down.
Commentary:  It looks like the page is getting reloaded or some such thing.  I'm not sure what exactly the page should do when the user presses Enter...at first I thought it should be the same behavior as pressing Tab but now I'm not sure.  In any case, what happened wasn't quite right.

Issue moved to esnet/oscars-frontend #49 via ZenHub


Add TVL on staking card (when there's nothing deposited yet)

Show TVL always, even if there's nothing deposited to the staking yet.

Design https://zpl.io/29d4Erl

After depositing or withdrawing funds my weekly rewards amount is updated after reopening the dapp
Deposit

Withdraw

weekly rewards updating will be fixed with https://github.com/BeamMW/beam-ui/issues/732

Checked


document out Cosmos Kit structures and rename them a bit

For renaming - we need to include Noah

document out Cosmos Kit structures done.


Revoke Single Token Request - Does not work

Hello, I am trying to use the "Revoke a single token" API Request via Postman, and I am getting the following error:
{
    "error": "invalid_token",
    "error_description": "Resource not found"
}

DELETE Request : http://{{IpAddress}}:8080/oauth/token/revoke/{tokenToRevoke}
with Bearer Authorization, with uaa.admin scope.
Any Ideas why?
Or if there is a problem with this particular request
What version of UAA are you running?
4.9
How are you deploying the UAA?
Via Docker Containers

Closing due to inactivity.


first and last pagination links injected multiple times

Hi folks,
I wrote a caching plugin and likely ran into an edge case, which under normal circumstances might not get triggered.
What it does: save the full ViewModel (HalJsonModel) onResponse (listener on MvcEvent::EVENT_FINISH) and inject it (if available in the cache) via onDispatch (listener on MvcEvent::EVENT_DISPATCH) and stopPropagation.
For some reason, the collection links will be reinjected after I set the cached Model into the MvcEvent/Reponse.
Normal HAL result:
{
  "_links": {
    "self": {
      "href": "https://myapi.dev/books?page=1"
    },
    "first": {
      "href": "https://myapi.dev/books"
    },
    "last": {
      "href": "https://myapi.dev/books?page=1"
    }
  },
  "_embedded": {
    "books": [
      {

With my caching plugin:
{
  "_links": {
    "self": {
      "href": "https://myapi.dev/books?page=1"
    },
    "first": [
      {
        "href": "https://myapi.dev/books"
      },
      {
        "href": "https://myapi.dev/books"
      }
    ],
    "last": [
      {
        "href": "https://myapi.dev/books?page=1"
      },
      {
        "href": "https://myapi.dev/books?page=1"
      }
    ],
  },
  "_embedded": {
    "books": [
      {

From my reaserch this is triggered here:
https://github.com/zfcampus/zf-hal/blob/master/src/Plugin/Hal.php#L554
Or further down the road:
https://github.com/zfcampus/zf-hal/blob/master/src/Link/PaginationInjector.php#L73
https://github.com/zfcampus/zf-hal/blob/master/src/Link/PaginationInjector.php#L80
Now my question:
Why do the "first" and "last" links don't use the "overwrite" flag, like "self" already utilizes?
Beside the fact that there can only be one "first" page ;-) it feels wrong, that a JSON object is suddenly turning into an array.
Any ideas how to prevent that behaviour or could that be fixed in zf-hal directly?
Regards
Kevin

Not using Apigility any longer, closing


Please add feature to show android deafault pop to enable notification using play services.

🚀 Feature Requests

Contextualize the feature

Describe the feature
The location plugin allows me to show pop to enable GPS location via google play services. Can you please add this feature to your plugin so I can remove that location plugin?
I am just frustrated to manage both plugins for this small feature.It is also good for your plugin as well.Please consider to add for next update

Platforms affected (mark all that apply)

[ ] :robot: Android

As far as I know geolocator always displays this kind of popup on location request when google play/location services are installed but  "Google Location Accuracy" setting is disabled.

Hey @parmeetmaster, thanks for your request. I did some research and I guess it's possible, but we will need to make some major changes to the Android implementation. I'm not sure if we will make the changes, will keep you up to date in this thread!

@florissmit1 if you feel okay, You can make me a contributor.I can add solution and create pull request,If you feel okay you can merge into main branch or do required updates.

Hi @parmeetmaster!
First of all, my apologies for the radio silence. Due to shifting priorities we were unable to keep up with the maintenance of the geolocator plugin. This has recently changed, giving us time to catch up and work on the geolocator once again.
To come back to your last comment:
Everyone can contribute to the geolocator plugin. You can fork the repository, create a new branch, submit a PR and wait for review. So feel free to contribute to the plugin and implement this feature! If you need help setting up a fork or getting familiar with this plugin's structure, do not hesitate to ping me or @mvanbeusekom. We would be happy to help.

Closing as duplicate of #543, we'll keep progress of this issue there.


Add new check lambda_on_eol_runtime

New feature motivation
Lambdas that are deployed on runtimes that are EOL or scheduled to become EOL represent a continuity risk to the business. Prowler should surface these runtimes so that there are not unwelcome surprises when attempting to update a stack.
This issue is particularly acute when dealing with certain older CDK versions that create runtime-version-pinned custom Lambdas that are not simple to change in the code.
Solution Proposed
Add a check that looks for Lambdas that are deployed with a runtime that is EOL or will be EOL soon. There may need to be multiple checks here, with severities depending on where the runtime is in its lifecycle.
Describe alternatives you've considered
Creating a custom Config rule to check for EOL versions.
Additional context
This check would require dynamically pulling some information from https://docs.aws.amazon.com/lambda/latest/dg/lambda-runtimes.html, since EOL data is dynamic and changes over time.

Hi @bmorrissirromb, thanks for reaching us out!
Prowler already has the check awslambda_function_using_supported_runtimes that covers the check that you mentioned.
We use the variable obsolete_lambda_runtimes to include all EOL runtimes, you can see this variable here.
Let me know if this check works for you or if it needs any change!


Missing iglu: in nodejs documentation

In the node-js tracker documentation the example unstructured event appears to be missing the iglu: in the schema name:
t.trackUnstructEvent({
  "schema": "com.example_company/save-game/jsonschema/1.0.2",
  "data": {
    "save_id": "4321",
    "level": 23,
    "difficultyLevel": "HARD",
    "dl_content": true
  }
})

Shouldn't that be:
t.trackUnstructEvent({
  "schema": "iglu:com.example_company/save-game/jsonschema/1.0.2",
  "data": {
    "save_id": "4321",
    "level": 23,
    "difficultyLevel": "HARD",
    "dl_content": true
  }
})

The documentation is here: https://github.com/snowplow/snowplow/wiki/Node.js-Tracker#46-track-unstructured-events-with-trackunstructevent

I think it works without iglu: as well. Nonetheless, amended to avoid confusion.

Thanks @ihortom - I can't see how it could work without the iglu: (it might "work" in that it gets passed to the collector okay, but it would fail validat


Express fragment dependencies?

We have a shell fragment (header + sidebar) and one or many content fragments (mostly a single SPA). Our plan for the shell is to provide certain services to the content fragments via a client-side JavaScript API (e.g. to interact with the sidebar menu or the header search). For that to work, we somehow need to express fragment dependencies or ensure otherwise that the shell bundle is evaluated before any content fragment bundle.
Currently, we implemented this through RequireJS by letting the shell fragment define an AMD module inside of the fragment template, which depends on the shell bundle that is resolved via tailor. I outlined the solution in a gist [1].
Is there any better way to achieve this?
[1] https://gist.github.com/jmaicher/f696b510008adadd94d2b7fbb35c8966

If both the shell and foo fragments are synchronous then you don't need that require magic(def and undef) since the order of flushing them to the browser is guaranteed  and requirejs takes care of the dependencies.
I did try out the scenario you have specified here and it works without any issues, It will not work incase if the shell fragment is marked async.
It will also work if you have specified the foo.bundle.js from foo fragment Link Headers...

I though so as well, but I see two problems here:

require.js is fetching scripts with <script async>. So even if the fragments are synchronous, the order of the client-side fragment initialization [1] is not guaranteed, is it?

tailor is fetching scripts via require([script]), where script is the link provided in the fragment headers. So in order for other fragments to depend on that module, they must know the exact script URI upfront, which breaks encapsulation of fragments.

So the require magic, which is controlled by the shell fragment, defines a named shell module, very similar to how you at zalando do it in the header for react and other dependencies provided by base assets. Then, the depending fragments only need to know the module name, not the location: define(['shell'], () => {});.
[1] https://github.com/zalando/tailor/blob/master/src/pipe.js#L65

Regarding your concerns

Yes you are right here, require.js fetches the script via async so the order is not guaranteed. This is applicable only to scripts that are sent through link headers. If you want ordered behaviour you can use require.js onNodeCreated hook

require.config({
    onNodeCreated: function(node){
        node.async = false;
        node.defer = true;
    }
});

This was a conscious decision we took, We do not want fragment scripts to be dependent on another fragments. This also applied to scripts that are sent through link headers.

But in your case, since you are defining the shell fragment through fragment html
//shell fragment
http.createServer((req, res) => {
   res.end(`
      // whatever
       <script>
           define('shell', ['http://shell.com/shell'], () => {});
       <script>
  `)
})

If you do it via this way and if the other fragments like foo or whatever depends on this shell module, It wont break any behaviour since the fragments are loaded synchronously

Thanks for the reply.
Your last example is basically exactly how we solved it now, except that we also send the link header for http://shell.com/shell to let tailor load and initialize the fragment bundle regularly with the DOM element. Note that we also do not expose the init function from the bundle (default export) in the named shell module but only the named api export [1].
Generally I really like the decision to let fragments not depend on each other. In our case, the shell fragment is a special snowflake :-) but we still decided to serve it as a regular fragment. We probably stick with our solution for now, just wanted to know if there was already a proven solution to solve said problem.
From my side we can close the issue/question.
[1] https://gist.github.com/jmaicher/f696b510008adadd94d2b7fbb35c8966#file-2-shell-fragment-html-L9

Yes as you mentioned, tailor looks for default init module from the fragment scripts and it was a requirement.
Your solution will continue to work, But I would suggest you guys to put that script defining fragments to be in the head so that its loaded fast and user experience would be better.
Thanks.


PT Run frequently crashes: "Dispatcher processing has been suspended, but messages are still being processed"

Version: <IP_ADDRESS>
OS Version: Microsoft Windows NT 10.0.19041.0
IntPtr Length: 8
x64: True
Date: 09/14/2020 23:04:30
Exception:
System.InvalidOperationException: Dispatcher processing has been suspended, but messages are still being processed.
at System.Windows.Threading.Dispatcher.WndProcHook(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
at MS.Win32.HwndWrapper.WndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
at MS.Win32.HwndSubclass.DispatcherCallbackOperation(Object o)
at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)
at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Int32 numArgs, Delegate catchHandler)
2020-09-12.txt
2020-09-13.txt
2020-09-14.txt
2020-09-05.txt
2020-09-08.txt
2020-09-09.txt
2020-09-10.txt
2020-09-11.txt

Tracked in #5658


async/await use in Ubuntu 16.04 results in error: use of unresolved identifier 'DispatchGroup'

Here is the result of swift build
/Source/Await.swift:14:17: error: use of unresolved identifier 'DispatchGroup'
    let group = DispatchGroup()
                ^~~~~~~~~~~~~
/.../.build/checkouts/then.git-5361947888815775990/Source/Async.swift:14:9: error: use of unresolved identifier 'DispatchQueue'
        DispatchQueue(label: "then.async.queue", attributes: .concurrent).async {

This should be good in 2.2.4 : https://github.com/freshOS/then/releases/tag/2.2.4
Thanks a ton :)

Great! It works with the tag 2.2.4


Use random wifi password by default, make country code configurable

Dynamically generate and use /var/run/hostapd.conf using /etc/hostapd.conf.in and config
Generate random wifi password if not set, this will be the default to improve security a bit
Introduce AAWG_WIFI_PASSWORD and AAWG_COUNTRY_CODE configurations in /etc/aawgd.conf.sh

Tested this a bit and does not seem to reconnect automatically. Seems to require some manual fiddling such as disconnecting from the wifi network and reinitiating the bluetooth connection.

Thanks a lot for testing out!

Tested this a bit and does not seem to reconnect automatically.

Can you please elaborate a bit? It has troubles reconnecting after a reboot? Or when retrying connection after disconnected for some reason?

Happy to help! Yes, it appears to be that after a reboot that it requires
reinitiating the connection from Bluetooth (and possibly prior to that
forcing a disconnect from the dongle's WiFi network), to get android auto
to appear. My suspicion is that my phone is remembering the original WiFi
password and the steps are required to get it to use the newly generated
one.
I have a small hdmi monitor now and I'll try to get a better understanding
of what's happening in real time using that.
On Sun, Oct 20, 2024, 3:08 AM Nisarg Jhaveri @.***>
wrote:

Thanks a lot for testing out!
Tested this a bit and does not seem to reconnect automatically.
Can you please elaborate a bit? It has troubles reconnecting after a
reboot? Or when retrying connection after disconnected for some reason?
—
Reply to this email directly, view it on GitHub
https://github.com/nisargjhaveri/WirelessAndroidAutoDongle/pull/200#issuecomment-2424687264,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAGLP3EALFUWPCHLNG2XGUTZ4NJHVAVCNFSM6AAAAABPEC3PZWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMRUGY4DOMRWGQ
.
You are receiving this because you commented.Message ID:
@.***>


Fix codespell issues with 2.3.0

Proposed change
Trying to update codespell to help https://github.com/zigpy/zha-device-handlers/pull/2336/ ship. There are some issues using codespell 2.3.0 on the dev branch which this PR attempts to fix.
Additional information
none
Checklist

[x] The changes are tested and work correctly
[x] pre-commit checks pass / the code has been formatted using Black
[ ] Tests have been added to verify that the new code works

keep getting this issue in CI :/
Different tests were collected between gw0 and gw3. The difference is:

Fix for broken CI: https://github.com/zigpy/zha-device-handlers/pull/3258


[stable/logstash] updated logstash to 6.5.0

Signed-off-by: André Bauer<EMAIL_ADDRESS>
What this PR does / why we need it:

updated logstash to 6.5.0

Which issue this PR fixes
(optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged)

fixes #

Special notes for your reviewer:
Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

[x] DCO signed
[x] Chart Version bumped
[x] Variables are documented in the README.md

/ok-to-test

/lgtm


Reading progress not showing in synchronized computers

Chartero worked well in my office computer. However, the reading progress was now showing in another synchronized computer (nevertheless, I could find the synchronized Chartero json files in the library).
But when I read a new item in the new computer, the progress did show properly.
Did I miss something? Is there any way to fix? Many thanks!

When you sync in a new computer, you should find your previous json item in library and right-click to set as history.

Worked like a charm. Thank you!


DependsON - Adding a depends on condition in modules

Hey, i'm proposing a depends on condition because sometimes in a terraform destroy the nodepool could be deleted before the nginx and certmanager removed.
When its happen the nginx and certmanager process could be stuck and enter an exception causing a timeout error.
In addition,
Can i use your project with base to my own project making some changes and adding in my public repo?
I will give you the credits on it

Hi @bremmercandia - thanks for the contribution. Yes sure, you can add the project to your public repo and change as you like.


fix: type errors on basic app

Will fix #156

[x] add test
[x] fix other 12 cases

Type-check failures being caught:
    console.log tests/integration/_helpers.ts:13
      /Users/jasonkuhrt/projects/prisma/nexus/src/builder.ts (1485,16): Type '"Int" | "Float" | "String" | "Boolean" | "ID" | NexusInputObjectTypeDef<string> | NexusEnumTypeDef<string> | NexusScalarTypeDef<string>' is not assignable to type 'NexusArgConfigType<NexusGenScalarNames>'.
        Type 'NexusInputObjectTypeDef<string>' is not assignable to type 'NexusArgConfigType<NexusGenScalarNames>'.
          Type 'NexusInputObjectTypeDef<string>' is not assignable to type 'NexusInputObjectTypeDef<NexusGenScalarNames>'.
            Type 'string' is not assignable to type 'NexusGenScalarNames'.
    console.log tests/integration/_helpers.ts:13
      /Users/jasonkuhrt/projects/prisma/nexus/src/definitions/definitionBlocks.ts (210,11): Type '{ name: FieldName; } & FieldOutConfig<TypeName, FieldName>' is not assignable to type 'NexusOutputFieldDef'.
        Type '{ name: FieldName; } & FieldOutConfig<TypeName, FieldName>' is not assignable to type 'NexusOutputFieldConfig<string, any>'.
    console.log tests/integration/_helpers.ts:13
      /Users/jasonkuhrt/projects/prisma/nexus/src/definitions/definitionBlocks.ts (227,7): Type 'FieldResolver<TypeName, any>' is not assignable to type 'FieldResolver<string, any>'.
        Type 'string' is not assignable to type 'TypeName'.
          'string' is assignable to the constraint of type 'TypeName', but 'TypeName' could be instantiated with a different subtype of constraint 'string'.
    console.log tests/integration/_helpers.ts:13
      /Users/jasonkuhrt/projects/prisma/nexus/src/definitions/extendType.ts (34,46): Argument of type '{ name: TypeName; type: TypeName; definition(t: OutputDefinitionBlock<TypeName>): void; }' is not assignable to parameter of type 'NexusExtendTypeConfig<string> & { name: string; }'.
        Type '{ name: TypeName; type: TypeName; definition(t: OutputDefinitionBlock<TypeName>): void; }' is not assignable to type 'NexusExtendTypeConfig<string>'.
          Types of property 'definition' are incompatible.
            Type '(t: OutputDefinitionBlock<TypeName>) => void' is not assignable to type '(t: OutputDefinitionBlock<string>) => void'.
              Types of parameters 't' and 't' are incompatible.
                Type 'OutputDefinitionBlock<string>' is not assignable to type 'OutputDefinitionBlock<TypeName>'.
                  Types of property 'string' are incompatible.
                    Type '<FieldName extends string>(fieldName: FieldName, ...opts: [] | [OutputScalarConfig<string, FieldName>] | [FieldResolver<string, FieldName>]) => void' is not assignable to type '<FieldName extends string>(fieldName: FieldName, ...opts: ScalarOutSpread<TypeName, FieldName>) => void'.
                      Types of parameters 'opts' and 'opts' are incompatible.
                        Type 'ScalarOutSpread<TypeName, any>' is not assignable to type '[] | [OutputScalarConfig<string, any>] | [FieldResolver<string, any>]'.
                          Type '((TypeName extends never ? any extends keyof NexusGenArgTypes[TypeName] ? true : false : false) extends true ? [ScalarOutConfig<TypeName, any>] : [ScalarOutConfig<TypeName, any>] | [...]) | ((TypeName extends never ? any extends keyof NexusGenArgTypes[TypeName] ? true : false : false) extends true ? [...] : [] | ......' is not assignable to type '[] | [OutputScalarConfig<string, any>] | [FieldResolver<string, any>]'.
                            Type '(TypeName extends never ? any extends keyof NexusGenArgTypes[TypeName] ? true : false : false) extends true ? [ScalarOutConfig<TypeName, any>] : [ScalarOutConfig<TypeName, any>] | [...]' is not assignable to type '[] | [OutputScalarConfig<string, any>] | [FieldResolver<string, any>]'.
                              Type '[ScalarOutConfig<TypeName, any>] | [FieldResolver<TypeName, any>]' is not assignable to type '[] | [OutputScalarConfig<string, any>] | [FieldResolver<string, any>]'.
                                Type '[ScalarOutConfig<TypeName, any>]' is not assignable to type '[] | [OutputScalarConfig<string, any>] | [FieldResolver<string, any>]'.
                                  Type '[ScalarOutConfig<TypeName, any>]' is not assignable to type '[OutputScalarConfig<string, any>]'.
                                    Type 'ScalarOutConfig<TypeName, any>' is not assignable to type 'OutputScalarConfig<string, any>'.
                                      Type 'OutputScalarConfig<TypeName, any> | (OutputScalarConfig<TypeName, any> & { resolve: FieldResolver<TypeName, any>; })' is not assignable to type 'OutputScalarConfig<string, any>'.
                                        Type 'OutputScalarConfig<TypeName, any>' is not assignable to type 'OutputScalarConfig<string, any>'.
                                          Types of property 'resolve' are incompatible.
                                            Type 'FieldResolver<TypeName, any> | undefined' is not assignable to type 'FieldResolver<string, any> | undefined'.
                                              Type 'FieldResolver<TypeName, any>' is not assignable to type 'FieldResolver<string, any>'.
                                                Type 'string' is not assignable to type 'TypeName'.
                                                  Type '(TypeName extends never ? any extends keyof NexusGenArgTypes[TypeName] ? true : false : false) extends true ? [ScalarOutConfig<TypeName, any>] : [ScalarOutConfig<TypeName, any>] | [...]' is not assignable to type '[FieldResolver<string, any>]'.
                                                    Type 'ScalarOutSpread<TypeName, any>' is not assignable to type '[FieldResolver<string, any>]'.
                                                      Type '((TypeName extends never ? any extends keyof NexusGenArgTypes[TypeName] ? true : false : false) extends true ? [ScalarOutConfig<TypeName, any>] : [ScalarOutConfig<TypeName, any>] | [...]) | ((TypeName extends never ? any extends keyof NexusGenArgTypes[TypeName] ? true : false : false) extends true ? [...] : [] | ......' is not assignable to type '[FieldResolver<string, any>]'.
                                                        Type '(TypeName extends never ? any extends keyof NexusGenArgTypes[TypeName] ? true : false : false) extends true ? [ScalarOutConfig<TypeName, any>] : [ScalarOutConfig<TypeName, any>] | [...]' is not assignable to type '[FieldResolver<string, any>]'.
                                                          Type '[ScalarOutConfig<TypeName, any>] | [FieldResolver<TypeName, any>]' is not assignable to type '[FieldResolver<string, any>]'.
                                                            Type '[ScalarOutConfig<TypeName, any>]' is not assignable to type '[FieldResolver<string, any>]'.
                                                              Type 'ScalarOutConfig<TypeName, any>' is not assignable to type 'FieldResolver<string, any>'.
                                                                Type 'OutputScalarConfig<TypeName, any> | (OutputScalarConfig<TypeName, any> & { resolve: FieldResolver<TypeName, any>; })' is not assignable to type 'FieldResolver<string, any>'.
                                                                  Type 'OutputScalarConfig<TypeName, any>' is not assignable to type 'FieldResolver<string, any>'.
                                                                    Type 'OutputScalarConfig<TypeName, any>' provides no match for the signature '(root: any, args: any, context: any, info: GraphQLResolveInfo): any'.
    console.log tests/integration/_helpers.ts:13
      /Users/jasonkuhrt/projects/prisma/nexus/src/definitions/inputObjectType.ts (38,32): Type 'TypeName' does not satisfy the constraint 'NexusGenScalarNames'.
        Type 'string' is not assignable to type 'NexusGenScalarNames'.
          Type 'TypeName' is not assignable to type '"ID"'.
            Type 'string' is not assignable to type '"ID"'.
    console.log tests/integration/_helpers.ts:13
      /Users/jasonkuhrt/projects/prisma/nexus/src/definitions/inputObjectType.ts (39,26): Type 'this' is not assignable to type 'NexusArgConfigType<NexusGenScalarNames>'.
        Type 'NexusInputObjectTypeDef<TypeName>' is not assignable to type 'NexusArgConfigType<NexusGenScalarNames>'.
          Type 'NexusInputObjectTypeDef<TypeName>' is not assignable to type 'NexusInputObjectTypeDef<NexusGenScalarNames>'.
            Type 'TypeName' is not assignable to type 'NexusGenScalarNames'.
              Type 'TypeName' is not assignable to type '"ID"'.
                Type 'this' is not assignable to type 'NexusWrappedType<AllNexusInputTypeDefs<NexusGenScalarNames>>'.
                  Type 'NexusInputObjectTypeDef<TypeName>' is missing the following properties from type 'NexusWrappedType<AllNexusInputTypeDefs<NexusGenScalarNames>>': wrappedFn, fn
    console.log tests/integration/_helpers.ts:13
      /Users/jasonkuhrt/projects/prisma/nexus/src/definitions/interfaceType.ts (79,49): Argument of type 'NexusInterfaceTypeConfig<TypeName>' is not assignable to parameter of type 'NexusInterfaceTypeConfig<string>'.
        Types of property 'definition' are incompatible.
          Type '(t: InterfaceDefinitionBlock<TypeName>) => void' is not assignable to type '(t: InterfaceDefinitionBlock<string>) => void'.
            Types of parameters 't' and 't' are incompatible.
              Type 'InterfaceDefinitionBlock<string>' is not assignable to type 'InterfaceDefinitionBlock<TypeName>'.
                Types of property 'typeBuilder' are incompatible.
                  Type 'AbstractOutputDefinitionBuilder<string>' is not assignable to type 'AbstractOutputDefinitionBuilder<TypeName>'.
                    Type 'string' is not assignable to type 'TypeName'.
                      'string' is assignable to the constraint of type 'TypeName', but 'TypeName' could be instantiated with a different subtype of constraint 'string'.
    console.log tests/integration/_helpers.ts:13
      /Users/jasonkuhrt/projects/prisma/nexus/src/definitions/objectType.ts (112,46): Argument of type 'NexusObjectTypeConfig<TypeName>' is not assignable to parameter of type 'NexusObjectTypeConfig<string>'.
        Types of property 'definition' are incompatible.
          Type '(t: ObjectDefinitionBlock<TypeName>) => void' is not assignable to type '(t: ObjectDefinitionBlock<string>) => void'.
            Types of parameters 't' and 't' are incompatible.
              Type 'ObjectDefinitionBlock<string>' is not assignable to type 'ObjectDefinitionBlock<TypeName>'.
                Types of property 'typeBuilder' are incompatible.
                  Type 'ObjectDefinitionBuilder<string>' is not assignable to type 'ObjectDefinitionBuilder<TypeName>'.
                    Types of property 'addFieldModifications' are incompatible.
                      Type '<FieldName extends string>(changes: FieldModificationDef<string, FieldName>) => void' is not assignable to type '<FieldName extends string>(changes: FieldModificationDef<TypeName, FieldName>) => void'.
                        Types of parameters 'changes' and 'changes' are incompatible.
                          Type 'FieldModificationDef<TypeName, any>' is not assignable to type 'FieldModificationDef<string, any>'.
                            Types of property 'resolve' are incompatible.
                              Type 'FieldResolver<TypeName, any> | undefined' is not assignable to type 'FieldResolver<string, any> | undefined'.
                                Type 'FieldResolver<TypeName, any>' is not assignable to type 'FieldResolver<string, any>'.
                                  Type 'string' is not assignable to type 'TypeName'.
                                    'string' is assignable to the constraint of type 'TypeName', but 'TypeName' could be instantiated with a different subtype of constraint 'string'.
    console.log tests/integration/_helpers.ts:13
      /Users/jasonkuhrt/projects/prisma/nexus/src/definitions/subscriptionField.ts (51,5): Type '"Subscription"' is not assignable to type '"Query" | "Mutation"'.
    console.log tests/integration/_helpers.ts:13
      /Users/jasonkuhrt/projects/prisma/nexus/src/definitions/subscriptionField.ts (54,26): Argument of type 'SubscribeFieldConfig<"Subscription", FieldName, any>' is not assignable to parameter of type 'FieldOutConfig<"Query" | "Mutation", FieldName>'.
    console.log tests/integration/_helpers.ts:13
      /Users/jasonkuhrt/projects/prisma/nexus/src/typegen.ts (402,12): Element implicitly has an 'any' type because expression of type 'string' can't be used to index type '{ Query?: string | undefined; }'.
        No index signature with a parameter of type 'string' was found on type '{ Query?: string | undefined; }'.
    console.log tests/integration/_helpers.ts:13
      /Users/jasonkuhrt/projects/prisma/nexus/src/typegen.ts (674,25): Element implicitly has an 'any' type because expression of type 'string' can't be used to index type '{ Query?: string | undefined; }'.
        No index signature with a parameter of type 'string' was found on type '{ Query?: string | undefined; }'.

@tgriesser I am not sure I am on the right track here

The integration tests are passing on my machine but not on cci
❯ yarn jest --ci
yarn run v1.17.3
$ /Users/jasonkuhrt/projects/prisma/nexus/node_modules/.bin/jest --ci
 PASS  tests/sdlConverter.spec.ts
 PASS  tests/resolveTypes.spec.ts
 PASS  tests/typegen.spec.ts
 PASS  tests/definitions.spec.ts
 PASS  tests/unknownType.spec.ts
 PASS  tests/backingTypes.spec.ts
 PASS  tests/nonNullDefaults.spec.ts
 PASS  tests/integration/simpleApp.spec.ts (7.674s)

Test Suites: 8 passed, 8 total
Tests:       36 passed, 36 total
Snapshots:   24 passed, 24 total
Time:        8.098s
Ran all test suites.
✨  Done in 9.18s.

investigating...

Tests pass after updating deps. It seems that TS compiler was targetting ES3 before, for some reason.
Reason tests were passing locally before was because I was installing packages with npm and given no npm lock had same effect as a yarn upgrade effectively.

I am finding more type errors as I add more integration tests. I suspect my initial fixes at this point:

did "fixes" actually introduce errors not caught at the time?
my understanding of nexus continues to evolve right now

I may remove all my fixes, leaving just the integration tests in place, and start over.

I took another pass, this time resorting to any when I had a low confidence. I feel this PR is ready for review and past an MVP state now.


IndexError: list index out of range

Scanning for missing songs...
Traceback (most recent call last):
  File "./gmsync.py", line 202, in <module>
    main()
  File "./gmsync.py", line 164, in main
    upload_songs = compare_song_collections(local_songs, google_songs)
  File "/home/rika-chan/gmusicapi-scripts-master/gmwrapper.py", line 49, in compare_song_collections
    src_key = create_song_key(src_song)
  File "/home/rika-chan/gmusicapi-scripts-master/gmwrapper.py", line 68, in create_song_key
    song = song if isinstance(song, dict) else _mutagen_fields_to_single_value(song)
  File "/home/rika-chan/gmusicapi-scripts-master/gmwrapper.py", line 35, in _mutagen_fields_to_single_value
    return {k: v[0] for k, v in mutagen.File(file, easy=True).iteritems()}
  File "/home/rika-chan/gmusicapi-scripts-master/gmwrapper.py", line 35, in <dictcomp>
    return {k: v[0] for k, v in mutagen.File(file, easy=True).iteritems()}
IndexError: list index out of range

Using debian 7.

Same here, Ubuntu 14.04

Closing, dev branch works fine.

Yeah, I've been running out of time/motivation to push a release to PyPI. This was fixed a while ago in the devel branch. For anyone curious, it's caused by an empty tag field from a local file which my code didn't handle.


Inconsistent relative links in web editor preview

Gogs version (or commit ref): <IP_ADDRESS>0
Can you reproduce the bug at https://try.gogs.io:

[Yes (https://try.gogs.io/tsukanov.as/test/src/master/README.md)

Description
Inconsistent relative links (web-editor preview VS markdown view)
Tested link:
[test link](/../test)
Web-editor preview

Markdown view

...

I think it's already fixed in latest release.


Added Fenwick Tree DS with docs and prob statement

Title: Fenwick Tree C++ implementation
Todos:

[x] Added code
[x] Proper documentation added
[x] Sample Test cases added
[x] Changes made on a new branch (arnabsen1729)

Changes:

New file named "Fenwick_Tree.cpp"

Fixed https://github.com/amritansh22/Data-Structures-and-Algorithms-in-cpp/issues/101

Excellent work @arnabsen1729 Thanks a lot for making this PR.


nixos-rebuild fails due to wg-quick

Describe the bug
I have a machine using wg-quick via the configFile option with nothing particularly special in the config file. When I nixops deploy or nixos-rebuild switch it fails due to the interface already existing:
× wg-quick-wg0.service - wg-quick WireGuard Tunnel - wg0
     Loaded: loaded (/etc/systemd/system/wg-quick-wg0.service; enabled; preset: enabled)
     Active: failed (Result: exit-code) since Mon 2023-04-24 19:21:20 MDT; 337ms ago
   Duration: 1w 4d 7h 46min 7.162s
    Process: 660632 ExecStart=/nix/store/9ll9s1cyi0bjb556nkiav2y9bjk1anyn-unit-script-wg-quick-wg0-start/bin/wg-quick-wg0-start (code=exited, status=1/FAILURE)
   Main PID: 660632 (code=exited, status=1/FAILURE)
         IP: 0B in, 0B out
        CPU: 46ms

Apr 24 19:21:20 r systemd[1]: Starting wg-quick WireGuard Tunnel - wg0...
Apr 24 19:21:20 r wg-quick-wg0-start[660639]: .wg-quick-wrapped: `wg0' already exists
Apr 24 19:21:20 r systemd[1]: wg-quick-wg0.service: Main process exited, code=exited, status=1/FAILURE
Apr 24 19:21:20 r systemd[1]: wg-quick-wg0.service: Failed with result 'exit-code'.
Apr 24 19:21:20 r systemd[1]: Failed to start wg-quick WireGuard Tunnel - wg0.
warning: error(s) occurred while switching to the new configuration

If I ip link del wg0 first, the nixos-rebuild succeeds.
Steps To Reproduce
As per above.
Expected behavior
I'm able to nixos-rebuild switch without error.
Additional context
I suspect that a postStop ip link del as in the wireguard config would resolve this issue. I'd be happy to make a PR to this effect.
Notify maintainers
@cab404 @ncfavier
Metadata
 - system: `"x86_64-linux"`
 - host os: `Linux 5.15.106, NixOS, 22.11 (Raccoon), 22.11.20230424.f536431`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.13.2`
 - channels(root): `"nixpkgs"`
 - channels(n8henrie): `"nixpkgs-22.11"`
 - nixpkgs: `/root/.nix-defexpr/channels/nixpkgs`

Weird, the service's ExecStop calls wg-quick down, which should remove the interface. Can you confirm that it runs when you rebuild?

Hmm. I waited until this had been a reproducible issue for a couple weeks, happened again after I'd manually resolved it a time or two with an ip link del and the problem returned, and happened with both nixops deploy and nixos-rebuild switch. But of course as soon as I post the issue, it seems to be working again. I'll close for now, if it comes back I'll try manually running the wg-quick down step, and re-open if needed. Thanks for your reply!

Ran into this again a few days ago. Not sure what's going on. Manually running wg-quick down resolved it for the time being.

For anyone finding this.
You can add an activationScript to remove the interfaces as a workaround.
PostDown does not work.
  system.activationScripts = {
    fix-wireguard-activation = ''
      ${pkgs.iproute2}/bin/ip link del wg0
     '';
  };

I am experiencing this as well. It happens on every single machine set up with wg-quick and deployed with deploy-rs.
This seems to happen every time I update my flakes before deploying.

Do you have NM enabled?

I am experiencing this as well. It happens on every single machine set up with wg-quick and deployed with deploy-rs.
This seems to happen every time I update my flakes before deploying.

Do you have NM enabled?

# systemctl status NetworkManager
Unit NetworkManager.service could not be found.

These are all headless servers without NetworkManager.

hm, worth a shot. You don't happen to have a public flake?


Fixes #1827 : Added new golang test cases for ECA Registrar feature

This change adds new golang test cases for ECA Registrar features.
Description
Test cases have been created to check registration behavior with various combinations of roles and delegateRoles for users
Motivation and Context
It increases code coverage tests for ECA registrar feature
Fixes #1827
How Has This Been Tested?
Changes have been tested by running "go test -v"
Checklist:

[x] I have added a Signed-off-by.
[x] I have either added documentation to cover my changes or this change requires no new documentation.
[x] I have either added unit tests to cover my changes or this change requires no new tests.
[x] I have run golint and have fixed valid warnings in code I have added or modified. This tool generates false positives so you may choose to ignore some warnings. The goal is clean, consistent, and readable code.

Signed-off-by: Sudeepta Bhuyan<EMAIL_ADDRESS>

@sudeepta-bhuyan This looks great! Thank you.
One thing though - once/when/after this is merged, I suggest to keep #1827 open though, so that we can add more of such good stuff to the tests...

@sudeepta-bhuyan Thanks, LGTM. Always appreciate more tests!
@JonathanLevi Thanks for the review!

@JonathanLevi I reopened #1827


Variable Var n is not bound

Summary
Hi, this occurs sporadically. I can run thousands of model checks in succession and not experience this, but sometimes I will experience this error:
  Standard Model Check:  FAIL (43.28s)
    *** Failed! (after 45 tests and 10 shrinks):
    Exception:
      Variable Var 14 is not bound!
      CallStack (from HasCallStack):
        error, called at src/Test/QuickCheck/StateModel.hs:75:18 in quickcheck-dynamic-<IP_ADDRESS>-KyLL9UuOfU2
5O9KQ5A71yO:Test.QuickCheck.StateModel
    Actions
     [tok3 := SetupTokens,
      tok8 := MintIdents (Wallet 1) ["plazlemff",""],
      Init (Wallet 1) (SymInstanceParams {ident = tok14.hk, assets = [tok3.A,tok3.C]})]

Steps to reproduce the behavior
Unable to share code for this, but I will try and make a reproduction when I can.
Actual Result
Error
Expected Result
No error
Describe the approach you would take to fix this
No response
System info
NixOS

As you can see from the error message you're trying to use a symbolic token that doesn't exist - you have SymInstanceParams {ident = tok14.hk, ...} but there is no tok14 in the list of actions. This is because your precondition for your actions is missing a check to make sure that the tokens that are in your actions after shrinking actually exist. Unfortunately you have to code this check up yourself as there is currently no generic programming support for this - we are working on a fix for that. For reference, see the Uniswap example.

Thank you for explaining I'll try this.

To be specific check out the following line:
https://github.com/input-output-hk/plutus-apps/blob/9b5aeea0bdac2784c22bdc8528720835e125fd0a/plutus-use-cases/test/Spec/Uniswap.hs#L241
Here we check that the tokens we trying to set up a swap for actually exist in the set of tokens we've created for this test. When running normal tests this is "obviously true" - we don't generate symbolic tokens that haven't been created by createToken. However, because a symbolic token is just a pair of basically an action number and a specific identifier within the action (an action can create more than one token) this check still needs to be there for shrinking to work properly. Specifically, your original counterexample may be something like Actions [tok1 := SetupTokens, UseToken tok1.A, <do something else>] and shrinking will try to remove individual actions, so you get Actions [UseToken tok1.A, <do something else>]. Here tok1 is basically a pointer to a token that is created non-existen action (what was originally SetupTokens) and so this test is meaningless. To avoid this problem we need checks like the one I linked above to make sure that tok1.A is actually meaningful in this particular trace.
Now, in the future it would be very nice to be able to automate these checks and make sure that no actions are present that contain references to unbound tokens. One way to do this is to pose some SYB-like constraints on Action model to require it to give you all symbolic tokens in an action so that we can check this behind the scenes. I'll bump this to the top of my bugfixing prio list.

Heads up @locallycompact a feature that makes this more ergonomic has just been merged to main. I think you should be able to get rid of some of your wellformedness checks here now!

This is wonderful I'll try this now. Thank you.

I can't actually locate that plutus commit you used 4127e9cd6e889824d724c30eae55033cb50cbf3e

You have to use release/node-1.34 - that's the version of plutus that plutus-apps depends on.

Ping @sjoerdvisscher as I don't quite understand how this is organized in separate projects.

I'm using a haskell.nix stack.yaml conversion. This works now:
https://gitlab.homotopic.tech/plutus/contracts/nft/-/blob/master/stack.yaml

This was after adding a Data instance to SymValue, which I needed to compile the model. Not sure if that's relevant. I'll try and put together some open source examples.

There is probably a bug in your generator. I would start by carefully going
through every use of elements to make sure you're not using it on an
empty list.
Secondly, the error you're getting (that the exception happened during
shrinking) is likely related to laziness. Perhaps your property is failing
(its definitely failing, and it most likely was failing before too - I
don't think recent changes should have changed that) and some part of the
input that wasn't evaluated when the property failed was evaluated during
shrinking.
On Tue, 8 Mar 2022, 19:09 Daniel Firth, @.***> wrote:

This was after adding a Data instance to SymValue, which I needed to
compile the model. Not sure if that's relevant. I'll try and put together
some open source examples.
—
Reply to this email directly, view it on GitHub
https://github.com/input-output-hk/plutus-apps/issues/342#issuecomment-1062061833,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACBPPQM7WSDKM2VFMKR3473U66JUPANCNFSM5PXH4FMQ
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you commented.Message ID:
@.***>

I'm not experiencing model failures before I switch to the new version and I get this one now with the new version. I'll try and dig in.

Ok, I think I know the reason. Previously the precondition was being evaluated against the ModelState eagerly first before constructing the Action lazily later, so the precondition was firing before the call to elements, so I did have a bug, which was incidentally a bug previously in plutus-apps.

Ah, that makes total sense. The new precondition is a lot stricter in the
action than the old precondition.
On Tue, 8 Mar 2022, 20:22 Daniel Firth, @.***> wrote:

Ok, I think I know the reason. Previously the precondition was being
evaluated against the ModelState eagerly first before constructing the
Action lazily later, so the precondition was firing before the call to
elements, so I did have a bug, which was incidentally a bug previously in
plutus-apps.
—
Reply to this email directly, view it on GitHub
https://github.com/input-output-hk/plutus-apps/issues/342#issuecomment-1062120490,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACBPPQNBJM23RHIIUDIFTCLU66SFVANCNFSM5PXH4FMQ
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you commented.Message ID:
@.***>


Broken link to connector description?

This is regarding the link highlighted in the screenshot below.

Where is it supposed to go? It currently just goes to the Power BI home page.

Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

ID: 054662fb-66f6-d36d-6ba5-85fde75574b9
Version Independent ID: 054662fb-66f6-d36d-6ba5-85fde75574b9
Content: Power Query Azure Synapse Analytics workspace connector - Power Query
Content Source: powerquery-docs/Connectors/Synapse.md
Service: powerquery
GitHub Login: @miquelladeboer
Microsoft Alias: mideboer

Hi @VitalyMCT
Thanks for the feedback.
This seems to be product feedback or a request for product support. In this case, please direct those queries to the Power BI community forum or to the connector-specific support contact (if applicable).


Rename pubgredzone to rotisserie

Handles scrubbing all instances of pubgredzone and replacing with rotisserie.

It looks good, but can you make all the user facing text say "PUBG rotisserie"?


libc 0.2.75

r? @JohnTitor
(rust_highfive has picked a reviewer for you, use r? to override)

Would love to get a release that includes my recent changes related to child processes, pidfd, and siginfo.

Published v0.2.75 on crates.io (https://crates.io/crates/libc/0.2.75), thanks!


riscv64: Improve scalar_to_vector codegen for constants

👋 Hey,
This is a fairly simple improvement. Cranelift's scalar_to_vector instruction grabs a scalar value and places it at the bottom of a vector register.
We translate this into the vmerge.vxm instruction in the RISC-V backend.
This is all fairly ok, but we don't have a rule to match the vmerge.vim instruction that can place an immediate value instead of a register.
Implementing this should be fairly simple, we can create a rule similar to the existing ones but using a imm5_from_value extractror:
(rule 2 (lower (has_type (ty_vec_fits_in_register ty) (scalar_to_vector (imm5_from_value x))))

This imm5_from_value extractor doesn't exist yet, but we already have an equivalent in the replicated_imm5 extractor. It should be fairly easy to extract that into it's own separate extractor for use in this new rule.
See the existing uimm5_from_value extractor for help.
If anyone needs help working on this issue let me know!

Hey! I'm fairly new to Cranelift but would like to give it a try.

Awesome 🎉 Let me know if you need any help getting started!


Missing cypress/included 10.3.1 docker images

Even tho #705 has been merged 13 hours ago still I cannot see cypress/included docker images:
https://hub.docker.com/r/cypress/included/tags
Not sure what went wrong. Thanks

Hi @michalbundyra, looking in to this currently. I think it's related to the changes we made to add a new architecture in #700.

10.3.1 images are now available on Hub and ECR.


Unable to lookup cesium.rivianservices.com

Apparently cesium is no longer a valid domain for Rivian? (I really wish they would just provide an official, supported API.)
I know technically I should have submitted this to the other repo, but I thought it might get more visibility here. Interestingly, looking at my DNS logs, the app appears to be only looking for rivian.com directly.
The plugin stopped today with this error:
This error originated from a custom integration.

Logger: custom_components.rivian
Source: custom_components/rivian/__init__.py:156
Integration: Rivian (Unofficial) (documentation)
First occurred: 6:08:12 PM (1964 occurrences)
Last logged: 9:12:29 PM

Unknown Exception while updating Rivian data: Error occurred while communicating with Rivian.
Traceback (most recent call last):
  File "/usr/local/lib/python3.10/site-packages/aiohttp/connector.py", line 1154, in _create_direct_connection
    hosts = await asyncio.shield(host_resolved)
  File "/usr/local/lib/python3.10/site-packages/aiohttp/connector.py", line 880, in _resolve_host
    addrs = await self._resolver.resolve(host, port, family=self._family)
  File "/usr/local/lib/python3.10/site-packages/aiohttp/resolver.py", line 33, in resolve
    infos = await self._loop.getaddrinfo(
  File "/usr/local/lib/python3.10/asyncio/base_events.py", line 860, in getaddrinfo
    return await self.run_in_executor(
  File "/usr/local/lib/python3.10/concurrent/futures/thread.py", line 58, in run
    result = self.fn(*self.args, **self.kwargs)
  File "/usr/local/lib/python3.10/socket.py", line 955, in getaddrinfo
    for res in _socket.getaddrinfo(host, port, family, type, proto, flags):
socket.gaierror: [Errno -2] Name does not resolve

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/usr/local/lib/python3.10/site-packages/rivian/rivian.py", line 264, in get_vehicle_info
    response = await self._session.request(
  File "/usr/local/lib/python3.10/site-packages/aiohttp/client.py", line 535, in _request
    conn = await self._connector.connect(
  File "/usr/local/lib/python3.10/site-packages/aiohttp/connector.py", line 542, in connect
    proto = await self._create_connection(req, traces, timeout)
  File "/usr/local/lib/python3.10/site-packages/aiohttp/connector.py", line 907, in _create_connection
    _, proto = await self._create_direct_connection(req, traces, timeout)
  File "/usr/local/lib/python3.10/site-packages/aiohttp/connector.py", line 1166, in _create_direct_connection
    raise ClientConnectorError(req.connection_key, exc) from exc
aiohttp.client_exceptions.ClientConnectorError: Cannot connect to host cesium.rivianservices.com:443 ssl:default [Name does not resolve]

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/config/custom_components/rivian/__init__.py", line 156, in _update_api_data
    vehicle_info = await self._api.get_vehicle_info(
  File "/usr/local/lib/python3.10/site-packages/rivian/rivian.py", line 275, in get_vehicle_info
    raise Exception(
Exception: Error occurred while communicating with Rivian.

Actually, the app is also looking for tsync.rivianservices.com and ruploader-asset.rivianservices.com (though I assume the latter is irrelevant).

Yeah, I can confirm cesium is dead. Even the previous IP addresses don't allow any connections. It's always on a Friday they do this.

We have been working to get this resolved.  I believe I have the code working again with location and a single sensor.  We are working as quick as possible to get the other sensors back online, but the switch over to GraphQL will cause us to lose access to a few items.
Here is where were at right now

Thank you for sticking with us while we work to resolve the issue!

That's great news! For me, personally, the battery level & location are the most useful. Anything else is just icing.

This is now resolved in https://github.com/bretterer/home-assistant-rivian/releases/tag/0.7.0-beta.1.   Please update to the latest version

Seems to be working great for me!
I'll have to see if I can figure out a new way to determine if the truck is plugged in or not. I was using rivian_energy_storage_charger_ems_charger_evse_type, but that seems to no longer be available. But other than that, it's nice having the data back!
Thank you all very much for working on this.

I'm updating some of my pre-canned dashboard I shared based on the new sensor naming that went into this release.
To have a simple "charging" or "not charging" check out Charging Status as shown below in the Logbook card (best way to see all sensor modifications and discover new data points).

I have charging/not charging, but I also like to track plugged in but not charging. My one alert is a reminder if the truck is not plugged in and the power is below 50%.
Sometimes with scheduled departure on my Tesla, it'll be plugged in and low, but not actively charging as it's waiting to charge until later. This is less of a concern on the Rivian, since it doesn't have scheduled departure (and I don't use time-of-day charging).
I just did some checking, it doesn't appear that there's information available right now to detect it, but that's OK, it's not critical. They are providing it to the app somehow, as it knows if it's plugged in and not charging on the graphic.

There are some prior sensors we haven't been able to reverse engineer into the new GraphQL API language. This is indeed one of those sensors. Likely it is still available for us, but with the new API we need to know the direct name of the sensor and there isn't a wild card or even a documented way to determine the name. Bare with us as we try to find what this sensor is 👍 .

Actually I stand corrected we are using a different sensor/attribute that is provided to us... forgot about this mapping.
Try to convert to using binary_sensor.rivian_energy_storage_charger_status_vehicle_charger_status which will be able to determine this for you @OverZealous

Oh yeah, no worries! I'm totally happy with what you have gotten working. Reverse engineering this is frustrating to say the least, I'm sure.
I'm pretty blown away by what you guys have done already. I love having this as part of my HA setup.
I'll check out out that new sensor when it pops up. Thanks!


Week1 raghuram

Good job 🎉
Nice UI !!

Good job, closing the pull request since changes have been approved


Consider fullscreen mode when installed

With #398 NoFlo UI (and therefore Flowhub) can be made a pseudo-app using mobile browser Add to homescreen features on both iOS and Android. Currently on Android we're running the UI as a regular app screen, meaning that OS title and navigation bars are still visible.

We could consider switching to fullscreen to give users even more space, but this needs discussion as it can also be seen as overtly invasive.
The different screen modes are explained at: http://updates.html5rocks.com/2014/11/Support-for-installable-web-apps-with-webapp-manifest-in-chrome-38-for-Android#utility-apps

We've dropped native apps, but the webapp manifest asks for full screen now:
display": "standalone",


Translate [Front End Engineer - Pleno]

Translate [Front End Engineer - Pleno] session on this link
Related to: #19

[ ] es
[x] en

Doing

Thanks @daliannyvieira!! :heart:


device.getWithServiceDetails: Stop auto-expanding the gateway_downloads

Change-type: patch
See: https://balena.zulipchat.com/#narrow/stream/345889-loop.2Fbalena-os/topic/Python.20SDK.20doesn't.20work.20with.20device.20API.20key

Resolves: #
HQ:
See:
Depends-on:
Change-type: major|minor|patch

Contributor checklist

[ ] Includes tests
[ ] Includes typings
[ ] Includes updated documentation
[ ] Includes updated build output

@balena-ci I self-certify!


WXWork: 我要续费token，客服联系不上

Please make sure you have read the Wechaty Puppet Service: WXWork from Wechaty Official Website before you continue writting this issue.
Question
续费token  ,客服没回复信息

@harrisHxy 续费的token前缀是什么？

我也要续费，为什么客服都不回复

续费的token前缀提供下


add brave-browser

the existing one which is submitted by  @KevinLaMS  is deprecated, this is the new one
Microsoft Reviewers: Open in CodeFlow

https://github.com/microsoft/winget-pkgs/pull/990
https://github.com/microsoft/winget-pkgs/pull/988

#990
#988

@SoftCreatR Oh, sorry, didn't see that


Types of Pointers

Description 📜
This documentation will contain the contents related to Types of Pointers

Domain of Contribution 📊

[x] C/CPP

Mode of Contribution

[x] Documentation

/assign

/assign

/assign documentation


Update linux-fatal-backtrace.swift

"swift/test/Runtime/linux-fatal-backtrace.swift" test case was earlier marked as XFAIL since it was failing when run as root users( #21541 ). However, this test case now passes successfully when run as non-root(normal) user. Submitting this changeset/pull request since the test suite proceeds ahead to other test suites like those for TestFoundation, etc as non-root(normal) user successfully.
Also this test case has some fixes done by users post PR#21541 which may be causing the test case to pass successfully.

@swift-ci please smoke test and merge

@compnerd any updates on this?

@swift-ci please test and merge


What's the difference with the original event-kit?

It’s been years so I dont remember exactly what it was but this repo originated from Github’s Event Kit, it was in copy-pasted from it. I must’ve needed to make some modifications or simplifications at the time.

I am planning some PRs for the original event-kit.
https://github.com/atom/event-kit/pull/52/files
I wanted to see if there are any improvements I can upstream.
I should probably diff the codes.


fix: Handle luis.endpoint empty

Description

Currently the runtime logic is if the luis.endpoint is missing from the setting, just use https://{luisRegion}.api.cognitive.microsoft.com
The runtime should also handle the condition when luis.endpoint does exist but it is an empty string.
Task Item
closes #4026

Screenshots

Coverage remained the same at 55.61% when pulling 886c0e93c0152aa0218344d66478dd653a36a262 on luhan/fixLuis into 5875b2bf991918978928a2a9a8b9e357b2585fc9 on main.


Stuck on booting worker

Following the Readme I'm putting the following on the puppetdb machine. It is separate from the master.
root@puppet-db:~# docker run -it -p 9080:80 -v /etc/puppetlabs/puppet/ssl:/etc/puppetlabs/puppet/ssl \
> -e PUPPETDB_HOST=localhost \
> -e PUPPETDB_PORT=8081 \
> -e PUPPETDB_SSL_VERIFY=/etc/puppetlabs/puppetdb/ssl/ca.pem \
> -e PUPPETDB_KEY=/etc/puppetlabs/puppetdb/ssl/private.pem \
> -e PUPPETDB_CERT=/etc/puppetlabs/puppetdb/ssl/public.pem \
> ghcr.io/voxpupuli/puppetboard
[2022-01-13 10:52:13 +0000] [1] [INFO] Starting gunicorn 20.0.0
[2022-01-13 10:52:13 +0000] [1] [INFO] Listening at: http://<IP_ADDRESS>:80 (1)
[2022-01-13 10:52:13 +0000] [1] [INFO] Using worker: sync
[2022-01-13 10:52:13 +0000] [11] [INFO] Booting worker with pid: 11

It gets stuck on booting here and never goes past it. I see no error messages. From what I understand this Docker image contains PuppetDB and PostgreSQL servers setup and routes traffic from port 80 to Docker container. Is there additional setup required for this to work? What kind of setup?

Hi @Levelleor ! Thanks for reporting the issue and sorry for the trouble.
I am not sure how it got to this as I have been only moving it around and reformating it, but the command we provided in the README in my opinion could never work. :(
tl;dr: try running this command instead, on your PuppetDB server:
docker run -it -e PUPPETDB_HOST=localhost -e PUPPETDB_PORT=8080 --net=host ghcr.io/voxpupuli/puppetboard

...and then in another terminal on the PuppetDB server try curling http://<IP_ADDRESS> .
(Why?
Firstly the volume path in -v in the command that it's the README doesn't match the path of the certs passed later in the env variables (-e).
Secondly without using host networking (--net=host) you cannot reference to the host (PuppetDB server) using localhost inside the container as that means the container there...
Lastly using SSL will not really work because your PuppetDB certname will probably not be localhost and you will get sth like:
ERROR:puppetboard.utils:HTTPSConnectionPool(host='localhost', port=8081): Max retries exceeded with url: /pdb/query/v4/environments (Caused by SSLError(SSLCertVerificationError("hostname 'localhost' doesn't match '<your puppetdb FQDN>'")))

)
Let's see if it helps and we'll move forward from there. :)

Hi @gdubicki, first of all, thank you for updating! Ok, so I do get this error. I didn't really find any documentation as to what PUPPETDB_HOST is supposed to be. Could you shine some light on this?

Lastly using SSL will not really work because your PuppetDB certname will probably not be localhost and you will get sth like:
ERROR:puppetboard.utils:HTTPSConnectionPool(host='localhost', port=8081): Max retries exceeded with url: /pdb/query/v4/environments (Caused by SSLError(SSLCertVerificationError("hostname 'localhost' doesn't match ''")))

Have you tried using the command I suggested above, @Levelleor ? Does it work for you?

@gdubicki yes, I get the issue above from the command you've provided.

Try this then:
docker run -it -e PUPPETDB_HOST=localhost -e PUPPETDB_PORT=8081 -e PUPPETDB_KEY=/etc/puppetlabs/puppetdb/ssl/private.pem -e PUPPETDB_CERT=/etc/puppetlabs/puppetdb/ssl/public.pem -e PUPPETDB_SSL_VERIFY=False --net=host -v /etc/puppetlabs/puppetdb/ssl:/etc/puppetlabs/puppetdb/ssl ghcr.io/voxpupuli/puppetboard

@gdubicki Thank you, it did something. It doesn't look like it's crashing anymore, now it simply says "Service Unavailable". Here're logs from a curl:

/usr/local/lib/python3.9/site-packages/urllib3/connectionpool.py:1013: InsecureRequestWarning: Unverified HTTPS request is being made to host 'localhost'. Adding certificate verification is strongly advised. See: https://urllib3.readthedocs.io/en/1.26.x/advanced-usage.html#ssl-warnings
warnings.warn(
WARNING:charset_normalizer:override steps (5) and chunk_size (512) as content does not fit (44 byte(s) given) parameters.
INFO:charset_normalizer:ascii passed initial chaos probing. Mean measured chaos is 0.000000 %
INFO:charset_normalizer:ascii should target any language(s) of ['Latin Based']
INFO:charset_normalizer:We detected language [('English', 1.0), ('Dutch', 1.0), ('Polish', 0.9412)] using ascii
INFO:charset_normalizer:ascii is most likely the one. Stopping the process.
ERROR:pypuppetdb.api.base:PuppetDB is currently down. Try again later. localhost:8081 over HTTPS.
ERROR:puppetboard.utils:503 Server Error: Service Unavailable for url: https://localhost:8081/pdb/query/v4/environments
<IP_ADDRESS> - - [18/Jan/2022:17:14:20 +0000] "GET / HTTP/1.1" 503 262 "-" "curl/7.68.0"

Sorry but at this point you need to check what is the proper port and protocol (HTTP/HTTPS) for your PuppetDB API and update one of the commands I gave you accordingly.
The first command I gave you is for plain HTTP and the second for HTTPS.

@gdubicki What do you mean the proper port? Where does that come from? Do I need to setup PuppetDB manually as well for this to work?

You need to already have PuppetDB itself set up and working, if that's what you meant. That is a requirement for using Puppetboard as its only a UI for the former.

Oh.. I see. I though this would install PuppetDB and PostgreSQL within a container without any additional setup required. Well, I guess back to troubleshooting PuppetDB and this isn't relevant anymore.

Ok, I don't know what's the issue now but I got PuppetDB up yet now it says this:

404 Not Found
Not Found
The requested URL was not found on the server. If you entered the URL manually please check your spelling and try again.

The PuppetDB is now working and I am lost again to finding the root cause.

Is your PuppetDB working and your nodes are publishing reports to it? Do you have nodes in the default environment "production" ? I am asking because perhaps you are hit by #515.


Hotfix for KMeans single-point predict_inplace impl

Make predict impl for arrays more flexible and remove bad assert on k_means predict_inplace impl

Codecov Report

Merging #154 (e869378) into master (473e7dd) will increase coverage by 0.02%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master     #154      +/-   ##
==========================================
+ Coverage   59.44%   59.46%   +0.02%
==========================================
  Files          84       84
  Lines        7730     7730
==========================================
+ Hits         4595     4597       +2
+ Misses       3135     3133       -2

Impacted Files
Coverage Δ

...gorithms/linfa-clustering/src/k_means/algorithm.rs
54.97% <100.00%> (+1.06%)
:arrow_up:

src/dataset/impl_dataset.rs
43.07% <100.00%> (ø)

...rithms/linfa-trees/src/decision_trees/algorithm.rs
52.31% <0.00%> (-1.43%)
:arrow_down:

...lgorithms/linfa-clustering/src/optics/algorithm.rs
64.11% <0.00%> (+2.12%)
:arrow_up:

Continue to review full report at Codecov.

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


Test2 does not pass even with correct code

I was playing around with learntris to learn as well as to contribute to this effort. I have a program which prints out the '.' in the correct format. I verified this from the command line. The correct code is here
http://pastebin.com/jEBVC987
But test2 does not pass

Thanks for trying learntris! :)
Your implementation is meant to read the commands from standard input, not the command line. The idea is you should be able to type the commands manually yourself to test things interactively. And also, it's a game, so it has to be a loop where the player is sending input dynamically in response to the output.
Make sense?

yes. indeed.  This one passed. http://pastebin.com/mh2SDycj


Name of the Stream manager name cannot hold .log

If I create a Stream with the name:
filter.log.day.machine.txt
No error is generated during the creation but when we try to append a message an error is logged:
Error: java.io.IOException: java.util.concurrent.ExecutionException: java.nio.file.NoSuchFileException: /var/greengrass/streams/filter.index.-day.machine.txt/0000000000000000000.index
That breaks the StreamManager component and does not allow us to make a new deployment, looks like the core tries to access to that folder that doesn't exist

Hello,
Can you please provide the full log which generates this error?

Hi @MikeDombo  thanks for your quick answer.. let me attach the logs and the information that you request.
GG V2 - amazon/aws-iot-greengrass:2.5.3-0
Component Name: aws.greengrass.StreamManager
Version: 2.0.14
State: RUNNING
aws.greengrass.StreamManager - Copy -  Error.log Main error that locks the deploy for the stream manager.
I solved it replacing the main folder:
sudo mkdir /var/greengrass/streams
sudo chown ggc_user /var/greengrass/streams
sudo chmod 700 /var/greengrass/streams
That's allows me to deploy again my component
And my lambda component' log:
gg-lambda-logs-rsalazar_2022_01_27_20_3.log

Please provide the configuration of the stream manager component too. Stream manager does not write to /var/greengrass/streams by default. So that means that you must have set that to be the Stream manager directory, right? Why have you set it to that location, is there a particular reason why the default location does not work?

Main error that locks the deploy for the stream manager.

What do you mean that it "locks the deployment for stream manager"? When a component is in the BROKEN state, you can absolutely still deploy, however, if it remains broken even after the deployment, the deployment will rollback to the previous state if configured to. The default is to rollback when a deployment fails, however you may choose to not rollback on failure.

Stream Manager config:
await client.createMessageStream(
     new MessageStreamDefinition()
       .withName(streamName)
       .withStrategyOnFull(StrategyOnFull.OverwriteOldestData)
       .withPersistence(Persistence.File)
       .withFlushOnWrite(false)
       .withMaxSize(268435456)
       .withStreamSegmentSize(16777216)
   );

I don't know the reason why the default location does not work, but you are right about the rollback, it's my default setting that makes the rollback but the deployment just logs that the Stream Manager component is broken, and due the deployment fails it tries to makes the rolleback but there is not healthy component to run again, so I was stuck and my core was unhealthy with the broken componet. Once that I changed the default folder, it allows me to deploy a healthy component.

For the config, I mean the configuration of the stream manager component itself. You said that you changed the directory structure. Please provide the configuration which you were using that did not work as well as the one which did work.
The missing file is not really a missing file, but more likely the missing path. The path is created when the stream is created using createMessageStream. Did you delete any directories, or move them manually?

Sorry my bad, I did not change the default folder, I just create the folder and add grants to it.
sudo mkdir /var/greengrass/streams
sudo chown ggc_user /var/greengrass/streams
sudo chmod 700 /var/greengrass/streams

The configuration of my component is the default:
{
  "STREAM_MANAGER_ENABLE_LOCK_ON_METADATA_STORE": "false",
  "STREAM_MANAGER_AUTHENTICATE_CLIENT": "true",
  "STREAM_MANAGER_EXPORTER_THREAD_POOL_SIZE": "5",
  "port": "",
  "STREAM_MANAGER_SERVER_PORT": "8088",
  "JVM_ARGS": "",
  "STREAM_MANAGER_STORE_ROOT_DIR": ".",
  "LOG_LEVEL": "INFO",
  "STREAM_MANAGER_EXPORTER_MAX_BANDWIDTH": "2147483647",
  "STREAM_MANAGER_EXPORTER_S3_DESTINATION_MULTIPART_UPLOAD_MIN_PART_SIZE_BYTES": "5242880"
}

When a directory is provided, it has to be setup correctly, meaning that the user running Stream manager (in your case ggc_user) needs permission on the directory. Due to how linux works, the user also needs read and execute permissions on all parent paths ie. /, /var, /var/greengrass, and /var/greengrass/streams.
Everything is currently working for you, is that right?

Yes.. right now is working with the new directory and the grants that I setup.
Also I changed the name of my Stream from "filter.log.filename.txt" to "f-log.filename.txt" my lambda component works properly, I'm able to create the Stream and append a message.

Now that the directories are working properly even with that fix, you say the stream name filter.log.filename.txt would cause issues? Is that something that you've tried?

I have verified the issue. We will work to fix this in stream manager, until then please avoid using a stream name with .log

Sorry this fell through the cracks and I forgot to close it. This issue was resolved in newer versions of stream manager