Work with @carbon/react team to determine shared codemods approach

Following up on earlier conversations on codemods. Think this would be a good opportunity for cross-pollination.

[x] Work with @carbon/react team to determine developer experience of codemods in a single package
[x] Work with @carbon/react team to investigate how ibm-products codemods appear in @carbon/upgrade
[x] Continue refinement of #6126

@elycheea Housing them in @carbon/upgrade in the monorepo makes sense to me 👍 I don't see a benefit of duplicating all the required infrastructure into this repo when you're going to have to manually author before/after test fixtures anyway.
To differentiate them we could start with a naming convention for the codemod(s): ibm-products-*
If/when the time comes we could do an onboarding/kickoff with y'all, myself, @2nikhiltom and @riddhybansal 🥳

We had a discussion with the core carbon team about codemod implmentation for ibm-products and has also refined the epic issue for codemods.
We'll be starting with codemod scripts mentioned in the epic.


Update active-directory-b2c-ui-customization-custom.md

Must DataUri be included, in order to avoid the error "The required "DataUri element is missing from ContentDefinition"? Should we comment that we can also add RecoveryUri and Metadata, and that this last one makes necessary to add the Item DisplayName?

@marcelodiiorio : Thanks for your contribution to the Azure documentation! The author, @saeedakhter-msft, has been notified to review your proposed change.

@SaeedAkhter-MSFT Please review this change. If approved, enter "#sign-off" in the comments to get it merged and published.

@mtillman: I'm sorry - only the author of this article, @saeedakhter-msft, can sign off on your changes. But we do have an exception process - if you are on the Microsoft content or product team for this product area, you can ask the PR review team to review and merge it by sending mail to the techdocprs alias.

@SaeedAkhter-MSFT bumping this to get your review of the proposed changes.

#sign-off

@davidmu1: I'm sorry - only the author of this article, @saeedakhter-msft, can sign off on your changes. But we do have an exception process - if you are on the Microsoft content or product team for this product area, you can ask the PR review team to review and merge it by sending mail to the techdocprs alias.


Reinstating original Skin functionality

In the process of renaming the "skin" functionality to "defaultApp" we have lost what I actually meant as the skin.    I am happy to call it something else than "skin"  -- maybe "fallbackApp" or something

Instead of redirecting the client to a remote viewer app, which messed up the URI bar, the app is returned directly as a text/html  file.   The file's origin is then the same as the data.

The very small HTML file is stored locally just like an error file.  A default version can be kept in the code.

It is invoked whenever the content negotiation perceives that the client is a browser capable running a web app, but is not capable of handling the data of the requested resource.    It is invoked if the browsers ability to handle HTML times 0.7 (say)   is greater than its q ability to handle the data itself.   Ask me if you do not understand content negotiation.

How about  --fallback media/html/tabulatorSkin.html  for the command line app?    It would be an alternative to --defaultApp

An example skin file is in https://github.com/linkeddata/tabulator/blob/master/js/mashup/skin.html
I'm using it for my webid at the moment
https://www.w3.org/People/Berners-Lee/card#i

Implemented in https://github.com/linkeddata/ldnode/commit/1a706d4181fd67bee676d03e8ab9040112ad65e5


Makes SSR's match space agnostic

issue #3186 step 2

Yeah, let's close this in favor of https://github.com/rust-analyzer/rust-analyzer/pull/3285
Sorry for not dealing with #3285 sooner: if I had reviewed it faster, that wold have saved some work :(
@mikhail-m1 @adamrk if you both want to drive ssr to completion, it might make sense to coordinate on zulip :)

Good point. Sent you a chat on zulip @mikhail-m1.


ReplaceTokens toLowerCase error

Hello I have a problem with Replace Tokens Task on Mac Build Agent...
The build in vsts raise error when replacing tokens...
Unhandled: Cannot read property 'toLowerCase' of undefined
Can you help me pls??

hi @jerry2007
Can you please paste the full log for the task?

sou obrigado a falar


Difficult to see with some desktop themes

apx is almost invisible when using the default theme on GNOME 3.

Reproducible for me, also in LXQt with dark theme.
Possible solution: Maybe enforce a dark background in Gtk independent from the active theme setting.

oh boy, how did that happen! :)

thanks @rapgro!


⚠ Bofrost.de has degraded performance

In 2f39a99, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 953 ms

Resolved: Bofrost.de performance has improved in 9cb57ba.


Cloning a LES should let you choose a new name

Now, the same name is used which is confusing.

Since this is almost identical to the "Save a new Local Energy Solution" button on the edit page, I think upon completing this request we should also make the "Clone" button visible on private LESes (currently it shows only on those which are public).

I was a bit to quick with that one.

we should also make the "Clone" button visible on private LESes

Hmm.. should we? I don't have a really strong opinion about this matter but maybe people who work at Alliander do? What insights do you have @ChaelKruip

Hmm.. should we?

Yes, I think so. Only the owners (and admin's) can use this button for private LESses so it is a very logical way to go IMO.
@dennisschoenmakers @MarjoleinSchwachofer do you have an opinion?

It isn't directly clear to me what the difference is, so I would have to look into this.
@ThomBuijs @JeroenvdLogt: do you already have an opinion on this?

If I clone  my own LES, cloning works and works the same as save as, only do not have to go to click edit, go to the general page en find this button (which needs a lot of more steps and is not directly visible). Is this correct?
I tried to clone a public LES from someone else, but nothing happened. This would be a handy function  and than it would be logical to give it another name so that it can be clear which was the orginal from the other person and which one is you new LES.

cloning works and works the same as save as, only do not have to go to click edit, go to the general page en find this button (which needs a lot of more steps and is not directly visible). Is this correct?

Yes. This is correct.

I tried to clone a public LES from someone else, but nothing happened

Could you be more specific? Nothing as in, the Clone button didn't work, the 'Save' button didn't bring you to the page of the cloned LES?

Then the button didn't work. However I tried it again today and now it worked.

Can we close this @grdw?

I think we can 👍


Key press event listeners should work with ActionList

Describe the bug
Key press event listeners for interacting with action list are not invoked when an element is in focus. This issue was first posted in the primer-react channel (link), opening an issue here for better tracking and visibility.
To Reproduce
Steps to reproduce the behavior with the current ActionList component:

Check out onto commit ff7e364 in the memex repo and run npm start
Click on the '+' icon in the omnibar at the bottom of the page
Select 'Add item from repository' to open the side panel
Try navigating the list with arrow keys as well as j/k
Tab once
Press j/k/arrow up/arrow down will have no effect
Click somewhere to blur the focused element
Press j/k/arrow up/arrow down navigates the list

Steps to reproduce the behavior with the new ActionList component:

Check out onto commit e7e437b6d8 in the memex repo
Run npm install @primer/react@[local-version] (the most recent local version as of now is 0.0.0-202252993854) and then npm start
Click on the '+' icon in the omnibar at the bottom of the page
Select 'Add item from repository' to open the side panel
Press j to start navigating the list (the indexing is not completely correct because we only added the single-key shortcuts here for making debugging this issue easier)
Press j/k again will have no effect
Click outside the list to blur the focused list item
Press j again navigates to the next item in the list

Expected behavior
Key press event listeners inside an ActionList should be invoked even if an element is in focus.
Desktop (please complete the following information):

OS: macOS Monterey 12.4
Browser: Chrome (103.0.5060.53), Safari(15.5), Firefox (102.0.1)

Additional context
Other keyboard shortcuts that are affected are x for selecting/unselecting the checkbox and cmd+Enter for submitting.
Following the recent updates on PR https://github.com/primer/react/pull/2152, we decided to revert our work (https://github.com/github/memex/pull/10707) to make use of the current ActionList component without adding any custom keyboard shortcuts, and therefore only commits are provided for debugging. However we thought opening an issue for this event listener problem might be helpful for future work.
cc @siddharthkp

Not stale

not stale


WORDLE.IOS.APP-DEMO

https://github.com/user-attachments/assets/9a12a41a-1f59-4eaa-90d8-3a30d3fa9d7d

https://github.com/user-attachments/assets/9a12a41a-1f59-4eaa-90d8-3a30d3fa9d7d


Adding userassigned identities for the compute

Latest improvements:
MSFT employees can try out our new experience at OpenAPI Hub  - one location for using our validation tools and finding your workflow.

Contribution checklist:

[y ] I have reviewed the documentation for the workflow.
[ y] Validation tools were run on swagger spec(s) and have all been fixed in this PR.
[ y] The OpenAPI Hub was used for checking validation status and next steps.

ARM API Review Checklist

[ ] Service team MUST add the "WaitForARMFeedback" label if the management plane API changes fall into one of the below categories.
adding/removing APIs.
adding/removing properties.
adding/removing API-version.
adding a new service in Azure.

Failure to comply may result in delays for manifest application. Note this does not apply to data plane APIs.

[ ] If you are blocked on ARM review and want to get the PR merged urgently, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.
Please follow the link to find more details on API review process.

/azp run automation - sdk

Can one of the admins verify this patch?

/azp run automation - sdk

/azp run automation - sdk

/azp run automation - sdk

/azp run automation - sdk

"version": "2020-02-02"

you already have a newer api-version in 2020-03-01.  Why introduce an older api-version?  That api-version will need these changes as well, if it has already been published you'd need to create a new api-version > 2020-03-01

Refers to: specification/machinelearningservices/resource-manager/Microsoft.MachineLearningServices/stable/2020-02-02/machineLearningServices.json:6 in e2f8ef1. [](commit_id = e2f8ef1e85939ce1bbcea1358e2108c98f552ef4, deletion_comment = False)

@pilor The newer api-version was published by mistake before making manifest changes. The newer version is not live yet. We will modify the latest version to base upon "2020-02-02" once it is ready to go live.

@pilor The newer api-version was published by mistake before making manifest changes. The newer version is not live yet. We will modify the latest version to base upon "2020-02-02" once it is ready to go live.

That should be done in this PR.  You shouldn't check in an older api-version with the newer one not supporting the features that the older one is adding.  From an API standpoint everything is fine but you need to clean up your swagger specs.

Hi @shail2208 please let me know when this is ready to merge.

Hi @shail2208 any updates? It has been quite a long time...


Make sure the implementations of sweep gradients adhere to the spec

In particular, extend modes seem to behave differently, in the spec, for sweep gradient than for linear and radial ones.
For example, normalizing the colorLine seems unwated for sweeps, but more processing of the color linee be required, for simulating repeat, pad, mirror.
Solutions will be different for Skia on one hand, and the other backends on the other hand.

Also: the Skia backend doesn't currently implement the sweep extend mode correctly: the extend mode should not extend before the start angle and after end angle (???).

First of all, big thanks @justvanrossum for the report on Chromium/Skia using the incorrect start axis (vertical up instead of horizontal right). I filed the following issues after further investigation: https://bugs.chromium.org/p/skia/issues/detail?id=13208, https://bugs.chromium.org/p/skia/issues/detail?id=13209, https://bugs.chromium.org/p/skia/issues/detail?id=13210. So the start angle was wrong, repeat modes didn't work, the sector was cut, and sectors crossing 0 did not work.
To fix this, I increased test coverage and improved the Skia implementation.
In the following I try to break down some observations of what I am seeing in BlackRenderer to hopefully get to a common understanding and help with debugging issues in BlackRenderer for sweeps.
New Test Glyphs
https://github.com/googlefonts/color-fonts/pull/98 contains additional test glyphs for sweep (now merged to main)
Skia Fix and Results
My fix CL for Skia is in:
https://skia-review.googlesource.com/c/skia/+/529460
With that I get the following, in our opinion correct results (rows are extend modes pad, reflect, repeat respectively). Please do comment if you think some interpretations/renderings are still wrong as that may well be possible.

BlackRenderer results
Extend mode pad:
$ blackrenderer ~/dev/skia/resources/fonts/more_samples-glyf_colr_1.ttf "a45678α" sweeps.png --font-size=100
The tests glyphs are:
_sample_sweep(-360, 0, "pad", "narrow", next(access_chars)),
_sample_sweep(0, 90, "pad", "narrow", next(access_chars)),
_sample_sweep(45, 90, "pad", "narrow", next(access_chars)),
_sample_sweep(247.5, 292.5, "pad", "narrow", next(access_chars)),
_sample_sweep(90, 270, "pad", "narrow", next(access_chars)),
_sample_sweep(-270, 270, "pad", "narrow", next(access_chars)),
_sample_sweep(-45, 45, "pad", "narrow", next(access_chars)),
_sample_sweep(315, 45, "pad", "narrow", next(access_chars)),

This shows:

Start color red is not drawn only from start angle, but from 0 degrees, but color stop 0 should be mapped to start angle.
Issues when start Angle is negative.
Issues when angle valus cross 0/360 degrees. (last three images)

Extend mode reflect
$ blackrenderer ~/dev/skia/resources/fonts/more_samples-glyf_colr_1.ttf "βγδεζηθι" sweeps_reflect.png --font-size=100
_sample_sweep(-360, 0, "reflect", "narrow", next(access_chars)),
_sample_sweep(0, 90, "reflect", "narrow", next(access_chars)),
_sample_sweep(45, 90, "reflect", "narrow", next(access_chars)),
_sample_sweep(247.5, 292.5, "reflect", "narrow", next(access_chars)),
_sample_sweep(90, 270, "reflect", "narrow", next(access_chars)),
_sample_sweep(-270, 270, "reflect", "narrow", next(access_chars)),
_sample_sweep(-45, 45, "reflect", "narrow", next(access_chars)),
_sample_sweep(315, 45, "reflect", "narrow", next(access_chars)),

Issues, as much as I can tell:

Start angle (in first picture) starts from vertical position, not from horizontal
The reflecting sector seems too small?

Extend mode repeat
$ blackrenderer ~/dev/skia/resources/fonts/more_samples-glyf_colr_1.ttf "κλμνξοπρ" sweeps_repeat.png --font-size=100
_sample_sweep(-360, 0, "repeat", "narrow", next(access_chars)),
_sample_sweep(0, 90, "repeat", "narrow", next(access_chars)),
_sample_sweep(45, 90, "repeat", "narrow", next(access_chars)),
_sample_sweep(247.5, 292.5, "repeat", "narrow", next(access_chars)),
_sample_sweep(90, 270, "repeat", "narrow", next(access_chars)),
_sample_sweep(-270, 270, "repeat", "narrow", next(access_chars)),
_sample_sweep(-45, 45, "repeat", "narrow", next(access_chars)),
_sample_sweep(315, 45, "repeat", "narrow", next(access_chars)),

Issues, as much as I can tell, similar to reflect:

Start angle (in first picture) starts from vertical position, not from horizontal
The reflecting sector seems too small?

Also, contrary to what I said earlier:

starting from start angle 0, and padding with red seems correct and is not an issue.

This shows:

Start color red is not drawn only from start angle, but from 0 degrees, but color stop 0 should be mapped to start angle.

With WIP Skia CL we are getting closer but we still need some clarifications on what happens at the 0 / 360 degree boundary.
Extend mode pad:
Test glyphs
_sample_sweep(-360, 0, "pad", "narrow", next(access_chars)),
_sample_sweep(0, 90, "pad", "narrow", next(access_chars)),
_sample_sweep(45, 90, "pad", "narrow", next(access_chars)),
_sample_sweep(247.5, 292.5, "pad", "narrow", next(access_chars)),
_sample_sweep(90, 270, "pad", "narrow", next(access_chars)),
_sample_sweep(-270, 270, "pad", "narrow", next(access_chars)),
_sample_sweep(-45, 45, "pad", "narrow", next(access_chars)),
_sample_sweep(315, 45, "pad", "narrow", next(access_chars)),

$ blackrenderer ~/dev/skia/resources/fonts/more_samples-glyf_colr_1.ttf "a456789α" sweeps.png --font-size=100

Skia

_sample_sweep(-270, 270, "pad", "narrow", next(access_chars)), does not match in BlackRenderer and Skia, even though this glyph IMO should be equivalent to _sample_sweep(90, 270, "pad", "narrow", next(access_chars)),.
Also, not sure why we diverge on _sample_sweep(315, 45, "pad", "narrow", next(access_chars)),.
This result however is based on certain assumptions that are not 100% clear in the spec, see https://github.com/googlefonts/colr-gradients-spec/issues/361#issuecomment-1105250860

Extend mode reflect
Test glyphs
_sample_sweep(-360, 0, "reflect", "narrow", next(access_chars)),
_sample_sweep(0, 90, "reflect", "narrow", next(access_chars)),
_sample_sweep(45, 90, "reflect", "narrow", next(access_chars)),
_sample_sweep(247.5, 292.5, "reflect", "narrow", next(access_chars)),
_sample_sweep(90, 270, "reflect", "narrow", next(access_chars)),
_sample_sweep(-270, 270, "reflect", "narrow", next(access_chars)),
_sample_sweep(-45, 45, "reflect", "narrow", next(access_chars)),
_sample_sweep(315, 45, "reflect", "narrow", next(access_chars)),

$ blackrenderer ~/dev/skia/resources/fonts/more_samples-glyf_colr_1.ttf "βγδεζηθι" sweeps_reflect.png --font-size=100

Skia

Similarly quite well aligned, not sure what happens in BlackRenderer on the 6th and 8th glyph, which should IMO be equivalent to 5th and 7th respectively.
Extend mode repeat
Test glyphs
_sample_sweep(-360, 0, "repeat", "narrow", next(access_chars)),
_sample_sweep(0, 90, "repeat", "narrow", next(access_chars)),
_sample_sweep(45, 90, "repeat", "narrow", next(access_chars)),
_sample_sweep(247.5, 292.5, "repeat", "narrow", next(access_chars)),
_sample_sweep(90, 270, "repeat", "narrow", next(access_chars)),
_sample_sweep(-270, 270, "repeat", "narrow", next(access_chars)),
_sample_sweep(-45, 45, "repeat", "narrow", next(access_chars)),
_sample_sweep(315, 45, "repeat", "narrow", next(access_chars)),

$ blackrenderer ~/dev/skia/resources/fonts/more_samples-glyf_colr_1.ttf "κλμνξοπρ" sweeps_repeat.png --font-size=100

Skia

Similarly quite well aligned, not sure what happens in BlackRenderer on the 6th and 8th glyph, which should IMO be equivalent to 5th and 7th respectively.

Also relevant: https://github.com/fonttools/fonttools/pull/2743

New, wider set of tests in https://github.com/googlefonts/color-fonts/pull/119, Chrome rendering with https://skia-review.googlesource.com/c/skia/+/566416


control for output data type of coordinate axes

Reported by ansley b manke on 23 Oct 2012 17:20 UTC
This has been requested a few times, by people like Patrick Brockmnann, and in this recent thread,
http://www.pmel.noaa.gov/maillists/tmap/ferret_users/fu_2012/msg00591.html
We have a goal of letting people keep their files as is, writing subsets without changing the data types or attributes.
How about this, an easy addition:

Keep track of the data type of coordinate variables, and by default write coordinate data using the type from the input file.

Allow the user to control the output type, with a SET AXIS/OUTTYPE=

Migrated-From: http://dunkel.pmel.noaa.gov/trac/ferret/ticket/1982

Comment by ansley.b.manke on 10 Nov 2015 00:02 UTC
This was done in Ferret v6.84


Replace SessionOption(s) with ClientFactoryBuilder (Go HTTP-only part 5)

Motivation:
SessionOption(s) is a generic option type whose original purpose is to
provide extensible options for supporting more protocols than HTTP.
Now that we do not support other protocols than HTTP, we can simplify
this further and make it much easier to construct a ClientFactory.
Modifications:

Replace SessionOption, SessionOptions and SessionValue with
ClientFactoryBuilder
Replace AllInOneClientFactory with DefaultClientFactory
Remove NonDecoratingClientFactory and move its code to
DefaultClientFactory
Simplify ClientFactoryProvider
Make ClientFactory implementations package-local because a users can
use ClientFactoryBuilder to construct a ClientFactory
Add more flags to Flags
Rename DecoratingKeyedChannelPoolHandler to
KeyedChannelPoolHandlerWrapper now that we do not use decorator
pattern actively for monitoring a connection pool

To-do: we need to simplify this further given that PoolKey is the
only key type we use.

Result:

Simplification

Added Javadoc. Please review them. :-)

Checked it again because of the change of the javadoc for the build and decorator method and it looks good 👍

Thanks, reviewers!


-W is an invalid option for pwd

I'm running Atom 1.8.0 beta 3 on Windows 7. It works, but when I try to launch it using the atom shell command, I get this failure:
{ ~ }  » atom                                                                                ~
/cygdrive/c/Users/Linda/AppData/Local/atom/bin/../app-1.8.0-beta3/resources/cli/atom.sh: line 3: pwd: -W: invalid option
pwd: usage: pwd [-LP]
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

I'm using babun as my shell, which may be part of the problem. I believe the failing line of code is resources/win/atom.sh on line 3. It doesn't look like -W is a standard flag for the pwd command.
Can anyone else reproduce this issue?

/cc @damieng: -W does in fact seem to be non-standard.

I think the reality is we can only support so many windows Bash shells. We've done a ton of work to get things working with MSYS, MSYS2, Cygwin and MinGW.  Have to draw the line somewhere.

@damieng: babun is built on Cygwin, so if Atom is supposed to work on Cygwin, I would expect it to work with babun as well. Can you verify that Atom is still working properly with Cygwin?

Confirmed also broken on Cygwin now.  Given the lack of uniformity between these bash-like environments and the constant attention they need I'm not sure we should actively support any.

@damieng: Is Atom a project that GitHub officially supports, or is it a community-supported open source project? If it's an official GitHub project, then I wonder if we could find a project manager to prioritize Windows support. If it's a community-supported project, then I'm not sure exactly what "actively supported" means one way or another. If people are willing to contribute fixes to the project, shouldn't they be accepted?

I can't speak for GitHub - you'd have to ask them but I do always take a look at the Windows PRs - there is only one right now which is pending some other important Windows related work (getting specs running)
Sorry for sounding frustrated - getting bash working working with the --wait on Windows has been painful. Atom has a built-in feature that basically causes it to quit if another copy of atom is running - after telling the other one to open the file. To work around this --wait on Linux uses signals - we have no such facility on Windows and have had to use PowerShell but getting the PowerShell script to be reliably called from various versions and distributions of Bash on Windows has been cat and mouse.
It looks like we should be able to detect Cygwin in the script and then do cygpath . -a -w to achieve the same result as pwd -W

@singingwolfboy Can you type the following two commands in to your bash and paste the results here? Ditto anyone else who has a variant not already in the list that follows;
uname -a
pwd -W
cygpath . -a -w

For reference, the other platforms I have access to right now are:
Latest Cygwin download
CYGWIN_NT-10.0-WOW dpg-desk 2.5.1(0.297/5/3) 2016-04-21 22:12 i686 Cygwin
-bash: pwd: -W: invalid option
c:\cygwin\home\damie

MSYS install/GitHub Desktop Shell in Bash mode
MSYS_NT-10.0 dpg-desk 2.5.0(0.294/5/3) 2016-03-01 13:48 x86_64 Msys
C:/msys64/home/damie
C:\msys64\home\damie\

MinGW install
MINGW32_NT-10.0 dpg-desk 2.5.0(0.294/5/3) 2016-03-01 13:48 x86_64 Msys
C:/msys64/home/damie
C:\msys64\home\damie\

Git 2.8.2.windows.1 Bash
MINGW64_NT-10.0 dpg-desk 2.5.0(0.295/5/3) 2016-03-31 18:47 x86_64 Msys
C:/Users/damie
C:\Users\damie\

Just upgraded my test machine from Windows 7 to Windows 10 before I saw your comment. Here's what I get from running those commands via babun:
{ ~ }  » uname -a
CYGWIN_NT-10.0-WOW Linda-PC 1.7.35(0.287/5/3) 2015-03-04 12:07 i686 Cygwin
{ ~ }  » pwd -W
zsh: bad option: -W
{ ~ }  » cygpath . -a -w
C:\Users\Linda\.babun\cygwin\home\Linda

MSYS1 install
MINGW32_NT-6.2 DESKTOP-KRL6KF7 1.0.11(0.46/3/2) 2009-07-11 17:46 i686 Msys
C:/msys/1.0/home/damie
sh: cygpath: command not found

@singingwolfboy Can you try replacing your atom.sh in %localappdata%\atom\atom-1.whatever\resources\cli with the contents from  https://github.com/atom/atom/commit/0e5a4ffb6e34687eb8bd208e170564f5ffa4419c and let me know if that works for you?

@damieng: It doesn't work for me. I put the error message in the pull request you made. (I have no idea why that's a syntax error, or what the problem is!)
Unfortunately, I don't think I'll be able to do further testing on this, at least not right now. I'm visiting my parents, and testing this setup on their Windows computer, but I'm leaving today. I think/hope/assume that if you fix this problem for Cygwin, it will work for babun as well, but I totally understand that the Atom team has to limit the number of different configurations it can support. Thanks for your help on this!

Hi, that error is actually caused by Cygwin being given a script with Windows-style CRLF's instead of LF's. I've merged the PR and included a line to tell git to leave the .sh line endings as LF. This should now work and be in the next full release.

Also broke in 1.7.3 on Windows + Cygwin. Thanks for fixing this.

If you want the fix sooner you can over write your resources\cli\atom.sh
with the one from master :)
On Thu, May 19, 2016, 13:28 Juraj Vitko<EMAIL_ADDRESS>wrote:

Also broke in 1.7.3 on Windows + Cygwin. Thanks for fixing this.
—
You are receiving this because you modified the open/close state.
Reply to this email directly or view it on GitHub
https://github.com/atom/atom/issues/11756#issuecomment-220438789

command still not working in 1.8.0, possibly a different isssue:

It didn't ship in 1.8. you can however overwrite your copy of atom.sh with
the one in resources/windows from master and see if that works.
On Sat, Jun 18, 2016, 03:08 Juraj Vitko<EMAIL_ADDRESS>wrote:

command still not working in 1.8.0, possibly a different isssue:
[image: image]
https://cloud.githubusercontent.com/assets/588573/16170259/9b92f3b6-3555-11e6-85b8-593e2f7a5bd5.png
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/atom/atom/issues/11756#issuecomment-226933740, or mute
the thread
https://github.com/notifications/unsubscribe/AAHQp4V6y5D1-R67C0OdZ3rATbq-y8dcks5qM8OkgaJpZM4Ie4NG
.


Add notification upon completion if window is closed

Uses document.hidden to check if the Alchemy window is visible and sends a notification if's not. Chooses one of various success/failure messages to display at random.
Closes #16

@briandennis sorry, merge conflicts ☹


Avoid querying unwritten values from changesets during historical lookups

This PR avoids querying the plain state or changesets for accounts and storage values if the history tables show the value has not been written. This will return incorrect results for queries about genesis accounts if you synced prior to #2606.
<1% of historical queries will incur an extra cursor.prev(). I have not benchmarked the cost of this, but I assume it worth it to save full lookups in the PlainState/Changeset tables.
The semantics of return value of storage() have changed when the value is zero. The old semantics were "If the key has ever been written (including after the requested block) return Some(StorageValue::ZERO), else return None. The new semantics are "If the key has not been written prior to the requested block return None, else return Some(StorageValue::ZERO).

Codecov Report

Merging #2966 (eb2e59f) into main (5c7c660) will decrease coverage by 53.70%.
The diff coverage is 0.00%.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
@@             Coverage Diff             @@
##             main    #2966       +/-   ##
===========================================
- Coverage   70.97%   17.27%   -53.70%
===========================================
  Files         520      520
  Lines       67144    67195       +51
===========================================
- Hits        47656    11611    -36045
- Misses      19488    55584    +36096

Flag
Coverage Δ

integration-tests
17.27% <0.00%> (-0.04%)
:arrow_down:

unit-tests
?

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

...storage/provider/src/providers/state/historical.rs
0.00% <0.00%> (-85.61%)
:arrow_down:

... and 365 files with indirect coverage changes

@joshieDo PTAL


fix: Fix typo of test_8 for BUFFER_SIZE 42

Test 8 would have gotten the .txt file of test 9.

You're right, thanks for the PR

Thank you for creating the test!


⚠ ClamAV has degraded performance

In 0054640, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 189 ms

Resolved: ClamAV performance has improved in 64a509c.


Could not find artifact ru.tinkoff:gatling-kafka-plugin_2.12:jar

I am trying to use this plugin in my Java maven project.
I am getting error like
Could not find artifact ru.tinkoff:gatling-kafka-plugin_2.12:jar:0.12.0 in central (https://repo.maven.apache.org/maven2)
Could not find artifact org.apache.kafka:kafka-streams-scala_2.13:pom:7.4.0-ce in central (https://repo.maven.apache.org/maven2)
Could not find artifact io.confluent:kafka-streams-avro-serde:pom:7.4.0 in central (https://repo.maven.apache.org/maven2)
Could not find artifact io.confluent:kafka-avro-serializer:pom:7.4.0 in central (https://repo.maven.apache.org/maven2)

how to solve this problem？I meet the same problem

Dependencies are in confluent maven. so need to include confluent maven in pom.mxl.

confluent
https://packages.confluent.io/maven/


chore: change the visibility of num mod

@ChengYueJia is there a reason that you want num to be public? We intentionally made it not public so that all methods have to go through our uint functions, since the num functions are generally a bit ugly and shouldn't be used directly.

@ChengYueJia is there a reason that you want num to be public? We intentionally made it not public so that all methods have to go through our uint functions, since the num functions are generally a bit ugly and shouldn't be used directly.

Hi, as we need to use plonky2x::frontend::uint::num::u32::gadgets::multiple_comparison::list_lte_circuit   .

@ChengYueJia if you continue to need this, we can potentially discuss merging it (or potentially making just list_lte_circuit gadget pub mod) since we really don'd want to make the entire num folder pub mod since it is not really meant to be used.


FloorMapSideEventItem should accept image if exists

Idea Description
Update FloorMapSideEventItem so that it can to show image if exists.
Reference images and links

✋

@matsumo0922 Thanks! Assigned!


Styling issues in Run or Debug button

Description:
Aliment of the Run or Debug button is wrong

Suggested Labels:
Bug
Studio
Suggested Assignees:
Damith
Affected Product Version:
4.0.0-M14

For me its showing correctly . please see
 I checked on chrome Version 58.0.3029.81 and firefox 56.0

this issue is there on Mac
Chrome 61.0.3163.100

Cannot see this issue anymore


[Submission]: Keploy extension for docker desktop

Docker Hub repository name
yaxhveer/keploy:1.0.0
Terms of services

[X] I accept the term of services

Hi, I quicky installed the extension, could you do some minor improvement before this can make it to the marketplace:

Change the docker.svg file copied in the extension image. This is the icon that appears when running the extension (icon in red circle). Please test it in dark/light mode to see how it renders.

/validate


Can I do unlimited requests?

I have a question. Most of the WhoIs python packages require a WhoIs API key. This one doesn't. Can I do unlimited requests and if so is this package just scraping the data from some website to check if it is available?

This package and the successor whoisdomain use the native Linux/Mac/windows
command line "whois" to do it's work. No keys required.
On Mon, Jan 8, 2024, 21:19 Martijn de Vries @.***>
wrote:

I have a question. Most of the WhoIs python packages require a WhoIs API
key. This one doesn't. Can I do unlimited requests and if so is this
package just scraping the data from some website to check if it is
available?
—
Reply to this email directly, view it on GitHub
https://github.com/mboot-github/python-whois/issues/339, or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACU73CT5PQTUHEJSZILW5RLYNRIFVAVCNFSM6AAAAABBSAQUWCVHI2DSMVQWIX3LMV43ASLTON2WKOZSGA3TCMJVG4ZTKOA
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>


Copying child process output

pexpect has child.logfile* APIs to log child process output to a file-like destination.
I looked around the docs but I didn't seem to find anything similar for rexpect.
Is there any chance this could be supported?

I think this is very important for this crate to be useful. I'll start looking at it.
I'm looking at pulling in termcolor crate, to output e.g. black output for stdout, green for stdin, and yellow for control-characters, or something like that.
I think it is very useful in pexpect for debugging and while developing scripts.


build(deps): bump dd-trace-cpp to v0.1.12

I created this pull request of Caleb's changes so that I can tell GitHub's diff to ignore whitespace. Also a good place to leave comments.

This has been proposed upstream in https://github.com/envoyproxy/envoy/pull/31526.


Dangerous approach outside the command area

Experienced on EDDH today:

How often are you seeing these?
On 30 December 2016 at 16:46, P@nther <EMAIL_ADDRESS>wrote:

Experienced on EDDH today:
[image: 1]
https://cloud.githubusercontent.com/assets/20812775/21568800/cdd2d656-ceb7-11e6-86c8-cbb2100c3793.gif
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/zlsa/atc/issues/774, or mute the thread
https://github.com/notifications/unsubscribe-auth/ASgmWJuTW-Q6Pf6YSOBv4wH1tL5zcq0Gks5rNTVLgaJpZM4LYR1j
.

I noticed it the first time today... did not play for long, though...

In that case, it can be fixed through airport design by adding an offset -
isn't particularly major though, so I'll fix that some time in the first
weeks of 2017.

I think I've seen this at other airports since 3.2.0 was merged too - might have affected the airport arrivals algorithm?  If I see it anywhere I'll post the details here.

The most likely cause is the way the arrivals are arranged in the airport file. A few things to point out to that end:

any arrival streams that "join" a common route will not be automatically separated from each other

if this attachment is absolutely necessary, perhaps you could make both spawn patterns "cyclic" and apply an "part" that fixes the issue. This isn't very realistic though.

setting a speed in a given arrival that is very high can cause successive arrivals to clump up when the first one slows down dramatically

setting a speed that is above the capabilities of all aircraft that could be spawned based on the specified airlines means though they will SPAWN with adequate separation, they probably won't have adequate separation by the time they get to the airspace boundary

The ATC repository is being migrated to it's new home at https://github.com/openscope/openscope,
and thus, all issues are being closed. If this is still an issue with the latest version of the sim
(accessible at http://www.openscope.co), or is a feature you still think we are lacking,
please reopen the issue at the new repo.
Please note that the vast majority of these issues have been copied to the new repository, or else are covered by other issues created there. See the below screenshot for what it looks like when your issue is known in the new repo:

Thank you!
Closing this issue.


CLI: run as server

Implement the ability to listen on a specified port for further incoming documents:

e.g. using the standard library wsgiref
http.server is not recommended for production but usable

How about using FastAPI and uvcorn?
In past for Obsei (https://github.com/obsei/obsei-rest), I used these techs. They are also suitable for production.
Along with FastAPI and Uvcorn, I used apscheduler which can help with repetitive jobs.

It is maybe a little convoluted, I would prefer a default Python-WSGI solution but I take note of it.

Note: see the API as described in corresponding doc page.

This looks good @adbar, also good idea in making API commercial.


add link to new warningFilter option in onwarn docs

Describe the bug
I wanted to use https://github.com/sveltejs/vite-plugin-svelte/blob/main/docs/config.md#onwarn yet it seems this is now superseeded by Svelte 5's warningFilter compiler option.
I propose to update the docs accordingly or include a link to the new option?
Reproduction URL

Reproduction
No response
Logs
No response
System Info
-

For reference: https://svelte.dev/docs/svelte/svelte-compiler#ModuleCompileOptions

onwarn is still supported. warningFilter is less flexible and does not include warnings emitted by vite-plugin-svelte (something we could change for uniformity)
a link to the new option can be added to the docs here, PR welcome.

thank you!


Handle new locations API response

:tada: This PR is included in version 1.24.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


update-Kafka-in-combination

This PR will Fix #98 which Update docs to only use "Kafka" in combination - "Apache Kafka" .
fix #98
Test :
npm run spell:error     was green, No error, No Warnings.

Hi @Rawshansharma  thanks for your PR!
Could you check your local branch again for errors? Based on the pipeline checks, there are still a lot of occurrences of the use of "Kafka" without "Apache"

Hi @Rawshansharma  do you want to continue with this PR? It's stale for a bit now. It's not a problem if you don't, I just need to know, so I could open the issue up again for other Hacktoberfest folks :)


Fixes sample link

Bugs Fixed

Fixes #600

PR Checklist

[ ] Has tests (if omitted, state reason in description)
[ ] Has samples (if omitted, state reason in description)
[ ] Rebased on top of main at time of PR
[ ] Changes adhere to coding standard

[ ] Updated documentation

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


[duktape/open62541] Update the SHA512 of distfile

Duktape and open62541 failed due to the SHA512 mismatch when download the distfile: https://bootstrap.pypa.io/get-pip.py , so update it.

Thanks @Cheney-W


Laravel routes not matching Vue's

Hi, thanks a lot for this starter kit. I'm having some issues starting out with Vue 2 integrated into Laravel and this is being very helpful.
I think I found an issue with the project though:

I go to my 'rooms' list (Vue 2 knows /rooms)
I hit refresh
Not found exception (Laravel doesn't know /rooms)

Nothing too critical, just thought you'd like to be aware of it.

Hi thanks for using the package.
The routing is handled by the vuejs itself using its own package - vue-router. If you are not building a single page application, then you are free to change your routing mechanism with laravel's built in router.
Thanks

I'll close this now. I'm not considering this as an "issue". Better read the docs carefully if your'e just starting out with vuejs. Thanks

Hi thank you for using it.
Vuejs is one of the Single Page Application javascript framework or a SPA
which comprise of master layout wherein the partials are rendered on it.
The routing itself is handled by vue-router not the typical routing scheme
from laravel.
Hope it clears you out. Cheers !
Ray
On Jan 19, 2017 9:17 PM, "Sérgio Castro"<EMAIL_ADDRESS>wrote:

Hi, thanks a lot for this starter kit. I'm having some issues starting out
with Vue 2 integrated into Laravel and this is being very helpful.
I think I found an issue with the project though:

I go to my 'rooms' list (Vue 2 knows /rooms)
I hit refresh
Not found exception (Laravel doesn't know /rooms)

Nothing too critical, just thought you'd like to be aware of it.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/fagray/vuejs2-laravel53-starter/issues/6, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AGJjtKGfJWrLkuxlSW7z4V_AdesprxqUks5rT2JxgaJpZM4LoGTw
.

I do understand that, but shouldn't things work if I hit refresh on a given page? I'm talking about having a catch-all route on Laravel's end so that any given vue component is rendered properly, like this:
Route::get('/{vue?}', function () {     return view('layouts.app'); })->where('vue', '[\/\w\.-]*');

Thanks for realizing my mistake. Great suggestion mate !

Already made the changes https://github.com/fagray/vuejs2-laravel53-starter/commit/56921331740f4259e7234116ff3e8226f596826f
Thanks mate !


E2 1802 fcm gcm

Fixes #
The goal of this ticket is to remove GCM support from Leanplum Android sdk. As starting APRIL 11th, GCM will no longer be supported by google.
Proposed Changes
https://leanplum.atlassian.net/browse/E2-1802
Cleanup the code, get rid of GCM and refactor to use the new correct FCM standard for fetching tokens.

Looking good, just one note, since we are modifying public API we need to bump major version.


Android minSdk

Is your feature request related to a problem? Please describe.
I see the min support for SDK is 23, is there some new features that I cannot use in the blow 23 version. Need clear response, because I can force override the version tools:overrideLibrary, but I am not sure whether there are some risks.
Describe the solution you'd like
A clear and concise description of what you want to happen.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.

Please test it by yourself we don't know either (Trust Android supports higher sdk version)


Switching to typescript

Description
Refactoring growcss to use typescript, stylelint, eslint and more

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@f87004a). Click here to learn what that means.
The diff coverage is 70.85%.

@@            Coverage Diff            @@
##             master      #18   +/-   ##
=========================================
  Coverage          ?   76.71%
=========================================
  Files             ?       37
  Lines             ?      597
  Branches          ?      153
=========================================
  Hits              ?      458
  Misses            ?      110
  Partials          ?       29

Impacted Files
Coverage Δ

packages/xy-grid/src/utils/FlexAlign.ts
90% <ø> (ø)

packages/image/src/styled/ImageElement.ts
100% <ø> (ø)

...es/elaborate/src/components/mediaquery/_mapNext.ts
100% <ø> (ø)

build/jest-config/setup-jsdom.js
100% <ø> (ø)

...ckages/image/src/styled/AspectRatioPlaceholder.tsx
100% <ø> (ø)

packages/xy-grid/src/utils/BreakpointCell.ts
100% <ø> (ø)

packages/image/src/styled/PreviewElement.ts
100% <ø> (ø)

packages/image/src/styled/FigureElement.ts
100% <ø> (ø)

packages/xy-grid/src/utils/CellSize.ts
100% <ø> (ø)

...borate/src/components/mediaquery/_mapNextNumber.ts
83.33% <ø> (ø)

... and 27 more

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 f87004a...fd24b49. Read the comment docs.

:tada: This PR is included in version 1.0.0-alpha.1 :tada:
The release is available on:

npm package (@alpha dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This PR is included in version 1.0.0-alpha.1 :tada:
The release is available on:

npm package (@alpha dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


vcmp support

Is it / can it be considered adding vcmp host/guest support? At least for non-Viprion devices. All that is needed, I believe, is a separate call to deploy a vlan on vcmp host (same vlan as the one being deployed on vcmp guest).
Thanks,
Michal

I'm in the same situation.

Thank you for your feedback. I have added this to our internal product backlog as AUTOTOOL-1246.

Same issues here... Can't forget about vcmp folks...

Where is this feature at on the roadmap?

This issue is still in the backlog and is not a high enough priority to be on our roadmap. If you have a critical need for this feature, please file an F5 support ticket as the README recommends: https://github.com/F5Networks/f5-declarative-onboarding#filing-issues-and-getting-help

Same issue here, also don't forget that the VLAN may be part of a route domain.

Same issue here, also don't forget that the VLAN may be part of a route domain.

Should be irrelevant in context of vcmp host..


Unable to read valid PNG

The following image cannot be read:

$ file invalid.png
invalid.png: PNG image data, 96 x 96, 8-bit/color RGBA, non-interlaced

import pixie
let img = readImage("invalid.png")

->
test.nim(2) test
pixie-1.1.3/pixie.nim(38) readImage
pixie-1.1.3/pixie.nim(23) decodeImage
pixie-1.1.3/pixie/fileformats/png.nim(430) decodePng
pixie-1.1.3/pixie/fileformats/png.nim(349) decodePng
Error: unhandled exception: Invalid PNG buffer, unable to load [PixieError]

Pixie version: 1.1.3
Nim Compiler Version 1.4.6 [Linux: amd64]

How did you generate the file? It appears to have extra NULL character at the end. Maybe some sort of null-terminated-string copy? It does not conform to spec but it looks like most png editors/viewers ignore that 0 byte at the end. Maybe we should too?

How did you generate the file?

This one wasn't made by me, so I'm not sure. I'm guessing a defective image editor added it in somewhere.
For what it's worth, Aseprite, GIMP and my system image viewer are all able to load it, so making Pixie accept trailing data is probably a good idea.

This fix is included in release 1.2.0 which is live as of a day or two ago.


Concatenate using Multiindex cannot be unstacked anymore

What happened?
When trying to concatenate data using a Pandas MultiIndex and then unstack it to get two independent dimensions (e.g. for varying different parameters in a simulation), the unstack errors. I have seen different errors with different data (MVE errors with ValueError: IndexVariable objects must be 1-dimensional, but my data errors with ValueError: cannot re-index or align objects with conflicting indexes found for the following dimensions: 'concat_dim' (2 conflicting indexes)).
One hint at the bug might be that conc._indexes shows more indexes then display(conc).
What did you expect to happen?
Originally (I think it was v2022.3.0) , it used to unstack neatly into the two levels of the multiindex as separate dimensions.
Minimal Complete Verifiable Example
import xarray as xr
import numpy as np
import pandas as pd

ds = xr.Dataset(data_vars={"a": (("dim1", "dim2"), np.arange(16).reshape(4,4))}, coords={"dim1": list(range(4)), "dim2": list(range(2,6))})
dslist = [ds for i in range(6)]

arrays = [
    ["bar", "bar", "baz", "baz", "foo", "foo"],
    ["one", "two", "one", "two", "one", "two"],
]
mindex = pd.MultiIndex.from_tuples(list(zip(*arrays)), names=["first", "second"])

conc = xr.concat(dslist, dim=mindex)
conc.unstack("concat_dim") # this errors

conc = xr.concat(dslist, dim='concat_dim')
conc = conc.assign_coords(dict(concat_dim=index)).unstack("concat_dim") # this does not

MVCE confirmation

[X] Minimal example — the example is as focused as reasonably possible to demonstrate the underlying issue in xarray.
[X] Complete example — the example is self-contained, including all data and the text of any traceback.
[X] Verifiable example — the example copy & pastes into an IPython prompt or Binder notebook, returning the result.
[X] New issue — a search of GitHub Issues suggests this is not a duplicate.

Relevant log output
No response
Anything else we need to know?
No response
Environment

Skip to left side bar

/
/phd_scripts/jupyter/
Name
Last Modified
import xarray as xr
import numpy as np
import pandas as pd

ds = xr.Dataset(data_vars={"a": (("dim1", "dim2"), np.arange(16).reshape(4,4))}, coords={"dim1": list(range(4)), "dim2": list(range(2,6))})
dslist = [ds for i in range(6)]

arrays = [
["bar", "bar", "baz", "baz", "foo", "foo"],

["one", "two", "one", "two", "one", "two"],

]
mindex = pd.MultiIndex.from_tuples(list(zip(*arrays)), names=["first", "second"])

conc = xr.concat(dslist, dim=mindex)
conc.unstack("concat_dim")

ValueError                                Traceback (most recent call last)
Cell In [24], line 15
12 mindex = pd.MultiIndex.from_tuples(list(zip(*arrays)), names=["first", "second"])
14 conc = xr.concat(dslist, dim=mindex)
---> 15 conc.unstack("concat_dim")
File ~/.conda/envs/xwrf-dev/lib/python3.10/site-packages/xarray/core/dataset.py:4870, in Dataset.unstack(self, dim, fill_value, sparse)
4866         result = result._unstack_full_reindex(
4867             d, stacked_indexes[d], fill_value, sparse
4868         )
4869     else:
-> 4870         result = result._unstack_once(d, stacked_indexes[d], fill_value, sparse)
4871 return result
File ~/.conda/envs/xwrf-dev/lib/python3.10/site-packages/xarray/core/dataset.py:4706, in Dataset.unstack_once(self, dim, index_and_vars, fill_value, sparse)
4703     else:
4704         fill_value = fill_value
-> 4706     variables[name] = var.unstack_once(
4707         index=clean_index,
4708         dim=dim,
4709         fill_value=fill_value,
4710         sparse=sparse,
4711     )
4712 else:
4713     variables[name] = var
File ~/.conda/envs/xwrf-dev/lib/python3.10/site-packages/xarray/core/variable.py:1764, in Variable._unstack_once(self, index, dim, fill_value, sparse)
1759     # Indexer is a list of lists of locations. Each list is the locations
1760     # on the new dimension. This is robust to the data being sparse; in that
1761     # case the destinations will be NaN / zero.
1762     data[(..., *indexer)] = reordered
-> 1764 return self._replace(dims=new_dims, data=data)
File ~/.conda/envs/xwrf-dev/lib/python3.10/site-packages/xarray/core/variable.py:1017, in Variable._replace(self, dims, data, attrs, encoding)
1015 if encoding is _default:
1016     encoding = copy.copy(self._encoding)
-> 1017 return type(self)(dims, data, attrs, encoding, fastpath=True)
File ~/.conda/envs/xwrf-dev/lib/python3.10/site-packages/xarray/core/variable.py:2776, in IndexVariable.init(self, dims, data, attrs, encoding, fastpath)
2774 super().init(dims, data, attrs, encoding, fastpath)
2775 if self.ndim != 1:
-> 2776     raise ValueError(f"{type(self).name} objects must be 1-dimensional")
2778 # Unlike in Variable, always eagerly load values into memory
2779 if not isinstance(self._data, PandasIndexingAdapter):
ValueError: IndexVariable objects must be 1-dimensional
conc = xr.concat(dslist, dim='concat_dim')
conc = conc.assign_coords(dict(concat_dim=index)).unstack("concat_dim")
conc
xarray.Dataset
Dimensions:
    first: 3second: 2dim1: 4dim2: 4
Coordinates:
    first
    (first)
    object
    'bar' 'baz' 'foo'
    second
    (second)
    object
    'one' 'two'
    dim1
    (dim1)
    int64
    0 1 2 3
    dim2
    (dim2)
    int64
    2 3 4 5
Data variables:
    a
    (dim1, dim2, first, second)
    int64
    0 0 0 0 0 0 1 ... 15 15 15 15 15 15
Attributes: (0)

xr.show_versions()
INSTALLED VERSIONS
commit: None
python: 3.10.6 | packaged by conda-forge | (main, Aug 22 2022, 20:35:26) [GCC 10.4.0]
python-bits: 64
OS: Linux
OS-release: 4.18.0-305.25.1.el8_4.x86_64
machine: x86_64
processor: x86_64
byteorder: little
LC_ALL: en_US.UTF-8
LANG: en_US.UTF-8
LOCALE: ('en_US', 'UTF-8')
libhdf5: 1.12.2
libnetcdf: 4.8.1
xarray: 2022.9.0
pandas: 1.5.0
numpy: 1.23.3
scipy: 1.9.1
netCDF4: 1.6.1
pydap: None
h5netcdf: 1.0.2
h5py: 3.7.0
Nio: None
zarr: None
cftime: 1.6.2
nc_time_axis: None
PseudoNetCDF: None
rasterio: None
cfgrib: None
iris: None
bottleneck: None
dask: 2022.9.2
distributed: 2022.9.2
matplotlib: 3.6.0
cartopy: 0.21.0
seaborn: None
numbagg: None
fsspec: 2022.8.2
cupy: None
pint: 0.19.2
sparse: None
flox: None
numpy_groupies: None
setuptools: 65.4.1
pip: 22.2.2
conda: None
pytest: None
IPython: 8.5.0
sphinx: None

Thanks for the report. There was a recent release (2022.09) with many Index related bugfixes (including MuliIndex) - could you test this?

Thanks for the quick response. This is actually also an issue on 2022.9.0, I just had the wrong kernel selected.

Looks like passing a pandas.MultiIndex object as dim argument to concat was forgotten during the explicit indexes refactor. While this can be fixed (could be tricky), we should deprecate it: it is convenient but probably too neat now that multi-indexes levels have their own, "real" coordinates (see https://github.com/pydata/xarray/issues/6293#issuecomment-1259228475). It should be preferred to explicitly chain concat with assign_coords (and set_index) like the last line in your example.


[5.9][move-only] More batched closure changes

CCC. This PR contains a few commits that do some small cleanups in the tests and
add more tests/test coverage , so I did not include them in the CCC. The CCC for
the major changes are as follows:
Commit 2f7c7e94146776deed6badbf8e323f6d86479df6:
• Description: [move-only] Ensure that we treat captured escaping closure
arguments as such even if the closure doesn't actually escape.
Specifically, we already have the appropriate semantics for arguments captured
by escaping closures but in certain cases allocbox to stack is able to prove
that the closure doesn’t actually escape. This results in the capture being
converted into a non-escaping SIL form. This then causes the move checker to
emit the wrong kind of error.
The solution is to create an early allocbox to stack that doesn’t promote move
only types in boxes from heap -> stack if it is captured by an escaping closure
but does everything else normally. Then once the move checking is completed, we
run alloc box to stack an additional time to ensure that we keep the guarantee
that heap -> stack is performed in those cases.
• Risk: Low risk. Only affects noncopyable types.
• Original PR: #65694
• Reviewed By: @kavon
• Testing: I added diagnostic tests that checked this behavior.
• Resolves: rdar://108905586
Commit 018f56fae265925ad45e3e006d49b5a45fc6678a:
• Description: [move-only] When assigning a var that escapes into a closure into
another local, emit the correct error message.
With some of the changes that I have made, we began to emit a mark_must_check
[no_copy] on a copy_addr here. This change teaches the move address checker how
to recognize that in this case if we have a project_box it is actually b/c we
have something captured by an escaping closure.
• Risk: Low risk. Only affects noncopyable types.
• Original PR: #65694
• Reviewed By: @kavon
• Testing: I updated the diagnostic tests that hit this behavior to have the new
correct diagnostic checks.
• Resolves: rdar://108972170

@swift-ci test

@swift-ci test macOS platform

MacOS tests failed in a flaky way in an unrelated test that doesn't have any noncopyable stuff in it.


Contributing guidelines

Describe the task
For someone new to Git and GitHub ecosystem, it's difficult to understand the concepts in one go. We should have a contributing guideline that can be helpful for new contributors.
Expected behavior

Updates on main readme

Create a new section with header "New contributor?"
The body for this section should have "If you are a new contributor, visit our Contributing Guidelines to get started"
The contributing guideline link should be present above.

Steps in contributing guideline markdown file

Create a new git branch - should have a bit more details with link of articles on how to create branch.
Make code changes that are needed
Commit and push the branch - more details with relevant links
Make a Pull Request - more details with relevant links

The contributing guideline has been added in GitHub refer screenshot

This issue is completed. Closing it.


[New App Request] Dell Command | Update

I have written a new NeverGreen script to return the latest versions of Dell Command | Update for Windows, this is obtained using a webscrape against the Dell Command | Update Summary page https://www.dell.com/support/kbdoc/en-uk/000177325/dell-command-update
N.B. The downloads ($URL in my script) are obtained from their own sub page ($ReleaseURL in my script) links from the Summary page
# Get-DellCommandUpdate.ps1

$AppName = "Dell Command Update"
$SummaryURL = 'https://www.dell.com/support/kbdoc/en-uk/000177325/dell-command-update'
[version]$Version = Get-Version -Uri $SummaryURL -Pattern '- Dell Command \| Update (\d+\.\d+\.\d+)'
Write-Verbose "Version :: $Version"

$Platforms = @(
    @{Architecture = 'x86'; Platform = 'Windows Universal Application'; Language = 'Neutral'; Pattern = 'Dell Command \| Update Windows Universal Application'; Download = 'Dell-Command-Update-Windows-Universal-Application_.*?_WIN_.*?\.EXE'}
    @{Architecture = 'x86'; Platform = 'Windows Application (Classic)'; Language = 'Neutral'; Pattern = 'Dell Command \| Update Application \(Classic\)'; Download = 'Dell-Command-Update-Application_.*?_WIN_.*?\.EXE'}
)

foreach ($Platform in $Platforms) {
	$SearchCount = 2

	do {
		$ReleaseURL = Get-Link -Uri $SummaryURL -MatchProperty outerHTML -Pattern $Platform.Pattern
		#Write-Verbose "Release URL :: $ReleaseURL"

		$URL = Get-Link -Uri $ReleaseURL -MatchProperty href -Pattern $Platform.Download
		#Write-Verbose "Download URL :: $URL"

		if ($URL) {
			New-NevergreenApp -Name $($AppName) -Version $Version -Uri $URL -Architecture $Platform.Architecture -Platform $Platform.Platform -Language $Platform.Language -Type 'exe'
			break
		}
		$SearchCount--
	} until ($SearchCount -eq 0)

	if ($SearchCount -eq 0) {
		Write-Warning "Could not find release for $($AppName) $($Platform.Platform) $($Platform.Architecture) $($Platform.Language)"
	}
}

@DanGough Unsure where you have got to in merging my additions into your next release, but thought I out to let you know...
FYI: This script appears to have broken, I suspect that Dell have changed the page slightly, and are now either expecting a specific header to be defined (I have so far been unable to determine this) or they are expecting a Cookie to be set - unsure if this can be achieved using PowerShell.
The script first checks the Dell Command | Update page (https://www.dell.com/support/kbdoc/en-uk/000177325/dell-command-update) - Defined as $SummaryUrl in my script, and searches for the URLs of the 2 platforms (Defined in $Platforms), this then opens each URL to search for and return the URL for the platform specific download by matching the Download in $Platforms.
It appears to be the second step (opening each URL) is where this is failing.


Pip button in tab bar doesn't show up

See in this video:
https://user-images.githubusercontent.com/87893636/156908342-7cd57da2-45ba-4251-a8eb-b7914aa6f889.MP4

@PoomSmart I tried to restart YouTube app after enable that option but it sill doesn't work

Detail
The bug appears since version 17.x.x
My device: iPhone 6 | iOS 12.5.5
Jailbreak: Chimera

@PoomSmart Any update to fix this ?

@NguyenASang
nếu bạn xem lịch sử Pull Request thì sẽ hiểu PoomSmart không thêm tùy chọn đấy mà là người khác thêm (BandarHL), nên bạn nên liên hệ người đó thì đúng hơn.
Look at the Pull Request, that option was added by BandarHL, you should contact him instead

@PoomSmart Fake the version works, it make the PiP in the bar tab display again. That's a smart way, thank you very much.
But one thing, I don't like the new PIP button very much, can you make it a little thicker ? (Just my opinion, the choice is yours)

Oh wait, the fake version will stop us from getting new stuffs in YT.
I will keep opening it until it is fixed


Strange localization behaviours

Not sure if this is related to Laravel 5.1, but with both the laravel-5 and develop branch I'm experiencing this behaviour:
Whatever locale I set in my frontend controller with App::setLocale('xx'):

non-JS labels are displayed correctly according to the locale set with App::setLocale
but js-localization is always set according to the browser (!) language.

I debugged by logging the Lang::locale() in both my frontend controller and in the JsLocalizationController in getMessagesJson() method, and the result is as mentioned above: Lang:locale() in JsLocalizationController is not influenced by the App::setLocale() value set in frontend controller, but always seems to depend on the browser's language. When I change the browser language, that value changes accordingly.
Any idea?

Hey Timo. Thanks for your feedback!
The issue was actually pretty simple: The localization controller that delivers the package's JS stuff set the locale. But as it is a request separate from the web app page, your app's locale logic had no chance to run for this request.
I changed a few things and the JS locale is set by some one-line inline JS code now.
Give it a try (develop branch) and tell me what you think :)
Cheers

That solved it. Thanks a lot for the quick help :)

PS: Merged develop into laravel-5. You will probably prefer to use this branch.


Apply k8s 1.18.5

Towards https://github.com/giantswarm/giantswarm/issues/12716

Just getting the basicapp integration updated to use K8s 1.18. Going with a ping.


Add Cloud Pub/Sub

Not enough stars: https://github.com/chiraggude/awesome-laravel/blob/master/CONTRIBUTING.md

@chiraggude I see
Just FYI stars count is not the right metric


Use 19px as the default font size for tabular data

All body copy should be the same, at 19px, this includes tabular data.
GOV.UK has tables set at 16px, these are to stand out from large areas
of body copy at 19px.
Add a .table-font-xsmall class, to recreate these smaller table styles.

This fixes #121.

cc. @timpaul, @edwardhorsford.

Not tested, but I support the idea in principle!

:+1: from me. It might be worth adding a table with a lot of columns, or wide column content, to illustrate the table-font-xsmall

:+1:


Add tests

fix #4

Can you add the workflow for code coverage as well? (also badge to readme reporting % covered)

Sure! Can you add the CODECOV_TOKEN?

Trying out organization level tokens now; it should be accessible here without adding it to the repo specifically (but first time trying, so maybe worth a shot?)

Oh nice! Fingers crossed

@CodyCBakerPhD Updated the testing trigger and added those extra workflows. They aren't working yet since they point to main, so let me know how you'd like to proceed.

@CodyCBakerPhD Updated the testing trigger and added those extra workflows. They aren't working yet since they point to main, so let me know how you'd like to proceed.

Yeah, that is always unfortunate
We'll just have to merge and proceed


Dart fixes

fixes some things(see commits) with the Dart lsp to make it work.

I tried to add an assert that prohibits dart.lsp.enable and dart.flutter-tools.enable to be both enabled, but i have no idea how to do it with nix's module system.

I also changed the default from dart.lsp.enable to dart.flutter-tools.enable. The reason behind it is that flutter-tools is compatible with both dart and flutter lsps, while dart.lsp is not compatible with flutter. But I had noticed that flutter-tools requires dart(or flutter) to be in path while running nvim, while dart.lsp doesn't. So I can drop the commit if you want dart.lsp to be the default.

honestly I also have no idea how to use assertions


lxqt.lxqt-globalkeys: 0.14.1 -> 0.14.3

Motivation for this change
Update to version 0.14.3
https://blog.lxqt.org/2019/10/release-lxqt-globalkeys-0-14-2/
https://blog.lxqt.org/2019/10/release-lxqt-globalkeys-0-14-3/
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nix-review --run "nix-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

@GrahamcOfBorg build lxqt.lxqt-globalkeys

@GrahamcOfBorg build lxqt.lxqt-globalkeys


aws classic elasticache ReplicationGroup automatic_failover_enabled cannot be enabled

What happened?
The elasticache.ReplicationGroup was first created with single node in single AZ. When doing an update to change to multi-AZ and automatic failover enabled, the automatic failover cannot be enabled. No error message.
Steps to reproduce
Initially create an ReplicationGroup as below:
aws.elasticache.ReplicationGroup(
    "replication-group",
    engine="redis",
    multi_az_enabled=False,
    automatic_failover_enabled=False,
    port=6379,
    node_type="cache.t3.medium",
    subnet_group_name=subnet_group.name,
    preferred_cache_cluster_azs=["ap-southeast-2a"],
    security_group_ids=[security_group.id],
    num_cache_clusters=1,
)

Then update with below:
aws.elasticache.ReplicationGroup(
    "replication-group",
    engine="redis",
    multi_az_enabled=True,
    automatic_failover_enabled=True,
    port=6379,
    node_type="cache.t3.medium",
    subnet_group_name=subnet_group.name,
    preferred_cache_cluster_azs=["ap-southeast-2a", ap-southeast-2b"],
    security_group_ids=[security_group.id],
    num_cache_clusters=2,
)

No error from running pulumi up, but checking from the AWS console that the automatic failover is still showing Disabled
If try to run pulumi up again, it will try to update the automatic_failover_enabled but still showing Disabled from the AWS console. No error message.
Expected Behavior
Expect to see the automatic failover become Enabled.
Actual Behavior
automatic failover is Disabled as shown from AWS console.
Output of pulumi about
No response
Additional context
No response
Contributing
Vote on this issue by adding a 👍 reaction.
To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).

Have resolved, need to set apply_immediately=true


Collisions prone via concurrency

set(myref, get(myref) + 1)

☝ this design isn't luck for real production with huge amount of concurrency tasks, which deals with same ref at same time
Big probability to receive wrong ref mutation
Much better to refactor solution to something like this
set(myref, fn(val) {val + 1})

And call update function inside actor itself. It's allow to avoid concurrency races and provide correct mutation of ref via pessimistic lock inside actor.

I unfortunately realised that after publishing, but that is why i quickly added the set_fun function. I still have to refactor the actor handler to actually use the functions directly though.

Side note, do you know if the vm would clean up and kill the cell actor if the garbage collector had cleaned up the process handle

I don't think, that GC can affect Actor somehow until it stopped

so cells created will just keep a whole bunch of memory until their parent dies? Is there any way to hook into the GC to make custom destruction sequences for the RefCell type?

I don't deep dived in Erlang/OTP, try to ask question in official Gleam Discord
In my opinion, you shouldn't touch memory at all, Erlang BEAM should do it best for you

meh i'll just leave it in that case. I have a feeling that Louis will not be happy seeing a refcell library made for gleam.

Yeah, agree. Louis already hated some of my libraries, because it's not Gleam idiomatic
https://github.com/darky/glatch
https://github.com/darky/gleaf


adding AVM customer presentation

Overview/Summary
adding AVM customer presentation
This PR fixes/adds/changes/removes
n/a
Breaking Changes
n/a
As part of this Pull Request I have

[x] Read the Contribution Guide and ensured this PR is compliant with the guide
[x] Checked for duplicate Pull Requests
[ ] Associated it with relevant GitHub Issues or ADO Work Items (Internal Only)
[x] Ensured my code/branch is up-to-date with the latest changes in the main branch
[x] Ensured PR tests are passing
[x] Updated relevant and associated documentation (e.g. Contribution Guide, Docs etc.)

Resources page added:

Navigation to the resources page available at the bottom of the menu:


dust: fix

Use pixie (the wrapper) rather than pixie-vm (the wrappee)
Add rlwrap command rather than using which

Fixes #72129

Motivation for this change
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[x] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
21.11 Release Notes (or backporting 21.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 137712 at 230e2670 run on x86_64-linux 1

1 package built successfully:

dust

5 suggestions:

warning: unclear-gpl
lgpl3 is a deprecated license, please check if project uses lgpl3Plus or lgpl3Only and change meta.license accordingly.
Near pkgs/development/interpreters/pixie/dust.nix:43:5:
   |
43 |     license = licenses.lgpl3;
   |     ^

warning: missing-phase-hooks
configurePhase should probably contain runHook preConfigure and runHook postConfigure.
Near pkgs/development/interpreters/pixie/dust.nix:20:3:
   |
20 |   configurePhase = ''
   |   ^

warning: maintainers-missing
Package does not have a maintainer. Consider adding yourself?
Near pkgs/development/interpreters/pixie/dust.nix:42:5:
   |
42 |     maintainers = with maintainers; [ ];
   |     ^

warning: missing-phase-hooks
installPhase should probably contain runHook preInstall and runHook postInstall.
Near pkgs/development/interpreters/pixie/dust.nix:33:3:
   |
33 |   installPhase = ''
   |   ^

warning: missing-patch-comment
Consider adding a comment explaining the purpose of this patch on the line preceeding.
Near pkgs/development/interpreters/pixie/dust.nix:18:15:
   |
18 |   patches = [ ./make-paths-configurable.patch ];
   |               ^


Not sure how I should deal with the forecast results and the results of the existing database

Hello! Thank you very much for developing such good software. Recently, I have a few unsure questions that I would like to ask you.
We assembled a genome and we made predictions through RepeatModeler software. We ran the RepeatMasker software using the predicted set of repeat sequences (***-family. fa) and found that the repeat sequence of the genome was as high as 38.75 %. This may be right. However, we also used the repetitive sequences of existing species based on dfam and repbase databases, and we found that the repetitive sequences reached 41.31%.  I also tried to merge the prediction results with the results of the database and found that the repetitive sequence was as high as 44.71%. This result was much higher than our expectations. This may be wrong.
I am not sure which result we should use for subsequent genome annotation analysis, I would like to ask you.
Looking forward to hearing from you!

Hi,
That is a good question. But, this does not necessarily sound like a problem. RepeatModeler processes samples of a particular genome assembly, so it may miss some specific TEs due to "bad luck" or due to limitations in the sequencing or assembly process that make them difficult to recognize. Dfam and RepBase include TE families from ancestral species, which are known from prior research but are too fragmented or mutated to meet RepeatModeler's thresholds. Due to the different limitations of the two approaches, it can be more informative to combine the newly discovered elements into one library as you did.
Does this seem likely to explain the differences in your results?

Hello!
Very happy to receive your reply!
You said that we used the combined collection as the input file. We tried it, and the result was very confusing to me.
We use the combined (cat ) result "the prediction result of RepeatModeler, dfam and repbase" and the result  is 44.71% as l said before.
If we first use the prediction result of RepeatModeler to shield the repetitive sequence., and then the shielded sequence again run the set of dfam and repbase the result is 43.64%. We first use the set of dfam and repbase and then run the the prediction result of RepeatModeler, the result is 43.91%.
I would like to ask which method should we use?
The combine is a very confusing place for us. What causes such a deviation?
Looking forward to hearing from you!

The combine is a very confusing place for us. What causes such a deviation?

Running RepeatMasker twice with two different libraries will likely produce different results from running it once with a combined library. For example, the two repeat libraries could include similar but not identical families or fragments of families. In this situation, the first RepeatMasker run might mask most of an element. Then, the second RepeatMasker run might not recognize the leftover part because it is too short. So, each RepeatMasker run can affect the other run depending on the order. If RepeatMasker starts with a combined library instead, it can more effectively discover the elements from both libraries at once.

I would like to ask which method should we use?

The most appropriate method will depend on your goal and how well the RepeatModeler libraries came out for your species. For example, one method might mask more sequence, while another could produce a cleaner annotation with fewer fragments or more well-known names.
I hope this explanation helps you to decide what method to use!

Thank you very much for your valuable advice and patient help.
Your help is really of great significance to our work.
We decided to "combine" it with the method you said.
Maybe this is a more appropriate method.
Sincerely yours

Glad to hear! It seems like this question has been answered, but please re-open this or a new issue if you have more.


Speculative Decoding not working with ExLlamaV2DynamicGeneratorAsync

Is the ExLlamaV2DynamicGeneratorAsync not working with speculative decoding? Hope that it is something i did wrongly instead cause i really want to use it
import sys, os
# sys.path.append(os.path.dirname(os.path.dirname(os.path.abspath(__file__))))

from exllamav2 import ExLlamaV2, ExLlamaV2Config, ExLlamaV2Cache, ExLlamaV2Tokenizer, Timer
from exllamav2.generator import ExLlamaV2DynamicGenerator, ExLlamaV2Sampler, ExLlamaV2DynamicGeneratorAsync, ExLlamaV2DynamicJobAsync
import datetime
import asyncio
#from util import format_prompt, get_stop_conditions

# Load model and draft model
async def main():
    total_cache_tokens = 16384

    #draft_model_dir = "/home//ML/model/Qwen2-7B-Instruct-5_0bpw_exl2"
    draft_model_dir = "/home//ML/model/Qwen2-1.5B-Instruct-5.0bpw-h6-exl2"
    draft_config = ExLlamaV2Config(draft_model_dir)
    # draft_config.arch_compat_overrides()
    draft_model = ExLlamaV2(draft_config)
    draft_cache = ExLlamaV2Cache(draft_model, max_seq_len = total_cache_tokens, lazy = True)
    draft_model.load_autosplit(draft_cache, progress = True)

    model_dir = "/home/remichu/work/ML/model/Qwen2-72B-Instruct-4.0bpw-h6-exl2"
    config = ExLlamaV2Config(model_dir)
    # config.arch_compat_overrides()
    model = ExLlamaV2(config)
    cache = ExLlamaV2Cache(model, max_seq_len = total_cache_tokens, lazy = True)
    model.load_autosplit(cache, progress = True)

    print("Loading tokenizer...")
    tokenizer = ExLlamaV2Tokenizer(config)

    # Create prompt. Don't use stop condition so we can measure speed over a set number of output tokens

    prompts = ["<|im_start|>user\nWrite a 200 words story about llama\n<|im_end|>\n<|im_start|>assistant\n"]

    max_new_tokens = 200
    gen_settings = ExLlamaV2Sampler.Settings()

    # Initialize generator without draft model, warm up to make sure we get correct timing results

    generator = ExLlamaV2DynamicGeneratorAsync(
        model=model,
        cache=cache,
        tokenizer=tokenizer,
    )

    generator_draft = ExLlamaV2DynamicGeneratorAsync(
        model=model,
        cache=cache,
        tokenizer=tokenizer,
        draft_model=draft_model,
        draft_cache=draft_cache,
        num_draft_tokens=5,
    )

    async def run_job(prompt: str, generator_to_use: ExLlamaV2DynamicGeneratorAsync, max_new_tokens):

        # Create an iterable, asynchronous job. The job will be transparently batched together with other concurrent
        # jobs on the started on the same generator.
        job = ExLlamaV2DynamicJobAsync(
            generator=generator_to_use,
            input_ids=tokenizer.encode(prompt, add_bos = False),
            max_new_tokens=max_new_tokens
        )

        full_completion = prompt

        # Iterate through the job. Each returned result is a dictionary containing an update on the status of the
        # job and/or part of the completion (see ExLlamaV2DynamicGenerator.iterate() for details)
        async for result in job:

            # We'll only collect text here, but the result could contain other updates
            chunk = result.get("text", "")
            full_completion += chunk

        return full_completion

    with Timer() as t_no_draft:
        print("-----------------------------------------------------------------------------------")
        print("- No draft model")
        print("-----------------------------------------------------------------------------------")
        tasks = [run_job(prompt, generator, max_new_tokens) for i, prompt in enumerate(prompts)]
        outputs = await asyncio.gather(*tasks)

        print(outputs)
        print()

    # Initialize and warm up generator with draft
    with Timer() as t_draft:
        print("-----------------------------------------------------------------------------------")
        print("- With draft model")
        print("-----------------------------------------------------------------------------------")

        tasks = [run_job(prompt, generator_draft, max_new_tokens) for i, prompt in enumerate(prompts)]
        outputs = await asyncio.gather(*tasks)

        print(outputs)
        print()

    print("-----------------------------------------------------------------------------------")
    print(f"speed, -SD: {max_new_tokens / t_no_draft.interval:.2f} tokens/second")
    print(f"speed, +SD: {max_new_tokens / t_draft.interval:.2f} tokens/second")

if __name__ == "__main__":
    asyncio.run(main())

output
-----------------------------------------------------------------------------------
- No draft model
-----------------------------------------------------------------------------------
["<|im_start|>user\nWrite a 200 words story about llama\n<|im_end|>\n<|im_start|>assistant\nIn the tranquil highlands of Peru, nestled amidst the Andean peaks, lived a llama named Luka. Unlike other llamas, Luka possessed an unusual dream. He yearned to travel beyond the mountains, to see the sea he had only heard tales about from passing traders.\n\nOne day, Luka gathered his courage and decided to embark on his journey. Leaving behind his herd, he descended the steep terrains, venturing into unfamiliar landscapes. He met various creatures along the way: the cunning fox who taught him wit, the wise old owl who shared stories of the world, and the cheerful hummingbird who sang songs of distant lands.\n\nAs days turned into weeks, Luka's hooves led him across lush jungles, arid deserts, and vast plains. His heart was filled with awe, his eyes with wonders unseen before. Yet, his longing for the sea remained unquenched.\n\nFinally, after a long and arduous journey, Luka reached the shoreline"]

-----------------------------------------------------------------------------------
- With draft model
-----------------------------------------------------------------------------------
["<|im_start|>user\nWrite a 200 words story about llama\n<|im_end|>\n<|im_start|>assistant\nIn the heart of the Andean highlands, nestled amid lush valleys and towering peaks, lived a llama named Luz. Unlike other llamas, Luz wasn't content with just grazing on the verdant grasses. She had a dream - to explore the world beyond her valley.\n\nEvery day, as the sun rose, painting the sky in hues of orange and pink, Luz would gaze at the distant horizon, imagining the vast deserts, dense forests, and deep oceans she'd heard about from passing birds. Her heart yearned for adventure, for stories to tell her kin.\n\nOne day, Luz gathered her courage. With a nod to her family, she embarked on her journey. She traversed through uncharted terrains, crossed roaring rivers, and climbed steep mountains. Along the way, she met various creatures who shared tales of their lands, enriching Luz's spirit.\n\nMonths turned into years, and Luz became a storyteller, a bearer of tales from far-off"]

-----------------------------------------------------------------------------------
speed, -SD: 20.37 tokens/second
speed, +SD: 20.68 tokens/second

Close the issue as the speculative decoding work perfectly.
The original prompt is too open hence there is not much benefit to speculative decoding.
When the whole code being run with this prompt:
prompts = ["<|im_start|>user\nWrite me a quicksort function in python\n<|im_end|>\n<|im_start|>assistant\n"]

The speed difference is much bigger:
-----------------------------------------------------------------------------------
speed, -SD: 20.33 tokens/second
speed, +SD: 48.22 tokens/second


Prep gcloud-0.18.4 release.

Identical to 0.18.3, except adding warnings to the PyPI page and the docs that the package has been renamed.
Closes: #2748, #2885.

Should the classifier change to Development Status :: 7 - Inactive?
Also, should there be a warning printed on install like @jonparrott was talking about?

@tseaver I agree with @daspecster about the classifier. See my comment, i.e. we don't need to make a new release just to update the PKG-INFO. That's not to say we shouldn't, but I don't think a new release is necessary.

Emitting a DeprecationWarning isn't likely to be much help:  they are not displayed by default.

I've started toying with the PKG-INFO for 0.18.3. So far I added a warning admonition (supported as part of ReST but apparently not by PyPI) and removed the badges that don't point to anything anymore (since our build URLs changed too)


[FLINK-5280] Update TableSource to support nested data

Thanks for contributing to Apache Flink. Before you open your pull request, please take the following check list into consideration.
If your changes take all of the items into account, feel free to open your pull request. For more information and/or questions please refer to the How To Contribute guide.
In addition to going through the list, please provide a meaningful description of your changes.

[x] General

The pull request references the related JIRA issue ("[FLINK-XXX] Jira title text")
The pull request addresses only one issue
Each commit in the PR has a meaningful commit message (including the JIRA id)

[x] Documentation

Documentation has been added for new functionality
Old documentation affected by the pull request has been updated
JavaDoc for public methods has been added

[x] Tests & Build

Functionality added by the pull request is covered by tests
mvn clean verify has been executed successfully locally or a Travis build has passed

Hi @wuchong
Thank you for review. I'll try to update the PR today.

Hi @wuchong
I've updated the PR according to your comments. Could you please review it again?

Thanks for working on this @mushketyk and the reviews @wuchong.
I just add a comment regarding the Scala trait with implemented function. I'll do a more thorough review in the next days.
Thanks, Fabian

Hi @fhueske, @wuchong
Thank you for your reviews.
I think creating three abstract classes is a good idea, since we don't expect any new types of table sources, so there will not be a lot of combinations.
I'll try to update the PR tomorrow according to all current comments.

Hi @fhueske, @wuchong
I've updated my PR according to your reviews.

Hi @mushketyk , thanks for the updating.
Regarding to the TableSource , currently, there are 8 TableSource interfaces provided to users including trait and abstract class. It is a little hard to choose which one to use to implement a custom table source. What about to implement TableSource as abstract class and provide default implementation for getFieldNames() and getFieldsIndices(). And provide three other abstract class : BatchTableSource (with getDataSet interface) , StreamTableSource (with getDataStream interface) and BatchStreamTableSource (with both interfaces), they all extend TableSource. In this way, we only provide 4 classes to user, the implementers should extend one of the latter three abstract class. What do you think ?

Hi @wuchong

And provide three other abstract class : BatchTableSource (with getDataSet interface) , StreamTableSource (with getDataStream interface) and BatchStreamTableSource (with both interfaces), they all extend TableSource

I thought about this, but in this case we won't be able to use an instance of BatchStreamTableSource where an instance of  BatchTableSource or  StreamTableSource is expected. Which seems to make BatchStreamTableSource abstract class useless.
I believe that we should be able to use BatchStreamTableSource where either TableSource, BatchTableSource or StreamTableSource is expected and this requires to use multiple inheritance which is only possible with traits. But since we want to provide partial implementations of these types I've add several abstract class for users to inherit from.
I see the issue with current approach, but I am not sure how to simplify it to achieve all required goals. Would better documentation do the trick?

What about extracting getDataSet(ExecutionEnvironment) and getDataStream(StreamExecutionEnvironment) to interfaces that called like DataSetGetter and DataStreamGetter.
And we can make BatchTableSource extend TableSource abstract class and implement  DataSetGetter interface. Make StreamTableSource extend TableSource abstract class and implement  DataStreamGetter interface. And  make BatchStreamTableSource implement both DataSetGetter and DataStreamGetter.  So that we can use TableSource plus DataSetGetter where only BatchTableSource is expected. For example, the BatchTableSourceScan can be changed to like this:
class BatchTableSourceScan(
    cluster: RelOptCluster,
    traitSet: RelTraitSet,
    table: RelOptTable,
    val tableSource: TableSource[_],
    val datasetGetter: DataSetGetter)

Can this solve our problem ?

Hi @fhueske, @wuchong
I think we can solve the problem with current TableSource class hierarchy in a different way. If we remove all abstract classes and move all default implementations in TableSource trait it will make class hierarchy much simpler. The only drawback of this is that Java users will need to provide implementations of trait methods that explicitly call default implementations.
I don't think this bad since it's a common way to extend Scala traits. We can additionally remove getFieldNames and getFieldIndices if you think they are superfluous.  But I don't think there is a big difference.
What do you think @fhueske, @wuchong ?

I'm fine with removing getFieldNames and getFieldIndices. The way of Scala trait is too hard to implement a custom TableSource for Java users who do not know this trick.

I just had a crazy thought. :-)
What do you think about moving getFieldNames() and getFieldIndicies() into a separate trait / interface maybe DefinedFieldNames?

I don't think I got the idea :) Could you elaborate on it?

we remove the methods from TableSource and add them to an interface. If a table source does not implement the methods, we use the names provided by the TypeInformation. If the table source implements the methods, we use those names. The distinction is done in TableSourceTable
What do you think?

I don't think we will win a lot with this. Even if we remove these two methods from the TableSource trait interface there is still getTypeIndices method and Java users will have to call it if they are going to implement a TableSource trait. And if a user knows how to inherit a trait with one method he/she will be able to inherit a trait with three methods.
The second problem with this approach is that it's not really Object-Oriented. We will have to rely on reflection tricks (probably sugared with pattern matching) while we simply having three methods is more clean OO solution.
What if we leave all three methods and simply add some base Java implementations that already implement these traits? Something like JavaBatchTableSource, JavaStreamTableSource, and JavaBatchStreamTableSource? Then users will not need to struggle with the traits inheritance issues.

Which getTypeIndicies methods are you referring to? TableSource does only have getReturnType, getFieldNames and getFieldIndicies. If we move the latter two to a separate interface, only getReturnType is left.
Also I think this is typical OO design. We do not need reflection to check if an object implements an interface. That's a very common operation in Java and Scala. A simple, isInstanceOf[DefinesFieldNames] in TableSourceTable is sufficient to check whether the table source implements the interface or not.
Isn't this a good compromise of having a lean interface (also simple for Java users) and at the same time the possibility to override field names if necessary?

@fhueske
Sorry, there are only two methods. Please ignore my comment :)
I think you are right and this seems like a good approach. If @wuchong is on board with this I'll update the PR accordingly.

I like this idea. In this way, we only need to provide BatchTableSource and StreamTableSource interfaces, not involving the odd BatchStreamTableSource.  We can keep the interface very clean.
If I understand right, all the concrete implementation of TableSource will not implement DefinesFieldNames for now ?

@mushketyk  no worries :-)
@wuchong Since the methods are only added when needed by implementing the interface there is no default implementation. The logic of the default implementation (calling the static method of TableEnvironment) is directly put into the TableSourceTable and only replaced if the table source implements the new interface.

Make sense to me 😄

@fhueske @wuchong Makes sense to me as well.
I'll try to update the PR during the weekend.

Hi @fhueske, @wuchong
I've updated the PR according to your feedback.
Could you please review it again?

Merging

Hi @fhueske, @wuchong
Thank you for your reviews and your help with this PR.
I've updated the PR.


淘宝登录框400错误

400 Bad Request
Your browser sent a request that this server could not understand. Sorry for the inconvenience.
Please report this message and include the following information to us.
Thank you very much!

Not tengine issue, I'm closing it.


Tasks in the environment

Hi,
Great work, excited to try out this environment. I was wondering what sort of tasks are integrated with each environment, since I couldn't find the documentation around it?
(x-posted from https://github.com/BYU-PCCL/holodeck-engine/issues/104, believe this is the more recent repo)

@ankeshanand I have written some basic documentation of the tasks for the environments in DefaultWorlds. Take a look at the tasks and worlds docs to get some direction. Thanks for the input! Let me know if anything is lacking

Thanks @MaxRobinsonTheGreat, this is def helpful! Could you also point me to the code where these reward functions are specified? I did a quick lookup but couldn't find it.

@ankeshanand The code for these reward functions is currently on the blueprint side which can only be edited/viewed when editing the Unreal project with Unreal editor. These can be viewed and edited by cloning the unreal project repo (https://github.com/byu-pccl/holodeck-engine) and editing it with Unreal Editor. However we realize these should be more transparent and are currently planning on moving them over to the C++ code in the near future.


Fix client with builder

There was a renaming of function in tower_hyper I think, so i changed them here too (I am not very good with github and I think i have left the commits of the other pull request I have made, sorry if it poses some problems)

Thanks so much!


'Find all reference' won't close on pressing 'ESC' when no reference is found

VSCode Version: 1.10.2
OS Version:  windows 10.0.14393

Steps to Reproduce:

Activate 'find all reference' on something that is not a symbol
Press ESC to close the popup and nothing happens

not for me. @DrakeXiang what extensions do have installed and do they take the ESC-key binding away?

@jrieken Thanks for the hint, after I disabled the 'vscodevim' extension, this issue no longer exists. There is indeed a custom key binding involves the , however, even after I comment out all my user settings, this issue  remains, seems to be the extension's guilt

Thanks for getting back. Please move this to the vim-extension then. @rebornix fyi


Discounts Applied

So far when adding a single Code to grouped discounts it shows up twice.
It does seem to be only taking the discount off 1 time though.

To recreate this issue:
I created a 25% off discount
When valid code entered (Not single use codes)
Starts immediatly
Products Groups
(I have 11 product groups added, some products are in more than 1 group this don't seem to make a difference)
No User Groups
When customer adds code it shows up like in the screen shot.

I believe I've tracked this one done and put in a fix for it, via:
https://github.com/concrete5-community-store/community_store/commit/188c9efad673507ef56c39a7b5655ea5b7e2563a
I could recreate this bug if I set up my discount with codes and then had the same code listed in it multiple times. That was the only way I could get that to happen though.

(the actual fix is one extra bit in an SQL statement, so it's pretty easy to apply directly)

Well this fix did take care of it.
I am very pleased at how this cart works and looks.
Thank you!


No averages shown if a surface's tag is selected

If one selects a tag which is given to a surface, than all topographies
are selected for analyses, but not the surface itself. Therefore no average is shown.
I expect that the average is also shown as the surface had been selected directly.

In order to reproduce:

assign a tag to a surface with at least 2 topographies, e.g. "demo"
change to tag tree and select "demo" tag
press "Analyze"
Select an analysis like "Power Spectrum" which should show an average
no average is show


Ignore unused imports

In flake8, users can ignore F401 to avoid warning about unused imports. I tried cython-lint --ignore F401 but it seems to do nothing. From the source of cython-lint, it doesn't seem like there is a way to disable this check right now. https://github.com/MarcoGorelli/cython-lint/blob/0afd5462e02db4a1f10442ca3111bb22c757ca7b/cython_lint/cython_lint.py#L744

Ideally users would be able to ignore import and cimport statements separately -- in the cases I'm considering, I'd like to detect unused cimport statements but ignore unused import statements.

good idea - interested in submitting a pr?

It seems like cython-lint might need a way to ignore violations raised by cython-lint itself (as opposed to pycodestyle) which seems like it could be a lot of scope. That would require naming a code for existing violations, unless you want to do something like add a flag for every violation (e.g. --ignore-unused-imports, --ignore-unused-cimports). What do you think is the best course of action?

either sounds good!
just fyi for now I'd expect that # no-cython-lint would work, but a cli argument to turn off this globally sounds useful


Add installation guide

Many people are installing this by: git clone https://github.com/pwntester/ysoserial.net

Hi, I think that many people are so familiar with git clone, so they may don't know what to do on the releases page (there are notes, source codes, ...), I used to be like this. So it's maybe better to include the download links in the README page!

Hi, I think that many people are so familiar with git clone, so they may don't know what to do on the releases page (there are notes, source codes, ...), I used to be like this. So it's maybe better to include the download links in the README page!

thanks!

thanks!


Change phpdoc @method tags

Fix #132

Thanks for the pull request. I'm not sure this does any difference? It seems to work fine with the previous behaviour:

What is your output from phpstan? When I'm running it everything seems fine.

It seems to work fine with the previous behaviour:

The return type of decode is wrong?

Oh, you're right. Merged.