better for popover extend.

https://github.com/twbs/bootstrap/blob/master/js/tooltip.js#L267
change to
var isVertical          = /^(top|bottom)/.test(placement)
may be better.

Why?

I'm not very familiar with tooltip.js so I could be wrong about this, but I think @icai's logic is that you don't want to change match value that isn't exactly "top" or "bottom". I believe the existing regex would match attributes such as margin-top as they include the word we are checking for since we are not anchoring it. If we wanted to be more specific though I would probably say it should be /^(top|bottom)$/.test(placement) though so that we anchor it to exactly "top" or exactly "bottom".
I could be wrong though :)

There are several places in the Tooltip plugin that assume placement (after removing auto) must be one of left, right, bottom, or top, and not any other value. Changing the plugin from having a closed-world assumption (that we know all possible legal placement values) to an open-world assumption is nontrivial.
If you're extending the plugin to add such a significant feature as additional placements, you're going to need to override or modify a few methods. Simply tweaking the regexes in the vanilla plugin itself (like is being proposed) won't be sufficient.

I want to extend the popover placement (right-bottom, right-top ......),
$.fn.popover.Constructor.prototype.getCalculatedOffset = function (placement, pos, actualWidth, actualHeight) {
    return placement == 'bottom' ? { top: pos.top + pos.height,   left: pos.left + pos.width / 2 - actualWidth / 2  } :
           placement == 'top'    ? { top: pos.top - actualHeight, left: pos.left + pos.width / 2 - actualWidth / 2  } :
           placement == 'left'   ? { top: pos.top + pos.height / 2 - actualHeight / 2, left: pos.left - actualWidth } :
           placement == 'right' ? { top: pos.top + pos.height / 2 - actualHeight / 2, left: pos.left + pos.width   } :
           placement == 'bottom-left' ? {top: pos.top + pos.height, left: pos.left + pos.width / 2 - (actualWidth * 0.10)} :
           placement == 'top-left' ? {top: pos.top - actualHeight,  left: pos.left + pos.width / 2 - (actualWidth * 0.10)} :
           placement == 'bottom-right' ? {top: pos.top + pos.height, left: pos.left + pos.width / 2 - (actualWidth * 0.90)} :
           placement == 'top-right' ? {top: pos.top - actualHeight, left: pos.left + pos.width / 2 - (actualWidth * 0.90)} :
           placement == 'right-top' ? {top: pos.top + pos.height / 2 - (actualHeight * 0.10), left: pos.left + pos.width} :
           placement == 'left-top' ? {top: pos.top + pos.height / 2 - (actualHeight * 0.10), left: pos.left - actualWidth} :
           placement == 'right-bottom' ? {top: pos.top + pos.height / 2 - (actualHeight * 0.90), left: pos.left + pos.width} :
           /* placement == 'left-bottom' */ {top: pos.top + pos.height / 2 - (actualHeight * 0.90), left: pos.left - actualWidth}
}

but the $.fn.popover.Constructor.prototype.applyPlacement = function(offset, placement){ method is too long. I must copy this again, but just change the /top|bottom/.test(placement)  to  ^(top|bottom)$/.test(placement)
do you have a better idea for me to do this?  @cvrebert @kkirsche  thanks


Crude Oil Analysis

It  involves data analysis and prediction of crude oil

@Akshat111111 Assign me this issue I will work on it.

Assign this to me, I'm interested in working on this.

Can i work on this ? My approach is to build a Random Forest crude oil price prediction model.

hello ,, pls assign this issue to me i will give my best
Waiting for your response

Im interested in this, kindly assign it to me

I would like to work on this issue. Please assign this task to me

It involves data analysis and prediction of crude oil under the main folder- Hedging by crude oil

@apooyadv  @tejasvinigoel lets give others some task, you can then improve upon.

@amishhaa has done the work,are you also working with new feature?? @Amarta113

@Akshat111111 Yes I am working on it, the dataset is too large therefore I am delay

If you are facing any issue in uploading the dataset, convert it to zip file.

Yet its not ready to upload,  I need some time to complete it. Is it necessary to upload now?

yes it is needed.

@Akshat111111 I am interested in working on this issue . Kindly assign it to me if possible

One implementation is already there, so create a new issue with a specific functionality.


JS Bin examples do not work

JS Bin examples do not work because they reference //rubaxa.github.io/Sortable/Sortable.js instead of https://sortablejs.github.io/Sortable/Sortable.js.
Possibly related: #1342

+1

Fixed


Generate a changelog for a specific lerna package

Do you have an idea to add  --lerna-package feature in mind?
Like conventional-changelog -p angular -i CHANGELOG.md -l @scope/package-name

The -l flag is something they already support? We could think of a way to then add the correct -l to the command.

Actually, I need commit-path parameter for monorepo project. Your repo doesn't forkable therefore I developed this feature in my repository. I can merge this feature into your repository if you enable the fork feature.

Not sure what you mean with fork feature? You can fork the repo, it is not disabled.

Oh sorry, Browser extension problems, I can see now.


Missing UpdateManifestVersion.exe

Its not possible to build the setup by running buildCC as it expects the executable UpdateManifestVersion.exe to exist in Microsoft.Research\common\bin.

May be closed as not relevant anymore.


"Permission denied" after "vagrant ssh"

Vagrant 1.9.3
box version: debian/jessie64 (virtualbox, 8.7.0)
virtualbox version: Version 5.1.18-114002
This happens when I use customized synced folder. See the Vagrantfile below.
The synced folder wasn't working (mount: unknown filesystem type 'vboxsf') unless I install the vagrant-vbguest plugin.
After executing 'vagrant plugin install vagrant-vbguest', I cannot 'vagrant ssh' anymore.
It reports "Permission denied (Public key)".
However I can 'ssh -p 2222<EMAIL_ADDRESS>Why is this happening and how to fix it?
# -*- mode: ruby -*-
# vi: set ft=ruby :

# All Vagrant configuration is done below. The "2" in Vagrant.configure
# configures the configuration version (we support older styles for
# backwards compatibility). Please don't change it unless you know what
# you're doing.
Vagrant.configure(2) do |config|
  # The most common configuration options are documented and commented below.
  # For a complete reference, please see the online documentation at
  # https://docs.vagrantup.com.

  # Every Vagrant development environment requires a box. You can search for
  # boxes at https://atlas.hashicorp.com/search.
  config.vm.box = "debian/jessie64"

  # Disable automatic box update checking. If you disable this, then
  # boxes will only be checked for updates when the user runs
  # `vagrant box outdated`. This is not recommended.
  # config.vm.box_check_update = false

  # Create a forwarded port mapping which allows access to a specific port
  # within the machine from a port on the host machine. In the example below,
  # accessing "localhost:8080" will access port 80 on the guest machine.
  # config.vm.network "forwarded_port", guest: 80, host: 8080
  config.vm.network "forwarded_port", guest: 80, host: 1757

  # Create a private network, which allows host-only access to the machine
  # using a specific IP.
  # config.vm.network "private_network", ip: "<IP_ADDRESS>"

  # Create a public network, which generally matched to bridged network.
  # Bridged networks make the machine appear as another physical device on
  # your network.
  # config.vm.network "public_network"

  # Share an additional folder to the guest VM. The first argument is
  # the path on the host to the actual folder. The second argument is
  # the path on the guest to mount the folder. And the optional third
  # argument is a set of non-required options.
  config.vm.synced_folder ".", "/vagrant", disabled: true
  config.vm.synced_folder "ikiwiki/", "/home/vagrant"

  # Provider-specific configuration so you can fine-tune various
  # backing providers for Vagrant. These expose provider-specific options.
  # Example for VirtualBox:
  #
  # config.vm.provider "virtualbox" do |vb|
  #   # Display the VirtualBox GUI when booting the machine
  #   vb.gui = true
  #
  #   # Customize the amount of memory on the VM:
  #   vb.memory = "1024"
  # end
  #
  # View the documentation for the provider you are using for more
  # information on available options.

  # Define a Vagrant Push strategy for pushing to Atlas. Other push strategies
  # such as FTP and Heroku are also available. See the documentation at
  # https://docs.vagrantup.com/v2/push/atlas.html for more information.
  # config.push.define "atlas" do |push|
  #   push.app = "YOUR_ATLAS_USERNAME/YOUR_APPLICATION_NAME"
  # end

  # Enable provisioning with a shell script. Additional provisioners such as
  # Puppet, Chef, Ansible, Salt, and Docker are also available. Please see the
  # documentation for more information about their specific syntax and use.
  # config.vm.provision "shell", path: "provision.sh"

end

I assume that vbguest was running and updating your guest additions.
Can you check if commenting out this line does help:
config.vm.synced_folder "ikiwiki/", "/home/vagrant"
It looks that you "overwrite" the entire guests home directory which make ssh keypairs disappear.


Fix mangler

Tried some stuff. It's still buggy ... With block scoping plugin, fixing one breaks the other and I had been going around in circles.

Still has some issues .. but mostly done and need to remove some dead code ...

Related: babel/babel#4815

#257 affects mangler because it changes bindings' scope. So mangler is not able to figure that out properly. It would be nice to have a babel utility to recalculate scope, references and binding. scope.crawl does it, but fails when it comes to bindings - related - https://github.com/babel/babel/issues/4818

Failed test is in "regexp-constructors"

rebased master


Special case inline unapply seq

Replacement for lampepfl/dotty#15053
Resolves #8577
Fixed a bug where extension inline unapplySeq would fail to type by adding a few special cases in Inliner.scala

@nicolasstucki enabled auto-merge 2 days ago

In case you didn't notice, the merge is currently blocked because of merge conflicts.

Thank you @gorilskij

https://github.com/scala/scala3/pull/16358 should have implemented all we need to support this feature.


Indexing without cache...still running slow layers crawling process

thanks Jorge - I'll review and merge the code manually if needed


Setup online documentation with github pages

There are infinite variations to this, but here is how I did it in Kuchiki:

Go to https://github.com/settings/tokens/new and create a new "personal access token" with only the repo "scope". Warning: this is like a password that gives push access to all your public repositories. (But it’s revocable.)
Go to Travis-CI for the relevant repository. Go to "Settings". Under "Environment Variables" add an entry with TOKEN as the name, and the hexadecimal string just created from GitHub as the value. Make sure "Display value in build log" is OFF.
Add something like this https://github.com/SimonSapin/kuchiki/commit/0f89e187e3298b2ad9a7c0a96f9915d00a71be1a to .travis.yml, changing kuchiki in the echo … line to the name of the "main" crate.
Commit and push to trigger a new build. (Maybe push to a temporary branch where you can freely rewrite commit history until everything is set up right.)

Great, thanks for your short guide! This will definitely save me some time.

Closed in: https://github.com/tomprogrammer/rust-ascii/commit/0d67777478e2fd0c95698d5ea09f4eaec74f0d61


Migrate authN tests

Link to JIRA ticket if there is one: GQE-278
New Features
Breaking Changes
Bug Fixes
Improvements
Dependency updates
Deployment changes

This all looks good! Maybe take a look at the changes you made to logging in the get_tokens function in the ras.py file to make sure it's what was intended (I see you removed logging for the input json data on the post request) but other than that this should be good to merge!

Logger statements are now removed.


Keyboard Input not working when mouse cursor is hovered over the application's window

VSCode Version: 1.17.1
OS Version: CentOS7.3.1611

Steps to Reproduce:

Manually install an extension from a VSIX.
Use the prompt to 'reload' the editor
Typing is no longer possible unless I move the mouse outside of the application window. I can repeatedly tap on the 'a' key and hover my mouse off the vscode window and 'a' start apearing next to the cursor as expected then hover my mouse back over the vscode window and 'a' no longer appears

Does this issue occur when all extensions are disabled?: Yes

I am seeing the same issue.

Does this still happen?


Create a  AliYun Image for MLSQL Testing

The Image is based on Ubuntu 16-64.
The following software should be installed under the webuser account:

Conda
/home/webuser/apps/spark 2.2/2.3/2.4
OpenJDK, notice that  we need JDK not JRE.
maven

Once Conda is installed, make sure there is a enviroment named  "mlsql" ready.
the mlsql should contain:

oss2
aliyun-python-sdk-core-v3
aliyun-python-sdk-ecs

This Image will be used in ECS instances created by scripts.
The scripts will send a shell script to the ECS instance which will do the following jobs:

download MLSQL releases  from oss2 to /home/webuser/apps/mlsql-test directory.
start MLSQL server
post mslql script to the server and check the result.

Image in aliyun had been create, something had been changed.
I had create 2 enviroments, one named mlsql-2.7 that python version is 2.7, another is mlsql-3.5 that python version is 3.5.
Both of then had install that packages you specify

Awesome! @RebieKong

if anyone want to have a choice,you can comment you aliyun uid under this issue,i will share it to you


[Feature] tooltip position callback with canvas rect info to get global cursor position

What problem does this feature solve?
When custom tooltip with appendWithBody and position callback, we want place tooltip along with cursor.
We try to get tooltip position with dom.getBoundingClientRect but it will flash because it`s rect will be changed with position callback.
eg
    position: (point, params, dom: HTMLDivElement, rect, size) => {
      const { contentSize } = size;
      const [contentWidth, contentHeight] = contentSize;
      const tooltipDomRect = dom?.getBoundingClientRect?.();
      const offsetX = tooltipDomRect?.x + contentWidth + 20 > window.innerWidth ? -20 - contentSize[0] : 20;
      const offsetY = tooltipDomRect?.y + contentHeight > window.innerHeight ? -20 - contentSize[1] : 20;
      return [point[0] + offsetX, point[1] + offsetY];
    },

If we have canvas rect info ,  calculating cursor global position will be easier using canvasRect.x + point[0] and canvasRect.y + point[1].
We can calculate tooltip position by cursor global position and window.innerWidth/innerHeight.
What does the proposed API look like?
just like
position: (point, params, dom: HTMLDivElement, rect, size, canvasRect)

I am not sure what rect param is. It always be null in my tests.


[extractor/common] improve m3u8 info extraction

parts from the documention that explain some of the changes.

If an EXT-X-STREAM-INF tag contains a RESOLUTION attribute and a
VIDEO attribute, then every alternative video Rendition MUST have
an optimal display resolution matching the value of the RESOLUTION
attribute.

                group = stream_info.get('VIDEO')
                if group:
                    groups[group] = r
...
                group = groups.get(media_info['GROUP-ID'])
                if group:
                    v.update(group)

If the media TYPE is AUDIO and the URI attribute is
missing, clients MUST assume that the audio data for this Rendition
is present in every video Rendition specified by the EXT-X-STREAM-INF
tag.

lang = media_info.get('LANGUAGE')
...
'language': lang,

Any sample M3U8 breaks current codes?

it extract some extra metadata about formats.
before:

youtube-dl -F http://www.crackle.com/the-art-of-more/2496419
[Crackle] 2496419: Downloading XML
[Crackle] 2496419: Downloading m3u8 information
[info] Available formats for 2496419:
format code      extension  resolution note
hls-meta         mp4        multiple   Quality selection URL
hls-127          mp4        192x108     127k , mp4a.40.5, avc1.42000b
hls-253          mp4        256x144     253k , mp4a.40.5, avc1.42000c
hls-475          mp4        416x234     475k , mp4a.40.5, avc1.42000d
http-c544        flv        544x306
http-360p        mp4        640x360
hls-935          mp4        704x396     935k , mp4a.40.5, avc1.4d001e
http-480p        mp4        852x478
http-480p_1mbps  mp4        852x478
hls-1827         mp4        896x504    1827k , mp4a.40.5, avc1.4d001f
hls-3837         mp4        1280x720   3837k , mp4a.40.5, avc1.4d001f (best)

after:
youtube-dl -F http://www.crackle.com/the-art-of-more/2496419
[Crackle] 2496419: Downloading XML
[Crackle] 2496419: Downloading m3u8 information
[info] Available formats for 2496419:
format code      extension  resolution note
hls-meta         mp4        multiple   Quality selection URL
hls-119          mp4        192x108    [en] 119k , mp4a.40.5, 15.0fps, avc1.42000b
hls-230          mp4        256x144    [en] 230k , mp4a.40.5, 30.0fps, avc1.42000c
hls-414          mp4        416x234    [en] 414k , mp4a.40.5, 30.0fps, avc1.42000d
http-c544        flv        544x306
http-360p        mp4        640x360
hls-709          mp4        704x396    [en] 709k , mp4a.40.5, 30.0fps, avc1.4d001e
http-480p        mp4        852x478
http-480p_1mbps  mp4        852x478
hls-1230         mp4        896x504    [en]1230k , mp4a.40.5, 30.0fps, avc1.4d001f
hls-2092         mp4        1280x720   [en]2092k , mp4a.40.5, 30.0fps, avc1.4d001f (best)

also from the previous example AVERAGE-BANDWIDTH should be more accurate than BANDWIDTH.
BANDWIDTH

The value is a decimal-integer of bits per second.
It represents the peak segment bit rate of the Variant Stream.
If all the Media Segments in a Variant Stream have already been
created, the BANDWIDTH value MUST be the largest sum of peak
segment bit rates that is produced by any playable combination of
Renditions.

AVERAGE-BANDWIDTH

The value is a decimal-integer of bits per second. It represents
the average segment bit rate of the Variant Stream.
If all the Media Segments in a Variant Stream have already been
created, the AVERAGE-BANDWIDTH value MUST be the largest sum of
average segment bit rates that is produced by any playable
combination of Renditions.

as a first step add some code to extract the subtiltes availibility simular to the one from extrac_smil*.
extract multiple audio formats if they are available in the manifest(multiple EXT-X-MEDIA with URI).
EXT-X-MEDIA as a fourth value that's not checked before(CLOSED-CAPTIONS).
even if some of this cases are not widely used i think it's good to implement them in case they appear.

Any ETA on this? This code should be useful for vlive extractor.
Sample playlists if you need some real examples:
#EXTM3U
#EXT-X-VERSION:3
#EXT-X-MEDIA:TYPE=SUBTITLES,GROUP-ID="subs",NAME="Vietnamese",FORCED=NO,AUTOSELECT=YES,URI="subtitlelist_lvie.m3u8",LANGUAGE="vie"
#EXT-X-MEDIA:TYPE=SUBTITLES,GROUP-ID="subs",NAME="English",FORCED=NO,AUTOSELECT=YES,URI="subtitlelist_leng.m3u8",LANGUAGE="eng"
#EXT-X-MEDIA:TYPE=SUBTITLES,GROUP-ID="subs",NAME="zcn",FORCED=NO,AUTOSELECT=YES,URI="subtitlelist_lzcn.m3u8",LANGUAGE="zcn"
#EXT-X-STREAM-INF:BANDWIDTH=1464974,CODECS="avc1.66.22,mp4a.40.2",RESOLUTION=640x368,SUBTITLES="subs"
chunklist.m3u8?__agda__=1461853927_d2d91835e251112f931019235adf7e99

#EXTM3U
#EXT-X-VERSION:3
#EXT-X-MEDIA:TYPE=SUBTITLES,GROUP-ID="subs",NAME="English",FORCED=NO,AUTOSELECT=YES,URI="subtitlelist_leng.m3u8",LANGUAGE="eng"
#EXT-X-MEDIA:TYPE=SUBTITLES,GROUP-ID="subs",NAME="zcn",FORCED=NO,AUTOSELECT=YES,URI="subtitlelist_lzcn.m3u8",LANGUAGE="zcn"
#EXT-X-STREAM-INF:BANDWIDTH=1552079,CODECS="avc1.66.41,mp4a.40.2",RESOLUTION=640x368,SUBTITLES="subs"
chunklist.m3u8?__agda__=1461870184_78a9da91e282182e47a811c0dd3c2c98

#EXTM3U
#EXT-X-VERSION:3
#EXT-X-STREAM-INF:BANDWIDTH=540832,CODECS="avc1.66.22,mp4a.40.2",RESOLUTION=640x368
chunklist.m3u8?__agda__=1461875868_c243897d8537d171a6ae968612588b42

@remitamine Any reason not using the old key, value loop?

@remitamine Any reason not using the old key, value loop?

there are some parts that depend on other information so i select only the part i need parse it completly then i pass to other parts(it should not depend on the order of tags).


Samsung A21S bootloop

Device name: Samsung A21S
Rom name: OneUI 4.1
Android version: 12
Pixelify version: 3.0

Bug Description:
Bootloop
I can't find the boot logs

hi,
when installing this module (v.3.0) on my Samsung A50 (Fresh 4.5 Custom ROM) I also get a phone stuck on a boot animation logo (fist time after installing module phone rebooted itself, but now it simply get's stuck while booting).
Disabling the pixelify module in recovery allows to boot properly..
Any ideas how to debug/check this further?
some version:

A12
OneUI 4.1.1
recent mint kernel (4.14.194 @1378)
magisk 26.4


exa: init at git 2016-02-15

This is my first work with the Nix package manager (with which I am not very familiar, since I don't use NixOS). Please let me know if the placement of my package in the Nix tree is proper or not.
I'm using a git revision due to some changes since the latest tagged release of exa that make compilation possible without a beta or nightly Rust.
I have also added myself as a maintainer, as I'd like to continue to maintain future releases of this package.
The exa issue regarding the addition of this package may be seen at https://github.com/ogham/exa/issues/98.

Would it be more appropriate to place this package in pkgs/tools/text/exa?

@ehegnes Personally, I would put it in pkgs/tools/misc/, because that's where coreutils (where the real ls is) and findutils (similar type of programs) are. But I can see how the appropriate place can be subjective!
Apart from the comment about updating the date and the question about where to place it, it looks good to me!

I have made the recommended changes. Thanks for the help! :)

Merged. Thanks!


human-state-estimator depends on xsens-mvn and such dependency is not documented

See https://github.com/robotology-playground/human-dynamics-estimation/blob/master/human-state-provider/CMakeLists.txt#L8 .
cc @lucaTagliapietra

This dependency should have been very temporary.
Those YARP interfaces should be integrated in YARP devel

In HDEv2 the dependency from xsens-mvn is dropped, and it will be replaced by the dependency on wearables (It will require to be properly documented).

We are closing this issue.


added android splash screen

Added Android Splash Screen

This is done incorrectly @thelosergeek. You must do it in React Native, not in Android. This is not only an Android application. I'm going to close this PR. :)


Adds support to metrics computed for a target branch

Description
Self-explained. This will allow easy implementation of stability of main branch use case
Types of changes

[ ] House cleaning (change at project level, like tooling revamp, refactors, etc)
[ ] Bug fix (non-breaking change which fixes an issue)
[ ] Enhancement (non-breaking change which improves existing functionality)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (something that would cause existing functionality to not work as expected)
[ ] Documentation (self-explained)

Implementation details
N/A

Codecov Report

Merging #85 (6290776) into main (b986181) will increase coverage by 0.58%.
The diff coverage is 97.72%.

@@            Coverage Diff             @@
##             main      #85      +/-   ##
==========================================
+ Coverage   85.68%   86.26%   +0.58%
==========================================
  Files          11       11
  Lines         454      466      +12
==========================================
+ Hits          389      402      +13
+ Misses         65       64       -1

Impacted Files
Coverage Δ

bitrise_reports/bitrise.py
95.91% <80.00%> (+1.12%)
:arrow_up:

bitrise_reports/app.py
100.00% <100.00%> (ø)

bitrise_reports/di.py
100.00% <100.00%> (ø)

bitrise_reports/entrypoint.py
100.00% <100.00%> (ø)

bitrise_reports/metrics.py
100.00% <100.00%> (ø)

bitrise_reports/middleware.py
83.33% <100.00%> (+4.02%)
:arrow_up:

bitrise_reports/models.py
100.00% <100.00%> (ø)

Continue to review full report at Codecov.

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


network-caching=1000 (option) e opto refer

Hi.
Care to explain the advantages of these modifications?
Opto channels work fine without the referrer parameter and cache is something that needs to be tested by each person, therefore should be set at the player level, not the M3U file.

I put the cache etc and tested it on Kodi libreelec the sic soap operas have pubs opto apk etc and it gets stuck that's why I did it like this but I haven't tested it well yet because the url that this is is yours here I have to upload the modified file somewhere and configure that there.
Now I don't know if with the reference the opto channels stop talking about the app etc. Maybe the headers prevent this. But as I said, I didn't test this well, I did it here locally with VLC but VLC reads everything easily

As far as the net cache is concerned, you might be right, I gave it a value of 1 second, I was looking at VLC and it gives its value, I removed it and left only the opto heads.


Add ability to filter data in multiple dropdown for GridView

Now  GridView could filter the data sent through the multiselect. Also added option to delay before sending data. Now user can select the values in multiselect (important for PJAX-update grid) without force reloading of page
Thanks to  @maxlapko for the help

Resolved by d3cfb87, #10302


Default initial value during widget build or in a button click.

Why there is no option here to initialize a default parent or children check value?  for example, during widget build, I want to set a specific parent or children as true so that the user can uncheck it if they want.

That's a nice idea actually. If you have a solution, feel free to work on it :)


 I developed a tiny little diffusion drawing app to make it easier to use the scribble model. It is free and open source, and you can use any Stable Diffusion model on HuggingFace with just two command line arguments:
pip install tldream
tldream --model runwayml/stable-diffusion-v1-5 --device cuda

https://github.com/Sanster/tldream
https://user-images.githubusercontent.com/3998421/223440685-c1f6ab9d-52b9-4cb2-a86a-6b0376f9893b.mp4

Awesome!


NOT_IMPLEMENTED warning message for OPEN type message

Saw the following messages:
Warn: NOT_IMPLEMENTED: OPEN Capability 2 is either unknown or currently unsupported (parsebgp_bgp_open.c:103)
WARN: NOT_IMPLEMENTED: OPEN Capability 64 is either unknown or currently unsupported (parsebgp_bgp_open.c:103)
WARN: NOT_IMPLEMENTED: OPEN Capability 70 is either unknown or currently unsupported (parsebgp_bgp_open.c:103)

Since OPEN messages are relatively simple, we might implement those to suppress frequent appearances of such messages.

The command I'm running: bgpreader -w<PHONE_NUMBER>,1524578400 -k <IP_ADDRESS>/24 -t updates.
I'm running the most recent version on master.
Some more of such warning messages.
WARN: NOT_IMPLEMENTED: BGP UPDATE Path Attribute 128 is not yet implemented (parsebgp_bgp_update.c:554)
WARN: NOT_IMPLEMENTED: OPEN Capability 128 is either unknown or currently unsupported (parsebgp_bgp_open.c:103)
WARN: NOT_IMPLEMENTED: OPEN Capability 2 is either unknown or currently unsupported (parsebgp_bgp_open.c:103)
WARN: NOT_IMPLEMENTED: OPEN Capability 69 is either unknown or currently unsupported (parsebgp_bgp_open.c:103)
WARN: NOT_IMPLEMENTED: OPEN Capability 73 is either unknown or currently unsupported (parsebgp_bgp_open.c:103)
WARN: NOT_IMPLEMENTED: OPEN Capability 64 is either unknown or currently unsupported (parsebgp_bgp_open.c:103)
WARN: NOT_IMPLEMENTED: OPEN Capability 128 is either unknown or currently unsupported (parsebgp_bgp_open.c:103)
WARN: NOT_IMPLEMENTED: OPEN Capability 2 is either unknown or currently unsupported (parsebgp_bgp_open.c:103)
WARN: NOT_IMPLEMENTED: OPEN Capability 69 is either unknown or currently unsupported (parsebgp_bgp_open.c:103)
WARN: NOT_IMPLEMENTED: OPEN Capability 73 is either unknown or currently unsupported (parsebgp_bgp_open.c:103)
WARN: NOT_IMPLEMENTED: OPEN Capability 64 is either unknown or currently unsupported (parsebgp_bgp_open.c:103)


[Storage] Nightly build failed for storage-file

https://dev.azure.com/azure-sdk/internal/_build/results?buildId=15096

https://github.com/Azure/azure-sdk-for-js/pull/2041


jax.numpy.isscalar returns False for numpy scalars

this is somewhat inconsistent
>>> import numpy as np
>>> import jax.numpy as jnp
>>> a_np = np.array(3)
>>> a_jnp = jnp.array(3)
>>> jnp.isscalar(3)
True
>>> jnp.isscalar(a_jnp)
True
>>> jnp.isscalar(a_np)
False

I believe JAX follows numpy's behavior here in not treating zero-dimensional numpy arrays as scalars:
>>> import numpy as np
>>> a = np.array(3)
>>> np.isscalar(a_np)
False

I'm not sure why numpy makes this choice.

But then you treat jax 0-dimensional arrays as scalars.
That is inconsistent to me.

I mean, if you are diverging from the jax API, i believe you should be consistent and return True also for numpy arrays.
Otherwise you should return False both for jax and numpy scalars.

I see – you're right that there is an inconsistency here. The reason we implemented this behavior for jnp.isscalar is to make it jit invariant:
>>> jit(jnp.isscalar)(1) == jnp.isscalar(1)
True

In a jit context, Python scalars are lowered to one-dimensional arrays, so those arrays must be treated as scalars when created from Python values.
If the zero-dimensional arrays are created in a different manner, this is not the case:
>>> x = np.array(1)
>>> jnp.isscalar(jnp.array(x))
False

So there is going to be an inconsistency somewhere. Perhaps it would be better if JAX broke with numpy and treated all zero-dimensional arrays as scalars? After all, unlike numpy, JAX has no scalar types (it uses zero dimensional arrays). But I'm not sure. What do you think?

In any case, according to numpy docstring (pasted below) the main reason for isscalar to diverge from ndim==0 is unrelevant to jax so you might as well break with it.
Surely, if your argument for breaking with the numpy API was being jit-invariant (a very valid argument indeed, and i agree with it), then you should go all the way with it and return True for numpy arrays too.
    Notes
    -----
    If you need a stricter way to identify a *numerical* scalar, use
    ``isinstance(x, numbers.Number)``, as that returns ``False`` for most
    non-numerical elements such as strings.

    In most cases ``np.ndim(x) == 0`` should be used instead of this function,
    as that will also return true for 0d arrays. This is how numpy overloads
    functions in the style of the ``dx`` arguments to `gradient` and the ``bins``
    argument to `histogram`. Some key differences:

    +--------------------------------------+---------------+-------------------+
    | x                                    |``isscalar(x)``|``np.ndim(x) == 0``|
    +======================================+===============+===================+
    | PEP 3141 numeric objects (including  | ``True``      | ``True``          |
    | builtins)                            |               |                   |
    +--------------------------------------+---------------+-------------------+
    | builtin string and buffer objects    | ``True``      | ``True``          |
    +--------------------------------------+---------------+-------------------+
    | other builtin objects, like          | ``False``     | ``True``          |
    | `pathlib.Path`, `Exception`,         |               |                   |
    | the result of `re.compile`           |               |                   |
    +--------------------------------------+---------------+-------------------+
    | third-party objects like             | ``False``     | ``True``          |
    | `matplotlib.figure.Figure`           |               |                   |
    +--------------------------------------+---------------+-------------------+
    | zero-dimensional numpy arrays        | ``False``     | ``True``          |
    +--------------------------------------+---------------+-------------------+
    | other numpy arrays                   | ``False``     | ``False``         |
    +--------------------------------------+---------------+-------------------+
    | `list`, `tuple`, and other sequence  | ``False``     | ``False``         |
    | objects                              |               |                   |
    +--------------------------------------+---------------+-------------------+

Apparently the behaviour is also not consistent between a regular JAX array and an abstract array:
>>> jnp.isscalar(jnp.array(0.0))
True
>>> jnp.isscalar(jax.ShapedArray((), dtype=float))
False

ShapedArray objects will never be passed to jnp functions directly in the normal course of things, so I don't think this is an issue.


[SymbolGraph] Add additional filtering test NFC

Adds an additional test case to make sure relationships are also filtered out
when checking if extended types are "implicitly private". NFC.
rdar://61843516

@swift-ci Please smoke test


Added release notes for new operator release and updated the document…

…ation for startupProbe and terminationGracePeriodSeconds

Released 12 July.


Add custom op MulMulSigmoid

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 84.75%. Comparing base (2e56978) to head (50daa69).

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #185   +/-   ##
=======================================
  Coverage   84.75%   84.75%
=======================================
  Files          58       58
  Lines        7050     7050
=======================================
  Hits         5975     5975
  Misses       1075     1075

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


Clarify NSG Flow Log Retention Policy

I would like to understand two parameters associated with retention policy
			"retentionPolicy": {
				"days": "0",
				"enabled": true
			},

Document says set days to 0 if I don't require the policy feature.
In may case, I send log to storage account, and I use storage account life cycle to manage log retention.
So what the configuration should be?
days: 0
enabled: true
or
days: any
enable: false
Document link:
https://docs.microsoft.com/en-us/azure/network-watcher/network-watcher-nsg-flow-logging-overview#nsg-flow-logging-considerations
If you do not require the retention policy feature, we recommend that you set this value to 0
[Enter feedback here]

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

ID: bd699dac-d6e5-5a39-624f-2d3f77f92fca
Version Independent ID: c922bcd2-0778-a7af-4855-1bff6c9ce380
Content: Introduction to flow logging for NSGs - Azure Network Watcher
Content Source: articles/network-watcher/network-watcher-nsg-flow-logging-overview.md
Service: network-watcher
GitHub Login: @damendo
Microsoft Alias: damendo

This is a critical question for compliance reason, can you please prioritize and provide guidance ASAP? Thank you!

This is a critical question for compliance reason, can you please prioritize and provide guidance ASAP? Thank you!

@RonnieQuan Thanks for your comment! We will review and provide an update as appropriate.

@RonnieQuan Thanks for your comment! We will review and provide an update as appropriate.

@RonnieQuan, Appreciate your patience. days: 0 is infinite retention where infinite retention = no deletion. We are assigning this issue to the respective content author for updating the doc if necessary.

@RonnieQuan, Appreciate your patience. days: 0 is infinite retention where infinite retention = no deletion. We are assigning this issue to the respective content author for updating the doc if necessary.

@SubhashVasarapu-MSFT
Can you please confirm the retention is on my storage account which I defined for the flow log settings
or the retention is on underlying storage account from MS Azure internally for the service?

The behavior as follows:
If Enabled = False, The retention policy is disabled irrespective of days mentioned.
If Enabled = True, Policy set for days given.
If Enabled = True and days = 0 , Effectively policy is disabled as days specified is 0.
Thus, setting enabled = false or setting days = 0 has same effect.
for above case, the best setting would be:
enabled = false
days =0

As advised by my manager @jyothisuri, closing the issues that are older than a year.
#please-close


Garbage collection

Currently, the VM uses reference counting.
This has a number of benefits, such as:

Simplicity: no extra code needed to implement, as it's part of Rust's standard library.
Easier interoperability: Objects do not need to have their lifetime bound to the VM. Anyone can allocate an object at any time, hand it to the VM, or take one out of the VM and store it.
Determinism: Objects are deallocated when their reference count reaches 0, there are no heuristics to defer deallocation.

But it also has downsides, mainly in performance:

Slow allocation: Rc<T> does not support the allocator API, so allocations always go through the global allocator.
Reference count tracking: There are currently 129 calls to .clone() in the runtime crate. Most of these are due to reference counting, all of which could be eliminated by using a tracing garbage collector.

We could trade the simplicitly and interoperability for better performance by implement a tracing garbage collector. Values taken out of the VM would have to be tied to its lifetime (this is easily done via a ValueRef<'a>/HandleRef<'a, T> with a PhantomData field). It would ideally be incremental, so that we may trade a lower impact of garbage collection cycles for lower maximum throughput.

https://github.com/jprochazk/mu/issues/8 was the first step towards this.

In the end, reference counting probably is more suitable for the goals of this project. In particular, reference counting is the easiest way to implement precise garbage collection, which ends up using the least memory. Runtime performance isn't always the most important property of an interpreter, low footprint is nice to have too, and reference counting certainly performs better there. Not to mention the overall reduced complexity of the implementation by not using a tracing garbage collector.


Send Access-Control-Allow-Origin header on 401 from custom authorizer

Due to an issue with API Gateway 4xx response from customer authorizers do not include CORS headers 😞
Further reading: https://forums.aws.amazon.com/thread.jspa?threadID=228211

https://aws.amazon.com/about-aws/whats-new/2017/06/amazon-api-gateway-enables-customization-of-error-responses/

This has to be done manually via the API Gateway console for now: http://docs.aws.amazon.com/apigateway/latest/developerguide/customize-gateway-responses.html#set-up-gateway-response-using-the-console.
See https://github.com/serverless/serverless/issues/3896 for Serverless discussion about scripting via CF.

Fixed in 6615299d0c426a7fefd3b033e9ad173c90bae786


Import fails for Blender assets

Bug description
I'm unable import blender assets because Blender is not installed in the container.

How to reproduce

Create a unity project with and import a .blend asset.

Expected behavior
I expect the asset to import correctly during build. However, I get the error:
2021-05-30T16:57:28.0980276Z Start importing Assets/tri.blend using Guid(1b0313b4d58e97d48b962f87d82a4889) Importer(-1,00000000000000000000000000000000) Error: execv(blender): No such file or directory -1Blender could not be launched.
2021-05-30T16:57:28.0982236Z Make sure that Blender is installed correctly and in your PATH.

It would be helpful to be able to import Blender assets without being required to convert them to a different format.

Thank you for creating this issue @dtrailin.
I would consider this an enhancement instead of a bug, since we're working with an incremental approach and this is functionality that we are not yet supporting.
As I understand it, blender would have to be installed for the assets to be imported correctly. The installation is about 190MB which might be acceptable to install in the unity-editor docker image. Either way in order to support this, it would have to be fixed upstream in game-ci/docker.

For reference, this was previously discussed here (when we were using gableroux/unity3d docker images):  https://gitlab.com/gableroux/unity3d-gitlab-ci-example/-/issues/19
Suggested solution should also apply here, we should document and explain how we can customize docker images to add dependencies like that. 👍

Blender assets will be supported as part of a plugin system in v3.0.0 which is tracked on the Roadmap to v3.0.0.


x/build: system linker warnings on macOS 10.15 when using cgo

What version of Go are you using (go version)?

$ go version

go version go1.15.2 darwin/amd64

Does this issue reproduce with the latest release?
Yes.
It seems this issue is related to https://github.com/golang/go/issues/36025.
What operating system and processor architecture are you using (go env)?
go env Output
$ go env
GO111MODULE="on"
GOARCH="amd64"
GOBIN=""
GOCACHE="/Users/peterlai/Library/Caches/go-build"
GOENV="/Users/peterlai/Library/Application Support/go/env"
GOEXE=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="darwin"
GOINSECURE=""
GOMODCACHE="/Users/peterlai/go/pkg/mod"
GONOPROXY=""
GONOSUMDB=""
GOOS="darwin"
GOPATH="/Users/peterlai/go"
GOPRIVATE=""
GOPROXY="https://proxy.golang.org,direct"
GOROOT="/usr/local/Cellar/go/1.15.2/libexec"
GOSUMDB="sum.golang.org"
GOTMPDIR=""
GOTOOLDIR="/usr/local/Cellar/go/1.15.2/libexec/pkg/tool/darwin_amd64"
GCCGO="gccgo"
AR="ar"
CC="clang"
CXX="clang++"
CGO_ENABLED="1"
GOMOD="/Users/peterlai/diode_go_client/go.mod"
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/sw/qywtwldj7vj9wh26cry0cngm0000gn/T/go-build398699140=/tmp/go-build -gno-record-gcc-switches -fno-common"

What did you do?
Recently I upgraded golang from 1.14.4 to 1.15.2 with brew upgrade go.
After I upgraded, there are couple of warnings when I build our client, which we use cgo because of using openssl library, the source code: https://github.com/diodechain/diode_go_client/.
What did you expect to see?
No output on stdout/stderr.
This output was not shown with my system using go 1.14.4
What did you see instead?
When running the run command, or the go build command, I have the following output:
ld: warning: object file (/var/folders/sw/qywtwldj7vj9wh26cry0cngm0000gn/T/go-link-116021407/000000.o) was built for newer OSX version (10.15) than being linked (10.14)
ld: warning: object file (/var/folders/sw/qywtwldj7vj9wh26cry0cngm0000gn/T/go-link-116021407/000001.o) was built for newer OSX version (10.15) than being linked (10.14)
ld: warning: object file (/var/folders/sw/qywtwldj7vj9wh26cry0cngm0000gn/T/go-link-116021407/000002.o) was built for newer OSX version (10.15) than being linked (10.14)
ld: warning: object file (/var/folders/sw/qywtwldj7vj9wh26cry0cngm0000gn/T/go-link-116021407/000003.o) was built for newer OSX version (10.15) than being linked (10.14)
ld: warning: object file (/var/folders/sw/qywtwldj7vj9wh26cry0cngm0000gn/T/go-link-116021407/000004.o) was built for newer OSX version (10.15) than being linked (10.14)
ld: warning: object file (/var/folders/sw/qywtwldj7vj9wh26cry0cngm0000gn/T/go-link-116021407/000005.o) was built for newer OSX version (10.15) than being linked (10.14)
ld: warning: object file (/var/folders/sw/qywtwldj7vj9wh26cry0cngm0000gn/T/go-link-116021407/000006.o) was built for newer OSX version (10.15) than being linked (10.14)
ld: warning: object file (/var/folders/sw/qywtwldj7vj9wh26cry0cngm0000gn/T/go-link-116021407/000007.o) was built for newer OSX version (10.15) than being linked (10.14)
ld: warning: object file (/var/folders/sw/qywtwldj7vj9wh26cry0cngm0000gn/T/go-link-116021407/000008.o) was built for newer OSX version (10.15) than being linked (10.14)
ld: warning: object file (/var/folders/sw/qywtwldj7vj9wh26cry0cngm0000gn/T/go-link-116021407/000009.o) was built for newer OSX version (10.15) than being linked (10.14)
ld: warning: object file (/var/folders/sw/qywtwldj7vj9wh26cry0cngm0000gn/T/go-link-116021407/go.o) was built for newer OSX version (10.15) than being linked (10.14)
ld: warning: object file (/var/folders/sw/qywtwldj7vj9wh26cry0cngm0000gn/T/go-link-116021407/000010.o) was built for newer OSX version (10.15) than being linked (10.14)
ld: warning: object file (/var/folders/sw/qywtwldj7vj9wh26cry0cngm0000gn/T/go-link-116021407/000011.o) was built for newer OSX version (10.15) than being linked (10.14)
ld: warning: object file (/var/folders/sw/qywtwldj7vj9wh26cry0cngm0000gn/T/go-link-116021407/000012.o) was built for newer OSX version (10.15) than being linked (10.14)
ld: warning: object file (/var/folders/sw/qywtwldj7vj9wh26cry0cngm0000gn/T/go-link-116021407/000013.o) was built for newer OSX version (10.15) than being linked (10.14)
ld: warning: object file (/var/folders/sw/qywtwldj7vj9wh26cry0cngm0000gn/T/go-link-116021407/000048.o) was built for newer OSX version (10.15) than being linked (10.14)
ld: warning: object file (/var/folders/sw/qywtwldj7vj9wh26cry0cngm0000gn/T/go-link-116021407/000049.o) was built for newer OSX version (10.15) than being linked (10.14)
ld: warning: object file (/var/folders/sw/qywtwldj7vj9wh26cry0cngm0000gn/T/go-link-116021407/000050.o) was built for newer OSX version (10.15) than being linked (10.14)
ld: warning: object file (/var/folders/sw/qywtwldj7vj9wh26cry0cngm0000gn/T/go-link-116021407/000051.o) was built for newer OSX version (10.15) than being linked (10.14)

I can remove these warning with the CGO_CFLAGS=-mmacosx-version-min=10.12 (found in this commit: https://go-review.googlesource.com/c/build/+/216304/5/cmd/release/release.go#367)

Changed this to an x/build issue since I believe this is an issue with the packaging.

/cc @andybons @dmitshur @toothrot

@gopherbot add OS-Darwin

@sc0Vu Do you encounter the same error if you download and use the pkg from the golang site?

Just chiming in, I encountered this same error after upgrading to go 1.15 with brew. Removing the version of go installed by brew and then installing the pkg from the golang site resolved my issue.


Remove duplication from autoInstall* profiles

This works on the principle that downstream projects
include the relevant plugin.
The configuration that enables installation is set in
a profile in the parent pom, but only in a pliginManagement
section. Thus the profile does not switch the plugin on/off
but it instead switches the configuration on/off. This way
profiles for different sub-project types (i.e. bundle and
content package) can be run on the full build, as e.g. the
contentpackage plugin is not enabled in a bundle sub-project.

Thanks for the contribution!
Applied in c653d8e42debb51cae3ed696e868b70c4cad3a9e


recode() failing in some single --> delimited set cases

We're seeing this error:
ValueError: invalid literal for int() with base 10: '1.0'

Resolved by PR #130


Update plotting to work with Matplotlib 2.2+.

In recent versions of Matplotlib, axes.color_cycle doesn't exist,
so the plotting routines throw a KeyError.  This fixes that.
I believe the fix is backward-compatible.

Hey @ketch, thanks for your PR!
I updated the master branch such that it runs fine on Travis CI again. Can you rebase?
And regarding the fix: it seems like axes.color_cycle was replaced with axes.prop_cycle – can you verify this and change the PR accordingly?

So from what I see it's the best solution if we update pseudopy to use axes.prop_cycle so we don't have any hard-coded values in there. I think you can then just update your preferences in your matplotlibrc as described in https://matplotlib.org/users/dflt_style_changes.html#colors-color-cycles-and-color-maps – would that work for you?
And I'm glad you find pseudopy useful! :) If you're using it in a project that is available publicly (github or elsewhere) I'd be happy to include a link to it in the README.

it's the best solution if we update pseudopy to use axes.prop_cycle so we don't have any hard-coded values in there

Sure, that seems fine.  I just didn't have time to figure out the syntax and this aspect wasn't important to me.
So far I've used pseudopy a few times for teaching purposes.  If I use it in a more serious way, I will let you know.

Do you want to update the PR to use axes.prop_cycle?

No; like I said before: feel free to patch it your way and close this.

Fixed in 1.2.5.


TypeError on trajectory_gpt2.py

When I ran experiment.py, it comes out an error with:
File "D:\ReinformentLearning\decision-transformer-master\gym\decision_transformer\models\trajectory_gpt2.py", line 590, in GPT2Model
config_class=_CONFIG_FOR_DOC,
TypeError: add_code_sample_docstrings() got an unexpected keyword argument 'tokenizer_class'
I guess it should be the problem of different versions of transformer, but I cannot solve.
Thanks

@dljzx  w do you solve this problem?

This problem is caused by using a different version of transformers.
You can solve this problem by installing transformers==4.5.1 or by manually changing the tokenizer_class to processor_class.
However, it is recommended to use 4.5.1 as specified in this repository, as using a different version of transformers will cause a new error elsewhere.


Understanding Pciseq output

Hi again,
I am doing some more tests with Pciseq and have now completed several runs.
What I would like to do is compare the Pciseq output with other segmentation & assignment outputs.
To do that I would like to construct a Cell x Gene matrix containing the spots assigned by Pciseq.
Do you have suggestion on how to accomplish that? What unit is CellGeneCount in cellData in?
Or do I need to group geneData by the assinged neighbour?
Thank you!

Hi
I saw your msg, I will get back to you later today. If you have set save_data to True when you did the run, then you should have a pickle saved in the temp dir, from that you can get the cell by gene array, it is in obj.cells.geneCount where obj is the pickle object,
I will come back later in anycase

Thanks.
I see that it contains one more cell then the cells dataframe. I guess there is the zero cell in there ?

yes, the top row, cell with label = 0, is the background. It doest have any values here, it contains zeros only. If you want to get the  counts on the background then this is in .cells.background_counts. The sum of the two, ie obj.cells.background_counts.sum() + obj.cells.geneCount.sum() will be the total number of your spots
The cell labels are the row numbers in .cells.geneCount, ie the
row number = 0 is the cell label = 0, ie the background
row number = 1 is the cell label = 1, etc
The column labels are the genes sorted alphabetically, we can get it from obj.genes.gene_panel
However those labels (lets call it pciSeq labels) might not be the same with the labels you pass in with your segmentation array from cellpose for example. Cellpose might give labels which have gaps between them like, 1,2,3,5, 10, 11, etc.
If you want to get the mapping between cellpose and pciSeq labels then call obj.counts_within_radius(10) and look at the first two columns. Im cannot check right now, but I think that should work

Perfect!
Everything is set-up exactly as you are saying.
The cellpose-pciseq mapping will also come in very handy

Hi
I didnt give an answer to your question, "What unit is CellGeneCount in cellData in?",
These are the counts of the corresponding gene in a given cell. If you are puzzled why these are not integers, the answer is because of the nature of pciSeq. This is a soft clustering algoritm and not a hard one where something either belongs to a cell or does not. Here everything comes with a probability.
To put it in a very simplistic way, lets say we have only two cells and just one spot. If for example you think that it is equally likely the spot to "belong" to any of the two cells, then you would give 0.5 counts to the first cell and another 0.5 to the second.
Similarly if you see for example that  a cell has lets say 1.4 counts of Npy, one way you could end up to something like that is to have two Npy spots, one assigned to the cell with 100% probability and the other spot with 40%.
A hard clustering approach is a special case of this where the assignemnt probabilities are 100%


Docker Setup for Production Environment

Hi All,
I want to setup Peatio in production envrionment using Docker. Can anybody please help me with the steps?

Can anybody please help me?

setting up, Peatio, Barong and Trading UI is simple using docker container.
Docker does it all installation/setup/settings for you.
please view instruction here

Anybody was setup Peatio in production (Docker or Ubuntu)?:)

Contact me in my telegram https://t.me/Poseidon_j
Thanks

@blacklevel7 Yes, Docker and Kubernetes.
You can easy find me if look for my username.

@blacklevel7 Yes, Docker and Kubernetes.
You can easy find me if look for my username.


Revert "Fix jumping when doing long press for selecting text"

Reverts flutter/flutter#102270
This broke internal google tests
Googlers, see b/230165332

The internal issue is closed, noting that the changes are acceptable, so I don't understand why a revert is needed.

I've added more context to the internal bug. I defer to @LongCatIsLooong and @chunhtai but I suspect we could send a g3fix since this was a single test failing.

Hi @CaseyHillers
Why we have to revert the fix. With the bug, we are not able to use a selectable RichText which has a size taller than the screen size?

@rgevrek please coordinate the reland with @LongCatIsLooong and @chunhtai. The internal test failed as it has a hard coded assumption that inactive cursors allow jumping to. This is a test issue that should be fixed, and I don't see anything wrong with this PR.


chore(deps): update dependencies to latest versions

Fixes Or Enhances

chore: update dependencies to latest versions

go ver. 1.23
all dependencies to latest versions
GitHub Action workflow with go 1.23

@go-playground/validator-maintainers

@deankarn Is it ok to merge this PR?

@nodivbyzero no because of:

The addition of the /vendor directory and deps within.
Min Go supported version has been bumped from 1.17 to 1.21 which is a breaking change requiring a major version bump

coverage: 74.318%. remained the same
when pulling 04042d575c1091b6e8f19b56a565f52bd3d783f6 on nodivbyzero:upd-deps-dec-2024
into 6c3307e6c64040ebc0efffe9366927c68146ffba on go-playground:master.

@deankarn I've updated my PR and removed the vendor folder.
Quick question: Is there a requirement to support Go 1.18 as the minimum version?

Quick question: Is there a requirement to support Go 1.17 as the minimum version?

@nodivbyzero only that if anyone is still using Go 1.17 it would/could break people existing builds if we add anything that’s not backward compatible with 1.17 which is more likely than other version bumps because thats when generics were added. I would love to recommend others update to a newer version if in this situation but possible they can’t for some reason or other reasons.
We can add more recent features though, without bumping a major version(which is a pain because of the way go versions > v1 is in the import path itself and is prolific down the dependency tree), by adding compile time directives.
I can totally be convinced otherwise though and perhaps, for a future addition, can add to the README + docs that we support up to only say 3-4 version back from the latest.

@deankarn Thank you for the detailed explanation.
I noticed that the last major release occurred on November 17, 2019, which was five years ago. While maintaining compatibility with older Go versions is important, addressing vulnerabilities and keeping dependencies updated is equally critical.
Here's a proposed plan:

Notify the community via 'GitHub Discussions' about introducing a major version update cycle aligned with every three Go version updates.
Update the README to include a compatibility plan.
Close this PR for the time being.

What are your thoughts on this approach?

@nodivbyzero it sounds reasonable, but I want to think about it for a little bit first as the one aspect that still bothers me is that bumping major versions in Go causes all package imports needing to be updated as well.
This doesn’t sound like much when it’s a single project or repo, but even I have production code that spans many repos which updating like this becomes a major chore. Maybe not with this package specifically but I have seen subtle bugs and issues arise when you miss updating one of these imports in your dependency chain also when the package self-initializes/ is meant to be a singleton. (As a personal note I very much dislike how go has done this and IMO should have relied on the mod file to specify the version and not imports…)
I have been and will continue to read about how others handle this. This is an old discussion for Rust not Go but highlight the same issues https://github.com/rust-lang/api-guidelines/discussions/123

Closing this PR in favor of the discussion at https://github.com/go-playground/validator/discussions/1342


Python is open-source

Prerequisites
in readme.md:
IronPython is an open-source implementation of the Python programming language

The thing is... python IS open-source

[ ] Are you running the latest version?
[ ] Are you reporting to the correct repository?
[x] Did you perform a cursory search?

Description
[Description of the bug or feature]
Steps to Reproduce

[First Step]
[Second Step]
[and so on...]

Expected behavior: [What you expected to happen]
Actual behavior: [What actually happened]
Versions
You can get this information from executing ipy -V.

I don't see the problem...

in the readme file

@Advik-B Your quote is out of context. The full sentence is: IronPython is an open-source implementation of the Python programming language which is tightly integrated with .NET. (emphasis mine).
Your link points to CPython, another open-source implementation of the Python programming language, written in C and not related to .NET in any way. I see no problem in our documentation.

@BCSharp look... no programming lang is built JUST FOR .NET ( other than C#, F#, etc) and at first glance... anyone will think python is open-source
source of the image: https://www.educba.com/is-python-open-source/


proposal: x/tools/go/analysis: register debug flag in analysistest.Run

Proposal Details
Currently, flags for analysis driver are registered in an internal package and are used in the Main function that runs analysis.
It would be nice to register flags in analysistest.Run and RunWithSuggestedFixes. I am interested in particular in the debug flag that allows to run analyzer sequentially, that simplifies debugging tests.
Other issues I found and red regarding flags #65776, #53215, and #32155.

CC @golang/tools-team

Would this API https://github.com/golang/go/issues/61324, in particular, the Sequential flag, address your need?
If so, I'll bring that change back up to date and finally merge it.

@adonovan the proposal looks great! Looking forward to it to be merged :)


Tahiti does not hash

Tahiti
slow time resulting in 0 hash:
I get 2800ms 0's instaead of 110ms 0's
http://i.imgur.com/LLRoFsI.png

see nvidia not supported

Tahiti is HD 7950 , not nvidia

Tahiti is also AMD R9 280, AMD R9 280X


fix(material/schematics): improve logging of mdc-migration ts migrator

related to issue #26038

@wagnermaciel @devversion Reminder :)
I got this: https://github.com/angular/components/issues/26038#issuecomment-1399261981


Scaffold-DbContext false warnings

Scaffold-DbContext warns about all the potential issues with the indexes of the objects excluded by providing -Schemas switch. It seems like this switch does not limit indexes scope. Note the lack of the schema prefixes in the warning message.
Example:
PM> Scaffold-DbContext "Server..." Microsoft.EntityFrameworkCore.SqlServer -Context TestContext -Schemas test
Index column dbo.Content belongs to index PK_Content on table LanguageId which is not included in the selection set. Skipping.

Steps to reproduce: take any DB with tables and indexes, add 'test' schema, create any table in that 'test' schema, run Scaffold-DbContext for the 'test' schema only. You will get bunch of warnings about 'dbo' schema indexes.

Duplicate of #9334
Already fixed in 2.1 release.


Is this still viable under ROCm 5.6.0?

No updates in an extremely long time with all the modern ROCm releases I just wanted to know.

I currently have no plan to update it, this is mostly a one-off that I created to help a friend of mine fine tune stable diffusion on their card. Also it seems like people are already trying to do some maintainable contribution to upstream.


Update main.nf: '\t' revised to '\t' in R scripts

You have a merge conflict here - it probably means that you don't have the most recent updates in your copy of the repository.
You need to do a git pull - it will complain that you have a merge conflict in main.nf. If you open that file you'll find a bunch of markup identifying the conflict. Delete as appropriate, then git add, git commit and git push and hopefully that little button above will turn green.
You can also revert to before your change (git checkout HEAD^), pull the new changes (git pull) and then make your changes again (git add, git commit, git push). As you haven't done much in this PR this may be easier.


Too much time spent in net.(*netFD).dial

When evaluating results of #6877 I have noticed a very strange behavior of apiserver when running density tests on a 100 node cluster with 30 pods per node. It seems that sometimes we spent more than 40% of CPU time in net.(*netFD).dial function.
My suspicion is that it's because after each watch message we terminate old connection to etcd and create a new one. With multiple watchers and many update this can be very expensive.
@davidopp @lavalamp @wojtek-t @xiang90

Does the etcd client not reuse HTTP connections? I thought the go http client did that by default?

Actually looking at that chart I see it stuck in write, not dial-- am I blind?

@lavalamp I think it is write... The number on dail is confusing though...

@lavalamp There is a small, but very heavy branch on the left of the chart with "dial" path".

@fgrzadkowski But it shows 0.03s of 22.90s. It does not show where is the other 22.87s.

@xiang90 The way I read this profile (might wrong though) is that for 28.90s dial was in the stack, but was not the "top" function for 22.87s
@lavalamp I tried to verify that etcd client reuses HTTP connection and I think it doesn't. I added simple log line here:
https://github.com/GoogleCloudPlatform/kubernetes/blob/master/Godeps/_workspace/src/github.com/coreos/go-etcd/etcd/client.go#L387
In empty 100 node cluster it got called ~10k times in ~3.5 min. This gives 45 dials per second
@xiang90 Do you have a theory why we create so many connections? After adding cache in #7288 this is responsible for a biggest chunk of CPU time.

I also run density test to check how correlated this is with the load. Results below (first column is number of dials per minute, second column is time):
$ sudo docker logs a9374dd44497 2>&1 | grep FFF | tr -s " " | cut -d" " -f 2 | cut -d":" -f-2 | sort | uniq -c
1839 13:12
4737 13:13
1942 13:14
1184 13:15
836 13:16
949 13:17
1360 13:18
880 13:19
770 13:20
1127 13:21
682 13:22
18953 13:23
34813 13:24
22377 13:25
29917 13:26
25207 13:27
22117 13:28
22701 13:29
22060 13:30
24797 13:31
22575 13:32
23313 13:33
22190 13:34
23338 13:35
22061 13:36
24249 13:37
22953 13:38
24566 13:39
21788 13:40
18880 13:41
26141 13:42
24083 13:43
22552 13:44
1314 13:45
244 13:46
Performance test started at 13:23 and finished around 13:44. Correlation is quite obvious. Note also that in the peak it was generating 560 dials per second!

@xiang90 @lavalamp
I think that we have a victim for it. What we've done is that we changed the Transport in go-etcd client:
https://github.com/GoogleCloudPlatform/kubernetes/blob/master/Godeps/_workspace/src/github.com/coreos/go-etcd/etcd/client.go#L194
but setting:
MaxIdleConnsPerHost: 10000 (from default 2)
This speeded up the test by ~35%
I think that 10000 is some exaggeration, but it definitely proves that increasing this value solves the problem.
My hypothesis why it solves the problem:

we have 100 opened watches( watching for the same changes (which definitely happens in 100-node cluster) and all of them are from apiserver (a single client)
a change that is interesting is written to etcd
etcd is responding to all of them at the same time
all those connections become iddle (or most of them) before the new request is send, and thus most of them are closed (we can have only 2 of them opened for a single client)
for the next requests within a watch we need to create new connections

Number of dials after change described by @wojtek-t :+1:
~$ sudo docker logs 6c7a949241ff 2>&1 | grep FFF | tr -s " " | cut -d" " -f 2 | cut -d":" -f-2 | sort | uniq -c
335 14:29
200 14:30
5 14:31
28 14:32
65 14:33
145 14:34
69 14:35
121 14:36
59 14:37
202 14:39
140 14:40
112 14:42
77 14:43
190 14:44
104 14:45
5 14:46
4 14:47
(this includes run of performance test)

Just a silly question: are we allowed to change files under Godeps/ directory? If not what is the best way to fix it?

@wojtek-t Call https://github.com/GoogleCloudPlatform/kubernetes/blob/master/Godeps/_workspace/src/github.com/coreos/go-etcd/etcd/client.go#L178 instead.

@fgrzadkowski @wojtek-t is probably right. If you only use one transport, there is a maxIdelConn limitation.

thanks @xiang90 !
Assigning to myself - I will prepare a PR for it.

@wojtek-t cool, this is great. 10000 max idle is probably a little high-- we don't want to use all of apiserver's available FDs for this. Does, say, 500 still get most of the benefits?
(I think if we multiplexed watches that might also help a lot, but obviously it's much easier to keep more idle connections.)
(If you really had needed to modify a file in the godeps/ directory, the proper way to do that is to send a PR to the downstream repo, and the update the dependency once they accept it.)

@wojtek-t cool, this is great. 10000 max idle is probably a little high-- we don't want to use all of apiserver's available FDs for this. Does, say, 500 still get most of the benefits?
I completely agree 10000 is too much. I didn't have time to make more experiments today, but my feeling is that 500 or 1000 should also be enough. I will come up with more accurate number on Monday.

(I think if we multiplexed watches that might also help a lot, but obviously it's much easier to keep more idle connections.)
Yes - but this would be much bigger change. I don't think it's worth doing now.

(If you really had needed to modify a file in the godeps/ directory, the proper way to do that is to send a PR to the downstream repo, and the update the dependency once they accept it.)
It seems it's ot needed. We just need to initialize the client properly. I will create a PR for it.


Add a method to ShapeStream to abort long poll + reconnect + emit a new up-to-date with latest LSN

Related to #2215, we will need something like a .refresh() method in ShapeStream that can be called to abort the current long poll, reconnect with live=false, and therefor emit a new up-to=date.
There is some nuance, as this call only wants to be made during long polling - I think it's a no-op when there is no active long poll.
Further apis can wrap this to create "aligned" streams, calling the refresh method on sibling streams when they receive an update and a timeout threshold has been exceeded without an up-to-date on the other streams.

I still don't understand how this is helpful. A live request is guaranteed to get sent data as soon as it exists. A non live request has longer caching headers so a response might there might even be further behind the tip of the stream...
I think a slight buffering (which we test in the wild to collect say 99.99% of associated stream updates) after receiving a new message along with resilience against missing messages (e.g. a join fails temporarily) seems better?

@KyleAMathews I'm trying to find a way to integrate this into D2. Each stream needs to send a frontier message that gives a lower bound of the versions that it may send in future. This lower bound is then used by the reduce, concat, consolidate in various ways. A pending long poll sent a frontier at some point in the past, but I need it to send on even when there is no data when other streams have received data.

reduce emits a result of the computation at a specific version when it receives a frontear message
concat and join join two streams, when either stream emits a frontier they emits the min(newFrontier, lastEmitedFrontier), essentially the lower band of what it knows about.
consolidate buffers messages until it receives a frontier, and then consolidates the buffered messages that have a version lower than the frontier.

Whenever you use a concat or join you want to then consolidate the stream before sending it to a user or materialising it. If you haven't received a frontier on one side of the join, but messages on the other side have a higher version, they will not be emitted.
This PR in the d2ts repo (https://github.com/electric-sql/d2ts/pull/11) has an working Electric -> D2 adapter, and an example that:

has issues, users, comments shapes
outputs a stream that combines them into an issue stream with the users details, and a count of comments
However, it doesn't work because it blocks the D2 pipeline waiting for a frontier on the various inputs.

You are correct that a timeout could work in theory. However, if we simulate a frontier based on a timeout, and then receive a late message, without chaining its version (max(simulatedLsn, messageLsn), which could have strange side effects) it will throw an error, stoping the stream, as a message has been received with a lower version than that of the last frontier and cannot be processed.
If we want to offer any guarantee (as we could if we use D2, it's what it's designed for) when joining streams, we need a way to assert the lower bound of LSN/Version that a stream could receive at a point in time so that we can inject a frontier.
There is an alternative, and that is to decide not to offer these guarantees, DBSP for example does away with all the versioning stuff, it is assumed that messages are receved in order, and at the correct time. We could either build a DBSP implementation or take the D2 ts lib and strip out all version/ordering stuff. There is a route to doing that, and it makes it simpler. But the downside is we loos the ability to offer the transactional guarantee.

So what you really want is every stream to output on every transaction whether it has a change or not? Would this also solve it?

That would also work, but on a busy database that's a lot of transactions. You could easily the long polling just becoming an endless loop of reconnects.
It ends up being a higher overhead than just aborting and reconnecting from the client side.

Right sure — just conceptually that's the goal. Just making sure I understand.


weasyprint: error: unrecognized arguments: --format

The exit status code '2' says something went wrong:
stderr: "usage: weasyprint [-h] [--version] [-i] [-e ENCODING] [-s STYLESHEET]
[-m MEDIA_TYPE] [-u BASE_URL] [-a ATTACHMENT] [-p]
[-O {images,fonts,all,none}] [-v] [-d] [-q]
input output
weasyprint: error: unrecognized arguments: --format C:\Users\AEM\AppData\Local\Temp\php_weasyprint61cbe3514c1101.17556704.pdf
"
stdout: ""
command: C:\Users\AEM\AppData\Local\Packages\PythonSoftwareFoundation.Python.3.8_qbz5n2kfra8p0\LocalCache\local-packages\Python38\Scripts\weasyprint.exe --format pdf "http://www.github.com" "C:\Users\AEM\AppData\Local\Temp\php_weasyprint61cbe3514c1101.17556704.pdf".
if i run in command line , i get same error
when i run this command is ok
weasyprint  https://example.com weasyprint-website.pdf

Hi @khonyuen,
which version of weasyprint are you running? can you report the output of weasyprint --info? --format was deprecated in version 53 and will be removed in a future release.

Ok, I missed the new 54.0b1 beta release of WeasyPrint, where --format is indeed removed.
As a quick workaround you can unset the format option:
$weasyprint = new \Pontedilana\PhpWeasyPrint\Pdf('/usr/local/bin/weasyprint');
$weasyprint->setOption('format', null);

I'll release a new version of php-weasyprint to accommodate this change in upstream.

I've released version 0.10.0 (and a tests fix release 0.10.1) that implements support for WeasyPrint 54
https://github.com/pontedilana/php-weasyprint/releases/tag/0.10.1


Fixing service ka-lite status command

Summary
thanks @jamalex!
TODO

[x] Updated installer's local changelog
[x] Verified test builds

@jamalex - should work fine both for systemd and sysVinit


Ui pointer enter exit forwarder

new Unit()  should be F.unit
Why is input button hardcoded?
Formatting: group fields logically with spacing.
On Nov 17, 2016 16:04, "astro75"<EMAIL_ADDRESS>wrote:

Merged #31 https://github.com/tinylabproductions/tlplib/pull/31.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/tinylabproductions/tlplib/pull/31#event-862835786,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAAygyxHDRixRSe-lM15-swFpCVwahGDks5q_F79gaJpZM4K1VyX
.


Implement custom renderers property

After reading the https://echarts.apache.org/en/api.html#echarts documentation, I found an option to change the renderer of the widget, either 'canvas' or 'svg', which can be very useful.
This feature doesn't seem too complicated to implement, just a couple of lines of code, however, the library now has two types of widgets, meaning that any new feature has to be added to the both of them, what do you think about adding a BaseWidgetView and a BaseWidgetModel? it would be easier to implement these methods... if you want I could draft a PR and/or follow your indications? if you see it as something feasible?

what do you think about adding a BaseWidgetView and a BaseWidgetModel? it would be easier to implement these methods...

I agree, this should be the way to go! And we should allow passing all options in the  echarts.init call from the Python side.

Fixed by #16


use centerpoint to process my customized dataset

how could I use centerpoint to process my customized dataset? where should i modify the code?
thx!

Hi :) have you figured this out? Please let me know. Thank you in advance!

请问有办法解决吗?下载完整的数据集太大了


(BKR-322) --fail-mode fast doesn't seem to be failing fast

was using the default value instead of the setting value

Looks good to me! :tada:

Refer to this link for build results (access rights to CI server needed):
http://jenkins-beaker.delivery.puppetlabs.net//job/qe_beaker_btc-intn/953/
Test PASSed.

@rick I think that we should revisit when it is appropriate to provide an accessor to class variables, for now these new spec tests behave the same way as the rest of the tests written for this object.

Refer to this link for build results (access rights to CI server needed):
http://jenkins-beaker.delivery.puppetlabs.net//job/qe_beaker_btc-intn/954/
Test FAILed.

retest this please

Refer to this link for build results (access rights to CI server needed):
http://jenkins-beaker.delivery.puppetlabs.net//job/qe_beaker_btc-intn/974/
Test FAILed.

retest this please

Refer to this link for build results (access rights to CI server needed):
http://jenkins-beaker.delivery.puppetlabs.net//job/qe_beaker_btc-intn/976/
Test FAILed.

Failure unrelated to patch.

@kevpl This should be ready to merge.


undefined method `copy' on 2.0.0

Hello,
I use your code with a vagrant dev environment: https://github.com/ProxiBlue/vagrant_m2_vuestorefront
As of v 2.0.0, connection to docker instances fail with error: undefined method `copy' for #<Docker::Container:0x00000000034c0b50> (NoMethodError)
stack trace:
~/vagrant$ vagrant up redis
========================================================
domain : hussja.test
folder : /home/dedmeet/vagrant
mysql root password : root
persistent storage: /home/dedmeet/vagrant/persistent_storage
========================================================
Bringing machine 'redis' up with 'docker' provider...
==> redis: [vagrant-hostmanager:guests] Updating hosts file on active guest virtual machines...
Traceback (most recent call last):
	63: from /opt/vagrant/embedded/gems/2.2.10/gems/vagrant-2.2.10/lib/vagrant/batch_action.rb:86:in `block (2 levels) in run'
	62: from /opt/vagrant/embedded/gems/2.2.10/gems/vagrant-2.2.10/lib/vagrant/machine.rb:201:in `action'
	61: from /opt/vagrant/embedded/gems/2.2.10/gems/vagrant-2.2.10/lib/vagrant/machine.rb:201:in `call'
	60: from /opt/vagrant/embedded/gems/2.2.10/gems/vagrant-2.2.10/lib/vagrant/environment.rb:613:in `lock'
	59: from /opt/vagrant/embedded/gems/2.2.10/gems/vagrant-2.2.10/lib/vagrant/machine.rb:215:in `block in action'
	58: from /opt/vagrant/embedded/gems/2.2.10/gems/vagrant-2.2.10/lib/vagrant/machine.rb:243:in `action_raw'
	57: from /opt/vagrant/embedded/gems/2.2.10/gems/vagrant-2.2.10/lib/vagrant/action/runner.rb:89:in `run'
	56: from /opt/vagrant/embedded/gems/2.2.10/gems/vagrant-2.2.10/lib/vagrant/util/busy.rb:19:in `busy'
	55: from /opt/vagrant/embedded/gems/2.2.10/gems/vagrant-2.2.10/lib/vagrant/action/runner.rb:89:in `block in run'
	54: from /opt/vagrant/embedded/gems/2.2.10/gems/vagrant-2.2.10/lib/vagrant/action/builder.rb:149:in `call'
	53: from /opt/vagrant/embedded/gems/2.2.10/gems/vagrant-2.2.10/lib/vagrant/action/warden.rb:48:in `call'
	52: from /opt/vagrant/embedded/gems/2.2.10/gems/vagrant-2.2.10/lib/vagrant/action/builtin/delayed.rb:19:in `call'
	51: from /opt/vagrant/embedded/gems/2.2.10/gems/vagrant-2.2.10/lib/vagrant/action/warden.rb:48:in `call'
	50: from /opt/vagrant/embedded/gems/2.2.10/gems/vagrant-2.2.10/lib/vagrant/action/builtin/call.rb:53:in `call'
	49: from /opt/vagrant/embedded/gems/2.2.10/gems/vagrant-2.2.10/lib/vagrant/action/runner.rb:89:in `run'
	48: from /opt/vagrant/embedded/gems/2.2.10/gems/vagrant-2.2.10/lib/vagrant/util/busy.rb:19:in `busy'
	47: from /opt/vagrant/embedded/gems/2.2.10/gems/vagrant-2.2.10/lib/vagrant/action/runner.rb:89:in `block in run'
	46: from /opt/vagrant/embedded/gems/2.2.10/gems/vagrant-2.2.10/lib/vagrant/action/builder.rb:149:in `call'
	45: from /opt/vagrant/embedded/gems/2.2.10/gems/vagrant-2.2.10/lib/vagrant/action/warden.rb:48:in `call'
	44: from /opt/vagrant/embedded/gems/2.2.10/gems/vagrant-2.2.10/lib/vagrant/action/warden.rb:127:in `block in finalize_action'
	43: from /opt/vagrant/embedded/gems/2.2.10/gems/vagrant-2.2.10/lib/vagrant/action/warden.rb:48:in `call'
	42: from /opt/vagrant/embedded/gems/2.2.10/gems/vagrant-2.2.10/lib/vagrant/action/warden.rb:127:in `block in finalize_action'
	41: from /opt/vagrant/embedded/gems/2.2.10/gems/vagrant-2.2.10/lib/vagrant/action/warden.rb:48:in `call'
	40: from /opt/vagrant/embedded/gems/2.2.10/gems/vagrant-2.2.10/lib/vagrant/action/builtin/config_validate.rb:25:in `call'
	39: from /opt/vagrant/embedded/gems/2.2.10/gems/vagrant-2.2.10/lib/vagrant/action/warden.rb:48:in `call'
	38: from /opt/vagrant/embedded/gems/2.2.10/gems/vagrant-2.2.10/plugins/providers/docker/action/host_machine.rb:18:in `call'
	37: from /opt/vagrant/embedded/gems/2.2.10/gems/vagrant-2.2.10/lib/vagrant/action/warden.rb:48:in `call'
	36: from /opt/vagrant/embedded/gems/2.2.10/gems/vagrant-2.2.10/lib/vagrant/action/builtin/call.rb:53:in `call'
	35: from /opt/vagrant/embedded/gems/2.2.10/gems/vagrant-2.2.10/lib/vagrant/action/runner.rb:89:in `run'
	34: from /opt/vagrant/embedded/gems/2.2.10/gems/vagrant-2.2.10/lib/vagrant/util/busy.rb:19:in `busy'
	33: from /opt/vagrant/embedded/gems/2.2.10/gems/vagrant-2.2.10/lib/vagrant/action/runner.rb:89:in `block in run'
	32: from /opt/vagrant/embedded/gems/2.2.10/gems/vagrant-2.2.10/lib/vagrant/action/builder.rb:149:in `call'
	31: from /opt/vagrant/embedded/gems/2.2.10/gems/vagrant-2.2.10/lib/vagrant/action/warden.rb:48:in `call'
	30: from /opt/vagrant/embedded/gems/2.2.10/gems/vagrant-2.2.10/lib/vagrant/action/warden.rb:127:in `block in finalize_action'
	29: from /opt/vagrant/embedded/gems/2.2.10/gems/vagrant-2.2.10/lib/vagrant/action/warden.rb:48:in `call'
	28: from /opt/vagrant/embedded/gems/2.2.10/gems/vagrant-2.2.10/lib/vagrant/action/warden.rb:127:in `block in finalize_action'
	27: from /opt/vagrant/embedded/gems/2.2.10/gems/vagrant-2.2.10/lib/vagrant/action/warden.rb:48:in `call'
	26: from /opt/vagrant/embedded/gems/2.2.10/gems/vagrant-2.2.10/lib/vagrant/action/builtin/call.rb:53:in `call'
	25: from /opt/vagrant/embedded/gems/2.2.10/gems/vagrant-2.2.10/lib/vagrant/action/runner.rb:89:in `run'
	24: from /opt/vagrant/embedded/gems/2.2.10/gems/vagrant-2.2.10/lib/vagrant/util/busy.rb:19:in `busy'
	23: from /opt/vagrant/embedded/gems/2.2.10/gems/vagrant-2.2.10/lib/vagrant/action/runner.rb:89:in `block in run'
	22: from /opt/vagrant/embedded/gems/2.2.10/gems/vagrant-2.2.10/lib/vagrant/action/builder.rb:149:in `call'
	21: from /opt/vagrant/embedded/gems/2.2.10/gems/vagrant-2.2.10/lib/vagrant/action/warden.rb:48:in `call'
	20: from /opt/vagrant/embedded/gems/2.2.10/gems/vagrant-2.2.10/lib/vagrant/action/warden.rb:127:in `block in finalize_action'
	19: from /opt/vagrant/embedded/gems/2.2.10/gems/vagrant-2.2.10/lib/vagrant/action/warden.rb:48:in `call'
	18: from /opt/vagrant/embedded/gems/2.2.10/gems/vagrant-2.2.10/lib/vagrant/action/builtin/call.rb:53:in `call'
	17: from /opt/vagrant/embedded/gems/2.2.10/gems/vagrant-2.2.10/lib/vagrant/action/runner.rb:89:in `run'
	16: from /opt/vagrant/embedded/gems/2.2.10/gems/vagrant-2.2.10/lib/vagrant/util/busy.rb:19:in `busy'
	15: from /opt/vagrant/embedded/gems/2.2.10/gems/vagrant-2.2.10/lib/vagrant/action/runner.rb:89:in `block in run'
	14: from /opt/vagrant/embedded/gems/2.2.10/gems/vagrant-2.2.10/lib/vagrant/action/builder.rb:149:in `call'
	13: from /opt/vagrant/embedded/gems/2.2.10/gems/vagrant-2.2.10/lib/vagrant/action/warden.rb:48:in `call'
	12: from /opt/vagrant/embedded/gems/2.2.10/gems/vagrant-2.2.10/lib/vagrant/action/warden.rb:127:in `block in finalize_action'
	11: from /opt/vagrant/embedded/gems/2.2.10/gems/vagrant-2.2.10/lib/vagrant/action/warden.rb:48:in `call'
	10: from /opt/vagrant/embedded/gems/2.2.10/gems/vagrant-2.2.10/lib/vagrant/action/builtin/provision.rb:80:in `call'
	 9: from /opt/vagrant/embedded/gems/2.2.10/gems/vagrant-2.2.10/lib/vagrant/action/warden.rb:48:in `call'
	 8: from /opt/vagrant/embedded/gems/2.2.10/gems/vagrant-2.2.10/lib/vagrant/action/builtin/config_validate.rb:25:in `call'
	 7: from /opt/vagrant/embedded/gems/2.2.10/gems/vagrant-2.2.10/lib/vagrant/action/warden.rb:48:in `call'
	 6: from /home/dedmeet/.vagrant.d/gems/2.6.6/gems/vagrant-hostmanager-1.8.9/lib/vagrant-hostmanager/action/update_all.rb:32:in `call'
	 5: from /home/dedmeet/.vagrant.d/gems/2.6.6/gems/vagrant-hostmanager-1.8.9/lib/vagrant-hostmanager/action/update_all.rb:32:in `each'
	 4: from /home/dedmeet/.vagrant.d/gems/2.6.6/gems/vagrant-hostmanager-1.8.9/lib/vagrant-hostmanager/action/update_all.rb:37:in `block in call'
	 3: from /home/dedmeet/.vagrant.d/gems/2.6.6/gems/vagrant-hostmanager-1.8.9/lib/vagrant-hostmanager/hosts_file/updater.rb:37:in `update_guest'
	 2: from /home/dedmeet/.vagrant.d/gems/2.6.6/gems/communicator-docker-1.0.5/lib/communicator-docker/communicator-docker.rb:72:in `download'
	 1: from /home/dedmeet/.vagrant.d/gems/2.6.6/gems/communicator-docker-1.0.5/lib/communicator-docker/communicator-docker.rb:72:in `open'
/home/dedmeet/.vagrant.d/gems/2.6.6/gems/communicator-docker-1.0.5/lib/communicator-docker/communicator-docker.rb:73:in `block in download': undefined method `copy' for #<Docker::Container:0x00000000034c0b50> (NoMethodError)

~/vagrant$ vagrant plugin list
communicator-docker (1.0.5, global)
  - Version Constraint: 1.0.5
docker-api (2.0.0, global)
vagrant-hostmanager (1.8.9, global)

downgrading to 1.34.2 resolves issue
vagrant plugin list
communicator-docker (1.0.5, global)
  - Version Constraint: 1.0.5
docker-api (1.34.2, global)
vagrant-hostmanager (1.8.9, global)

Further info: The fail starts here:
https://github.com/ProxiBlue/vagrant-communicator-docker/blob/master/lib/communicator-docker/communicator-docker.rb#L73
(a docker communicator plugin for vagrant I wrote as a requirement to the dev env)

See Remove old copy method, replaced by archive_out : https://github.com/swipely/docker-api/commit/425036dd85e41f8d4e6ea95ee6d001d76af9c7d7

Thanks, should have gone look, but was to lazy. Bad me!


A pop up new vscode window for jupyter notebook variable such as dataframe df, just like RStudio did.

Duplicate of https://github.com/microsoft/vscode-jupyter/issues/1148


chore: release main

:robot: I have created a release beep boop
dev-dependencies-client: 4.1.21
4.1.21 (2024-04-20)
Bug Fixes

bump client and server non-breaking dependencies (#286) (9cf91b2)

dev-dependencies-server: 4.0.4
4.0.4 (2024-04-20)
Bug Fixes

bump client and server non-breaking dependencies (#286) (9cf91b2)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/aversini/dev-dependencies/releases/tag/dev-dependencies-client-v4.1.21 :sunflower:

:robot: Release is at https://github.com/aversini/dev-dependencies/releases/tag/dev-dependencies-server-v4.0.4 :sunflower:


How to access the DOM from javascript?

Hi,
I try to use the following code to access a DOM object inside the HTML:
var config = Configuration.Default.WithJavaScript().WithCss();
var parser = new HtmlParser(config);
// sample html
var source = @"<!doctype html>
content
";
var document = parser.Parse(source);
var jsService = config.Services.OfType<JavaScriptProvider>().FirstOrDefault(x => x.Engine.Type == "text/javascript");
var jintEngine = jsService.Engine.GetOrCreateJint(document);
// trying to modify the context, but I don't know how to specify the correct thisBinding
jintEngine.EnterExecutionContext(jintEngine.GlobalEnvironment, jintEngine.GlobalEnvironment, ???);

// try to extract the contents of the div with JS
var result = jintEngine.Execute("document.querySelectorAll('#test').innerHTML").GetCompletionValue();

jintEngine.LeaveExecutionContext();
Console.WriteLine(result);

Some remarks:

I'm not allowed to modify the html content in the 'source' variable
I'm not sure if modifying the execution context is the correct way

The problem:
When I run this code (without modifying the execution environment) I get a JavascriptException saying that the 'document' is undefined. I've tried to modify the execution environment, but I have no idea what the correct value for the thisBinding parameter is in the EnterExecutionContext function. How can I set it to the window or the document?

I think a little bit too much is done here. Is there a specific reason for modifying the context? Why don't you want to run from the IWindow context?
See: https://github.com/AngleSharp/AngleSharp.Samples/blob/master/AngleSharp.Samples.App/ViewModels/ReplViewModel.cs for another example how to run JS against the DOM (here in a REPL).
If you really need this, then just do it like the scripting library does it:
_engine.EnterExecutionContext(Lexicals, Variables, _window);
_engine.Execute(source);
_engine.LeaveExecutionContext();

_window can be used via document.DefaultView. Hope this helps!

Hello,
What do you mean by running from the IWindow context? (sorry I'm new to the library)
I've checked the AngleSharp.Samples project, opened a web page and started playing with the REPL in the 'Console' tab. The 'window' and 'document' objects are undefined there also.
Regarding the execution context switch: the type of the 3rd parameter in the EnterExecutionContext function is JsValue. The document.DefaultView property has a type of IWindow, so when I used it I get a compiler error (cannot convert from IWindow to JsValue), and I don't know how to convert that IWindow instance to a proper JsValue.

I don't know why this is not working in the samples project (maybe as I've seen from your Fiddle you using the wrong combination - both, AngleSharp and AngleSharp.Scripting.JavaScript should be taken with their latest versions; here you just used AngleSharp.Scripting.JavaScript with implicitly used an older version of AngleSharp).
Either way I think there is some connection to #19. I've added an extension method and the unit tests pass.
Essentially, it allows you to do:
var config = Configuration.Default.WithJavaScript().WithCss();
var parser = new HtmlParser(config);
// sample html
var source = @"<!doctype html>
content
";
var document = parser.Parse(source);
var result = document.ExecuteScript("document.querySelectorAll('#test').innerHTML");
Console.WriteLine(result);

All the rest from above is not required.

It works perfectly, many thanks :).
There is just a small typo in the document.ExecuteScript line: the js expression should be document.querySelectorAll('#test')[0].innerHTML

Yes, edited. I just copied the one from above (your initial post) to illustrate the idea / savings in LOC.


operator tf-operator (2011.L2.372)

This operator helps bring-up Juniper Contrail SDN networking for Redhat Openshift.

Fixing and opening new PR


Core/azurerm_subnet: Make "private_endpoint_network_policies_enabled" configurable

Hi,
Do you see any problems with making "private_endpoint_network_policies_enabled" configurable as an optional variable in the Core module?
https://registry.terraform.io/providers/hashicorp/azurerm/latest/docs/resources/subnet#private_endpoint_network_policies_enabled
https://learn.microsoft.com/en-us/azure/private-link/disable-private-endpoint-network-policy?tabs=network-policy-portal
Please let me know if you have any questions.
Thanks in advance!

Go nuts @linus-lysell , feel free to create a PR.


flex not done well

Does not translate flex to -webkit-flex on Chrome browser

Yes, prefixfree doesn’t change existing prefixes. That would be odd.


Provide ByteBuddy plugin for Axon Framework

In a typical Axon Framework project I want to use the jmolecules annotations instead of Axon annotation.
Acceptance Criteria
Get rid of the following annotations:

Command / Command Model: @TargetAggregateIdentifier, @AggregateIdentifier, @Aggregate, @AggregateRoot, @EventSouringHandler
Event Handler: @EventHandler

Currently out of scope

Query Model: @Query, @QueryHandler, because currently not supported by jmolecules (no annotations yet, see https://github.com/xmolecules/jmolecules/issues/87)

Event: @Revision (not support inside of @DomainEvent see https://github.com/xmolecules/jmolecules/issues/84)

I have just pushed your commit and some polishing on top to the feature/121-axon branch. It uses the slightly reworked @Association annotation already merged into the jMolecules API library. Please have a final quick glance before I merge it into main. I've pulled out the example into the jmolecules-examples repository (all here locally, builds fine this feature branch work here included and about to be merged as well in case we think we're done here for now).
Sorry for the hassle, I'll have to review the code formatting settings going forward.

Looks good! Thank you for taking time and finishing it.
Sorry I could not help you with formatting, but somehow the formatter application changes the source code from develop...

For the examples - great. As soon the integration is merged, I can also provide the Axon example in Kotlin, since this is in my opinion a much better match for creation of DDD CARS/ES systems using Axon Framework than Java.

That's in place now. Happy to see the Kotlin based Axon example. Thanks again!


console crashes with symengine v0.4.1

Problem:
if I install python-symengine v0.4.0 together with symengine v0.4.1 (as is done automatically if you do conda install -c conda-forge python-symengine) the python-console crashes everytime i run a code that involves symengine without any warning whatsoever.
after downgrading to symengine v0.4.0 everything works as expected again.
is it possible that the python-symengine bindings need an update to work with symengine v0.4.1 ?

maybe I need to add here that I'm on a windows machine...
(it seems that things are working fine on linux)

@raphaelquast I think the versions are tied. Try the python-symengine 0.4.1 and see if it fixes things.
If that's the case, we should change the Conda package to enforce this. /cc @isuruf

There's no python-symengine 0.4.1. I thought symengine versions 0.4.0 and 0.4.1 will be ABI compatible, but they are not. (Looks like we are running into the windows issue mentioned in https://community.kde.org/Policies/Binary_Compatibility_Issues_With_C%2B%2B). I've removed 0.4.1 from conda-forge.


[Autocomplete] extend renderOption prop type to allow key and ref

[x] I have followed (at least) the PR section of the contributing guide.

I would like to be able to override the key property for renderOption. Like so
renderOption={(props, option, state) => renderOption({ ...props, key: option[optionValueField] }, option, state)}

Unfortunatyle this throws the following error
Object literal may only specify known properties, and 'key' does not exist in type 'HTMLAttributes<HTMLLIElement>'.

This merge request fails because React.DetailedHTMLProps still uses LegacyRef which enables the ref to be a string.
OverridableComponent no longer supports LegacyRef, only the new Ref type, Thats why the following error occurs
Type 'LegacyRef<HTMLLIElement> | undefined' is not assignable to type 'Ref<unknown> | undefined'.
          Type 'string' is not assignable to type 'Ref<unknown> | undefined'.

I would appreciate some help on this matter.

👋 The migration PR has been merged.
Please follow these steps to make sure that the contents are all updated. (Sorry for the inconvenience)

pull latest master from upstream to your branch
if your PR has changes on the *.md or demo files, you are likely to encounter conflict because all of them have been moved to the new folder.
2.1 revert the change on those markdown files you did
2.2 pull latest master from upstream (you should not see conflict)
2.3 make the changes again at docs/data/material/*
run yarn docs:api

you might see the changes in docs/pages/material/api/* if your PR touches some of the components
it is okay if there is no changes

If you are struggle with the steps above, feel free to tag @siriwatknp

@PascalLuginbuehl please open an issue and we can take a look and provide fix there. Looks like the renderOption you are talking about is defined in your codebase. When creating an issue make sure to share codesandbox with the whole code, so that it's clear what's the problem.


minimum version of ruby supported making Github Action rubocop crash + version missing on rubygems

On my computer bundle exec rubocop gives no offenses or error (ruby 2.7).
But on the CI (Github Action, image ruby 2.6) I get an error because ruby 2.1 is not supported by rubocop.
Rubocop detects ruby 2.1 in TargetRubyVersion of Rainbow rubocop file. It seems to be because I use the paint gems that requires rainbow 3.0.0 which is the last version available on rubygems.
Seems you know requires ruby 2.3 in git tag 3.1.0 but it will still crash since rubocops says:

Supported versions: 2.4, 2.5, 2.6, 2.7, 3.0

So could you requires at least ruby 2.4 in the rubocop file (and gemspec for no mismatch or disable the cop that check that), I don't really understand why rubocops on the CI is running on all the sub-dependencies instead of just my code, my best guess is that I requires paint here that itself requires rainbow.
So please:

Release 3.1.0 on rubygems
Make a new 3.2.0 with ruby 2.4 as min version and release it on rubygems

Duplicates #95.
Thanks for reporting!

@olleolleolle Not dupe. #95 is an issue from 2019 when there was only rainbow 3.0.0 that asked to create a new version 3.1.0 with ruby 2.3 as min. In the meantime (august 2020) rainbow 3.1.0 was released (git tag). My issue #106 is asking 2 things:

Release 3.1.0 on rubygems
Make a new 3.2.0 with ruby 2.4 as min version and release it on rubygems

which is different from creating a 3.1.0 release (which is already done) so you could close #95 and re-open this one.

The problem of access remains the same, though. As soon as that's cleared up, releases can be cut etc.

Please Github CI of thousands of tools are failing because of rainbow 3.0.0 min ruby requirements.

I'll try this workaround https://github.com/rubocop/rubocop/issues/6398#issuecomment-431901995 in the meantime


Doesn't seem to work with mnowotnik/fzshell

I tried this mnowotnik/fzshell plugin, which only mentions support for zplug.
I added it to zsh_plugins.txt as mnowotnik/fzshell.
I'm not sure how to use it, but when I type docker rmi and then type ctrl-n I get this error:
fzshell_widget:3: no such file or directory: /home/jason/.cache/antidote/https-COLON--SLASH--SLASH-github.com-SLASH-mnowotnik-SLASH-fzshell/fzshell

Yes - tracking it here: https://github.com/mattmc3/antidote/issues/12


Please add this package to conda forge

Thank you all for this package. I find it very useful for linting code in jupyter notebooks via jupyterlab-lsp.
As a conda user, I would find it useful if the package was available to install with conda, not just pip.
Thanks again!

Python-lsp-ruff is now available via conda-forge, closed with https://github.com/conda-forge/staged-recipes/pull/22139