I'm Buddhist and I'm offended

The gear icon in VScode resembles the religious symbol of Buddhism, the Dharmachakra and I find it very offensive.

Please remove it. Or at least cover it with a hat or something.

I agree.
Related:

https://github.com/microsoft/vscode/issues/87268
https://github.com/microsoft/vscode/issues/87419

perfect solution is to cover it with a SANTA hat

Boatymcboatface might be offended too, looks like a boat steering wheel.

Thanks for creating this issue. We think this issue is unactionable or unrelated to the goals of this project. Please follow our issue reporting guidelines.
Happy Coding!

I find the word happy offensive. Not everyone is happy during the holiday season. Could we change that from Happy Coding! to Coding! please. Thanks in advance!

I am offended that everyone is offended.  I feel like I am being personally attacked and would like for people to stop being offended since it goes against my personal beliefs.

 So sad 🙁

Ok boomer

The symbol also represents an old ship steelering wheel..... it's okay. The symbol also known as a t in English also represents a cross in Christianity, where can I submit a request to remove

Jude observe do nothing

how is this in my feed what

No worries, nothing lasts forever!

Make everything flagged as offensive optional, but also default.
This should make everyone happy.

how is this in my feed what

Same reason I ended up here. Wat? (Sorry in advance as "wat" might be offensive to someone, somewhere)

I will work on this issue

@Isuru-Nanayakkara 😂😂😂

Replace it with nothing, and our Zen brothers and sisters will become offended

Is therea bounty on this?

Google feed brought me here, I'm not disappointed.

Dear vscode team, I hope it is quite apparent now how ridiculous the claim of @Christian-Schiffer, about the santa hat was.

Atleast I'm not the only one that get this item in the Google News timeline..

I got here because it appeared in my Google Feed. Why is this issue closed? And what's this icon for?

The icon kinda looks like a ❄ to me...

Im offended by this issue

Guys, I am here just for the comments! (Keep em Coming.) 😂

Does this expose Google's algorithm as promoting liberal propaganda.

I am offended that people are offended by things.

yall are buggin.

The gear icon in VScode resembles the religious symbol of Buddhism, the Dharmachakra and I find it very offensive.

Please remove it. Or at least cover it with a hat or something.

Basically it's the captain's wheel ..

For God's sake get over it, it's a captain's wheel! Do you have anything else of value to contribute to open source community?

dalai lama to bhai he apna, bol to sahi symbol badalwa doun.

You kidding me right? These discussions do not belong here on GitHub, contribute with code but don't start these kinds of bull here, if you chose to be offended go make a complaint email.

I find writing offensive. The invention of writing is EXACTLY what made millions of people illiterate. I will not stop writing about this until it's banned.

@konrad-bak same here. Write until it's against the law to write.

uh oh... #87537 too

Isn't buddhism all in for forgiveness and letting go?
🙄

I'm so happy to be a part of this community. I love you all.
Merry Christmas everyone!

Oo wokesoft close the thread 😱😱😅😅

Is a free software, if you are offended is your problem and don't use, is about software not your feelings.

Is a free software, if you are offended is your problem and don't use, is about software not your feelings.

@jycr753 This is a joke making fun of MS for pandering to every Tom, Dick, and Harry that gets offended by the most inconceivable things. Such as someone being upset about the Santa hat, so they removed it.

Is a free software, if you are offended is your problem and don't use, is about software not your feelings.

@jycr753 This is a joke making fun of MS for pandering to every Tom, Dick, and Harry that gets offended by the most inconceivable things. Such as some snowflake being upset about the Santa hat, so they removed it to pander to them.
It's riding on the growing level of unrest over blind pandering to "offended" people, actively making things worse or less enjoyable for many just to serve the unconformed feelings of a single individual.

What! Amazing the Microsoft remove it just for some "feelings"

Meanwhile in another world, this was observed.

I would recommend watching this https://youtu.be/ceS_jkKjIgo


Fixed files for Netbox 4.0 Compliance

I changed extras.plugins to netbox.plugins  for the following files:
in init.py
template_content.py
I also removed the button color (as it is no longer supported) for the following file:
navigation.py
Documentation for performing these tasks I found here:
https://netboxlabs.com/docs/netbox/en/stable/plugins/development/migration-v4/
I have never contributed to a Github repo before, so I hope I helped, and this is sufficient.

Didn't see someone already did the changes just waiting for approval


Build self dataset problem when colmap generate pose

When I tried to generate the MVSGaussian dataset using the video frame data I collected myself, I encountered some problems. When I run the command
python lib/colmap/imgs2poses.py -s examples/myscene

It always reports information
Need to run COLMAP
Features extracted
Features matched
Sparse map created
Finished running COLMAP, see .\dataset\colmap_output.txt for logs
Post-colmap
Cameras 5
Images # 21
ERROR: the correct camera poses for current points cannot be accessed
Done with imgs2poses

It seems that there is a problem with the camera pose and corresponding point cloud,But the most crucial thing is that it cannot generate the data poses_bounds.npy  to be used in the next stage.
Can you provide some suggestions for me to collect datasets that are compatible with MVSGaussian,for example, the parameters captured by the camera, as well as the characteristics of the images used for processing, such as image size, image quality, and image clarity.

Hi, you can try runing colmap sparse reconstruction https://colmap.github.io/cli.html# , and then run the script lib/colmap/imgs2poses.py to get poses_bounds.npy.

This is because there are images in your image that cannot estimate the camera pose. It is recommended to manually filter the following images. it works


--only does not scope commands to one step

Minimal repro in this repo: https://github.com/ling1726/lage-only-repro
Simply run npx yarn lage run test --only you will see that the build steps are run every single time

I think something might have gotten messed up about scoping/pipelining in general, because --to also doesn't work properly (IMO): if you run lage run test --to react-components it ONLY runs tests for the last package, not for all the ones in between. And lage run test --scope react-components only runs tests for react-components and the things after it?? Pretty sure both of those worked as I expected in the past.

Apparently the issue is that @kenotron refactored things in #153 which removed the implementation of --only (it was previously passed to a @microsoft/task-scheduler pipeline via src/task/taskRunner.ts which was deleted in that commit).
Also FYI for @ling1726 or @Hotell if you try to look into this at some point: lage's latest dist-tag has been moved back to 0.31.2, and for changes checked into master you'd need to pick up the unstable tag or specific versions (you'd have to ask Ken about the background/reasoning).


2.6-beta:  Add noUndefined and noErrors to the new config files

The TeX noErrors and noUndefined extensions need to be added to the new TeX combined configuration files.

I've opend https://github.com/mathjax/MathJax-dev/issues/15

fixed upstream.


BIG CHANGE! changing all pipeline

Hi @meomancer thanks for refactoring. How come we don't need pipeline stuff in prod anymore?

hi @timlinux
on the production, the setting is for compression, and it changes all of name of js function that makes not found for the function. So, it is not compressed now
or is there anything that i should do?


Update to work Work Php 8 and  Symfony 5.3. Add Sonata Admin integration tutorial.

Hi, i made some modifications to be able to work with this bundle in Symfony 5.3 and Php 8.
Also i updated the documentation in https://gist.github.com/mpclarkson/d5dbd5f4096069a43ef1 explaining how integrate the bundle with Sonata Admin.
If you think is usefull, please add to the main repository.

See https://github.com/94noni/ObHighchartsBundle#obhighchartsbundle


[utils] stopwatch fixed seconds

Hi Developers,
The calculation of the second has been fixed in this small patch.

@AndreyBarmaley the current code is correct.
The stopwatch can be stopped and resumed (started) multiple times and will provide the time elapsed while it was running.
If you want to reuse the stopwatch use stopwatch_reset to reset it to its initial state.

@mfleisz
Sory, but I don't understand the logic of stopwatch.
stopwatch_start
...
stopwatch_stop
stopwatch_get_elapsed_time_in_seconds

// check elapsed, elapsed is small and continue

stopwatch_stop
stopwatch_get_elapsed_time_in_seconds

// here we have the elapsed already wrong.

How can I check elapsed without stopping?

Use it depending on what you want:
stopwatch_start
/* do work1 */
stopwatch_stop

/* check elapsed time of work1 */
stopwatch_get_elapsed_time_in_seconds

stopwatch_start
/* do work2 */
stopwatch_stop

/* check elapsed time of work1 + work2 */
stopwatch_get_elapsed_time_in_seconds

Or:
stopwatch_start
/* do work1 */
stopwatch_stop

/* check elapsed time of work1 */
stopwatch_get_elapsed_time_in_seconds

stopwatch_reset
stopwatch_start
/* do work2 */
stopwatch_stop

/* check elapsed time of work2 */
stopwatch_get_elapsed_time_in_seconds


K8SSAND-1434 ⁃ Federation

What is missing?
TLDR: Authorization system for the federation of K8ssandra data planes.
Federation requires access provision, and management. This feature is curently lacking in K8ssandra (correct me if I am wrong). The access can be delegated by a private/public key scheme where the signatures are passed to the control-plane from the federated data-plane. These private keys can be rotated automatically using something like a transit secret engine for security assurance.
Why do we need it?
Projects that require networks of individual groups rather than a single hierarchial entity such as a company can benefit from the horizontal scaling capabilities of Cassandra.
Cassandra alone can't and shouldn't support this feature, it should be something that is provided at the level of orchestration, K8ssandra.
┆Issue is synchronized with this Jira Task by Unito
┆friendlyId: K8SSAND-1434
┆priority: Medium

I might have misunderstood your request here, but to me this feels like a feature at the Kubernetes level rather than k8ssandra-operator level. For example, Openshift has security features that would allow restricting the access to those namespaces where the control-plane is deployed to with different authentication / authorisation methods.

I might have misunderstood your request here, but to me this feels like a feature at the Kubernetes level rather than k8ssandra-operator level.

An eye-openening point! I am not looking for any namespace restriction, maybe this is applicable to some, but restriction to what clusters can enter the federation. I realize that I was requesting a bidirectional control between the control plane and KubeFed.
The authentication should be at the level of Kubernetes for sure. And scaling should be handled by the contorl plane like any other scenario. I am closing this issue.


Extend testing of CL_UNORM_INT_101010_2

All existing tests in test_image_streams, that are capable of testing image formats using the CL_UNORM_INT_101010_2 data type, now do so.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

get_32_bit_image_format() - Added (although this function isn't used anywhere).
compare_scanlines() - As you suggested, no need for a special case because all 32 bits in CL_UNORM_INT_101010_2 are used.
get_format_max_int() - Added.
get_format_min_int() - Added.
read_image_pixel<T>() - Already present in read_image_pixel_float(). Seems like read_image_pixel<T>() is used for int and uint while float has a separate function. As a side note, it looks like the cases for 101010, 555 and 565 in read_image_pixel<T>() are wrong, they are missing the normalisation divisions.
get_pixel_bytes() - Added.

Any objections to merging this PR ahead of the next teleconference? It is blocking the addition of testing for the 2_101010 format added by https://github.com/KhronosGroup/OpenCL-Docs/pull/1223.

I'm going to go ahead and merge this.  Since these are purely additions I think the risk of problems for implementations that do not support the 101010_2 format is low.  If we find problems we can always revert it.
@lakshmih FYI.

Thanks!


Why is Laravel Mix so painfully slow?

It used to take me less than a second to compile code, then all of a sudden It takes me more than 30 seconds. I uninstalled a bunch of npm packages and have even less code than when it took less than a second to compile but it still takes soooo long to compile. SOMEONE PLEASE HELP

We'd love to help but need more details. Can you please provide a reproduction repo that exhibits the slowness?
Some of it is webpack related and we have control over. In addition, if you are doing a production build, minification is a CPU intensive process and can take a significant amount of time when you have a lot of modules / files.

here is my package.json and webpack.mix.js. Both are very basic and barbones so I don't understand why this is going so slowly?? Please help
`{
    "private": true,
    "scripts": {
        "dev": "npm run development",
        "development": "mix",
        "watch": "mix watch",
        "watch-poll": "mix watch -- --watch-options-poll=1000",
        "hot": "mix watch --hot",
        "prod": "npm run production",
        "production": "mix --production"
    },
    "devDependencies": {
        "axios": "^0.21",
        "bootstrap": "^4.0.0",
        "jquery": "^3.2",
        "laravel-mix": "^6.0.6",
        "lodash": "^4.17.19",
        "popper.js": "^1.12",
        "postcss": "^8.1.14",
        "resolve-url-loader": "^2.3.1",
        "sass": "^1.20.1",
        "sass-loader": "^8.0.0",
        "vue": "^2.5.17",
        "vue-loader": "^15.9.5",
        "vue-template-compiler": "^2.6.10"
    },
    "dependencies": {
        "animate.css": "^4.1.1",
        "express": "^4.17.1",
        "intersection-observer": "^0.12.0",
        "laravel-echo": "^1.9.0",
        "luxon": "^1.26.0",
        "moment": "^2.29.1",
        "pusher-js": "^7.0.0",
        "randomatic": "^3.1.1",
        "reveal.js": "^4.1.0",
        "shufflejs": "^5.2.3",
        "uuid": "^8.3.1",
        "vue-browser-geolocation": "^1.8.0",
        "vue-colcade": "^1.2.4",
        "vue-collapsible-component": "^0.1.3",
        "vue-datetime": "^1.0.0-beta.14",
        "vue-debounce": "^2.6.0",
        "vue-image-lightbox": "^7.2.0",
        "vue-lazyload": "^1.3.3",
        "vue-observe-visibility": "^1.0.0",
        "vue-router": "^3.5.1",
        "vue-slick": "^1.1.16",
        "vue-toasted": "^1.1.28",
        "weekstart": "^1.0.1",
        "wysiwyg.css": "0.0.3",
        "ziggy-js": "^1.0.4"
    }
}
`

webpack.mix.js
const mix = require('laravel-mix');
/*
 |--------------------------------------------------------------------------
 | Mix Asset Management
 |--------------------------------------------------------------------------
 |
 | Mix provides a clean, fluent API for defining some Webpack build steps
 | for your Laravel application. By default, we are compiling the Sass
 | file for the application as well as bundling up all the JS files.
 |
 */

mix.js('resources/js/app.js', 'public/js')
    .vue()
    //.extract(['vue'])
    .sass('resources/sass/app.scss', 'public/css');

Few more questions:

At a high level what's in your app.js file?
Are you using any PostCSS plugins?
Compiling sass (or other css preprocessors) can be much slower than using something like PostCSS.

Here is the top of my public/app.js file. It works sometimes, but every once in a while it is either 1. works, but is very slow to compile (30s+), 2. does work and does compile but doesnt update when i use npm run watch. 3. or just npm run dev and npm run watch doesnt works at all so i have to delete my node_modules and reinstall node again to make it work.
/******/ (() => { // webpackBootstrap
/******/ 	var __webpack_modules__ = ({

/***/<EMAIL_ADDRESS>/*!**********************************************************!*\
  !***<EMAIL_ADDRESS>***!
  \**********************************************************/
/***/ ((module, __unused_webpack_exports, __webpack_require__) => {

module.exports = __webpack_require__(/*! regenerator-runtime */ "./node_modules/regenerator-runtime/runtime.js");

/***/ }),

/***/ "./node_modules/axios/index.js":
/*!*************************************!*\
  !*** ./node_modules/axios/index.js ***!
  \*************************************/
/***/ ((module, __unused_webpack_exports, __webpack_require__) => {

module.exports = __webpack_require__(/*! ./lib/axios */ "./node_modules/axios/lib/axios.js");

/***/ }),

/***/ "./node_modules/axios/lib/adapters/xhr.js":
/*!************************************************!*\
  !*** ./node_modules/axios/lib/adapters/xhr.js ***!
  \************************************************/
/***/ ((module, __unused_webpack_exports, __webpack_require__) => {

"use strict";

var utils = __webpack_require__(/*! ./../utils */ "./node_modules/axios/lib/utils.js");
var settle = __webpack_require__(/*! ./../core/settle */ "./node_modules/axios/lib/core/settle.js");
var cookies = __webpack_require__(/*! ./../helpers/cookies */ "./node_modules/axios/lib/helpers/cookies.js");
var buildURL = __webpack_require__(/*! ./../helpers/buildURL */ "./node_modules/axios/lib/helpers/buildURL.js");
var buildFullPath = __webpack_require__(/*! ../core/buildFullPath */ "./node_modules/axios/lib/core/buildFullPath.js");
var parseHeaders = __webpack_require__(/*! ./../helpers/parseHeaders */ "./node_modules/axios/lib/helpers/parseHeaders.js");
var isURLSameOrigin = __webpack_require__(/*! ./../helpers/isURLSameOrigin */ "./node_modules/axios/lib/helpers/isURLSameOrigin.js");
var createError = __webpack_require__(/*! ../core/createError */ "./node_modules/axios/lib/core/createError.js");

module.exports = function xhrAdapter(config) {
  return new Promise(function dispatchXhrRequest(resolve, reject) {
    var requestData = config.data;
    var requestHeaders = config.headers;

    if (utils.isFormData(requestData)) {
      delete requestHeaders['Content-Type']; // Let the browser set it
    }

    var request = new XMLHttpRequest();

    // HTTP basic authentication
    if (config.auth) {
      var username = config.auth.username || '';
      var password = config.auth.password ? unescape(encodeURIComponent(config.auth.password)) : '';
      requestHeaders.Authorization = 'Basic ' + btoa(username + ':' + password);
    }

    var fullPath = buildFullPath(config.baseURL, config.url);
    request.open(config.method.toUpperCase(), buildURL(fullPath, config.params, config.paramsSerializer), true);

    // Set the request timeout in MS
    request.timeout = config.timeout;

    // Listen for ready state
    request.onreadystatechange = function handleLoad() {
      if (!request || request.readyState !== 4) {
        return;
      }

      // The request errored out and we didn't get a response, this will be
      // handled by onerror instead
      // With one exception: request that using file: protocol, most browsers
      // will return status as 0 even though it's a successful request
      if (request.status === 0 && !(request.responseURL && request.responseURL.indexOf('file:') === 0)) {
        return;
      }

      // Prepare the response
      var responseHeaders = 'getAllResponseHeaders' in request ? parseHeaders(request.getAllResponseHeaders()) : null;
      var responseData = !config.responseType || config.responseType === 'text' ? request.responseText : request.response;
      var response = {
        data: responseData,
        status: request.status,
        statusText: request.statusText,
        headers: responseHeaders,
        config: config,
        request: request
      };

      settle(resolve, reject, response);

      // Clean up request
      request = null;
    };

    // Handle browser request cancellation (as opposed to a manual cancellation)
    request.onabort = function handleAbort() {
      if (!request) {
        return;
      }

      reject(createError('Request aborted', config, 'ECONNABORTED', request));

      // Clean up request
      request = null;
    };

    // Handle low level network errors
    request.onerror = function handleError() {
      // Real errors are hidden from us by the browser
      // onerror should only fire if it's a network error
      reject(createError('Network Error', config, null, request));

      // Clean up request
      request = null;
    };

    // Handle timeout
    request.ontimeout = function handleTimeout() {
      var timeoutErrorMessage = 'timeout of ' + config.timeout + 'ms exceeded';
      if (config.timeoutErrorMessage) {
        timeoutErrorMessage = config.timeoutErrorMessage;
      }
      reject(createError(timeoutErrorMessage, config, 'ECONNABORTED',
        request));

      // Clean up request
      request = null;
    };

    // Add xsrf header
    // This is only done if running in a standard browser environment.
    // Specifically not if we're in a web worker, or react-native.
    if (utils.isStandardBrowserEnv()) {
      // Add xsrf header
      var xsrfValue = (config.withCredentials || isURLSameOrigin(fullPath)) && config.xsrfCookieName ?
        cookies.read(config.xsrfCookieName) :
        undefined;

      if (xsrfValue) {
        requestHeaders[config.xsrfHeaderName] = xsrfValue;
      }
    }

    // Add headers to the request
    if ('setRequestHeader' in request) {
      utils.forEach(requestHeaders, function setRequestHeader(val, key) {
        if (typeof requestData === 'undefined' && key.toLowerCase() === 'content-type') {
          // Remove Content-Type if data is undefined
          delete requestHeaders[key];
        } else {
          // Otherwise add header to the request
          request.setRequestHeader(key, val);
        }
      });
    }

    // Add withCredentials to request if needed
    if (!utils.isUndefined(config.withCredentials)) {
      request.withCredentials = !!config.withCredentials;
    }

    // Add responseType to request if needed
    if (config.responseType) {
      try {
        request.responseType = config.responseType;
      } catch (e) {
        // Expected DOMException thrown by browsers not compatible XMLHttpRequest Level 2.
        // But, this can be suppressed for 'json' type as it can be parsed by default 'transformResponse' function.
        if (config.responseType !== 'json') {
          throw e;
        }
      }
    }

    // Handle progress if needed
    if (typeof config.onDownloadProgress === 'function') {
      request.addEventListener('progress', config.onDownloadProgress);
    }

    // Not all browsers support upload events
    if (typeof config.onUploadProgress === 'function' && request.upload) {
      request.upload.addEventListener('progress', config.onUploadProgress);
    }

    if (config.cancelToken) {
      // Handle cancellation
      config.cancelToken.promise.then(function onCanceled(cancel) {
        if (!request) {
          return;
        }

        request.abort();
        reject(cancel);
        // Clean up request
        request = null;
      });
    }

    if (!requestData) {
      requestData = null;
    }

    // Send the request
    request.send(requestData);
  });
};

/***/ }),

/***/ "./node_modules/axios/lib/axios.js":
/*!*****************************************!*\
  !*** ./node_modules/axios/lib/axios.js ***!
  \*****************************************/
/***/ ((module, __unused_webpack_exports, __webpack_require__) => {

"use strict";

var utils = __webpack_require__(/*! ./utils */ "./node_modules/axios/lib/utils.js");
var bind = __webpack_require__(/*! ./helpers/bind */ "./node_modules/axios/lib/helpers/bind.js");
var Axios = __webpack_require__(/*! ./core/Axios */ "./node_modules/axios/lib/core/Axios.js");
var mergeConfig = __webpack_require__(/*! ./core/mergeConfig */ "./node_modules/axios/lib/core/mergeConfig.js");
var defaults = __webpack_require__(/*! ./defaults */ "./node_modules/axios/lib/defaults.js");

/**
 * Create an instance of Axios
 *
 * @param {Object} defaultConfig The default config for the instance
 * @return {Axios} A new instance of Axios
 */
function createInstance(defaultConfig) {
  var context = new Axios(defaultConfig);
  var instance = bind(Axios.prototype.request, context);

  // Copy axios.prototype to instance
  utils.extend(instance, Axios.prototype, context);

  // Copy context to instance
  utils.extend(instance, context);

  return instance;
}

// Create the default instance to be exported
var axios = createInstance(defaults);

// Expose Axios class to allow class inheritance
axios.Axios = Axios;

I have never touched webpack and only code in vue so I don't know why it suddently breaks!!

I know I have postcss folders in my node_modules, but I don't think i ever intentionally installed it, so anything with postcss likely came prepackaged since i don't ever remember using it. AND i dont use sass

Things like this are very difficult to assist with if we don't have any concrete example. For example, the Laracasts codebase compiles in about 5 seconds. With the watcher running, it recompiles almost instantly.
Play around with you webpack.mix.js file, comment out certain lines to figure out what is slowing down your compile, and then come back and update this thread.

Hi @JeffreyWay,
I find mix slow even on a fresh install of Laravel, I think because it's being run through Laravel Sail, this is on basically every development machine I use, either at work or at home. Have you had this feedback before / is there a way to speed this up?
Also the watch command doesn't seem to pick up changes, but I guess it's maybe harder to track changes when the files are being mounted?


General spliner class

Replace generate_splines by a more flexible class
Allow to calculate the derivative of the radial integral numerically
Add linter for to check docstrings for double backticked strings which should be links to the Python documentation
Some minor cleanup to the rascaline __init__.py, i.e. adding an __all__ list.

Splitting the code into a SplinerBase and SplinerFromFunction class sounds maybe like an overkill here. However, this is only the first commit and should serve as a discussion basis for the architecture of the classes. After we agree on the design I will use the base class to extend the splining classes to more real and also kspace splining classes.

:books: Documentation preview :books:: https://rascaline--212.org.readthedocs.build/en/212/

We have to repbase again metatensor but otherwise should be fine.


Adding OSM as an alpha state adapter

Description
This PR fixes #282
Signed commits

[x] Yes, I signed my commits.

@leecalcote We need to fix a few things in mobile view

hem burger icon in the navbar needs to be shifted towards the right

footer needs to be center-aligned

And "Overview" can be center-aligned

https://github.com/layer5io/meshery.io/pull/285#issuecomment-671045934
Good eye, @manishdangi98. Here's a new issue for this - https://github.com/layer5io/meshery.io/issues/288. You might consider tackling this one. 👍

Thanks for these reviews, @PluckyPrecious @Ruth-ikegah @manishdangi98


Network: Adds network property support to sriov NIC driver

This PR allows one to use a sriov managed network for adding sriov NICs, e.g.
lxc network create test --type=sriov parent=enp4s0f0
lxc config device add c1 eth0 nic network=test

Testsuite passed


Render custom component as Event

Can somebody point me on how to render a custom component as an event. Ideally, I would like to render different components for different days
Thx in advance

All you need is a component or function that uses an event prop.  You can then pass it to the calendar component.
A simplified example of one I started (I'm using CSS modules):
const MonthEvent = ({ event }) => (

{event.start}

{event.name}

);

Then in the calendar just do
<BigCalendar
  components={{
    month: { event: MonthEvent },
  }}
/>

or if you wanted to use that for all events you could do
<BigCalendar
  components={{
    event: MonthEvent,
  }}
/>

This is my guess from digging the source - you can basically pass any renderable component. By default, it just shows "title":

    { Event
        ? <Event event={event} title={title}/>
        : title
     }

So, passing components={{event: ...}} allows you to change the text inside the event. Now as you have control over the events prop in <BigCalendar\>, you can pass in your own key/values and event titles can be modified depending on those values.
My example with simplified code, where I've added isBooked and noOfPax key/values to my event objects:

class CustomEvent extends React.Component {
  render() {
    const bookedIcon = event.isBooked ? <Badge></Badge> : null ;

    return (

        {moment(event.start).format('ha')} {event.title}

          {bookedIcon}
          <Badge>{event.noOfPax} </Badge>

    );
  }
}

There are two other things you can control:

eventPropGetter lets you change the styling of the event background (the blue portion) by changing CSS classes or adding inline styles (source)
eventWrapper  provides a wrapper around the whole event - I'm not sure why/how one would use this, but it's there.

Thanks @jrhalchak and @wasabigeek!

I am trying to resolve a much simpler problem: displaying just the event title without the event start / end time.
My custom event:
export default class CustomEvent extends React.Component {     render() {         return (
             {this.props.title}
         );     } }
How I use BigCalendar:
`
import CustomEvent from './CustomEvent';
<BigCalendar
selectable
events={this.props.bookingsList}
components={{
event: CustomEvent,
}}
defaultView="week"
defaultDate={moment().toDate()}
min={moment('2018-02-23 09:00:00').toDate()}
max={moment('2018-02-23 19:00:00').toDate()}
onSelectEvent={event => //some code}
onSelectSlot={slotInfo => //some code}
`
The event box still has the start / end time.
Quite a newbie here, so I'm not figuring out what I'm doing wrong. Any help woul be appreciated. Thanks

@bradeac This site is more for issues with the library itself (bugs/improvements).  Your question would do better over on stackoverflow.
Just from glancing at it, you're using this.props.title, I believe the prop that gets passed to the event component is just event so you'd want this.props.event.title.  Although it looks like you're passing a different component so I'm not sure why it would display otherwise.

That's exactly why I commented on an already closed issue, because it's more of a question instead of a bug.
True, it should be this.props.event.title. But this is not the problem. The problem is that the time range is still displayed, even though {this.props.event.title} is the only thing displayed by the custom component.

Maybe some else needs this behaviour. The fix is to modify the CSS:
.rbc-event-label {
  display: none;
}

@bradeac You can remove the time range using the formats prop:
<BigCalendar
  formats={{ eventTimeRangeFormat: () => null }}
/>

quick fix if someone need,
.rbc-time-content {
display: none;
}
.rbc-time-view {
flex: none;
}

Is there a way to pass props from the parent component that creates the BigCalander into the custom Event component? I'd love the ability to change the each individual event.title when the user clicks the event.title

Hello, I'm veeeery late to the party, but here's a demo on how you can change the styles of the EventWrapper.
I'm using tailwind but I believe you can use whatever you like.
const EventWrapperComponent = ({ event, children }: any) => {   const newChildren = { ...children };   const newChildrenProps = { ...newChildren.props };   newChildrenProps.className = ${newChildrenProps.className} outline-none border-none  bg-red-500`;
newChildren.props = { ...newChildrenProps };
return {newChildren};
};
`
For any adittional modification, just log the children props, copy the object, make the necessary modifications on the class name, (you have the event for your conditions) and replace it on the newChildren object you're passing.
<BigCalendar
     components={{
       eventWrapper: EventWrapperComponent,
     }}
   />

All you need is a component or function that uses an event prop. You can then pass it to the calendar component.
A simplified example of one I started (I'm using CSS modules):
const MonthEvent = ({ event }) => (

{event.start}

{event.name}

);

Then in the calendar just do
<BigCalendar
  components={{
    month: { event: MonthEvent },
  }}
/>

or if you wanted to use that for all events you could do
<BigCalendar
  components={{
    event: MonthEvent,
  }}
/>

This part doesn't seem to work. But allowing the custom element to be applied over all views can ruin the styling in the month view for instance.
<BigCalendar
  components={{
    month: { event: MonthEvent },
  }}
/>

However, this is a potential work-around to control the card style depending on the view it is being looked from:
const EventComponent = ({ event }: any) => (

{ parent.document.querySelector('.rbc-month-view') ? 'Month View' : 'Nope' }

);

Then applying EventComponent here:
components= {{
   event: EventComponent,
}}

As you can see, the text changes depending on the view:
Month View:

Week View:

If there are better work-arounds other than setting a max-height property (something like what follows), please do let me know.
.rbc-month-view {
  .rbc-month-row {
    .rbc-event {
      max-height: 1.5rem;
    }
  }
}

@mourabitiziyad A few things here
This works fine
components={{
  month: {event: MyMonthEventLayout}

Hi everyone,
Thanks in advance. Is there a way one can edit calendar event (change start or end) without using DragAndDrop? I wish one can help me with a code please

@lcim This question is better asked in our Slack #general channel, of on StackOverflow.


Standardize the Notice and HTTP tagging

Standardize the Notice and HTTP tagging

The tests were broken so I am merging this one manually on the command line, outside this MR, because I have to add another commit.


Updated DoubleTrim

Small change for clarity

@joecronin2 , test this piece of code against 1,000,000 random numbers!


Add support for Google Maps API For Work

This is the same PR as discussed here: https://github.com/kellydunn/golang-geo/pull/45
As noted breaking changes are included since a AuthSchema must now be provided to the GoogleGeocoder struct.

Looks like travis is reporting a failure, but I think that's because the v1.0.0 in-progress branch hasn't gotten the updates from master just yet.  I'll merge it now, thank you!

Thanks a lot!
Good luck on the v1.0.


Cannot place sign on other

It can be really disapointing to not be able to create farms with this mod :(

Please provide more information. Are you unable to place signs at all, or are you unable to place signs quickly like blocks?
Using the latest version I'm able to place signs fine, and placing signs quickly like other blocks is impossible by default due to how Minecraft opens the editing screen when you place them down. The only way to do so is to obtain a sign with NBT/Components, so that Minecraft doesn't open said editing screen; This can be done in creative by CTRL + Middle-Clicking a sign. I'm not aware of a way to do this in survival.

This was a while ago but I remember not being able to place a sign on another sign. I was trying to make an iron farm and I needed to disable the mod to place a sign on another sign.

@KayZzleTryHard testing with v1.2.6 for 1.21.1 shows I can place signs on signs. Testing on v1.2.5 shows the same thing.
Did you have other mods installed? What version of this mod, and what version of Minecraft?


Solo: Player vs AI

Story: As a player, I want to have the Game Mode ‘Player vs AI’ in order to play against an AI in a chilling round of Words++.
Acceptance Criteria:

[ ] I want to be able to play against a computer player.
[ ] The game mode should inherit its criteria from the Words++ user story.
[ ] The AI will have multiple difficulty levels.
[ ] The AI score will not appear in the ranked section.

Priority: low
Author: SoPra Group 9
Estimate: 16h

Couldn't be completed since we lost a group member in the beginning.
Please find further explanation in the group report.


Update link for BPF design Q&A

Previous link does not work any more.

Thanks!
The .txt file has been removed from the kernel tree, are you sure that it will remain accessible at this URL? It might be worth to switch to the RST file anyway, which is likely the only one susceptible to receive updates in the future.

Sure, it makes sense. I've updated it to the rst version.

All good, I merged it. Thanks a lot!


Fail to compile on web "Support for the experimental syntax 'jsx' isn't currently enabled"

Package version: 7.0.8
React version: 18.2.0
I am using babel in my project, when I added react-native-shaow-2 package. The project runs fine on IOS and Android. But running on web will result in the following error.

I have tried lowering the package version to 7.0.x and 6.0.6. Still result in this error.
I tried to create a bare-minimum react-native-web project, and added react-native-shadow-2. It produces the same error.
I have checked all the babel setup is correct, I have tried adding the plugin instead, still no luck.

Hi, this is a problem is your babel/webpack/maybe typescript setup. It's failing to convert the library's jsx to js. You would have the same problem with other libraries that also have jsx in their bundle files.
I believe I can not provide further help.
https://stackoverflow.com/a/67086430

Hey @SrBrahma, thanks for the reply. Yes you are right, I just had to make sure babel parse the package. By default our project exclude all node_modoules for babel. Just had to add this package to the exception.
Just leave the solution here incase anyone else face the same problem.
In webpack config.
    // Here we exclude all the packages from node_modules from using `babel-loader`
    // However some packages still need the babel loader to parse the source code
    // Therefore we need to add them to the exclude exception like so:
    // exclude: /node_modules\/(?!(MY-MODULE|ANOTHER-ONE)\/).*/,
    config.module.rules.push({
      test: /\.(js|jsx|ts|tsx)$/,
      exclude: /node_modules\/(?!(react-native-shadow-2)\/).*/,
      use: {
        loader: "babel-loader",
      },
    });

If you or someone else want to do this, I would happily accept a PR that adds babel/vite to the library building step to transpile the jsx to js to skip the step you made.


Update README.md

[x] Have you followed the guidelines in our Contributing document?
[x] Have you checked to ensure there aren't other open Pull Requests for the same change?
[x] Have you added an explanation of what your changes do and why you'd like us to include them?

Running the README example brew search --desc gives this warning:
Warning: Calling brew search --desc is deprecated! Use brew search --desc --eval-all or HOMEBREW_EVAL_ALL instead.

This PR updates that command to the preferred brew search --eval-all --desc.

Thanks @memark!


Fix false positive for recompiling

Description
It seems like node.automatic_attrs['nginx']['configure_arguments'] omits the quotes for this argument, creating a false positive for recompiling. Removing the quotes at all fixes the issue.
Check List

[ ] All tests pass. See https://github.com/chef-cookbooks/community_cookbook_documentation/blob/master/TESTING.MD
[ ] New functionality includes testing.
[ ] New functionality has been documented in the README if applicable
[ ] All commits have been signed for the Developer Certificate of Origin. See https://github.com/chef-cookbooks/community_cookbook_documentation/blob/master/CONTRIBUTING.MD

Test failures do not seem related

Merging under the obvious fix so no DCO signoff necessary. Thanks @krasnoukhov


Add a new command to write contract configuration

Writing configuration
beamer config write --rpc-file RPC-FILE --artifact CHAIN-NAME.deployment.json current.config.json desired.config.json
The write command takes an existing artifact file, a path to a "current" config file
and a path to the desired config file. It then issues appropriate transactions so that
the contracts' chain state reflects the desired configuration.
More concretely, the command does the following things, in order:

read the current config file and note the block number, block
compute the checksum and check if it matches the one written in the current config file
if the checksums don't match, exit with an error
read the desired config file (this one lacks both the block number and the checksum)
get the latest block number, latest_block
if latest_block <= block, exit with an error
if there were any configuration changes between block and latest_block, exit with an error
compute the set S of contract calls that need to be performed in order to make the desired
state current
for each call in S

get the current state from the RPC
if the desired state differs from the current state, issue a transaction to the RPC

compute the checksum of latest_block and the desired state
write the latest_block, checksum and the desired state to the desired config file

Tasks

[ ] add the new beamer config write command
[ ] write a test for the case where no transactions need to be issued (i.e. the config on chain is already in the desired state)
[ ] write a test that makes sure only necessary transactions are issued
[ ] write documentation

Hey team! Please add your planning poker estimate with Zenhub @bilbeyt @compojoom @fredo @GabrielBuragev @manuelwedler @panpilkarz


Website Unclear/Typo

In the Google Code description, the second paragraph, second to last
sentence would be more clear if it started "Unlike Yahoo Combo Builder,"
instead of "However,"

Also the warning has a typo: "Minify is designed for efficiency, but, for
very high traffic sites, Minify will serve files slower *than* your HTTPd
due to the CGI overhead of PHP. See the FAQ for more info."

Original issue reported on code.google.com by<EMAIL_ADDRESS>on 22 Jul 2008 at 7:09

Thanks!

Original comment by<EMAIL_ADDRESS>on 22 Jul 2008 at 11:44

Changed state: Verified
Added labels: Type-Other, Priority-Low
Removed labels: Type-Defect, Priority-Medium


Warning: Range var backend copies lock

Hi @bmf-san
I am getting some warnings in the code which point to line 93 @ server.go:
    for _, backend := range cfg.Backends {

The warning spew points to the Backend struct:
type Backend struct {
	URL    string `json:"url"`
	IsDead bool
	mu     sync.RWMutex
}

Fix: The sync.RWMutex variable should be embedded into a pointer.
	mu     *sync.RWMutex

Since we are assigning a temp var as backend, which holds the object of the used in the loop. The issue arises here, since we are holding a value of the mutex, and not the actual reference to the Mutex. Granted, we don't use the Mutex anywhere in the range in the healthcheck function, so we don't run into problems.
Feel free to correct me, if I am wrong 🙂

@wolflegend99
Sorry for the late reply😓
As you pointed out, I fixed it. https://github.com/bmf-san/godon/pull/3#pullrequestreview-1072590013
Thanks :D


Adding new footer component

Hey There,
I'm adding a new component called Footer component.
Thank you

Hi @bobbyiliev
Can you please review and merg my PR.
Thank you


Show how can you do in case the tag contais ':'

It is really common to do docker build -t myimage:latest but the syntax highlight goes crazy because of the : on multline scripts

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

ID: e825c07d-2168-c0aa-782a-ef6f9c7ba95e
Version Independent ID: 5cb6926b-215a-bf89-8e63-b2e1129e41df
Content: Build, test, and push Docker container apps - Azure Pipelines
Content Source: docs/pipelines/languages/docker.md
Product: devops
GitHub Login: @andyjlewis
Microsoft Alias: alewis

According to Docker's documentation on tags, tag name must adhere to the following format -
A tag name must be valid ASCII and may contain lowercase and uppercase letters, digits, underscores, periods and dashes. A tag name may not start with a period or a dash and may contain a maximum of 128 characters.
Closing this issue as only underscores, periods and dashes have been mentioned as accepted special characters for tags and not colons.


fix #14

https://github.com/Alir3z4/python-stop-words/issues/14

Thanks for contribution.
I've merged the patch.


Fix options passed in the constructor.

It was not possible to pass options to the $websocket constructor.
This fix should also resolve the issue : https://github.com/gdi2290/angular-websocket/issues/18, if you do : ws = $websocket('ws://<IP_ADDRESS>:8888', null, {reconnectIfNotNormalClose: true});

thanks!


Wallet creation time

address #805

[x] daemon
[x] tests
[ ] gui
[ ] doc

Concept ACK. I think the GUI integration should go in a latter PR (since it needs to update the daemon). So a small addition to doc/API.md seems to be all that's left to do here.

docs added, now ready for review


Color picker + align/distribute popup menus

Related to https://github.com/camunda/improved-canvas/issues/5

I mentioned in the weekly we could possibly open to bottom of context pad if there is no space on top. While I like that idea, it also was mentioned that we should keep this behaviour for all popup menus the same. And they do indeed behave the same at the moment:
https://github.com/camunda/improved-canvas/assets/25825387/bd9923ec-3c35-4b40-b2b8-dc5b4fc12e40
We could look into not covering the context pad as a core improvement potentially. But it shouldn't block this. And in this case, it's rare the cases where the popup menu will be cut off anyway since it's quite small

The contrast between separator and the background is super low. Is it necessary to be there if it's so hard to notice?

What I just noticed is that the selected popup menu button (paint brush) is a rectangular while the hovered popup menu buttons are round rectangulars.

The contrast between separator and the background is super low. Is it necessary to be there if it's so hard to notice?

I personally like that it's there but subtle. We can discuss this with @YanaSegal too.

I noticed that the first item is selected per default, even though it's not the value that is in fact selected.

This is a color picker issue. You can also see it in https://demo.bpmn.io/ . I can open an issue and follow up
I will have a look at the other hover aspects you mentioned.

I implemented your suggestions @barmac.

I replaced the groups logic with css (for context pad, I added it to an already opened PR with context pad issues: https://github.com/camunda/improved-canvas/pull/10)

The issue of the first element being selected is a popup menu feature (happens for normal popups, color picker and align). We do that intentionally and we treat "hover" as .selected. This is probably related to keyboard navigation purposes. But in these cases, it looks weird. I will treat this as a follow up to properly consider how to approach this.

@barmac I updated with your last suggestions 🙂


Update s3.md

Should it be "IAM policy" rather than "AIM policy"?

Proposed changes

Unreleased project version (optional)

Related issues (optional)

Yep, thanks @scjane 👍


Possible issue with recent fix for iOS 9 audio unlocking

Apologies if this is the wrong place to post this or if I haven't followed the right protocol here.
I was trying the recent fix for the iOS 9 'audio unlock' problem discussed here:
https://github.com/photonstorm/phaser/issues/2095
And may have found a case where it doesn't work correctly. I'm seeing this problem in my own code as well.
It seems that if the 'touch end' event comes at the end of a held touch or drag (rather than a brief tap), iOS will not unlock Web Audio inside that event. Since Phaser considers audio to be unlocked after the first 'touch end' event, if the first user interaction is a drag or held touch, audio will never be unlocked (or at least that seems to be the case).
Here's a self-contained test program:
var sound, playSound = false;
var game = new Phaser.Game(800, 600, Phaser.CANVAS, 'unlock-test', {
  preload: function() { game.load.audio("sound", "sound.m4a"); },
  create: function() {
    sound = game.add.audio("sound");
    game.input.onDown.add(function() { playSound = true; });
  },
  update: function() {
    if (playSound) {
      sound.play();
      playSound = false;
    }
  }
});

If the first interaction is a tap, it works and audio is unlocked, but if the first interaction is a drag or held touch, audio never unlocks. (I'm pretty sure the test program is implemented correctly, but it's possible I've made an error somewhere.)
I realize this is really more of an iOS issue than a Phaser issue, but I thought it might be worth mentioning.

Hmm if that's the case I'm not sure of any fix for it.

One thing I've tried is waiting for the 'onended' event of the Web Audio source to fire, indicating that audio has actually been unlocked, and only then removing the listeners. That seems a little circuitous though, and it still doesn't guarantee an unlock if the user never makes a 'tap' gesture at all.
Anyway, it seemed like it might be worth asking about, but maybe as you said it's just a limitation in iOS that there's no easy fix for at the moment.

I've been exploring bugs related to mobile WebAudio in this repo. It's truly a pain:
https://github.com/Jam3/web-audio-player#webaudio-gotchas
I'm also working on a variety of modules to ease these pains and wrap up the boilerplate into a single function.
I noticed the same 'touchend' issue in a recent demo. To fix, I'm listening for 'touchstart', storing the time and position, and then checking that in the 'touchend' event to see whether it's less than a certain threshold.
https://github.com/mattdesl/codevember/blob/25512f80a0aea27131b959a9ebd99f85456dfd03/src/30.js#L110-L115

Given the fix for this is now merged with webkit I'm wondering what the next best course of action is.
They may well revert to 'touchend' again at a later date, but assuming the fix lands in iOS shortly we're in the wonderful grey area of "all versions of iOS can use touchstart, except these two specific versions of iOS9", which is a hell of a mess. Or I guess you could just update all code to work on touchend only, and then do the timing trick and pray it wasn't actually a drag event, even if the timer threshold thinks it was.

This has now landed in iOS, so I'm going to keep an eye on it, but otherwise it'll go down as one of those lovely Apple legacy issues.


Documentation: MySQLConfigStore

Suggestion
Document the MySQLConfigStore integration with all the necessary details that explain what the store is and how to use it.
Motivation

Introduces users to the ConfigStore.
Improves usability of the store by providing usage examples.
Improves the completeness of the integration package.

Context

Integration docs: https://dev.mysql.com/doc
Integration SDK docs: https://typeorm.io/data-source-options#mysql--mariadb-data-source-options
Example PR of a store doc contribution: #575

@RichardAkman Can you please assign this to me.

All yours! @abhirajadhikary06

Thank you 😁. Excited to contribute

@RichardAkman please check if I am in the right file path or not ?

@abhirajadhikary06, the right file for store docs contribution is the README.md file of the integration package. Please take a look at #575 as a reference for what needs to be done.

@RichardAkman I have raised a PR. Could you kindly review it, and if everything looks good, please proceed with merging it into the main branch.

@RichardAkman I have updated the file with the changes suggested you. Please check it.


SkeletonViewer: Try to display a spur for the last bone of a chain

In the "spur" or "sphere/spur" mode, a spur is drawn from the current bone to its child(ren). But for the last bone of a chain, there's no next, so we can't draw the "spur".
This PR attempts to draw a "spur" in this case, calculating the bounding sphere of the vertices affected by the bone and using the center of this sphere to calculate the length of the spur.
PG: https://playground.babylonjs.com/#HFWCMJ#30

Without PR
With PR

Please make sure to label your PR with "bug", "new feature" or "breaking change" label(s).
To prevent this PR from going to the changelog marked it with the "skip changelog" label.

Snapshot stored with reference name:
refs/pull/14802/merge
Test environment:
https://babylonsnapshots.z22.web.core.windows.net/refs/pull/14802/merge/index.html
To test a playground add it to the URL, for example:
https://babylonsnapshots.z22.web.core.windows.net/refs/pull/14802/merge/index.html#WGZLGJ#4600
Links to test babylon tools with this snapshot:
https://playground.babylonjs.com/?snapshot=refs/pull/14802/merge
https://sandbox.babylonjs.com/?snapshot=refs/pull/14802/merge
https://gui.babylonjs.com/?snapshot=refs/pull/14802/merge
https://nme.babylonjs.com/?snapshot=refs/pull/14802/merge
To test the snapshot in the playground with a playground ID add it after the snapshot query string:
https://playground.babylonjs.com/?snapshot=refs/pull/14802/merge#BCU1XR#0

Visualization tests for WebGPU (Experimental)
Important - these might fail sporadically. This is an optional test.
https://babylonsnapshots.z22.web.core.windows.net/refs/pull/14802/merge/testResults/webgpuplaywright/index.html


[POC] Add a new SQLite backend using the sqlite3-api module

This new back-end relies on a module instead of the custom executable used by emacsql-sqlite.el.
I have implemented this in the hope it would help with the meaning of live #42 and to some extend it does; it doesn't error when storing a string that contains a null character (instead if silently discards the text that follows, and then errors when trying to read the incomplete string again). The reason this works is that it uses sqlite3_bind*() to supply the parameters - that way SQLite does not try and fail to tokenize the value containing the null character.
Since this approach is not enough to fix the issue I was having (while changing more than needed to do so), I probably won't work on this for a while, and it should be considered a proof-of-concept. While it would be nice to complete this eventually, there is still quite a bit work left. For starters, sqlite3 would have to be made available on Melpa (1) and the sqlite3 errors would have to be converted to emacsql errors.
(1) I would welcome that even if this back-end never got finished, and I would be willing to lend a helping hand here.
/cc @pekingduck

Were you intending for this to be merged right now, or is this just a placeholder/announcement?

The latter. I probably won't work on it any time soon because your fix for #42 addresses the issue that caused me to write this in the first place and I have quite a lot of other things on my place.
Still, I would be interested to know whether you see an alternative to the introduction of the new $V -- that's quite a hack I would rather do without, but I don't see how.

Closing because I don't know if and when I will resume work on this and its not actually necessary. It would just be nice to not having to rely on subprocesses.

@tarsius Just curious, how was performance with this code compared to using subprocesses?

Hm. Good point. As far as I remember, I never actually tested that. If it does make significant difference then we might have to upgrade this from nice to have to quite desirable. :stuck_out_tongue_winking_eye:
I certainly wouldn't mind if you pushed this forward. ** whistling **
But I fear the first step would be to get the module ready for release on Melpa. That would involve writing a wrapper elisp library that provides the package documentation and loads and compiles the module if necessary (not just on linux but also windows). Also the readme currently contains "This is an alpha release so it might crash your Emacs. Save your work before you try it out!". While it probably is pretty safe to use this anyway I would feel more comfortable if there were a maintainer that is more committed to the maintaining and improving the module than what we apparently currently have. I don't want to risk ending up in a maintainer role for this!


A lot of XA0106 warnings for Android projects that target Oreo

I am getting like 13 XA0106 warnings for Android projects that target Oreo API 26 for XamarinMediaManager.Forms
Reproduction steps
Create a new Xamarin Android project and target latest version of Android (Oreo) 8.0. Add the XamarinMediaManager.Forms. Build the project.
Expected outcome
No warnings.
Actually happening
A lot of XA0106 warnings
Your setup
Droid Oreo 8.0, latest version 0.4.5 XamarinMediaManager.Forms

Forgot to mention but I am using Visual Studio for Mac

Not sure if 8.x had anything to do with it, but I have the same thing these days with 8.1. If I include the ExoPlayer package, I get 74 warnings and 2 errors.
I'm using .NET Standard FWIW.


BaseOrder JSONfields default uses mutable dicts

https://docs.djangoproject.com/en/1.9/ref/contrib/postgres/fields/#jsonfield
I'm not 100% sure if this applies to to jsonfield.JSONField  but I think this should be changed
from default={}
to
default=dict for
BaseOder.extra and BaseOrder.stored_request

Hi @simonfloris
thanks for pointing this out.
Currently djangoSHOP uses https://pypi.python.org/pypi/django-jsonfield which is portable across databases. The JSONField you refer to, is specific to Postgres only, hence not portable.
I might create a wrapper which uses whatever is more suitable to the used database. I just reread the docs from jsonfield.JSONField and it states:
If no default is provided, and null=True is not passed in to the field constructor, then a default of {} will be used.

Therefore I removed all occurrences of default={}.

Feel free to implement #398


Document that data_path in custom queries cannot contain wildcards

What does this PR do?

Motivation

Additional Notes

Review checklist (to be filled by reviewers)

[ ] Feature or bugfix MUST have appropriate tests (unit, integration, e2e)
[ ] PR title must be written as a CHANGELOG entry (see why)
[ ] Files changes must correspond to the primary purpose of the PR as described in the title (small unrelated changes should have their own PR)
[ ] PR must have changelog/ and integration/ labels attached
[ ] If the PR doesn't need to be tested during QA, please add a qa/skip-qa label.

Current dependencies on/for this PR:

master

PR #14551   👈

This comment was auto-generated by Graphite.


System.AggregateException

Running the PowerShell script "Fetch - Run.ps1" as normal with default full refresh cadence of 30days returned the below error after serveral days. The issue appered during the catalog part.
I'm wondering, if there is a certain file size limit for the catalog json files. The file size of the full refresh json files is ~30-70MB, while for the incremental refreshed I get up to 200MB.

This issue didn't happen anymore since. Maybe was just a one-off

This issue didn't happen anymore since. Maybe was just a one-off


Offset not working as expected

Describe the bug
Whatever I put in the offset property, it seems to have no effect.
I would expect if I put e.g. value 10, that I should not get information about departures that are in less than 10 minutes. However I do , although next two departures are in 7 and 17 minutes, I am still shown departure due in 7 minutes.
Steps/data to reproduce the behavior, e.g.

configure offset in minutes value to e.g. 10
wait until departure is in less than 10 minutes
departure should not be shown, but it gets shown

Release used
gtfs2 release 0.3.8
HA OS core 2024.2.5

How long did you wait after applying the setting? It does not immediately apply, only after the next refresh. Only 3 days ago I tested this and it worked fine for me
As per the requests for any ticket...need more data to verify and please provide exact data, screenshots, etc.

Adding, this is part of previous code and what it seems to do is add X minutes to the departure time so that you can account for e.g. walking time to the stop. When I add e.g. 60 mins...the whole thing moves with ...60 mins

I am using data from Croatian transportation system in Zagreb located here:
https://www.zet.hr/odredbe/datoteke-u-gtfs-formatu/669
Direct link:
https://www.zet.hr/gtfs-scheduled/latest
Regarding configurations, there is not much to show, but here it is:
basic config:

second config screen:

how it is represented:

detailed calculation:

these times are regular times from schedule. They are correct departure times, not modified by the offset I put.
I would expect that times are either moved by the specified number of minutes or that they are not shown then they are less then specified amount of offset. If I understand your last comment, it should be the first option -that the times are actually moved by offset value.
Just to check, is the value that I need to put really in minutes (like it's specified in GUI), not seconds or milliseconds or something similar?  I can read python code, could you direct me to file where this is taken into account, perhaps I can figure out what could be wrong with my config?

OK, found the location, it moves current time (now) by the offset in minutes. Nothing wrong with the code, so my assumption is that the calculation is not executed on my side. But the config is inside for more than 24 hours, and it still does not takes it into consideration. What could I do to force recalculation?

I figured it out. I have put same value for data refresh (15 minutes) and offset (15 minutes).
Refresh time must be lower (more frequent) in order to get the desired effect, as otherwise it will too often recalculate too late.


[Feature] Support custom prefered response code for HTTP probe

@douglarek  Thanks for this contribution. My comments are as below:
It's better to use a range instead of only one status code. because 1xx , 2xx, 3xx, ... all of them represent success.
I think we can check the ranges something like:
success_code:
   - [200, 210]  # from 200 to 210
   - [300, 320] # from 300 to 320

So, the default range is  [0 - 499]

@douglarek Thanks for this contribution. My comments are as below:
It's better to use a range instead of only one status code. because 1xx , 2xx, 3xx, ... all of them represent success.
I think we can check the ranges something like:
success_code:
   - [200, 210]  # from 200 to 210
   - [300, 320] # from 300 to 320

So, the default range is [0 - 499]

thanks for the deep thought, @haoel , I will make some minor fix.

by the way, I think we can remove the >= 500 checking...


REPL: process is not defined

This issue appears to have crept back in https://github.com/sveltejs/svelte-repl/issues/105
Here is a minimal reproduction based on Tan's screenshot https://svelte.dev/repl/2c3f456eae7244399c24963d0195a5fb?version=3.49.0

Came upon this error as well. I was trying the @tanstack/table library for svelte.
For a quick fix, inserting a fake process object at the front did work.
globalThis.process = { env: { NODE_ENV: 'production' }};

Screenshot

process is only available in the Node global namespace and not in the browser global namespace. Offending packages should be fixed


feat: add ecsact support

Hi! I've developed and maintain a project called Ecsact. We've made an LSP server for our language and I'd love to include it in nvim-lspconfig as I am a big neovim user myself!

I missed my make lint in my previous push. I've re-ran it and force pushed now.

does this server not support windows?

please squash and use correct commit format then force push.

Thanks for the review and the patience :)


Added new template variable {{noteCreatedDateTime}}

Hi!
I miss the option to paste note created date with date and time. I've simply added another variable for that, but in future it probably better to give users option to configure format.

Looks nice. I'm merging it

I will deploy this change with other fixes next week


Unable to revert merge commit because RevertOptions cannot be passed in NodeGit

I am trying to revert a branch commit by using the Revert.revert() and trying to pass in the RevertOptions, but I am unable to create that instance to give it the necessary values. I get a  "Property 'RevertOptions' does not exist on type 'typeof'...".
I am using Typescript. I wrote it as:
const revertOpts = new NodeGit.RevertOptions();
and get that error, however I have no problems when creating an instance of MergeOptions. Also noticed that RevertOptions is also an interface while MergeOptions is a class
Am I doing this correctly?

Construct your options as a plain object. The object will magically convert into revert options along the way.

Construct your options as a plain object. The object will magically convert into revert options along the way.

I tried what you recommended:
NodeGit.Revert.revert(gitRepo, commitid, {mainline: 1});
And I got a Segmentation Fault. Passed in the object with all the fields too
{checkoutOpts: null, mainline: 1, mergeOpts: null, version: null} , and get the same error.

I was able to reproduce this. Seems there was a slight error in Revert.revert on line 72 of revert.js

https://github.com/nodegit/nodegit/pull/1605 will solve the issue. Thanks for bringing this to my attention.


Support installing as Grunt/Gulp tasks.

It's possible to add Grunt tasks and Gulp tasks so that this tool can be used as part of a build script or testing.

@thinkingmedia Sorry this took so long to reply to. Massively not cool.
So - yes, that would be a good idea. We should do that. Do you know where to start with that/would you be interested in taking up the task?

@basicallydan yes, I can do a pull request for Grunt support.
I picture something like this running as a lint task. Have you ever used jslint?
https://github.com/douglascrockford/JSLint

@basicallydan
To run as a grunt task the forkability report needs to be generated using the current working directory. Is that possible? Looking at the index.js it appears setup to use the Github API only.
To be a grunt task it needs to generate the report on the folder before changes are pushed to Github.
Is this possible?

Hmm. This is intriguing, but would probably require a decently heavy rewrite of internals- or adding a new api that works on  local files.
Will add more feedback in the morning

I'm afraid that this wouldn't totally work. When using the directory we'd have to compromise on functionality. Forkability would still support:

Linting of files
Tags
Issues
The ignore file

But it wouldn't support:

Issues
Pull requests

I'm not saying that wouldn't be helpful, but it would mean essentially a "cut-down" configuration of Forkability.
And as @M-Zuber said, it would also mean a heavy re-write. I don't think it'd be very heavy though. Most of the re-writing would happen in lib/app.js since that's where the data retrieval step is. None of the lint*.js files make GitHub API requests. We'd merely need to get the structure of the specified directory and put it into a format which lintFiles.js understands.
I think if this is done we should create a generic API for data retrieval and the appropriate module can be selected. I'm sure there are good modules out there for understanding local git data, too.
I'm personally OK with this, but IMO organisation is really important, or we risk polluting app.js. And we need to make it really clear to users what they're compromising on. @M-Zuber thoughts?

Great write up.
I was thinking of initially simply creating two modules: one that encapsulates the current functionality, and the other that works over a local directory.
Then the refactor can be very simple:

Add a flag to lint a local directory
If it was not sent, just lint using the github api.

As far as code reuse goes, that can even be done at a later date.
Such a structure may also enable us to support other sites in the future.
Did I answer all your points?

@M-Zuber Yep, sounds like we're on the same page.
So for the gulp/grunt tasks it'd use the flag.
We might need a few modules though. One for looking at files and one for getting the tags from the .git directory. Having said that, do you know @M-Zuber if it's possible that not all the tags will be brought over when cloning the repo?

Also, if we're gonna do this let's make two more issues: One for creating a local directory structure retriever which has a function to produce the data in the appropriate format, and one for a module to retrieve tags.
@M-Zuber We agreed this is a good idea?!

Great idea! :shipit:
re tags not being brought over, I have no idea but will tweet some people

I think this just grew in complexity beyond what I can do at this stage, but having written many grunt tasks. I'd be happy to help add the grunt support when you're ready.

@thinkingmedia Cool - that's totally reasonable, thank you.


hough lines - osx only

Subsumes #54, partially closes #50

But what about iOS? What is the problem of porting it to iOS also ?

I've ported it to iOS today. I'll commit it on weekend. You also forgot to call deallocate/free after allocating data for lines, which caused memory leak and app crash. Fixed. Just wait till this weekend

Thanks!  I haven't looked at this in a long time. Glad to see it finally
got sorted out.
Max
On Thu, Mar 30, 2017 at 9:13 AM, Denis Grebennicov<EMAIL_ADDRESS>
wrote:

I've ported it to iOS today. I'll commit it on weekend. You also forgot to
call deallocate/free after allocating data for lines, which caused memory
leak and app crash. Fixed. Just wait till this weekend
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/BradLarson/GPUImage2/pull/94#issuecomment-290461248,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAneTHgUcSNMwO53EZAJ-uPT6XwW5Mcyks5rq9SOgaJpZM4K-hrM
.


04/22/2018 18:04 : Create Pull Request for branch prTesting_2018042218 -> master

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

split/updateTestRef.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


LANG-1604: Deprecate RandomUtils class

jira issue - https://issues.apache.org/jira/browse/LANG-1604

Codecov Report

Merging #936 (3daf5df) into master (ceb7fbb) will decrease coverage by 0.00%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##             master     #936      +/-   ##
============================================
- Coverage     92.01%   92.01%   -0.01%
+ Complexity     7436     7435       -1
============================================
  Files           189      189
  Lines         15751    15751
  Branches       2961     2961
============================================
- Hits          14494    14493       -1
  Misses          672      672
- Partials        585      586       +1

Impacted Files
Coverage Δ

...ain/java/org/apache/commons/lang3/RandomUtils.java
97.22% <ø> (ø)

...apache/commons/lang3/reflect/ConstructorUtils.java
84.00% <0.00%> (-2.00%)
:arrow_down:

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


Wrong Date/Time Format on SK language

Originaly brought up in #63372 by @jans-y
I mean, this is allowed format:
2. 1. 2003
this works too:
02. 01. 2003
but this doesn't:
02.01.2003
Personally, I am not sure I have ever seen anybody in Slovakia "sk", put spaces after dots.
Double spaces or space at the end also doesn't work which is a common typo:

I am not sure what the bug is - what functionality of package:intl are you calling? As for the date formatting in Slovakian, the source of truth is the CLDR data which specifies the format with spaces after the numbers. If you disagree, consider filing a bug with there. Closing for now.


Heap Sort

I added the heap sort sorting algorithm and changed the array element swapping to take advantage of the built-in Kotlin functionality.

Thanks for the PR @goodnic . Merging it


Extend C# IntelliSence suggestions list to symbols out of current using directives.

VSCode Version: 1.4.0
OS Version: OS X El Capitan & Windows 10

It would be very handy to see in suggestions list classes that come from namespaces not used in the editable file. For example, when we start typing class name "EventHandler" we'll not see suggestion for it if "using System;" is not presented. Now we have only ability to type class name completely, expand light bulb and choose quick fix to add missing "using". But sometimes it is too hard to remember class name exactly and class names can be too long to type. This is why it would be good to include such classes in suggestions list.

@GuidC0DE Are you using the C# extension ?

@ramya-rao-a yes, I'm using this extension. Thank you for clarification! I'm sorry for posting it here.

@GuidC0DE no problem


Fix hook for Doctrine PDO class

When using doctrine the return type of PDO->prepare is Doctrine\DBAL\Driver\PDO\Statement and the hook didn't work. Changed the if to a match statement and added a bunch of debug statements. Fixed a minor typo.

Please format the code with: cargo +nightly fmt --all


feat: add template variables

Hello!
This PR adds some more variables that can be used in the footer template (basically everything available in the slide metadata):

{title}
{sub_title}
{location}
{event}
{date}

There may be a better way of including all the metadata in the FooterContext without having to repeat all the definitions?
Default Template
I tried to add a default footer template, but I couldn't seem to decouple the footer template itself from the template style.
The following template is very common in presentations and I think it would make a great default:
left: "{author}"
center: "{title}" # this can also be a short title
right: "{current_slide} / {total_slides}"

Ideally, I would like to just be able to set the style to template and have the default template used:
theme:
  override:
    footer:
      style: template

However, it seems I must manually define the template for all of my slides
Thanks!

Thanks!


Deprecated Gradle features were used

This appears in the logs:
Deprecated Gradle features were used in this build, making it incompatible with Gradle 5.0.
See https://docs.gradle.org/4.6/userguide/command_line_interface.html#sec:command_line_warnings

Narrowing down where's the problem. After building each subproject, the issue appears only in web.

> Task :web:webpack-config UP-TO-DATE
A problem was found with the configuration of task ':web:webpack-config'. Registering invalid inputs and outputs via TaskInputs and TaskOutputs methods has been deprecated and is scheduled to be removed in Gradle 5.0.
 - Directory '/home/piotr/repos/fsynth/web/webpack.config.d' specified for property '$1' does not exist.

It's caused by https://github.com/Kotlin/kotlin-frontend-plugin. Their README says that some configuration may be placed in webpack.config.d directory, and there's no such directory in fsynth/web. I'll add an empty directory to silence this warning.


Crash sending lighting tips

When sending a lightning tip, erase the value and the app crashes

+1


Update guessit to v3

Changes:

format -> source
Update video_codec values
Update audio_codec values
BluRay -> Blu-ray
Update guessit version requirement
WEB-DL -> Web
WEBRip -> Web
Fix usage.rst test
PEP8

We have been using this version with Medusa for quite some time now.

@Diaoul, @fernandog would be great if this could be merged. :wink:


m.Delete(key)  -> m.store.Delete(key)

https://github.com/asim/go-micro/blob/2653e7a977d31a03a9580b1aa62e1f7e6dae64f5/store/memory.go#L119

Did you lose the store?

Fixed


Question: Why does mamba use LayerNorm instead of RMSNorm?

according to https://arxiv.org/abs/1910.07467 RMSNorm is now considered to be a better choice (at least for transformer and related architectures).
Is there something specific to mamba that makes the performance advantage of RMSNorm not  relevant? or is there something specific in S4/mamba that makes LayerNorm a better choice for mamba?
Upon further examination of the code, it looks like RMSNorm is there, but it's unclear to me why it is gated? Can some kind soul clarify the reasoning behind this?
Thank you!

We use RMSNorm in Mamba.

We use RMSNorm in Mamba.

Thank you for your response. Are your mamba models in hf using RMSNorm? (your paper and parts of the code specifically mention LayerNorm, so I was wondering)

Afaik all Mamba and Mamba-2 models use RMSNorm.


Unable to locate Credentials

We have a Cloudformation template created and I am in the process of testing this using TaskCat.  Here’s the command I am using
taskcat -c awstaskcat/ci/config.yml -A "AKIAJXXXXXXXE6GEVXX" -S "V6k2XXXXXXXXXXXXXXXXXXXXXXXiiXX"
Although the Access and Secret Keys are valid, I am getting the following error message
"Unable to locate Credentials"
"Cannot launch XXXXXXXXX.template"

I got the same error
if I change to another template, the taskcat worked as expected, but another template met this error.
what will cause this error? any update.

Can you describe the differences bewteen the templates?
I need more info to reproduce this error
On Sep 29, 2017 7:21 PM, "zhenqing-zhang"<EMAIL_ADDRESS>wrote:

I got the same error
if I change to another template, the taskcat worked as expected, but
another template met this error.
what will cause this error? any update.
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
https://github.com/aws-quickstart/taskcat/issues/41#issuecomment-333275568,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AFo2QJS-TQdr10wVyp6bzFxWUxAPmd11ks5snaWSgaJpZM4PPrWH
.

@zhenqing-zhang when say "change templates" do you mean changed the filenames ? Can you tell me exactly what you did so I can replicate it.
Also please paste the error message.

Fixed in  https://github.com/aws-quickstart/taskcat/commit/da7644bbb4dc7954f834264163856fad8fd9c06d

I tried with same configuration with region set as us-east-1 and us-west-1. However, its throwing following error:
[ERROR  ] :Credential Error - Please check you keys!
My command is taskcat -c  -A ACCESS_KEY -S ACCESS_SECRET_KEY


[Bug]: Unhandled Promise Rejection Issue in JS ChromaClient Code post backup/restore

What happened?
Description:
I am encountering a problem with the ChromaClient in JavaScript, where it throws an UnhandledPromiseRejectionWarning. I have tried the JS client on different machines using different deployments. One deployment had no collections in it.
Surprisingly, the Python client continues to work flawlessly under the same conditions. The JavaScript client was functioning correctly until I backed up and restored the Chroma database using a Python script. Post that, the JavaScript client has consistently been throwing errors. This issue occurs during the execution of any method on the JavaScript client (e.g., version, heartbeat, etc.).
I have tested this scenario with the latest version of Chroma deployed using AWS CloudFormation but encountered the same issue. I have tried creating a local client on AWS to check the client and with the same result of UnhandledPromiseRejectionWarning.
Below are the Python scripts used for backup and restore operations which probably created the mess.
backup:
import pysqlite3
import sys
sys.modules['sqlite3'] = sys.modules.pop('pysqlite3')

import chromadb
from chromadb.config import Settings
from chroma_datasets.utils import export_collection_to_hf_dataset_to_disk,import_chroma_exported_hf_dataset_from_disk
import os
from chromadb.utils import embedding_functions

api_key = os.environ.get('OPENAI_API_KEY')

emb_fn = embedding_functions.OpenAIEmbeddingFunction(
                api_key=api_key,
                model_name="text-embedding-ada-002"
            )

collection_name = 'xxx'
data_path = './chroma_data'
# export
chroma_client = chromadb.HttpClient(host="x.x.x.x", port="8000")

collection = chroma_client.get_collection(name="Predictable-Dialogs", embedding_function=emb_fn)

export_collection_to_hf_dataset_to_disk(chroma_client, collection_name, data_path)

restore:
import pysqlite3
import sys
sys.modules['sqlite3'] = sys.modules.pop('pysqlite3')

import chromadb
from chromadb.config import Settings
from chroma_datasets.utils import export_collection_to_hf_dataset_to_disk,import_chroma_exported_hf_dataset_from_disk
import os
from chromadb.utils import embedding_functions

# https://github.com/chroma-core/chroma_datasets#utility-api-documentation

api_key = os.environ.get('OPENAI_API_KEY')

emb_fn = embedding_functions.OpenAIEmbeddingFunction(
                api_key=api_key,
                model_name="text-embedding-ada-002"
            )

collection_name = 'xxxx'
data_path = './chroma_data'
# export
chroma_client = chromadb.HttpClient(host="x.x.x.x", port="8000")

import_chroma_exported_hf_dataset_from_disk(chroma_client, data_path, collection_name, embedding_function=emb_fn)

Versions
I tried to check if the issue disappears with older or newer JS client versions, but the issue persists. I tried with JS client versions from 1.5.1 to 1.5.5.
Relevant log output
(node:14034) UnhandledPromiseRejectionWarning: #<Response>
(Use `node --trace-warnings ...` to show where the warning was created)
(node:14034) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
(node:14034) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

Well I must have easily spent 3 hours on this issue! but I am happy that I solved it. And since I am working for myself - I don't have a boss to judge me.
To resolve the problem I changed the code from:
const client = new ChromaClient({ path: 'http://localhost:8000/' });

TO
const client = new ChromaClient({ path: 'http://localhost:8000' });


fix(tag): update state to clear form on success

SUMMARY

Currently the state in the tags form isn't being cleared. So the values from a previous entry are staying whenever a user wants to create a new tag. To fix this I refactored the component to have a clearForm function that will clear the state in the component whenever called.
https://github.com/apache/superset/assets/27827808/4c731cd9-3ffc-4cdc-a218-46561cf8f5e4
BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF

TESTING INSTRUCTIONS

Goto Tags Page
Create a new tag (enter name + description)
Click Save
Click + Tag form should be empty

ADDITIONAL INFORMATION

[ ] Has associated issue:
[ ] Required feature flags:
[ ] Changes UI
[ ] Includes DB Migration (follow approval process in SIP-59)

[ ] Migration is atomic, supports rollback & is backwards-compatible
[ ] Confirm DB migration upgrade and downgrade tested
[ ] Runtime estimates and downtime expectations provided

[ ] Introduces new feature or API
[ ] Removes existing feature or API

@hughhhh would you mind adding some testing instructions and unit tests (if possible). I've also added @justinpark as a reviewer as it seems unclear why we need to clear the form, i.e., this seems like an atypical pattern.

Added test instructions, but the problem is when users are creating a Tag and save the form. The values are kept on the next instantiation of the modal, when they should it should be cleared for new data.

@justinpark would you mind reviewing this as I'm somewhat naive when it comes to frontend.


P/weardemo

@doneill I have pushed these changes. Please have a look.

Thanks @PuneetEsri, well done.


Feature: add option to ignore user/group already exists + user already a member of group

Description
When running user.add and user.group, add a boolean option to treat user already exist and user already a group member as not a failure.
Additional information
It would be very useful to simply make sure that the user account exists with the specified details, and not fail if the user already exists. Likewise for creating groups and adding users to groups.
If the user already exists, but any of the attributes are different, Comtrya should make the changes.

What you describe is how it should actually work, no extra Boolean required.
Comtrya actions have plan phases to determine if it needs to run, but existing user checks are missing for the user providers.

See PR #453


Xamarian.Forms Out of memory exception

I'm having a problem with the signature pad on android  under forms. After around 35 uses the app crashes with an OOM exception inside android. This was tested on a  J3 phone with version 2.1.1 With version 1.5.1 this problem doesn't happen, and I can repeat the calling of the page as many times as I like. I've attached a demo solution that exhibits this problem.
TestSignaturePad.zip
07-10 16:40:23.766 I/MonoDroid( 6196): UNHANDLED EXCEPTION:
07-10 16:40:23.886 I/MonoDroid( 6196): Java.Lang.OutOfMemoryError: Failed to allocate a 2851212 byte allocation with 632184 free bytes and 617KB until OOM
07-10 16:40:23.886 I/MonoDroid( 6196):   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw () [0x0000c] in <3fd174ff54b146228c505f23cf75ce71>:0
07-10 16:40:23.886 I/MonoDroid( 6196):   at Java.Interop.JniEnvironment+StaticMethods.CallStaticObjectMethod (Java.Interop.JniObjectReference type, Java.Interop.JniMethodInfo method, Java.Interop.JniArgumentValue* args) [0x00069] in :0
07-10 16:40:23.886 I/MonoDroid( 6196):   at Java.Interop.JniPeerMembers+JniStaticMethods.InvokeObjectMethod (System.String encodedMember, Java.Interop.JniArgumentValue* parameters) [0x00018] in :0
07-10 16:40:23.886 I/MonoDroid( 6196):   at Android.Graphics.Bitmap.CreateBitmap (System.Int32 width, System.Int32 height, Android.Graphics.Bitmap+Config config) [0x0005a] in :0
07-10 16:40:23.886 I/MonoDroid( 6196):   at Xamarin.Controls.InkPresenter.CreateBufferImage () [0x00047] in <1c8da6cdedc6484799a7f1284def41ac>:0
07-10 16:40:23.886 I/MonoDroid( 6196):   at Xamarin.Controls.InkPresenter.OnDraw (Android.Graphics.Canvas canvas) [0x00044] in <1c8da6cdedc6484799a7f1284def41ac>:0
07-10 16:40:23.886 I/MonoDroid( 6196):   at Android.Views.View.n_OnDraw_Landroid_graphics_Canvas_ (System.IntPtr jnienv, System.IntPtr native__this, System.IntPtr native_canvas) [0x0000f] in :0
07-10 16:40:23.886 I/MonoDroid( 6196):   at (wrapper dynamic-method) System.Object:05e98750-69cc-4ddd-bc25-2dbaafb6a9ad (intptr,intptr,intptr)
07-10 16:40:23.886 I/MonoDroid( 6196):   --- End of managed Java.Lang.OutOfMemoryError stack trace ---

We are experiencing a memory leak as well in the Android SignaturePad. We're running Xamarin.Forms version <IP_ADDRESS>0 and Xamarin.Controls.SignaturePad.Forms version 2.2.0.
We have a ContentPage with a SignaturePad.Forms.SignaturePadView control on it. When navigating to this page back and forth everything works as expected. When navigating to this page and draw something, then navigate back and again navigate to this page (with the SignaturePadView) and draw something (repeating this a couple of time), we also get the same exception as described above. We're not even calling the GetImageStreamAsync() method yet!
Could you investigate this issue, as we are running this on a Production environment. Might be that some Canvas, Bitmaps or something related doesn't get disposed properly inside the SignaturePad?

I`m having a same issue.

Xamarin.Forms <IP_ADDRESS>
SignaturePad.Forms version 2.1.0

After disposing the GetImagetStreamAsync() mehotd, calling the Clear() method bumps up a memory bit, but, still it occurs OutOfMemoryError. (In my case, 15+ times uses)

@mattleibow any updates on this issue?

Hey guys, I just wrote a detailed blog post on the subject. The workaround is to invoke explicit garbage collection after collecting the signature. I used Leonscape's TestSignaturePad solution to demonstrate how GC.Collect() helps.

Hi @markolazic88, thank you for your great detailed blog about this subject. Unfortunately the example that you've provided doesn't work how you've described it in your blog. The heap size isn't decreasing when a call to GC.Collect() has been made. In the Android Device Monitor I also got this strange error: "Invalid object in managed heap". This error also occurs when I hit the "Cause GC" button inside the Android Device Monitor tool and the heap size also won't shrink.

Hey @jBijsterboschNL, thanks for pointing this out.
Are you trying the example from my GitHub repo? I made a small mistake at line 27 of SignaturePage.xaml.cs, because I checked in GC.Collect(0) call instead of GC.Collect(). I was testing GC.Collect(0), which should perform only Minor collection on the Mono heap, but it does not do the trick for SignaturePad. You can see in the blog post that I was referring to GC.Collect() call. Also make sure that the line we are talking about is uncommented. It is commented out by default to demonstrate that the issue exists.
Android Device Monitor works for me fine. Try other device (I am working on VS Android Emulator), or maybe something is not properly installed on your machine.
Android "Cause GC" will not shrink heap size in this case, as Xamarin is still holding the reference to the bitmap image. When GC.Collect() is called, it will remove the reference and then it will call Android "Cause GC", which now is able to remove the big image.

Hi @markolazic88, thanks for your quick reply. This morning I did try several attempts and I'd also noticed that there was a call to GC.Collect(0) and thought I'd also tested it with the default call GC.Collect(). Apparently not, because now it is working as you've described. Thanks for your assistance!

I know this is an old issue, but is it still happening? I have been updating the project and trying to get all the fixes in for a brand new release.
It may have been an issue with Xamarin.Forms or it may be SignaturePad. Times have changed, and things have improved. Hopefully.
If you want to try out the latest bits from the CI system, you can get them here: https://jenkins.mono-project.com/user/mattleibow/my-views/view/Interesting/job/Components-SignaturePad-Windows/lastSuccessfulBuild/Azure/
I hope to release a preview soon so that this can tested in the real world due to some major improvements.

@mattleibow it is still reproduced

I found that error. When i check all code, there is error type value properti.

@ehansenp please create PR: https://github.com/VladislavAntonyuk/SignaturePad


SyntaxError: Unexpected token ...

$ node sentry-symbols.js
error
...options,
^^^
SyntaxError: Unexpected token ...
at createScript (vm.js:74:10)
at Object.runInThisContext (vm.js:116:10)
at Module._compile (module.js:533:28)
at Object.Module._extensions..js (module.js:580:10)
at Module.load (module.js:503:32)
at tryModuleLoad (module.js:466:12)
at Function.Module._load (module.js:458:3)
at Function.Module.runMain (module.js:605:10)
at startup (bootstrap_node.js:158:16)
at bootstrap_node.js:575:3

What version of node are you using? I guess you're using a version which doesn't support the spread syntax.

node:8.2.1   electron:1.8.4

The node version you are quoting here is suspiciously the one shipped with v1.8.4 of Electron. I'm asking which version of node you have installed on your system. You can get this by running:
node -v

node:8.2.1

What is the minimum supported version of node?

We have just released v3.0.0 of the SDK which includes a lot of changes and improvements since this issue was opened.
If you can still reproduce this with v3, please open a new issue and I'll look into it.