Bug in slick.min.js

Bug in slick.min.js (slick.js works well)

====================================================================
Use this jsfiddle to reproduce bug:
https://jsfiddle.net/barbaris/bx4dmu19/8/
If you click prev / next buttons images in bottom carousel will be moved.
Here is the same page with not minimized JS
https://jsfiddle.net/barbaris/bx4dmu19/7/
====================================================================
Steps to reproduce the problem

Click next / prev buttons on both pages
On page with minimized slick.min.js nav carousel moves.

====================================================================
What is the expected behaviour?
Navigation carousel should not move if number of slides is less then slidesToShow parameter
====================================================================
What is observed behaviour?
When I use minimized slick.min.js file transform style is updated for nav carousel
transform: translate3d(-100px, 0px, 0px);

====================================================================
More Details

Kubuntu 16.04
Google Chrome Version 66.0.3359.181 (Official Build) (64-bit)
jQuery 2.1.13
Slick 1.8.1?
It works well with not minimized slick.js

Regards,
Alex.

Yeah i came across the exact same issue today.
Can confirm using unminified Slick.js resolved issue for me too.
I minified the Slick.js myself and it also works.
Must be the way Slick.min.js is being minified?
Cheers,
Henry


Enforce Import Sort Order

@RyanMacBern suggests: "import/order": [ "error", { "groups": ["object", "builtin", "external", "internal", "parent", "sibling", "index"] } ],

+1 from me @JCarmine @RyanMacBern

JS sort order is being enforced out-of-the-box, however, there is no rule for ensuring that css imports go last. I think this is more of a style choice that we just need to enforce our selves.


Remove GRPC API from http_server and kythe tools [phab:D1340]

Created by schroederc at 2017-02-15 00:50:48:

zarko wrote at 2017-02-15 01:10:42:
I have some downstream stuff that depends on gRPC; please give me a couple of days to drop these dependencies before we land this.

zarko required changes at 2017-02-15 01:10:42

zarko wrote at 2017-02-16 06:00:06:
Fixed the aforementioned stuff.

zarko accepted this revision at 2017-02-16 06:00:06

schroederc closed via commit 8d52d8d7bf5a15f80959e5a089e6b0eac4e2dc4d at 2017-02-16 17:06:52


Add cleanup option and test for file path on use.

Cleanup is accessed under -d.  Refactored out the score check as a separate function to be used for both cleanup and remove functions.  Also added Test-Path in z to check for file paths when determining the list of suitable options.

I would almost argue to remove the cleanup option and just exclude inaccessible paths from the list of possible selections to maintain a consistent nature to z.sh.

Can you please re-submit this to the development branch? Will be good to test this over the next few days

Sorry,  I didn't see that when I submitted the PR.   Will submit again to the other branch.


v0.4.1 doesnt compile with Java 1.8

I'm using retrolambda in my project but I do have targetCompatibility and sourceCompatibility to 1.7
Error:Error converting bytecode to dex:
Cause: Dex cannot parse version 52 byte code.
This is caused by library dependencies that have been compiled using Java 8 or above.
If you are using the 'java' gradle plugin in a library submodule add
targetCompatibility = '1.7'
sourceCompatibility = '1.7'
to that submodule's build.gradle file.
...while parsing pub/devrel/easypermissions/AfterPermissionGranted.class

@loki666 yep 0.4.1 was a mistake, released 0.4.2 this morning which moves back down to 1.7 and should fix everything.  Give it a try!


Use full path when generating typedefs for message type

Hi!
I have notice that running foxglove with the bridge show some errors when trying to parse /topics_and_raw_types for complex types. E.g. types that contains e.g. a header type. It cannot solve Header it needs the full path std_msgs/msg/Header.
See console errors from browser below
3524.0ed3d11ba3fb8482838c.js:79 Error: Expected 1 top level type definition for 'Header' but found 0     at f (5820.27f2c9eaba8daa4be416.js:32:1250)     at 5820.27f2c9eaba8daa4be416.js:32:487     at Array.forEach (<anonymous>)     at 5820.27f2c9eaba8daa4be416.js:32:408     at Array.forEach (<anonymous>)     at e (5820.27f2c9eaba8daa4be416.js:32:371)     at t (5820.27f2c9eaba8daa4be416.js:32:338)     at #T (3524.0ed3d11ba3fb8482838c.js:79:22247)
(anonymous) @ 3524.0ed3d11ba3fb8482838c.js:79 3524.0ed3d11ba3fb8482838c.js:79 Player problem requestTopics:error {severity: 'error', message: 'Failed to fetch topics from rosbridge', error: Error: Expected 1 top level type definition for 'Header' but found 0     at f (https://app.foxglove…}
This fix solves the errors

Hi, thanks for the fix!
It was working with Foxglove before, so I assume something has changed in Foxglove recently.


fix name of Duration metric in the analyzer

The analysis executable assumed that the name of the test duration metric was "duration", with a lowercase D, which caused the MetricValues dictionary to throw since the duration metric is called "Duration", with an uppercase D. This PR lifts that value into a constant and fixes all occurrences of referring to the duration metric in this dictionary with a lowercase D.

Thanks!


How to configure toolbar items?

I'm new to ng-quill and want to know how to configure the editor's toolbar items.
I found some instructions on http://ngmodules.org/modules/ngQuill and thought I can use toolbar attribute and toolbar-entries as stated but the result is different from I expected:

Am I using the directive in a wrong way? I was expecting either the toolbar got hidden or the toolbar items got set according to the value (or both)
You may refer to https://codepen.io/louiscth/pen/bgyKMB
BTW, My runtime environment is Ubuntu 14.04 with Chrome Version 56.0.2924.87

naaaa ngmodules is crappy --> read the readme here ;). There is no toolbar-entries any longer in the new version.
https://github.com/KillerCodeMonkey/ng-quill/blob/develop/README.md
the default toolbar configuration looks like this:
modules: {
    toolbar: [
        ['bold', 'italic', 'underline', 'strike'],        // toggled buttons
        ['blockquote', 'code-block'],

        [{ 'header': 1 }, { 'header': 2 }],               // custom button values
        [{ 'list': 'ordered' }, { 'list': 'bullet' }],
        [{ 'script': 'sub' }, { 'script': 'super' }],      // superscript/subscript
        [{ 'indent': '-1' }, { 'indent': '+1' }],          // outdent/indent
        [{ 'direction': 'rtl' }],                         // text direction

        [{ 'size': ['small', false, 'large', 'huge'] }],  // custom dropdown
        [{ 'header': [1, 2, 3, 4, 5, 6, false] }],

        [{ 'color': [] }, { 'background': [] }],          // dropdown with defaults from theme
        [{ 'font': [] }],
        [{ 'align': [] }],

        ['clean'],                                         // remove formatting button

        ['link', 'image', 'video']                         // link and image, video
    ]
}

and you can pass modules-config object to the ng-quill-editor component --> it is explained in the readme. and there is a demo.html in the root of this repo, with some usage examples.
you can even build your own toolbar following the guides on quilljs:
http://quilljs.com/playground/#custom-fonts
simply pass something like this as module config { toolbar: '#IDofMyToolbarElement' }.
Please close the issue on your own, if this helps and you get it, Thanks.

Thank you for pointing me that the toolbar-entries no longer exists.
By passing the module config as you suggested, I can now reference the toolbar to the DOM.
I've seen in https://killercodemonkey.github.io/ng-quill/demo.html how you control the 'read-only' status , so I expected the toolbar attribute should be the same (since in the readme, there is a line

show toolbar: toolbar="isVisible" (default: false)

My goal is to show/hide the toolbar on the fly, so I copied the way you use to set read-only in my 2nd editor,

The 'toggle readOnly' function works just fine as in the demo page, but 'toggle visibility' button doesn't do anything for me. I can of course hide the toolbar by using ng-hide in the toolbar container DOM like what I did with the 1st editor, but I thought I can use toolbar="xxx" directly... Would you mind giving me some suggestion on the toolbar usage?
I've created another codepen just for reference:
https://codepen.io/louiscth/pen/PWvBBE
Thanks.

there is not toolbar option in the newer ngquill version, just an invalid readme sorry ;)
just disable the toobar via modules config if the editor is initialized.
There was no need toggle toolbar on the fly.

I released a new version an updated the readme. sorry for the confusion.


🐞 - Svg throws Assertion failed: Failed to load external SVG during SSR

Playground Link
https://github.com/Tinkoff/maskito/actions/runs/4572709295/jobs/8072254292
Description

Open logs of prerender job https://github.com/Tinkoff/maskito/actions/runs/4572709295/jobs/8072254292
They contain

Assertion failed: Failed to load external SVG assets/icons/github.svg

Reproduction
<a
    tuiLink
    tuiMode="onLight"
    href="https://github.com/tinkoff/maskito"
    title="Maskito source code on GitHub"
    rel="noreferrer"
    iconAlign="left"
    icon="assets/icons/github.svg"
    target="_blank"
    class="link"
></a>

Run nx serve-ssr
Taiga UI version
3.22.0
Which operating systems have you used?

[X] macOS
[ ] Windows
[ ] Linux
[ ] iOS
[ ] Android

https://github.com/Tinkoff/maskito/blob/34622646ea1d78428ff0298a9868dbcbcf11c468/projects/demo/src/app/app.component.html#L3-L13

Error is thrown here:
https://github.com/Tinkoff/taiga-ui/blob/856bc574815a7749e86f405b777cc95d686fe55f/projects/core/components/svg/svg.component.ts#L189-L191
It happens because TuiStaticRequestService uses legacy XMLHttpRequest
https://github.com/Tinkoff/taiga-ui/blob/856bc574815a7749e86f405b777cc95d686fe55f/projects/cdk/services/static-request.service.ts#L19
and it causes this error during SSR:
ReferenceError: XMLHttpRequest is not defined

In this PR legacy XMLHttpRequest was replaced by modern fetch:

https://github.com/Tinkoff/taiga-ui/pull/4258

It was just a small refactor (since Taiga 3.x.x all our required browser supports fetch).
But problem still persists - no external icons after SSR.
Even with Node.js >18.0.0 (this version introduces built-in support of fetch).

Maybe it's a sanitizing issue now?

The new error is the following:
ERROR Error: Uncaught (in promise): TypeError: Failed to parse URL from assets/images/github.svg
ERROR Error: Uncaught (in promise): TypeError: Failed to parse URL from assets/images/github.svg
TypeError: Failed to parse URL from assets/images/github.svg
    at new Request (node:internal/deps/undici/undici:7043:19)
    at fetch2 (node:internal/deps/undici/undici:10598:25)
    at Object.fetch (node:internal/deps/undici/undici:11455:18)
    at fetch (node:internal/process/pre_execution:230:25)
    at /Users/n.barsukov/WebstormProjects/taiga-ui/dist/demo/server/main.js:207285:36
    at proto.<computed> (/Users/n.barsukov/WebstormProjects/taiga-ui/dist/demo/server/main.js:206744:24)
    at Observable._subscribe (/Users/n.barsukov/WebstormProjects/taiga-ui/dist/demo/server/main.js:192657:9)
    at Observable._trySubscribe (/Users/n.barsukov/WebstormProjects/taiga-ui/dist/demo/server/main.js:191268:25)
    at Observable.subscribe (/Users/n.barsukov/WebstormProjects/taiga-ui/dist/demo/server/main.js:191254:22)
    at SwitchMapOperator.call (/Users/n.barsukov/WebstormProjects/taiga-ui/dist/demo/server/main.js:195137:23)
    at resolvePromise (/Users/n.barsukov/WebstormProjects/taiga-ui/dist/demo/server/main.js:206978:31)
    at /Users/n.barsukov/WebstormProjects/taiga-ui/dist/demo/server/main.js:206885:17
    at Object.reject (/Users/n.barsukov/WebstormProjects/taiga-ui/dist/demo/server/main.js:206901:33)
    at fetch2 (node:internal/deps/undici/undici:10600:11)
    at Object.fetch (node:internal/deps/undici/undici:11455:18)
    at fetch (node:internal/process/pre_execution:230:25)
    at /Users/n.barsukov/WebstormProjects/taiga-ui/dist/demo/server/main.js:207285:36
    at proto.<computed> (/Users/n.barsukov/WebstormProjects/taiga-ui/dist/demo/server/main.js:206744:24)
    at Observable._subscribe (/Users/n.barsukov/WebstormProjects/taiga-ui/dist/demo/server/main.js:192657:9)
    at Observable._trySubscribe (/Users/n.barsukov/WebstormProjects/taiga-ui/dist/demo/server/main.js:191268:25) {
  rejection: TypeError: Failed to parse URL from assets/images/github.svg
      at new Request (node:internal/deps/undici/undici:7043:19)
      at fetch2 (node:internal/deps/undici/undici:10598:25)
      ... 5 lines matching cause stack trace ...
      at Observable._trySubscribe (/Users/n.barsukov/WebstormProjects/taiga-ui/dist/demo/server/main.js:191268:25)
      at Observable.subscribe (/Users/n.barsukov/WebstormProjects/taiga-ui/dist/demo/server/main.js:191254:22)
      at SwitchMapOperator.call (/Users/n.barsukov/WebstormProjects/taiga-ui/dist/demo/server/main.js:195137:23) {
    [cause]: TypeError [ERR_INVALID_URL]: Invalid URL
        at new NodeError (node:internal/errors:399:5)
        at new URL (node:internal/url:560:13)
        at new Request (node:internal/deps/undici/undici:7041:25)
        at fetch2 (node:internal/deps/undici/undici:10598:25)
        at Object.fetch (node:internal/deps/undici/undici:11455:18)
        at fetch (node:internal/process/pre_execution:230:25)
        at /Users/n.barsukov/WebstormProjects/taiga-ui/dist/demo/server/main.js:207285:36
        at proto.<computed> (/Users/n.barsukov/WebstormProjects/taiga-ui/dist/demo/server/main.js:206744:24)
        at Observable._subscribe (/Users/n.barsukov/WebstormProjects/taiga-ui/dist/demo/server/main.js:192657:9)
        at Observable._trySubscribe (/Users/n.barsukov/WebstormProjects/taiga-ui/dist/demo/server/main.js:191268:25) {
      input: 'assets/images/github.svg',
      code: 'ERR_INVALID_URL'
    }
  },
  promise: ZoneAwarePromise [Promise] {
    __zone_symbol__state: 0,
    __zone_symbol__value: TypeError: Failed to parse URL from assets/images/github.svg
        at new Request (node:internal/deps/undici/undici:7043:19)
        at fetch2 (node:internal/deps/undici/undici:10598:25)
        ... 5 lines matching cause stack trace ...
        at Observable._trySubscribe (/Users/n.barsukov/WebstormProjects/taiga-ui/dist/demo/server/main.js:191268:25)
        at Observable.subscribe (/Users/n.barsukov/WebstormProjects/taiga-ui/dist/demo/server/main.js:191254:22)
        at SwitchMapOperator.call (/Users/n.barsukov/WebstormProjects/taiga-ui/dist/demo/server/main.js:195137:23) {
      [cause]: [TypeError]
    }
  },
  zone: <ref *1> Zone {
    _parent: Zone {
      _parent: null,
      _name: '<root>',
      _properties: {},
      _zoneDelegate: [_ZoneDelegate]
    },
    _name: 'angular',
    _properties: { isAngularZone: true },
    _zoneDelegate: <ref *2> _ZoneDelegate {
      _taskCounts: [Object],
      zone: [Circular *1],
      _parentDelegate: [_ZoneDelegate],
      _forkZS: null,
      _forkDlgt: null,
      _forkCurrZone: null,
      _interceptZS: null,
      _interceptDlgt: null,
      _interceptCurrZone: null,
      _invokeZS: [Object],
      _invokeDlgt: [_ZoneDelegate],
      _invokeCurrZone: [Circular *1],
      _handleErrorZS: [Object],
      _handleErrorDlgt: [_ZoneDelegate],
      _handleErrorCurrZone: [Circular *1],
      _scheduleTaskZS: [Object],
      _scheduleTaskDlgt: [_ZoneDelegate],
      _scheduleTaskCurrZone: [Circular *1],
      _invokeTaskZS: [Object],
      _invokeTaskDlgt: [_ZoneDelegate],
      _invokeTaskCurrZone: [Circular *1],
      _cancelTaskZS: [Object],
      _cancelTaskDlgt: [_ZoneDelegate],
      _cancelTaskCurrZone: [Circular *1],
      _hasTaskZS: [Object],
      _hasTaskDlgt: [_ZoneDelegate],
      _hasTaskDlgtOwner: [Circular *2],
      _hasTaskCurrZone: [Circular *1]
    }
  },
  task: ZoneTask {
    _zone: <ref *1> Zone {
      _parent: [Zone],
      _name: 'angular',
      _properties: [Object],
      _zoneDelegate: [_ZoneDelegate]
    },
    runCount: 0,
    _zoneDelegates: null,
    _state: 'notScheduled',
    type: 'microTask',
    source: 'Promise.then',
    data: ZoneAwarePromise [Promise] {
      __zone_symbol__state: true,
      __zone_symbol__value: [NgModuleRef$1]
    },
    scheduleFn: undefined,
    cancelFn: undefined,
    callback: [Function (anonymous)],
    invoke: [Function (anonymous)]
  }
}

Reproduction

Open Taiga UI project
Execute nvm use 18
Run nx serve-ssr demo
Open http://localhost:4200

We no longer load SVGs manually


Create subclasses for types of locations

Proposal:

Add class gist:Location
Rename gist:Place (a physical place) to gist:PhysicalLocation and make it a subclass of gist:Location
Add gist:VirtualLocation, also a subclass of gist:Location
Same predicate used for all three - gist:hasLocation.
Physical place located by a street address, geo points, etc.
Virtual location located by URL, file path, etc.

In English, place and location are virtually identical in meaning.   We already use gist:Place as the generic "any possible answer to a 'where' question", but if there is a good reason we could rename it to be gist:Location. Whatever we choose, the two subclasses should be prefixed by 'Physical' and 'Virtual'.

same predicate for all three

There lots of predicates that can point to a place.  I have a birth place and I have a residence and I have where I am sitting right now, which I wish was on a mountain top watching a sunset.

Physical place identified by a street address, geo points, etc
Virtual location identified by URL, etc

identifiedBy has range of ID, not Content.  Its a bit tricky relating a building address to a physical location.  You can think of web address or a zoom adddress as virtual places that you go to.  I don't know the best way to do that.

Jamie's use case: where can I find the data that I want to point to? E.g., this named graph in this dataset. This use case is solved by the resolution of #483, so we will leave it in review.

Won't fix. Distinction between VirtualLocation and its address isn't clear, and there are no urgent use cases.

This keeps coming up. It came up again today: #1009

Closing - the address working group has not found a need to model different types of locations.


Fork cereal submodule, add hasEPB to carParams

This will probably require manually updating everyone...

Fork is complete:
https://github.com/opgm/cereal
https://github.com/opgm/openpilot/commit/0b8097a315c6d2fb635aad2b38e5efde61a17bc5


Allow sending the actual selection without expanding to the full line

Current behaviour: If nothing is selected, the current line is send to 3ds Max (when using send_selection_to_max). If multiple lines are (partially) selected, the selection is expanded to the complete lines and send to 3ds Max.
Desired behaviour (could be an additional command or an option to the existing one): When a region in the code is selected, send only that region to 3ds Max. Example:
if sme.isOpen() do (
    ....
)

When just selecting sme.isOpen() and sending that, 3ds Max will instead receive: if sme.isOpen() do ( and thus fail to execute that snippet due to syntax errors. It should only receive sme.isOpen() which is valid MAXScript.

The new behaviour can be very simply enabled by replacing: https://github.com/cb109/sublime3dsmax/blob/master/sublime3dsmax.py#L141 with: regiontext = self.view.substr(region) and removing the then-obsolete lines 138-140.

We could allow both behaviours by configuring the send_selection_to_max command with an extra argument.

Actually configuring this would be overkill. Empty and multiline selections will be expanded to whole lines, selecting something on a single line will send exactly that. Implemented in: https://github.com/cb109/sublime3dsmax/commit/69c19cccdce377c7a39969fd4b0fac4945f7864b


Problem with percents in chart(using mode 2)

Hi. I have doing charts with lightweight-charts. And i have bug and i don't know how i can fix it. Bug: I push data like {time: "2021-03-23", value: 32.20} (i did parseFloat). But if i use "mode: 2" in options(i need it), i have troubles with percents on chart. If i push value "32.30", on chart it will be 3220%. But it should be 32.20%, and it was write in documentation. If i don't use "mode: 2", it works right. What i should do, to fix this? I need your help, please.
Code of my React component:
import React, {Component} from 'react';
import { createChart } from 'lightweight-charts';
import moment from "moment";

export default class BigChart extends Component
{
  constructor(props)
  {
    super(props);

    this.mounted = false
  }

  getOptions(width, height)
  {
    return {
      width: width,
      height: height,
      priceScale: {
        scaleMargins: {
          top: 0.2,
          bottom: 0.2,
        },
        borderVisible: false,
        mode: 2,
      },
      timeScale: {
        scaleMargins: {
          top: 0.2,
          bottom: 0.2,
        },
        borderVisible: false,
        mode: 2
      },
      layout: {
        backgroundColor: this.props.backgroundColor,
        textColor: '#fff',
      },
      grid: {
        horzLines: {
          color: false,
        },
        vertLines: {
          color: false,
        },
      },
    }
  }

  getContainer(width, height)
  {
    var container = document.createElement('div');

    var chart = createChart(container, this.getOptions(width, height));

    // chart.resize(height, width);

    var areaSeries = chart.addAreaSeries({
      symbol: '%',
      topColor: this.props.lineColor,
      lineColor: this.props.lineColor,
      bottomColor: 'transparent',
      lineWidth: 1,
    });

    let data = [];
    let startRange = moment();
    let endRange = moment();

    if(this.props.data.length > 0)
    {
      data.push({
        time: moment(this.props.data[0].date, "YYYY-MM-DD").utc().valueOf(),
        value: 1
      })
    }

    this.props.data.map((item, i) => {
      if(i === 0)
      {
        startRange = moment(item.date, 'YYYY-MM-DD').utc().valueOf();
      }

      if(i === this.props.data.length - 1)
      {
        endRange = moment(item.date, 'YYYY-MM-DD').utc().valueOf();
      }

      data.push({
        time: moment(item.date, 'YYYY-MM-DD').utc().valueOf(),
        value: item.bal,
      });
    });

    chart.timeScale().setVisibleRange({
      from: startRange,
      to: endRange,
    });
    chart.timeScale().fitContent();

    areaSeries.setData(data);

    areaSeries.applyOptions({
      baseLineVisible: true,
      baseLineColor: '#ff0000',
      baseLineWidth: 1,
      baseLineStyle: 1,
    });

    return container;
  }

  render()
  {
    return <div style={{
      width: this.props.width,
      height: this.props.height + 'px',
    }} onClick={(e) => {
      if(typeof this.props.onClick !== 'undefined')
      {
        this.props.onClick(e);
      }
    }} ref={(nodeElement) => {

      if(this.mounted === false)
      {
        nodeElement.appendChild(this.getContainer(nodeElement.getBoundingClientRect().width, this.props.height));
        this.mounted = true;
      }

      return nodeElement;
    }}/>
  }
}

Can you create jsfiddle repro please so we can debug it and see what's going on?

i have troubles with percents on chart. If i push value "32.30", on chart it will be 3220%. But it should be 32.20%, and it was write in documentation. If i don't use "mode: 2", it works right. What i should do, to fix this? I need your help, please.

Percentage mode != just display percent on the chart. Percentage mode shows you the change of a value relative to the first visible value, see https://github.com/tradingview/lightweight-charts/blob/7d9866e86b47e060dd175e08e46ad8ca7a2a5d06/src/model/price-scale-conversions.ts#L19-L22

If you'd like to show percentages, you can put a custom formatter to format your value like a percent


60x Slowdown Using Concurrency

Description

There seems to be a clear issue related to how lightgbm handles resource sharing. When restricting the number of cores associated with a process, the runtime increases significantly.
In the example provided below, the run time using all cores (0-15) is about 1.821 seconds. When restricting the process to all cores but one (0 - 14), the runtime increases to 109.31 seconds; more than a 60x increase. This only happens if the resource restriction is done from within the Python script. If the affinity is set beforehand using taskset -c 0-14 the runtime is approximately the same, 1.796 seconds.
This makes training multiple lightgbm models in parallel undesirable, at least if the subprocesses are called from within a Python script. As this a common pattern of implementing concurrency, this appears to be a limitation which can hopefully be easily addressed and fixed.
Thanks!
Reproducible example

lgbm_affinity.py
import argparse
import lightgbm as lgb
import numpy as np
import os

np.random.seed(42)

def main(use_setaffinity: bool = False, use_taskset: bool = False):

    n = os.cpu_count()

    # Set affinity using ``os.sched_setaffinity``
    if use_setaffinity:
        os.sched_setaffinity(0, set(range(n - 1)))
        os.environ['OMP_NUM_THREADS'] = str(n - 1)  # Added after suggestion

    # Set affinity using ``taskset``
    if use_taskset:
        pid = os.getpid()
        command = f"taskset -cp 0-{n - 2} {pid}"
        os.system(command)
        os.environ['OMP_NUM_THREADS'] = str(n - 1)  # Added after suggestion

    # Generate a data set
    nrows, ncols = 1_000, 10
    X = np.random.normal(size=(nrows, ncols))
    y = X @ np.random.normal(size=ncols) + np.random.normal(size=nrows)

    lgb_train = lgb.Dataset(X, y)

    # Train model
    params = {
        "objective": "regression",
        "metric": "rmse",
        "num_leaves": 31,  # the default value
        "learning_rate": 0.05,
        "feature_fraction": 0.9,
        "bagging_fraction": 0.8,
        "bagging_freq": 5,
        "verbose": 0
    }
    lgb.train(params, lgb_train)

if __name__ == "__main__":

    parser = argparse.ArgumentParser()

    parser.add_argument(
        "--use-setaffinity",
        dest="use_setaffinity",
        action="store_true",
    )

    parser.add_argument(
        "--use-taskset",
        dest="use_taskset",
        action="store_true",
    )

    args = parser.parse_args()
    main(**vars(args))

lgbm_affinity.sh
time python lgbm_affinity.py > /dev/null 2>&1
time python lgbm_affinity.py  --use-setaffinity > /dev/null 2>&1
time python lgbm_affinity.py  --use-taskset > /dev/null 2>&1
time taskset -c 0-14 python lgbm_affinity.py > /dev/null 2>&1

Output
# Using all cores
real    0m1.821s
user    0m4.394s
sys     0m0.178s

# Using ``set_affinity`` from within the process
real    1m49.313s
user    25m44.344s
sys     0m1.109s

# Using ``taskset`` from within the process
real    1m48.820s
user    25m54.104s
sys     0m0.959s

# Using ``taskset`` before initializing the process
real    0m1.796s
user    0m4.135s
sys     0m0.203s

Environment info
LightGBM version or commit hash:
liblightgbm  4.5.0    cpu_h155599f_3  conda-forge
lightgbm     4.5.0    cpu_py_3        conda-forge

Command(s) you used to install LightGBM
micromamba install lightgbm

Other used packages:
numpy     1.26.4   py312heda63a1_0  conda-forge

The example was run on an AWS instance (ml.m5.4xlarge) with 16 cores.
Additional Comments

Hey @JohanLoknaQC, thanks for using LightGBM.
By default LightGBM uses all available threads on the machine unless you tell it otherwise. So in your examples you're submitting n tasks and assigning only n - 1 threads, so they have to fight each other to execute them. I think the easiest way to fix this is by doing something like os.environ['OMP_NUM_THREADS'] = str(n-1), that way you tell LightGBM to use the number of threads that you've limited the process to have.

Thanks a lot for the answer! However, after adding the suggested fix (see code above) the run-times remains virtually unchanged. It does seem like something else might be causing this additional run-time.

Sorry, I think that only works if provided through the command line. Can you please set the num_threads argument instead? e.g.
    params = {
        "objective": "regression",
        "metric": "rmse",
        "num_leaves": 31,  # the default value
        "learning_rate": 0.05,
        "feature_fraction": 0.9,
        "bagging_fraction": 0.8,
        "bagging_freq": 5,
        "verbose": 0,
        "num_threads": n - 1,  # <- set this
    }

Thank you very much - this solved this issue.
Just for reference, it also worked when the affinities were set quite arbitrarily, e.g. 3-12. It therefore seems to a quite general solution. 👍


See over there,the "Home","Timer","Clock" are not aligned correctly and enough spacing is required..Under that copyright,2024 the whole line has to get enough alignment to make it perfect

@param-code @sanjay-kv @17arindam @samyak-aditya @HarshitShukla-dev
Please assign me this issue so that I can fix it and make it perfect

sure.

I've created a CSS file as well as html for the correction of the issue #70 ..Kindly check those files and please merge it into your project.Hope this helps..The alignment as well as spacing problem is gone.

Kindly merge it @param-code ..Please!!

See #74

@param-code

@param-code I am ready to contribute in this, could you please assign it to me?


Add connection pooler

Implement connection pooler value reads and toggling in the terraform provider

closes https://github.com/timescale/terraform-provider-timescale/issues/142

I might worth adding the test into our integration test suite, WDYT @Khyme ?


[WIP]Feature/nodejs request sdkgen

Adds nodejs-request sdkgen.

Adds basic boilerplate
Adds sdk which has the following

folder structure
variables (partially completed)

basic tests for generate function

@someshkoli Can you move the npm/boilerplate changes to a different branch? It's making this PR too big to review.
Also, all the changes in output/* can be put in .gitignore these are for your local testing and not required to be in the Repo.

Okay sure

By adding the /output folder to .gitignore will avoid committing in the future. You will have to manually remove them from this branch now.

Yes yes have already made it locally, push soon

Overall looks good to me. Let me know when you make these changes^.
I will merge it and use it from my end and check.

Overall looks good to me. Let me know when you make these changes^.
I will merge it and use it from my end and check.

Actually I tried using the SDK without that thing and it was like a blackbox wich didn't indicate that wether we can use/set variable initially so added doc so that it can indicate the initial usage and variables which are available to for usage.

Overall looks good to me. Let me know when you make these changes^.
I will merge it and use it from my end and check.

Done

without that thing

What thing? Are you talking about class doc? Should reply to the comment that you are talking about.


FancyZones Layout Editor Space around zones not disabling

Microsoft PowerToys version
0.64.0
Installation method
PowerToys auto-update
Running as admin
Yes
Area(s) with issue?
FancyZones
Steps to reproduce
Open FancyZones Editor
Disable space around window
✔ Expected Behavior
Space to be removed
❌ Actual Behavior
Even if 'disabled', space still shows around window until brought to '0'.
Note, this started occurring since latest update.
Other Software
No response

/dup of https://github.com/microsoft/PowerToys/issues/21630


Include/Internal/arm_nn_compiler.h: undefined __ARM_FEATURE_MVE

Missing check that __ARM_FEATURE_MVE is defined before checking its value
Include/Internal/arm_nn_compiler.h:130
#if ((__ARM_FEATURE_MVE & 3) == 3) || (__ARM_FEATURE_MVE & 1)
    #include <arm_mve.h>
#endif

Update to:
#if defined(__ARM_FEATURE_MVE)
    #if ((__ARM_FEATURE_MVE & 3) == 3) || (__ARM_FEATURE_MVE & 1)
        #include <arm_mve.h>
    #endif
#endif

Thanks @matthewbstokes-zz for finding this. Feel free to raise a PR. We shall anyway fix it.


How to install this?

Any instruction about building this app?
My goal is the create a docker image out of it :)
Cheers!

Hi. You just need to compile it. No dependencies.

Sorry I don't know how.
I'm really good at packaging Dockerfile (per example) but without a clear instruction on how to install the package, I'm clueless. Thanks!

I guess it's similar to https://github.com/aktau/github-release#how-to-install
Thank you

sorry for the long reply. There are several options of how you can install it:

as you describe, just do go get github.com/ikruglov/slapper
clone the repo, and do go build in the repo's folder

hope this helps


Add "git commit" step to the "Get Streamers" workflow

I'm a bash noob so this could probably be cleaned up a bit.

Could the call to Vercel webhook we removed if this gets merged? If the workflow commits the changed json file won't Vercel trigger automatically?

Yeah if we the commit works - then there is no need to trigger it again - because it will use the usual webhook of a commit

True story @jwalter! Thanks! However, we need to put some secrets into GitHub and pipe them into the script somehow – as the environment variables in the .env file wont be available currently.

I think we found a way to have a commit of this file ready and keep the main branch commit history "clean"
If we create the json file but push it to a different branch like "stream-data" or something , which would be always force pushed
Then we could download this json (under the stream-data branch)  during the vercel build and with that we could have the best of both-worlds

True story @jwalter! Thanks! However, we need to put some secrets into GitHub and pipe them into the script somehow – as the environment variables in the .env file wont be available currently.

Wouldn't this be only the VERCEL_DEPLOY_GH_ACTION_HOOK env var? since the rest would be done by vercel anyway ?

No, main is now only loading data from the JSON file.
So the branch that generates the file via the action needs the secrets.
On Sun, 27 Jun 2021 at 18:37, negue @.***> wrote:

True story @jwalter https://github.com/jwalter! Thanks! However, we
need to put some secrets into GitHub and pipe them into the script somehow
– as the environment variables in the .env file wont be available currently.
Wouldn't this be only the VERCEL_DEPLOY_GH_ACTION_HOOK env var? since the
rest would be done by vercel anyway ?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/whitep4nth3r/womenwhostream.tech/pull/7#issuecomment-869199785,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AMS2HEJXAO7NUATU4MMRUZDTU5OTXANCNFSM47LX5SKQ
.

@jwalter what do you think can you change it to force push to a different branch?
Then I'd update the script to download the json file from a specific url (the upcoming new branch) and then at the end it'll all work out :) ... atleast if the plan works out ha

No, main is now only loading data from the JSON file.
So the branch that generates the file via the action needs the secrets.

oh those secrets ok ... yeah then we'd need them to be added to this repo too

Shall I add the secrets to the repo — some changes would need to be made in
the streamers script to load them. (I THINK.)
On Sun, 27 Jun 2021 at 18:40, negue @.***> wrote:

@jwalter https://github.com/jwalter what do you think can you change it
to force push to a different branch?
Then I'd update the script to download the json file from a specific url
(the upcoming new branch) and then at the end it'll all work out :) ...
atleast if the plan works out ha
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/whitep4nth3r/womenwhostream.tech/pull/7#issuecomment-869200359,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AMS2HELLMLR2RWKWWZ6T5QLTU5PBJANCNFSM47LX5SKQ
.

All env vars added to repo secrets! (Same names)

Changes LGTM - with this can already try the first dispatch to a branch and then I can start the download / build of this file


Feature stats

This is a draft PR about stats part in echoshader.
Modification, demo showcase and docstring will be added later.

For get_stats.py :  plot_side_hist is  reserved and opsional functions, not related to core business. plot_hist and plot_table return relative holoview object based on MVBS parameter.
For ehocgram.py:

histogram plots histogram with two modes optional, overlay and layout. There are 2 control widgets are bond to this function: bin_size_input and overlay_layout_toggle to tune bins and toggle mode. The plot is updated automatically without update button.
table plots stats info with N+1 columns (sum + n channels). The plot is also updated automatically without update button

Hey @ldr426 : I changed the PR target to dev (you originally had it targeting main) but it did not help with pulling the commits that you had from #122. I've just merged #122 to dev. Please merge the new dev into your branch feature-stats and then create a new PR, and hopefully we can see the clean commit history there. Make sure to resolve the conflicts and pre-commit error in the new PR. Thanks!


fix: #6719 remove validator on function categories access prompt

Issue #, if available: Fixes #6719
Description of changes:
Package: amplify-category-function
Removes the validator for the prompt question: 'Select the categories you want this function to have access to.'
Fixes bug where user had to have atleast one category selected. This PR allows user to deselect all category options during that prompt.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

@kaustavghosh06 I was working on a related issue so tested this PR. It works fine but it still prints info to the terminal.

Should we ensure that it prints info only if envVarStringList is not empty in the askExecRolePermissionsQuestions function code?


Microsoft Copilot Plugin doesn't give the OAuth token

Steps to reproduce
We have created a bot with search command message extension, we get a token from Microsoft bot framework This token comes on individual user chats when the search command extension is performed, and not on the M365 chat where we use Copilot plugin (same is the case with Copilot for Microsoft 365 App).
Expected behavior
The OAuth token is to come in M365 chat as it comes in individual user chats
Actual behavior
The OAuth token doesn't come in M365 chat as it comes in individual user chats
Error details
No response

Hello @vigneshsathisrikumar Thanks for raising your query, we will repro it and get back to you soon.

Hello @vigneshsathisrikumar - Could you please confirm whether you have implemented bot SSO or ME SSO.
If you have use ME SSO then it should work fine.
Please refer this sample:
https://github.com/OfficeDev/Microsoft-Teams-Samples/tree/main/samples/msgext-search-sso-config
Other sample repo:
https://github.com/OfficeDev/Copilot-for-M365-Plugins-Samples/tree/main


Remove lambda function responses and fix serverless offline cache issue

[x] Remove unnecessary status code responses in lambda functions
[x] Fix unit tests
[x] Add offline-invalidate plugin to invalidate serverless-offline cache

✅  Verified that the invalidate-cache serverless plugin fixes my issue with serverless not reloading lambda code changes


ci: add workflow automation to ffmpeg-sdk

Merged in https://github.com/snapcrafters/ffmpeg-sdk/commit/c457df3f633769e8c8f87dcc57e6518e1252a942


Remove automated docker builds for PRs

Closes #443. Adds a conditional to the docker job that won't run any of the Docker build steps if triggered by a PR. Based on the docker/metadata-action docs, this should stop any of the pr-* images from being built

Got it, I initially misunderstood. Thanks for clarifying! I updated the PR and commit message so that it runs everything except the push for PRs


Archive contents of ZIP-Files

When I download documents, they are sometimes archived in a zip file. Provide a way to archive these documents

Still need to address the success- and error-delegates
It should not only move the zipfile, but sort the containing documents to the error and successpaths


pin symengine<0.10.0

the new version was released today and has been causing our notebook tests to fail (see also https://github.com/Qiskit/qiskit-terra/pull/9857)

The notebook test is failing because of ss#2146

yep, just wanted to get rid of this new error


[ADD ME TO THE ORGANIZATION]

Name: SamratGhosh
Location: India
Interest: web development
Discord username(optional):-
Why do you want to join?

I want to join because I want to explore web development

You can also join our Discord community here
Feel free to check out other cool repositories of the DevsInTech Community here.

@samratghosh291 Thanks for your interest. Invitations have been sent to you. Kindly accept it and make your membership public.


make require and module properties enumerable

The tab autocompletion shows me more properties than console.dir:
>> console.dir(require)
[Function]
>>
arguments    arity        extensions   length       main         name         paths
>> require.

the same is true for "module".
Making those properties more discoverable would be nice for beginners.

just nice to have


show parseJson with '.' key

It looks like this is just a test of a native cheat code, not a forge-std stdCheat. Going to close this as a result, but feel free to add this test upstream to in the foundry repo


[WIP] Matrix Operations

This is ongoing. Comments and suggestions are welcome!

Can you use a github fork to propose a PR?

Will reopen from a fork and with changes addressed.


Fix scrollToHash to handle hashes starting with a number

When hash starts with a number, document.querySelector throws an error, causing scrollToHash to fail.

Do you see any reason why we wouldn't always use get document by id? I admit I wasn't responsible for the hash router implementation so the fact that there is all this query selector stuff just for this case sort of surprises me. I will do some forensics here but the native DOM behavior seems to be restricted to ids so I don't see benefit in applying a general selector and trying to restrict it to fit.

I prefer to use document.getElementById, but since there might be cases in the existing project where a selector is used (even though it's not documented), I was a bit hesitant to change the code.


Snapshot window

Feature request:
Currently, only one snapshot can be created and used for reverting. A better solution would be a new window containing a list of snapshots together with their timestamp. The user can then restore any snapshot (by double-clicking?).

Implemented in v4.11.


error Couldn't find any versions for "xmldom" that matches "^0.8.3"

I tried to set up CI, but came across the issue
https://github.com/jizusun/backstage-jquad/actions/runs/3279332667/jobs/5398748592
yarn install v1.22.19
[1/5] Validating package.json...
[2/5] Resolving packages...
warning Lockfile has incorrect entry for<EMAIL_ADDRESS>Ignoring it.
error Couldn't find any versions for "xmldom" that matches "^0.8.3"
info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.
Error: Process completed with exit code 1.

Hi!
i tried to update the packages, that had security issues using resolutions: https://github.com/jquad-group/backstage-jquad/blob/main/package.json#L43. Maybe the resolutions broke the build.
Although I think we should remove the resolutions, because those libraries are used in Backstage, and they should be updated there?

Oh I see, the resolution is a feature of yarn v1 https://classic.yarnpkg.com/en/docs/selective-version-resolutions/
And I guess maybe the<EMAIL_ADDRESS>is wrong?

Sorry for the late answer, yeah it was wrong, the resolutions are now fixed. I am closing this issue, feel free to open it again, if needed :)


Script fails on proxmox

When running the script it errors out almost immediately, it appears that the usage of sudo in the script is causing it - proxmox is run as the root user.
When running lines manually:
sudo -u $user python3 -m venv /home/$user/OctoPrint sudo: invalid option -- 'm'

Did you try it sudo -u $USER python3 -m ....? Lowercase $user is defined in the script but not in your shell env.

Uppercase $USER does appear to work. A quick replacement in the script just gives me the install camera option though. How do I get it to start a fresh install?
Anyways, I realized the issue was that Octoprint will refuse to start if run by the root user. I used the '--iknowwhatimdoing' flag to get it going for now as proxmox doesn't seem to want to create a working non-root user. Case closed, I guess.

sudo rm /etc/octoprint_deploy and then re-running script will start it again.


How are these values calculated?

Hi there,
First of all thanks for your code. I appreciate if you can have the time to explain the part when you calculate the heartbeat.
You have this function:
        // find peak power and bin
        var power = 0.0 as Float
        var bin = 0 as vDSP_Length

        // calculate heart rate, ie pulse
        // course bandwidth filter --- skip hr under/over unreasonable amounts
        let minHeartRate = 20                                       // skip anything lower ~35 bpm
        let maxHeartRate = Double(windowSizeOverTwo) / 4            // skip anything over ~225 bpm
        vDSP_maxvi(&powerVector+minHeartRate, 1, &power, &bin, vDSP_Length(maxHeartRate))
        bin += vDSP_Length(minHeartRate)

        // push heart rate data to the user
        let timeElapsed = NSDate().timeIntervalSinceDate(timeElapsedStart)
        timeLabel.text = NSString(format: "Seconds: %d", Int(timeElapsed)) as String

        let binSize = fps * 60.0 / Float(windowSize)
        let errorSize = fps * 60.0 / Float(windowSize)

        let bpm = Float(bin) / Float(windowSize) * (fps * 60.0)
        pulseLabel.text = ("\(Int(bpm))")

First of all, I think the values you get there for minHeartRate and maxHeartRate depends on the FPS you are using that is 30 FPS, right? How do you get these values? In my case I am using 60 FPS and still using 512 samples when the app gets there.

power will contain the maximum value coming from the fourier transform and bin its index. You calculate these values but you just use bin.

you do not use either binSize and errorSize. What these variables represent?

what shows on the pulseLabel is the result of bpm that is the division of bin by some number.

I do not understand this.
bin is the Fourier Transform bin that has the highest intensity. A bin in the Fourier Transform is a frequency. I do not understand the relation between a bin and the heartbeat..
thanks.

Hello,
This code is several years old, let me see what I can recall
I probably decided not to use not use binSize, errorSize and power in the
final code and they were only used while I was figuring things out.
minHeartRate and maxHeartRate were just guesses to clip the data. I'm
guessing any bpm above or below that is junk. There is always noise to be
filtered when using sensors
30 fps was the most I could use to get the data through processing and on
screen to user with out getting backed up or losing data. If the device you
are using can do more, by all mean do so. It'll increase your accuracy. The
really interesting stuff happens when you get fps high enough to determine
HRV
Using FFT the bin with the most power is the strongest frequency.
This is just a scale factor to correct units
Linda MacPhee-Cobb
https://github.com/timestocome
On Mon, Mar 4, 2019 at 3:45 PM Magno Urbano<EMAIL_ADDRESS>wrote:

Hi there,
First of all thanks for your code. I appreciate if you can have the time
to explain the part when you calculate the heartbeat.
You have this function:
    // find peak power and bin
    var power = 0.0 as Float
    var bin = 0 as vDSP_Length

    // calculate heart rate, ie pulse
    // course bandwidth filter --- skip hr under/over unreasonable amounts
    let minHeartRate = 20                                       // skip anything lower ~35 bpm
    let maxHeartRate = Double(windowSizeOverTwo) / 4            // skip anything over ~225 bpm
    vDSP_maxvi(&powerVector+minHeartRate, 1, &power, &bin, vDSP_Length(maxHeartRate))
    bin += vDSP_Length(minHeartRate)

    // push heart rate data to the user
    let timeElapsed = NSDate().timeIntervalSinceDate(timeElapsedStart)
    timeLabel.text = NSString(format: "Seconds: %d", Int(timeElapsed)) as String

    let binSize = fps * 60.0 / Float(windowSize)
    let errorSize = fps * 60.0 / Float(windowSize)

    let bpm = Float(bin) / Float(windowSize) * (fps * 60.0)
    pulseLabel.text = ("\(Int(bpm))")

First of all, I think the values you get there for minHeartRate and
maxHeartRate depends on the FPS you are using that is 30 FPS, right?
How do you get these values? In my case I am using 60 FPS and still using
512 samples when the app gets there.
2.
power will contain the maximum value coming from the fourier transform
and bin its index. You calculate these values but you just use bin.
3.
you do not use either binSize and errorSize. What these variables
represent?
4.
what shows on the pulseLabel is the result of bpm that is the division
of bin by some number.
I do not understand this.
bin is the Fourier Transform bin that has the highest intensity. A bin in
the Fourier Transform is a frequency. I do not understand the relation
between a bin and the heartbeat..
thanks.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/timestocome/SwiftHeartRate/issues/1, or mute the
thread
https://github.com/notifications/unsubscribe-auth/ACJx4ULexGn1A5oC0S0DKVG2T9iDzKQAks5vTZPtgaJpZM4bdRUv
.

awsome answer. thanks!!!


Data explorer figures don't match

Data Explorer section in Registry page has some consistency issues:
There is DPG types section for filtering:
AI Model, Open Content, Open Data, Open Software and Standard are the categories under this types section.
In the data visualisation section not all of these sub categories are reflected. There are only Content, Data and Software categories reflected.
@skylark1848 @gazdagergo

#214 duplicate


test asl_Map hangs with maxconcurrency values != 0

When maxconcurrency is set to 1, hangs by printing "Test 1/4" (i.e., first test tuple).
When maxconcurrency is set to 2 or 3, hangs by printing "Test 4/4" (i.e., fourth test tuple).
A recent PR #111 has fixed some indentation issues in FunctionWorker/StateUtils. However, it appears that the problem was already there (i.e., before the indentation fixes).

not sure if related, but I just fixed a slash "/" that was appearing in the workflow label of a kservice in https://github.com/knix-microfunctions/knix/commit/372e77151d1bbf343ecafafacb611391684869d9 and wouldn't deploy on k8s

This was running on a single-host, bare metal setup, so probably not.

Fixed by 6983c3d16dbee88ae4383f29c7d616fe0303a0d0.


[Docs] Chat/Support still points to spectrum

The following files still mention spectrum as the place to get support and chat.

README.md badge at the top
README.md, section "Support, Community & Chat"
CONTRIBUTING.md says Help others in our Spectrum Support Community
CODE_OF_CONDUCT.md, section "Enforcement" says ay be reported by contacting the project team at https://spectrum.chat/react-static

Should I PR this and replace spectrum with Github Discussions everywhere?
And is there some chat platform still in use in parallel to Github Discussions?

Only Github Discussions is used, and we'd love a PR.


Various missing nodes - suggest update to Installation instructions

The provided example uses nodes such as GetNode that is not in this repository. I suggest adding an installation step to install https://github.com/kijai/ComfyUI-KJNodes.

Sure, done.


Need to have ability to exclude specific entities or properties

I love the idea behind this project. This is great and I am looking forward to this becoming more mature, stable and famous!
The following configuration options might be required in a lot of cases:

Exclude specific entities: I might be fine with exposing a 100 other entities within my DbContext in this way. But I need the ability to exclude some (for example User entity), so that I can create my own endpoints with my own business logic for it.
Exclude specific properties of an entity: In some cases, there may be properties that are not meant to be modified directly by a PUT or a POST request. For example, columns that are updated behind the scenes via some business logic.

Thanks,
Raghu

Suggestion for the properties.  In true DDD fashion, they need to be read-only (private setter). Could this work? It would drop the need for complex configuration of includes/excludes.

That would absolutely work and eliminate messy configuration.
On Sat, 19 Feb, 2022, 3:14 pm Dries, @.***> wrote:

Suggestion for the properties. In true DDD fashion, they need to be
read-only (private setter). Could this work? It would drop the need for
complex configuration of includes/excludes.
—
Reply to this email directly, view it on GitHub
https://github.com/csharpfritz/InstantAPIs/issues/2#issuecomment-1045979043,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAJEA5X2BCBM4GOP6EAGPU3U35Q73ANCNFSM5OVD4MJA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you authored the thread.Message ID:
@.***>


Derive PriorityClassName for shadow pod group from pod PriorityClassName

Is this a BUG REPORT or FEATURE REQUEST?:

Uncomment only one, leave it on its own line:
/kind bug
/kind feature

Implementation
It should be fairly simple few lines change in createShadowPodGroup() in pkg/scheduler/cache/util.go
Happy to make a PR.

that makes sense to me :)
BTW, did you try Volcano: http://github.com/volcano-sh/volcano ?

@k82cn Hi! I looked it up. Volcano seems like a more complicated solution. There are more custom resource definitions to learn and services to maintain. I want batch scheduling capabilities without forcing users to use specific frameworks or workflows, ideally enabling batch scheduling should be as simple specifying scheduler name plus and some optional annotations in the pod template.

oh, Volcano provide the same interface for scheduling part; it's up to you whether using job or not. One more feature is Queue, whose lifecycle is managed by queue controller :)


Support auto-dark mode.

Hello,
Please please support auto-dark mode. (like Aurora Droid):

Thanks.

Similar to #785 . Keeping that one as it has some more info


Replaced @octokit/rest with @actions/github to add GHES support

Hi!
Thanks for the Action! I wanted to use this in my project, but I am using a Github Enterprise Server instance. This didn't seem to be supported.
I replaced @octokit/rest with @actions/github, and everything works as expected.
Note: I added a .catch(console.error) to catch any unhandled exceptions. This exposed an existing issue in the test cases, something to do with how helpers.readFilePromise is mocked. I haven't fixed this issue here, all test cases are still passing.

Thanks!

@simondesancha thanks for your contribution! Can you address this failing test https://github.com/TinkurLab/monorepo-pr-labeler-action/runs/6316057298?check_suite_focus=true. I think you just need to update the package in the test as well.

@simondesancha the repo https://github.com/actions/github indicates "This action is deprecated! Please use actions/github-script, instead." Can you check into the compatibility of using actions/github-script?

@simondesancha the repo https://github.com/actions/github indicates "This action is deprecated! Please use actions/github-script, instead." Can you check into the compatibility of using actions/github-script?

As far as I can tell, that deprecation notice is referring to the Github Action (actions/github) instead of the NPM library (@action/github). Happy to be corrected though. I believe this is the repo holding the NPM library: https://github.com/actions/toolkit.

@simondesancha indeed. My mistake. Thanks for clarifying.

Released https://github.com/TinkurLab/monorepo-pr-labeler-action/releases/tag/4.1.0


Update installation guide with info about installing the package on Laravel 5

Information on this page is not actual and does not reflect the Laravel 5 way to publish vendor files (I mean vendor:publish instead of config:publish):
http://administrator.frozennode.com/docs/installation
I can try to make pull reqest with fix for that, but is seems like source files of administrator.frozennode.com are not in this repo.

+1

fixed in the docs, I do not have access to build administrator.frozennode and will change the docs to another domain soon.

Thanks @davemathews


Ruby 3 compatibility

Have there been any efforts already on getting this gem ready for Ruby 3?
this kind of magic: https://github.com/DatabaseCleaner/database_cleaner/blob/master/lib/database_cleaner/cleaner.rb#L43
    def strategy=(args)
      strategy, *strategy_args = args

won't work in Ruby 3, I've seen quite some usage of this pattern.
Also, the redis and the active_record sub-gems use kwargs vs. options-hashes differently, see:
options hash: https://github.com/DatabaseCleaner/database_cleaner-active_record/blob/master/lib/database_cleaner/active_record/truncation.rb#L8
class Truncation < Base
  def initialize(opts={})

kwargs: https://github.com/DatabaseCleaner/database_cleaner-redis/blob/master/lib/database_cleaner/redis/deletion.rb#L6
    class Deletion < Strategy
      def initialize only: [], except: []

which will make it harder to upgrade the database gem family.
So probably as a first step, we should harmonize all sub-gems to use the same way of passing options around, either as a hash or using keyword arguments. From there we can tinker further.
I've tried it quickly locally and run into too many issues to push a draft PR. I might find more time on one of the next weekends though. -> hence the question, if there is already any PR/fork that started working on Ruby 3 compatibility.
As always, thanks for the gems 🙂
=> Specs are passing for Postgresql, MySQL, SQLlite locally, however, when I use
DatabaseCleaner.strategy = :deletion, { except: %i[not_you also_not_you blubb] }

in one of my projects, strategy= fails with the Ruby 3 kwargs/hash error.

@botandrose in case one would start working on this, any preference from the maintainers for either kwargs or options-hashes? I think, using hashes gives more flexibility regarding the DSL, since the gem is broken into multiple gems, and each gem might want to add or omit certain options/key-words. On the other hand, being explicit makes it easier to follow the codebase if you are not familiar with it. From my short look at two of the gems (Redis, active-record), there are not that many options, thus being explicit could be the way to go.

@swiknaba Not sure about Micah's preference, but I would prefer the options-hash way.
So instead of doing this:
    def strategy=(args)
      strategy, *strategy_args = args

I would be interested in it doing this:
    def strategy=(strategy, strategy_args = {})
      ...

I think that would be the least disruptive change and it wouldn't require people using database_cleaner to change their implementations.

@swiknaba @etagwerker Yes, options-hash sounds good to me!

Ruby 3.0 is out since almost 2 years now, when could we expect this gem to be adapted for Ruby 3 ?
@botandrose which branch has that fix ? If I can help by testing it, I would be very happy to do so.

@botandrose  indeed, tests are all passing, however when I used
DatabaseCleaner.strategy = :deletion, { except: %i[not_you also_not_you blubb] }

in my codebase, then RSpec failed with a syntax error.

In the case that helps, here is the deprecation warning from Ruby 2.7 :
/usr/local/bundle/gems/database_cleaner-core-2.0.1/lib/database_cleaner/cleaner.rb:85: warning: Using the last argument as keyword parameters is deprecated; maybe ** should be added to the call

Even though CI seems to pass, for me running Ruby 3.0.3 against v2.01 locally raises two errors:

In any event, I ran into the same issue as others, and circumvented it by specifying the strategy object explicitly:
DatabaseCleaner[:redis].strategy = DatabaseCleaner::Redis::Deletion.new(only: ["something:*"])

This approach is documented in the ActiveRecord adapter, but isn't present on this specific repository and other adapter repositories.
Is an easy solution to this problem adjusting the documentation to recommend the above approach? Anyone upgrading who runs into this issue will likely revisit the docs and can correct the problem easily. Downside is that it smells like a bit of an abstraction leak. If there is a desire to keep using primitive values to set a strategy, then I think the strategy= should be deprecated in favor of something like set_strategy(strategy, strategy_args = {}), similar to how @etagwerker suggested.

I faced the same issue on Redis adapter and I would be happy if this problem is resolved 👋
Now I resolve the error by the way described at https://github.com/DatabaseCleaner/database_cleaner/issues/677#issuecomment-1376593917


Relative Routes + Links

Pretty sure this is all we need, we can cut/paste the stuff into core Route/Link, or export <RelativeRoute> and <RelativeLink>, or keep it external, whatever, but with each route putting itself on context as router it got real easy.
import React, { Component, PropTypes } from 'react'
import BaseRoute from 'react-router-dom/Route'
import BaseLink from 'react-router-dom/Link'

class Route extends Component {
  static contextTypes = {
    router: PropTypes.object
  }

  getPath() {
    const { path } = this.props
    const isAbsolute = path.startsWith('/')
    const parent = this.context.router
    // todo handle `/blah/ + blah` turning into `/blah//blah`
    return isAbsolute ? path : (
      parent.match ? `${parent.match.url}/${path}` : `/${path}`
    )
  }

  render() {
    return <BaseRoute {...this.props} path={this.getPath()}/>
  }
}

class Link extends Component {
  static contextTypes = {
    router: PropTypes.object
  }

  getTo() {
    const { to } = this.props
    const isAbsolute = to.startsWith('/')
    const { router } = this.context
    return isAbsolute ? to : (
      router.match ? `${router.match.url}/${to}` : `/${to}`
    )
  }

  render() {
    const to = this.getTo()
    return <BaseLink {...this.props} to={to}/>
  }
}

export { Route, Link }

I just used it in this app and it works great:
import React from 'react'
import { BrowserRouter as Router } from 'react-router-dom'
import { Link, Route } from './Relative'

const PEEPS = [
  { id: 0, name: 'Michelle', friends: [ 1, 2, 3 ] },
  { id: 1, name: 'Sean', friends: [ 0, 3 ] },
  { id: 2, name: 'Kim', friends: [ 0, 1, 3 ], },
  { id: 3, name: 'David', friends: [ 1, 2 ] }
]

const find = (id) => PEEPS.find(p => p.id == id)

const RecursiveExample = () => (
  <Router>
    <Person match={{ params: { id: 0 }, url: '' }}/>
  </Router>
)

const Person = ({ match }) => {
  const person = find(match.params.id)

  return (

{person.name}’s Friends

        {person.friends.map(id => (

            {/* relative */}
            <Link to={''+id}>
              {find(id).name}
            </Link>

        ))}

      {/* relative */}
      <Route path=":id" component={Person}/>

  )
}

export default RecursiveExample

#4539
#4459
@pshrmn @mjackson @wmertens @timdorr See any holes in this?

There's a differing amount of "relativeness" to this approach. It only handles (when the parent is /foo) something like path="bar" -> path="/foo/bar".
I think the intent of the other approaches is more robust relativity (yeah, that's the word!). So you could also do path="../bar" -> path="/bar" or path="../../bar" -> throw Error(). The point being to support all the relative stuff in hrefs that the DOM supports. In particular, the ability to "navigate up" easily.

And that's not to say the composition approach couldn't be applied. You just need something like resolveLocation to be as robust as possible. But then the question is raised: why have this be a separate component? Why not just bundle it into <Route> and <Link> directly, since it's really just a function on one prop?

I don't think ../ is something I want to support. What does it mean?
<Route path="accounts"/>
// then a child in there somehwere
<Route path="foo/bar/baz"/>

If I'm at /accounts/foo/bar/baz and I link to ../ does that take me to /accounts/foo/bar or /accounts?
Because the Links and Route's are relative to the entire path of the parent, so does link up go up to the parent or does it work on the location.pathname?
I just see confusion. I really don't think it's a common need to link "up". Linking "down" and "laterally" is what people want 99% of the time.

Why not just bundle it into  and  directly

Because there are too many questions right now. When external components are put through the ringer long enough, then we know exactly what the constraints are and won't have to fiddle around with the core API. When it comes in, it comes in solid.

<Link> needs to support both strings and location objects. That is an easy change, just missing from the example code.
Relative <Redirect>s should work like relative <Link>s. I'm not sure how often this would be done, but they both support the same to signature, so it is another easy change.
When match.url is falsy, it can be incorrect to assume that the relative path should just have a slash prepended (see #4560 case 1).
A relative <Link> has to listen to history in order to always resolve with the correct match.url. This is probably the most frustrating part of this because of how many extra listeners it adds. I considered adding a separate <RelativeLink> so that only those listen for changes, but <NavLink> only works for <Link>s, so I had to merge it in.
(╯°□°）╯︵ ┻ǝʇɐpd∩ʇuǝuodɯoƆplnoɥs┻
I'm not sure how this works with dot relative paths. You can test out this example which was inspired by the recursive example.

@ryanflorence I just saw your comment about not supporting dot relative paths. Will expand on why I think that they are necessary in another comment.
As an aside, are there any examples that the React team has posted showing when using context is unreliable? From what I have seen, this only happens when someone is already using subscribers, which re-render a component before the getChildContext of their parent gets called, so they end up using the previous context.

Thanks @pshrmn

A relative <Link> has to listen to history ... (╯°□°）╯︵ ┻ǝʇɐpd∩ʇuǝuodɯoƆplnoɥs┻

Ah, yes. So frustrating.
Okay, I'd say continue on your work then, you've clearly got your head wrapped around it. We really don't want Link to listen to history, that's why NavLink got split out. Maybe we make RelativeLink or add relativity to NavLink and name it something else, SlowLink or UsesMoreMemoryLink or a name that is actually good.
Another option that I really don't like as the library author but really love as the consumer: we just have one Link. It detects if it has activeClassName, activeStyles, or a relative path, and then subscribes/unsubscribes to history.

First, I missed this in my previous list:

Resolving a <Route> using match.url means that the params parsed from earlier routes will not be passed to that <Route>. You could use match.path, but that will mean that you're creating a more complex matching regular expression in order to capture values that you have already parsed out of the URL.

I personally think that dot relative paths are the most useful feature of adding relative links. It allows you to write reusable components that don't have to have a knowledge of their actual location.
<Route path='albums' render={() => (
  // match = { url: '/albums' }
  <Switch>
    <Route path='' render={() => (
      // match = { url: '/albums' }

        // here, simple concatenation can be used to resolve paths
        {
          albumAPI.loadAlbums()
            .map(a => <Link key={a.id} to={a.id}>{a.name}</Link>
        }

    )} />
    <Route path=':albumID' render={() => (
      // match = { url: '/albums/<albumID>', params: { albumID: <albumID> }}
      <Switch>
        <Route path='' render={() => (
          // match = { url: '/albums/<albumID>', params: { albumID: <albumID> }}
          // generate links to images similar to album links, nothing interesting
          {
            albumAPI.getPhotos(match.params.albumID)
              .map(p => <Link key={p.id} to={p.id}></Link>
          }
          // going back to the /albums page can be done with dot relative paths
          // this isn't particularly interesting, but means that this component could be
          // reused in someone's /galleries page or /user/profile/<id>/albums/ page
          // and still work.
          <Link to='..'>Back</Link>
        )} />
        <Route path=':photoID' render={() => (
          // assuming parent params are merged:
          // match = {
          //   url: '/albums/<albumID>/<photoID>',
          //   params: { albumID: <albumID>, photoID: <photoID> }
          // }
          // here, a photo might have links back to its album and to sibling photos. Without
          // dot relative paths, you would have to build the URLs using params
          <Link to={`/albums/${match.params.albumID}`}>Back to Album</Link>
          //  or split match.url in order to figure out its parent URL.
          <Link to={`${match.url.split('/').slice(0, -1).join('/')}/${siblingID}`}>Next</Link>
          // with dot relative paths these become
          <Link to='..'>Back to Album</Link>
          <Link to={`../${siblingID}`}>Next</Link>
        )} />
      </Switch>
    )} />
  </Switch>
)} />

@pshrmn what about: https://github.com/ReactTraining/react-router/issues/4571#issuecomment-281405901 ?

sorry, I split this conversation into a new thread, closing in favor of the pull requests #4539 #4459

Just to answer the question here, it would be relative to match.url. If match.url = '/accounts/foo/bar/baz', the path .. resolves to /accounts/foo/bar. This would render the accounts route's component, which ideally either has a <Route> that matches that path or has a "no match" component to handle the miss.
<Route path='accounts' render={() => (
  <Switch>
    <Route exact path='' render={() => (
      <Link to='foo/bar/baz'>Deep Link</Link>
    )}/>
    <Route path='foo/bar/baz' render={() => (
      <Link to='..'>Up</Link>
    )}/>
    <Route render={() =>
Failed to match pathname
}/>
  </Switch>
)}/>

This definitely can cause confusion when a route's path is deeply nested, but I think that clear documentation should help here (at least for people who read the documentation, for everyone else :man_shrugging:) Something along the lines of this (maybe with an example?).

A <Link> can use double dot notation (..) to resolve a location relative to its parent match.url.

if we want to use relative Link,  should keep in mind that the href must be trailed with a '/'. so the Link to='./sam' could work.
and Why we couldn't use relative Route? I can't find some detail referring to training

@JimmyVV That approach to resolving relative URLs is more of a quirk than a real solution. The approach that we are working towards is one that will always work without having to mess with the parent route's path. Also, instead of using dot relative paths, you would just not include a leading slash for relative paths.
There are a couple of PRs with this pretty much implemented, it is just a matter of verifying that everything works as expected.


Backport timer reset() fix

Clear release notes
Add test for reset() while a timer is being waited on
Fix reseting the timer while it is being waited on
Update the release notes
Fix typo in comment

Fixes #242.

OK, I accepted the suggestion, now we need to forwardport the fix of the backported fix :rofl:


Update AWS ECS Executor to use AWSExecutor

Acceptance Criteria

[ ] Pass any required attributes from credentials_file, region, s3_bucket_name, profile, execution_role, and log_group_name to AWSExecutor super class
[ ] Re-structure executor in order to accord with abstract class methods as defined in RemoteExecutor, namely _upload_task, submit_task, get_status, _poll_task, _query_result, and cancel when appropriate
[ ] Update unit tests for executor
[ ] Update doc strings for executor

Closed as duplicate of https://github.com/AgnostiqHQ/covalent-ecs-plugin/issues/25


Changes.md out of data

Recently performed an update to 0.16.2, change-log only goes to 0.15.0: https://github.com/sensortower/sidekiq-throttled/blob/master/CHANGES.md

I've lost access to this repo, so the updated source code now lives under https://github.com/ixti/sidekiq-throttled


findLetsAlg: tracking preds is enough

I think before is not needed in findLetsAlg because preds already records processed nodes.
I've also removed all the indirections introduced by online functions because it was harder for me to understand what was done, but feel free to ignore this PR and just remove before the way you want.

Hey, thanks for the PR, nice spot 👍 I've merged it in myself, preserving the original helper functions: I agree it makes it harder to understand how it's working internally, but it helps keep the intention a bit clearer.


Fix Issue#6042, #6030 CreateDatabase failure on Windows

[x] CHANGELOG.md updated
[X] Rebased/mergable
[X] Tests pass
[X] Sign CLA (if not already signed)

Commit 27cfaa4  introduced a regression in meta/client.go, which made CreateDatabase calls to fail on windows. Root cause is the [os.Rename](https://github.com/influxdata/influxdb/blob/27cfaa4b7a517364556cdd1a7225cab513784bc6/services/meta/client.go#L898) in func (c *Client) Snapshot(). In Windows this fails when the file already exists. Fix is to remove the old file, and store the new file.
Fixes #6042, #6030

@jsternberg @jwilder attempt#2. I closed previous PR#6043 and resubmitted this one with proper author info. I also moved the snapshot function to a separate file, and provided a OS specific override. Since we now have ARM release, I am not sure if it needs another file. It compiled and ran on my raspberry pi2 without any issues.

as per @jsternberg suggestion, moved only rename part to be platform specific, and covered windows vs non windows, all platforms should be good.

Can you rename renameFile_unix.go to file_unix.go? The same with renameFile_windows.go to file_windows.go.

You want me to just rename the files or the function as well?

Just the file and please squash your commits so it's only one commit.

@jsternberg Done!! because of you I learnt a lot of new git commands.. Thank you! Hope everything is good now.

@mvadu did you find this bug from master or when running against the 0.11 release candidate? I'm unable to cherry pick it to the 0.11 branch due to a conflict.
I need to know so I can make sure this bugfix gets into 0.11 if the problem happens in 0.11.

The bug (renaming in snapshot method, and whole snapshot method were part of Commit 27cfaa4). I have given the link to that commit in my PR comment.

Ah, it looks like that commit was made after we branched off for 0.11, so it shouldn't exist in the 0.11 release candidate or 0.11. I'll make sure to modify the changelog appropriately.

Oh!! so for 0.11 RC branch, #5999 should be merged, so that on Windows we can run without any modifications to config. Let me know if you want to consider it, and I will resubmit.

I submitted #6056 against 0.11 branch for one open issue in Windows. Merging that will allow 0.11 version to run fresh out of build.

@mvadu since we're about to release 0.11 and Windows isn't officially supported in that release, I think it would be best to just try running off of master if you want to use InfluxDB on Windows. If you find any other issues with compiling and using InfluxDB on Windows, please open an issue and we appreciate pull requests that help us get to Windows support.
Thanks for your help. We will also have 0.12 out by sometime in April if you would prefer to wait until then.

@jsternberg Sure,I understand. Just to let you know, I released a version of InfluxDB (off of 011 branch with #6056 at https://github.com/mvadu/influxdb/releases/tag/v0.11.0-rc1 so people like me who are interested in Windows and Influx can give it a try earlier than you guys can officially offer it.


go get github.com/veandco/go-sdl2/{img, mix} fails

When running in bash getting this error.
In file included from go/src/github.com/veandco/go-sdl2/img/sdl_image.go:5:0:
./sdl_image_wrapper.h:5:11: fatal error: SDL_image.h: No such file or directory
  #include <SDL_image.h>
                ^~~~~~~~~~~~~

In file included from go/src/github.com/veandco/go-sdl2/mix/midi.go:6:0:
./sdl_mixer_wrapper.h:4:11: fatal error: SDL_mixer.h: No such file or directory
  #include <SDL_mixer.h>
           ^~~~~~~~~~~~~

Hi @CarterScadden, what platform are you on? Did you install the native libraries for SDL_image and SDL_Mixer?

Yes sorry, I've resolved the issue didn't realize I needed to install those libraries from else where. Thank you


Is it possible to define transparency for an entity?

We would like loaded model gradually to appear in the scene by animating it transparency level over the time. What would be the best way to achieve that in Filament?
Modifying material(s) to have transparency enabled is not a good option could expose inner parts of the model that is not visible otherwise.

We have a special blend mode called "fade" for that very purpose. You can also use the transparency property and set it to twoPassesOneSide.

I have been experimenting with "fade" blending mode. Unfortunately that is not what we are looking for. Similar to the transparent blending it will expose part of the model that are not visible in the opaque mode.That can be seen in material_sandbox for monkey model if you turn the head so that one ear is behind the head. Switching blending modes will make that ear visible.
We are looking for something that is close to normal opaque rendering and then applying alpha value for rendered results before compositing with the rest of the scene entities.

Right which is why I mentioned the "transparency" property. Set it to "twoPassesOneSide". You can see pictures showing what it does in the materials documentation.

The twoPassesOneSide value actually helped us to get the effect we were looking for, Thanks!
We have couple of more questions:
What is the performance impact (battery usage, frame rate) of different blending mode? Does transparency and twoPassesOneSide property contributes  potentially to higher power consumption?
Other question, while animating alpha value we are using now non opaque blending mode (transparent or fade) for materials that originally were designed as opaque. After animation is done we continue using blending in transparent mode but alpha is set to 1 to get rid of transparency. Do you foresee any problems with that approach (artifacts,  power usage...)? We can also change implementation that would recreate renderable  with opaque materials after animation if that is needed.

Transparency is more expensive yes, particularly if you have multiple transparent objects in front of each other.
Using a transparent material with an opacity of 1 has effectively the same cost as using an opacity < 1. You won't (shouldn't :) get artifacts but it's more expensive. Note that you can swap material without creating a new renderable (see RenderableManager::setMaterialInstanceAt).


Properties store with escaped chars

Properties column is saved on the database like this<EMAIL_ADDRESS>Whenever I try to use $activity->properties it just returns me the above string, not an array that I can work with.
Please advise on how to fix this. Thanks!

Are you using the provided Activity model? This cast should take care of converting the properties to a collection.

Actually just installed it and using it out of the box.
I was messing around and saw this cast, so I tried with a model of my own. I've manually created a text column on the database on one of my tables, used that same cast and on tinker I assigned another model to that attribute.
It got saved as:
testing: """\"\\\"{\\\\\\\"id\\\\\\\":1,\\\\\\\"code\\\\\\\":\\\\\\\"123\\\\\\\\
Now I am completely lost. :(

If you cannot get casts to work properly, there probably something wrong with your Laravel app as that feature is provided by Laravel itself. Could you try installing and using the package into a vanilla Laravel app?

Vanilla installation showed no problem. It's a laravel problem.
You can close the issue. But please, any tips on how can I debug this?

If anyone gets here form Google: updating from Laravel 5.3 to 5.4 worked for me, might work for you too.
Thanks spatie team for the amazing work.