Adapter chrashes when srf is not sending valid json

Adapter crashes when srf is not sending a valid json. after trying to restart, adapter will stay stopped.
Use
typeof body[0].id == undefined
to check if variable is there. NOT
body[0].id === undefined

2021-06-09 18:49:25.158  - error: swiss-weather-api.0 (19183) uncaught exception: Cannot read property '60minutes' of undefined
2021-06-09 18:49:25.164  - error: swiss-weather-api.0 (19183) TypeError: Cannot read property '60minutes' of undefined
at IncomingMessage. (/opt/iobroker/node_modules/iobroker.swiss-weather-api/main.js:1480:17)
at IncomingMessage.emit (events.js:327:22)
at endReadableNT (_stream_readable.js:1221:12)
at processTicksAndRejections (internal/process/task_queues.js:84:21)
2021-06-09 18:49:25.166  - error: swiss-weather-api.0 (19183) Cannot read property '60minutes' of undefined
2021-06-09 18:49:25.222  - info: swiss-weather-api.0 (19183) cleaned everything up...
2021-06-09 18:49:25.225  - info: swiss-weather-api.0 (19183) terminating
2021-06-09 18:49:25.229  - warn: swiss-weather-api.0 (19183) Terminated (UNCAUGHT_EXCEPTION): Without reason
2021-06-09 18:49:25.232  - error: swiss-weather-api.0 (19183) uncaught exception: Cannot read property 'id' of undefined
2021-06-09 18:49:25.235  - error: swiss-weather-api.0 (19183) TypeError: Cannot read property 'id' of undefined
at Immediate. (/opt/iobroker/node_modules/iobroker.swiss-weather-api/main.js:1128:28)
at processImmediate (internal/timers.js:458:21)
2021-06-09 18:49:25.237  - error: swiss-weather-api.0 (19183) Cannot read property 'id' of undefined
2021-06-09 18:49:25.241  - error: swiss-weather-api.0 (19183) uncaught exception: Cannot read property 'lat' of undefined
2021-06-09 18:49:25.243  - error: swiss-weather-api.0 (19183) TypeError: Cannot read property 'lat' of undefined
at Immediate. (/opt/iobroker/node_modules/iobroker.swiss-weather-api/main.js:1143:28)
at processImmediate (internal/timers.js:458:21)
2021-06-09 18:49:25.245  - error: swiss-weather-api.0 (19183) Cannot read property 'lat' of undefined
2021-06-09 18:49:25.250  - error: swiss-weather-api.0 (19183) uncaught exception: Cannot read property 'lon' of undefined
2021-06-09 18:49:25.253  - error: swiss-weather-api.0 (19183) TypeError: Cannot read property 'lon' of undefined
at Immediate. (/opt/iobroker/node_modules/iobroker.swiss-weather-api/main.js:1158:28)
at processImmediate (internal/timers.js:458:21)
2021-06-09 18:49:25.255  - error: swiss-weather-api.0 (19183) Cannot read property 'lon' of undefined
2021-06-09 18:49:25.259  - error: swiss-weather-api.0 (19183) uncaught exception: Cannot read property 'station_id' of undefined
2021-06-09 18:49:25.260  - error: swiss-weather-api.0 (19183) TypeError: Cannot read property 'station_id' of undefined
at Immediate. (/opt/iobroker/node_modules/iobroker.swiss-weather-api/main.js:1173:28)
at processImmediate (internal/timers.js:458:21)
2021-06-09 18:49:25.262  - error: swiss-weather-api.0 (19183) Cannot read property 'station_id' of undefined
2021-06-09 18:49:25.265  - error: swiss-weather-api.0 (19183) uncaught exception: Cannot read property 'timezone' of undefined
2021-06-09 18:49:25.266  - error: swiss-weather-api.0 (19183) TypeError: Cannot read property 'timezone' of undefined
at Immediate. (/opt/iobroker/node_modules/iobroker.swiss-weather-api/main.js:1188:28)
at processImmediate (internal/timers.js:458:21)
2021-06-09 18:49:25.267  - error: swiss-weather-api.0 (19183) Cannot read property 'timezone' of undefined
2021-06-09 18:49:25.270  - error: swiss-weather-api.0 (19183) uncaught exception: Cannot read property 'default_name' of undefined
2021-06-09 18:49:25.271  - error: swiss-weather-api.0 (19183) TypeError: Cannot read property 'default_name' of undefined
at Immediate. (/opt/iobroker/node_modules/iobroker.swiss-weather-api/main.js:1203:28)
at processImmediate (internal/timers.js:458:21)
2021-06-09 18:49:25.273  - error: swiss-weather-api.0 (19183) Cannot read property 'default_name' of undefined
2021-06-09 18:49:25.275  - error: swiss-weather-api.0 (19183) uncaught exception: Cannot read property 'alarm_region_id' of undefined
2021-06-09 18:49:25.277  - error: swiss-weather-api.0 (19183) TypeError: Cannot read property 'alarm_region_id' of undefined
at Immediate. (/opt/iobroker/node_modules/iobroker.swiss-weather-api/main.js:1218:28)
at processImmediate (internal/timers.js:458:21)
2021-06-09 18:49:25.278  - error: swiss-weather-api.0 (19183) Cannot read property 'alarm_region_id' of undefined
2021-06-09 18:49:25.281  - error: swiss-weather-api.0 (19183) uncaught exception: Cannot read property 'alarm_region_name' of undefined
2021-06-09 18:49:25.282  - error: swiss-weather-api.0 (19183) TypeError: Cannot read property 'alarm_region_name' of undefined
at Immediate. (/opt/iobroker/node_modules/iobroker.swiss-weather-api/main.js:1233:28)
at processImmediate (internal/timers.js:458:21)
2021-06-09 18:49:25.284  - error: swiss-weather-api.0 (19183) Cannot read property 'alarm_region_name' of undefined
2021-06-09 18:49:25.286  - error: swiss-weather-api.0 (19183) uncaught exception: Cannot read property 'district' of undefined
2021-06-09 18:49:25.288  - error: swiss-weather-api.0 (19183) TypeError: Cannot read property 'district' of undefined
at Immediate. (/opt/iobroker/node_modules/iobroker.swiss-weather-api/main.js:1248:28)
at processImmediate (internal/timers.js:458:21)
2021-06-09 18:49:25.289  - error: swiss-weather-api.0 (19183) Cannot read property 'district' of undefined
2021-06-09 18:49:25.292  - error: swiss-weather-api.0 (19183) uncaught exception: Cannot read property 'geolocation_names' of undefined
2021-06-09 18:49:25.293  - error: swiss-weather-api.0 (19183) TypeError: Cannot read property 'geolocation_names' of undefined
at Immediate. (/opt/iobroker/node_modules/iobroker.swiss-weather-api/main.js:1264:28)
at processImmediate (internal/timers.js:458:21)
2021-06-09 18:49:25.295  - error: swiss-weather-api.0 (19183) Cannot read property 'geolocation_names' of undefined
2021-06-09 18:49:25.297  - error: swiss-weather-api.0 (19183) uncaught exception: Cannot read property 'geolocation_names' of undefined
2021-06-09 18:49:25.298  - error: swiss-weather-api.0 (19183) TypeError: Cannot read property 'geolocation_names' of undefined
at Immediate. (/opt/iobroker/node_modules/iobroker.swiss-weather-api/main.js:1278:28)
at processImmediate (internal/timers.js:458:21)
2021-06-09 18:49:25.300  - error: swiss-weather-api.0 (19183) Cannot read property 'geolocation_names' of undefined
2021-06-09 18:49:25.306  - error: swiss-weather-api.0 (19183) uncaught exception: Cannot read property 'geolocation_names' of undefined
2021-06-09 18:49:25.307  - error: swiss-weather-api.0 (19183) TypeError: Cannot read property 'geolocation_names' of undefined
at Immediate. (/opt/iobroker/node_modules/iobroker.swiss-weather-api/main.js:1292:28)
at processImmediate (internal/timers.js:458:21)
2021-06-09 18:49:25.308  - error: swiss-weather-api.0 (19183) Cannot read property 'geolocation_names' of undefined
2021-06-09 18:49:25.310  - error: swiss-weather-api.0 (19183) uncaught exception: Cannot read property 'geolocation_names' of undefined
2021-06-09 18:49:25.312  - error: swiss-weather-api.0 (19183) TypeError: Cannot read property 'geolocation_names' of undefined
at Immediate. (/opt/iobroker/node_modules/iobroker.swiss-weather-api/main.js:1306:28)
at processImmediate (internal/timers.js:458:21)
2021-06-09 18:49:25.313  - error: swiss-weather-api.0 (19183) Cannot read property 'geolocation_names' of undefined
2021-06-09 18:49:25.315  - error: swiss-weather-api.0 (19183) uncaught exception: Cannot read property 'geolocation_names' of undefined
2021-06-09 18:49:25.317  - error: swiss-weather-api.0 (19183) TypeError: Cannot read property 'geolocation_names' of undefined
at Immediate. (/opt/iobroker/node_modules/iobroker.swiss-weather-api/main.js:1320:28)
at processImmediate (internal/timers.js:458:21)
2021-06-09 18:49:25.318  - error: swiss-weather-api.0 (19183) Cannot read property 'geolocation_names' of undefined
2021-06-09 18:49:25.320  - error: swiss-weather-api.0 (19183) uncaught exception: Cannot read property 'geolocation_names' of undefined
2021-06-09 18:49:25.321  - error: swiss-weather-api.0 (19183) TypeError: Cannot read property 'geolocation_names' of undefined
at Immediate. (/opt/iobroker/node_modules/iobroker.swiss-weather-api/main.js:1334:28)
at processImmediate (internal/timers.js:458:21)
2021-06-09 18:49:25.322  - error: swiss-weather-api.0 (19183) Cannot read property 'geolocation_names' of undefined
2021-06-09 18:49:25.324  - error: swiss-weather-api.0 (19183) uncaught exception: Cannot read property 'geolocation_names' of undefined
2021-06-09 18:49:25.326  - error: swiss-weather-api.0 (19183) TypeError: Cannot read property 'geolocation_names' of undefined
at Immediate. (/opt/iobroker/node_modules/iobroker.swiss-weather-api/main.js:1348:28)
at processImmediate (internal/timers.js:458:21)
2021-06-09 18:49:25.327  - error: swiss-weather-api.0 (19183) Cannot read property 'geolocation_names' of undefined
2021-06-09 18:49:25.329  - error: swiss-weather-api.0 (19183) uncaught exception: Cannot read property 'geolocation_names' of undefined
2021-06-09 18:49:25.330  - error: swiss-weather-api.0 (19183) TypeError: Cannot read property 'geolocation_names' of undefined
at Immediate. (/opt/iobroker/node_modules/iobroker.swiss-weather-api/main.js:1362:28)
at processImmediate (internal/timers.js:458:21)
2021-06-09 18:49:25.331  - error: swiss-weather-api.0 (19183) Cannot read property 'geolocation_names' of undefined
2021-06-09 18:49:25.334  - error: swiss-weather-api.0 (19183) uncaught exception: Cannot read property 'geolocation_names' of undefined
2021-06-09 18:49:25.335  - error: swiss-weather-api.0 (19183) TypeError: Cannot read property 'geolocation_names' of undefined
at Immediate. (/opt/iobroker/node_modules/iobroker.swiss-weather-api/main.js:1376:28)
at processImmediate (internal/timers.js:458:21)
2021-06-09 18:49:25.336  - error: swiss-weather-api.0 (19183) Cannot read property 'geolocation_names' of undefined
2021-06-09 18:49:25.357  - error: swiss-weather-api.0 (19183) uncaught exception: Cannot read property 'geolocation_names' of undefined
2021-06-09 18:49:25.358  - error: swiss-weather-api.0 (19183) TypeError: Cannot read property 'geolocation_names' of undefined
at Immediate. (/opt/iobroker/node_modules/iobroker.swiss-weather-api/main.js:1390:28)
at processImmediate (internal/timers.js:458:21)
2021-06-09 18:49:25.359  - error: swiss-weather-api.0 (19183) Cannot read property 'geolocation_names' of undefined
2021-06-09 18:49:25.361  - error: swiss-weather-api.0 (19183) uncaught exception: Cannot read property 'geolocation_names' of undefined
2021-06-09 18:49:25.362  - error: swiss-weather-api.0 (19183) TypeError: Cannot read property 'geolocation_names' of undefined
at Immediate. (/opt/iobroker/node_modules/iobroker.swiss-weather-api/main.js:1404:28)
at processImmediate (internal/timers.js:458:21)
2021-06-09 18:49:25.363  - error: swiss-weather-api.0 (19183) Cannot read property 'geolocation_names' of undefined
2021-06-09 18:49:25.366  - error: swiss-weather-api.0 (19183) uncaught exception: Cannot read property 'geolocation_names' of undefined
2021-06-09 18:49:25.367  - error: swiss-weather-api.0 (19183) TypeError: Cannot read property 'geolocation_names' of undefined
at Immediate. (/opt/iobroker/node_modules/iobroker.swiss-weather-api/main.js:1418:28)
at processImmediate (internal/timers.js:458:21)
2021-06-09 18:49:25.368  - error: swiss-weather-api.0 (19183) Cannot read property 'geolocation_names' of undefined
2021-06-09 18:49:25.917  - error: host.ioBroker-RasPi instance system.adapter.swiss-weather-api.0 terminated with code 6 (UNCAUGHT_EXCEPTION)
2021-06-09 18:49:25.927  - info: host.ioBroker-RasPi Restart adapter system.adapter.swiss-weather-api.0 because enabled
2021-06-09 18:49:56.031  - info: host.ioBroker-RasPi instance system.adapter.swiss-weather-api.0 started with pid 14327
2021-06-09 18:49:58.704  - info:  swiss-weather-api.0 (14327) starting. Version 0.9.5 in  /opt/iobroker/node_modules/iobroker.swiss-weather-api, node: v12.18.2,  js-controller: 3.2.16
2021-06-09 18:49:58.764  - info: swiss-weather-api.0 (14327) longitude/longitude not set, get data from system
2021-06-09 18:49:58.807  - info: swiss-weather-api.0 (14327) system  longitude: 7.375587970018386 latitude: 47.04616448019215
2021-06-09 18:51:04.325  - error: swiss-weather-api.0 (14327) uncaught exception: Cannot read property 'id' of undefined
2021-06-09 18:51:04.329  - error: swiss-weather-api.0 (14327) TypeError: Cannot read property 'id' of undefined
at IncomingMessage. (/opt/iobroker/node_modules/iobroker.swiss-weather-api/main.js:2705:16)
at IncomingMessage.emit (events.js:327:22)
at endReadableNT (_stream_readable.js:1221:12)
at processTicksAndRejections (internal/process/task_queues.js:84:21)
2021-06-09 18:51:04.330  - error: swiss-weather-api.0 (14327) Cannot read property 'id' of undefined
2021-06-09 18:51:04.348  - info: swiss-weather-api.0 (14327) cleaned everything up...
2021-06-09 18:51:04.350  - info: swiss-weather-api.0 (14327) terminating
2021-06-09 18:51:04.352  - warn: swiss-weather-api.0 (14327) Terminated (UNCAUGHT_EXCEPTION): Without reason
2021-06-09 18:51:05.072  - error: host.ioBroker-RasPi instance system.adapter.swiss-weather-api.0 terminated with code 6 (UNCAUGHT_EXCEPTION)
2021-06-09 18:51:05.075  - info: host.ioBroker-RasPi Restart adapter system.adapter.swiss-weather-api.0 because enabled
2021-06-09 18:51:35.129  - info: host.ioBroker-RasPi instance system.adapter.swiss-weather-api.0 started with pid 15999
2021-06-09 18:51:37.933  - info:  swiss-weather-api.0 (15999) starting. Version 0.9.5 in  /opt/iobroker/node_modules/iobroker.swiss-weather-api, node: v12.18.2,  js-controller: 3.2.16
2021-06-09 18:51:37.992  - info: swiss-weather-api.0 (15999) longitude/longitude not set, get data from system
2021-06-09 18:51:38.026  - info: swiss-weather-api.0 (15999) system  longitude: 7.375587970018386 latitude: 47.04616448019215
2021-06-09 18:52:43.790  - error: swiss-weather-api.0 (15999) uncaught exception: Cannot read property 'id' of undefined
2021-06-09 18:52:43.794  - error: swiss-weather-api.0 (15999) TypeError: Cannot read property 'id' of undefined
at IncomingMessage. (/opt/iobroker/node_modules/iobroker.swiss-weather-api/main.js:2705:16)
at IncomingMessage.emit (events.js:327:22)
at endReadableNT (_stream_readable.js:1221:12)
at processTicksAndRejections (internal/process/task_queues.js:84:21)
2021-06-09 18:52:43.796  - error: swiss-weather-api.0 (15999) Cannot read property 'id' of undefined
2021-06-09 18:52:43.820  - info: swiss-weather-api.0 (15999) cleaned everything up...
2021-06-09 18:52:43.821  - info: swiss-weather-api.0 (15999) terminating
2021-06-09 18:52:43.824  - warn: swiss-weather-api.0 (15999) Terminated (UNCAUGHT_EXCEPTION): Without reason
2021-06-09 18:52:44.508  - error: host.ioBroker-RasPi instance system.adapter.swiss-weather-api.0 terminated with code 6 (UNCAUGHT_EXCEPTION)
2021-06-09 18:52:44.511  - info: host.ioBroker-RasPi Restart adapter system.adapter.swiss-weather-api.0 because enabled
2021-06-09 18:52:44.512  - warn: host.ioBroker-RasPi Do not restart adapter system.adapter.swiss-weather-api.0 because restart loop detected

done


nestedScrollEnabled

I added the nestedScrollEnabled property to the ScrollView of the BarChart to enable nested scrolling. This is useful when the BarChart is used inside a horizontal ScrollView, as without this property, the chart's scrolling is compromised.

Hi @PellegriniGuilherme
Thanks for this valuable contribution.
Please undo the unnecessary reordering of import statements in your PR and please don't push the yarn.lock file.
Once you make these changes in your PR, I can merge it.

All changes have been made. Thank you!


Flutter: Introduction to DART - Video

A video to understand dart programming language.
(It should cover live implementation of topics)
It should cover all the basics and some advanced topics of DART, and maybe sections can be divided into several contributors.
Those who want to contribute can comment on the topics they would like to cover in thier video.
Topics to cover:

Dart Variables
Dart Data Types
Dart Functions
Dart Arrow Function
Dart Lists
Dart Conditionals
Dart classes and objects
Dart Class constructors
Any other topics that you may find useful

References:
Dart: https://dart.dev/

I am interested in this. I can cover the explanation part, but will i have to handle the video editing as well.?

I am interested in topics from 1 - 4.

i am intrested in contributing for topics 5 -8

@sunny7898 @rithish26 have you both completed the video part?

@ViAsmit  Sorry for the inconvenience, but I wont be able to complete this. I am running linux on my system, and have been trying to rectify the mic input quality from few days. So I request you to reassign it to somebody else.

@sunny7898 Ok No Problem... Have you tried simplescreenrecorder? I am also a linux user.. I usually use this application.

@ViAsmit Actually I use Bluetooth headsets, and the problem is because of the audio profile its been using. I have tried to configure it, but its not working yet.

Will be taking the issues from 1-5

@arcAman07 have you been able to complete this issue?

@ViAsmit can you assign me topic 1-6

@apprenant-jd00  I think topics 5-8 are already completed. see that video, and add only those topics which haven't been covered yet. I have assigned to you

@ViAsmit I found only documentations and not the video. Can you provide the link of contributions made on video

@apprenant-jd00 ..yeah I think video part is not done for any part of this topic .. ok then..you can take any topics...
OR will you able to take all the topics..and make two videos? If possible...
Or if you can't...then you can work on any part you like...

@ViAsmit I'll take topics 1-6

@ViAsmit Is there anything which is left in the above-mentioned topics?


Files/Blobs are not getting returned in Action

getValidatedFormData is not returning the file data.
{
  firstName: 'Jack',
  lastName: 'Sparrow',
  screenName: 'sparrow1',
  profileImage: { '0': {} } // No blob/file data
}

Issue is here: https://github.com/Centerworx/remix-hook-form/blob/d082e1d0e7929451505db9ac0519952860d56bc4/src/utilities/index.ts#L49
FormData Blob/FIles are not handled. JSON cannot hold a file.
formData.set(pathString, blob) or  formData.set(pathString, blob, filenameString)

you can use react-hook-form set function to do this.
import { set } from "react-hook-form";

set(
  object: FieldValues, // in your case currentObject
  path: string, // formData key
  value?: unknown, // formData blob
)

With this set function you can eliminate all the string parsing and conversion you are doing in "generateFormData" it would just become the below:
/**
 * Generates an output object from the given form data, where the keys in the output object retain
 * the structure of the keys in the form data. Keys containing integer indexes are treated as arrays.
 *
 * @param {FormData} formData - The form data to generate an output object from.
 * @param {boolean} [preserveStringified=false] - Whether to preserve stringified values or try to convert them
 * @returns {Object} The output object generated from the form data.
 */
export const generateFormData = (
  formData: FormData,
  preserveStringified = false,
) => {
  // Initialize an empty output object.
  const outputObject: Record<any, any> = {};

  // Iterate through each key-value pair in the form data.
  for (const [key, value] of formData.entries()) {
    if (value instanceof Blob || toString.call(value) === "[object Blob]") {
        set(currentObject, key, value)
        continue;
    }

    // Try to convert data to the original type, otherwise return the original value
    const data = preserveStringified ? value : tryParseJSON(value.toString());

    set(currentObject, key, data)
  }

  // Return the output object.
  return outputObject;
};

The only issue with using react-hook-form set function is it will not use empty [] in keys urlSearchParams or dotKey syntax. You can use my "cleanArrayStringKeys" function to allow for empty [] or remove those test to conform to react-hook-form standards, you could even throw an error if there is an empty [].
/**
 * cleanArrayStringUrl - This is a Fix for react-hook-form url empty [] brackets set conversion,
 * react-hook-form will not load array values that use the empty [] keys.
 *
 * This utility will add number keys to empty [].
 *
 * Note: empty url arrays and no js forms don't seam to be very popular either.
 *
 * @param {string} urlString
 * @returns {string}
 */
export const cleanArrayStringKeys = (urlString: URLSearchParams) => {
  const cleanedFormData = new URLSearchParams();
  const counter = {} as Record<string, number>;

  for (const [path, value] of urlString.entries()) {
    const keys = path.split(/([\D]$\[\])/g);
    // early return if single key
    if (keys.length === 1 && !/\[\]/g.test(keys[0])) {
      cleanedFormData.set(keys.join(""), value);
      continue;
    }

    const cleanedKey = [] as string[];

    // adds indexes to empty arrays to match react-hook-form
    keys.forEach((key) => {
      key = key.replace(/\.\[/g, "[");
      counter[key] = (counter[key] === undefined ? -1 : counter[key]) + 1;

      cleanedKey.push(key.replace(/\[\]/g, () => `[${counter[key]}]`));

      // merge array keys back into path
      const cleanedPath = cleanedKey.join("");

      cleanedFormData.set(cleanedPath, value);
    });
  }

If you don't want to simplify your code, you can just add this to "tryParseJSON", this should do the trick, but should be tested:
 tryParseJSON= (jsonString) => {
  if (jsonString === "null") {
    return null;
  }
  if (jsonString === "undefined") {
    return void 0;
  }
  if (jsonString instanceof File || jsonString instanceof Blob) { // new check before JSON.parse
    return jsonString;
  }

on a side note: value instanceof Blob -> Some node servers (<16, It can be imported in 16+) may not have access to Blob and so it could break some projects. See ref: https://stackoverflow.com/questions/14653349/node-js-cant-create-blobs#:~:text=41-,Since Node.js 16,-%2C Blob can

@AlemTuzlak See above.

The issue here is that you can't parse files from request.formData(), you have to use Remix unstable_parseMultiPartFormData. You get the streamed data from the frontend there and you can return it to your action however you like, I wrote an article explaining how yo ucan upload your images to supabase and return paths here:
https://alemtuzlak.hashnode.dev/uploading-images-to-supabase-with-remix
Although this set helper seems really interesting, is there a doc page anywhere on how it works?


ID360 calls do not work on IOS

they are ok on android

1.14.2 IOS, it does not open the browser

1.14.3 same issue on IOS


Adding @adhoc

https://experimental-site-testing-only.github.io/language-common/attributes/

Great, thanks!


stardist segmentation

Open ToDos:

[ ] document that normalize is required for stardist
[ ] https://github.com/theislab/squidpy/issues/328
[ ] have parameters in normalize in segment directly

was just checking out the notebooks out of curiosity, looks really promising imho!

also: how did you install stardist? I've followed the hints on using CC=gcc-10 CXX=g++-10 pip install stardist for Mac, but no luck so far.

sorry just jumping on this, would be good to always make an environemnt.yaml file for installing the full env with conda, for reproducibility (what we have now for all external tutorials).I think a separate env per tutorial is fine?

sorry just jumping on this, would be good to always make an environemnt.yaml file for installing the full env with conda, for reproducibility (what we have now for all external tutorials).I think a separate env per tutorial is fine?

that's a good point! So you would have environment_tangram.yml, environment_cellpose.yml, etc, right? And inside this, you'd always require squidpy and any other external tools that you need. And then we could just link this environment file in the tutorials.

Yes exactly! This would make each tutorial self contained and the user could install only a minimal env (if wants to try cell pose, no need to have tangram installed)

This look really impressive, great that you got it to work even for H&E stain! This looks a bit better than our watershed approach! I looks like it is still missing some cells though, is that related to the prob_thresh parameter?

yes, thats related to the prob_thresh parameter and I just followed their best parameter for H&E.

What is the complete_img parameter in stardist_3D_versatile_hne doing? Is it not possible to just use crop/img? If you bypass the img parameter like this, chunking won't work properly anymore I believe?

this was a quick fix. this is resolved now as @michalk8 allowed channel=None as stardist segmentation works on multiply channels. I will adjust this and remove this additional complete_img param. will push an update later today.

I'd love for this to be part of squidpy_notebooks as well (as an external tutorial - meaning it will go in docs/source/external_tutorials).

will add!

For this, some explanatory text would be good. Essentially just explaining the functions that you define, and how you are setting the parameters; similar to #11 . Also, a citation + link to the stardist code would be needed.

saw this already and keep a similar structure to this matches!

We can edit this here, or directly over at https://github.com/theislab/squidpy_notebooks . Have a look at the contributing guide for some hints to how the formatting should be done: https://github.com/theislab/squidpy_notebooks/blob/master/CONTRIBUTING.rst#external-tutorials

also: how did you install stardist? I've followed the hints on using CC=gcc-10 CXX=g++-10 pip install stardist for Mac, but no luck so far.

I just used pip install stardist and it worked like a charm. I think CC=gcc-10 CXX=g++-10 pip install stardist is required if installation failed. I just created a new repo with only squidpy, tensorflow and stardist and it worked

this was merged in squidpy_notebooks


Ionic2 - Show/Hide button based how the controller was shown

I have a page Page 2 which needs to be open sometimes using a modal() and sometimes using a push().
In the normal scenario, if the controller is opened using a push method it will show a "Back" button. However, in the other scenario which is opening the page using a modal() method, I need to add a close button to Page 2 so the user can dismiss that controller at any time.
The Problem
If I add a close button to Page 2 then that button shows even if the controller was opened using a push() method and in this case it shows a back button and a close button.
What I want
I want to add a condition, in which if the controller was opened using push(), then it should hide that close button
The flow:
Page 1 > (Push to) > Page 2 (Hide the close button)
Page 3 > (Modal to) > Page 2 (Show the close button)

Hello! Thanks for opening an issue with us! As this seems like more of a support question of how to implement certain functionality i will urge that you ask this question on our forum (forum.ionicframework.com). Thanks for using Ionic!


git add --renormalize .

Hopefully the last diff with a ton of line-ending changes
With hidden whitespace changes: https://github.com/lunet-io/markdig/pull/426/files?diff=split&w=1

Han didn't know about this new --renormalize command, cool, thanks!

I just found out about it from https://github.com/microsoft/reverse-proxy/pull/35


on-the-fly doesn't decode messages with nested repeating groups correctly

using an SBE template which contains a single repeating group which itself contains three repeating groups the message does not decode properly when using the on-the-fly decoder
in the decodeGroups method the end group index is being set incorrectly. it is currently being found by simply looking for the next occurrence of an end group token. in the case of nested repeating groups this will happen to be the the end group token of one of the inner groups and not the end group token for the group for which start was just called. this will only be observed when decodeGroups was called recursively from within the decoding of a parent group. once the lower value is returned and the blocks in the repeating group have all been decoded the index on which token is to be processed will be lower than expected and some repeating groups will attempt to be decoded at the message level. note that there needs to be more than one nested repeating group for the end group index to come back lower than intended.
a fix could be in the findNextOrLimit method - instead of just looking for the first end group token and returning it should look for the end group token of the group for which start group was called

I assume this is from an older version of SBE? We believe this bug was fixed with the migration to RC3.  See https://github.com/real-logic/simple-binary-encoding/issues/230

Yes - this was found with RC2. Is the RC3 decoder backward compatible with RC2? Our systems currently use RC2 extensively and do not have any current plans to move to RC3.

The wire protocol is backwards compatible. The API has evolved based on what we learned from usage and also to support integration with Aeron.


Change the login photo to tech cell

Tech cell is asserting dominance. This cannot be negotiated.
Resolves #384
[Demo PR]

Closing this before I get in trouble.


feat: Use Plus Jakarta Sans as the default font

Hi everyone,
In the design, Plus Jarkarta Sans is the font used by default.
This PR switches all the app to it.

Codecov Report

Merging #4361 (e563e73) into develop (899cea6) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff            @@
##           develop    #4361   +/-   ##
========================================
  Coverage    10.45%   10.45%
========================================
  Files          291      291
  Lines        14416    14416
========================================
  Hits          1507     1507
  Misses       12909    12909

Impacted Files
Coverage Δ

packages/smooth_app/lib/themes/smooth_theme.dart
76.08% <ø> (ø)

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more

We reverted in the past because it doesn't work for all locales

We reverted in the past because it doesn't work for all locales

Do you have the issue related to this?
Because Roboto is kind of boring - we could maybe use the font only on supported locales

Here is a list of unsupported langagues:
 // Adyghe, Avaric,Azerbaijani (Cyrillic),Bosnian (Cyrillic),Bulgarian
    //Chechen,Chuvash,Dargwa,Erzya,Evenki,Gagauz, Cyrillic,Interlingua,
    // Kabardian,Karachay-Balkar,Khakas, Komi, Komi-Permyak, Kumyk, Kurdish
    //Lak,Lezghian,Macedonian,Mari,Modern Greek,Moksha,Mongolian,Nanai,Nenets,
    // Ossetic,Romanian, Cyrillic,Russian,Russian Buriat,Rusyn,Sakha,Shor,
    // Southern Altai,Udmurt,Ukrainian,Western Mari

We should tell to revert to Roboto for them

Here is a list of unsupported languages:

@g123k Keep in mind the maintainability. If reaaaaally you don't like the default font, please find a different font that works for all languages. If not, I would suggest you to close this PR.

Here is a list of unsupported languages:

@g123k Keep in mind the maintainability. If reaaaaally you don't like the default font, please find a different font that works for all languages. If not, I would suggest you to close this PR.

Actually, even Roboto doesn't support all languages.
Jakarta supports languages that Roboto doesn't and vice-versa.

Roboto: ✅ Good European Support, 🔴 Generic
Plus Jakarta Sans: 🔴 Poor European Support, ✅ Matches our brand identity
Risk: showing a Russian/Greek products in the French app. We'd need to make a potentially complex exception.
https://fonts.google.com/specimen/Roboto/glyphs?query=roboto
https://fonts.google.com/specimen/Plus+Jakarta+Sans/glyphs?query=plus+jakarta+sans

It seems that we ended up using Public Sans on the web: https://fonts.google.com/specimen/Public+Sans: https://github.com/openfoodfacts/openfoodfacts-server/blob/8034910890ecd9c54cc39a360791ace6cbbf83e6/scss/_off.scss#L6

I close this PR, as a real plan B is to use a real universal font.
Even if we use Roboto, it doesn't implement all the languages we need


multiple registry

It's is possible to publish the package on several repositories ? (ex: gitlab + aws ecr)

That's not possible at the moment

Should not even be that hard to support, if you check the logic here
https://github.com/nflaig/semantic-release-helm/blob/c14843dbb91ff34ce803f8cf640b256610733c83/lib/publish.js#L11-L27
All that has to be done is not use if-else and just do multiple publish if multiple options are specified


Bumping go version to 1.19.6 in 0.43.x line

Bumping go version to 1.19.6 in 0.43.x line

1.19.7 is the latest version; should it be bumped to that one instead?

go1.19.7 (released 2023-03-07) includes a security fix to the crypto/elliptic package, as well as bug fixes to the linker, the runtime, and the crypto/x509 and syscall packages. See the Go 1.19.7 milestone on our issue tracker for details.

LGTM

1.19.7 is the latest version; should it be bumped to that one instead?

go1.19.7 (released 2023-03-07) includes a security fix to the crypto/elliptic package, as well as bug fixes to the linker, the runtime, and the crypto/x509 and syscall packages. See the Go 1.19.7 milestone on our issue tracker for details.

Hey @kencochrane. Thanks for calling that out. It's a legitimate question.
There's a number of concerns that get folded into selecting a specific dependency (even the version of Go we use). We have the desire to keep the suite in sync on Go version. It's currently some effort to produce new releases for all the tools and any downstream work that the VMware folks are also responsible for.
So, we'll pick a version and trigger a release.  Right now, sometimes that means not getting the absolute latest.
We're investing in our overall automation and making this effort shorter/cheaper. When we get to where we want to be, yeah, we'll be able to consume dependencies at will — as we'd all hope.
Again, thanks for the review; it's great to know folks are looking out, here. 👍🏻

It's my understanding that we are — whenever possible — making such changes on develop and then cherry-picking into version branches.
From what I'm seeing this change is not yet on develop.
Do I have my wires crossed? Or are we all still sync'ing up on this intended practice?

@pivotaljohn Thank you for explaining that, and I totally get where you are coming from. I mainly brought it up because there are known security issues with 1.19.6 that are fixed in 1.19.7, and I thought since it requires work to bump the version anyway, it might be a good idea to use a version of go with no known security vulnerabilities.
When Go binaries are built with a version of Go that has known security vulnerabilities, it triggers security alerts on containers that contain those binaries. If companies want to stay in compliance, they have to fix those scan alerts within 30 to 90 days (depending on the CVE severity). Bumping to 1.19.7 would help those companies clear those alerts in their SLA window without needing another release.
It's your project, so feel free to do what is best. I just wanted to give a little heads-up in case it would have saved you time without having to do the whole process twice (with 1.19.6 and then again with 1.19.7).
Thanks again!


Please change the method of extending ki to fn like in jquery

I suggest you provide a method of extending ki like in jquery
$.fn.text = function() {}
That way it's easy to swap with jquery.

this is already supported. https://github.com/dciccale/ki.js/blob/master/ki.js#L27


Make input output consistency

Pull Request Test Coverage Report for Build<PHONE_NUMBER>1
Details

0 of 0   changed or added relevant lines in 0 files are covered.
36 unchanged lines in 1 file lost coverage.
Overall coverage increased (+0.05%) to 64.633%

Files with Coverage Reduction
New Missed Lines
%

input.py
36
76.85%

Totals

Change from base Build<PHONE_NUMBER>2:
0.05%

Covered Lines:
519

Relevant Lines:
803

💛  - Coveralls


monetdb: 11.35.19 -> 11.37.7

Semi-automatic update generated by nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/monetdb/versions.
meta.description for monetdb is: "An open source database system"
meta.homepage for monetdb is: "https://www.monetdb.org/"
meta.changelog for monetdb is: ""
Updates performed

Version update

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS

The tests defined in passthru.tests, if any, passed

0 of 0 passed binary check by having a zero exit code.

0 of 0 passed binary check by having the new version present in output.

found 11.37.7 with grep in /nix/store/wqpwqazqs6qmlym90g55a4dwsyhg32kh-monetdb-11.37.7

directory tree listing: https://gist.github.com/bb60bba0ab49a5788ab19bce93175647

du listing: https://gist.github.com/b3f507c73557004af33745bbd9a8ed15

Rebuild report (if merged into master) (click to expand)

4 total rebuild path(s)

1 package rebuild(s)

1 x86_64-linux rebuild(s)
1 i686-linux rebuild(s)
1 x86_64-darwin rebuild(s)
1 aarch64-linux rebuild(s)

First fifty rebuilds by attrpath
monetdb

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/wqpwqazqs6qmlym90g55a4dwsyhg32kh-monetdb-11.37.7 \
  --option binary-caches 'https://cache.nixos.org/ https://r-ryantm.cachix.org/' \
  --option trusted-public-keys '
  r-ryantm.cachix.org-1:gkUbLkouDAyvBdpBX0JOdIiD2/DP1ldF3Z3Y6Gqcc4c=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(r-ryantm's Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A monetdb https://github.com/r-ryantm/nixpkgs/archive/4ae1d1b3bbad9ab056af06f4272a875eac368075.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/wqpwqazqs6qmlym90g55a4dwsyhg32kh-monetdb-11.37.7
ls -la /nix/store/wqpwqazqs6qmlym90g55a4dwsyhg32kh-monetdb-11.37.7/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review 1

1 package built:
- monetdb

Maintainer pings
cc @StillerHarpo for testing.

All binaries are working.


chore: Corrected analytics event for instance setting events

Description
Minor changes in the way analytics events are sent for instance setting updated events
Type of change

New feature (non-breaking change which adds functionality)

How Has This Been Tested?

Locally

Checklist:

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes

/ok-to-test sha=56160610b4796b6f998075fe9b8d08f278397ee2


test: module to parse key input

It is unfinished, but will prove useful for
supporting configurable keybinds.
There's a lot of boilerplate in the tests that it'll help solve. So starting there.

Codecov Report
Attention: Patch coverage is 98.38710% with 1 lines in your changes are missing coverage. Please review.

Project coverage is 88.32%. Comparing base (699b133) to head (aad5cbb).

Files
Patch %
Lines

src/tests/helpers/ui.rs
85.71%
1 Missing :warning:

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff             @@
##           master     #109      +/-   ##
==========================================
+ Coverage   88.21%   88.32%   +0.11%
==========================================
  Files          41       42       +1
  Lines        3885     3933      +48
==========================================
+ Hits         3427     3474      +47
- Misses        458      459       +1

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


Bump v0.17.2

Remove the release argument from execute_macro. Everything worked fine with or without it. While I left it in, I saw the deprecation warning:
* Deprecation Warning: The "release" argument to execute_macro is now ignored,
and will be removed in a future relase of dbt. At that time, providing a
`release` argument will result in an error.

Leaving as a draft until we release dbt v0.17.2.

This is good. I'd like to change get_catalog and _get_one_catalog to use submit_connected, which would bring it more in-line with core, but I think that's a purely cosmetic issue at least for spark (possibly for get_catalog as a whole).

@beckjake Sorry I lost track of this. Is that a change you want to make for 0.17.2, or to include as part of reworking for 0.18.0?

I don't have strong feelings either way, as long as we get to it! Happy to just ship 0.17.2 as-is.

Keeping this quick-and-simple for now


Cannot find module 'tweetnacl'

src/lib/SignInMessage.ts:2:18 - error TS2307: Cannot find module 'tweetnacl' or its corresponding type declarations.

2 import nacl from 'tweetnacl';

We missed doing yarn ig XD, Thanks for fixing it @Code-Parth


Blazor — System.Text.Json and JsonConverter

I have found more or less related issue:

https://github.com/aspnet/AspNetCore/issues/12685
https://github.com/aspnet/AspNetCore/pull/10171
https://github.com/aspnet/AspNetCore/issues/10404
https://github.com/aspnet/AspNetCore/issues/14254

As Blazor should no more use SimpleJSON but System.Text.Json  by default, I should be able to use custom JsonConverter<T> by configuring Blazor But I find nothing on how to use custom JsonConverter<T> inside Blazor…
For now I use extensions methods, but I am looking for some configurations inside the Startup class:
public class Startup
{
    public void ConfigureServices(IServiceCollection services)
    {
    }

    public void Configure(IComponentsApplicationBuilder app)
    {
        app.AddComponent<App>("app");
    }
}

Where can I get any information about this? Is there any such configuration available through services ?

@vintzl at this point Blazor does not have any extensibility to configure serialization globally. The best you could do is to decorate types with JsonConverterAttribute and author custom converters to manage seriaization on a per-type basis.
https://github.com/aspnet/AspNetCore/issues/12685 tracks further improvements in this area.


Feature: Event Organizer Panel

Issue Description:
Creating an Event Organizer Panel is essential to provide a dedicated and efficient platform for event organizers to manage their events, participants, and related tasks. This feature will empower event organizers with the tools and capabilities to ensure successful event planning and execution.
Issue Details:
1. Problem Statement:
Currently, our application needs a dedicated interface or platform for event organizers. Event organizers need a centralized platform to create, manage, and monitor events, which can lead to inefficiencies and challenges in event planning and execution.
2. Objectives:

Develop an Event Organizer Panel to provide a user-friendly interface for event organizers.
Enhance the efficiency and effectiveness of event planning and management.

3. Benefits:

Improved event planning and execution through a dedicated organizer interface.
Streamlined event management processes for organizers.
Enhanced user experience for event organizers.
Increased participant engagement and satisfaction.

4. Proposed Tasks:

Design and develop the Event Organizer Panel interface with Authentication.
Define the functionalities and features accessible to event organizers in the panel.
Test the Event Organizer Panel thoroughly to ensure functionality and user-friendliness.

5. Acceptance Criteria:

The Event Organizer Panel is successfully designed and implemented.
Event organizers can access and use designated functionalities for event management.
The panel provides a user-friendly and efficient experience for event organizers.
Event organizers can create, edit, and monitor events.

do u have any design file or a basic wireframe/structure for this issue ?
i can work on this issue

Hey, you can design a basic responsive organiser panel from a very basic design according to you. Make sure it meets the requirements and clean modular code.


Remove log4j-kubernetes module

The log4j-kubernetes module is problematic, because:

the kubernetes-model-core dependency follows Kubernetes lifecycle. It might be (and it already occurred) that breaking changes occurred on a minor version change,
on the other hand it depends only on StrLookup, which is unlikely to ever change,
the Fabric8 team has a better idea, which properties could be interesting to users.

Therefore if fabric8io/kubernetes-client#5718 is accepted, I propose to remove log4j-kubernetes from our codebase.

An improved kubernetes-log4j module is available since Kubernetes Client version 6.11.0 (cf. announcement), therefore we can remove log4j-kubernetes.


Allow operator to install resources to WATCH_NAMESPACE instead of requiring keda ns

Currently the KEDA OLM operator is hard-coded to work only in the keda namespace.
This change makes it so that whichever namespace the KEDA operator is installed to,
the operands (and required resources) will be installed to the same namespace.
The fundamental difference:
Before:

The operator could be installed in any namespace
The kedacontroller custom resource could only be installed in the keda namespace.
The operand controllers and necessary resources were always installed (by the operator) in the keda namespace.

After:

The operator can be installed in any namespace
The kedacontroller custom resource can only be installed in the same namespace where the operator is installed.
The operand controllers and necessary resources are always installed (by the operator) in the namespace where the operator is installed.

Checklist

[X] Commits are signed with Developer Certificate of Origin (DCO)
[x] Add tests for transform function
[x] Update docs to explain the new behavior

@zroubalik thanks for the review! I had a few final tasks which are now done. (I renamed a variable as suggested by your review comment, I switched the unit tests to use ginkgo to get rid of a CI test error, and I updated the docs to match the new behavior.)
If you have time for a final review, that would be great. If not, I can have somebody from my team review it -- now that I know you're okay with the general approach.


Feature request: make core extensions (monkey patches) optional

What would you say to making it possible to use word_wrap without it monkey patching String?
Background: I prefer to avoid, or at least minimize, gems that monkey patch core classes.  It can get ugly in a hurry as the program grows and starts including other libraries that also monkey patch core classes.
I can think of a few ways to go, if you wanted to allow this.  One would be to make the monkey-patch be omitted by:
require 'word_wrap'

and put into a piece you could require separately, if you wanted it:
require 'word_wrap/core_extensions'

This is a breaking API change.  The other way, which is not a breaking API change, is to make the monkey patch be included, as it is now, by:
require 'word_wrap'

But omitted by, for example:
require 'word_wrap/core'

What do you think?  Good idea?  If so, how would you like it to work?

Hi Wayne,
I see you point. It makes sense to keep the core_extensions separate, I haven't really thought that through all that well. I'd go with your first suggestion, even though it breaks the current interface. It seems like a right thing to do.

Sounds good.  If you like, I'll cook up a pull request.

This should be addressed in 1.0.0.
Core extensions are omitted by default and can be added using:
require 'word_wrap/core_ext'

Thanks @wconrad!


[ios] Not receiving notifications at all.

RN: 0.37
react-native-fcm: 2.3.3
iPhone 6  iOS10
Running in foreground and background
I'm not really sure what I'm doing wrong here but I'm not getting any notifications altogether.
Anyone having a project, which is working in the sense of receiving notifications sent from FCM control panel, laying about and is interested in sharing it for pointers in which direction Should go to make it work at all?

can you investigate by

try native firebase cloud messaging example to make sure you've set up certificates correctly?
make sure you have requested permission before receiving notification?
curl to fcm api endpoint with specific fcm token and check their response error?

close due to inactivity


lp Features

Personally suggest adding a function that can increase the limited time inheritance time. I believe this function will be very popular. The function means that it can increase the time from the original time.

You can already achieve this by adding accumulate after the duration in the addtemp command, see the [temporary modifier] argument in the parent addtemp command page :)

That one. . . . . Can you give me a specific example how to write.

Already understand, thank you for your confusion


IS_MEMBER does work for Azure AD groups.

The docs state that IS_MEMBER does not work for AAD groups. However, I have been able to get this to work.
You have to add any group you want to check for membership as a contained user and then IS_MEMBER works as expected. Am I missing something?

@toddkitta -- thank you for your feedback.  You appear to be on the right track.
@VanMSFT -- please look into this issue.

Hi @GithubMirek - Is this something you can help check? Thanks!
https://docs.microsoft.com/en-us/sql/t-sql/functions/is-member-transact-sql?view=sql-server-ver15
#reassign:GithubMirek

The AAD/SQL product group is in the process of completing and testing this functionality. It should be publicly available toward the end of Q1 2021 (CY).

The AAD/SQL product group is in the process of completing and testing this functionality. It should be publicly available toward the end of Q1 2021 (CY).

to is not a valid GitHub ID, or is not a collaborator on this repo.

to is not a valid GitHub ID, or is not a collaborator on this repo.

Thanks @GithubMirek!
@toddkitta - Thanks for bringing this issue up. We will track this internally and make the necessary doc changes as needed. I will close this issue for now, but please feel free to let us know if you have any concerns.

Thanks @GithubMirek!
@toddkitta - Thanks for bringing this issue up. We will track this internally and make the necessary doc changes as needed. I will close this issue for now, but please feel free to let us know if you have any concerns.


Custom plugins not properly handled if authentication is enabled

Because the addCustomPlugins() function is only called once after initially loading the (incomplete) config, custom plugins appear to a logged in user only after refreshing the page. Similarly, they stay put after logging out until the page is refreshed again.

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

GitHub release
v6.15.1

Your semantic-release bot :package::rocket:


Speaker button in menu bar should reflect state of volume

Even if the volume is at 0% or muted, it shows little waves coming out of the speaker. It would be good if the icon reflected more accurately the volume level of the machine.

Oops, this should definitely be addressed.

This is now available.


ci: retry flaky tests

related #9492
Description
This updates the CI test jobs to use retry.sh, which reruns the given command (up to 3 times by default) if its output contains one of the errors indicated in #9492. I picked 3 for the default retry count because in my experiments, the same error can appear twice in a row.
The script also adds a warning annotation to the GitHub workflow run to easily identify the flakiness from the Summary view:

This script can be run locally like this:
# retry 3 times
./scripts/retry.sh "pnpm --color=always test"

# retry 5 times
./scripts/retry.sh "pnpm --color=always test" 5

Testing retry.sh
Here's a script that runs pnpm --color=always test-build 10 times in a row, which causes one of the known errors in Node 16:
#!/usr/bin/env bash -e

for i in `seq 10`; do
  echo "************* test run ${i} *************"
  ./scripts/retry.sh "pnpm --color=always test-build"
done

(Tested on macOS Big Sur with Node 16.16.0)
Screenshot:

Additional context

What is the purpose of this pull request?

[ ] Bug fix
[ ] New Feature
[ ] Documentation update
[x] Other

Before submitting the PR, please make sure you do the following

[x] Read the Contributing Guidelines.
[x] Read the Pull Request Guidelines and follow the Commit Convention.
[x] Check that there isn't already a PR that solves the problem the same way to avoid creating a duplicate.
[x] Provide a description in this PR that addresses what the PR is solving, or reference the issue that it solves (e.g. fixes #123).
[ ] Ideally, include relevant tests that fail without this PR but pass with it.

not a fan of a bash script wrapper in general

hard to maintain
breaks easily
potentially abusable if someone snuck in output that it is looking for

other remarks

ci timeout for the job would need to be increased
really love the warning annotation, going to add that one to my toolbox :+1:
instead of working around it, we should put more preassure on upstream to fix it. random crashes are not acceptable

@dominikg Thanks for the feedback!
I did actually experiment with a Node/zx script, but the startup speed with the shell script seemed superior to me. But points taken, I can switch from shell script to TypeScript to address your concerns.
I also agree with pushing for an upstream fix, but it doesn't look like the Node team is anywhere close to a fix, and they're not sure the fix is even feasible:

@bnoordhuis commented on Jun 29
For reference: the fix is v8/v8@fcdf35e but that commit can't be back-ported because it sits on top of a bigger, backwards incompatible change, v8/v8@578f6be.

For the time being, an automated retry seems like a reasonable workaround to keep the builds going without babysitting them. I'm completely open to other ideas though!

Looks great!
A side note, I guess it might be good to create a CLI wrapper like vitest-retry for others to reuse. Or even we could have it built-in in Vitest's CLI, (cc @sheremet-va WDYT?)

Or even we could have it built-in in Vitest's CLI, (cc @sheremet-va WDYT?)

Sure, something like --segfault-retry? We have an issue for .flaky and --retry 3 for regular tests, so I don't want to use it for this case.

@antfu @sheremet-va Yes, please! 😄 A native vitest fix would be so helpful! Let me know if I could help.

A flag on vitest bin makes it reusable which is great!
Not sure how i feel about it being enabled by default, tbh i havn't seen this segfault happening in vite-plugin-svelte suite (which is a bit smaller but uses the same setup as vite).
It should be something users conciously opt-in to, so as they are aware of it. If it is enabled and can detect github action event to log the warning card, that would be awesome.

https://github.com/vitest-dev/vitest/releases/tag/v0.22.0
Shipped as Vitest v0.22.0.
Could provide as env: https://github.com/vitest-dev/vitest/blob/8f24c2f65e436aa98a9e1c77eddf5d082c2ca60d/.github/workflows/ci.yml#L12-L13

Node published a v16 fix in 16.17.0. I verified using that version eliminates the segfaults in CI.


Remove unnecessary files from docker container

The container is unnecessarily cloning thee blawx repo to get access to the source files for the documentation. Dockerfile should copy them in instead.

This will not be relevant in the v1 branch.


Differing behavior between Aead.[encrypt|decrypt] vs DeterministicAead.[encrypt|decrypt]Deterministically when passing null for additionalData

I've been encrypting values with Google Tink successfully using AES256_GCM, and was passing in null for the additionalData parameter in encrypt/decrypt for Aead (i.e. encrypt(clearBytes, null);).
Some things have come up and now I need to use DeterministicAead (AES256_SIV).  Calling encrypt/decrypt Deterministically while passing in null parameter to additionalData (i.e. encryptDeterministically(clearBytes, null) results in a NullPointerException:
java.lang.NullPointerException
	at com.google.crypto.tink.subtle.AesCmac.computeMac(AesCmac.java:77)
	at com.google.crypto.tink.subtle.AesSiv.s2v(AesSiv.java:78)
	at com.google.crypto.tink.subtle.AesSiv.decryptDeterministically(AesSiv.java:139)
	at com.google.crypto.tink.daead.DeterministicAeadFactory$1.decryptDeterministically(DeterministicAeadFactory.java:100)
...

I think it has to do with the fact that com.google.crypto.tink.subtle.AesSiv has a method private byte[] s2v(final byte[]... s) that doesn't handle the null from [encrypt|decrypt]Deterministically for additionalData.
This is how it's handled in com.google.crypto.tink.subtle.AesGcmJce, for example:
if (associatedData != null && associatedData.length != 0) {
    cipher.updateAAD(associatedData);
}

The method works as expected when passing new byte[0] in for additionalData.
There's not really any contract from the methods that they should accept null values so it might not be actually considered a bug.  But, it was taking me some time to figure out why it wasn't possible to just replace Aead with DeterminisiticAead everywhere, and thought that having consistent behavior would be worth raising the issue.

Thanks for reporting this bug.
Could you please send a PR to fix it? I think it's relatively simple and you've already figured out the root cause.
Thanks again!

Fixed by #287.


Create docker-publish.yml

Github actions provided docker-publish workflow.

Closed in lieu of #3 .


[zh] Update reference\glossary (4)

Update about reference/glossary,this chapter is often used, so make adjustments.
the following
content/zh-cn/docs/reference/glossary/cloud-controller-manager.md
content/zh-cn/docs/reference/glossary/cloud-provider.md
content/zh-cn/docs/reference/glossary/cluster-architect.md
content/zh-cn/docs/reference/glossary/cluster-infrastructure.md
content/zh-cn/docs/reference/glossary/cluster-operations.md

Signed-off-by: ydFu<EMAIL_ADDRESS>

Please ensure all these files were still in sync with English upstream.

/approve

/lgtm


[V2] camelCased properties are not working the same in 2.0

Working on potentially moving polished over to using camelCased properties (https://github.com/styled-components/polished/issues/167) and in testing with 2.0 discovered that this seems to no longer be working the same way it did in V1.
They work when passed as objects within the string interpolation, but previously they worked without needing to be in an object.
Is this an intentional change we should be aware of?
Version
2.0.0-17
Reproduction
Doesn't work in 2.0.0-17: https://www.webpackbin.com/bins/-Kk-yp0vQFWgMO9gRTd0
Works in 2.0.0-17 (as object): https://www.webpackbin.com/bins/-Kjqz5YRz2-dp7NREedN
Works in 1.4.6: https://www.webpackbin.com/bins/-Kk-z5JKXRiM6WrhzTux
Steps to reproduce
Add any CSS property using the camelCased version.
Expected Behavior
The property is converted to the hyphenated version.
Actual Behavior
The property is left camelCased and is invalid.

It indeed doesn't work, but to make it work we'd have to write a stylis middleware for something that I'd consider unexpected behaviour. I'm kind of baffled as to why this was part of styled-components v1 in the first place, i.e. where it was coming from before. Was it part of a postcss plugin that we used?
I don't think that we should fix this regression in v2 as it is one of the features that moves it farther away from actual CSS.
cc @geelen

The whole reason we added that was to make it possible for polished to support all CSS in JS solutions...

Yeah this came about because we converted everything from CSS to objects to use inline-style-autoprefixer then back to CSS string to use PostCSS. So this is behaviour I'm happy to lose.
FYI, if you use camel cased CSS properties inside objects, v2 works just fine:
const Title = styled.h1`${{
  fontSize: '1.5em',
  textAlign: 'center',
  color: 'palevioletred'
}}`

Reproduction: https://www.webpackbin.com/bins/-KkjGYcrLZDO1doiMjEN
So, this shouldn't affect polished at all, right?

Oh right I just re-read your original issue. Yep, I don't see any reason to restore this behaviour from v1 to v2 as long as objects still work 100%.

Thanks folks! Just wanted to a) point it out in case it was unintentional and b) make sure that was going to be the case going forward just so we didn't end up building any functionality that assumed it (unlikely).

Oh yeah now that I re-read the initial issue that's perfectly fine, my bad! I thought it didn't work inside objects.


Contents of spl.txt is confusing

Problem 1: Power is calculated as negative for one of the power analyzer - it is positive on the analyzer side.
Problem 2: Sum of power is correct, but instead of "-1" can we use "N/A" as "-1" is used for invalid readings.

This is what we did:
Modified the parse_mlperf.py file to address two issues:

Corrected the power calculation for negative values from power analyzers.
Changed the representation of invalid readings from '-1' to 'N/A'.

You can review changes in this commit: https://github.com/jjyutm4532/mlcommons-power-dev-329/commit/946b7543ce5c59fd4672840357b1e70325645aed.

[!CAUTION]
Disclaimer: The concept of solution was created by AI and you should never copy paste this code before you check the correctness of generated code. Solution might not be complete, you should use this code as an inspiration only.

If you no longer want Latta AI to attempt solving issues on your repository, you can block this account.


component version is wrong

Type: Incorrect
Summary:
component version is wrong
Details:
This entry seems to have been automatically harvested from the GitHub tag. However, the tag name has not been used as the artifact version (1.14.0) but the corresponding Git revision.
Resolution:
Set the artifact version to 1.14.0
Affected definitions:

qpid-dispatch 525291a9b5b86e2dcc9e957c189a5cc73262de1d

We are not curating facets at this time, which is the only change I see on this PR, so am closing this PR.
I do see the definition (qpid-dispatch 525291a9b5b86e2dcc9e957c189a5cc73262de1d) is using the commit vs. the tagged version ID, and that is how the definitions are setup.


[Diagrams for Jira] Save image as SVG/PNG

[X] I agree to follow the Code of Conduct that this project adheres to.
[X] I have searched the issue tracker for a feature request that matches the one I want to file, without success.

Is your feature request related to a problem? Please describe.
I want to use the Jira draw.io app, but currently using the draw.io app is completely pointless, because I work a lot on the SmartPhone and here it is not even possible to view the images.
Describe the solution you'd like
A simple and elegant solution here would be to include the "save format" in the configuration.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered. The user then has the option to select "DrawIO", "SVG", "PNG".
If the user selects DrawIO, then the document will still be saved normally (mxfile). If he chooses one of the other two options this will be saved as an image with the embedded content.
This gives the additional possibility that the images can be included in the content and also the "draw.io" panel does not have to be used any further.
Additional context

Unfortunately, the Jira app doesn't support third party apps yet.

A simple and elegant solution here would be to include the "save format" in the configuration.

Fix the default save format in the JSON configuration or just change the default?
At the moment Confluence Connect has a bug that mangles the PNG+XML format when we try to upload it. If that were fixed we could combine the two.
If you removed the draw.io panel there'd be no way to edit the diagram from within an issue. You'd have to download the file, edit and save it, then upload it again.


JQuery Compatibility

I've installed EmptyJS, and the first thing I noticed was that all my JQuery code stopped working. Is there a compatibility setting I can use? I'm also using mootools on my page.

Confirmed, only difference is that I am using jQuery 1.6 from my local codebase and 3 other versions of jQuery are brought in from CDN via copy and pasted code from various tutorials. Adding mootools didn't help.
Any insight?

@bennybtl @j-hernandez

Well I have to say this seems... capricious and arbitrary.

I got the same issue and adding a semicolon to the end of the file fixed it for me.

I really wish I could "like" issue comments, you guys are great!


Currently Doesn't Install

I'm currently having trouble installing this because dependencies on older version of GeoStats.jl.  The required older versions of GeoStats.jl doesn't seem to precompile.
Despite the technical difficulties, I'd love to give this library a try!

Hi Peter
The last few versions of GeoStats had some big refactoring. To use with the new version, LocalAnisotropies needs some adjusts indeed to work. I'll take a look tomorrow to see how big are the changes and update it. Meanwhile, it should work well if you use an older GeoStats version

Thanks Rafael,
I was actually having trouble getting the older GeoStats version to
precompile in my current environment.  I might have time to review the
LocalAnisotropies.jl source code this coming week and try to help out if
you'd like.
On Thu, Oct 26, 2023 at 6:06 PM Rafael Caixeta @.***>
wrote:

Hi Peter
The last few versions of GeoStats had some big refactoring. To use with
the new version, LocalAnisotropies needs some adjusts indeed to work. I'll
take a look tomorrow to see how big are the changes and update it.
Meanwhile, it should work well if you use an older GeoStats version
—
Reply to this email directly, view it on GitHub
https://github.com/rmcaixeta/LocalAnisotropies.jl/issues/103#issuecomment-1782095610,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ALRV2UJDJM52J2UC7YEAAKLYBL3JNAVCNFSM6AAAAAA6R6SRWOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTOOBSGA4TKNRRGA
.
You are receiving this because you authored the thread.Message ID:
@.***>

I took an initial look yesterday. There were quite a few functions renamed. And even packages deleted/renamed, what might block installing previous versions. I guess I just need to review the adapted kriging functions now, I'll let you know if it works or if I'll need some help

Well, still needs some refactoring to make the code cleaner
But now the last release 0.4 should work well with GeoStats version 0.46
The only thing that will not work in the README example is the plot of the arrows/ellipses into the same Makie environment as the GeoStats (need to migrate the plot recipe later); but should still work well alone with Plots.jl (2D) and VTK export (3D)
If you still have issues let me know that I'll reopen the issue


Would it be possible to slow down the rate of major version changes?

Hi @vicapow!
That's a valid questions - in the past few majors, we stabilized Base UI, we had to work on making right a few early decisions. Moving forward, I'd expect the rate of major versions to slow down.


UIStoryboard extension for easily instantiating view controllers

Creating view controllers from code using storyboards is a lot of boilerplate.
From
let vcName = ViewController.className;
let vc = storyboard!.instantiateViewControllerWithIdentifier(vcName) as! ViewController
To
let vc = storyboard!.instantiateVC(ViewController)
Both vc are of type ViewController.

Thanks 👍


add negative number support

Fix ValueType not recognizing sign (+/-) characters at the start of the input string.

You're awesome, thanks!


Minor addition to avoid changed result on csf installation check

Avoid hosts to be marked as changed each time the role is executed because of the CSF installation check

Awesome, thanks for the merge!


more idiomatic API

the current API is entirely defined in Rust via wasm-bindgen, but could benefit from JS side helpers, like template strings

i think this is covered by #18 and #26


Rename bn_BD path for consistency

This PR just renames the location of the Bengali cheatsheet so it's consistent with all other titles.

@hectorsector thank you for catching this :+1:


Fix spelling error in names-generator.go

Not much is required to reproduce the issue, since it's just a spelling error (and one in a comment, at that).
Here's a picture of my brother's new puppy:

LGTM

LGTM

LGTM 🐰


Examples won't run if first adapter doesn't support DX12

All examples pass nullptr as the first argument to D3D12CreateDevice. The implementation of D3D12CreateDevice is flawed in that it will pick the first adapter, regardless of whether it supports DX12 or not. This will result in device creation failing if the first adapter doesn't support DX12 but the second adapter does.
D3D12CreateDevice either needs to be fixed to pick the first working adapter (probably too late for that?), or the samples should be fixed to autodetect the first working adapter. Nobody should use the current flawed implementation of passing nullptr as first argument, because that means the application/game won't run on random machines which are unlucky enough to have their DX12 adapter in second position.

Happens to me too

You are correct.  To give you some context, our original aim for the API samples was for each of them to highlight specific Direct3D APIs/features in the leanest way possible such that someone could take a look at the code file and follow it from beginning to end without too much "boilerplate" code getting in the way.  That is why you will also notice that other framework-type code paths are missing (such as handling WM_SIZE and DXGI_ERROR_DEVICE_REMOVED events).
That said, I will concede that we may have been too aggressive in pruning this from our setup code and should add it in because it will get in the way of some developers (such as yourself) getting started if they try to run the code.

I'm mostly worried about developers picking up that code and use D3D12CreateDevice passing nullptr, and if it works for them they never realize their app/game will fail on random machines.
Took me several evenings to figure out what caused it and I can imagine some devs with less resources won't spend that time after an app shipped and just say "get a DX12 machine".
Currently almost all samples on the net make the same mistake and it would be great to have samples with proper adapter selection code. Thanks in advance if we can get some :-)

I sent out a change for review internally yesterday.  I plan to commit it today.
Be aware though, that this behavior is not a regression from previous versions of Direct3D.  Even 11 will pick your primary adapter by default.  The prevailing thought around the community is that most people use their most powerful (or recent) GPU as their primary adapter.  The majority of games do create the device by passing in nullptr for the adapter, so I would recommend you change your settings to avoid being broken in the future.
You should be able to set your DX12 GPU as your primary adapter by going to Display Settings and selecting "Make this my main display" while selecting the monitor that it is plugged in to.

Actually it is different, DX11 only reports a single adapter and works just fine. The AMD drivers are responsible to decide which chipset is running for which application and can even have different applications run on different chipsets. I don't really know what the hardware does, but from what I understand there is an onboard intel chipset which handles the normal operation (to save energy if you believe the marketing), and for high performance stuff like games it forwards everything to an AMD GPU. All games (and most Windows dialogs) only ever offer me one adapter, usually labeled by the intel chipset, only starting with DX12 I see two adapters offered by the API. Thats part of why it took me so long to figure out the problem.
Since both chipsets share the same display and everything I'm not sure I can configure which adapter is the first. Certainly not by selecting a monitor.
From what I gathered on the net this has been a trend for notebooks over the last several years. In fact when I bought the notebook I explicitely looked for one with a powerful enough GPU to play (and develop) DX11 games (at the time there was no DX12). They sold it listing only the AMD chipset so I was surprised it had a second chipset. From my research all newer notebooks I was interested in (at that time) used this dual chipset approach.
So since I can't seem to change adapter order, and DX12 is the first version which exposes both of this dual chipset, I believe its a different scenario to DX11 and the current behavior will be causing new problems for people.

Ah, a hybrid laptop.  I thought you were talking about a desktop with two discrete GPUs.  DX12 allows developers to use both GPUs in parallel, so we certainly would want the integrated GPU to show up in the adapter list.  Let me ask around.  This reminds me of a driver bug we sent over to Intel recently.  We have seen a few problems with hybrids where the Intel adapter is trying to advertise itself as the primary.  Would you be willing to share a dxdiag with me?  I'll PM you if that's ok.

Sure, you can reach me via the mail on my profile.

I just committed a change to develop that will allow the samples to enumerate adapters and choose the first one that supports DX12.  Note that the change is in the DXGI API which is why I asserted that you should get the same behavior regardless of the Direct3D API version you are using.
The caveat is that on hybrid systems, the AMD driver has the ability to hide the Intel adapter for known games/processes.  I don't expect SDK samples to make it onto that list, but AMD probably provides some settings that you can configure in the control panel to help it decide when to hide the Intel GPU or not.
You can test this theory by replacing the DX12 create device method with D3D11CreateDevice and pass in nullptr for the adapter.  d3d11device->QueryInterface for the IDXGIDevice and then get the adapter from it.  Compare that adapter with the first adapter that gets enumerated by EnumAdapters(which should be Intel) and see if they're the same.

Hi
I just tried to enumerate adapters on my machine and used eg. D3D12CreateDevice(my_adapter_list...) to created device but an  error 0x887a0004 returned from this method, this laptop has two gpu with nvidia optimus (intel hd 4000 and nvidia gt 645m).
The  error  0x887a0004 still returned when  d3d12 device was created  by second device directly,but the second device (gt 645m) is support D3D_FEATURE_LEVEL_12_0.
I have checked my platform(win 10 pro ) and sdk version(10.0.10240.0) ,dx dig shows everything work normally

Is the new explicit adapter enumeration code returning nullptr for you?  If so, then it sounds like the nVidia driver doesn't have support for that GPU.  It looks like that's a Kepler GPU, so I'm a bit surprised.  What's the driver version number?

@bobbrow Alright, I tested your suggestions. The adapter selection code works nicely.
DX11 reports the intel chipset as adapter (i.e. it's the same as the first adapter DXGI enumerates)
If I select "high performance" for the application in the AMD control center then DXGI no longer enumerates the intel chipset at all, DX12 works without passing an adapter, and DX11 reports the AMD adapter. The latter is suprising to me because in the past that was not how it worked, it always reported the intel chipset, and only the intel chipset, but you could clearly see the difference in performance if you changed the driver settings. Either driver bugs have been fixed since I last checked this, or the behavior changed with the Windows 10 update.
Anyways, I'm glad there are options to work around the problems caused by D3D12CreateDevice being called without an explicit adapter, so we don't have to rely on everyone implementing adapter selection code after all. Thanks for looking at the problem and explaining it :-)

Explicit adapter enumeration and attempt to create device in  D3D12CreateDevice(...) doesn't initialize the device(device is nullptr),and return code by this method show me this message :
(0x887a004 Specified device interface or functionality is not supported on this system).
I have checked my nvidia driver version(355.60) and found some strange problems, In nvidia control panel, the DirectX runtime version and Directx API version is 12.0 but the DirectX feature level shows 11.0. The lastest driver version on nvidia website is 355.82.
Is the driver problem？

Yes, it's intentional that we don't initialize the device during enumeration.  We're just testing the driver to see if it's supported.  By the looks of things, the API is telling you that your GPU is not supported.
I believe that 355.82 is the latest driver out on Windows Update.  Please try installing that.  If it still doesn't work, I can send email out to nVidia to see if this GPU is supposed to be supported or not.
The difference between runtime/API version and feature level is one that has confused a lot of people.  DirectX 12 only requires "feature level" 11.  Note that we pass in D3D_FEATURE_LEVEL_11_0 to the CreateDevice function in the samples.  This is how we made DX12 available to the majority of the GPUs already out there.  Otherwise it would have needlessly required everyone to buy new graphics cards.  There are additional features available for GPUs that support feature level 12 and 12.1, but the current set of samples do not make use of those features.

Thanks.
I didn't figured out the difference between D3D_FEATURE_LEVEL_11_0 and D3D_FEATURE_LEVEL_12_0 until you ponited out that we should pass in  D3D_FEATURE_LEVEL_11_0  to DirectX 12 CreateDevice function on a DirectX 11  conpatible device.
Kepler GPU do not support DirectX 12 completely,so i pass in D3D_FEATURE_LEVEL_12_0 to CreateDevice function result an error. Return code shows S_Ok when i pass in D3D_FEATURE_LEVEL_11_0 .

Good to hear.  Merged the code into master and will close this issue now.


Player flying in survival mode

I've searched existing issues and couldn't find a duplicate.

[X] I confirm this is not a duplicate.

Operating System
Linux manjaro
Server Software Version/Commit
public server
What happened?
If you join the server, you are in survival mode by default. As long as you don't change your gamemode, you're able to fly through the world. If you do change your gamemode and switch back to survival, you're unable to fly, as it should be.
To Reproduce
switch to creative and back to survival
Expected behavior
If the player is in survival mode, he shouldn't be able to fly.

I already opened a PR for fixing that, it was just some leftover debug code.


OpenSSL issue 2

The vulnerabilities were addressed in OpenSSL 1.02f/1.01r. To confirm your OpenSSL version, you can do a grep search for:
$ unzip -p YourApp.apk | strings | grep "OpenSSL"
You can find more information and next steps in this Google Help Center article.
https://support.google.com/faqs/answer/6376725

Solved in 0.2.3


preserve original photo time when uploading.

When uploading from a Web Browsethe image original creation time is preserved. When uploading with gpup the image has the time of upload as creation time. Is it possible to preserve original time so later image are searchable by proper time.

Now I see EXIF data is totally missing.

My bad, it seems some photos are missing EXIF. When it is present, the time in photos looks alright. But it's missing, then photo appears to be from time of upload. Can't gpup set last modification time?


Testing/CI: Add missing platforms for CI tests

Currently our CI only tests for Linux. Although it's the primary development platform, v1.0 is planned to have full cross platform support.
Add new CI jobs to run the core tests on Windows and macOS. For macOS we should aim to support the x86_64 arch as well.

This need #67 which will resolve dependencies dynamically update the config file to avoid separate config files per platform.


Custom Iterables and Maps documentation seems to be out of date

I just tried to use the IterableMapper as described here but discovered that it now requires a parameter called mapper of type MapperContainer. I cannot find any documentation on what this parameter is for or what it does either in the code or the docs. It appears to be related to equality checking. What should I be populating it with?
MapMapper also appears to require this new parameter as well.

Oh yes I forgot to update this. For now use Mapper.i for this parameter.
I will update the readme with the next version.

I also noticed that the MapMapper requires the factory function to return a Map (or implementation of a Map). Is this correct?
This would prevent it from being used to support IMap from the fast_immutable_collections package since IMap does not implement map. I am currently supporting it via the more verbose BaseMapper class.

This is by design and required for the implementation.
I'm will close this issue in favor of #28.


Rework button focus/active styling, with extra changes for checks/radios

This long-overdue PR does a few things concerning buttons:

for all .btns, it changes the :focus styling to :focus-visible - this way, the focus style doesn't take effect and "stick" (until you click somewhere else) for mouse/touch users
for button-like checks and radios, the :focus-visible style now doesn't set the background colour, and there is no :hover styling. this stops the very confusing problem of having the mouse, or keyboard focus, on a checkbox, checking/unchecking it, but only being able to see whether they did indeed check/uncheck by moving keyboard focus away/clicking somewhere else. particularly noticeable in our outline button example, where before you simply couldn't tell what was going on.

Closes #33481, closes #31149, closes #34664, closes #36502, Fixes #26804.
Possibly supersedes #28999 (think this approach may be cleaner)

This is a noticeable change, but don't think we'd class it as a breaking change...more a refinement/more sensible styling.
Video of the before/after, showing checks/radios buttons, check/radio button groups, and regular buttons
https://user-images.githubusercontent.com/895831/186750247-e2183e0b-1fac-4812-973d-0cdf3b33d59e.mp4

In our team we don't use button-like checks and radios (even though sometimes we really want to) for the reasons you mentioned. This would be a very valued fix for us.
Quick question: Is it intentional to keep the outline (with mouse use / click) on elements like .form-check (checkbox, radio, switch)? I would have thought that .form-check and button-like checks and radios would behave the same way.

Quick question: Is it intentional to keep the outline (with mouse use / click) on elements like .form-check (checkbox, radio, switch)? I would have thought that .form-check and button-like checks and radios would behave the same way.

@florianlacreuse yeah that's probably something we'll want to revisit as well. admittedly, for this PR, I concentrated solely on the button-like checks/radios which have been problematic for ages. once I get a moment I'll look at all the other places where :focus-visible is probably more appropriate, now that it's mostly supported in browsers

Thanks for the work @patrickhlauke.
@mdo Please consider shiping this merge request with v5.2.1. In my opinion it is a bug fix as the current state is not usable as @florianlacreuse already said.
The bug was first mentioned two years ago and v5.3.0 may be a long way off.

@mdo personally, i'd also prefer pushing this as soon as possible as it's been a known broken/unusable thing for quite a long time.
if it's felt to be too big, sure it can go in a 5.3, as long as that's not too far off into the future.

Fixed the merge conflict caused by https://github.com/twbs/bootstrap/pull/36507 ... although to do this I removed the new chunk in buttons.scss that does the :focus:not(:focus-visible) dance, I think that's now superfluous as I switched the actual :focus to :focus-visible in the preceding rules (so rather than setting and then unsetting it per #36507, this now just only sets it for :focus-visible from the start)

My god, do you intend to remove those borders from focused fields also?
Your buttons were far more beautiful before this change. As it's not a big deal for buttons (I prefered the previous style but I can manage), it would break everything I like in Bootstrap if you remove those border from input fields.
At least, give us the choice by adding some classes like form-control-shadow or form-control-noshadow or a simple bs-focus-shadow to all input and buttons that we could add to our fields.

we aim to make bootstrap accessible out of the box. if you don't want it to be accessible, you're always free to add CSS to override it...

I gotta say that the "sticky" border around elements that were interacted with was always a big part of the bootstrap design for me.
After this PR buttons feel really flat and lack a visual cue that they were pressed.
I would really appreciate it if you could at least display the border temporarily while a button is clicked.


Minimum Version Rule for APIKit

There is a memory leak issue in APIKit versions <= 1.3.11 (https://help.mulesoft.com/s/article/Out-Of-Memory-Metaspace-while-often-re-deploying-applications-using-APIKit). The linter should check that the version of APIKit dependency in the mule application pom.xml file is at least 1.3.12.
Group ID: org.mule.modules
Artifact ID: mule-apikit-module
Version: atleast 1.3.12

To implement this rule for checking APIKit version, we will do the following:

Extend the existing PomDependencyVersionRule linter rule implementation, and set below parameters in the implementation to check APIKit version in the pom.xml file:

groupId: org.mule.modules
artifactId: mule-apikit-module
artifactVersion: 1.3.12.
versionOperator: GREATER_THAN

@dileepkumarv-avio - artifactVersion should probably default to something newer now, 1.3.12 is about 3 years old.  We should also make that version configurable w/ a default value.

@adesjardin That makes sense. I will make artifactVersion configurable and default it to latest version 1.9.1 when not provided in the rule.
Latest version of APIKit - 1.9.1 is compatible for Mule 4.1.5 and above.
https://docs.mulesoft.com/release-notes/apikit/apikit-<IP_ADDRESS>-release-notes

APIKIT_VERSION linter rule is added to validate Apikit version in the Mule application. Implementation in done in PR - #131


Bump storybook version

Is your feature request related to a problem? Please describe.
The storybook version we use is outdated.
Describe the solution you'd like
We should go to the latest and greatest version.
Describe alternatives you've considered
N/A
Additional context
N/A

Apparently, we should do an upgrade of nodesjs from v16 upwards.


adding filter

the main part is in https://github.com/leibatt/scalable-vega/blob/master/lib/spec_rewrite.ts#L194


changing log structure for DEV mode

What this PR does / why we need it:
Log structure refactoring
Which issue this PR fixes
Fixes #190
Special notes for your reviewer:
Logs with dev mode:
2022-08-30T15:12:38.555+0200 - DEBUG - DATAPLANE - validating DataPlane resource conditions - {"namespace": "default", "name": "kong-zkr5n"}
2022-08-30T15:12:38.600+0200 - DEBUG - GATEWAY - reconciling gateway resource - {"namespace": "default", "name": "kong"}
2022-08-30T15:12:38.600+0200 - DEBUG - DATAPLANE - reconciling DataPlane resource - {"namespace": "default", "name": "kong-zkr5n"}
2022-08-30T15:12:41.441+0200 - DEBUG - GATEWAY - checking gatewayclass - {"namespace": "default", "name": "kong"}
2022-08-30T15:12:41.441+0200 - DEBUG - DATAPLANE - validating DataPlane resource conditions - {"namespace": "default", "name": "kong-zkr5n"}
2022-08-30T15:12:41.441+0200 - DEBUG - DATAPLANE - exposing DataPlane deployment via service - {"namespace": "default", "name": "kong-zkr5n"}

logs without dev mode:
{"level":"debug","ts":1661865281.052911,"logger":"gateway","msg":"ensuring dataplane config is up to date","controller":"gateway","controllerGroup":"gateway.networking.k8s.io","controllerKind":"Gateway","gateway":{"name":"kong","namespace":"default"},"namespace":"default","name":"kong","reconcileID":"036519c4-a627-4912-91e6-476458379a5d","namespace":"default","name":"kong"}
{"level":"debug","ts":1661865281.052948,"logger":"gateway","msg":"waiting for dataplane readiness","controller":"gateway","controllerGroup":"gateway.networking.k8s.io","controllerKind":"Gateway","gateway":{"name":"kong","namespace":"default"},"namespace":"default","name":"kong","reconcileID":"036519c4-a627-4912-91e6-476458379a5d","namespace":"default","name":"kong"}
{"level":"debug","ts":1661865281.05301,"logger":"gateway","msg":"looking for associated controlplanes","controller":"gateway","controllerGroup":"gateway.networking.k8s.io","controllerKind":"Gateway","gateway":{"name":"kong","namespace":"default"},"namespace":"default","name":"kong","reconcileID":"036519c4-a627-4912-91e6-476458379a5d","namespace":"default","name":"kong"}
{"level":"debug","ts":1661865281.053045,"logger":"gateway","msg":"ensuring controlplane config is up to date","controller":"gateway","controllerGroup":"gateway.networking.k8s.io","controllerKind":"Gateway","gateway":{"name":"kong","namespace":"default"},"namespace":"default","name":"kong","reconcileID":"036519c4-a627-4912-91e6-476458379a5d","namespace":"default","name":"kong"}
{"level":"debug","ts":1661865281.053072,"logger":"gateway","msg":"waiting for controlplane readiness","controller":"gateway","controllerGroup":"gateway.networking.k8s.io","controllerKind":"Gateway","gateway":{"name":"kong","namespace":"default"},"namespace":"default","name":"kong","reconcileID":"036519c4-a627-4912-91e6-476458379a5d","namespace":"default","name":"kong"}
{"level":"debug","ts":1661865281.0530849,"logger":"gateway","msg":"ensuring DataPlane's NetworkPolicy is created","controller":"gateway","controllerGroup":"gateway.networking.k8s.io","controllerKind":"Gateway","gateway":{"name":"kong","namespace":"default"},"namespace":"default","name":"kong","reconcileID":"036519c4-a627-4912-91e6-476458379a5d","namespace":"default","name":"kong"}

PR Readiness Checklist:
Complete these before marking the PR as ready to review:

[x] the CHANGELOG.md release notes have been updated to reflect significant changes

You have conflicts to resolve :)
-{"level":"debug","ts":1661865281.0530849,"logger":"gateway","msg":"ensuring DataPlane's NetworkPolicy is created","controller":"gateway","controllerGroup":"gateway.networking.k8s.io","controllerKind":"Gateway","gateway":{"name":"kong","namespace":"default"},"namespace":"default","name":"kong","reconcileID":"036519c4-a627-4912-91e6-476458379a5d","namespace":"default","name":"kong"}
+{"level":"debug","ts":1661865281.0530849,"logger":"gateway","msg":"ensuring DataPlane's NetworkPolicy is created","controller":"gateway","controllerGroup":"gateway.networking.k8s.io","controllerKind":"Gateway","gateway":{"name":"kong","namespace":"default"},"reconcileID":"036519c4-a627-4912-91e6-476458379a5d","namespace":"default","name":"kong"}

It would be ideal if we could remove those duplicated namespace and name fields.

You have conflicts to resolve :)
-{"level":"debug","ts":1661865281.0530849,"logger":"gateway","msg":"ensuring DataPlane's NetworkPolicy is created","controller":"gateway","controllerGroup":"gateway.networking.k8s.io","controllerKind":"Gateway","gateway":{"name":"kong","namespace":"default"},"namespace":"default","name":"kong","reconcileID":"036519c4-a627-4912-91e6-476458379a5d","namespace":"default","name":"kong"}
+{"level":"debug","ts":1661865281.0530849,"logger":"gateway","msg":"ensuring DataPlane's NetworkPolicy is created","controller":"gateway","controllerGroup":"gateway.networking.k8s.io","controllerKind":"Gateway","gateway":{"name":"kong","namespace":"default"},"reconcileID":"036519c4-a627-4912-91e6-476458379a5d","namespace":"default","name":"kong"}

It would be ideal if we could remove those duplicated namespace and name fields.

This is not possible a priori because one comes from the context and the other from the object. We could do it by not passing the object to the debug, info, whatever helper, but this is out of scope for this PR. There is another issue related to what to log: #189


Drildown options depends on the query sintax

Is your feature request related to a problem? Please describe.
I recently discovered that in some conditions, DBeaver shows a little button on the result set keys that references other tables.
It's a neat feature, however, it's only available when the query contains the schema and the fields are preceded by the table name, which it's a little strange...
Describe the solution you'd like
Show the drill down buttons in all queries
Additional context
I'm using informix database, but i'm assuming the behavior is the same in all databases.

I think it is a bug, not a feature request.
I also encountered it but didn't figured out why sometimes it is shown and sometimes it is not.
Hope it will be fixed soon.

Could you provide clear minimal example to reproduce the issue?

Here you have some DDL/SQL.
The name of the database schema i used is forte and the database ins Informix.
`create table table1(id integer, detail char(10));
create index table1_pk on table1(id);
ALTER TABLE table1
ADD CONSTRAINT PRIMARY KEY (id)
CONSTRAINT table1_pk  ;
insert into table1 values(1,'lemons');
insert into table1 values(2,'oranges');
insert into table1 values(3,'bananas');
create table table2(id integer, table1_id integer, quantity integer);
ALTER TABLE table2
ADD CONSTRAINT PRIMARY KEY (id)
CONSTRAINT table2_pk  ;
create index table2_ix1 on table2(table1_id);
alter table table2
ADD CONSTRAINT (FOREIGN KEY (table1_id)
REFERENCES table1
CONSTRAINT table2_ix1);
insert into table2 values (1,1,5);
insert into table2 values (2,2,10);
insert into table2 values (3,3,15);
-- Not Ok
select *
from table1
inner join table2
on table2.table1_id = table1.id
-- Not Ok
select table2.table1_id, table1.detail
from table1
inner join table2
on table2.table1_id = table1.id
-- Not Ok
select table2.table1_id, table1.detail
from forte.table1
inner join table2
on table2.table1_id = table1.id
-- Ok
select table2.table1_id, table1.detail
from table1
inner join forte.table2
on table2.table1_id = table1.id
-- Ok
select table2.table1_id, table1.detail
from table1, forte.table2
where table2.table1_id = table1.id
-- Not OK
select table2.table1_id, table1.detail
from table1, table2
where table2.table1_id = table1.id
-- Not OK
select table1_id, table1.detail
from table1, forte.table2
where table2.table1_id = table1.id`

Thank you.


Proposer can query their available stake

Requirements
Proposer can get info re the portion of their stake (MATIC) still available for continuing proposing - CHECK if this feature is possible as per the current implementation or needs further development in nightfall_3

No longer valid


Update bower.json

Edit ignore module

Coverage remained the same at 99.634% when pulling f3d054de72c22c9fd66162203487f787e73727bc on StiVVi:patch-1 into 4d1e835ef70940154f2a11bf9285647471142e53 on peterolson:master.

Thanks, looks good to me


Debug cassandra sink - best practice

Some documentation on how best to debug the Cassandra sink would be welcome.
My specific use case is I have an Avro topic stream that is working, I've configured a Cassandra sink with error policy "THROW", the connect REST API report the sink is "RUNNING", the connect logs look normal (all INFO level, committing offsets etc), but there is no data in Cassandra. At this point I'm at a loss on where to go next, and think some general documentation on debugging problems would be helpful.
Some information it would be useful to know (plus I'm sure the data mountaineer team have a lot more to add):

Can we log the CQL insert statements?
Can we confirm behaviour of bad commits - will it throw?
Any insight on how to debug from the Cassandra side (ie if the connector is getting successful inserts, how to find the problem on Cassandra side)?

@0zeroth,
What version of cassandra do you use. 3.0.9 is required to fix a bug with json inserts

@0zeroth Please share your connector configs. We also have a slack channel that makes it easier to communicate?


[release-1.27] update k8s.io/kubernetes to v1.27.8 in go.mod

What this PR does / why we need it:
Update dependencies to v1.27.8 go version to 1.20.12
Which issue this PR fixes(if applicable):
fixes #2490
Special notes for reviewers:

Release note:

NONE

/test openstack-cloud-csi-cinder-e2e-test-release-127

/approve

@zetaab @jichenjc can you lgtm this PR?

/lgtm


Website not working in Firefox

Congratulations and thank you for these libraries!
The website demos (such as Placement, Shift, Flip, Size,...) and tutorial don't work in my Firefox 96.0.3 (64-bit) (but they work in Chrome). There are console errors such as:

Is Floating UI ready for production or is Popper.js still the official stable solution?

The site works fine for me in FF. Do you have an extension or something else blocking the scripts from loading?

🤦♂ Yes, that's it. I just forgot to think. With so many browsers open, I had not realised I was using another browser when comparing with the Popper documentation. Sorry for the trouble.


Create data nodes which contain images

Created by: brollb
This would be useful for supporting an entire CNN development (define architecture, training,  etc)

Created by: brollb
Fixed as of https://github.com/brollb/cnn-creator/commit/ff385ff785eb8e4d8125cd868412b92822649ae9


Fetch product media url on frontend

Hi,
My product images are not loading from s3 bucket via cloud front url, instead it is loading from my pub media folder of orgin domain.
My product images are loading from htt://mydomain.com/pub/get.php/catalog/product/cache/75eed2686e01eb22cb4050b2f40ddf97/d/i/dish_1.png
I need to get from cloud front http://cloudfront.net/catalog/product/cache/75eed2686e01eb22cb4050b2f40ddf97/d/i/dish_1.png
Thanks in advance....

This should help -
Enable URL rewrites from Magento admin panel.
You also need to update your Base Static Url settings if you are using CDN to deliver media.

thank you @pranavgaikwad . Will try that you said.

@spellmen, you have to set the base-urls. I just updated the installation wiki, see here.

@spellmen hasn't followed up with @pranavgaikwad so I'm assuming that this issue is resolved.