firebase with ESP8266

Failed to read/write data to firebase.
``#include <ESP8266WiFi.h>
#include <FirebaseArduino.h>
// Set these to run example.
#define FIREBASE_HOST "esp8266-fbd9c.firebaseio.com/"
#define FIREBASE_AUTH "serect_key"
#define WIFI_SSID "SSID_name"
#define WIFI_PASSWORD "password"
void setup() {
Serial.begin(115200);
// connect to wifi.
WiFi.begin(WIFI_SSID, WIFI_PASSWORD);
Serial.print("connecting");
while (WiFi.status() != WL_CONNECTED) {
Serial.print(".");
delay(500);
}
Serial.println();
Serial.print("connected: ");
Serial.println(WiFi.localIP());
Firebase.begin(FIREBASE_HOST, FIREBASE_AUTH);
}
int n = 0;
void loop() {
// set value
Firebase.setFloat("number", 42.0);
// handle error
if (Firebase.failed()) {
Serial.print("setting /number failed:");
Serial.println(Firebase.error());
return;
}
delay(1000);
// update value
Firebase.setFloat("number", 43.0);
// handle error
if (Firebase.failed()) {
Serial.print("setting /number failed:");
Serial.println(Firebase.error());
return;
}
delay(1000);
// get value
Serial.print("number: ");
Serial.println(Firebase.getFloat("number"));
delay(1000);
// remove value
Firebase.remove("number");
delay(1000);
// set string value
Firebase.setString("message", "hello world");
// handle error
if (Firebase.failed()) {
Serial.print("setting /message failed:");
Serial.println(Firebase.error());
return;
}
delay(1000);
// set bool value
Firebase.setBool("truth", false);
// handle error
if (Firebase.failed()) {
Serial.print("setting /truth failed:");
Serial.println(Firebase.error());
return;
}
delay(1000);
// append a new value to /logs
String name = Firebase.pushInt("logs", n++);
// handle error
if (Firebase.failed()) {
Serial.print("pushing /logs failed:");
Serial.println(Firebase.error());
return;
}
Serial.print("pushed: /logs/");
Serial.println(name);
delay(1000);
}``
Am using Arduino IDE 1.8.5
ESP8266MOD

Im having the same issue as well. I found the secret key for the database but it says that its been deprecated and that the code needs to be updated with the firebase admin sdk. However the most obvious ways are only for android, ios, and web applications....

Does anyone show this error below and how to fix it
/Users/huifengchen/Documents/Arduino/libraries/firebase-arduino-master/src/FirebaseHttpClient_Esp8266.cpp: In member function 'virtual std::string FirebaseHttpClientEsp8266::errorToString(int)':
/Users/huifengchen/Documents/Arduino/libraries/firebase-arduino-master/src/FirebaseHttpClient_Esp8266.cpp:83:11: error: 'errorToString' is not a member of 'HTTPClient'
return HTTPClient::errorToString(error_code).c_str();

@JuanPTM sir there is possible that there a problem on circuit that's why it failed? can  you help me? i have the same problem above..

@Jackfr0zt sorry but i can't help you, I've never use an ESP with and Arduino UNO, just used a NodeMCU or WEMOS.

Looks like Database Secrets is deprecated. Anyone know what is takes to use a non-deprecated method?

any updates on the firebase-arduino?

Same issues faced while setting up nodemcu with firebase. not able to push/get data even after modifying the KEY in firebaseHttpclient.
a.txt
This is my code. Thanks in advance

Got it... the issue was with wifi connection

I'm having the same problem, I downloaded it again, updated but it does not work.
Someone?

Ive had that issue and changed the arduino ide to a older version. I think
18.3
On Tue, Mar 13, 2018 at 1:25 PM, heriveltogabriel<EMAIL_ADDRESS>wrote:

I'm having the same problem, I downloaded it again, updated but it does
not work.
Someone?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/firebase/firebase-arduino/issues/310#issuecomment-372806298,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AK-f4zyO6rd3rR650aTExsYFPczqxsKHks5teCtNgaJpZM4RQm7B
.

Documents\Arduino\libraries\firebase-arduino-master\src\FirebaseHttpClient_Esp8266.cpp:83:11: error: 'errorToString' is not a member of 'HTTPClient'
return HTTPClient::errorToString(error_code).c_str();

this is error can u please help me with this

@JuanPTM
I'm struggling to make the firebase example running on esp8266. I tried everything that's available on the online forums with no luck. Are you sure that Google still allows to use the deprecated secret_key inside Database Secrets?
Any help would be a great help.
Thanks,
Sharan

I have successfully tested on Node MCU
I love to help anybody.

Just try to download your library again and upgrade your ide. Hope that ll work

As per my research most of 8266 code not compatible with wemos D1. Try is on node MCU .I will try to help.

Folks,
FYI, finally I'm able to run the firebase samples successfully on Wemos D1 Mini. I think firebase library has a dependancy on arduinojson library. Once I included it, everything went smooth.
Thanks for your inputs.

Never had any problems with D1 Mini, in fact it is the most used controller for me.
And FYI, this is in the main readme:
Dependencies
FirebaseArduino now depends on ArduinoJson library instead of containing it's own version of it. Please either use Library Manager or download specific version of the library from github.

Filed #349 to improve error messaging, I hope it can clear some of the issues reported here.

Failed to set data to firebase database, I am using Wemos Mini, and I have include ArduinoJson Library but it is still not working
#include <ESP8266WiFi.h>
#include <FirebaseArduino.h>
#include <ArduinoJson.h>
// Set these to run example.
#define FIREBASE_HOST "waterlevel-ff5c0.firebaseio.com"
#define FIREBASE_AUTH "vnpv6YNyX3qOZWalKh5dgAHe69yZKrC1BAXXtkA4"
#define WIFI_SSID "Dan"
#define WIFI_PASSWORD "Danick007@ROSS"
void setup() {
Serial.begin(9600);
// connect to wifi.
WiFi.begin(WIFI_SSID, WIFI_PASSWORD);
Serial.print("connecting");
while (WiFi.status() != WL_CONNECTED) {
Serial.print(".");
delay(500);
}
Serial.println();
Serial.print("connected: ");
Serial.println(WiFi.localIP());
Firebase.begin(FIREBASE_HOST, FIREBASE_AUTH);
}
int n = 0;
void loop() {
// set value
Firebase.setFloat("MaxWaterLevel", 42.0);
// handle error
if (Firebase.failed()) {
Serial.print("setting /number failed:");
Serial.println(Firebase.error());
return;
}
delay(1000);
}

Please am having the same issue on my nodeMCU, any solution??

i am having the same problem any solution -thanks
#include <ESP8266WiFi.h>
#include <FirebaseArduino.h>
// Set these to run example.
#define FIREBASE_HOST "xxxxxxxx.firebaseio.com"
#define FIREBASE_AUTH "5OJ4r2dGMESZP0juJDKPf4Ky51QDa39TzV8snS9K"
char* WIFI_SSID = "RK";
char* WIFI_PASSWORD = "m2tusu4fpyrk";
void setup() {
Serial.begin(115200);
// connect to wifi.
WiFi.begin(WIFI_SSID, WIFI_PASSWORD);
Serial.print("connecting");
while (WiFi.status() != WL_CONNECTED) {
Serial.print(".");
delay(500);
}
Serial.println();
Serial.print("connected: ");
Serial.println(WiFi.localIP());
Firebase.begin(FIREBASE_HOST,FIREBASE_AUTH);
}
void loop()
{
// set value
Firebase.getInt("fir-demo-b1a3e/ram");
// handle error
if (Firebase.failed())
{
Serial.print("setting /number failed:");
Serial.println(Firebase.error());
return;
}
}
output:
setting /number failed:
setting /number failed:
setting /number failed:
setting /number failed:
setting /number failed:
setting /number failed:
setting /number failed:

remove / from   **.firebaseio.com/**. IT worked for me now

I am searching for solution till now but don't get any.....
Please Post your code that will helpful to me.
Thanks.

I have successfully tested on Node MCU
I love to help anybody.

I am searching for solution till now but don't get any.....
Please Post your code that will helpful to me.
Thanks.

Its fixed!!!
go to C:/Users/{username}/My Documents/Arduino/libraries/firebase-arduino-master/src
open FirebaseHttpClient.h file, and paste following fingerprint =>
6F D0 9A 52 C0 E9 E4 CD A0 D3 02 A4 B7 A1 92 38 2D CA 2F 26
Now build and upload the sketch to NodeMCU using Arduino IDE

still the same situation repeating
can you please provide your code...
thanks

Its fixed!!!
go to C:/Users/{username}/My Documents/Arduino/libraries/firebase-arduino-master/src
open FirebaseHttpClient.h file, and paste following fingerprint =>
6F D0 9A 52 C0 E9 E4 CD A0 D3 02 A4 B7 A1 92 38 2D CA 2F 26
Now build and upload the sketch to NodeMCU using Arduino IDE

still the same situation repeating
can you please provide your code...
thanks

Add the below header files to your code
#include <FirebaseArduino.h>
#include <Firebase.h>
#include <FirebaseCloudMessaging.h>
#include <FirebaseError.h>
#include <FirebaseHttpClient.h>
#include <FirebaseObject.h>
#include <ESP8266WiFi.h>
followed by
go to C:/Users/{username}/My Documents/Arduino/libraries/firebase-arduino-master/src
open FirebaseHttpClient.h file, and paste following fingerprint =>
6F D0 9A 52 C0 E9 E4 CD A0 D3 02 A4 B7 A1 92 38 2D CA 2F 26
Now build and upload the sketch to NodeMCU or ESP01 using Arduino IDE.
This procedure works guaranteed with ESP01.

Its fixed!!!
go to C:/Users/{username}/My Documents/Arduino/libraries/firebase-arduino-master/src
open FirebaseHttpClient.h file, and paste following fingerprint =>
6F D0 9A 52 C0 E9 E4 CD A0 D3 02 A4 B7 A1 92 38 2D CA 2F 26
Now build and upload the sketch to NodeMCU using Arduino IDE

still the same situation repeating
can you please provide your code...
thanks

here is the code I am using-
#include <ESP8266WiFi.h>
#include<FirebaseArduino.h>
#define FIREBASE_HOST "test.firebaseio.com" //Your Firebase Project URL goes here without "http:" , "" and "/"
#define FIREBASE_AUTH "firebase_secret_key" //Your Firebase Database Secret goes here
#define WIFI_SSID "wifi_name" //your WiFi SSID for which yout NodeMCU connects
#define WIFI_PASSWORD "wifi_password"//Password of your wifi network
#define DEVICE1 D1
#define DEVICE2 D2
#define DEVICE3 D3
#define DEVICE4 D4
#define Device1Text "Device1"
#define Device2Text "Device2"
#define Device3Text "Device3"
#define Device4Text "Device4"
void setup() {
// put your setup code here, to run once:
Serial.begin(115200); //baud rate ,if you want to see the process in the serial monitor ,same baud rate should be set.
pinMode(DEVICE1,OUTPUT);
WiFi.begin(WIFI_SSID,WIFI_PASSWORD);
Serial.print("connecting");
while (WiFi.status()!=WL_CONNECTED){
Serial.print(".");
delay(500);
}
Serial.println();
Serial.print("connected:");
Serial.println(WiFi.localIP());
Firebase.begin(FIREBASE_HOST,FIREBASE_AUTH);
if (Firebase.failed()) {
Serial.print("setting number failed:");
Serial.println(Firebase.error());
firebasereconnect();
return;
}
}
void firebasereconnect()
{
Serial.println("Trying to reconnect");
Firebase.begin(FIREBASE_HOST, FIREBASE_AUTH);
}
int signal1;
int signal2;
int signal3;
int signal4;
void loop() {
if (Firebase.failed()) {
Serial.print("setting number failed:");
Serial.println(Firebase.error());
firebasereconnect();
return;
}
signal1=Firebase.getString(Device1Text).toInt();
if(signal1 == 1){
digitalWrite(DEVICE1,HIGH);
Serial.println("lightON");
}
else if(signal1 == 0){
digitalWrite(DEVICE1,LOW);
Serial.println("lightOFF");
}
signal2=Firebase.getString(Device2Text).toInt();
if(signal2 == 1){
digitalWrite(DEVICE2,HIGH);
Serial.println("lightON");
}
else if(signal2 == 0){
digitalWrite(DEVICE2,LOW);
Serial.println("lightOFF");
}
signal3=Firebase.getString(Device3Text).toInt();
if(signal3 == 1){
digitalWrite(DEVICE3,HIGH);
Serial.println("lightON");
}
else if(signal3 == 0){
digitalWrite(DEVICE3,LOW);
Serial.println("lightOFF");
}
signal4=Firebase.getString(Device4Text).toInt();
if(signal4 == 1){
digitalWrite(DEVICE4,HIGH);
Serial.println("lightON");
}
else if(signal4 == 0){
digitalWrite(DEVICE4,LOW);
Serial.println("lightOFF");
}
}
I am using 4 devices to control using Relay. And using NodeMCU 12E
Everything is working smoothly.

Thank you very much bro your code is very very very helpful to me......

Its fixed!!!
go to C:/Users/{username}/My Documents/Arduino/libraries/firebase-arduino-master/src
open FirebaseHttpClient.h file, and paste following fingerprint =>
6F D0 9A 52 C0 E9 E4 CD A0 D3 02 A4 B7 A1 92 38 2D CA 2F 26
Now build and upload the sketch to NodeMCU using Arduino IDE

still the same situation repeating
can you please provide your code...
thanks

Add the below header files to your code
#include <FirebaseArduino.h>
#include <Firebase.h>
#include <FirebaseCloudMessaging.h>
#include <FirebaseError.h>
#include <FirebaseHttpClient.h>
#include <FirebaseObject.h>
#include <ESP8266WiFi.h>
followed by
go to C:/Users/{username}/My Documents/Arduino/libraries/firebase-arduino-master/src
open FirebaseHttpClient.h file, and paste following fingerprint =>
6F D0 9A 52 C0 E9 E4 CD A0 D3 02 A4 B7 A1 92 38 2D CA 2F 26
Now build and upload the sketch to NodeMCU or ESP01 using Arduino IDE.
This procedure works guaranteed with ESP01.

#ifndef FIREBASE_HTTP_CLIENT_H
#define FIREBASE_HTTP_CLIENT_H
#include
#include "Arduino.h"
#include "Stream.h"
struct HttpStatus {
static const int TEMPORARY_REDIRECT = 307;
};
class FirebaseHttpClient {
public:
static FirebaseHttpClient* create();
virtual void setReuseConnection(bool reuse) = 0;
virtual void begin(const std::string& url) = 0;
virtual void begin(const std::string& host, const std::string& path) = 0;
virtual void end() = 0;
virtual void addHeader(const std::string& name, const std::string& value) = 0;
virtual void collectHeaders(const char* header_keys[],
const int header_key_count) = 0;
virtual std::string header(const std::string& name) = 0;
virtual int sendRequest(const std::string& method, const std::string& data) = 0;
virtual std::string getString() = 0;
virtual Stream* getStreamPtr() = 0;
virtual std::string errorToString(int error_code) = 0;
virtual bool connected() = 0;
protected:
static const uint16_t kFirebasePort = 443;
};
static const char kFirebaseFingerprint[] =
"6F D0 9A 52 C0 E9 E4 CD A0 D3 02 A4 B7 A1 92 38 2D CA 2F 26"; // 2019-04
#endif  // FIREBASE_HTTP_CLIENT_H
I had replaced this row :
static const char kFirebaseFingerprint[] =
"B6 F5 80 C8 B1 DA 61 C1 07 9D 80 42 D8 A9 1F AF 9F C8 96 7D"; // 2019-04
with :
static const char kFirebaseFingerprint[] =
"6F D0 9A 52 C0 E9 E4 CD A0 D3 02 A4 B7 A1 92 38 2D CA 2F 26"; // 2019-04
is that what you mean ?

Its fixed!!!
go to C:/Users/{username}/My Documents/Arduino/libraries/firebase-arduino-master/src
open FirebaseHttpClient.h file, and paste following fingerprint =>
6F D0 9A 52 C0 E9 E4 CD A0 D3 02 A4 B7 A1 92 38 2D CA 2F 26
Now build and upload the sketch to NodeMCU using Arduino IDE

still the same situation repeating
can you please provide your code...
thanks

here is the code I am using-
#include <ESP8266WiFi.h>
#include<FirebaseArduino.h>
#define FIREBASE_HOST "test.firebaseio.com" //Your Firebase Project URL goes here without "http:" , "" and "/"
#define FIREBASE_AUTH "firebase_secret_key" //Your Firebase Database Secret goes here
#define WIFI_SSID "wifi_name" //your WiFi SSID for which yout NodeMCU connects
#define WIFI_PASSWORD "wifi_password"//Password of your wifi network
#define DEVICE1 D1
#define DEVICE2 D2
#define DEVICE3 D3
#define DEVICE4 D4
#define Device1Text "Device1"
#define Device2Text "Device2"
#define Device3Text "Device3"
#define Device4Text "Device4"
void setup() {
// put your setup code here, to run once:
Serial.begin(115200); //baud rate ,if you want to see the process in the serial monitor ,same baud rate should be set.
pinMode(DEVICE1,OUTPUT);
WiFi.begin(WIFI_SSID,WIFI_PASSWORD);
Serial.print("connecting");
while (WiFi.status()!=WL_CONNECTED){
Serial.print(".");
delay(500);
}
Serial.println();
Serial.print("connected:");
Serial.println(WiFi.localIP());
Firebase.begin(FIREBASE_HOST,FIREBASE_AUTH);
if (Firebase.failed()) {
Serial.print("setting number failed:");
Serial.println(Firebase.error());
firebasereconnect();
return;
}
}
void firebasereconnect()
{
Serial.println("Trying to reconnect");
Firebase.begin(FIREBASE_HOST, FIREBASE_AUTH);
}
int signal1;
int signal2;
int signal3;
int signal4;
void loop() {
if (Firebase.failed()) {
Serial.print("setting number failed:");
Serial.println(Firebase.error());
firebasereconnect();
return;
}
signal1=Firebase.getString(Device1Text).toInt();
if(signal1 == 1){
digitalWrite(DEVICE1,HIGH);
Serial.println("lightON");
}
else if(signal1 == 0){
digitalWrite(DEVICE1,LOW);
Serial.println("lightOFF");
}
signal2=Firebase.getString(Device2Text).toInt();
if(signal2 == 1){
digitalWrite(DEVICE2,HIGH);
Serial.println("lightON");
}
else if(signal2 == 0){
digitalWrite(DEVICE2,LOW);
Serial.println("lightOFF");
}
signal3=Firebase.getString(Device3Text).toInt();
if(signal3 == 1){
digitalWrite(DEVICE3,HIGH);
Serial.println("lightON");
}
else if(signal3 == 0){
digitalWrite(DEVICE3,LOW);
Serial.println("lightOFF");
}
signal4=Firebase.getString(Device4Text).toInt();
if(signal4 == 1){
digitalWrite(DEVICE4,HIGH);
Serial.println("lightON");
}
else if(signal4 == 0){
digitalWrite(DEVICE4,LOW);
Serial.println("lightOFF");
}
}
I am using 4 devices to control using Relay. And using NodeMCU 12E
Everything is working smoothly.

Thank you very much bro your code is very very very helpful to me......

could you please til us what was the solution for the problem?

Change your firebase url in your source
Don't include http: in your source file of firebase url statement
Example:
#define FIREBASE_HOST "myfirebase-url.firebase.com";
Don't include http in url
Hope this helps


chore(app): Update default session image to renku/renkulab-py:3.9-0.17.0

Generated automatically on a new release in renkulab-docker to update the default image used when launching a user session.

We skipped a version we are already on 0.18.0.


"An argument" description for some commands

I think this happens when the command is not recognize, but not sure.
How to reproduce
Try, for example, ansible

Hi @FerPerales , thanks for reporting this.
You assumed right. This message is displayed when the client doesn't find a match for the program you just queried. The message could be improved in order to tell the user that the program ansible is not supported yet. I'll definitely keep ansible under the radar and try to integrate it soon.
You can check the list of supported programs here https://github.com/ediardo/kmdr.sh#supported-programs. Let me know if you think of more programs we should support as it helps us to focus on important use cases.

It will be fixed in v.0.2 #21

Superb. Waiting for it.


Swap cell arrays instead of allocating new ones

This should fix the issue described in https://github.com/jeremywen/JW-Modules/issues/46.

Thank you for this fix!  The same change will need to be done for similar modules noteseq16 and patterns.  I can do that if you want.

On Sep 28, 2019, at 11:55 PM, Federico Bond<EMAIL_ADDRESS>wrote:
This should fix the issue described in #46.
You can view, comment on, or merge this pull request online at:
https://github.com/jeremywen/JW-Modules/pull/47
Commit Summary
Swap cell arrays instead of allocating new ones
File Changes
M src/NoteSeq.cpp (28)
Patch Links:
https://github.com/jeremywen/JW-Modules/pull/47.patch
https://github.com/jeremywen/JW-Modules/pull/47.diff
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

NoteSeq16 does not changes AFAIK because the algorithms are implemented differently. I added the changes to Patterns though. Should be ready to merge.

Thank You.  I will test this out now.


Benchmarking tests: automatically restore Neon reuse databases, too and migrate to pg16

IMPORTANT: FIRST WE NEED TO DEPLOY NEW GITHUB SECRETS FOR NEON REUSE DB
Problem
We use a set of Neon reuse databases in benchmarking.yml which are still using pg14.
Because we want to compare apples to apples and have migrated the AWS reuse clusters to pg16 we should also use pg16 for Neon.
Summary of changes

Automatically restore the test databases for Neon project

test is running https://github.com/neondatabase/neon/actions/runs/10373076535/job/28717325073


Support for static reverse proxying with SSL

Add support for proxy destinations that are "off-box" and not in docker containers. For example, It would be great to be able to have an encrypted connection land on the nginx-proxy docker container, and then travel unencrypted to the destination server (which isn't a container).
nginx-proxy supports adding a configuration file to achieve this end, but nginx-letsencrypt has no method to handle generating/managing the certificates for this sort of situation.
Perhaps permit allowing some environment variables for passing in additional hostnames/emails for certificates that should be managed, regardless of container existence?

Dupe of #127, though that one was arguably never resolved.

Yeah, only a workaround, would be interested in this

The best is perhaps to use another solution like traefik

if you are still having problem with it, I solved it by using another nginx container to serve the static directory, like so:
# other lines

static-main-site:
     restart: always
     image: nginx:alpine
     volumes:
       - ./static/path:/usr/share/nginx/html:ro
     environment:
       - VIRTUAL_HOST=www.domain.com,domain.com
       - VIRTUAL_NETWORK=nginx-proxy
       - VIRTUAL_PORT=80
       - LETSENCRYPT_HOST=www.domain.com,domain.com
       -<EMAIL_ADDRESS>

I would love to be able to put some config somewhere for a reverse https proxy with letsencrypt SSL. This would also work if u for some reason don't want to use docker socket.

An experimental feature allowing to generate certificates from a config file instead of containers env var (inspired by @ymettier PR #220) has been added to dev.
This instructions are here. Any feedback is welcome.
Closing in favor of #386 so we can keep track of this in a single issue.


Why token_expires is emitted twice? Bug?

Describe the bug
I use setupAutomaticSilentRefresh and I found that the event token_expires is emitted twice what makes refreshing code request twice so, I went to the implementation of the method and found that setupAutomaticSilentRefresh calls restartRefreshTimerIfStillLoggedIn and this calls setupExpirationTimers. In this flow the method clearAccessTokenTimer is not called as it is done for setupRefreshTimer that is called in the OAuthService constructor.
Implementation:

clearAccessTokenTimer is called before setupExpirationTimers what makes sense to unsubscribe from any previous timeouts
but when using setupAutomaticSilentRefresh there is no call to clearAccessTokenTimer and this creates another subcription that is not handled

After all this, my assumption is that there is a bug but, I preferred to report it as a question as I may miss something in the way.
Desktop (please complete the following information):

Angular ^14.3.0
angular-oauth2-oidc: ^14.0.1
Browser edge
Version 115.0.1901.200

Additional methods used:
configure, loadDiscoveryDocumentAndTryLogin and initCodeFlow

I'm a little late to the show but this is definitely a bug. Ideally, all timers/subscriptions should be cleared/unsubscribed internally before starting a new one. We've run into issues because of this as well but we were able to workaround the bug by manually unsubscribing to all events by calling stopAutomaticRefresh() just prior to calling any functions that may create new subscriptions (ie. configure() and setupAutomaticSilentRefresh()). Hopefully this workaround will help anyone that's stuck dealing with this issue.


Validate properly on GitHub actions

At the moment we don't seem to be running the tests on GitHub Actions. Let's use this ticket as an epic to cover any updates required on GitHub Actions to get basic builds, tests and test coverage working.

[ ] Builds and tests
[ ] Test coverage report
[ ] Report to Slack on build / test


func onResize, func updateSlides fix for direction

direction horizontal to vertical, vertical to horizontal when resize window
Fixes #308

Hi, thanks for your PR. But again, it affect files not in src/ folder :) So i merged it manually with some restructuring. I am afraid it doesn't cover many use cases, but for basics it is fine.

Sorry, but I have question about mobile adaptation fow swiper. So, in version 3.4.1 when width of windows is 485px, we have two columns. If these colums with for example Testimonials, then we have so long text. It's not beautifully. When width is 320px, we have one columns. I look at code, but algorithm so dificult. How can I do two columns for width 485px. Thank you for answer.


Release Microsoft.Extensions.Logging.NLog?

We are a bit confused. There is some code here to get NLog working with ASP.Net 5, but it isn't released as NuGet package. Why not? Are there any troubles with this code? Do we (NLog) need to provide our own package?
Cheers,
Julian (NLog team)
Edit: I see this is related: https://github.com/aspnet/Logging/issues/292 (https://github.com/aspnet/Logging/issues/292#issuecomment-160706959)
PS: There is also a PR, which is unclear if it will be merged or rejected: https://github.com/aspnet/Logging/pull/262

There is some code here to get NLog working with ASP.Net 5, but it isn't released as NuGet package. Why not?

We don't own that product so we shouldn't be releasing it on nuget.

Do we (NLog) need to provide our own package?

Yes! We ideally want to delete this code from our repository. It was here to help validate our extensibility but we'd want the NLog team to own it (similar to how serilog took over).

Thanks for the quick response!
We will fix a package soon. If that is done, the code can be removed here :)
I will let you know!


line 99

Running the progress...
./install.sh:  line 99: ./IMEI-AndroidChanger.o Invalid argument
Where is the problem ?

same
./install.sh: line 99: ./IMEI-AndroidChanger.o Invalid argument

same here

The file you are trying to execute is not compatible with your operating system architecture. Your phone has a stock kernel, but requires a custom kernel to run. Find a flashed kernel with firmware for your device, install ANDRAX/NetHunter or work as root on Termux and everything will work


connect to supabase

Describe the bug
can't connect to supabase
Link to the Bolt URL that caused the error
https://bolt.new/~/sb1-qtlk7ax8
Validations

[X] Please make your project public or accessible by URL. This will allow anyone trying to help you to easily reproduce the issue and provide assistance.

Steps to reproduce
click connect to supabase
Expected behavior
connection with supabase
Screen Recording / Screenshot
No response
Platform
Browser name = Chrome
Full version = <IP_ADDRESS>
Major version = 131
navigator.appName = Netscape
navigator.userAgent = Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/<IP_ADDRESS> Safari/537.36
performance.memory = {
  "totalJSHeapSize": 307782924,
  "usedJSHeapSize": 298521516,
  "jsHeapSizeLimit":<PHONE_NUMBER>
}
Username = Guillaume Rostand
Chat ID = c8c02a1b1260

Additional context
Error:
Could not connect to Supabase.

they should have warned someone about this. I didnt know what was wrong it auto connected this morning. I didnt know what was happening. Now I cant connect at all.


[MISC] Velox maintainers as triage member(collaborators)

What changes were proposed in this pull request?
This patch adds Velox maintainer Deepak and Pedro as triage member(collaborators), so they could help to manage the issues related with Velox easier.
How was this patch tested?
no tests required

Thanks, @zhouyuan!

Just noted the PR. @zhouyuan can you also add @yingsu00 @surnaik @xiaoxmeng @zaziz_pins and @ArnavBalyan. Let's have at least one from each Gluten customer as collaborators so they can easily manage their issues.

Just noted the PR. @zhouyuan can you also add @yingsu00 @surnaik @xiaoxmeng @zaziz_pins and @ArnavBalyan. Let's have at least one from each Gluten customer as collaborators so they can easily manage their issues.

Sounds good! Will follow up to add more as collaborators
-yuan


Does not autmatically load restored closed tabs

I don't know if it's by design (or perhaps an interaction with another addon?): if I restore a closed tab with Ctrl-Shift-T that tab is restored but not loaded, so I get a tab with "Tab unloaded by LoadTabOnSelect." as the whole content, and I have to flip tabs to load that tab.
Firefox 56.0.1 (64 bit), Windows 10

Same for me

Same for me when trying to reload tabs from the OneTab plugin. Same error message as in the OP.

Yeah, you get this in the URL bar: "moz-extension://d22fa2fb-aba0-8149-97b5-e26191987d2a/html/tab.html?managedUrl=https://original.url.here". If you delete everything but the original URL, you get the content you expect back. This should be happening automatically.


using UseIdentityServerBearerTokenAuthentication

I'm using the following code to ensure my access token is correct
            JwtSecurityTokenHandler.InboundClaimTypeMap = ClaimMappings.None;

            app.UseIdentityServerBearerTokenAuthentication(new IdentityServerBearerTokenAuthenticationOptions
            {
                Authority = "https://localhost:44310/identity",
                RequiredScopes = new[] { "csRA" },
            });

I was expecting that any request that came through that did not have this scope would return a 404 and exit the pipeline, but instead it seems as though the pipeline continues with an unauthenticated user instead.
I'm using Owin and WebApi 2.2 and the above are the first lines in my startup class.  Should I be adding this method to the end of my startup instead?

You still need to have an [Authorize] attribute on your Web APIs.

yep, have that in all cases, but honestly I'm not 100% sure I understand why I would need that.  Is it the case that UseIdentityServerBearerTokenAuthentication is saying "when authentication is required, make sure the token contains this scope?" and that is why the request continues so that the [Authorize] attribute can be evaluated?

Authentication happens first. Authorization is the job of the application layer (typically).

oh.  duh!  so if I want to force Authentication for all requests, I'd need to use an Authentication filter in addition to UseIdentityServerBearerTokenAuthentication (which is part of authorization)?

You mean authorization, right? The bearer token is authentication. If that works, then great, but if not then the request is anonymous. Authorization ensures that the current request is allowed. If anonymous is not allowed, then that authorization is required.

The scope is only enforced when a valid token has been found. Otherwise the request is anonymous.
You need additional authZ rules - in any case.

@brockallen that isn't what I meant, but it's clear now.  This all comes down to one of my injected services that depends on an authenticated user.  Now that I understand this process better I can handle the unauthenticated use case.  I was thinking the UseIdentityServerBearerTokenAuthentication method would prevent the request getting all the way down the pipeline but I get it now.


High Availability - Fault Tolerance

Hi,
I did a test (I have only one master):

I launched one job
I stop metronome service (on Centos console)
I started the service again
Result: I have two running instances of my job.

Note: This issue has been migrated to https://jira.mesosphere.com/browse/MARATHON-1658. For more information see https://groups.google.com/forum/#!topic/marathon-framework/khtvf-ifnp8.


[(old)azeventgrid] delete old package. It's been released (deprecated) and should no longer be used

In case you want to see the deprecation notice: https://pkg.go.dev/github.com/Azure/azure-sdk-for-go/sdk/messaging/azeventgrid

Fairly certain I have to override checks on this since I'm removing the folder.


Flickering drop down menus

Description of the Issue
Drop down menus flicker. I've noticed this on the top right menu and the currenty setting in the settings submenu. Both menu flicker for approx 1 second each time I click on them. I've tried recording a video of it, it didn't quite capture what it looks like, which is probably because the flickering is so fast. Note that this only happens when Joule is open within an existing browser window, not when I open it through the "Full page" action.
Steps to Reproduce
Click the top right dropdown menu or the currency setting menu.
Description of Your Setup
Browser & version: Firefox 66
Operating system: Ubuntu 18.10
Node software & version: LND 0.5.2
Console Logs / Screenshots
https://gfycat.com/DrearyGiddyGroundhog

Thanks for the report, looks like this happening only in Firefox. We're using ant design for this dropdown, so it's probably going to require an upstream fix. However, I can't get it to happen in their docs for the dropdown component, so it's possible I'm doing something wrong here.

I can not reproduce either in their docs. Note that I'm not seeing this behavior when Joule is opened in its own page, just with the small extension window. Could that affect this?

I've played around with this a bunch and haven't found a clean fix. Hopefully this is just a Firefox rendering bug (likely to do with multiple transforms / z-index stuff, explaining why it only happens in the popover) and gets fixed. But I'll leave this open until it's finally licked.


Sunsetting DEPNotify integration

I'd like to sunset DEPNotify integration for a few reasons:

There are a few edge cases
Not every command is supported
I had to make assumptions that an admin may disagree with
There are now multiple flavors of "DEPNotify" that I have no intention of supporting.

If you object with this, please comment and we can discuss. I will leave this open for a week or two and then pull the integration, unless I am convinced otherwise.
In place will be some example scripts that an admin can use and recommended approaches for the JSON.

Those reasons sound pretty solid to me. I'm pretty sure I hit a few of those edge cases while building out our workflows.
With DEPNotify being integrated with NoMAD Login, IAs probably would have needed significant code changes to support that, too. I agree that it's best to separate out the DEPNotify support, since IAs is flexible enough to allow me to build out what I need on my own (that said, I appreciate the example code 😉).
Thanks, Erik.

Simpler is better. I’m also not using this project so my opinion doesn’t
really matter.
On Wed, Oct 31, 2018 at 11:40 AM Mike Solin<EMAIL_ADDRESS>wrote:

Those reasons sound pretty solid to me. I'm pretty sure I hit a few of
those edge cases while building out our workflows.
With DEPNotify being integrated with NoMAD Login, IAs probably would have
needed significant code changes to support that, too. I agree that it's
best to separate out the DEPNotify support, since IAs is flexible enough to
allow me to build out what I need on my own (that said, I appreciate the
example code 😉).
Thanks, Erik.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/erikng/installapplications/issues/41#issuecomment-434756090,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACsz2FSGKm6DhWrhMrgHV6IFO_J5Xc_4ks5uqdJ8gaJpZM4YEbNT
.

--
Clayton Burlison
https://clburlison.com

I think this sounds reasonable.  Reducing complexity should improve maintainability overall.

Just yesterday I was thinking through following problem.

There is installapplication.py script doing its stuff sequentially (f.e. installing packages).
There is MDM pushing apps.
BUT macOS installer installs one package at the time.
-> This gives us race condition between package installs by installapplications.py and those form MDM.

As a result some package from setupassistant phase may not be yet installed when user logs in. Launch of DEPnotify by installapplication.py is therefore posponed until it gets to userland phase. This is not good when I need fullscreen DEPNotify just righ after first console log in.
This thread actually gave me right idea. I need my own LaunchAgents which if going to be part of bootstrap package along with DEPNotify.

I have removed the DEPNotify integration and updated the readme.


Expand and Flatten

This is the commit in which the Hash Map Helper class has been added. It has the recursive expand and flatten functions.

@thecmart out of curiosity, what is the purpose of this hashmap?

@alexfdz The GreenDao database can't store nested data like arrays or HashMaps but sometimes we want to store nested meta data. This function allows define data in a flat format like this:
{
    cities/1: London,
    cities/2: Berlin,
}

But to store it in Firebase as a nested hash map:
{
    cities: {
        1: London,
        2: Berlin,
    }
}


New components landing v2

We need to merge #5 first.

[x]  Add new gradient and optional shadow to BackgroundGradient
[x]  Stepper: add: background, header fluorescent, and back arrow
[x]  SectionLayout: border, image top, the content below
[x]  Check the typography of the new landing and adjust the theme

 The typo seems to be still there

I don't see it on the deployed version, also I don't see how a typo would affect the functionality :trollface:


Support for Razor4-beta6.

Be compatible with razor4-beta6, fixes #301, #310 and possibly #306 and #309 (after they switch to the latest 4.X beta containing this change).

Seems like they removed the @helper feature in beta4: https://github.com/aspnet/Razor/releases

Thank you Matt , Will keep you posted


move_and_slide_with_snap ignores RayShape collision shape in 3D

Godot version:
3.1 Beta 1
(can't test in Beta 2 due to 25227
Issue description:
When snapping to the floor the rayshape collision of kinematicBody 3D is ignored. Object snaps into the floor until i.e. the box shape of the 2nd collider hits the floor.
Steps to reproduce:

Add boxshape and rayshape to kinematic body
rayshape has to be lower than box shape
move kinematicbody 3D to floor with move_and_slide_with_snap
as soon as body snaps to floor, it sinks in to the box shape, ignoring the rayshape

Minimal reproduction project:

red ball has box shape
green ball ray shape
yellow ball box and rayshape
yellow ball snaps into the floor. (use Beta 1! In Beta 2 the Rayshape is broken)
RayShapeBug.zip

Another thing I noticed is that the green ball (only rayshape) does not stand still on the floor. It jumps up and down a little bit.

The issue happens with both Bullet and GodotPhysics. Still reproducible in the current master branch (88a36e20).


[Request] some way to set your current status (online, offline)

API seems to be PUT @ https://client-s.gateway.messenger.live.com/v1/users/ME/presenceDocs/messagingService
{status: "Online"} was the payload

Already implemented


Add CacheHeaders

We need a way to pass metadata for the cache. Examples might be TTL or offlineCritical.
This header info will be passed to CacheStore for read and writes. As CacheStore is user configurable, I feel we should make this CacheHeader a key-value String map. This allows a user to add custom CacheHeaders that make sense for their individual cache.
Couple options on how to implement for the API:
public final class CacheControl {
     public CacheControl(CacheFetchPolicy) ...
     public CacheControl(CacheFetchPolicy, Map<String, String> cacheHeaders)
}

public enum CacheFetchPolicy {
  CACHE_FIRST,
  CACHE_ONLY,
  NETWORK_FIRST,
  NETWORK_ONLY,
}

or in ApolloCall just:
  @Nonnull ApolloCall<T> cacheControl(@Nonnull CacheControl cacheControl);
 @Nonnull ApolloCall<T> cacheControl(@Nonnull CacheControl cacheControl, @Nullable Map<String, String> cacheHeaders);

But if we talking about TTL that completely on the impl of cache store, when writing response to cache impl of normalized cache store should add this to the record

As for offlineCritical  I'm not sure that we need this option, you can get this functionality by setting TTL to some large value, and cache store will keep records for a long time

But don't we want different TTL for different requests? Some request (say a message thread) should never be evicted (or at least, have a very low eviction priority). Whereas a temporary search results should be evicted quickly.

But don't we want different TTL for different requests

Should it be defined by request or by record? CacheStore implementation when merge records can attach different TTL for different records. The only that we are missing the type of the record.

Some request (say a message thread) should never be evicted

What if the message referenced to user, this TTL for messages will be used as TTL for user as well?

The message/user case you brought up is the perfect example as to why it needs to be on the request:
If a message request stores a user, and the message is marked as "never expire", we expect that anytime I run that request, it will return -- including the user.
However, a different request, this time just for a user  may be marked as "ttl 1 minute". Although this request accesses the same record in the normalized cache, the cache should actually return null if the record hasn't been updated in more than 1 minute.
The general sentiment I trying to drive at is that TTL to record is many to one, whereas TTL to request is 1:1.
There are many variations of how to approach this (we plan to only use offline-critical, and no TTL) -- but fundamentally it seems to me that this metadata belongs to the request -- not the record.

Ok if we just pass the Operation from RealApolloCall to com.apollographql.android.cache.normalized.RealCache#write -> com.apollographql.android.cache.normalized.CacheStore#merge will it be enough info for user cache store implementation to have TTL per request?

The only concern/question now from design perspective CacheStore knows about Operation, should it?

I feel like passing the whole Operation is too much information (though it is an option). It would also require hand-coding the TTL requirement for every different operation type on the cache (or, again, attaching some metadata to the operation itself).
On the flipside -- we already have the concept of CacheControl, which could easily be passed to the cache. It seems pretty harmless to add a generic (and completely optional) cache control header map to this object.
What do other's think? @digitalbuddha @brianPlummer @marwanad
cc @martijnwalraven - don't think iOS has this yet, but would appreciate your input. (Also fyi roughly CacheStore = iosNormalizedCache, Cache = iosStore. Though, I think there is some value on standardizing names soon.)


Add support for max_tokens = -1 for LlamaCPP

Calculate max_tokens
Added a '_get_max_tokens' function to the LlamaCpp wrapper to calculate the max_tokens if the max_token paramter is set to -1 (similar to the BaseOpenAI wrapper). Setting max_tokens = -1 returns as many tokens as possible given the prompt and the models maximal context size.
Who can review?
@agola11

@masands Hi , could you, please, resolve the merging issues and address the last comments (if needed)? After that, ping me and I push this PR for the review. Thanks!

Closing because the PR wouldn't line up with the current directory structure of the library (would need to be in /libs/langchain/langchain instead of /langchain). Feel free to reopen against the current head if it's still relevant!


username without the @domain.com

I'm trying to authenticate a user named "username" however it seems this system is adding on the @domain.edu extension, and then failing...
In the API tester web app, I only typed in username, but it is using<EMAIL_ADDRESS>AUTH USER<EMAIL_ADDRESS>password
BACK FROM AUTH { InvalidCredentialsError: InvalidCredentialsError
at messageCallback (/usr/local/lib/node_modules/addict/node_modules/ldapjs/lib/client/client.js:1419:45)
at Parser.onMessage (/usr/local/lib/node_modules/addict/node_modules/ldapjs/lib/client/client.js:1089:14)
at emitOne (events.js:115:13)
at Parser.emit (events.js:210:7)
at Parser.write (/usr/local/lib/node_modules/addict/node_modules/ldapjs/lib/messages/parser.js:111:8)
at Socket.onData (/usr/local/lib/node_modules/addict/node_modules/ldapjs/lib/client/client.js:1076:22)
at emitOne (events.js:115:13)
at Socket.emit (events.js:210:7)
at addChunk (_stream_readable.js:252:12)
at readableAddChunk (_stream_readable.js:239:11)
lde_message: '80090308: LdapErr: DSID-0C090400, comment: AcceptSecurityContext error, data 52e, v1db1\u0000',
lde_dn: null } false

What's the full DN of the user? These usually have the FQDN appended to it, so addict does it by default.

I don't know a lot about AD (which is why I'm interested in REST web interface to it :) )... but what I can tell you is that we have a previous project that was able to connect to our system with the following nodejs code:
and this connection was able to validate people's passwords which is basically all I would need a REST interface to do.
var restify = require('restify');
var ActiveDirectory = require('activedirectory');
var config = {url: 'ldap://ourldapserver.net',
baseDN: 'DC=mcwcorp,DC=net',
username: 'xxxxxx',
password: 'xxxxxxx'
}
var ad = new ActiveDirectory(config);
var server = restify.createServer();


The Max7219.h library

Hello i was looking at the code and say there is a Max7219.h in the arduino ino. But in your files you do not have have the libray there. I don't know that library either. I know the Max7219 chip is a input/output driver for leds. But yet somehow the code compiles with no problem even if i don't have that library. Strage!!
I never saw a code  compile with no errors with a missing library. Why is this?
Joseph

Hi,
I don't see this in the .ino file?

I'm  sorry that was the sd2iec i was looking at my mistake.

No worries :-)

I just tried tapuino for the first time tonight and went great
I hand build my own becuase i cant afford to buy one. But it took me a while to figure out the wiring. Used a lot of jumper wires lol.


[Umbrella][Sort] Support Batch Processing based on Flink

Describe the proposal
Support Batch Processing based on Flink
Task list
Support Batch Processing based on Flink
InLong Component
Other for not specified component
Are you willing to submit PR?

[ ] Yes, I am willing to submit a PR!

Code of Conduct

[X] I agree to follow this project's Code of Conduct

Hi @dockerzhang.  I'm interested in this issue, can you assign it to me ?

Hi @dockerzhang, I'm following Flink batch processing recently. If nobody is working on this, I'd like to take it.

duplicated with https://github.com/apache/inlong/issues/9779, close it.


add JD Finance（京东金融） to featured list in showcase

See @hramos 's response on a similar PR here: https://github.com/facebook/react-native/pull/15869#issuecomment-328140929


Deploy to Vapor from Sail

Currently it's not possible to deploy from Sail to Vapor as it seems.
(Probably only if you add vapor-cli to your dependencies, but I think it should not end up in production?)
It would be great if vapor-cli could be part of the container.
Otherwise, you need everything installed on your host system that you also install in the container, or you get  error.
Just now I had to change my .env to not use redis anymore, just to make a deployment.

@madsem sail composer require --dev laravel/vapor-cli && sail php vendor/bin/vapor deploy your-environment - works without any problems 👍

I get this error,
sh: 1: docker: not found
How to fix it?

@madsem sail composer require --dev laravel/vapor-cli && sail php vendor/bin/vapor deploy your-environment - works without any problems +1

I get this error, sh: 1: docker: not found
How to fix it?

i have de same problem.

@madsem sail composer require --dev laravel/vapor-cli && sail php vendor/bin/vapor deploy your-environment - works without any problems 👍

I get this error, sh: 1: docker: not found
How to fix it?

You don't have to run vapor from the devcontainer. If you are on windows, you can run vapor from the wsl2 distro.

For docker based Vapor applications, you may modify the Dockerfile inside vendor/laravel/sail/runtimes/8.x and add one line there to install docker-cli inside the Sail's Ubuntu container.
RUN curl -fsSL https://get.docker.com | bash

@paulocastellano @PiaNoly

In my case, after the installation of Docker inside the image at build time, the ID used by group docker was 999, while on the host it was 1001. This lead to the /var/run/docker.sock file being owned by a group other than docker. RUN groupmod -g 1001 docker to fix.
Note: Setting user: 1000:1001 in docker-compose.yml, which I tried first, didn't help: it lead to all kinds of permissions issues on docker compose up or docker compose run.

In my case, after the installation of Docker inside the image at build time, the ID used by group docker was 999, while on the host it was 1001. This lead to the /var/run/docker.sock file being owned by a group other than docker. RUN groupmod -g 1001 docker to fix.
Note: Setting user: "1000:1001" in docker-compose.yml, which I tried first, didn't help: it lead to all kinds of permissions issues on docker compose up or docker compose run.

  ================
  ERROR: permission denied while trying to connect to the Docker daemon socket at unix:///var/run/docker.sock: Head "http://%2Fvar%2Frun%2Fdocker.sock/_ping": dial unix /var/run/docker.sock: connect: permission denied ```

I'm getting this error, any tips on how to get my host group id?


Karpenter provisions instance types that are not part of the requested instance-family

Version

Karpenter: v0.13.1

Kubernetes: v1.21
Expected Behavior

Karpenter should only provision requested instance types from instance-family in the provisioner spec.
Actual Behavior

We experimented with instance types last week where we just removed the instance type field from the provisioner, so it could use any of them. We got few issues there, so we fixed it back to specific family.
Since we fixed it back (25th July afternoon), it still provisions new nodes with instance types which are not part of the requirement set in the provisioner.
The spec request for the following instance family
  - key: node.kubernetes.io/instance-family
    operator: In
    values:
    - m5
    - m6i
    - m6a

And we can see nodes created from the t3 family
ip-10-146-47-176.us-west-2.compute.internal   Ready                      <none>   7h25m   v1.21.12-eks-5308cf7   default      us-west-2b   t3.2xlarge
ip-10-146-46-201.us-west-2.compute.internal   Ready                      <none>   3h12m   v1.21.12-eks-5308cf7   default      us-west-2b   t3.2xlarge
ip-10-146-42-49.us-west-2.compute.internal    Ready                      <none>   3h10m   v1.21.12-eks-5308cf7   default      us-west-2b   t3.2xlarge
ip-10-146-52-168.us-west-2.compute.internal   Ready                      <none>   3h      v1.21.12-eks-5308cf7   default      us-west-2c   t3.2xlarge

Steps to Reproduce the Problem

We haven't yet tried to reproduce it. But the I'd guess, the steps would be

Having a provisioner without the instance type field
Let it provision some nodes
Update that provisioner and specify similar spec as ours using instance family and excluding some instance sizes
Scale up some deployment, see the instance types used for the new nodes.

Resource Specs and Logs

Provisioner spec
spec:
  kubeletConfiguration: {}
  labels:
    containerd: enabled
    group: default
  limits: {}
  provider:
    amiFamily: AL2
    apiVersion: extensions.karpenter.sh/v1alpha1
    blockDeviceMappings:
    - deviceName: /dev/xvda
      ebs:
        deleteOnTermination: true
        encrypted: true
        kmsKeyID: ****removed****
        volumeSize: 100Gi
        volumeType: gp2
    instanceProfile: ****removed****
    kind: AWS
    securityGroupSelector:
      aws-ids: ****removed****
    subnetSelector:
      Name: ****removed****
  requirements:
  - key: karpenter.sh/capacity-type
    operator: In
    values:
    - spot
    - on-demand
  - key: node.kubernetes.io/instance-size
    operator: NotIn
    values:
    - 16xlarge
    - 24xlarge
    - 32xlarge
    - 48xlarge
    - metal
  - key: node.kubernetes.io/instance-family
    operator: In
    values:
    - m5
    - m6i
    - m6a
  - key: topology.kubernetes.io/zone
    operator: In
    values:
    - us-west-2a
    - us-west-2b
    - us-west-2c
  - key: kubernetes.io/arch
    operator: In
    values:
    - amd64
  ttlSecondsAfterEmpty: 30
  ttlSecondsUntilExpired: 86400

Getting nodes from this provisioner (26th July at 3:53pm EST)
kubectl get nodes   -L group -L topology.kubernetes.io/zone --sort-by=.metadata.creationTimestamp -L node.kubernetes.io/instance-type | grep default
ip-10-146-32-185.us-west-2.compute.internal   Ready,SchedulingDisabled   <none>   25h     v1.21.12-eks-5308cf7   default      us-west-2a   t3.2xlarge
ip-10-146-40-147.us-west-2.compute.internal   Ready                      <none>   23h     v1.21.12-eks-5308cf7   default      us-west-2b   r6a.4xlarge
ip-10-146-34-99.us-west-2.compute.internal    Ready                      <none>   23h     v1.21.12-eks-5308cf7   default      us-west-2a   c6i.4xlarge
ip-10-146-45-14.us-west-2.compute.internal    Ready                      <none>   22h     v1.21.12-eks-5308cf7   default      us-west-2b   t3.2xlarge
ip-10-146-43-247.us-west-2.compute.internal   Ready                      <none>   22h     v1.21.12-eks-5308cf7   default      us-west-2b   t3.2xlarge
ip-10-146-41-231.us-west-2.compute.internal   Ready                      <none>   22h     v1.21.12-eks-5308cf7   default      us-west-2b   t3.2xlarge
ip-10-146-39-223.us-west-2.compute.internal   Ready                      <none>   22h     v1.21.12-eks-5308cf7   default      us-west-2a   c6i.4xlarge
ip-10-146-45-45.us-west-2.compute.internal    Ready                      <none>   21h     v1.21.12-eks-5308cf7   default      us-west-2b   t3.2xlarge
ip-10-146-43-232.us-west-2.compute.internal   Ready                      <none>   21h     v1.21.12-eks-5308cf7   default      us-west-2b   r6a.4xlarge
ip-10-146-52-24.us-west-2.compute.internal    Ready                      <none>   19h     v1.21.12-eks-5308cf7   default      us-west-2c   t3.xlarge
ip-10-146-53-42.us-west-2.compute.internal    Ready                      <none>   19h     v1.21.12-eks-5308cf7   default      us-west-2c   t3.xlarge
ip-10-146-55-120.us-west-2.compute.internal   Ready                      <none>   19h     v1.21.12-eks-5308cf7   default      us-west-2c   t3.2xlarge
ip-10-146-34-170.us-west-2.compute.internal   Ready                      <none>   7h46m   v1.21.12-eks-5308cf7   default      us-west-2a   m4.xlarge
ip-10-146-47-176.us-west-2.compute.internal   Ready                      <none>   7h38m   v1.21.12-eks-5308cf7   default      us-west-2b   t3.2xlarge
ip-10-146-46-201.us-west-2.compute.internal   Ready                      <none>   3h25m   v1.21.12-eks-5308cf7   default      us-west-2b   t3.2xlarge
ip-10-146-42-49.us-west-2.compute.internal    Ready                      <none>   3h23m   v1.21.12-eks-5308cf7   default      us-west-2b   t3.2xlarge
ip-10-146-52-168.us-west-2.compute.internal   Ready                      <none>   3h13m   v1.21.12-eks-5308cf7   default      us-west-2c   t3.2xlarge
ip-10-146-37-117.us-west-2.compute.internal   Ready                      <none>   9m40s   v1.21.12-eks-5308cf7   default      us-west-2a   t3a.2xlarge
ip-10-146-49-11.us-west-2.compute.internal    Ready                      <none>   9m2s    v1.21.12-eks-5308cf7   default      us-west-2c   c6a.4xlarge
ip-10-146-52-46.us-west-2.compute.internal    Ready                      <none>   2m56s   v1.21.12-eks-5308cf7   default      us-west-2c   c6a.4xlarge

Extract of Karpenter logs, we can give more logs if needed.

Jul 26 08:16:28.005
ip-10-146-22-77.us-west-2.compute.internal
ip-10-146-22-77.us-west-2.compute.internal
karpenter
2022-07-26T12:16:27.326Z DEBUG controller.events Normal {"commit": "1f7a67b", "object": {"kind":"Pod","namespace":"istio-system","name":"istio-egressgateway-844694587-nkc2x","uid":"bf301110-f8b4-46f3-ad1d-b6d628acbb38","apiVersion":"v1","resourceVersion":"1091990907"}, "reason": "NominatePod", "message": "Pod should schedule on ip-10-146-47-176.us-west-2.compute.internal"}
Jul 26 08:15:49.006
ip-10-146-22-77.us-west-2.compute.internal
ip-10-146-22-77.us-west-2.compute.internal
karpenter
2022-07-26T12:15:48.946Z DEBUG controller.aws.launchtemplate Deleted launch template lt-05b83ab41019fddbd {"commit": "1f7a67b"}
Jul 26 08:15:23.005
ip-10-146-22-77.us-west-2.compute.internal
ip-10-146-22-77.us-west-2.compute.internal
karpenter
2022-07-26T12:15:22.362Z DEBUG controller.events Normal {"commit": "1f7a67b", "object": {"kind":"Pod","namespace":"istio-system","name":"istio-egressgateway-844694587-nkc2x","uid":"bf301110-f8b4-46f3-ad1d-b6d628acbb38","apiVersion":"v1","resourceVersion":"1091990907"}, "reason": "NominatePod", "message": "Pod should schedule on ip-10-146-47-176.us-west-2.compute.internal"}
Jul 26 08:14:48.007
ip-10-146-22-77.us-west-2.compute.internal
ip-10-146-22-77.us-west-2.compute.internal
karpenter
2022-07-26T12:14:47.945Z DEBUG controller.provisioning Discovered EC2 instance types zonal offerings {"commit": "1f7a67b"}
Jul 26 08:14:48.007
ip-10-146-22-77.us-west-2.compute.internal
ip-10-146-22-77.us-west-2.compute.internal
karpenter
2022-07-26T12:14:47.809Z DEBUG controller.provisioning Discovered 550 EC2 instance types {"commit": "1f7a67b"}
Jul 26 08:14:18.007
ip-10-146-22-77.us-west-2.compute.internal
ip-10-146-22-77.us-west-2.compute.internal
karpenter
2022-07-26T12:14:17.737Z DEBUG controller.events Normal {"commit": "1f7a67b", "object": {"kind":"Pod","namespace":"istio-system","name":"istio-egressgateway-844694587-nkc2x","uid":"bf301110-f8b4-46f3-ad1d-b6d628acbb38","apiVersion":"v1","resourceVersion":"1091989066"}, "reason": "NominatePod", "message": "Pod should schedule on ip-10-146-47-176.us-west-2.compute.internal"}
Jul 26 08:14:18.007
ip-10-146-22-77.us-west-2.compute.internal
ip-10-146-22-77.us-west-2.compute.internal
karpenter
2022-07-26T12:14:17.737Z INFO controller.provisioning Waiting for unschedulable pods {"commit": "1f7a67b"}
Jul 26 08:14:18.007
ip-10-146-22-77.us-west-2.compute.internal
ip-10-146-22-77.us-west-2.compute.internal
karpenter
2022-07-26T12:14:17.737Z INFO controller.provisioning Created node with 1 pods requesting {"cpu":"4260m","memory":"12430Mi","pods":"13"} from types t3a.2xlarge, c6a.2xlarge, c5a.2xlarge, t3.2xlarge, c5.2xlarge and 318 other(s) {"commit": "1f7a67b", "provisioner": "default"}
Jul 26 08:14:18.007
ip-10-146-22-77.us-west-2.compute.internal
ip-10-146-22-77.us-west-2.compute.internal
karpenter
2022-07-26T12:14:17.729Z INFO controller.provisioning.cloudprovider Launched instance: ****removed*****, hostname: ip-10-146-47-176.us-west-2.compute.internal, type: t3.2xlarge, zone: us-west-2b, capacityType: spot {"commit": "1f7a67b", "provisioner": "default"}
Jul 26 08:14:16.009
ip-10-146-22-77.us-west-2.compute.internal
ip-10-146-22-77.us-west-2.compute.internal
karpenter
2022-07-26T12:14:15.631Z DEBUG controller.provisioning.cloudprovider Discovered launch template Karpenter-eks-us-west-2-11598945489831860394 {"commit": "1f7a67b", "provisioner": "default"}

The labels are actually: karpenter.k8s.aws/instance-family not the node.kubernetes.io domain.  Check out the docs on those labels here: https://karpenter.sh/v0.13.2/tasks/scheduling/#supported-labels

Thanks for spotting this one out. We'll fix that asap on our end and will update you

🤔 We should be validating these labels, since kubernetes.io is a restricted prefix.

We'll prioritize this validation

Thanks, we applied the fix, we'll let it run for the night see if everything went as expected ;) Sorry about this one!

@suket22 reminds me that we can't validate this, because these are allowable kubelet labels:
	// LabelNamespaceSuffixKubelet is an allowed label namespace suffix kubelets can self-set ([*.]kubelet.kubernetes.io/*)
	LabelNamespaceSuffixKubelet = "kubelet.kubernetes.io"
	// LabelNamespaceSuffixNode is an allowed label namespace suffix kubelets can self-set ([*.]node.kubernetes.io/*)
	LabelNamespaceSuffixNode = "node.kubernetes.io"


Naming convention of the campaigns

Hi
We created campaigns [1] recently and passed the validation step successfully. But while the pilot there was a failure complaining about the naming conventions i.e. campaign names can not start with numeric as discussed in [2]. If there is no serious issue with the setup, we would like to remove this constraint on the naming convention of the campaigns.
Thanks!
Sunil (for pdmV), @bbilin @kskovpen
[1]
https://its.cern.ch/jira/browse/PRCAMPAIGNS-321
https://its.cern.ch/jira/browse/PRCAMPAIGNS-322
https://its.cern.ch/jira/browse/PRCAMPAIGNS-323
[2]
https://its.cern.ch/jira/browse/PRCAMPAIGNS-321

@sunilUIET Hi Sunil, thanks for creating this issue.
From one of the JIRA tickets, I see that Hasan managed to identify and explain what the problem is.
To add to that, a workflow campaign gets validated with this regular expression:
https://github.com/dmwm/WMCore/blob/master/src/python/WMCore/Lexicon.py#L308
unfortunately, we do not have the same validation for campaigns created in WMCore.
Given that a campaign is defined in Unified, and then propagated to WMCore, I think we will have to apply the same regex validation on the Unified side, such that these problems can be spotted right at the beginning (and we should also implement the same validation on the WMCore side).
Is there any strong reason blocking us from renaming that campaign 2022CommissionGS to CommissionGS2022? Or anything that would fulfill the regular expression?
We apologize for the extra work that this causes.

@haozturk Hi Hasan, is it something that you could easily implement on the unified side? While we work on unifying these campaign definitions among the systems.

@sunilUIET @haozturk do you know if this ticket is still relevant? Has Unified enforced any campaign name validation?

@amaltaro I think we can close this issue


Support Fast XML Parser v4.x

💁 These changes update the version of fast-xml-parser to 4.2.4 to mitigate the following vulnerabilities:

CWE-1321
CWE-1333

👋 @kamilkisiela: are you able to review these changes?

Thanks! Are you planning to release a new version with these changes?


Are the tags automatically recognized by dolphin and other programs that use xattr?

I want to add a list of tags to a file programmatically but I don't know how to do that using Dolphin. I was looking around and I've seen that this program uses the same way of keeping track of the tags, but I'm not sure how xattr works, so I don't know if I add tags with wutag to a file will I be able to search for those files using the tags in Dolphin or only with wutag?

Tags are currently stored in a way that makes them unique to wutag. They might get picked up by other programs, but they won't look the same. The reason why is that tags get serialized in cbor and prefixed with wutag. for easier future extraction as can be seen here: https://github.com/vv9k/wutag/blob/6d697957cc87ad75c380b6cd7f7ecaee2ef83182/wutag_core/tag.rs#L99-L102
It might be worth revisiting if there are usecases for the tags to be plaintext.

Could you give an example of how would I serialize the tags in cbor and prefix them with wutag. I think it would be something like:
import cbor2
USERSPACE = "user.wutag"
def import_to_wutag(path: str, tags: List[str]) -> None:
    serialized_tags = cbor2.dumps(tags)
    write_xattr(path, serialized_tags)
    xattr.setxattr(path, USERSPACE, serialized_tags)


Validation failed when connecting mysql hue database:ImportError: No module named useradmin.hue_password_policy

Unexpected error. Unable to verify database connection.
And when I tail the log of cloudera server:
An error occurred that :
    new_errors = check(app_configs=app_configs)
  File "/usr/lib/hue/build/env/lib/python2.7/site-packages/Django-1.11-py2.7.egg/django/core/checks/urls.py", line 16, in check_url_config
    return check_resolver(resolver)
  File "/usr/lib/hue/build/env/lib/python2.7/site-packages/Django-1.11-py2.7.egg/django/core/checks/urls.py", line 26, in check_resolver
    return check_method()
  File "/usr/lib/hue/build/env/lib/python2.7/site-packages/Django-1.11-py2.7.egg/django/urls/resolvers.py", line 254, in check
    for pattern in self.url_patterns:
  File "/usr/lib/hue/build/env/lib/python2.7/site-packages/Django-1.11-py2.7.egg/django/utils/functional.py", line 35, in __get__
    res = instance.__dict__[self.name] = self.func(instance)
  File "/usr/lib/hue/build/env/lib/python2.7/site-packages/Django-1.11-py2.7.egg/django/urls/resolvers.py", line 405, in url_patterns
    patterns = getattr(self.urlconf_module, "urlpatterns", self.urlconf_module)
  File "/usr/lib/hue/build/env/lib/python2.7/site-packages/Django-1.11-py2.7.egg/django/utils/functional.py", line 35, in __get__
    res = instance.__dict__[self.name] = self.func(instance)
  File "/usr/lib/hue/build/env/lib/python2.7/site-packages/Django-1.11-py2.7.egg/django/urls/resolvers.py", line 398, in urlconf_module
    return import_module(self.urlconf_name)
  File "/usr/lib64/python2.7/importlib/__init__.py", line 37, in import_module
    __import__(name)
  File "/usr/lib/hue/desktop/core/src/desktop/urls.py", line 41, in <module>
    from desktop.auth import views as desktop_auth_views
  File "/usr/lib/hue/desktop/core/src/desktop/auth/views.py", line 38, in <module>
    from desktop.auth import forms as auth_forms
  File "/usr/lib/hue/desktop/core/src/desktop/auth/forms.py", line 30, in <module>
    from useradmin.hue_password_policy import hue_get_password_validators
ImportError: No module named useradmin.hue_password_policy

2018-10-17 15:45:51,839 ERROR CommandPusher:com.cloudera.cmf.model.DbCommand: Command 1855(HueTestDatabaseConnection) has completed. finalstate:FINISHED, success:false, msg:Unexpected error. Unable to verify database connection.

It seems that missing module useradmin.hue_password_policy, so how can I fix this.

HUE-WebUI-doesn-t-launch
This is my solution


Create index_nl.js

I translated the web-app in Dutch (Nederlands)

Thanks for your pull request and your help ! 👍🏻
There are some more files that needs to be translated for now, especially about dashboard and workspace
For Blockly, maybe we can have a look on the already existing translations to speed up a little bit the process
I'll also figure out a way to enable this translation from the code, so the new files can be used when someone use the web application

I translate it later ok maybe today

2/3 done! panel_nl.js and index_nl.js done!

Nice, thanks !
We must also work on the code to enable those translations to be displayed when browsing the web application. Maybe you don't know the project or JS enough to do it, so I'll work on it when available. I don't have a lot of spare time, but I'll do my best 👍🏻


🚀 Feature Request: Can Workers generated by wrangler include tests again?

Describe the solution
Currently if you want a Worker with Vitest preconfigured, you have to run:
npx wrangler@2 init my-tested-worker -y

It would be cool if wrangler v3 could generate Workers with tests too.

#5189 closes this by adding @cloudflare/vitest-pool-workers to "Hello World" templates with an example test.


Separate saveCustomerAddress method on Cart.php

Hello,
I'm trying to write my own controller to change some behavior. One thing I noticed, currently it is impossible to make my checkout process address split into billing and shipping. That occurs because of the saveCustomerAddress which requires me to have the both billing and shipping process at the same time.
It is possible to change saveCustomerAddress or split it so I can save billing and shipping addresses in different times (such as two forms submit).

HI @xalexslx,
You can create a custom route and controller in your new theme to override the default behavior.

I am closing this, if you see something broken in existing themes then feel free to raise the issue.
Please use the forum for discussions, this channel is only for reporting bugs and enhancement,
https://forums.bagisto.com/


Add function to override default use-contractkit wallet config

Add function that dapps can use to override the default centralized wallet configurations.
This should enable wallets to specify which wallets to omit and what order to present wallet to their users.

Yes please! This is a must-have if we're really trying to build an open and inclusive ecosystem.

Duplicate


refactor(st_b_lcd40_dsi1_mb1166_a09): disable default STM32_LTDC_RGB8…

…88 configuration
I removed the configuration for STM32_LTDC_RGB888 in the stm32h747i_disco_stm32h747xx_m7.conf, as I believe this should not be set here. When enabling DMA2D (Chrom-ART) this line leads to significant issues (noise on display). Within this situation it needs to be set to STM32_LTDC_ARGB8888 instead. Within the context of Zephyr, LVGL and the STM32H747I-DISCO many people online mention to be running into problems when activating DMA2D. Deactivating this line solved it for me. Although I'm not an expert I think best practise should be to declare this within the project prj.conf.
Signed-off-by: Maarten Scherpenisse<EMAIL_ADDRESS>

@CharlesDias Can you have a look ?

Hi, @maarten1C96. Thanks for your contribution.
@maarten1C96 and @erwango, about using the STM32_LTDC_ARGB8888 instead of STM32_LTDC_RGB888 make sense because the current LVGL version supports the color depth ARGB8888, RGB565, RGB232, and monochrome. https://github.com/zephyrproject-rtos/zephyr/blob/de69ebd1f88854d14ca5b7c259870c35570ddfcb/modules/lvgl/Kconfig#L74
I believe that there are two approaches:

the simplest one is to comment on the STM32_LTDC_RGB888, as suggested, if it solves the problem. When you do this, the default STM32_LTDC_PIXEL_FORMAT is STM32_LTDC_RGB565. I suggest testing it with the LVGL Music Demo to be sure (I don't have a STM32H747I-DISCO to test it). https://github.com/zephyrproject-rtos/zephyr/blob/de69ebd1f88854d14ca5b7c259870c35570ddfcb/drivers/display/Kconfig.stm32_ltdc#L17
improved solution: considering that we are talking about a display shield, maybe it could be better to improve the configuration to fix the problem and also achieve a better benchmark, as I did for the STM32H7B3I DK board. I've had a flicking issue in the STM32H7B3I DK board when activating the DMA2D. This was fixed by the PR #68254.

@maarten1C96 and @erwango.
Strange fact. When I comment on the CONFIG_STM32_LTDC_RGB888, we have the compilation result CONFIG_STM32_LTDC_RGB565=y and CONFIG_LV_COLOR_DEPTH_32=y. Compiler command used:
west build -p -b stm32h747i_disco/stm32h747xx/m7 samples/modules/lvgl/demos/  -- -DCONFIG_LV_Z_DEMO_MUSIC=y -DSHIELD=st_b_lcd40_dsi1_mb1166

@CharlesDias @erwango
I happen to have an STM32H747I-DISCO over here and did some tests:
Within the context of the demos: all compiled and flashed without errors, but all did result in a black screen. With or without CONFIG_STM32_LTDC_RGB888=y. Also when replaced by CONFIG_STM32_LTDC_ARGB8888=y in this display shield config.
Within the context of my own app: CONFIG_STM32_LTDC_ARGB8888=y works both with and without DMA2D enabled. Only notable difference to CONFIG_STM32_LTDC_RGB888=y is the alteration of the colours. However, after having set the default colours to custom colours, it turns out that STM32_LTDC_RGB888 was actually producing incorrect colours from the start.
As @CharlesDias suggested, perhaps replacing CONFIG_STM32_LTDC_RGB888=y by CONFIG_STM32_LTDC_ARGB8888=y could be even better indeed? Although I slightly prefer to keep control within my own prj.conf (which doesn't seem able to override configurations in the shield configuration?), I can imagine other users would appreciate not having to set this themselves.

[...] prj.conf (which doesn't seem able to override configurations in the shield configuration?)

It should actually. If this is not the case, then it is a bug.

@maarten1C96 and @erwango.
Strange fact. When I comment on the CONFIG_STM32_LTDC_RGB888, we have the compilation result CONFIG_STM32_LTDC_RGB565=y and CONFIG_LV_COLOR_DEPTH_32=y.

(Same here, but I think this is related to the demo itself. In my own project, when I comment out everything related to defining color configurations, RGB565 is not enabled.)

It should actually. If this is not the case, then it is a bug.

(I struggled with this issue quite a bit past week, but when I tried to replicate the bug today, it magically disappeared...) ✨

(Closed this pull request myself by accident)

I've reopened it for you, but you should not merge main into your branch...

@pdgendt
Thank you for reopening this pull request, and I apologise for my foolish proceeding! Only commit d693b81053becdc24029500c583ee43d62a05901 is supposed to be mentioned in this pull request.

@pdgendt @erwango @CharlesDias @ajarmouni-st
Ok, important lessons learned. I think my first pull request now is cleaned up and ready.

@pdgendt @erwango @CharlesDias @ajarmouni-st
Ok, important lessons learned. I think my first pull request now is cleaned up and ready.

Dear @maarten1C96 and @erwango. I'm not allowed to approve.

What is the reason this pull request has not been merged yet? Any feedback would be appreciated!

@kartben @pdgendt @erwango @ajarmouni-st
What is the reason this pull request has not been merged yet? Any feedback would be appreciated!

What is the reason this pull request has not been merged yet? Any feedback would be appreciated!

It needs to be reviewed still, and a lot of people are out-of-office these days. Sorry for the delay


Let non-curators see (but not edit) the taxon names page

Currently, only curators, site admins, and staff can see the /taxa/[taxon number]/names page (eg https://www.inaturalist.org/taxa/12937/names). That means if someone is investigating a question they have about a name, they can't see which places the name is associated with, and where it "ranks" in priority for both global use and place name preferences.
We should make this page viewable by any user, but still only editable by curators, site admins and staff, so I suggest:

[ ] Making the "Manage Names" button viewable for non-curators, but it should read "Common Names Chart" or something that doesn't indicate the user can alter anything.
[ ] Non-curators should be able to see the list of names but not interact with them, so for those users we need to remove the "edit" links and make sure the names are not draggable.
[ ] Change the text at the top to:

Taxa can have many common names. We support one default common name globally, which curators can change here by dragging a name to the top of the list. Curators can also specify default names in different places by editing the name and adding a place, but please only do this when different places have conflicting names.

Hello @kueda , Please assign me this issue. Thanks.

We decided to handle this not by letting non-curators access the edit page, rather move the regional names to the names tab on the taxon page


Store statistics in array metadata

Under the key _ome2024_ngff_challenge_stats we now store the following statistics for each array conversion:

input: endpoint of the input location, "default", or "" if not s3
output: endpoint of the output location, "default", or "" if not s3
read: total bytes read
written: total bytes written
start: epoch at which the conversion started
stop: epoch at which the conversion stopped
elapsed: equals "stop - start"

For example:
  "attributes": {
    "_ome2024_ngff_challenge_stats": {
      "input": "https://uk1s3.embassy.ebi.ac.uk",
      "output": "",
      "start":<PHONE_NUMBER>.7066,
      "stop":<PHONE_NUMBER>.515819,
      "read": 2312282,
      "written": 1661288,
      "elapsed": 0.8092191219329834
    }

Thanks. Merging to get the metadata work discussed during this morning's challenge chat opened before the afternoon session.

@perlman suggestions something like --performance-notes with free-text notes but more specifics might include:

threads
cpus
memory
entire command-line
"run on the cloud"

Opened https://github.com/ome/ome2024-ngff-challenge/pull/35


Unhandled rejection TypeError: Cannor read property 'define' of undefined

Welcome to Ghost's GitHub repo! 👋🎉
Do you need help or have a question? Please come chat in Slack: https://ghost.org/slack 👫. Got an idea for a new feature? Please add it to our wishlist: http://ideas.ghost.org 🌟. Found a bug? Please fill out the sections below... thank you 👍
Issue Summary
For a few weeks now I have been getting an error with Ghost when starting it with an Express app.
I get an error on /ghost/core/server/index.js:100:28 where Node throws an unhandled rejection typeerror. I have added the stack trace at the bottom.
I haven't been able to diagnose the issue because Ghost starts up properly in my Windows dev environment.
I removed all node_modules and reinstalled everything as at<EMAIL_ADDRESS>but still got the same error after the fresh install.
Steps to Reproduce

Install ghost as Express.js middleware
Start Express.js server
Get error

Any other info e.g. Why do you consider this to be a bug? What did you expect to happen instead?
Below is a stack trace:
Unhandled rejection TypeError: Cannot read property 'define' of undefined
    at /home/ubuntu-user/var/expressapp/node_modules/ghost/core/server/index.js:100:28
    at tryCatcher (/home/ubuntu-user/var/expressapp/node_modules/ghost/node_modules/bluebird/js/main/util.js:26:23)
    at Promise._settlePromiseFromHandler (/home/ubuntu-user/var/expressapp/node_modules/ghost/node_modules/bluebird/js/main/promise.js:507:31)
    at Promise._settlePromiseAt (/home/ubuntu-user/var/expressapp/node_modules/ghost/node_modules/bluebird/js/main/promise.js:581:18)
    at Async._drainQueue (/home/ubuntu-user/var/expressapp/node_modules/ghost/node_modules/bluebird/js/main/async.js:128:12)
    at Async._drainQueues (/home/ubuntu-user/var/expressapp/node_modules/ghost/node_modules/bluebird/js/main/async.js:133:10)
    at Immediate.Async.drainQueues (/home/ubuntu-user/var/expressapp/node_modules/ghost/node_modules/bluebird/js/main/async.js:15:14)
    at processImmediate [as _immediateCallback] (timers.js:383:17)

Technical details:

Ghost Version: 0.7.6 - 0.7.8
Node Version: 4.3.1
Browser/OS: any/Ubuntu LTS 14.04
Database: sqlite

This doesn't sound like a Ghost bug, but rather a conflict between your top level express app and Ghost.
The line of code that is throwing error is:
express.static.mime.define({'application/font-woff': ['woff']});
This indicates that something about your top level express app is different to Ghost's as express.static.mime is undefined for your app. serve-static is a default dependency of express, and I'm not sure what you could do to remove it.
Do you have any dependency conflicts - e.g. dependencies which are the same as Ghost but your app defines a different version. The key one being express?

Hi @ErisDS, I'll check now. I presumed that since I'm still using NPM 2 I wouldn't have a conflict in modules.
Current serve-static is "serve-static": "^1.10.2".
Using it as app.use(require('serve-static')(config.root + '/public'));

Hi @nevi-me, this is almost certainly a conflict issue with your top level app & not a bug with Ghost.
Therefore, I'm going to close this issue, and recommend you use slack to get help debugging the issue as going back and forth debugging a config issue doesn't work on GitHub.
If the result is uncovering a bug, we can reopen.


New function of isLength0

Is your feature request related to a problem? Please describe.
check length is 0

:tada: This issue has been resolved in version 1.8.0-beta.1 :tada:
The release is available on:

npm package (@beta dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This issue has been resolved in version 1.8.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Cleanups for cmd_debug/repository and remove dead code from restic package

What does this PR change? What problem does it solve?
Cleanup some code, see commit messages for details.

Was the change previously discussed in an issue or on the forum?
No..

Checklist

[x] I have read the contribution guidelines.
[x] I have enabled maintainer edits.
[ ] I have added tests for all code changes.
[ ] I have added documentation for relevant changes (in the manual).
[ ] There's a new file in changelog/unreleased/ that describes the changes for our users (see template).
[x] I have run gofmt on the code in all commits.
[x] All commit messages are formatted in the same style as the other commits in the repo.
[x] I'm done! This pull request is ready for review.

LGTM.


ReadAt storage

Uses GetRange to create an io.ReaderAt to not have to read the full file into memory to process it.

Love it!


[wallet/desktop] task: unit tests added for components

Added tests for:

MaxFeeAndSubmit
MaxFeeSelector

Removed useless code from MaxFeeSelector

Nice job, looks good to me. @gimre-xymcity could you also possibly review it mate?

can you please rebase this and resolve conflict(s)?
can you make branch in this repository for this PR, which makes reviews a bit easier?

@Jaguar0625 Sure. I've rebased and reopened from internal branch: https://github.com/symbol/desktop-wallet/pull/1885


UCO semi-open vocabularies need to become enumerations of xsd:strings

Background
UCO gives sets of strings that suggest values to use for certain properties.  UCO has called this the "Semi-open vocabulary" design pattern: While certain strings should be used, strings not included in UCO's ontology files can still be used instead when the user knows the value they are using is not yet in UCO, and/or might never be in UCO for whatever reason (e.g., confidentiality of non-public vocabularies).
UCO uses a syntax for its semi-open vocabularies that uses what has appeared to date to be an OWL design pattern for defining a datatype as a set of typed string values.  However, it turns out the pattern used by UCO is invalid OWL syntax.  Issue 593 covers half of the issues raised by an externally-developed OWL syntax reviewing tool, ROBOT[^1].  Issue 593's correction has no known impact on user data.
The other half of the syntax correction takes this form, which unfortunately differs from UCO's user data guidance since UCO's earliest examples.  Given the known non-0 impact on user data, this is being treated as a non-fast-track proposal.
Here is (again, selected for its small size) the Bitness vocabulary, as implemented in UCO 1.3.0 and long before:
vocabulary:BitnessVocab
	a rdfs:Datatype ;
	rdfs:label "Bitness Vocabulary"@en-US ;
	rdfs:comment "Defines an open-vocabulary of word sizes that define classes of operating systems."@en ;
	owl:equivalentClass [
		a rdfs:Datatype ;
		owl:onDatatype xsd:string ;
		owl:oneOf (
			"32"^^vocabulary:BitnessVocab
			"64"^^vocabulary:BitnessVocab
		) ;
	] ;
	.

Issue 593 cut the triple [] owl:onDatatype xsd:string ..  This Issue finishes the OWL syntax correction by changing the members to values typed only as xsd:string (which is the OWL-wide (IIRC, RDF-wide) default when no other type is stated):
vocabulary:BitnessVocab
        a rdfs:Datatype ;
        rdfs:label "Bitness Vocabulary"@en-US ;
        rdfs:comment "Defines an open-vocabulary of word sizes that define classes of operating systems."@en ;
        owl:equivalentClass [
                a rdfs:Datatype ;
                owl:onDatatype xsd:string ;
                owl:oneOf (
                        "32"
                        "64"
                ) ;
        ] ;
        .

The syntax error this addresses is that the enumeration attempted to assign a datatype to the enumeration's member-literals; but, that datatype is not yet defined at the time the enumeration is being consumed by the parsing process, because they are inside the referenced datatype's definition.  ROBOT describes this as a cyclic reference in a definition, and calls it a syntax error.  The "Bug description" section below goes into the details describing why the cycle is also a symptom of another syntax error.
Requirements
Requirement 1
UCO vocabularies must adhere to OWL syntactic requirements for custom datatypes.
Requirement 2
Any UCO vocabulary X must not use itself as a datatype in its enumerated literals, due to OWL syntax requirements (cited in "Bug description" section).
Risk / Benefit analysis
Benefits

Presently, OWL tools using the OWL API library[^1] declare UCO as having syntax errors (one per vocabulary) using the cyclic-reference pattern.  (The error's call stack ends in this method.)  From (offline) testing the patch with ROBOT, this change proposal addresses that error type, removing a barrier to compatibility for other OWL-based ontologies that might adopt UCO.
Using plain xsd:string in vocabularies resolves a blocking design question on JSON-LD context dictionaries, on how to assign datatypes to semi-open vocabulary properties without inducing SHACL errors when a value outside the suggested set is used.
This reduces programming languages' complexities in assigning datatypes to certain properties only when certain values are used.  (This is a concern downstream from the UCO ontology, and applies to e.g. Python bindings.)

Risks

All CASE and UCO data using semi-open vocabularies would need to revert vocabulary assignments to simple strings.  This would be a backwards-incompatible change because 1.3.0-and-prior data would be flagged as erroneous, but this change can be implemented in stages with the warning pattern used for other proposals with pre-2.0.0 and post-2.0.0 effects.

Competencies demonstrated
Competency 1
A hash is being migrated from UCO 1.3.0 to UCO 1.4.0.  The form in UCO 1.3.0 is:
{
    "@context": {
        "kb": "http://example.org/kb/",
        "types": "https://ontology.unifiedcyberontology.org/uco/types/",
        "vocabulary": "https://ontology.unifiedcyberontology.org/uco/types/"
    },
    "@graph": {
        "@id": "kb:Hash-9ed55c42-3204-4e45-ace7-7ae6bd7d8f38",
        "@type": "types:Hash",
        "types:hashMethod": {
            "@type": "vocabulary:HashNameVocab",
            "@value": "SHA3-256"
        },
        "types:hashValue": {
            "@type": "xsd:hexBinary",
            "@value": "36f028580bb02cc8272a9a020f4200e346e276ae664e45ee80745574e2f5ab80"
        }
    }
}

Competency Question 1.1
How is the hash supposed to be spelled with this proposal?
Result 1.1
Note that two lines are dropped: The "vocabulary" prefix from the context dictionary will never be needed by users, and hashMethod no longer needs the typed-literal JSON object in its spelling.
{
    "@context": {
        "kb": "http://example.org/kb/",
        "types": "https://ontology.unifiedcyberontology.org/uco/types/"
    },
    "@graph": {
        "@id": "kb:Hash-9ed55c42-3204-4e45-ace7-7ae6bd7d8f38",
        "@type": "types:Hash",
        "types:hashMethod": "SHA3-256",
        "types:hashValue": {
            "@type": "xsd:hexBinary",
            "@value": "36f028580bb02cc8272a9a020f4200e346e276ae664e45ee80745574e2f5ab80"
        }
    }
}

Competency Question 1.2
How is a hash using an algorithm name not in UCO supposed to be spelled?
Result 1.2
# UCO 1.4.0 form
kb:Hash-9ed55c42-3204-4e45-ace7-7ae6bd7d8f38
	a types:Hash ;
	types:hashMethod "FooHash" ;
	types:hashValue "098f6bcd4621d373cade4e832627b4f6"^^xsd:hexBinary ;
	.

Competency Question 1.3
How should semi-open vocabulary properties' ranges be spelled?
Result 1.3
These properties' ranges should continue to be spelled as the union of xsd:string and the UCO Vocabulary IRI.  The OWL 2 Syntax document, Section 9.4 gives an example for a restricted string-property.  UCO's semi-open vocabulary still permits general xsd:string, so an OWL Union'd range should be used in owl:DatatypePropertys, and vocabulary membership should be reviewed with SHACL.
Solution suggestion
No changes are necessary to the owl:DatatypeProperty OWL definitions currently using the semi-open vocabulary pattern, taking for example types:hashMethod:
types:hashMethod
	a owl:DatatypeProperty ;
	rdfs:label "hashMethod"@en ;
	rdfs:comment "A particular cryptographic hashing method (e.g., MD5)."@en ;
	rdfs:range [
		a rdfs:Datatype ;
		owl:unionOf (
			vocabulary:HashNameVocab
			xsd:string
		) ;
	] ;
	.

The SHACL shapes for the semi-open vocabulary pattern have been coming as trios of property shapes.  They need to be adjusted as follows for the implementing next UCO SEMVER-minor release, so current data raises SHACL warnings instead of errors.  Note that the sh:Info-severity "gentle suggestion" shape is now the shape that bears the enumeration.
types:Hash
	sh:property
		[
			sh:datatype xsd:string ;
			sh:message "As of UCO 1.4.0, the datatype to use for types:hashMethod should be xsd:string.  Not using xsd:string will be an error in UCO 2.0.0." ;
			sh:path types:hashMethod ;
			sh:severity sh:Warning ;
		] ,
		[
			sh:maxCount "1"^^xsd:integer ;
			sh:minCount "1"^^xsd:integer ;
			sh:nodeKind sh:Literal ;
			sh:path types:hashMethod ;
		] ,
		[
			sh:message "Value is not member of the vocabulary HashNameVocab." ;
			sh:in (
				"MD5"
				"MD6"
				"SHA1"
				"SHA224"
				"SHA256"
				"SHA3-224"
				"SHA3-256"
				"SHA3-384"
				"SHA3-512"
				"SHA384"
				"SHA512"
				"SSDEEP"
			) ;
			sh:path types:hashMethod ;
			sh:severity sh:Info ;
		]
		;
	.

(An aside: the new sh:Warning shape makes some new cases that previously failed now pass as warnings, like using an integer for hashMethod's value.  Given the warnings, this feels like a low-risk relaxation.)
For UCO 2.0.0, the first two shapes would combine, leaving the implementation as follows.
types:Hash
	sh:property
		[
			sh:datatype xsd:string ;
			sh:maxCount "1"^^xsd:integer ;
			sh:minCount "1"^^xsd:integer ;
			sh:nodeKind sh:Literal ;
			sh:path types:hashMethod ;
		] ,
		[
			sh:message "Value is not member of the vocabulary HashNameVocab." ;
			sh:in (
				"MD5"
				"MD6"
				"SHA1"
				"SHA224"
				"SHA256"
				"SHA3-224"
				"SHA3-256"
				"SHA3-384"
				"SHA3-512"
				"SHA384"
				"SHA512"
				"SSDEEP"
			) ;
			sh:path types:hashMethod ;
			sh:severity sh:Info ;
		]
		;
	.

Due to a processing efficiency issue, one final modification from current practice is suggested: The "Gentle suggestion" property shape should change from an inlined, blank-node-identified sh:PropertyShape to a class-independent, IRI-identified sh:NodeShape that uses the targeting statement ... sh:targetObjectsOf types:hashMethod .  The reason for this is that certain SHACL reporting practices, like those used in UCO's unit testing, inline all blank node property shapes in the SHACL result-sets.  For some vocabularies, especially longer ones that suggest intensive extension (in particular, the 200+-member vocabulary:ObservableObjectRelationshipVocab), this could be hopelessly obscuring in the result sets whenever users engage in local vocabulary extension.
This pattern is suggested for the implementation instead, to offer users (1) a reference to an IRI they can look up on the documentation site instead of getting an inlined and long anonymous shape, and (2) the opportunity to opt out of any specific "Gentle suggestion" shapes by using sh:deactivate:
types:hashMethod-objects-in-shape
	a sh:NodeShape ;
	sh:in (
		"MD5"
		"MD6"
		"SHA1"
		"SHA224"
		"SHA256"
		"SHA3-224"
		"SHA3-256"
		"SHA3-384"
		"SHA3-512"
		"SHA384"
		"SHA512"
		"SSDEEP"
	) ;
	sh:message "Value is not member of the vocabulary HashNameVocab." ;
	sh:severity sh:Info ;
	sh:targetObjectsOf types:hashMethod ;
	.

The replacement for the class's sh:property links would be as follows, using an rdfs:seeAlso to preserve some reference on the documentation website without any other mechanical impact:
 types:Hash
+	rdfs:seeAlso types:hashMethod-objects-in-shape ;
 	sh:property
 		[
 			sh:datatype xsd:string ;
 			sh:maxCount "1"^^xsd:integer ;
 			sh:minCount "1"^^xsd:integer ;
 			sh:nodeKind sh:Literal ;
 			sh:path types:hashMethod ;
- 		] ,
- 		[
- 			sh:message "Value is not member of the vocabulary HashNameVocab." ;
- 			sh:in (
- 				"MD5"
- 				"MD6"
- 				"SHA1"
- 				"SHA224"
- 				"SHA256"
- 				"SHA3-224"
- 				"SHA3-256"
- 				"SHA3-384"
- 				"SHA3-512"
- 				"SHA384"
- 				"SHA512"
- 				"SSDEEP"
- 			) ;
- 			sh:path types:hashMethod ;
- 			sh:severity sh:Info ;
 		]
 		;
 	.

If a user wishes to opt out of the gentle suggestions, they can add this triple in their extension SHACL shapes:
types:hashMethod-objects-in-shape
	sh:deactivated true ;
	.

Bug description
While at least one tool reports that the current UCO vocabulary pattern is a cyclic definition error, the OWL syntax specification and RDF mapping documents together describe the problem as an inappropriate use of an OWL structure, DatatypeDefinition.
Looking through the OWL 2 Mapping to RDF document, Table 16 includes this mapping:
IF this pattern is in the RDF graph G:
*:x owl:equivalentClass y .
{ DR(*:x) ≠ ε amd DR(y) ≠ ε }

THEN the following axiom is added to the ontology OG:
DatatypeDefinition( DR(*:x) DR(y) )

For quick reference, the smbols above mean:

*:x is an IRI
y is either a blank node or an IRI
DR(z) is a function mapping a node z to a DataRange structre in the ontology OG

Nodes for DR can be IRIs or blank nodes

DR(z) ≠ ε states that DR(z) is defined (or equivalently, the function at the value z is not empty)

Taken together, owl:equivalentClass as a predicate between two certain nodes pertaining to DataRanges imply a DatatypeDefinition.
*:x being in a DatatypeDefinition imposes a certain constraint on *:x, with which UCO has been incongruous to date.  Section 9.4 of the OWL 2 Syntax document defines that in the structure DatatypeDefinition ( DT DR ), the Datatype that is the first parameter (DT, or *:x, or uco-vocabulary:BitnessVocab) is a "synonym for DR..."  And: "The datatypes defined by datatype definition axioms ... have empty lexical spaces and therefore they must not occur in literals."
The example in the OWL 2 syntax document that immediately follows that quote illustrates a datatype a:SSN, which is part of a datatype definition that would be spelled like this in Turtle:
# First axiom: "Declaration( Datatype( a:SSN ) )"
a:SSN
	a rdfs:Datatype ;
	.

# Second axiom: "DatatypeDefinition( ..."
a:SSN
	owl:equivalentClass [
		a rdfs:Datatype ;
		owl:onDatatype xsd:string ;
		owl:withRestrictions (
			[
				xsd:pattern "[0-9]{3}-[0-9]{2}-[0-9]{4}" ;
			]
		) ;
	] ;
	.

# Third axiom: "DataPropertyRange( a:hasSSN a:SSN )"
a:hasSSN
	rdfs:range a:SSN ;
	.

Note the end of the example block states "there can be no literals of datatype a:SSN".
In UCO's case, there can be no literals of datatype vocabulary:BitnessVocab, vocabulary:HashNameVocab, etc.
Coordination

Tracking in Jira ticket OCUCO-323
[ ] Administrative review completed, proposal announced to Ontology Committees (OCs) on 2024-08-12
[ ] Requirements to be discussed in OC meeting, 2024-08-20

[ ] Requirements Review vote has not occurred

[ ] Requirements development phase completed.
[ ] Solution announced to OCs on TODO-date
[ ] Solutions Approval to be discussed in OC meeting, date TBD
[ ] Solutions Approval vote has not occurred

[ ] Solutions development phase completed.
[ ] Backwards-compatible implementation merged into develop for the next release
[ ] develop state with backwards-compatible implementation merged into develop-2.0.0
[ ] Backwards-incompatible implementation merged into develop-2.0.0 (or N/A)
[x] Milestone linked
[ ] Documentation logged in pending release page
[ ] Prerelease publication: CASE develop branch updated to track UCO's updated develop branch
[ ] Prerelease publication: CASE develop-2.0.0 branch updated to track UCO's updated develop-2.0.0 branch

[^1]: Disclaimer: Participation by NIST in the creation of the documentation of mentioned software is not intended to imply a recommendation or endorsement by the National Institute of Standards and Technology, nor is it intended to imply that any specific software is necessarily the best available for the purpose.

This proposal also has an impact on the implementation of Issue 549, as that issue adds a new vocabulary.


Unclear if "click" waits for element to be visible

Does click wait for an element to be visible before clicking it or does it depend on certain factors or Capybara settings? If so, which ones?
I have a flaky test where clicking a link sometimes brings us to the linked page and sometimes does not and no request for that page is sent to the server. I'm wondering if it's because the link is not yet visible.

It follows the standard webdriver spec. If you have implicit waits configured then they will be observed. Alternatively use a waiter.
The README has a whole bunch of info on waiting. If you feel as though the info isn't there, feel free to submit a PR to alter the README.


No mention about the license for this repository

Hi,
I want to use this as a starter for a project. There is no license associated with this repository. Is it safe to assume to be MIT?
thanks

Hi @prabak , I've added a license. Thanks :-)


Make delimiters symmetric for \left and \right.  #1084

Mark delimters are symmetric when used with \left and \right.  In particular, this makes the arrow delimiters be symmetric.  Resolves issue #1084.

lgtm.


[WFCORE-5412] Upgrade WildFly OpenSSL to 2.1.4.Final

https://issues.redhat.com/browse/WFCORE-5412
https://github.com/wildfly-security/wildfly-openssl/compare/2.1.3.Final...2.1.4.Final
    Release Notes - WildFly OpenSSL - Version 2.1.4.Final

        Improvement

[WFSSL-70] -         update license name to match SPDX license list and also Wildfly

        Bug

[WFSSL-71] -         OpenSSlSession.initPeerChain() fails on JDK 15+

[WFSSL-73] -         OpenSSLEngine shuts down too early

        Task

[WFSSL-72] -         Investigate failures in BasicOpenSSLEngineLegacyProtocolsTest

[WFSSL-74] -         Update the error message that occurs when OpenSSLEngine#closeInbound is called before receiving a close_notify message from the peer

[WFSSL-75] -         Release WildFly OpenSSL 2.1.4.Final

Core - Full Integration Build 10558 outcome was FAILURE using a merge of d2518dc7bf86aa039b12ff0b3bd7f3c22cb49ff8
Summary: Exit code 1 (Step: Build & test core (Maven)) (new) Build time: 00:00:51

Core - Full Integration Build 10633 outcome was FAILURE using a merge of d2518dc7bf86aa039b12ff0b3bd7f3c22cb49ff8
Summary: Exit code 1 (Step: Build & test core (Maven)) (new) Build time: 00:01:47

Core - Full Integration Build 10559 outcome was FAILURE using a merge of d2518dc7bf86aa039b12ff0b3bd7f3c22cb49ff8
Summary: Exit code 1 (Step: Build & test core (Maven)) Build time: 00:00:41

Core - Full Integration Build 10634 outcome was FAILURE using a merge of d2518dc7bf86aa039b12ff0b3bd7f3c22cb49ff8
Summary: Exit code 1 (Step: Build & test core (Maven)) Build time: 00:01:05