Write Ahead Log

The basic hooks into the rest of the storage engine is done. Serialization format will definitely need to change, as we add in varlen fields. (Because we will probably rewrite that, I am not adding checksums) A bunch of other code needs to be written for handling errors on reading records back in.
Tests will be added soon. fix #111

Coverage increased (+17.5%) to 96.208% when pulling 36fd1f6107eadd09434f8e360394b72fa818b82a on tli2:tianyu-wal into 45115ada20e2e9618bb60aef09aeaff4efb23166 on cmu-db:master.

Any guess why this isn't running Jenkins?

The configuration option to periodically scan the repository got destroyed after a recent security update for a plug-in.
I’ve restored it now and Jenkins  appears to building the commit.
On a related note, I did discover the mechanism do the webhook trigger from Travis but I still have to work out the details.

Thanks for looking into it @crd477!

Is this the first commit to get rejected because of the benchmark step?

I believe so, yes. We'll have to investigate if that's a real failure, but I believe that it is.

The benchmark result is real, but not a regression. I have a PR to submit, that controls how the benchmark is run. With that change, I expect the performance to come in line with historical average.
Will submit shortly, if possible.


pygit2: support 1.14 credentials

Fixes #311

Codecov Report
Attention: 3 lines in your changes are missing coverage. Please review.

Comparison is base (0d23565) 78.35% compared to head (af6500e) 76.47%.

Files
Patch %
Lines

src/scmrepo/git/backend/pygit2/callbacks.py
0.00%
3 Missing :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #314      +/-   ##
==========================================
- Coverage   78.35%   76.47%   -1.88%
==========================================
  Files          39       39
  Lines        4980     4982       +2
  Branches      897      606     -291
==========================================
- Hits         3902     3810      -92
- Misses        924     1005      +81
- Partials      154      167      +13

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


x/pkgsite: package removal request for go.mongodb.org/mongo-driver/mongo @ 1.6.0, 1.6.1, 1.7.0 and 1.7.1

What is the path of the package that you would like to have removed?
We would like to remove<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>and<EMAIL_ADDRESS>These are four versions of the MongoDB Go driver that are affected by a security bug.
Are you the owner of this package?
Yes, one of the couple co-owners.
What is the reason that you could not retract this package instead?
We would use a retract directive, but the MongoDB Go driver has to build on Golang version 1.10, which is lower than Golang 1.16. retract directives can only be used in the main module without error on Golang 1.16+, so our only option is to remove the affected versions manually.

We only support removing all versions of a package or module by path. If we manually removed these versions from pkg.go.dev a user can still download them via go get and re-add them pkg.go.dev by looking them up on the site.

Got it; thank you for the update @jamalc.


No appointment created!

when I ask an agent.
end result, always showing this message only.
I'm sorry, there are no slots available for Invalid Date, would you like to check another day?
No appointment created. :(
pls, help me.

Can you post your code?

@sarahdwyer
PFA.
index.js
/**

Copyright 2017 Google Inc. All Rights Reserved.

Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at

 http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
*/

'use strict';
const functions = require('firebase-functions');
const {google} = require('googleapis');
const {WebhookClient} = require('dialogflow-fulfillment');
// Enter your calendar ID below and service account JSON below, see https://github.com/dialogflow/bike-shop/blob/master/README.md#calendar-setup
const calendarId = ' /deleted my self/'; // looks like<EMAIL_ADDRESS>const serviceAccount = { /deleted my self/ };
// Starts with {"type": "service_account",...
// Set up Google Calendar Service account credentials
const serviceAccountAuth = new google.auth.JWT({
email: serviceAccount.client_email,
key: serviceAccount.private_key,
scopes: 'https://www.googleapis.com/auth/calendar'
});
const calendar = google.calendar('v3');
process.env.DEBUG = 'dialogflow:*'; // enables lib debugging statements
const timeZone = 'Asia/Colombo';
const timeZoneOffset = '-05:30';
exports.dialogflowFirebaseFulfillment = functions.https.onRequest((request, response) => {
const agent = new WebhookClient({ request, response });
function hours (agent) {
if (currentlyOpen()) {
agent.add(We're open now! We close at 5:30pm today.);
} else {
agent.add(We're currently closed, but we open every weekday at 9am!);
}
}
function makeAppointment (agent) {
// Calculate appointment start and end datetimes (end = +1hr from start)
const dateTimeStart = new Date(Date.parse(agent.parameters.date + 'T' + agent.parameters.time + timeZoneOffset));
const dateTimeEnd = new Date(new Date(dateTimeStart).setHours(dateTimeStart.getHours() + 1));
const appointmentTimeString = dateTimeStart.toLocaleString(
'en-US',
{ month: 'long', day: 'numeric', hour: 'numeric', timeZone: timeZone }
);
// Check the availibility of the time, and make an appointment if there is time on the calendar
return createCalendarEvent(dateTimeStart, dateTimeEnd).then(() => {
  agent.add(`Ok, let me see if we can fit you in.  ${appointmentTimeString} is fine!.  Do you need a repair or just a tune-up?`);
}).catch(() => {
  agent.add(`I'm sorry, there are no slots available for ${appointmentTimeString}, would you like to check another day?`);
});

}
let intentMap = new Map();
intentMap.set('Hours', hours);
intentMap.set('Make Appointment', makeAppointment);
agent.handleRequest(intentMap);
});
function currentlyOpen () {
var currentDateTime = new Date(); // current time
var hours = currentDateTime.getHours();
var mins = currentDateTime.getMinutes();
var day = currentDateTime.getDay();
return day >= 1 &&
day <= 5 &&
hours >= 9 &&
(hours < 17 || hours === 17 && mins <= 30);
}
function createCalendarEvent (dateTimeStart, dateTimeEnd) {
return new Promise((resolve, reject) => {
calendar.events.list({
auth: serviceAccountAuth, // List events for time period
calendarId: calendarId,
timeMin: dateTimeStart.toISOString(),
timeMax: dateTimeEnd.toISOString()
}, (err, calendarResponse) => {
// Check if there is a event already on the Bike Shop Calendar
if (err || calendarResponse.data.items.length > 0) {
reject(err || new Error('Requested time conflicts with another appointment'));
}
// Create event for the requested time period
calendar.events.insert({ auth: serviceAccountAuth,
calendarId: calendarId,
resource: {summary: 'Bike Appointment',
start: {dateTime: dateTimeStart},
end: {dateTime: dateTimeEnd}}
}, (err, event) => {
err ? reject(err) : resolve(event);
}
);
});
});
}
package.json
{
"name": "dialogflowFirebaseFulfillment",
"description": "Dialogflow fulfillment for the bike shop sample",
"version": "0.0.1",
"private": true,
"license": "Apache Version 2.0",
"author": "Google Inc.",
"engines": {
"node": "~4.2"
},
"scripts": {
"lint": "semistandard --fix "**/*.js"",
"start": "firebase deploy --only functions",
"deploy": "firebase deploy --only functions"
},
"dependencies": {
"actions-on-google":"^2.2.0",
"firebase-functions": "^0.6.2",
"firebase-admin": "^5.2.1",
"googleapis": "27.0.0",
"dialogflow-fulfillment": "0.3.0-beta.1"
}
}

Aways showing this result..
I'm sorry, there are no slots available for Invalid Date, would you like to check another day?
Pls, anyone Help me.

First try updating your dependencies:
"node": "6.0"
"dependencies": {
"actions-on-google": "^2.2.0",
"firebase-admin": "^5.13.1",
"firebase-functions": "^2.0.2",
"dialogflow": "^0.6.0",
"dialogflow-fulfillment": "0.5.0"
}

Hi sarah,
I am also getting same error, there are no slots available for Invalid Date, would you like to check another day?
My code package.json
{
"name": "DialogflowFirebaseWebhook",
"description": "Firebase Webhook dependencies for a Dialogflow agent.",
"version": "0.0.1",
"private": true,
"license": "Apache Version 2.0",
"author": "Google Inc.",
"engines": {
"node": "6"
},
"scripts": {
"lint": "semistandard --fix "**/*.js"",
"start": "firebase deploy --only functions",
"deploy": "firebase deploy --only functions"
},
"dependencies": {
"actions-on-google": "^2.2.0",
"firebase-admin": "^5.13.1",
"firebase-functions": "^2.0.2",
"dialogflow": "^0.6.0",
"googleapis": "^27.0.0",
"dialogflow-fulfillment": "0.5.0"
}
}
index.js
/**

Copyright 2017 Google Inc. All Rights Reserved.

Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at

 http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
*/

'use strict';
const functions = require('firebase-functions');
const {google} = require('googleapis');
const {WebhookClient} = require('dialogflow-fulfillment');
// Enter your calendar ID and service account JSON below.
const calendarId =<EMAIL_ADDRESS>// Example<EMAIL_ADDRESS>const serviceAccount = {}; // The JSON object looks like: { "type": "service_account", ... }
// Set up Google Calendar service account credentials
const serviceAccountAuth = new google.auth.JWT({
email: serviceAccount.client_email,
key: serviceAccount.private_key,
scopes: 'https://www.googleapis.com/auth/calendar'
});
const calendar = google.calendar('v3');
process.env.DEBUG = 'dialogflow:*'; // It enables lib debugging statements
const timeZone = 'America/Los_Angeles';  // Change it to your time zone
const timeZoneOffset = '-07:00';         // Change it to your time zone offset
exports.dialogflowFirebaseFulfillment = functions.https.onRequest((request, response) => {
const agent = new WebhookClient({ request, response });
function makeAppointment (agent) {
// Use the Dialogflow's date and time parameters to create Javascript Date instances, 'dateTimeStart' and 'dateTimeEnd',
// which are used to specify the appointment's time.
const appointmentDuration = 1;// Define the length of the appointment to be one hour.
const dateTimeStart = convertParametersDate(agent.parameters.date, agent.parameters.time);
const dateTimeEnd = addHours(dateTimeStart, appointmentDuration);
const appointmentTimeString = getLocaleTimeString(dateTimeStart);
const appointmentDateString = getLocaleDateString(dateTimeStart);
// Check the availability of the time slot and set up an appointment if the time slot is available on the calendar
return createCalendarEvent(dateTimeStart, dateTimeEnd).then(() => {
agent.add(Got it. I have your appointment scheduled on ${appointmentDateString} at ${appointmentTimeString}. See you soon. Good-bye.);
}).catch(() => {
agent.add(Sorry, we're booked on ${appointmentDateString} at ${appointmentTimeString}. Is there anything else I can do for you?);
});
}
let intentMap = new Map();
intentMap.set('Make Appointment', makeAppointment);  // It maps the intent 'Make Appointment' to the function 'makeAppointment()'
agent.handleRequest(intentMap);
});
function createCalendarEvent (dateTimeStart, dateTimeEnd) {
return new Promise((resolve, reject) => {
calendar.events.list({  // List all events in the specified time period
auth: serviceAccountAuth,
calendarId: calendarId,
timeMin: dateTimeStart.toISOString(),
timeMax: dateTimeEnd.toISOString()
}, (err, calendarResponse) => {
// Check if there exists any event on the calendar given the specified the time period
if (err || calendarResponse.data.items.length > 0) {
reject(err || new Error('Requested time conflicts with another appointment'));
} else {
// Create an event for the requested time period
calendar.events.insert({ auth: serviceAccountAuth,
calendarId: calendarId,
resource: {summary: 'Bike Appointment',
start: {dateTime: dateTimeStart},
end: {dateTime: dateTimeEnd}}
}, (err, event) => {
err ? reject(err) : resolve(event);
}
);
}
});
});
}
// A helper function that receives Dialogflow's 'date' and 'time' parameters and creates a Date instance.
function convertParametersDate(date, time){
return new Date(Date.parse(date.split('T')[0] + 'T' + time.split('T')[1].split('-')[0] + timeZoneOffset));
}
// A helper function that adds the integer value of 'hoursToAdd' to the Date instance 'dateObj' and returns a new Data instance.
function addHours(dateObj, hoursToAdd){
return new Date(new Date(dateObj).setHours(dateObj.getHours() + hoursToAdd));
}
// A helper function that converts the Date instance 'dateObj' into a string that represents this time in English.
function getLocaleTimeString(dateObj){
return dateObj.toLocaleTimeString('en-US', { hour: 'numeric', hour12: true, timeZone: timeZone });
}
// A helper function that converts the Date instance 'dateObj' into a string that represents this date in English.
function getLocaleDateString(dateObj){
return dateObj.toLocaleDateString('en-US', { weekday: 'long', month: 'long', day: 'numeric', timeZone: timeZone });
}
Kindly help me to solve this issue.

Hi,
I do have the same problem.  Please help us find a solution.

Invalid Date
{
"name": "dialogflowFirebaseFulfillment",
"description": "Dialogflow fulfillment for the bike shop sample",
"version": "0.0.1",
"private": true,
"license": "Apache Version 2.0",
"author": "Google Inc.",
"engines": {
"node": "6"
},
"scripts": {
"lint": "semistandard --fix "**/*.js"",
"start": "firebase deploy --only functions",
"deploy": "firebase deploy --only functions"
},
"dependencies": {
"firebase-functions": "2.0.2",
"firebase-admin": "^5.13.1",
"actions-on-google": "2.2.0",
"googleapis": "^27.0.0",
"dialogflow-fulfillment": "0.5.0"
}
}
/**

Copyright 2017 Google Inc. All Rights Reserved.

Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at

 http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
*/

'use strict';
const functions = require('firebase-functions');
const {google} = require('googleapis');
const {WebhookClient} = require('dialogflow-fulfillment');
// Enter your calendar ID below and service account JSON below, see https://github.com/dialogflow/bike-shop/blob/master/README.md#calendar-setup
const calendarId =<EMAIL_ADDRESS>// looks like<EMAIL_ADDRESS>const serviceAccount = {
"type": "service_account",
"project_id": "bikeshopsample-d7b5b",
"private_key_id": "e8c94e4776bebb61f6505642936b80bcfdb8fd25",
"private_key": "e8c94e4776bebb61f6505642936b80bcfdb8fd25\nMIIEvgIBADANBgkqhkiG9w0BAQEFAASCBKgwggSkAgEAAoIBAQDaiEFtVJ8DgYZJ\neiWY33I0c9dsCf1QxefySd5ACepBIT3+GxixbooXLCndojiGPot6qLhnL+hM0sTf\nNl1p3SizTQHOGkiHWvVlyMtSPYUw4dz2PZfufm4sjcZbmC+0EeWE3S4V8ul2kHmv\n5OcAnaZehFjSG/3NhEqKW1+BwvRGeUbZY0ZbGnaSIGT0hss29//oiK+pnkB2egUn\niom1XGpLbxr5anbutVyJaWZ+x3TojMcFpC+78TToiOSdt2GrDXEoP8SN/zbfs6+b\nsQhMXTahYG5YGGBRv3dXaiBCyGrGaOuFjVCVDAy3rEIKVrAYR4IeIR1EZkAJkTrN\nJDSnrM+DAgMBAAECggEACoYNQIqWrcCLCvbK4LXB9iyt7xH8FOuy48QS49qWYVSM\ne7QqWEEOfVcvHPE276ALb3i4iJ+R/EEaIfWoQfTYhOnscFRrsbj7oE8vG2LDCzuV\nPHZy3pVQEO0y5C5L/cvu1ZshIQV1oLQMaCAJz8nHvT16WYPnkQIR5N/JlaIhyVLu\n8i8+B7JVxZ/A1tWlNePeQxHcxlSscGSb1//KWdQob/3pFku7dD3/PZshnTn+VzZR\ncQ5FS1qArff/TD+mHwmKXdm7pU3ZZErQCdb/D+RQmBKs9qVZEVERBlxf29D1AE08\nW7AvCQUzSanj9hED8l9uzN9PtEJD17ppWv55UMGlgQKBgQD+/neoOEXfzedhpl0d\nvMl3Txk3tErKd8m5PVd7vYz3DnFAbazJmMd7/s5ljs6n2dZ1atGv0JYpf233IKA7\nLgvC5I7i0J/A09n/sZMucl4Olfydfapj8Tly8NHilQqGSc9xUssMk1gv6D80Nw5r\neJHnad8lWMJbiPUGpDte+AobcQKBgQDbZPahyowda9hytcn1OI2Woyi/pgo7gVyQ\n+c2hyoG4Vhvw6r3cD2dEgfoiU/ATXibalAgrbXsp3yd6m//r3gxGKWbIgoYthIiL\nhZykZ9Y8ITAkdQKcxO7z5lGnHPdBgUj1GBvrp87EkVu5yxdvgJyGkBI50iwoekM2\npDf6aaLYMwKBgQCfyABernRKWxGDxOVQPv3W/v+EQjsjR5BlvKRW612raadZgd/l\nqxBFCFN4m9Wuo/eYN8kQ7BlMA4d6dT0yGBZSlzlZsvSHtbhCWpkpX4zEgwN6BEaC\nvaML/Q7ndhDUOOf90K1fQezeiB8iruUgPrreUR78nfObu+Qdt0dkqPRcYQKBgQDU\nRGsbPo0yKhXRZnFwALd893+FbXCZAiA9ZHPABd5cK3P9NCFduMmBTwBkFjJBiuas\ntGzzF4oCiRX5WtXRr5TQjV4UwbRwdbpmw2864fw1USbzHwLYCvHmqQB3X18a0at0\n906MQl+bb8f/iq+yAg1vZBU+PErdHu3JADno3ivgYQKBgFB+bXO4gR+qNjowpch2\n8DyMqDgmfEjQK57MoApG29KOENWLK5CXMAT6JK4uQwJPQJZYMsqxUnzGqJpIihsF\nBwKe/sJPgXAm5AgoDKnZzcEnruW7uG0Qheh1YqmEJwKuUsQmk1NmKRWFxMn5QMyz\nZEJ0D83A5kxPL5LSuozASq3h\n-----END PRIVATE KEY-----\n",
"client_email"<EMAIL_ADDRESS>"client_id": "103027792139444114351",
"auth_uri": "https://accounts.google.com/o/oauth2/auth",
"token_uri": "https://oauth2.googleapis.com/token",
"auth_provider_x509_cert_url": "https://www.googleapis.com/oauth2/v1/certs",
"client_x509_cert_url": "https://www.googleapis.com/robot/v1/metadata/x509/bike-shop-calender%40bikeshopsample-d7b5b.iam.gserviceaccount.com"
} ; // Starts with {"type": "service_account",...
// Set up Google Calendar Service account credentials
const serviceAccountAuth = new google.auth.JWT({
email: serviceAccount.client_email,
key: serviceAccount.private_key,
scopes: 'https://www.googleapis.com/auth/calendar'
});
const calendar = google.calendar('v3');
process.env.DEBUG = 'dialogflow:*'; // enables lib debugging statements
const timeZone = 'Europe/Berlin';
const timeZoneOffset = '+02:00';
exports.dialogflowFirebaseFulfillment = functions.https.onRequest((request, response) => {
const agent = new WebhookClient({ request, response });
function hours (agent) {
if (currentlyOpen()) {
agent.add(We're open now! We close at 5pm today.);
} else {
agent.add(We're currently closed, but we open every weekday at 9am!);
}
}
function makeAppointment (agent) {
// Calculate appointment start and end datetimes (end = +1hr from start)
const dateTimeStart = new Date(Date.parse(agent.parameters.date.split('T')[0] + 'T' + agent.parameters.time.split('T')[1].split('-')[0] + timeZoneOffset));
const dateTimeEnd = new Date(new Date(dateTimeStart).setHours(dateTimeStart.getHours() + 1));
const appointmentTimeString = dateTimeStart.toLocaleString(
'en-US',
{ month: 'long', day: 'numeric', hour: 'numeric', timeZone: timeZone }
);
// Check the availibility of the time, and make an appointment if there is time on the calendar
return createCalendarEvent(dateTimeStart, dateTimeEnd).then(() => {
  agent.add(`Ok, let me see if we can fit you in. ${appointmentTimeString} is fine!. Do you need a repair or just a tune-up?`);
}).catch(() => {
  agent.add(`I'm sorry, there are no slots available for ${appointmentTimeString}.`);
});

}
let intentMap = new Map();
intentMap.set('Hours', hours);
intentMap.set('Make Appointment', makeAppointment);
agent.handleRequest(intentMap);
});
function currentlyOpen () {
// Get current datetime with proper timezone
let date = new Date();
date.setHours(date.getHours() + parseInt(timeZoneOffset.split(':')[0]));
date.setMinutes(date.getMinutes() + parseInt(timeZoneOffset.split(':')[0][0] + timeZoneOffset.split(':')[1]));
return date.getDay() >= 1 &&
date.getDay() <= 5 &&
date.getHours() >= 9 &&
date.getHours() <= 17;
}
function createCalendarEvent (dateTimeStart, dateTimeEnd) {
return new Promise((resolve, reject) => {
calendar.events.list({
auth: serviceAccountAuth, // List events for time period
calendarId: calendarId,
timeMin: dateTimeStart.toISOString(),
timeMax: dateTimeEnd.toISOString()
}, (err, calendarResponse) => {
// Check if there is a event already on the Bike Shop Calendar
if (err || calendarResponse.data.items.length > 0) {
reject(err || new Error('Requested time conflicts with another appointment'));
} else {
// Create event for the requested time period
calendar.events.insert({ auth: serviceAccountAuth,
calendarId: calendarId,
resource: {summary: 'Bike Appointment',
start: {dateTime: dateTimeStart},
end: {dateTime: dateTimeEnd}}
}, (err, event) => {
err ? reject(err) : resolve(event);
}
);
}
});
});
}

Hi guys, I don't know if this is still going to help anyone. Battled with the same issue for 2 days and it finally worked today. So in stripping the dates, I had to strip a + instead of a - since my time formats have a + since I'm in South Africa. This solved the 'invalid date' part but it still didn't insert in the calendar. Then I realised that in calendar permissions I had to change the permissions for the email that we get from the json file to "make changes to events". Then it worked.

Someone has discussed this issue here


mwaa-local-env build-image fails

Hi!
I've done a fresh clone the repo and tried building the image
git clone --branch v2.2.2 https://github.com/aws/aws-mwaa-local-runner.git
cd aws-mwaa-local-runner
./mwaa-local-env build-image

I'm experiencing the exact issue and error message as https://github.com/aws/aws-mwaa-local-runner/issues/7 today.
@subashcanapathy mentioned that this was a transient problem on the repo URLs, was wondering if anyone could elaborate more on that and if there is anything I could do on my end to fix this.
Thank you!

I have same issue. Any further help?

Please try again--there was an issue with docker naming on some systems that has been resolved.

Same issue here too.

Stuck here as well.

@jplauri I managed to workaround this by changing this line: https://github.com/aws/aws-mwaa-local-runner/blob/v2.2.2/docker/docker-compose-local.yml#L17
For this:
build:
            context: .
            dockerfile: "${PWD}/docker/Dockerfile"

This worked for me.

The error in issue #7 mentions a timeout after 5 seconds, which is the default yum timeout.
Could not retrieve mirrorlist http://amazonlinux.default.amazonaws.com/2/core/latest/x86_64/mirror.list error was
12: Timeout on http://amazonlinux.default.amazonaws.com/2/core/latest/x86_64/mirror.list: (28, 'Resolving timed out after 5000 milliseconds')

Using curl we get the response in 6 seconds:
$ time docker run -it amazonlinux curl -s 'http://amazonlinux.default.amazonaws.com/2/core/latest/x86_64/mirror.list' > /dev/null

real	0m6,249s
user	0m0,012s
sys	0m0,024s

Seems like the server is slow in responding.
The solution for me was to increase this timeout by adding
sed -i 's/timeout=5/timeout=10/g' /etc/yum.conf

to https://github.com/aws/aws-mwaa-local-runner/blob/v2.2.2/docker/script/systemlibs.sh#L5

For me it helped adding --nework=host argument to the docker build command: https://github.com/aws/aws-mwaa-local-runner/blob/v2.2.2/mwaa-local-env#L55)](https://github.com/aws/aws-mwaa-local-runner/blob/v2.2.2/mwaa-local-env#L55


macOS 10.12

Seeing an issue with macOS 10.12 GM1 and GM2 at this point.  We cannot get the action or bash action to work at all.  10.11 or 10.10 of course works fine.  Not sure what has changed, sure it's on Apple's side.  Any news on when 10.12 will be supported via Yo official?  We love making use of it.

Well it appears this is only an issue with our compiled version to customize the app icon.  The package here works fine.  What could that be?

Hey @clarkml.
I just pushed a Swift 3 / Xcode 8 version to the testing branch if you want to try that.
Both the "action" and "bash action" seem to be working in my testing. Let me know how it goes for you!

Hey awesome!  We’ll check it out and provide feedback. I do believe we refactored to Swift 2.3 and that allowed us to get by.  I’m thankful for this app, makes a huge different on the experience of alerting our users.
Thank you!
From: Shea Craig<EMAIL_ADDRESS>Reply-To: sheagcraig/yo<EMAIL_ADDRESS>Date: Wednesday, September 28, 2016 at 11:08 AM
To: sheagcraig/yo<EMAIL_ADDRESS>Cc: "Mike Clark Jr (clarkm)"<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [sheagcraig/yo] macOS 10.12 (#14)
Hey @clarkmlhttps://github.com/clarkml.
I just pushed a Swift 3 / Xcode 8 version to the testing branch if you want to try that.
Both the "action" and "bash action" seem to be working in my testing. Let me know how it goes for you!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/sheagcraig/yo/issues/14#issuecomment-250195918, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ABjcN7JwALv3uGH5yNstMtcS4fOhL5Fxks5quoL-gaJpZM4J_pbc.


No time slice for AnalogSignals

It would be very useful to slice AnalogSignals by time, just like SpikeTrains.
l=bl.list_children_by_class("SpikeTrain")[0]
print l.time_slice(0,50000)
l=bl.list_children_by_class("AnalogSignal")[0]
print l.time_slice(0,5000)

Code is developed, needs pull request to Neo.

Where is the code?

No, I was thinking of Paul's code, but do not know where the latest is, but one version is hidden in here:
https://github.com/mdenker/python-neo/commits/master
However, as we now know, we do not need this anymore, since the AnalogSignalArray (which will become the new AnalogSignal) already has the time slice. So we could actually close this issue I think...

Was ported to neo.


Add WidgetsFlutterBinding Assertion to setMethodCallHandler

This adds an assertion to prevent an exception before WidgetsFlutterBinding has been initialized.
Fixes #84203.
Pre-launch Checklist

[x] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[x] I read the Tree Hygiene wiki page, which explains my responsibilities.
[x] I read and followed the Flutter Style Guide, including Features we expect every widget to implement.
[x] I signed the CLA.
[x] I listed at least one issue that this PR fixes in the description above.
[x] I updated/added relevant documentation (doc comments with ///).
[x] I added new tests to check the change I am making or feature I am adding, or Hixie said the PR is test-exempt.
[x] All existing and new tests are passing.

If you need help, consider asking for advice on the #hackers-new channel on Discord.

@flutter-dashboard I added tests now :)

@chunhtai All done 👍


Documentation: deferring a recover directly is a no-op (spec)

Please answer these questions before submitting your issue. Thanks!
What version of Go are you using (go version)?
go version go1.10.3 linux/amd64 (on Manjaro)
Does this issue reproduce with the latest release?
This is the latest release.
What operating system and processor architecture are you using (go env)?
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOOS="linux"

What did you do?
General form: defer recover()
Sample code demonstrating problem: https://play.golang.org/p/CwvgC7W6tw7
What did you expect to see?
One of the following:

Panic caught.
Compiler error.
Something in the spec explaining why this should not work.

What did you see instead?
Code panics, compiles with no errors.

@ianlancetaylor it then probably could have been explained better.

The return value of recover is nil if any of the following conditions holds:

Just because something returns nil does not mean it is a no-op.
It's not obvious from the https://golang.org/ref/spec#Handling_panics why returning nil is semantically equivalent to "it's skipped and does nothing".

It's not the case that it is skipped and does nothing.  It is called, does not recover a panic, and returns nil.
Are you suggesting that the spec should explicitly say that when recover is not called directly by a deferred function that any panic is not stopped?  Above and beyond saying that in that case recover returns nil?

does not recover a panic

this part is not obvious, at least from the spec.
I've re-read the https://golang.org/ref/spec#Handling_panics section once again and I cannot explain based solely on that section why https://play.golang.org/p/CwvgC7W6tw7 case b is not recovered.

Honest question: do you expect that the panic would be recovered but that recover would still return nil?
Any suggestions for improved wording here?

would still return nil?

given in defer recover() statement the recover() expression returns to nowhere - it would not surprise too much (again, given go already does something like that with returning multiple values).

Any suggestions for improved wording here?

Probably an explicit statement that defer recover() is effectively a no-op (and in Go2 it could be even a compiler error, given it's a mistake in 100% of cases).

Probably an explicit statement that defer recover() is effectively a no-op (and in Go2 it could be even a compiler error, given it's a mistake in 100% of cases).

The spec is not a tutorial, though.  We want to be precise without being verbose.

We want to be precise without being verbose.

And at the moment a standard compliant compiler for the defer recover() is allowed to recover.

I honestly think that you are misreading the spec.
I'm willing to clarify it and I hoping that you will be able to suggest a brief addition to make it more clear.

I'm really sorry to taking your time, seriously.
But in the spec I don't see anything about why defer recover() is a no-op. It only says that recover() would return  nil. Returning a nil does not mean it wouldn't recover.
Anyway, if you think it's clear and obvious - I'm not pushing, so be it like it is :-)

The crux of the matter is, catching an exception only works in Go if the expression recover() appears in a deferred function's body. The spec uses "Suppose a function G defers a function D that calls recover..."
The problem with this is, it makes it sound like a hypothetical when in all reality, it's a hard requirement. recover() must appear in a deferred function's body to work correctly.
This is an... interesting interface for exception handling and it's unintuitive and it's easy to get wrong. defer recover() should "just work" from a caller's perspective.


NoClassDefFoundError Only for Release. In Development the app is working

Xamarin.Android Version (eg: 6.0):
7.1
Operating System & Version (eg: Mac OSX 10.11):
Windows 10 Enterprise 1709
Support Libraries Version (eg: 23.3.0):
<IP_ADDRESS>
Describe your Issue:
In my Development Environment i can Start my app and everything is working. When i pack the app and upload the apk to the play store i get on the other Devices the error:
java.lang.NoClassDefFoundError: Failed resolution of: Landroid/support/v7/appcompat/R$drawable;
Am i missing something or do i have a mistake anywhere?
Steps to Reproduce (with link to sample solution if possible):
Include any relevant Exception Stack traces, build logs, adb logs:
packages.config.txt
logcat.txt

Found a Sollution. First i played around with the Linker Settings and found out that when i turn of the linker the app is working. So then i decide to made a Dummy function to include the Drawable class.
Like that:
private void noUseOnlyForLinker()
        {
            DrawableWrapper dwDummy;

        }

Is there something you can do to let the linker include the class when you need it? Or do i really need the Dummy function?

Please update to the latest Support library version


Tokio 0.3 and async-std 1.0 support

Eventually I'm able to implement the async-std support and also Tokio 0.3 support.
Kind of funny that this was the goal which started my signal-hook journey back in june :)
I added some macros to make common code for Tokio and async-std reusable. At the moment those live in their own small utility crate. Maybe there is a better place for them?

Using a symbolic link is a nice idea. I'm also more comfortable if we can keep those macros private. You're right, we agreed to put support for major releases into the root of the crate. I changed those things.
I can squash the last two commits into the appropriate initial ones if you do not have any other objections.

The adapter crates don't work on windows. But the failing step is cargo fmt. We could deactivate it in the CI script. But future contributors to the Windows parts would have the same problem. With this in mind I get the feeling that the symlink isn't a good solution.
I see the following options:

Go with the initial macro helper crate. The create requires a lot of boilerplate for two rather small macros. But in the end using crates is the recommended way for sharing code.
Moving the macros inside the main signal-hook crate. This shouldn't introduce any dependencies to the async runtimes or the futures crate. But the macros are strongly related to the async functionality. So it would feel odd to have them in this crate.
Do not try to be as DRY as possible between crates but only within a single crate. So implement the async_std crate by hand and use some macro in the Tokio crate to reduce duplication for wrapping the SignalIterator type. This also allows to tailor the documentation to the specific runtime. At the moment I had to write very generic documentation.
Move the adapter crates into their own Rust workspace and repository which then contains only Unix things. Using symbolic links there would be OK. Makes things more complicated w. r. t. CI, consistency and developer quality of life.

At the moment I would go with option 3. The introduced duplication can be easier removed than the public macros if someone has a better solution in the future.

At the moment I would go with option 3. The introduced duplication can be easier removed than the public macros if someone has a better solution in the future.

I agree the option 3, to duplicate a bit of code, is probably the least bad option, so lets go with it.

I removed the symbolic link. Hopefully the tests are OK now.

The remaining failure in the test also appears on the master branch. It looks like clippy got some additional tests recently.
I'm not sure if you already ran into this issue and fixed it in some other branch. If not I can add the suggested fix. Using try_for_each in this scenario looks correct to me.
If you do not have any further concerns I would squash the history into one commit for Tokio 0.3 and one for async-std and possibly add a third one for the clippy issue mentioned above.

Thank you :+1:
And I really promise to do some release soon.
I would like to accompany the release with a blog post and I would definitely like to thank you there and give you credit for all the work you've done. But I would like to check first, are you OK with that?

Thank you +1
And I really promise to do some release soon.
I would like to accompany the release with a blog post and I would definitely like to thank you there and give you credit for all the work you've done. But I would like to check first, are you OK with that?

It was my pleasure. I have to thank you for the good collaboration, too :+1:
I will be honored if you mention me in your blog post :smiley:


Update Haskell to LTS 22.9

Purpose
Update to GHC 9.6.4, LTS 22.9.
Changes

Update concordium-client
Clean up dependencies
Update http2-client and http2-grpc-haskell
Fix proto-lens related dependencies (outside current stackage).

Checklist

[X] My code follows the style of this project.
[X] The code compiles without warnings.
[X] I have performed a self-review of the changes.
[X] I have documented my code, in particular the intent of the
hard-to-understand areas.
[X] (If necessary) I have updated the CHANGELOG.

Did you make sure that the https://jenkins.internal.concordium.com/job/wallet-proxy/ builds?
I don't see any recent builds there.

Yes.


Simplify, improve and document the i18n pipeline

Fixes

Fixes #2591 by @zackkrida
Fixes #2885 by @dhruvkb
Fixes #2886 by @dhruvkb
Description

This PR

fixes a bug where untranslated locales would always be blank
fixes a bug where locales without ISO would be dropped from the application
fixes a bug where the translated field in the locale was missing in the TS type
removes fields from wp-locales.json that were not used anywhere
simplifies some code and adds logging in the locale management scripts
implements fallback locales, with Español covered as an example
adds documentation for the translation upload, download pipeline (to clarify the meaning of the Node scripts)
adds documentation about how to use fallback locales

Testing Instructions

Delete all i18n files.

frontend/src/locales/*.json
frontend/src/locales/scripts/(wp|valid|untranslated)-locales.json

Check out the PR and run the dev server.
Switch to Spanish (Mexico) as the locale, it is incompletely translated.
Compare the page to the same page on staging and see that in the locally running app, English fallback is nowhere to be seen.
Compare some strings from the 'About' page to translations for Spanish (Spain) and see that fallback locales have been recognised.

Checklist

[x] My pull request has a descriptive title (not a vague title likeUpdate index.md).
[x] My pull request targets the default branch of the repository (main) or a parent feature branch.
[x] My commit messages follow best practices.
[x] My code follows the established code style of the repository.
[ ] I added or updated tests for the changes I made (if applicable).
[x] I added or updated documentation (if applicable).
[x] I tried running the project locally and verified that there are no visible errors.
[ ] I ran the DAG documentation generator (if applicable).

Developer Certificate of Origin

Developer Certificate of Origin
Developer Certificate of Origin
Version 1.1

Copyright (C) 2004, 2006 The Linux Foundation and its contributors.
1 Letterman Drive
Suite D4700
San Francisco, CA, 94129

Everyone is permitted to copy and distribute verbatim copies of this
license document, but changing it is not allowed.

Developer's Certificate of Origin 1.1

By making a contribution to this project, I certify that:

(a) The contribution was created in whole or in part by me and I
    have the right to submit it under the open source license
    indicated in the file; or

(b) The contribution is based upon previous work that, to the best
    of my knowledge, is covered under an appropriate open source
    license and I have the right under that license to submit that
    work with modifications, whether created in whole or in part
    by me, under the same open source license (unless I am
    permitted to submit under a different license), as indicated
    in the file; or

(c) The contribution was provided directly to me by some other
    person who certified (a), (b) or (c) and I have not modified
    it.

(d) I understand and agree that this project and the contribution
    are public and that a record of the contribution (including all
    personal information I submit with it, including my sign-off) is
    maintained indefinitely and may be redistributed consistent with
    this project or the open source license(s) involved.

@dhruvkb I'm trying to review this but unfamiliar with frontend testing 😓  When I follow the steps in the PR description, locally I don't even see any option to switch locales:

@stacimc I missed a step because I thought it would run automatically. Can you run just frontend/run i18n and then test again?


feat: upgrade swc

It seems like the latest version of swc solves https://github.com/denoland/deno_lint/issues/1011, which I can confirm by comparing the AST output from different versions of swc in the swc playground. So it would be nice to upgrade it.
Relavant PR is https://github.com/swc-project/swc/pull/3449

@magurotuna thanks! :)


Tx status icon incorrect in activity tab

I performed a swap on Arkadiko and when the tx was in a mircoblock the tx status in the activity tab did not show the microblock icon. See images...

Closing as stale


macOS: Process explorer not put to front if minimized

Steps to Reproduce:

open process explorer on macOS
minimize the window
try to open the process explorer again

=> 🐛  the window is not restored

I can't repro on windows or mac:

I can no longer reproduce when I restore the window if minimized. Pushed a change also for issue reporter, please check i tout.


Update OSP version on stone-prd-m01

Update already verified on the staging clusters. We start with updating a single prod clusters to verify the process and MPC update after initially encountering some problems with the staging clusters.

@ifireball Can you update this PR to include the MPC  update so they both goes in at the same time

@ifireball Can you update this PR to include the MPC update so they both goes in at the same time

done.


Does not compile error

Can not open the file inclusion: hadesmem / injector.hpp

It requires hadesmem.  https://github.com/RaptorFactor/hadesmem


error on first time deploy of chart ISPN000512 Cannot acquire lock /opt/infinispan/server/data/___global.lck

I'm running into this error when deploying this helm chart to eks and not really sure what's going on. This is the first attempt at deploying this.
Our EKS cluster is 1.26
ISPN000512 Cannot acquire lock /opt/infinispan/server/data/___global.lck
install command used:
helm install infinispan-server . -n token-cache
No values overrides being used.
Full stack trace:
2023-11-13 21:13:23,197 ERROR (main) [org.infinispan.CONFIG] ISPN000660: DefaultCacheManager start failed, stopping any running components org.infinispan.commons.CacheConfigurationException: ISPN000512: Cannot acquire lock '/opt/infinispan/server/data/___global.lck' for persistent global state
	at org.infinispan.globalstate.impl.GlobalStateManagerImpl.acquireGlobalLock(GlobalStateManagerImpl.java:88)
	at org.infinispan.globalstate.impl.GlobalStateManagerImpl.start(GlobalStateManagerImpl.java:65)
	at org.infinispan.globalstate.impl.CorePackageImpl$1.start(CorePackageImpl.java:34)
	at org.infinispan.globalstate.impl.CorePackageImpl$1.start(CorePackageImpl.java:27)
	at org.infinispan.factories.impl.BasicComponentRegistryImpl.invokeStart(BasicComponentRegistryImpl.java:616)
	at org.infinispan.factories.impl.BasicComponentRegistryImpl.doStartWrapper(BasicComponentRegistryImpl.java:607)
	at org.infinispan.factories.impl.BasicComponentRegistryImpl.startWrapper(BasicComponentRegistryImpl.java:576)
	at org.infinispan.factories.impl.BasicComponentRegistryImpl$ComponentWrapper.running(BasicComponentRegistryImpl.java:807)
	at org.infinispan.factories.AbstractComponentRegistry.internalStart(AbstractComponentRegistry.java:379)
	at org.infinispan.factories.AbstractComponentRegistry.start(AbstractComponentRegistry.java:252)
	at org.infinispan.manager.DefaultCacheManager.internalStart(DefaultCacheManager.java:779)
	at org.infinispan.manager.DefaultCacheManager.start(DefaultCacheManager.java:747)
	at org.infinispan.server.SecurityActions.lambda$startCacheManager$1(SecurityActions.java:68)
	at org.infinispan.security.Security.doPrivileged(Security.java:56)
	at org.infinispan.server.SecurityActions.doPrivileged(SecurityActions.java:40)
	at org.infinispan.server.SecurityActions.startCacheManager(SecurityActions.java:71)
	at org.infinispan.server.Server.run(Server.java:417)
	at org.infinispan.server.Bootstrap.runInternal(Bootstrap.java:173)
	at org.infinispan.server.tool.Main.run(Main.java:98)
	at org.infinispan.server.Bootstrap.main(Bootstrap.java:56)
	at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77)
	at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.base/java.lang.reflect.Method.invoke(Method.java:568)
	at org.infinispan.server.loader.Loader.run(Loader.java:106)
	at org.infinispan.server.loader.Loader.main(Loader.java:51)
Caused by: java.io.FileNotFoundException: /opt/infinispan/server/data/___global.lck (Permission denied)
	at java.base/java.io.FileOutputStream.open0(Native Method)
	at java.base/java.io.FileOutputStream.open(FileOutputStream.java:293)
	at java.base/java.io.FileOutputStream.<init>(FileOutputStream.java:235)
	at java.base/java.io.FileOutputStream.<init>(FileOutputStream.java:184)
	at org.infinispan.globalstate.impl.GlobalStateManagerImpl.acquireGlobalLock(GlobalStateManagerImpl.java:82)
	... 25 more

2023-11-13 21:13:23,198 WARN  (main) [org.infinispan.CONTAINER] ISPN000574: Global state cannot persisted because it is incomplete (usually caused by errors at startup).
2023-11-13 21:13:23,384 FATAL (main) [org.infinispan.SERVER] ISPN080028: Infinispan Server failed to start org.infinispan.manager.EmbeddedCacheManagerStartupException: ISPN000512: Cannot acquire lock '/opt/infinispan/server/data/___global.lck' for persistent global state

I happened to have the exact same problem this morning. It seems that the persistent volume needs to be updated to allow it be writable.
Setting deploy.makeDataDirWritable: true in the values of the chart should solve this.

This also affects our operator https://github.com/infinispan/infinispan-operator/issues/392
Unfortunately we only have the workaround suggested by @rjl79. It would be great to have a better solution for this that didn't require an explicit workaround, but so far investigating this has been a low priority. Any suggestions are very welcome :slightly_smiling_face:

Thanks for the workaround @rjl79, although I cannot seem to get that to work.
I changed makeDataDirWritable: true in values.yaml and got Init:CreateContainerConfigError. I also tried this by modified my install command as such helm install infinispan-server . --set deploy.makeDataDirWritable=true -n token-cache and got Init:CreateContainerConfigError as well.

another workaround could be to explicitly set the fs group on the pv. See here

@rigazilla Sorry not quite following how that changes anything. Our situation is we are deploying to a namespace without privileged pod security. The initContainer data-chmod-pv seems like what is requiring elevated permissions and terminates when it's done. Leaving the infinispan container running as the jboss user. From what the template blocks says, the initContainer data-chmod-pv only runs when we set deploy.makeDataDirWriteable which is to fix the above issue error ISPN000512 Cannot acquire lock /opt/infinispan/server/data/___global.lck. Taking all this in seems to make me think we just need a way to set the perms and mount that /opt/infinispan/server/data other than using the initContainer. I added the fsGroup as in the link you provided, but it didn't change anything on our end when turning off privileged access in the namespace. I haven't had much exposure to helm charts, so maybe I'm missing something.

@thetoolsmith , you have security issue or the solution doesn't work?
I didn't specify but you don't need the  deploy.makeDataDirWriteable: true change for this; with fsGroup kubernetes should set correctly the group on the file system for you (see here)

Thanks @rigazilla . I updated the config and the containers are starting up now without the need to set privileged on the namespace.

possibly we could expose the fsgroup workaround via a flag in the values.yaml file

+1 to allowing this to be configurable. How about allowing  a user to specify the entire container securityContext via deploy.container.securityContext?


Switch isEmpty() to .equals("")

Issue #, if available:
Main-build Enablement E2E tests started failing starting from this PR. It was due to the usage of isEmpty(), which isn't compatible with Java 8.
Description of changes:
Replaced all reference to the method isEmpty() with .equals("")
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

:warning: Please install the  to ensure uploads and comments are reliably processed by Codecov.
Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 71.99%. Comparing base (09e6487) to head (f8a8fa9).
Report is 361 commits behind head on main.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@              Coverage Diff              @@
##               main     #939       +/-   ##
=============================================
- Coverage     85.71%   71.99%   -13.73%
- Complexity       19      278      +259
=============================================
  Files             3       21       +18
  Lines            49      989      +940
  Branches          5      144      +139
=============================================
+ Hits             42      712      +670
- Misses            3      233      +230
- Partials          4       44       +40

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


🚧 Add a pull request template

 Create a PR template for the parser

The template is lacking instructions on how to reference the issue they are solving, if this is relevant.

This LGTM, but I am a bit unsure on something - do the people copy and paste and edit this template into the description of the PR then? I assume so, but maybe you should clarify that this is what's expected at the beginning?

@lizgzil If you're unsure of what to do with this, then it's worth specifying it 😄

@jdkram @nsorros @lizgzil Another round? (Hopefully the last one 😄 )

@jdkram Fixed

@SamDepardieu 🎉

Still need two other approvals 😢

@SamDepardieu see if they leave their laptops unlocked in Datalabs...


Explicitly mark lone getters as readonly

Fixes #4229
I confirm I have read the contributing guidelines and signed the Contributor License Agreement.

This is great! Such an easy solution!

Actually, it's not that easy. The TS declarations now fail to compile with errors like:
build/playcanvas.d.ts(466,5): error TS1024: 'readonly' modifier can only appear on a property declaration or index signature.

And it seems JSDoc isn't smart enough to spot a getter without a setter and mark it as readonly implicitly. 😢

Closing for now this since it breaks the TS declarations.


Improve Github Workflows

Proposed Changes
This PR should fix an issue, where Megalinter scanned workflow files, despite being excluded.
Also this PR should fix the issues, that Megalinter had found within the Yaml files.
Related Issues

(Github link to related issues or pull requests)

GitHub Actions contain workflow_dispatch inputs parameters
To maintain an untampered workflow, pipelines should be unaffected by user input. In GitHub Actions, workflow_dispatch allows you to manually trigger pipelines and enter unique inputs per run. While this may be helpful for running different scenarios, it breaks the policy that workflows should not use user input and should be automated.
Thats the reason. Github Actions wont like manual user input in those runs.
We will remove the check fully for now

About the part that megalinter still scans files within the workflow folder: Looks like a bug to me, but I will try to figure it out

GitHub Actions contain workflow_dispatch inputs parameters To maintain an untampered workflow, pipelines should be unaffected by user input. In GitHub Actions, workflow_dispatch allows you to manually trigger pipelines and enter unique inputs per run. While this may be helpful for running different scenarios, it breaks the policy that workflows should not use user input and should be automated.
Thats the reason. Github Actions wont like manual user input in those runs.
We will remove the check fully for now

I agree with that, but I implemented a workload that I want to run with parameters to automatically create a new release (and avoid any mistake on releasing new version)


Add command to list deployments with commit id and/or commit message

How can recent deployments be listed including the commit ID and message for each? This feature would streamline deployment tracking by displaying essential commit details in a single view.

@ACPK - are you using Github? If so you could call something like this to a post deploy hook:
#!/usr/bin/env bash

gh release create $KAMAL_SERVICE_VERSION --target $KAMAL_VERSION --generate-notes 2> /dev/null || true

The you can view the releases in the Github UI.
You probably want to gate it based on the branch and destination though if you deploy to multiple ones.
Kamal doesn't contain release tracking itself though and there are no plans to add it, right now anyway.


DOCS-4924 Platform limits (adapted from Runtime Manager info)

Closing this - changes in https://github.com/mulesoft/docs-private-cloud/pull/49.


Missing hyphen before description and newline

/**
 * @param {!Array} value -
 *   [0] - some value;
 *   [1] - some value
 */
function foo(value) {
}

---
Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/26064979-missing-hyphen-before-description-and-newline?utm_campaign=plugin&utm_content=tracker%2F281640&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F281640&utm_medium=issues&utm_source=github).

Can you elaborate? ;-) You don't want to have this hyphen if it ends with a newline?

Can you elaborate? ;-) You don't want to have this hyphen if it ends with a newline?

All fine
/**
 * @param {!Array} value - parameters:
 *   [0] - some value;
 *   [1] - some value
 */
function foo(value) {
}

Error, but it must work
/**
 * @param {!Array} value -
 *   [0] - some value;
 *   [1] - some value
 */
function foo(value) {
}

@zxqfox is this still an issue?

Yep, unfortunately. I've missed this issue. Will fix it in a week or so.

At this point only major and CST related bugs will be fixed.


Temperature Rewrite

#143 rewrite
Adds brakes and suspension temperatures

Codecov Report

Merging #150 (90046b0) into master (516a539) will increase coverage by 0.06%.
The diff coverage is 27.27%.

@@            Coverage Diff             @@
##           master     #150      +/-   ##
==========================================
+ Coverage   38.20%   38.27%   +0.06%
==========================================
  Files          69       69
  Lines        3942     3977      +35
==========================================
+ Hits         1506     1522      +16
- Misses       2436     2455      +19

Impacted Files
Coverage Δ

src/data/data.hpp
100.00% <ø> (ø)

src/sensors/temperature.hpp
100.00% <ø> (ø)

src/sensors/temperature.cpp
8.33% <7.69%> (-8.34%)
:arrow_down:

src/sensors/main.cpp
35.92% <31.70%> (+2.70%)
:arrow_up:

src/debugging/observer.cpp
32.22% <100.00%> (ø)

Continue to review full report at Codecov.

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


Add a Frames option to the timer node

Adds a frame option to the Timer node.
This is useful for frame-timed games such as doom-likes or tick-games.
I'm uncertain about using wait_time as fake ints for frame counting but introducing a hell of new variables seemed not optimal as well.
Looking forward to any feedback.

Thank you for your contributions, but I would recommend opening a proposal first to gauge interest in this.
Implementation aside, personally, this feature is superfluous. Especially nowadays, a strict dependency on framerate is generally undesirable and prone to very, very nasty bugs.
If you want to gather seconds from a count in ticks, keep in mind you can evaluate expressions inside of the Inspector's input fields. With that knowledge, you can divide a number of ticks by, for example, the physics ticks per second. 5 ticks, 60 ticks per second, 5 / 60.0 (notice the float division) equals 0.0833333333, which is the corresponding time in seconds.
The engine's unit of time is often in seconds, so this is extremely consistent.

Fair points!

Thank you for your contributions, but I would recommend opening a proposal first to gauge interest in this.

I've aonly implemented this because of interest from discords and reddit. But yeah I guess a Proposal would have been better.

Implementation aside, personally, this feature is superfluous. Especially nowadays, a strict dependency on framerate is generally undesirable and prone to very, very nasty bugs.

Yes and no - sure it not needed for 99% of the users but you very often see people start their programming journey by cloning games and a lot of games used to be frame rate bound (see doom). So I still think its useful to have given the low maintenance this needs once implemented  - especially because its completely optional and not the default.

If you want to gather seconds from a count in ticks, keep in mind you can evaluate expressions inside of the Inspector's input fields. With that knowledge, you can divide a number of ticks by, for example, the physics ticks per second. 5 ticks, 60 ticks per second, 5 / 60.0 (notice the float division) equals 0.0833333333, which is the corresponding time in seconds. The engine's unit of time is often in seconds, so this is extremely consistent.

On a second note - I had this problem multiple times before; for some reason github workflows/tests pass on my fork but then fail on PR. Is there a reason for that?

On a second note - I had this problem multiple times before; for some reason github workflows/tests pass on my fork but then fail on PR. Is there a reason for that?

It's a fault of the checking system. Sometimes the servers fail for reasons entirely out of your control. Force-pushing (basically trying again) tends to fix it.

you very often see people start their programming journey by cloning games and a lot of games used to be frame rate bound (see doom).

I do sympathise. I was one of them, and I still am. Some parts of my code are framerate dependent because it is sometimes faster to write. But I still don't think it should be encouraged by implementing this feature on an easily accessible node, for the reasons I stated above.

In the era of variable refresh rates and arbitrary framerate limits, I'd say this encourages bad practices. I only know one game genre where durations are still expressed in frames (fighting games), and even then, I'd say it's legacy baggage at this point :slightly_smiling_face:
Either way, this should be discussed in a proposal.

On a second note - I had this problem multiple times before; for some reason github workflows/tests pass on my fork but then fail on PR. Is there a reason for that?

It's a fault of the checking system. Sometimes the servers fail for reasons entirely out of your control. Force-pushing (basically trying again) tends to fix it.

you very often see people start their programming journey by cloning games and a lot of games used to be frame rate bound (see doom).

I do sympathise. I was one of them, and I still am. Some parts of my code are framerate-dependent because it is sometimes faster to write and less bloated. But I still don't think it should be encouraged by implementing this feature on an easily accessible node, for the reasons I stated above. Code in a script tends to suffice.

I see thanks. Will open a Proposal


Example makefile for prox_reporter project

@pkmurphy-renesas, Sorry we're lagging in reviewing that. We'll work on it ASAP

@blauret, anything else I need to do before this is reviewed/merged? I think the build-check-deploy action may be failing as this pull request originated from a fork of the repo. Need me to move the changes to a branch of this repo and do a new pull request?

Hello @pkmurphy-renesas,
The checks for this pull request are failing because the merge is from your private GitHub where there are no valid AWS credentials configured. This can be fixed by first merging your private repo onto a branch of this repo (for which you do not need to pass any checks) and then merging that branch into the main.

Closing this pull request. Will merge into another branch of this repo and initiate a new pull request from it.


AARCH64 (apple silicon) support

When on Apple Silicon use the arm64 binary from: https://github.com/vscode-shellcheck/shellcheck-binaries/releases/tag/v0.9.0

Shellcheck proper does not yet publish this binary.
there is an issue open https://github.com/koalaman/shellcheck/issues/2714 but has not yet provided it's own arm64 build.
luckily vscode-shellcheck/shellcheck-binaries does provide this binary

@aignas is it ok for you?

Thinking about this a little more, we should support pulling all of the binaries from either the upstream or the vscode github repo. At the end of the day we would be pulling from GH, defaulting to the vscode repo would make sense. What is more, adding all of the available platforms would be also good.

If you are OK with it, I would gladly update this to pull all binaries from vscode-shellcheck/shellcheck-binaries releases.

Thanks, that would be great. Whilst you are at it, could you also add the extra supported platforms as well?
On 3 January 2024 04:22:24 GMT+09:00, Stefan Penner @.***> wrote:

If you are OK with it, I would gladly update this to pull all binaries from vscode-shellcheck/shellcheck-binaries releases.
--
Reply to this email directly or view it on GitHub:
https://github.com/aignas/rules_shellcheck/pull/30#issuecomment-1874446103
You are receiving this because you were mentioned.
Message ID: @.***>

Let me work on that.

I've switched this to always use the binaries provided by: https://github.com/vscode-shellcheck/shellcheck-binaries
I've also included all available architectures, apple silicon, windows, raspberry pie, but was only able to test that apple silicon actually works, because I do not have windows or a raspberry pie around.
This could be good for another view.

Let's switch to x86_64 everywhere and this will be good for merging.
✅

Maybu adding a bazel skylib build_test to ensure that we can fetch each platform-specific binary would be nice to have, but I am happy to leave this out of the scope of this PR.

That is a good idea, unfortunately I'm a little strapped for time or I would gladly doit.

Consider doing bazel fetch on the shellcheck target to check that repo definitions are correct for all platforms.

Consider doing bazel fetch on the shellcheck target to check that repo definitions are correct for all platforms.

Good catch, linux arm -> aarch change has been added, and now bazel fetch //... completes without issue. Any additional checks I should run?

Merged as the examples are broken due to bzlmod by default, which will need to be fixed separately.

@aignas thank you for the reviews! Could I ask when a release might be cut?

I'll be looking into that next week.
On 5 January 2024 01:20:28 GMT+09:00, Stefan Penner @.***> wrote:

@aignas thank you for the reviews! Could I ask when a release might be cut?
--
Reply to this email directly or view it on GitHub:
https://github.com/aignas/rules_shellcheck/pull/30#issuecomment-1877382038
You are receiving this because you were mentioned.
Message ID: @.***>

Has been released in https://github.com/bazelbuild/bazel-central-registry/pull/1303

@aignas thanks for the merge & release!


Create Ashokleyland.txt

Adding Ashokleyland

@Prasanna-Git This domain does not belong to an educational institution. I have to close the request without merging. Please ensure you are familiar with this repository rules located at the bottom of this page. Thank you for the understanding!


RPC is dreamy

#3297 noted that our JSON approach was confusing
#3339 introduced some standardisation with a HasLotusJson trait, and clarified the issues with the prior approach
#3345 introduced the LotusJson<T> struct, and made the API cleaner and easier to implement
#3390 removes the old json module altogether
#3389 is outstanding
#3383 is outstanding
[ ] crate::ipld::json needs to be removed
[ ] Consider splitting snapshots out of HasLotusJson
[x] #3638

Currently a bit reluctant to add macros to the codebase, and this would maybe only be useful for a handful of types at present

[ ] Documentation needs clarifying on when it's acceptable to use #[serde(with = "crate::lotus_json")]
[ ] trait RPCEndpoint needs design/implemention #3029
[ ] removal of LotusJson<T> altogether

Superseded by #4032


Update getStarted.tsx

Material UI TextField accepts inputRef asi reference not innerRef. I changed in all languages except in japanesse and chinese because they already differ from other languages translation.

thank you @cargallo <3


Adding detailed rewards doc

Adds informations about

Rewards schedule
Rewards calculation

@joshuahannan Did this get the OK ?

No, this will definitely need more work


add support for debian based OS

We are running the puppet module on Ubuntu 20.04 and 22.04 and so far it works flawlessly. Would it be possible to update the metadata and add support for debian based OS?

Unfortunately, I am seeing errors when trying to persist firewall rules using the module on Ubuntu 22.04
Execution of '/usr/sbin/service iptables-persistent save' returned 1: iptables-persistent: unrecognized service


Add publish workflow

This sets up the action that publishes beta versions and makes a PR for the release like this PR https://github.com/tinacms/tina-graphql-gateway/pull/358

how does the matrix work in this situation? is it going to run a publish to latest every time code lands on main?


Academic Programs as a Related Object

With the focus on Education, there is functionality to relate events to Academic Programs. These would be managed in an object and records to be created based on the users desired functionality.
Need to create the related objects and/or connect to EDA functioning objects.

I believe we should use the EDA functionality for Academic Programs - "An Academic Program in EDA is simply an Account with a specific record type called 'Academic Program'."  https://powerofus.force.com/s/article/EDA-Create-Academic-Programs-and-Program-Enrollments

THis is related to #14.  Closing this one to utilize #14


!players insurgency isn't working

Needs to get the players list from the insurgency server.

Fixed...


Updated postcodes for PIP

Update to outcome: https://www.gov.uk/pip-checker/y/yes/1985-01-01
I've combined the 2 sets of postcodes that went live on 13 July and 17 August. And added a new list of postcodes to be included from 1 September.

:+1:
Closing in favour of #1905


Crash upon equipping neural interface in goggle trinket slot

crash-2024-08-22_01.33.42-server.txt

Plethora is currently incompatible with CC:T 1.112 or later. Afraid you'll need to downgrade to CC:T 1.111 for now.


fix: alpha-numeric sorting of tokens

Description

get tokens with number in the token name sorted/ordered properly by alpha-numeric order
spectrum-non-color data only

Motivation and context

Related issue

https://jira.corp.adobe.com/browse/DTT-1952
Types of changes

[X] Patch (bug fixes, typos, mistakes; non-breaking change which fixes an issue)
[ ] Minor (add a new token, changing a value; non-breaking change which adds functionality)
[ ] Major (deleting a token, changing token value type; fix or feature that would cause existing functionality to change)

Checklist:

[X] I have signed the Adobe Open Source CLA.
[X] I updated the token in all applicable sets. This applies if updating, adding, or deleting a token that has data across different sets (for example, if the value differs across color themes.)


NEW Add sniffer code

NOTES

After this is merged, we need to add it to packagist and set up the relevant webhook(s).
The CI builds on the cc fork are failing, but they pass locally. I think it's related to https://github.com/silverstripe/gha-generate-matrix/pull/70

Issue

https://github.com/silverstripe/developer-docs/issues/11

Was some of this code lifted and shifted from PHPCS? If so can you point out those bits so I can largely ignore them

As discussed in person, I've pointed the main blocks of these out with PR comments, plus the FixerReport is basically a lift-and-shift with some parts removed.
There are other bits here-and-there but not in such easily identifiable chunks.


chore: remove bats test suite

Reason for Change:

Requirements

[x] squashed commits
[x] included documentation
[x] added unit tests and e2e tests (if applicable).

Issue Fixed:

Does this change contain code from or inspired by another project?

[ ] Yes
[x] No

If "Yes," did you notify that project's maintainers and provide attribution?
Special Notes for Reviewers:

Codecov Report

Merging #391 (d9e348b) into master (d0a8e14) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #391   +/-   ##
=======================================
  Coverage   62.86%   62.86%
=======================================
  Files           6        6
  Lines         474      474
=======================================
  Hits          298      298
  Misses        144      144
  Partials       32       32

I don't think we are testing pv/pvc in the driver or provider anymore. should we remove these?

Sounds good! I've removed it from the examples folder.


Process to generate Event list is CSV formatted text-file

Hi @toni-heittola,
I am first time working on the SED task and got stuck in the generation of the Event list is CSV formatted text-file during the evaluation in Development dataset and Evaluation dataset of DCASE 2017 task 2 and 3. I can get the test predictions but am not sure about how to convert these frame-wise predictions to the time intervals (onset and offset time interval) for the Event list is CSV formatted text-file. Kindly help me to get any reference where I can learn this process from.
Stay Safe
Best Regards

In order to convert frame-based predictions to onset-offset lists, one needs to go through frames in order and identify contiguous active regions.
In the DCASE2017 baseline system, this is implemented here > https://github.com/TUT-ARG/DCASE2017-baseline-system/blob/master/dcase_framework/recognizers.py#L160
The same functionality has been later released in dcase_util package as method dcase_util.data.DecisionEncoder.find_contiguous_regions. Here is the tutorial how to use this > https://dcase-repo.github.io/dcase_util/tutorial_data.html#decision-encoding
This will give you a list of frame indices. In order to get onset and offset in seconds, one needs to multiply these with the analysis hop length (often feature extraction hop length).

Hi @toni-heittola, thank you very much for sharing the detail. I will have a look at this. I have the following queries regarding DCASE 2017 Challenge:

In the case of the Mono SED task (DCASE 2017 Task 2) do we need to train three different models for each event with ground truth of length 1 i.e., either [0] or [1]? or there should be a single model with a dense layer of 3 units to detect the three events?
I came across one of the examples created by you for DCASE 2017 task 3. However, I can see that you are downloading and preprocessing the dataset using the dcase_util library. But in my case, I need to use the already downloaded copy of the DCASE 2017 Task 3 dataset and need to extract Mel-spectrogram as the feature instead of Mel-band energy. So, is it possible to use the dcase_util library for analyzing and preprocessing the local copy of the dataset?

Best Regards

In DCASE2017 task 2, "Target sound event categories will be treated independently, therefore it is allowed to use completely different approaches for detection, tailored to the characteristics of each sound category." One solution for this is to build three separate systems (models).
dcase_util library has dataset classes to download, extract and handle metadata. If you specify data_path parameter to the directory with already downloaded zip packages, the download will be skipped.

db = dcase_util.datasets.TUTSoundEvents_2017_DevelopmentSet(
    data_path=dataset_storage_path
).initialize()

Hi @toni-heittola ,
Thank you for the confirmation. In my case the downloaded dataset is already extracted and merged in different directories as below:
dcase_2017_task_3\development\audio\street
dcase_2017_task_3\development\meta\evaluation_setup
dcase_2017_task_3\evaluation\audio\street
dcase_2017_task_3\evaluation\meta\evaluation_setup

Then this should work:
db_dev = dcase_util.datasets.TUTSoundEvents_2017_DevelopmentSet(
    data_path='dcase_2017_task_3\development\'
).initialize()

db_eval = dcase_util.datasets.TUTSoundEvents_2017_EvaluationSet(
    data_path='dcase_2017_task_3\evaluation\'
).initialize()

Just place dev and eval dataset zip-packages under those folder. I will close this issue now as it is not about sed_eval.


Update to latest API

I'll make a pull request for this as I get a little time, but working on the current version of the Sovren API I had to use my own client class to make the API calls.  The classes in this library for parsing still worked great on the response, so it's just the client that needs updating.

Hi -- any movement on this? It's been a couple years...

Should this issue be closed now, since the PR has been merged?

Also should the gem's version - in lib/sovren/version.rb -- be updated?

This got merged in on #9


🐛 Global viewGenerator not been applied to the nodes

The PR #103 changes introduced in the latest release (2.0.0-rc1) do seem to have a bug when being applied to real projects. If the user defines a viewGenerator in the config object, its value is completely ignored and the default view is used instead.
It seems as if the Node object receives viewGenerator as an undefined value, instead of receiving the generator function defined by the user in the config object. Things work fine if the viewGenerator is defined at node level, though.
For some reason, this error does not happen in the Sandbox example, which is why this issue wasn't detected before merging the feature into the main branch.

As the author of the changes, I'll make myself responsible for this and upload a fix for this ASAP. Sorry for the inconvenience! 😞

Closing with #131


Add logo for better branding

Signed-off-by: Baiju Muthukadan<EMAIL_ADDRESS>

Codecov Report

Merging #133 (fb88557) into main (9612884) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #133   +/-   ##
=======================================
  Coverage   82.02%   82.02%
=======================================
  Files          14       14
  Lines        1346     1346
=======================================
  Hits         1104     1104
  Misses        206      206
  Partials       36       36

Continue to review full report at Codecov.

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