POST doesn't close the connection when 204 response used

What you did:
Created a POST route
{     "id": "8e54c04a-21fd-4cb3-b8de-1aa5a9ef988e",     "route": "/events",     "httpMethod": "POST",     "statusCode": "204",     "delay": "0",     "payload": {         "success": true     },     "headers": [         {             "id": "6ffb195d-c434-46da-a08c-52090415c949",             "header": "Retry-After",             "value": "60"         }     ],     "disabled": false }
that responds with a HTTP 204 with a simple body of { success: true } and posted:
curl --request POST '<IP_ADDRESS>:3000/events' --header 'Content-Type: application/json' --data-raw '[{"eventId":"fbf1de19-8629-45d3-ad0f-34b8e17d594f","sessionId":"07726e3d-68ed-49a2-bb37-d1372e941191","dateTime":"2020-08-14T01:45:44.975Z","eventType":"App Launched","category":"engagement","latitude":40.4543,"longitude":41.4563},{"eventId":"37314774-d52b-4219-b5c4-e3b2c14aeda0","sessionId":"48830e55-33b2-4a8e-b5c7-710b85b44bf5","dateTime":"2020-08-14T01:56:53.220Z","eventType":"view cart","category":"engagement","latitude":40.4543,"longitude":41.4563,"sku":"abc123","price":10.95},{"eventId":"6c8a2370-0fb0-4c47-8914-11a8e2ffe47f","sessionId":"48830e55-33b2-4a8e-b5c7-710b85b44bf5","dateTime":"2020-08-14T01:57:23.341Z","eventType":"App Launched","category","engagement","latitude":40.4543,"longitude":41.4563}]'
What happened:
The body isn't delivered for ~90 seconds -- my connection timeout on the client is set to 30 seconds.
Problem description:
Because it should immediately respond and close the connection?
Suggested solution:
Changing nothing other than the response code back to HTTP 200 fixes the problem (the route responds instantaneously), but I would like to emulate several of the available responses, and I specifically need the 204 response for this POST :)

Hey @billmote, i'm not the maintainer but just stumbled upon this issue.
while I'd agree that a timeout is suboptimal in this situation, your desired behaviour is kinda confusing as well.
204 is explicitly for situation where you do not have a body.
you should use another status code if you wish to respond with a body, for example 200 OK,

Interesting @wohlben.  I will raise that with the people writing the endpoint.  204 shouldn't be an issue though (ref. https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/204).  It just seems odd that it holds the connection open for a 204 and not a 200.  In both cases the work is "done."

eh, yes. thats exactly the documentation i linked earlier, and the source of my quotes as well.
for what its worth: i wasn't able to reproduce your timeout issue on my end. though mockIt never responded with a body either, only with the explizit status code, which is 204 No Content
$ curl -X POST localhost:3000 -vs
* Rebuilt URL to: localhost:3000/
*   Trying ::1...
* TCP_NODELAY set
* Connected to localhost (::1) port 3000 (#0)
> POST / HTTP/1.1
> Host: localhost:3000
> User-Agent: curl/7.60.0
> Accept: */*
>
< HTTP/1.1 204 No Content
< Access-Control-Allow-Origin: *
< x-api-key: testing123
< Content-Type: application/json; charset=utf-8
< Content-Length: 16
< ETag: W/"10-oV4hJxRVSENxc/wX8+mA4/Pe4tA"
< Date: Sun, 16 Aug 2020 19:17:28 GMT
< Connection: keep-alive
<
* Connection #0 to host localhost left intact

I worked around the issue by adding a byteCount check before calling readAll(), which is what was getting hung up on the empty response.  End of the day, makes my networking stack more resilient.  Still talking through it with the service team, but here's my current config if you're interested:
{             "id": "8e54c04a-21fd-4cb3-b8de-1aa5a9ef988e",             "route": "/events",             "httpMethod": "POST",             "statusCode": "204",             "delay": "500",             "payload": {},             "headers": [                 {                     "id": "6ffb195d-c434-46da-a08c-52090415c949",                     "header": "Retry-After",                     "value": "5"                 }             ],             "disabled": false         }

@billmote wonder if it's worth adding this to the docs? What do you think?
Sounds like you got a work around, are you happy for me to close this issue?

I did work around it by not including a body IIRC.  Anyone that has this
issue will probably find this.  Docs seem unnecessary.
On Tue, Nov 24, 2020 at 3:03 AM David Boyne<EMAIL_ADDRESS>wrote:

@billmote https://github.com/billmote wonder if it's worth adding this
to the docs? What do you think?
Sounds like you got a work around, are you happy for me to close this
issue?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/boyney123/mockit/issues/80#issuecomment-732725895,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAMSPPANVGJORWADCSBGLCLSRNSEDANCNFSM4P7BHPBQ
.


Struct2xas 2023.3.x

Some improvements and bug fixes on struct2xas.
@newville if we release a patched version for 0.9.72 it may be good to include this now, otherwise I will wait for 0.9.73

@maurov This seems okay to me.  It seems like the main change is to add the sorting of the sites -- is that correct.  Should we just merge?
I think my main concern would be the use of Black styling, which makes it sort of hard to tell what the real changes are.
Not a fan of Black.

@newville

@maurov This seems okay to me. It seems like the main change is to add the sorting of the sites -- is that correct. Should we just merge?

The main change is actually of not using CifParser to instantiate the Pymatgen structure object
            self.struct = Structure.from_file(self.file)
            #self.struct = self.cif.get_structures()[0]  #: NOT WORKING!

We need more testing on the FDMNES side and I would keep this unmerged unless you are planning a release soon.

I think my main concern would be the use of Black styling, which makes it sort of hard to tell what the real changes are. Not a fan of Black.

OK, I understand and I apologize for it. In my opinion, using a code formatter is important to uniform the way we code and it comes from free in most editors. If you do not like black, do you prefer something else?

@maurov Oh, that's all OK.  I'm not in a rush to push out 0.9.73, mostly because of other commitments over the next week or two.   Maybe we can aim for December 1. At the rate we're going, I would be willing to say we generally want releases every 60 to 90 days, but that's sort of a rough target, like if we've gone 90 days without a release, we should probably start thinking that we should get a release out soonish.
For formatting, I think I prefer PEP8 recommendations and being sensible.  My feelings on Black are that they sort of made up the existence of formatting arguments and then proposed an absurd set of choices with the goal of "ending the endless discussions". But, there were not endless discussions about formatting until Black imposed its unsolicited opinions, bad choices, and inflexibility-as-an-alleged-feature.

@newville since you are planning to release 0.9.73 soon, I propose to merge these few changes in struct2xas. I was planning to work more on it, but I am fully busy on other tasks for the moment.

@maurov Thanks -- I'll merge this and describe it as "continued improvements"!


Streamline fetch lifecycle and fix fetching Subject from queue

PR Overview

This PR handles two major issues.
First, the fetching Subject-Classification lifecycle has been refactored.

Instead of createClassification()  triggering inside ClassifierContainer as it waits for a new Subject to come in...
... createClassification() is now triggered directly after a Subject is successfully fetched within its Duck. i.e., we're removing the 'React component monitoring for changes' bit.

Second, this PR fixes an issue where you can't get the third Subject from your queue.

Issue: after submitting the Classification for the second Subject in your queue, you can't load any more Subjects - the system crashes.
Analysis: In fetchSubject(), there's an if-else fork that either A. fetches a new Subject Queue and the latest Subject on that queue, or B. fetches the next Subject in an existing queue. Path B was set up in such a way that not all the necessary Subject information was passed to the reducer.
Solution: fixed that.

@wgranger : Wait I just realised this, have we accounted for Subject Queues that are empty? i.e. no next subject?
This PR replace PR #113 which wasn't a good enough a fix, alas.
Status
@wgranger Ready for review

A rebase will be needed here before merge.

LGTM. Ready to merge after rebased.

A rebase is being force-pushed, invalidating previous incarnations of this branch. Please be prepared.
Also, note that I may have found another weird issue where this PR fails on the newly re-enabled "Random Subject Set" option.

@wgranger So, right, at the moment of this writing...

In the master branch, if you submit (click Done) a few times, you'll eventually run into an error (the Subject Queue issue that this PR fixes).

This applies whether you're on a specific Subject Set or a random one - there's one Subject Set that has more than 1 item in it that lets you see the error.

In this fix-subject-queue-fetch,

If you choose a specific Subject Set from the Home page, you can submit forevermore.
If you choose a random Subject Set, you can't even submit once, because the Workflow ID isn't set.

That's a hint on where the issue might be - the is Workflow ID set in the usual manner if we go with the random route, correct?

Scratch that, this appears to be random - I'm testing on an incognito window.

The error I see; can't seem to find the conditions that trigger it, though.

Are you talking about workflow version can't be blank?

Yeah, and BLARGH I now realise what it is.
God freaking dangit... there's a proper chain of events that need to trigger. Create Classification must occur after Fetch Subject AND Fetch Workflow succeed. I've only accounted for Fetch Subject, what.

Wait, wait, no, maybe I'm just insane... not sure how this got into the code: dispatch(createClassification(createClassification()));

This bring up a thought I had earlier. I believe the way PFE works is that the app waits until all items are collected before proceeding to load anything. I believe that's done in the ProjectPageControlled here, which is something we can investigate implementing?

I saw that crazy line above but thought you knew what you were doing and the code seemed to operate fine with it. I should've tested it more in the review. We're both going a bit stir crazy as this project nears completion.

Actually, it's a combination of I'm insane, as well as spot on on the core problem. Take a look at this...

Notice that CREATE_CLASSIFICATION triggers before FETCH_WORKFLOW_SUCCESS, leading to an unfortunate incident where submitClassification() triggers without having a valid workflow data to construct it.
EDIT: based on what you said, the ProjectPageControlled seems to be on the right path. We need to block any action on the page until all resources are loaded. Worth implementing? Yes. Do we have time? Hmm-

PR Update

SURPRISE, I modified App.jsx
The whole website now just shows a "Loading..." message while it waits for both the Project and Workflow Panoptes resources to load.

Future TODO: handle error statuses as well.
Future TODO: Make that Loading... message look good.

Status
@wgranger This is now ready for a re-review. The wait-until-all-resources-have-loaded is basically the ultimate way of us correctly chaining the resources that depend on one another. Despite the very, very few lines of code in this PR, it does feel somewhat like a sledgehammer... but it is effective.

Bonus clarification: the reason master doesn't have that problem I discovered is because, when the ClassifierContainer component was 'managing' the fetch life cycles, it basically listened for every update and triggered createClassification() whenever all the pieces were in place.
componentWillReceiveProps(nextProps) {
  if (nextProps.currentSubject && nextProps.workflow && !this.props.classification) {  //Note that it checks for workflow here
    this.props.dispatch(createClassification());
  }
}

The method of chain-of-fetch-lifecycles method I'm proposing in this PR separates those fetch lifecycles from the components (which I think is a good idea) but the price to pay is that it requires a more acute awareness of the order required of things. (Which has been flarrrgh.)
I should have noted the nextProps.workflow check though, that one was on me to be more aware.

I'm going to merge this under the assumption we will address error handling and the loading message in time for beta. It shouldn't be a huge problem to solve, but it is worth discussion.


[FR] - Number of coders

How come you have got only 4 developers for such large project?
Ethereum got 2 000 developers working around the clock
What is happening?

Cardano Community response: What makes you think this? There are hundreds developers and scientists working on Cardano.
Please close this as this is not relevant...

I propose to increase dev count by x10
plenty of money at CEO

it has been 6 months+ but trezor t hardware wallet passphrase is still not working, which is essential key core element

How come you have got only 4 developers for such large project?

That is not correct, for a number of reasons:

There have been over 70 contributors to this repo, the vast majority of them employed by IOHK.
This repository is not the whole project. This repository uses a number of other repositories as libraries and those other repositories also have large contributor lists.

Ethereum got 2 000 developers working around the clock

Maybe, but how effective are all those developers? It has been known since the 1970s (see the book The Mythical Man Month) that simply adding more developers (especially by ridiculous increases like 10x) nearly always makes development slower.
That said, support for things like Trezor is one of the few things that actually could be done by developers not currently engaged in the project.

social media on github , any reason this "issue" is still open 😄

Increasing number of developers doesn't scale linearly. It will simply increases the cost of coordination that, given the nature of software development, can be a huge problem. Also not to forget that lines of code is actually a cost. Somebody needs to maintain them. Ironically as it seems, developer actually need to write less code to achieve more, so that it does not build up additional complexity due to maintenance.
Oh hey wait... am i in reddit?

Sorry, I meant to close it.


Will need to replace grunt-usemin eventually

Feature Request
Desired behaviour
https://libraries.io/npm/grunt-usemin appears to be unmaintained. Will need to find an alternative

Superseded by ng


add missing PHONENUM and fix saving phone number

http://issues.shopware.com/issues/PT-6714

Hi Andre,
thanks for your PR. if have scheduled the linked ticket. we will have a look at it in the next PayPal sprint.
best regards

hey @hlb-schmidt
after two years... sorry for that! :see_no_evil:
thanks for your contribution anyway! :+1: :blue_heart:
your fix will be part of the next release


⚠ Bofrost.be has degraded performance

In 1691624, Bofrost.be (https://www.bofrost.be) experienced degraded performance:

HTTP code: 200
Response time: 870 ms

Resolved: Bofrost.be performance has improved in 9789424.


[REEF-204] Fixed failure to react to misconfigured Hadoop 2.6 clusters.

This addressed the issue by making sure that both YarnConfiguration.YARN_APPLICATION_CLASSPATH  and DEFAULT_YARN_CROSS_PLATFORM_APPLICATION_CLASSPATH are configured,   otherwise we use legacy CLASSPATH. We also make sure that HADOOP_CONF_DIR is in the prefix.
JIRA: REEF-204

I'll review this.


[OIDC] The disable of alternate identifier is not working

Describe the Issue:

Before enabling the subject identifier, the subject is the user id without the domain or organization. When the user enables it and modifies it, the disabling doesn't make sense. Because disabling it is not bringing it to the statue before enabling it.

How To Reproduce:

Navigate to the User Attribute section of an OIDC application
Enable the alternate subject identifier and change the config > verify the sub in id token and userinfo endpoint
Disable the alternate subject identifier and verify the behaviour > the sub in id token remains the enabled config state.

Expected behavior:
If we are providing a behaviour to disable, it should be reverting the config to its default state , the user is should be the subject identifier.

Closing this issue because the master PR is merged


Manage static routes

https://docs.opnsense.org/development/api/core/routes.html

done in https://github.com/andeman/opn-cli/pull/28


Update scene_exceptions.json #221

Alternate names for Code Geass
Season 1 and 2 names for Code Geass
Season 2 names for Mushi-shi
Corrected syntax

Thanks for the pull request! Before a real human comes by, please make sure your PR has all of the below criteria checked

[x] Give a description on what the PR is for.
[ ] Make sure your PR is based on the DEVELOP branch
[x] Don't send big changes all at once. Split up big PRs into multiple smaller PRs that are easier to manage and review

Please make sure you also read contribution guide and followed all of the steps.
Thanks!

I'm seeing "Make sure your PR is based on the DEVELOP branch" in the criteria, but couldn't see that there is currently a develop branch available.

Ignore that, its the same message we use for the main repo. Just some nonsense.


Thank you

Tq for the great library. Does it gives only 2 values CO2 and TVOC?
CO2 concentration : 16848 ppm
TVOC concentration :<PHONE_NUMBER> ppb
I think something wrong it keeps giving this value. How many pins do i have to connect? I am using WEMOS D1 Mini

Hello mshaz, I had the same problem - I use Wemos D1 Pro and it seems this problem is related to usage of this sensor together with ESP8266, I use this basic sketch from Sparkfun  - I was able to detect I2C device fine, read values from registers such as STATUS, HW_ID, HW_VERSION fine but problem starts when I try switch the CCS811 state from boot to application mode (APP_START). My Wemos crash to soft-reset and I2C connected devices were not detected anymore.
I found out this discussion  and it seems ESP8266 is very sensitive to power and this sensor takes up to 30mA during measuring (application mode). See datasheet here:
Please let me know if you solved this issue somehow. Right now I'm using Arduino Uno just to test the sensor and it seems the sensor is working fine.

Thank you for your reply. I guess it won't work on nodemcu too?

Probably not but test it, I will let you know if it is working fine with ESP32 (now I'm waiting for the new Lolin32 board) I can also test it with Raspberry Pi 3. Definitely it is working fine with Arduino Uno and Mega (but I need something with wifi...)
What sensor board are you using? I have this combo one: link

CFSUNBIRD CCS811  same thing with you. Would be nice if it works on WEMOS D1 coz i nd something small with WIFI too.  I m waiting for my Raspberry pi Zero to arrive thru mail . Not sure how to make it work with a Pi. Seems difficult to get Pi Zero and Zero W here in my country.

Where are you from? I'm also thinking about RPi Zero.

I am from Malaysia. I found one local supplier for this but i can only buy a unit as it is limited.  Do you know where i can get more of RPi Zero and Zero W cheaply. Do let me know your progress with  CCS811, I was thinking of making wearables with this that's why i chose Wemos D1 . I tried other codes from other sources also but not working. Almost given up on this.

I bought RPi 3 from local distributor for 44 USD and I see Zero for 15.3 USD here in Czechia. But maybe try some cheap chinese shops (Aliexpress, Banggood...)
That would be cool to have it as wearable! I was working on static air quality detector for meeting room. I'll try to solve it somehow...don't give up yet :) It seems the sensors returns HEATER_SUPPLY error which could confirm the reason. Qustion is if this problem couldn't be solved by adding of capacitor or switching of measurement cycle...I'll let you know if I discover something.

Hi there, I think I've just solved it...at least my own sketch returns promising data...
I made sketch for Wemos D1 Pro and script for RPi (Python). Let me know if you want to test it.

Cool. Can i test it for Wemos D1 and RPi too. I just got my RPi Zero. I will update you with the results. Thank you

I made this using MAX30100 and Wemos D1 Mini. Readings are not consistent. Could it be same issues with current like  CCS811.

cool :-) actually the problem was with initiating I2C communication...where do you want to post the scripts? e-mail?

yes please at<EMAIL_ADDRESS>Thank you.

xxlukas42!
Please send me too the sketch for wemos d1.
Thank You very much!!
email<EMAIL_ADDRESS>

Hi, I am also struggling with LGAQS-HT01 a combination of CCS811 and SI7021, typically the same as yours xxlukas42. I can run it on Arduino, I can get values for Humidity and Temp from SI7021 on Wemos but I cannot run CS811 on Wemos. Please help or send the code to me at<EMAIL_ADDRESS>Thanks

Hello guys, I'm sending you to your emails latest version of my source-just note this is only beta version and I'm still testing it (that is the reason why the code is not public yet) so please let me know your observations. Thank you.

Hello Lukas, i recently bought wemos D1 pro and CCS811. I have the same problems with the i2c.
Can you send me your code, i will really appreciate it. My email is<EMAIL_ADDRESS>Thanks

I use the CCS811 with an ESP8266 get perfect values, reacting to breathing very quickly.
I found out that after WAKE is brought LOW, it needs about 50us before you can do I2C transaction. So in the Lib I changed all calls to digitalWrite in digWriteWait and added this:
void CCS811::digWriteWait(uint8_t WAKE_PIN, bool VAL) {
  digitalWrite(WAKE_PIN, VAL);
  delayMicroseconds(60);
}

Now it works like a charm.
DJ

Hi DJ!
Could You share the working library?
Thank You!
Peter
----- Original Message -----
From: djdehaan
To: AKstudios/CCS811-library
Cc: digiservice2001 ; Comment
Sent: Thursday, June 15, 2017 8:28 PM
Subject: Re: [AKstudios/CCS811-library] Thank you (#3)
I use the CCS811 with an ESP8266 get perfect values, reacting to breathing very quickly.
I found out that after WAKE is brought LOW, it needs about 50us before you can do I2C transaction. So in the Lib I changed all calls to digitalWrite in digWriteWait and added this:
void CCS811::digWriteWait(uint8_t WAKE_PIN, bool VAL) {
digitalWrite(WAKE_PIN, VAL);
delayMicroseconds(60);
}
Now it works like a charm.
DJ
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.

Attached:
CCS811-library-update-DJ.zip

Still can not read right values...
Please help me with the sketch what U use, and wire connections.
Thank You!!!
----- Original Message -----
From: djdehaan
To: AKstudios/CCS811-library
Cc: digiservice2001 ; Comment
Sent: Thursday, June 15, 2017 10:07 PM
Subject: Re: [AKstudios/CCS811-library] Thank you (#3)
Attached:
CCS811-library-update-DJ.zip
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.

Sorry, I don't reset the sensor after use your modified library.
I can read correct values now... It's working well!!!
Thank You!!
----- Original Message -----
From: djdehaan
To: AKstudios/CCS811-library
Cc: digiservice2001 ; Comment
Sent: Thursday, June 15, 2017 10:07 PM
Subject: Re: [AKstudios/CCS811-library] Thank you (#3)
Attached:
CCS811-library-update-DJ.zip
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.

First I checked if it found the I2C address of the CCS811. Attached .ino does search and found mine only after I connected WAKE to D0 of the Wemos.
I2CScanner.zip

Hi DJ,
I used your code with the CCS811_test.ino and get some very high values of CO2 in 6000 and VOC in millions. Where could i go wrong? I deleted the earlier master library of CCS811 and added your new library as well. Please help.
On Friday, June 16, 2017 1:38 AM, djdehaan<EMAIL_ADDRESS>wrote:

First I checked if it found the I2C address of the CCS811. Attached .ino does search and found mine only after I connected WAKE to D0 of the Wemos.I2CScanner.zip—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.

Did you run the I2CScanner script and did it find the CSS811? With what address?

Thanks. I have now run the I2C Scanner and its giving many errors. I tested it about a week ago and it was giving me 0x40 and 0x5A as addresses. Now its all errors, I checked the connections and they are fine. Where could i go wrong?
On Friday, June 16, 2017 2:22 AM, djdehaan<EMAIL_ADDRESS>wrote:

Did you run the I2CScanner script and did it find the CSS811? With what address?—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.

Sorry, I just checked, the ground pin was not connected and now i get this
I2C device found at address 0x40I2C device found at address 0x5a
Am testing the CCS811 text ino and will get back.
On Friday, June 16, 2017 2:35 AM, riaz ahmed<EMAIL_ADDRESS>wrote:

Thanks. I have now run the I2C Scanner and its giving many errors. I tested it about a week ago and it was giving me 0x40 and 0x5A as addresses. Now its all errors, I checked the connections and they are fine. Where could i go wrong?
On Friday, June 16, 2017 2:22 AM, djdehaan<EMAIL_ADDRESS>wrote:

Did you run the I2CScanner script and did it find the CSS811? With what address?—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.

Hi there, i've just read the forum and saw you manage it somehow. I had the same issue with not responding sensor on I2C scanner and it helps me simply disconnect VCC from the sensor and connect it again.

Hi, again. I got the I2C scanner to give 0x40 and 0x5A as addresses. But when I run CCS811 text .ino i get these results:
Error: Incorrect Hardware ID detected.Initialization failed.CO2 concentration : 65028 ppmTVOC concentration :<PHONE_NUMBER> ppb
pl help.
On Friday, June 16, 2017 1:38 AM, djdehaan<EMAIL_ADDRESS>wrote:

First I checked if it found the I2C address of the CCS811. Attached .ino does search and found mine only after I connected WAKE to D0 of the Wemos.I2CScanner.zip—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.

Like xxlukas42 says: reset or power-off/on the device. I found that trick too. Am now looking into a routine that will do an automated hardware reset if the hardware ID is 0xFF.

HI, I guess your code wants the CCS811 WAK pin to be as shown here https://learn.sparkfun.com/tutorials/ccs811-air-quality-breakout-hookup-guide However my CCS811 is from Logoele called LGAQS-HT01 and it has 10 pins as here http://www.sereslink.com/UpFiles/image/20160826172927_9272.jpg Can you please identify which one is WAKE?
On Friday, June 16, 2017 11:36 AM, djdehaan<EMAIL_ADDRESS>wrote:

Like xxlukas42 says: reset or power-off/on the device. I found that trick too. Am now looking into a routine that will do an automated hardware reset if the hardware ID is 0xFF.—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.

Through elimination I would say C2D, but I cannot think a meaning of C2D like WAKE. Please check the documentation. The WAKE pin puts the CCS811 in sleep with very low power consumption. It is a pin directly on the CCS811 itself.

Hi,
I read at an Arduino forum where martinayotte  explains in a discussion on some I2C sensors that you need to add Wire.begin(sda_pin, sclp_in) in order "To make it working on ESP8266, it needs to provide the pin numbers you are using " and I did that and bingo! it works straight away. So for people like me I am quoting the modified code here:
/**/#include <Wire.h>
#include <CCS811.h>
#define ADDR      0x5A//#define ADDR      0x5B#define WAKE_PIN  4
CCS811 sensor;
void setup(){  Wire.begin(D2, D1);
  Serial.begin(115200);  Serial.println("CCS811 test");  if(!sensor.begin(uint8_t(ADDR), uint8_t(WAKE_PIN)))    Serial.println("Initialization failed.");}
void loop(){   //sensor.compensate(22.56, 30.73);  // replace with t and rh values from sensor  sensor.getData();  Serial.print("CO2 concentration : "); Serial.print(sensor.readCO2()); Serial.println(" ppm");  Serial.print("TVOC concentration : "); Serial.print(sensor.readTVOC()); Serial.println(" ppb");  Serial.println();  delay(2000);}
On Friday, June 16, 2017 3:55 PM, djdehaan<EMAIL_ADDRESS>wrote:

Through elimination I would say C2D, but I cannot think a meaning of C2D like WAKE. Please check the documentation. The WAKE pin puts the CCS811 in sleep with very low power consumption. It is a pin directly on the CCS811 itself.—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.

Thanks AK, one issue remains and i hope you can fix it. The Logoele LGAQS-HT01 has two sensors, CCS811 and SI7021, the later for temp and humidity. When I write a code using the CCS811 test ino with one for SI7021 it seems there is a cinflict. SI7021 uses Wire.begin() while CCS811 uses Wire.begin(Sda,Scl). It gets compiled but gives odd values for SI7021. Can u help?
Get Outlook for Android
On Sat, Jun 17, 2017 at 10:53 AM +0500, "Akram Ali"<EMAIL_ADDRESS>wrote:
@djdehaan thanks for sharing the fix! I've now updated the library with a slight modification to your code. Hopefully it should work well for more people now.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.

@ahmedriazku I left the call to Wire.begin() in the code as this library is intended to be easily used with Arduino boards and the CCS811 sensor. Any other board or sensor would require modification of the code.
As suggested above, you can comment out the call to Wire.begin() in the library and add your own calls in the main code to make it compatible with other devices. I've not tried the sensor you mentioned, but I tested the code with breakouts for CCS811 and Si7021 on the same circuit and it runs fine.

Hi, I have now written a code that does not use the CCS811 library. It runs fine until I unplug the Wemos and when I replug and reload the code it gives odd values for CO2 and TVOC. Can you suggest what could be wrong. It appears that unplugging causes the SDA to be high and could not be brought to low until one uses another program, like yours, to make the SDA low. The attached code is:
#include <Wire.h>#define CCS811ADDR 0x5A  //#define ADDR      0x5B  CCS811 I2C address is 0x5A or 0x5B#define SI7021ADDR 0x40 // SI7021 I2C address is 0x40(64)
float humidity = 0;float temp = 0;float CO2 = 0;float TVOC = 0;#define WAKE_PIN D0
void setup()  {    Wire.begin(D2, D1); //define the SDA (D2) and SCL(D1) pins for Wemos/Nodemcu/Esp8266 setup
    Serial.begin(9600);    pinMode(WAKE_PIN, OUTPUT);
    digitalWrite(WAKE_PIN, 0);    delay(70);  Wire.beginTransmission(0x5A); // least significant bit indicates write (0) or read (1)  Wire.write(0xF4);  Wire.endTransmission();  digitalWrite(WAKE_PIN, HIGH);delay(60);    // sensor.begin(uint8_t(ADDR), uint8_t(WAKE_PIN));//    Serial.println("Initialization failed.");  }
void loop()  {
delay(70);
// temp and humidity part of loop
    // Code for data access from SI7021     unsigned int data[4];    digitalWrite(WAKE_PIN, 0);    delay(60);    Wire.beginTransmission(SI7021ADDR);    Wire.write(0xF5); // Trigger humidity measurement command to register 0xF5 , its 2 byte register    Wire.endTransmission();    delay(500);       Wire.requestFrom(SI7021ADDR, 2); // Request 2 bytes of humidity data      if(Wire.available() == 2)       {        data[0] = Wire.read();        data[1] = Wire.read();      }      // Convert the humidity data      float humidity  = ((data[0] * 256.0) + data[1]);      humidity = ((125 * humidity) / 65536.0) - 6;
    Wire.beginTransmission(SI7021ADDR);    Wire.write(0xF3); // Trigger temperature measurement command to 0xF3    Wire.endTransmission();    delay(500);     Wire.requestFrom(SI7021ADDR, 2); // Request 2 bytes of temp data      if(Wire.available() == 2)      {      data[0] = Wire.read();      data[1] = Wire.read();      }     // Convert the temp data        float temp  = ((data[0] * 256.0) + data[1]);        float celsTemp = ((175.72 * temp) / 65536.0) - 46.85;        float fahrTemp = celsTemp * 1.8 + 32;     // Output temp and humidity data to serial monitor      Serial.print("Humidity : ");      Serial.print(humidity);      Serial.println(" % RH");      Serial.print("Temperature : ");      Serial.print(celsTemp);      Serial.println(" C");
      digitalWrite(WAKE_PIN, 1);  delay(60);    // Code for CCS811 to get CO2 and TVOC values      digitalWrite(WAKE_PIN, 0);      delay(60);      Wire.beginTransmission(CCS811ADDR);      Wire.write(0x02);   // Trigger CO2 and TVOC measurement command  0x02 , its a 4 byte register      Wire.endTransmission();           Wire.requestFrom(CCS811ADDR, 4); // Request 4 bytes of CO2 and TVOC data        if(Wire.available() == 4)        {        data[0] = Wire.read();        data[1] = Wire.read();        data[2] = Wire.read();        data[3] = Wire.read();        }        // Convert the data by shifting the registers 8 bit        float CO2 = (data[0]<<8) + data[1];        float TVOC = (data[2]<<8) + data[3];      // Output temp and humidity data to serial monitor      Serial.print("CO2 : ");      Serial.print(CO2);      Serial.println(" ppm ");      Serial.print("TVOC : ");      Serial.print(TVOC);      Serial.println(" ppb");      digitalWrite(WAKE_PIN, 1);
delay(60);}
On Saturday, June 17, 2017 11:03 AM, riaz ahmed<EMAIL_ADDRESS>wrote:

Thanks AK, one issue remains and i hope you can fix it. The Logoele LGAQS-HT01 has two sensors, CCS811 and SI7021, the later for temp and humidity. When I write a code using the CCS811 test ino with one for SI7021 it seems there is a cinflict. SI7021 uses Wire.begin() while CCS811 uses Wire.begin(Sda,Scl). It gets compiled but gives odd values for SI7021. Can u help?
Get Outlook for Android
On Sat, Jun 17, 2017 at 10:53 AM +0500, "Akram Ali"<EMAIL_ADDRESS>wrote:
@djdehaan thanks for sharing the fix! I've now updated the library with a slight modification to your code. Hopefully it should work well for more people now.—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.

Finally got the LGAQS-HT01 to work with Wemos ESP826 12E ! Last confusion about the odd values on replugging Wemos was removed after we looked into CCS811 library of AKStudios and added in Setup to reset 0xF4 and 0x01 registers of CCS811.
/***************************************************  June 18 2017  This is an example that uses Wemos ESP8266 12E as   microcontroller and sensor Logoele LGAQS-HT01   (a combination of CCS811 digital TVOC/eCO2 sensor   by CCMOSS/AMS and SI7021 by Silicon Instruments).   The code is largely based on Wire and SI7021   Readsensor.ino example that gives Temp and Humidity values.  The code was further modified to get CO2 and TVOC   values from the same architecture of SI7021 Readsensor.ino  It uses Wire.begin library so as to indicate   to microcontroller the pins of sda and scl. The CCS811  library was not used in this code.     VDD -- 3.3V  GND -- G  SDA -- D2  SCL -- D1  WAK/C2D -- D0  ****************************************************/
#include <Wire.h>#define CCS811ADDR 0x5A  //#define ADDR      0x5B  CCS811 I2C address is 0x5A or 0x5B#define SI7021ADDR 0x40 // SI7021 I2C address is 0x40(64)#define WAKE_PIN D0
float humidity = 0;float temp = 0;float CO2 = 0;float TVOC = 0;
void setup()  {    Wire.begin(D2, D1); //define the SDA (D2) and SCL(D1) pins for Wemos/Nodemcu/Esp8266 setup
    Serial.begin(9600);    pinMode(WAKE_PIN, OUTPUT);
    digitalWrite(WAKE_PIN, 0);      delay(70);    Wire.beginTransmission(0x5A); // this resets the SDA    Wire.write(0xF4);    Wire.endTransmission();    digitalWrite(WAKE_PIN, HIGH);      delay(60);
    digitalWrite(WAKE_PIN, LOW);      delay(60);    Wire.beginTransmission(0x5A);    Wire.write(0x01);    Wire.write(0x10);  // constant power mode, IAQ measurement every second    Wire.endTransmission();    digitalWrite(WAKE_PIN, HIGH);      delay(60); }
void loop()  {
// Temp and humidity part of loop for SI7021
    unsigned int data[4];    digitalWrite(WAKE_PIN, 0);      delay(60);    Wire.beginTransmission(SI7021ADDR);    Wire.write(0xF5); // Trigger humidity measurement command to register 0xF5 , its 2 byte register    Wire.endTransmission();      delay(60);       Wire.requestFrom(SI7021ADDR, 2); // Request 2 bytes of humidity data      if(Wire.available() == 2)       {        data[0] = Wire.read();        data[1] = Wire.read();      }      // Convert the humidity data      float humidity  = ((data[0] * 256.0) + data[1]);      humidity = ((125 * humidity) / 65536.0) - 6;
    Wire.beginTransmission(SI7021ADDR);    Wire.write(0xF3); // Trigger temperature measurement command to 0xF3    Wire.endTransmission();    delay(60);     Wire.requestFrom(SI7021ADDR, 2); // Request 2 bytes of temp data      if(Wire.available() == 2)      {      data[0] = Wire.read();      data[1] = Wire.read();      }     // Convert the temp data        float temp  = ((data[0] * 256.0) + data[1]);        float celsTemp = ((175.72 * temp) / 65536.0) - 46.85;        float fahrTemp = celsTemp * 1.8 + 32;     // Output temp and humidity data to serial monitor      Serial.print("Humidity : ");      Serial.print(humidity);      Serial.println(" % RH");      Serial.print("Temperature : ");      Serial.print(celsTemp);      Serial.println(" C");      digitalWrite(WAKE_PIN, 1); // make SDA high        delay(600);  // CO2 and TVOC part of loop for CCS811
      digitalWrite(WAKE_PIN, 0); //make SDA low         delay(60);      Wire.beginTransmission(CCS811ADDR);      Wire.write(0x02);   // Trigger CO2 and TVOC measurement command  0x02 , its a 4 byte register      Wire.endTransmission();           Wire.requestFrom(CCS811ADDR, 4); // Request 4 bytes of CO2 and TVOC data        if(Wire.available() == 4)        {        data[0] = Wire.read();        data[1] = Wire.read();        data[2] = Wire.read();        data[3] = Wire.read();        }        // Convert the data by shifting the registers 8 bit        float CO2 = (data[0]<<8) + data[1];        float TVOC = (data[2]<<8) + data[3];      // Output temp and humidity data to serial monitor      Serial.print("CO2 : ");      Serial.print(CO2);      Serial.println(" ppm ");      Serial.print("TVOC : ");      Serial.print(TVOC);      Serial.println(" ppb");      digitalWrite(WAKE_PIN, 1); // make SDA high        delay(600);}
On Saturday, June 17, 2017 11:25 AM, Akram Ali<EMAIL_ADDRESS>wrote:

@ahmedriazku I left the call to Wire.begin() in the code as this library is intended to be easily used with Arduino boards and the CCS811 sensor. Any other board or sensor would require modification of the code.As suggested above, you can comment out the call to Wire.begin() in the library and add your own calls in the main code to make it compatible with other devices. I've not tried the sensor you mentioned, but I tested the code with breakouts for CCS811 and Si7021 on the same circuit and it runs fine.—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

Hi,
I'm trying to get the CJMCU-811 CCS811 board to work but something is wrong:
Usually, after I flashed the Wemos, the sensor works. But after a while, I get an odd reading which is frozen (does not change anymore) like
CO2 concentration : 1021 ppm
TVOC concentration : 65021 ppb
or
CO2 concentration : 253 ppm
TVOC concentration : 65021 ppb
or it goes straight to
CO2 concentration :<PHONE_NUMBER> ppm
TVOC concentration :<PHONE_NUMBER> ppb
After reset/restart I get:
Error: Firmware still in boot mode.
Error ID: 3
Initialization failed.
It looks like something crashed. The only thing to fix this seems to be to re-flash.
Does anybody have an idea how to fix this or point into a direction as where the problem could be? THANKS!

Hi @maddhin,
I also had that problem, i found a lot in many blogs pages like Sparkfun, Adafruit. I can solve the problem adding a Clock Stretch Limit , with this change the sensor is working normally for more than 2 months. Make sure that only start the I2C once and then insert the Clock Stretch like:
Wire.begin();
Wire.setClockStretchLimit(2000);
I hope I've helped :)

@dielume Thanks a lot - I'm not quite sure how to apply this. I add the code and run it for a short while and then remove the Clock stretch and flash again?
I found something like this in a Chinese forum (Google translation):
"chip sends 0XF4 instructions have to wait extra 180uS to access it, and I2C time between each byte that is sent to more than 50US"
So it seems to be somehow related to "timing" (I'm a noob, so not sure what that really means).
On https://download.ams.com/ENVIRONMENTAL-SENSORS they have all the datasheets etc for the sensor. Especially the CC-000619-DS document should be useful (https://cdn.sparkfun.com/datasheets/BreakoutBoards/CCS811_Programming_Guide.pdf), or? Shouldn't that give any hint as how to solve this? Did anybody try to contact AMS re this?

@dielume I added your 2 lines in the setup and removed it after one run. This seems to work! THANK YOU!
I already thought my sensor broke...
I found this line
Wire.begin(TWI_PINS_20_21); // set master mode using pins 20 (SDA) and 21 (SCL)    Wire.setClock(400000); // I2C frequency at 400 kHz   delay(1000);
at https://github.com/kriswiner/CCS811 - which seems to be a C++ written library for the CCS811. I do not know whether this is helpful to make this library "perfect" so noobs like me can handle the CCS811 :)

Hm, sadly, after ~20-60min the CCS811 showed the same problems again. Only after reflashing a few(!) times with the Wire.setClockStretchLimit(2000); in the setup(); fixes the problem again.
I still think the library is not ready for production;)

I have correct some issues with editing library. Check it here https://github.com/pushpa66/CCS811

I got this library here working after I moved the WAK pin from D0 to D3 on the Wemos. There seem to have been some startup issues.
Practically, the main issue I have with this library here is that it always seems to need a reset after giving the Wemos power. Without reset the CCS811 goes to 65000.
Is this fixed in the new @pushpa66 library? The new library is no fork, or?

PS: this library here I only got working with changing the twi_setClockStretchLimit(230). Did the new library fix this? I would love to change the twi_setClockStretchLimit(460) back to 230 just to make sure other library or what not are not influenced.

Actually modified library should use according to my example.. Try it.. I
test it properly with ESP32.
On Oct 13, 2017 11:46 AM, "maddhin"<EMAIL_ADDRESS>wrote:

PS: this library here I only got working with changing the
twi_setClockStretchLimit(230). Did the new library fix this? I would love
to change the twi_setClockStretchLimit(460) back to 230 just to make sure
other library or what not are not influenced.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/AKstudios/CCS811-library/issues/3#issuecomment-336360650,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AQyrm3g15TzMLs6ZCyGK8tLZ-FZp8I4Hks5srwBLgaJpZM4NKkah
.

@pushpa66 : just to make sure to understand: so the twi_setClockStretchLimit(460) is still necessary?
Ya, also found this out about D0 but somebody, somewhere recommended it... I guess that was a noob like me... :)
Will give your library a try over the weekend. Thanks for the work anyway!!!

actually I have not studied about  twi_setClockStretchLimit(460) thing. I can test my example with wemos D1. It works fine. DO NOT defend on the library. We have to add some trick on program. Follow my code itself.  You will be able to understand.. https://github.com/pushpa66/CCS811/tree/master/CCS811_Example_WeMos_D1

Hi,
Sadly to say I am experiencing the same issues with a WeMos D1 R2. I have a CCS811 combined with a HDC1080, and the CCS811 seems to show the same behaviours as described after a few minutes of running.. @pushpa66  I tried your library, but after a while I get strange values and need to power off the unit.. I also tried the clock settings, but no joy... Any other solutions?

Did you use my example code?
On Oct 25, 2017 3:20 AM, "martin072"<EMAIL_ADDRESS>wrote:
Hi,
Sadly to say I am experiencing the same issues with a WeMos D1 R2. I have a
CCS811 combined with a HDC1080, and the CCS811 seems to show the same
behaviours as described after a few minutes of running.. @pushpa66
https://github.com/pushpa66 I tried your library, but after a while I get
strange values and need to power off the unit.. I also tried the clock
settings, but no joy... Any other solutions?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/AKstudios/CCS811-library/issues/3#issuecomment-339143731,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AQyrmwLJq_sgGvTLY3soX-0D3AO4X4Tvks5svluJgaJpZM4NKkah
.

hi @pushpa66,
Yes I did. Did not work. I followed the lead to change the twi_setClockStretchLimit(230) to 460, and now it seems to run for 12 hrs with no issues.. So I am guessing it is an issues with the wemos..

The key change seems to be the twi_setClockStretchLimit(230) to 460. I tried all the other tricks, too but after the stretchlimit change, no other trick seems necessary.
My CCS811 runs stable BUT right after the power on, when it shows the million or 65000 values. Pushing the rest button usually fixes the problem. This happens ALWAYS when plugging power in (put USB plug into Wemos).
So, if this startup problem is fixed, the libary works. I have the CCS811 running for ~3 weeks now and as far as I can remember no crashes / crazy values anymore (once one did the initial after-power-on-reset).

I am not very familiar with working with Github but wouldn't it be easier if @pushpa66 forks and adds this valuable changes into this repository? Then we would have one place to discuss and one could also see the code change, etc.
The CCS811 and ESP8266 don't seem to be big friends, let's try to channel the info so other people can find solutions easily!?

Some times  we cannot initialize CCS811 sensor just calling initialization method one time. That is why I try many times to intialize. After initialization It works fine. If you work with deepSleep modes, we need another way to handle issues. I have working examples if you need. (ESPs are not easy to handle compared to Arduino)


[aws-mountpoint-s3-csi-driver] Addon support

Describe the feature
Since cdk-eks-blueprints has supported EbsCsiDriverAddOn and EfsCsiDriverAddOn, it will be good to support aws-mountpoint-s3-csi-driver.
So that customer will have more storage options with cdk-eks-blueprints, and aws-mountpoint-s3-csi-driver is a great feature for eks nodes to write to S3.
Use Case
EKS nodes write to S3 just like filesystem.
Proposed Solution
No response
Other Information
No response
Acknowledgements

[ ] I may be able to implement this feature request

CDK version used
2.139.0
EKS Blueprints Version
No response
Node.js Version
v20.9.0
Environment details (OS name and version, etc.)
MacOS 14.5 (23F79)

For now, you can use HelmAddon to install Mountpoint for S3 CSI driver. See https://github.com/aws-solutions-library-samples/guidance-for-asynchronous-inference-with-stable-diffusion-on-aws/blob/main/lib/addons/s3CSIDriver.ts for demo implementation.


Fix spelling

interupted to interrupted
paramter to parameter

Description
Fix typos

Types of changes

[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] New feature (non-breaking change which adds functionality)
[ ] Bug fix (non-breaking change which fixes an issue)
[ ] Enhancement (improves an existing feature and functionality)
[X] Cleanup (Code refactoring and cleanup, that may add test cases)

Feature/Enhancement Scale or Bug Severity
Feature/Enhancement Scale

[ ] Major
[X] Minor

Bug Severity

[ ] BLOCKER
[ ] Critical
[ ] Major
[ ] Minor
[X] Trivial

Screenshots (if appropriate):
How Has This Been Tested?

@nvazquez a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress.

Packaging result: :heavy_check_mark: el7 :heavy_check_mark: el8 :heavy_check_mark: debian :heavy_check_mark: suse15. SL-JID 2784

@blueorangutan test

@nvazquez a Trillian-Jenkins test job (centos7 mgmt + kvm-centos7) has been kicked to run smoke tests

Trillian test result (tid-3518)
Environment: kvm-centos7 (x2), Advanced Networking with Mgmt server 7
Total time taken: 31083 seconds
Marvin logs: https://github.com/blueorangutan/acs-prs/releases/download/trillian/pr6064-t3518-kvm-centos7.zip
Smoke tests completed. 91 look OK, 1 have errors
Only failed tests results shown below:

Test
Result
Time (s)
Test File

test_hostha_enable_ha_when_host_disabled
Error
4.71
test_hostha_kvm.py

test_hostha_enable_ha_when_host_in_maintenance
Error
303.89
test_hostha_kvm.py


Please support --remove-signature & --all-architectures

For the codesign binary to be a closer drop-in replacement for /usr/bin/codesign, this is needed.

Also ad-hoc signatures


Refactor CeForm

In conjunction with "TYPO3-Initiatives/headless: Form output optimized for frontend" and "TYPO3-Initiatives/nuxt-typo3: middleware - POST-Requests", I want to refactor this.

go ahead, CeForm component is still PoC to show how we can work with that, but you can't find there response handling - we have to get the response from page content - after submit we have to find content element responsible for this specific form and get the response - this is tricky part, we haven't published yet (but we have it in our projects).
In the other hand I would like to get rid off vue-formulate, we have tested it in our projects and it's not fit for us. We prefer write own field components with small helper to validation like https://vee-validate.logaretm.com/


feat: add gitignore to template

Pull Request Test Coverage Report for Build 745028651

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

Totals

Change from base Build 744682004:
0.0%

Covered Lines:
3

Relevant Lines:
3

💛  - Coveralls

This was fixed by d4c70050bc428a520ba17673546bb7e20e5bf976


Clean up S2N_UNIT_TEST

Description of changes:

the environmental variable S2N_UNIT_TEST is no longer required
it was replaced with s2n_in_unit_test() in a previous PR (#1252)
remove remaining references to avoid confusion

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Codecov Report

Merging #1748 into master will increase coverage by 19.39%.
The diff coverage is n/a.

@@             Coverage Diff             @@
##           master    #1748       +/-   ##
===========================================
+ Coverage   71.02%   90.42%   +19.39%
===========================================
  Files         224      146       -78
  Lines       16340    10444     -5896
===========================================
- Hits        11606     9444     -2162
+ Misses       4734     1000     -3734


Disney Junior - Comcast - Unable to extract post url

[x] I've verified and I assure that I'm running youtube-dl 2017.04.03
[x] At least skimmed through README and most notably FAQ and BUGS sections
[x] Searched the bugtracker for similar issues including closed ones
[x] Bug report (encountered problems with youtube-dl)

C:\>youtube-dl.exe --ap-mso=Comcast_SSO --ap-username=foo --ap-password=bar --verbose http://watchdisneyjunior.go.com/miles-from-tomorrowland/video/vdka3764052/02/18-who-stole-the-dinosaur-nine-minutes-til-bedtime#playlist=PL551978168
[debug] System config: []
[debug] User config: []
[debug] Custom config: []
[debug] Command-line args: ['--ap-mso=Comcast_SSO', '--ap-username=PRIVATE', '--ap-password=PRIVATE', '--verbose', 'http://watchdisneyjunior.go.com/miles-from-tomorrowland/video/vdka3764052/02/18-who-stole-the-dinosaur-nine-minutes-til-bedtime#playlist=PL551978168']
[debug] Encodings: locale cp1252, fs mbcs, out cp437, pref cp1252
[debug] youtube-dl version 2017.04.03
[debug] Python version 3.4.4 - Windows-10-10.0.14393
[debug] exe versions: ffmpeg N-84348-gdb7a05d, ffprobe N-84348-gdb7a05d
[debug] Proxy map: {}
[Go] 18-who-stole-the-dinosaur-nine-minutes-til-bedtime: Downloading webpage
[Go] 3764052: Downloading JSON metadata
[Go] 3764052: Downloading Provider Redirect Page
ERROR: Unable to extract post url; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; type  youtube-dl -U  to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
Traceback (most recent call last):
  File "C:\Users\dst\AppData\Roaming\Build archive\youtube-dl\rg3\tmpam8ojdsi\build\youtube_dl\YoutubeDL.py", line 761, in extract_info
  File "C:\Users\dst\AppData\Roaming\Build archive\youtube-dl\rg3\tmpam8ojdsi\build\youtube_dl\extractor\common.py", line 429, in extract
  File "C:\Users\dst\AppData\Roaming\Build archive\youtube-dl\rg3\tmpam8ojdsi\build\youtube_dl\extractor\go.py", line 98, in _real_extract
  File "C:\Users\dst\AppData\Roaming\Build archive\youtube-dl\rg3\tmpam8ojdsi\build\youtube_dl\extractor\adobepass.py", line 1409, in _extract_mvpd_auth
  File "C:\Users\dst\AppData\Roaming\Build archive\youtube-dl\rg3\tmpam8ojdsi\build\youtube_dl\extractor\adobepass.py", line 1332, in post_form
  File "C:\Users\dst\AppData\Roaming\Build archive\youtube-dl\rg3\tmpam8ojdsi\build\youtube_dl\extractor\common.py", line 787, in _html_search_regex
  File "C:\Users\dst\AppData\Roaming\Build archive\youtube-dl\rg3\tmpam8ojdsi\build\youtube_dl\extractor\common.py", line 778, in _search_regex
youtube_dl.utils.RegexNotFoundError: Unable to extract post url; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; type  youtube-dl -U  to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.

When trying to download videos from http://disneyjunior.disney.com I get an error stating "unable to extract post url".  I'm able to view these videos in the browser after logging in with the same credentials provided on the command-line.

That's likely a duplicate of #12563, where Comcast support is broken. Please move on there for further discussions.


Position calculation problem when sorting draggable elements

When i try to sort Draggable elements, dragging element positions itself wrong.
I guess the problem occurs due to html hierachy change.
Please watch following video in order to reproduce the problem.

Hi @STRML,
How can I fix that problem?
Or are there any workaround solution that you recommend?

I found another react component which has advanced sorting+dragging capabilities.
it works reliable and fancy :)
http://clauderic.github.io/react-sortable-hoc/#/basic-configuration/basic-usage
Issue can be closed.


Game crashes when accepting a lobby invite from a friend while the game is not running

To reproduce:

Don't have the game open
Accept a lobby invite from a friend

We get the following errors:
ERROR: No loader found for resource: res://+connect_lobby
ERROR: Failed loading scene: res://+connect_lobby

By default, when accepting a lobby invite, Steam launches the game with command line arguments +connect_lobby <SteamIDLobby>, but I guess in Godot it searches for a scene if given cmd args.
The current workaround is to simply open the game first before accepting a lobby invite

The reason for this is simple: when receiving command line arguments, Godot treats first argument as the path to the scene that should be loaded when starting the game. The workaround for this is the following: you should specify the name of your starting scene in Steam launch options:

Please note that I've placed res://main.tscn into the Arguments box, this should do the trick. In this case the actual command line will be: res://main.tscn +connect_lobby
And of course, you should also handle +connect_lobby command line parameter. You can use, for example, the following code:
var args = OS.get_cmdline_args() 	var has_lobby_invite = false 	for arg in args: 		if has_lobby_invite: 			connect_to_lobby(int(arg)) 			return 		if arg == "+connect_lobby": 			has_lobby_invite = true
You can use the source code of our game 'I Know Everything' for reference, if you want:
https://github.com/Antokolos/know-everything-os/blob/master/godotsteam.gd

Thank you! It works perfectly

Man, I was super late to the game on this one.    That is pretty much was I would have said but less explanatory.  Excellent code snippet, sir!


Setup auto-generating system

We have system for mgmt libraries to use latest swagger and auto-gen tool to generate code.
Let's see if we can expand the usage of the system to be able to auto gen data libraries too.

Label prediction was below confidence level 0.6 for Model:ServiceLabels: 'Automation:0.26544115,Service Bus:0.0903351,Storage:0.05824624'
Label prediction was below confidence level 0.6 for Model:CategoryLabels: 'Mgmt:0.57684654,Client:0.4015755,Service:0.0156219825'


need some help about it

i did the git clone phase and I can see my files, but I'm in the installation phase and I couldn't install
pip install -r requirements.txt and
i tried the npm install commands, but it didn't happen, can you help

i just have to install but the command are not workin


Adding delay between timed traffic light steps

@Artemis Seven says: "I wanted to ask whether it would be possible to introduce a variable (user selectable) delay between time traffic light steps? (to allow vehicles to clear out, or pass through if their speed didn't allow for a full stop, before the next step triggers) Like a red light hold function :)"
https://github.com/VictorPhilipp/Cities-Skylines-Traffic-Manager-President-Edition/issues/77

it is possible to do that with a dedicated all red step already ... but well ... convenience is king ;D

Tagging #8

You tagged the wrong artemis @VictorPhilipp. 🙃


Kasko js v2

Add basic information about the usage of KASKO js v2.

Waiting for QA team to finish their testing before releasing this into the wild.🐕


banned.video

`$ youtube-dl -f best -i --verbose https://banned.video/watch?id=5f7bab002a73f00ed2755e89 https://banned.video/watch?id=5f7f89b091d9ae103cc8405b
[debug] System config: []
[debug] User config: []
[debug] Custom config: []
[debug] Command-line args: [u'-f', u'best', u'-i', u'--verbose', u'https://banned.video/watch?id=5f7bab002a73f00ed2755e89', u'https://banned.video/watch?id=5f7f89b091d9ae103cc8405b']
[debug] Encodings: locale UTF-8, fs UTF-8, out UTF-8, pref UTF-8
[debug] youtube-dl version 2020.09.20
[debug] Python version 2.7.17 (CPython) - Linux-5.4.0-48-generic-x86_64-with-LinuxMint-19.3-tricia
[debug] exe versions: ffmpeg 3.4.8, ffprobe 3.4.8
[debug] Proxy map: {}
[generic] watch?id=5f7bab002a73f00ed2755e89: Requesting header
WARNING: Could not send HEAD request to https://banned.video/watch?id=5f7bab002a73f00ed2755e89: HTTP Error 403: Forbidden
[generic] watch?id=5f7bab002a73f00ed2755e89: Downloading webpage
ERROR: Unable to download webpage: HTTP Error 403: Forbidden (caused by HTTPError()); please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; type  youtube-dl -U  to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
File "/usr/local/bin/youtube-dl/youtube_dl/extractor/common.py", line 632, in _request_webpage
return self._downloader.urlopen(url_or_request)
File "/usr/local/bin/youtube-dl/youtube_dl/YoutubeDL.py", line 2238, in urlopen
return self._opener.open(req, timeout=self._socket_timeout)
File "/usr/lib/python2.7/urllib2.py", line 435, in open
response = meth(req, response)
File "/usr/lib/python2.7/urllib2.py", line 548, in http_response
'http', request, response, code, msg, hdrs)
File "/usr/lib/python2.7/urllib2.py", line 473, in error
return self._call_chain(*args)
File "/usr/lib/python2.7/urllib2.py", line 407, in _call_chain
result = func(*args)
File "/usr/lib/python2.7/urllib2.py", line 556, in http_error_default
raise HTTPError(req.get_full_url(), code, msg, hdrs, fp)
[generic] watch?id=5f7f89b091d9ae103cc8405b: Requesting header
WARNING: Could not send HEAD request to https://banned.video/watch?id=5f7f89b091d9ae103cc8405b: HTTP Error 403: Forbidden
[generic] watch?id=5f7f89b091d9ae103cc8405b: Downloading webpage
ERROR: Unable to download webpage: HTTP Error 403: Forbidden (caused by HTTPError()); please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; type  youtube-dl -U  to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
File "/usr/local/bin/youtube-dl/youtube_dl/extractor/common.py", line 632, in _request_webpage
return self._downloader.urlopen(url_or_request)
File "/usr/local/bin/youtube-dl/youtube_dl/YoutubeDL.py", line 2238, in urlopen
return self._opener.open(req, timeout=self._socket_timeout)
File "/usr/lib/python2.7/urllib2.py", line 435, in open
response = meth(req, response)
File "/usr/lib/python2.7/urllib2.py", line 548, in http_response
'http', request, response, code, msg, hdrs)
File "/usr/lib/python2.7/urllib2.py", line 473, in error
return self._call_chain(*args)
File "/usr/lib/python2.7/urllib2.py", line 407, in _call_chain
result = func(*args)
File "/usr/lib/python2.7/urllib2.py", line 556, in http_error_default
raise HTTPError(req.get_full_url(), code, msg, hdrs, fp)
`

Duplicate of https://github.com/ytdl-org/youtube-dl/issues/26805


AbstractNormalizer tries to instanciate Dunglas\ApiBundle\JsonLd\Serializer\ItemNormalizer during denormalization

Hi,
I'm running this bundle from about 2015-07-15 14:19:51. I try to denormalize a complex entity, and to my surprise, it fails with the following message:
"Catchable Fatal Error: Argument 1 passed to Dunglas\ApiBundle\JsonLd\Serializer\ItemNormalizer::__construct() must implement interface Dunglas\ApiBundle\Api\ResourceCollectionInterface, none given, called in /home/felicitus/public_html/PartKeepr/vendor/symfony/symfony/src/Symfony/Component/Serializer/Normalizer/AbstractNormalizer.php on line 347 and defined"
This only occurs within the manufacturers property. The distributors property works just fine.
The backtrace can be found here: http://pastebin.ca/3152210
The relevant backtrace line starts at line number 30 in the paste.
I've spent several hours trying to figure out why, but I'm pretty puzzled at this point.

The problem is probably related with object_to_populate being null or an empty object (line 31 of the trace). It will crash anyway with such data (an object as value is mandatory).
However there is something strange the line 347 in AbstractNormalizer doesn't exist (at least in Symfony 2.7): https://github.com/symfony/symfony/blob/2.7/src/Symfony/Component/Serializer/Normalizer/AbstractNormalizer.php

How can I debug this further? I already tried some debug statements, but didn't get to an conclusion why this happens.
In my project, line 347 in AbstractNormalizer is like 343 in Sf2.7. I probably should upgrade my system, however, I'm afraid that this will break as there were several changes. Or should I be safe to upgrade to the 1.0 branch of DunglasApiBundle?

Downgrading to the 1.0 branch looks like the best idea for now because many BC breaks will occur in dev-master.
If the error persist with 1.0, can you dump the content of the context passed to the normalizer here: https://github.com/dunglas/DunglasApiBundle/blob/1.0/Controller/ResourceController.php#L88?

I have finally upgraded to dev-master and the issue has gone away. Still I have no clue where this came from, but it works now.


bash completion: remove shebang

Address rpmlint warning by removing the shebang as the completion script
isn't meant to be an executable.
Signed-off-by: Valentin Rothberg<EMAIL_ADDRESS>

bot, add author to whitelist

bot, test pull request

LGTM

bot, retest this please

@rh-atomic-bot retry

Homu does not seem to be working.
Merging manually.


feature request: prune default make configs

synth prune-options to delete make configs that aren't different to the defaults.
(to improve fetching prebuilt-packages and keep the options clean)

It can't prune the configs (the mount is read-only) but it could provide a list.
When an environment variable set, it could flag any configs that are the same as the default (and thus could be deleted).
Is that sufficient?

I mean flag during any ports scan, not a special command, and only when the env var is set.

actually, synth can't even easily do that.  It doesn't know what the default options are supposed to be because the presence of the saved configuration changes the results.
Maybe a separate script utility could be provided (assuming I can figure out how to get the default values by ignoring any saved options firstd).  So it wouldn't be part of synth, just a script utility people could run (likely only once or infrequently)

i could even write a shell script and port it directly to ports (e.g. /usr/ports/Tools/scripts/ ) as a general tool that lists options files that are identical to defauls.
That could work, right?  You could just pipe the stdout into xargs rm -rf to remove in one step.

That sounds great actually!

okay, done:
https://svnweb.freebsd.org/ports?view=revision&revision=408849
pull the latest ports and you can use it now.

great, thanks!


Introduce wallet kit core

This is an experiment to move the WalletKit logic into a core, framework-agnostic package. While we don't plan on supporting other UI libraries in the near-term, this could help bootstrap community efforts, as they could leverage the core package to implement similar behavior in their own UI. The API is as minimal as I could make it, and the state model should easily incorporate into anything. As a neat aside, it's also Svelte Store compatible.

Replaced by: https://github.com/MystenLabs/sui/pull/6950


Dockerfile

File: docker-hub/webhooks.md

Thanks for sharing the issue. As this issue is old, some context may have been lost. Can you share more details about the issue with that topic?


Get schema does not deal with trailing /

Added removal of trailing slash and a test in the suite.


run tests from command line?

From your index.html I assume you had trouble making it run from the command line, right? Is this impossible? What is missing to make that work so that running mocha would be enough?

I just found the related discussion in the jspm-cli project. I will try if and how well the suggested approach works and report back. I hope I can skip the dummy es6-test-setup.js file and directly import the module to be tested in the tests, so something like...
var System = require("jspm");
var assert = require("assert");

System.import("src/moduletotest").then(function(mod) {
  describe("mod methods", function() {
    describe("#...", function() {
      //...
    }
  }
})
.catch(function(e) {
    describe("JSPM", function() {
        it("should load the ES6 module", function(done) {
            assert.fail(null, "", e);
        })
    })
})

I have a feeling though that the describes must be at the root to work properly, but I really would hate to have this promise boilerplate in each testcase...

Yes, it's true that I had trouble getting Mocha to run on the command line with JSPM. This was one of the major things that stopped me from adopting JSPM. I would like to re-investigate soon though, I know there has been lots of work done on JSPM in the past few months.
I would love to hear about any technique that works for you if you do find a solution. There should be some straightforward path to write tests for ES6 code in ES6, and run them in the command line with Mocha, I just haven't seen it work yet.

Same issue here. I want to write my code and test code in ES6.

I found a funny work-around to at least run the tests and not have ridiculous boilerplate inside each test or additional setup files:
var System = require("jspm");
var assert = require("assert");

// boiler-plate
var count = 12 // numbers of tests in this module
var oldit = it
it = function(name, fn) {count--; oldit(name, fn)}
describe("ignore", function() { it("me", function(done) {
    var iv = setInterval(function() {
      if (count === 0) {clearInterval(iv); done()}
    }, 500)
})})

// your tests
System.import("src/reader").then(function(reader) {
  describe("reader methods", function() {
    describe("#read", function() {
      it("should do stuff", function() {
        // test code
      })
    })
  })
})

The problem was that the file ran through without the tests having had enough time to actually start and letting mocha now about them. So, what the above does is start a waiting-test which waits until all tests have started and then succeeds itself. Obviously, this is rubbish, but it works! @guybedford Any idea how to make this nicer?

Nice! Thank you for sharing this solution.
On Mon, Aug 24, 2015 at 3:11 PM, Maik Riechert<EMAIL_ADDRESS>wrote:

I found a funny work-around to at least run the tests and not have
ridiculous boilerplate inside each test or additional setup files:
var System = require("jspm");var assert = require("assert");
// boiler-platevar count = 12 // numbers of tests in this modulevar oldit = itit = function(name, fn) {count--; oldit(name, fn)}describe("ignore", function() { it("me", function(done) {
var iv = setInterval(function() {
if (count === 0) {clearInterval(iv); done()}
}, 500)
})})
// your tests
System.import("src/reader").then(function(reader) {
describe("reader methods", function() {
describe("#read", function() {
it("should do stuff", function() {
// test code
})
})
})
})
The problem was that the file ran through without the tests having had
enough time to actually start and letting mocha now about them. So, what
the above does is start a waiting-test which waits until all tests have
started and then succeeds itself. Obviously, this is rubbish, but it works!
@guybedford https://github.com/guybedford Any idea how to make this
nicer?
—
Reply to this email directly or view it on GitHub
https://github.com/curran/jspm-mocha-example/issues/1#issuecomment-134395671
.

I believe I've got it! :tada: Not only I can run my tests at the command line, I can mock dependencies as well.
See my pull request #2

Great work! Merged.

@ScreenDriver Looks good, I wonder if you can like I did require jspm and then skip requireing the config file. That should work right? Would make it even more easier.

@neothemachine I've tried it but it does not work. I mean it does work in the first place but when you want to mock something it throws a Cannot set property 'the-library' of undefined.
Here is an example Gist where I mock the bluebird library. Yes I know, bluebird does not need to be mocked. It's only for this example and works only when you import config.js.
The most important part was to change the baseUrl in config.js from baseURL: "/" to baseURL: "./". Without that it's not working.
Oh and by the way: because you import systemjs and config.js in your unit test file the tests are not working in the browser anymore.

Maybe someone can help me with this one systemjs/systemjs#725

@ScreenDriver  I just tested this myself (using jspm import since I don't need mocks yet), and I simplified the before hook a bit more and made error handling better:
  before(() => {
    return System.import('./lib/myModule.js')
      .then(mod => myModule = mod)
  });

When import fails, then by returning the promise Mocha will automatically handle it correctly and display the error.  Feel free to put that in a pull request, I'm currently a little busy myself!

By the way, when the test file has a syntax error, then the output gets really ugly now due to babel compilation (at least for me, under Windows console), I think this is because babel is not using console colors properly or they get messed up at some step when pushing the error around. Still, it's certainly very nice to write ES6 tests now! Good job.

Sorry for spamming, just a suggestion for adding this to package.json:
  "scripts": {
    "test": "./node_modules/.bin/mocha --compilers js:babel/register test/tests"
  }

Then you can just do npm test and be happy.

:+1:
I added your suggestions to my already existent #3

For another library of mine I needed real browser-based testing, and for that I use karma with karma-jspm and this has full jspm integration, so jspm import is happening from the start without any special things to do: https://github.com/Reading-eScience-Centre/leaflet-coverage/blob/master/test/util/utils.spec.js
I think this is how it should be, and I wonder if this can be achieved with the test-in-node approach that we are discussing here. I have a feeling that this could be solved by using/developing a different compiler for mocha for example, which more directly integrates jspm instead of just running babel. Because if you achieve that, then you can use the same test code base for node testing and browser testing, which.... would be wonderful.

Nice work adding a mock example and npm test script. Merged the PR. I'm considering trying to set up a travis integration to see if all this plays well with CI.

Travis works! I think we've got this issue sorted out now - all the code is ES6 and we can run tests with Mocha. After these changes this repo is much more usable as a starter project / learning resource. Thank you both for your work on this.
Closing the issue, but feel free to continue the conversation here.


replace noinput with noshell so providers that ask for input work

Fixes use of providers like rebar3 hex which reads user input.

made sure this doesn't weirdly interact with rebar3 shell; appears to be fine.


boards: arc: Remove label property from devicetree

The label property isn't needed in devicetree so remove it.
Signed-off-by: Kumar Gala<EMAIL_ADDRESS>

blocked on #48660


Apply fixes from StyleCI

This pull request applies code style fixes from an analysis carried out by StyleCI.

For more information, click here.

Current coverage is 66.25% (diff: 100%)

Merging #4 into master will not change coverage

@@             master         #4   diff @@
==========================================
  Files             7          7
  Lines            80         80
  Methods          21         21
  Messages          0          0
  Branches          0          0
==========================================
  Hits             53         53
  Misses           27         27
  Partials          0          0

Powered by Codecov. Last update e27bb95...c5d0531


Nativescript Angular iOS built is successful (and works in emualator) but crashes on physical phone

I need your help!
My nativescript app is running perfectly fine on android as well as in my iPhone 6S (iOS 10) emulator. The problem arise when trying to run the exact same code on my physical iPhone 6S (with the cmd: tns run ios) - it simply crashes with the following error:
Native stack trace:
1   0x10064bd48 -[TNSRuntime executeModule:]
2   0x1000a1494 main
3   0x180d568b8 <redacted>
JavaScript stack trace:
1   @file:///app/shared/student/student-list.service.js:14:24
JavaScript error:
file:///app/shared/student/student-list.service.js:14:24: JS ERROR Error: Could not find module './student'. Computed path '/var/containers/Bundle/Application/D87AA4D8-4172-4BBB-A033-FA56D354C6E9/instructorapp.app/app/shared/student/student'.

I have been trying to figure out what is going on for a couple of days now. I still have a suspicion that it is related to nativescript and angular versions where NgModule was introduced but since it runs on android and in the emulator i sort of dropped the thought. I have been fiddling around with npm/node versions but I have come to a full stop now and have no idea how to progress from here since it is running in the emulator.
I have also tried opening the project in xcode, building the ipa (also succesfull) and then copying it to the phone. It always get to the loadscreen and then crashes.
My package.json:
 "dependencies": {
    "@angular/common": "2.0.0-rc.5",
    "@angular/compiler": "2.0.0-rc.5",
    "@angular/core": "2.0.0-rc.5",
    "@angular/http": "2.0.0-rc.5",
    "@angular/platform-browser": "2.0.0-rc.5",
    "@angular/platform-browser-dynamic": "2.0.0-rc.5",
    "@angular/platform-server": "2.0.0-rc.5",
    "@angular/router": "3.0.0-rc.1",
    "email-validator": "1.0.4",
    "moment": "2.13.0",
    "nativescript-angular": "0.4.0",
    "nativescript-iqkeyboardmanager": "1.0.1",
    "nativescript-loading-indicator": "^2.1.0",
    "nativescript-telerik-ui-pro": "file:nativescript-ui-pro.tgz",
    "nativescript-timedatepicker": "^0.2.2",
    "nativescript-unit-test-runner": "0.3.3",
    "nativescript-web-image-cache": "^2.0.1",
    "rxjs": "5.0.0-beta.6",
    "tns-core-modules": "^2.3.0",
    "zone.js": "0.6.12"
  },
  "devDependencies": {
    "babel-traverse": "6.8.0",
    "babel-types": "6.8.1",
    "babylon": "6.8.0",
    "filewalker": "0.1.2",
    "jasmine-core": "^2.4.1",
    "karma": "^0.13.22",
    "karma-jasmine": "^1.0.2",
    "karma-nativescript-launcher": "^0.4.0",
    "lazy": "1.0.11",
    "nativescript-dev-typescript": "^0.3.2",
    "typescript": "^1.8.10"
  }

Any suggestions would we dearly appreciated. This is really getting to me ;)

It looks like a missing module import that may have been passing on your simulator due to an older version of a file lying around. You could verify that by deleting your platforms folder and trying to run your app.
In addition you could try upgrading to angular 2.0.0 and nativescript-angular 1.0.0, if you suspect you hit an issue in the old RC builds.


Update Composer dependencies (2021-07-07-00-12)

Visual regression test passed!
View the visual regression test report


Added tslint to the project

#3 @tanaypratap
Added tslint and tslint-react to the project.
Added a script to fix linting errors
Added a doc to help understand how to use tslint

@js-sapphire resolve the conflicts.


Add documentation on how to install utilities with go install

This updates the utility installation documentation with instructions on how to install them with go install.

Thanks for review! Build failure is from master, and fix is https://github.com/gruntwork-io/terratest/pull/1099, but since this is docs only, I'll merge it in.

Confirmed it is live and looks good: https://terratest.gruntwork.io/docs/testing-best-practices/debugging-interleaved-test-output/#installing-the-utility-binaries


Bug: lazy_repeat drops utf8_iterator when matching a char8_t string

The following example reproduces the error:
// Compiles:
match<"x+">(u8"x");
// Fails:
match<"x+?">(u8"x");

In the lazy_repeat evaluator, a nested call to evaluate() looks like this:
evaluate(begin, inner_result.get_end_position(), last, ...);

The type of last/EndIterator is utf8_iterator::sentinel, but inner_result.get_end_position() returns a const char8_t*, and these types are not equality-comparable.
Possibly needs a static_cast<Itertaor> around the call to get_end_position? I'm not sure if this would have some other unintended effects, or if there are other points in the code that will need to be similarly modified.

It should be fixed now :)

Excellent! Thank you for the quick fix!


Crash: realm::util::terminate_internal(std::__1::basic_stringstream<char, std::__1::char_traits, std::__1::allocator >&)

Hello,
Some users keep getting crashes at app launch. They are not able to use the app at all even after reinstalling! Not sure which version of Realm I'm using, but I think it's 0.93.1.
Here's the call stack:
Thread : Crashed: com.apple.main-thread
0  libsystem_kernel.dylib         0x0000000195a57270 __pthread_kill + 8
1  libsystem_pthread.dylib        0x0000000195af5170 pthread_kill + 112
2  libsystem_c.dylib              0x00000001959ceb18 abort + 112
3  Ayah                           0x000000010011b9e0 realm::util::terminate_internal(std::__1::basic_stringstream<char, std::__1::char_traits<char>, std::__1::allocator<char> >&) + 1156
4  Ayah                           0x000000010011bb20 realm::util::terminate_internal(std::__1::basic_stringstream<char, std::__1::char_traits<char>, std::__1::allocator<char> >&) + 1476
5  libsystem_pthread.dylib        0x0000000195af5170 pthread_kill + 112
6  Ayah                           0x00000001001115f4 void realm::util::terminate<unsigned long, unsigned long>(char const*, char const*, long, unsigned long, unsigned long) (terminate.hpp:45)
7  Ayah                           0x0000000100190bf8 realm::Group::init_from_ref(unsigned long) + 1972
8  libsystem_pthread.dylib        0x0000000195af5170 pthread_kill + 112
9  Ayah                           0x000000010019b444 realm::SharedGroup::begin_read(realm::SharedGroup::VersionID) + 7656
10 Ayah                           0x0000000100108164 -[RLMRealm getOrCreateGroup] (RLMRealm.mm:250)
11 Ayah                           0x0000000100113154 RLMRealmSchemaVersion (group.hpp:596)
12 Ayah                           0x00000001000e4c78 RLMUpdateRealmToSchemaVersion (RLMObjectStore.mm:299)
13 Ayah                           0x0000000100108ab0 +[RLMRealm realmWithPath:key:readOnly:inMemory:dynamic:schema:error:] (RLMRealm.mm:406)
14 Ayah                           0x000000010010841c +[RLMRealm realmWithPath:readOnly:error:] (RLMRealm.mm:311)
15 Ayah                           0x00000001001083d4 +[RLMRealm realmWithPath:] (RLMRealm.mm:304)
...

@Bajaber thanks for reporting this! v0.93.2 should contain a fix for this particular issue, so could you please try updating and letting us know if that fixes things? Thanks!

Uploaded a new version to the App Store. I'll keep you updated.

Great, thanks!

Updated the app to 0.93.2, but the problem persists! Any clue?

The problem will persist with the same database, unfortunately -- but 0.93.2 should not make database files that it is unable to open.


Add support in meltano run for state files

Migrated from GitLab: https://gitlab.com/meltano/meltano/-/issues/3148
Originally created by @tayloramurphy on 2022-01-07 21:00:21

meltano elt supports the passing of catalog and state files via the command line - https://meltano.com/docs/command-line-interface.html#parameters-2

meltano run tap-gitlab --state <file> target-x

View 2 previous comments from the original issue on GitLab

Still relevant

Similar to https://github.com/meltano/meltano/issues/3071. Not sure what the CLI would work for indicating which extractor the option is referring to. Perhaps:
meltano run --state tap-github:/path/to/state.json tap-github target-jsonl

i.e. a --state option that accepts zero or more inputs like <plugin-name>:<value>. We then build a dictionary mapping plugin names to state paths and use it to instantiate a PluginSettingsService with config_override={"_state": ...}:
https://github.com/meltano/meltano/blob/52d28a34b6389b7976b5b6d97593d325a3f4d323/src/meltano/core/block/extract_load.py#L265-L287
Similar to the meltano el implementation:
https://github.com/meltano/meltano/blob/52d28a34b6389b7976b5b6d97593d325a3f4d323/src/meltano/core/elt_context.py#L443-L486


ansis:SoilSite  land cover 0..1 to 0..*

Would be reasonable to say this is an ontology fix as well as schema?


Upgrade to gradle 8.6.

Trying to move this plugin forward. Starting with the gradle upgrade so Java 21 could be used to build.

Thanks a lot David. In the next few days repository will be updated and changes appear in marketplace


[tests-only] apiTest: list of trash files and restore files from the trash

added apiTest:

users can see the files in the trash
and restore files from the trash

Thanks for the review. I have redone the tests and made the tests more readable (I hope)


Rewrite test_proxymanager.py to be pytest-style

Related to #1160.

Codecov Report

Merging #1197 into master will not change coverage.
The diff coverage is n/a.

@@          Coverage Diff           @@
##           master   #1197   +/-   ##
======================================
  Coverage     100%    100%
======================================
  Files          21      21
  Lines        1975    1975
======================================
  Hits         1975    1975

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 2426b6e...91307e2. Read the comment docs.


Fix case sensitivity for name check

closes #177

Codecov Report

Merging #199 (721e61f) into master (185bebf) will not change coverage.
The diff coverage is 100.00%.

@@            Coverage Diff            @@
##             master     #199   +/-   ##
=========================================
  Coverage     71.52%   71.52%
  Complexity      711      711
=========================================
  Files           114      114
  Lines          2325     2325
  Branches        271      271
=========================================
  Hits           1663     1663
  Misses          573      573
  Partials         89       89

Impacted Files
Coverage Δ

...rc/main/java/seedu/address/model/student/Name.java
81.81% <100.00%> (ø)

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


Update minimum version requirements to ensure upgrades

Signed-off-by: Nathaniel Clark<EMAIL_ADDRESS>

Codecov Report

Merging #1018 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #1018   +/-   ##
=======================================
  Coverage   95.42%   95.42%
=======================================
  Files           2        2
  Lines         153      153
=======================================
  Hits          146      146
  Misses          7        7

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 a95c6c1...fc97fda. Read the comment docs.

Tests are failing with:
           Requires: iml-device-scanner-aggregator >= 2.2.1
           Available: iml-device-scanner-aggregator-2.2.0-198.el7.x86_64 (managerforlustre-manager-for-lustre-devel)

Looks like that will need a bump in devel

Once release is bumped, I think this looks good.


Unique validation rule getting skipped while form submission

What steps will reproduce the problem?
Unique validation rule doesn't work at all:
[['phone'], 'unique'],
Yii2 just bypasses this validation rule and tries to insert values.
Here is create SQL of table:
SET NAMES utf8;
SET FOREIGN_KEY_CHECKS = 0;

-- ----------------------------
--  Table structure for `EGCampaign`
-- ----------------------------
DROP TABLE IF EXISTS `EGCampaign`;
CREATE TABLE `EGCampaign` (
  `id` int(10) unsigned NOT NULL AUTO_INCREMENT,
  `firstname` varchar(255) NOT NULL,
  `lastname` varchar(255) NOT NULL,
  `phone` varchar(255) NOT NULL,
  `email` varchar(255) NOT NULL,
  `countryID` int(10) unsigned DEFAULT NULL,
  `promoCode` varchar(255) DEFAULT NULL,
  `createdAt` timestamp NULL DEFAULT CURRENT_TIMESTAMP,
  `updatedAt` datetime DEFAULT NULL,
  `reported` tinyint(1) DEFAULT '0',
  PRIMARY KEY (`id`),
  UNIQUE KEY `uk2` (`email`),
  UNIQUE KEY `uk3` (`phone`),
  UNIQUE KEY `uk1` (`promoCode`),
  KEY `countryID` (`countryID`),
  CONSTRAINT `FC_FK1` FOREIGN KEY (`countryID`) REFERENCES `Country` (`id`) ON DELETE SET NULL ON UPDATE CASCADE
) ENGINE=InnoDB AUTO_INCREMENT=1090 DEFAULT CHARSET=utf8;

SET FOREIGN_KEY_CHECKS = 1;

Here is the model:
https://gist.github.com/anonymous/0886dd56b72c270b0c38cca08b040e16
And here is the controller:
            $model = new EGCampaign();
            $model->promoCode = Yii::$app->security->generateRandomString(4);
            $model->load(Yii::$app->request->post());

            if ($model->validate() && $model->save()) {
                $result = "<h1>" . Yii::t("campaign", "Well done! Please, check your mailbox.") . "</h1>";
            } else
                $result = HTML::errorSummary($model,
                    [
                        'class' => "error-summary"
                    ]);

            return $result;

What is the expected result?
Expected result is preventing duplicate value insertion.
What do you get instead?
Exception (Integrity constraint violation) 'yii\db\IntegrityException' with message 'SQLSTATE[23000]: Integrity constraint violation: 1062 Duplicate entry '(050) 999 99 99' for key 'uk3'
The SQL being executed was: INSERT INTO `EGCampaign` (`promoCode`, `firstname`, `lastname`, `phone`, `email`, `countryID`, `createdAt`, `updatedAt`) VALUES ('nQKb', 'Test', 'Test', '(050) 999 99 99'<EMAIL_ADDRESS>5, NOW(), NOW())'

in /usr/share/nginx/www/vendor/yiisoft/yii2/db/Schema.php:633

Additional info

Q
A

Yii version
2

PHP version
7.0

Operating system
Ubuntu Server 16.04

Humm, I was unable to reproduce the problem. The validator worked as expected.

@nevermnd what can go wrong?

@turalsprofile which Yii version exactly are you using?

Tested with 7.0.7 (Debian), works as expected

@samdark 2.0.9-dev

@samdark why did you close?

Because I wasn't able to reproduce it.

@samdark but it doesn't mean that problem doesn't exist

If I we can't reproduce it we cannot fix it. You can provide a unit test that fails to make sure we have all data necessary to do it.

@samdark it's not fair and respectful at all to close existing issue just because you can't reproduce it. What else do I need to provide to make you sure that issue exists?

@turalsprofile If no one can reproduce this bug, the problem is probably in your application, not in the framework.

@turalsprofile ideally a unit test that fails.

It's not only myself who weren't able to reproduce it. See https://github.com/yiisoft/yii2/issues/11754#issuecomment-225827478

@turalsprofile  may be you have some "magic" in application (like this), that can change your model's behavior?

Sorry for bringing back this old issue. Actually I'm also encountering this issue for quite a long time. I got random error notification about this integrity constraint violation in production but unable to reproduce it in my dev environment. The unique rule works fine most of the time in my prod and works all the time in my dev env, so I just ignore it and thought there's something wrong with my db server.
But lately this problem occurring more often in my prod environment on an action that never showed this problem before. And I notice that this newer problem start showing up after I moved the action to a background job using yii2 queue. And I think the problem might be around concurrency, because I run multiple worker and from the log I see that there's 2 job run at almost the same time trying to insert the same thing. And that's why this occurred randomly and only on production.
So what I think is happening is like this:

thread 1
thread 2

unique rule check if record already exist
unique rule check if record already exist

record is not exist yet
record is not exist yet

try to insert new row
try to insert new row

row inserted successfully
row already exist, integrity constraint violation

I try to reproduce the problem by spawning 2 worker on my dev env and pushing 2 jobs that trying to insert the same record. One of the job succeed, and one of the job failed with the same error.
I know this might not be the same issue with what the OP posted, but maybe this can help to find a solution (or if there's any already, please tell me).

Done at #14693

Did anyone solve this issue? Now am getting it


Plugin fails if Enable reCAPTCHA is enabled

Overview
If you have a mailing list with the setting for Enable reCAPTCHA turned on, publishing to the list will fail with the error message:  captcha.
To get things working I turned off this setting, but it would be nice to have an option for having this feature enabled. I am not exactly sure of the best course of action to get this resolved. At a minimum, the README should be updated to document this issue.
It would be nice to have the option to using this feature within this plugin, if their API supports it then it should be added.

looking into this.

Thanks for pointing this out @mikelax
I don't know if the Mailchimp API allows it.  I can look into this.
In the meantime, got a moment to open a PR updating the README?  I can merge this week.

not sure if there is any way around this.  open to suggestions.

I fell into this issue as well.  I think I have a work around which could potentially be integrated into the plugin.  If I receive "captcha" back as the error, I manually build the URL for the popup window that is triggered in the normal mailchimp embedded form case.  I can then open that popup and successfully fulfill the captcha and sign up the user.  It's not a great user experience since they need to allow popups but its no worse than using that captcha otherwise.  You may be able to load the url in an iframe on the page and allow the user to finish the flow there.  The url for the pop up looks like this:
const { result, msg, params } = await addToMailchimp(this.state.email);
if (msg === 'captcha') {
    window.open(`https://<same domain used in plugin config>/subscribe/post?u=${params.u}&id=${params.id}&EMAIL=${encodeURIComponent(params.EMAIL)});
}

I haven't tried it with any of the additional fields that can be passed along as listFields but I expect they could be handled similarly.


File paths as value tags

Normally, the takes value # tags are not allowed to have multiple levels.  However, there is one case that we are going to need to handle -- the case where that value is a File-path.   I think that we can require that paths be given with forward slash separators but for this one tag (or perhaps a couple of others) we are going to need to allow path values.
My thinking is that we should introduce a schema attribute such as pathValue to indicate this. Alternatively, we could add path as a unitClass. I would like to get opinions and suggestions on this. @happy5214 @IanCa @dungscout96

This is accommodated by the valueClass which is posixPath.


[Catalog] Introduce a BackstagePluginsProvider

What / Why
At Spotify, we build and maintain hundreds of Backstage plugins owned by many dozens of teams.  Just as the cobbler's children have no shoes, so too do we have no strategy for tracking Backstage plugins in our Software Catalog.
This PR proposes a strategy!  At its essence:

The Model: A Backstage plugin should be modeled as a Component of type backstage-plugin.
The Method: Backstage plugins can be almost entirely derived from the contents of their package.json files; we therefore want to introduce a discovery-based mechanism for providing them to the Catalog. We can key-in on Backstage plugins (as opposed to standard JavaScript packages) based on the existence of a backstage.role key.
Incentives: Enabling teams to modify and deploy changes to their plugins without the need to interact with the core team is key to our InnerSource strategy; we achieve this through CODEOWNERS. Aligning plugin ownership with code ownership ensures both code ownership and catalog metadata is up-to-date.
Customization close to the code: Though we can cobble together (😉) a basic entity from a package.json, there will inevitably be a need to add customizations (system, tags, links, etc). We know from experience that the closer this metadata lives to the code it represents, the more likely it is to be kept up-to-date. So for those customizations, a catalogInfo key on package.json is proposed for per-plugin overrides.
Customization outside the code too:  We also have situations where we can't keep that metadata close to the code (e.g. we maintain many of the plugins in this very monorepo!), so this PR proposes a transformer that can be supplied to the provider where custom logic can be applied.

More details in the README.md
Still Todo

[ ] Modify backstage-cli pre/post-pack commands to remove catalogInfo key from package.json files
[ ] Tests

:heavy_check_mark: Checklist

[x] A changeset describing the change and affected packages. (more info)
[ ] Added or updated documentation
[ ] Tests for new functionality and regression tests for bug fixes
[ ] Screenshots attached (for UI changes)
[ ] All your commits have a Signed-off-by line in the message. (more info)

Closing this out, with https://github.com/backstage/backstage/pull/18354 replacing the proposal.
Primary reason we're not going down this path is that the proposed catalogInfo property in package.json incentivizes risky behavior (namely: storing potentially sensitive metadata in a file that is regularly published to registries).


Custom errors for prop validators

What problem does this feature solve?
I'm loving the way that prop specification and validation works compared to React, but one thing I wish is that custom validator functions could explain why validation failed, so that you don't have to hunt down the validator function and follow its logic to check your data.
What does the proposed API look like?
props: {
  foobar: {
    type: Object,
    required: true,
    validator: function(value) {
      // Default error message
      if (!value.foo) return false;

      try {
        JSON.parse(value.foo);
      }
      catch (e) {
        // Custom message
        return 'foobar: foo property isn\'t valid JSON!';
      }

      // Validated
      return true;
    }
  }
}

Any progress on when this will be added?