Automatically detect encoding of the file opened

VSCode Version:1.0.0
OS Version:6.1.7601 Service Pack 1 Build 7601

Steps to Reproduce:

Use Notepad to save the batch under windows, So Character set is GBK.
open xxx.bat
All chinese text is garbled

Same here. Mac OSX El Captain
VSCode v.1.3.1
When i open a file "Windows 1252", it changes automatically to UTF-8, then i need to reopen as "Windows 1252" and save. If i close the VSCode and open, the files will be "UTF-8"

+1

How about adding setEncoding API to VSCode and creating auto detect and changing extension?

Curren status: you always can set a workspace encoding to be used for all files of an opened folder. You can also configure this globally for any files being opened (files.encoding).
Things that would help a lot already is to persist the encoding for particular files when changed from the status bar. This is tracked in https://github.com/Microsoft/vscode/issues/10444

I am using Chinese Simplified Win10 now.
Some of my old cpp and cs files(not many) are ANSI(GBK)-encoding which were created by old version of Visual Studio.
VS can open ANSI files correctly and I can search ANSI(GBK) string through files. With VSCode I have to open file and choose the correct encoding to search.
Notepad++ are more powerful dealing with encodings, it can detect many encodings and open correctly. So I don't need to choose the encoding manually and I can search a string from files mixed with GBK-encoding and BIG5-encoding without opening them, even if the hex-codes of the string are different in GBK and BIG5.
It would be good if vscode could detect encodings, at least ANSI encoding.

Great to see plan/progress on this issue. I agree that auto detecting encoding would be a great help for large projects which may has various encoding for environments difference or historical reasons across thousands of files. Really need this feature +1.

I expect this issue to appear in the iteration plan.

Why is someone trying to close this issue??
To be honest, auto encoding detection is one of the basic features of a modern editor. VS Code team need to face this issue rather than avoiding it.
Seriously.

Landed via the new files.autoGuessEncoding setting leveraging the power of jschardet.

+1
File encoding is most important issue for NON-ENGLISH PEOPLE!!
You English people don't know how we non-english people bored for changing encoding when opening file each time...

If someone wants to verify this, the feature landed in insiders (tomorrows build): https://github.com/Microsoft/vscode/issues/23322

bpasero, the issue doesn't appear to be resolved in the new build. I replied to that thread with a demo of the persistent bug.

@duanehutchins separate issues deserve separate issues on our GH issue tracker.

https://github.com/Microsoft/vscode/issues/23322#issuecomment-289995631


UMAP wrapper for SPD matrices

UMAP embedding wrapper for covariance matrices.
I'm also finishing up Riemannian LLE in the next days, should I include it in this one or make a new PR when it's done?
When LLE is implemented, I could write an example comparing the three embedding methods.

Uch, there's a dependency issue with the numba package used in umap which wants an older numpy version. I'll just wait for them to fix that (hopefully soon) and then try again. In the meantime I'll do the LLE.

Thanks, this is a good idea to have different embedding and it could be very nice to compare the different approaches. Beware that adding a dependency is a choice with lots of long term consequences. Even if UMAP is update its numba dependency, we should have very good reasons to add a dependency to UMAP in pyRiemann (adding thus indirectely numba and others).
Will you recode the Riemannian LLE from scratch or do you plan to use an existing implementation?

Good point. I really like UMAP, it often gives nicer results than the other methods, but the dependencies can be quite a pain.
I coded LLE basically from scratch based on the structure in sklearn.manifold._locally_linear and it doesn't require any new packages.


Removing lifetimes where it can be automatically inferred

For some reason this fails locally for two tests. But not on the workflow @chaseWillden do you have any idea why this is so?


[native bridge smart contract 6/n] - add function for derive ETH Address from pub key

Description
Describe the changes or additions included in this PR.
Test Plan
How did you test the new or updated feature?

If your changes are not user-facing and do not break anything, you can skip the following section. Otherwise, please briefly describe what has changed under the Release Notes section.
Type of Change (Check all that apply)

[ ] protocol change
[ ] user-visible impact
[ ] breaking change for a client SDKs
[ ] breaking change for FNs (FN binary must upgrade)
[ ] breaking change for validators or node operators (must upgrade binaries)
[ ] breaking change for on-chain data layout
[ ] necessitate either a data wipe or data migration

Release notes

changes are now in https://github.com/MystenLabs/sui/pull/16022, closing this PR


Go Server Configs and docker-compose.yml

New Go servers have to take some ENV config (devel, deployment, testing...). docker-compose.yml has to be corrected to properly share selected directories from local machine into the Docker containers.
In general re-write and test of docker-compose.yml is needed.

I have started adding config.yml via https://github.com/spf13/viper to our servers...

After the Dockerfile corrections I am seeing problems of this type: http://stackoverflow.com/questions/31746182/docker-compose-wait-for-container-x-before-starting-y. Huh.. it's never easy.
dockerize looks like an interesting fix: http://jasonwilder.com/blog/2014/10/13/a-simple-way-to-dockerize-applications/

Finally, dockerize is not needed, problem was hostnames of nats and mongo as defined in the docker-compose.
Commit https://github.com/Mainflux/mainflux/commit/0bc2fd8ff683a87d53174e6fa7304307d20c6c4a fixes this.


Fixed #27027 -- Restored Client.force_login() using the first auth backend.

b6433866682baac35a953e59298dff7f399ac49b changed the test client's force_login() method to require a backend to be specified when multiple are configured in settings. This restores it to its original behavior.

Note that the only case that this change affects is the one where an exception would be thrown. If a backend is specified, then this change doesn't affect the code path. If a backend is specified and there is only one backend configured, then it will use that backend, also not affecting the behavior. If a backend is specified and multiple backends are configured, then this will choose the first one rather than raising an exception.
So, the only reason I could see why this change might not be desirable is if for some reason we want to force test writers to choose a backend when calling force_login() with multiple backends configured.

merged in fc8f097117af7ada616fad20ae5b417fcf740413, thanks!


Scala.js 1.0.0-M5 support

Unfortunately the new release  is not binary compatible with the previous 1.0.0-Mx releases.
Release notes: http://www.scala-js.org/news/2018/08/13/announcing-scalajs-1.0.0-M5/
Probably you can close #1178 and #1299 - the version for Scala.js 1.0.0-M3 is already released.

@Starzu We have released for 1.0.0-M3 in 3.0.6-SNAP5, but unfortunately for 1.0.0-M5 we are blocked by scalacheck release.

This is probably not relevant anymore since scala.js 1.0.0 was released, and also, support for 1.0.0-RC2 was already published. See https://github.com/scalatest/scalatest/pull/1742.


Draw map markers on the elevation chart

Would it be possible to draw map markers into elevation chart?
Somewhat related to #169, when I draw multi-days route, I add markers at the end of each day. It would be cool to see these on the elevation chart. I quickly looked at elevation chart code but I'm unfamiliar with react. Do you think it'd be doable @nrenner?
I believe the upstream issue is https://github.com/MrMufflon/Leaflet.Elevation/issues/9

Somewhat related to #169, when I draw multi-days route, I add markers at the end of each day.

But those are not be distinguishable from regular via points that are used to adjust the route?

[...] unfamiliar with react.

You probably mean D3.js?
An idea might be to draw a SVG line for each waypoint similar to the mouse position indicator:

see this._mousefocus init and actual drawing as example
add a way to pass marker locations by either passing

waypoint latLngs and use _findItemForLatLng to get the corresponding item position
or segments instead of track, convert to GeoJSON MultiLineString and flag the first/last data item of each segment somewhere in _addData


Remove typeclass from interval constructor

Moves the Ordering inputs from the constructor to the methods that need it, as discussed in #600 .

Current coverage is 80.83% (diff: 87.93%)

Merging #605 into develop will increase coverage by 0.59%

@@            develop       #605   diff @@
==========================================
  Files           110        110
  Lines          4924       4942    +18
  Methods        4468       4494    +26
  Messages          0          0
  Branches        456        448     -8
==========================================
+ Hits           3951       3995    +44
+ Misses          973        947    -26
  Partials          0          0

Powered by Codecov. Last update d14c81a...bf81915


Create a staticlib with a node API for C

Enables the creation of custom nodes in C.
TODO:

[x] Testing
[x] Usage example
[x] README

On the c-dataflow/run.rs. Is this script, just for the CI and ease of testing it out, or would you recommend users to use a similar pattern run script to launch the dataflow?
From a user perspective, compiling c from rust might not be common knowledge I feel. And, therefore I would maybe just write a few lines in the README.md on how to run the dataflow without the run script.

The run.rs script is just for easier testing, since there are quite a number of steps. I assume that most C projects have their own build system, so I expect that most people will just integrate the build steps there.

From a user perspective, compiling c from rust might not be common knowledge I feel. And, therefore I would maybe just write a few lines in the README.md on how to run the dataflow without the run script.

Yeah, agreed! I will write up some instructions.

Thanks for testing!

Just for info, I have a couple of zenoh log when I run on stdout, and i feel that it should not be default, but it's not directly linked to this PR.

Yeah, I get these too. I'll open a follow-up PR to hide the low-priority messages (e.g. debug level), but I'm not sure if we should also hide WARN log messages...


Add instructions for edition 2021

Content request
We should add trouble shooting advice for people running into:
Caused by:
  feature edition2021 is required

  The package requires the Cargo feature called edition2021, but that feature is not stabilized in this version of Cargo (1.55.0 (32da73ab1 2021-08-23)).
  Consider trying a newer version of Cargo (this may require the nightly release).
  See https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#edition-2021 for more information about the status of this feature."

Are you willing to help with this request?
No.

This only requires a rustup update, right? I think that is how I fixed mine.

yep

I think this is ubiquitous enough that it's no longer needed, and if so, we should open a https://substrate.stackexchange.com/ post on it


Resources on Jupyter notebooks

Collect resources on how to use Jupyter notebooks - to be added to the TeachOpenCADD documentation:

https://www.dataquest.io/blog/jupyter-notebook-tutorial/

Collect resources on how to use Jupyter notebooks - to be added to the TeachOpenCADD documentation:
https://www.dataquest.io/blog/jupyter-notebook-tutorial/

@dominiquesydow
Assign this issue to me, I will make the documentation in the .rst file for - "How to use Jupyter notebooks" and will add it to /docs.

@Telomelonia, thanks!!
I was thinking of adding a "Jupyter notebook tutorials" section here:
https://github.com/volkamerlab/teachopencadd/blob/master/docs/external_tutorials_collections.rst
Adding the following two links to the new section should be enough (one tutorial and one cheat sheet):

https://s3.amazonaws.com/assets.datacamp.com/blog_assets/Jupyter_Notebook_Cheat_Sheet.pdf
https://www.dataquest.io/blog/jupyter-notebook-tutorial/

We can link to this new section in the installation instructions (step 4)
https://github.com/volkamerlab/teachopencadd/blob/master/docs/installing.rst
with something like "If you need an introduction to Jupyter notebooks, please check here ".
Would you like to take this on?

@dominiquesydow
Ohh nice ... That saves a lot of work will add the PR once done. ✌

@dominiquesydow
I added the PR for the issue.


chore(deps): upgrade configuration

Upgrades project dependencies. See details in workflow run.

Automatically created by projen via the "upgrade-configuration-k8s-25-main" workflow

⚪ Backport skipped
The pull request was not backported as there were no branches to backport to. If this is a mistake, please apply the desired version labels or run the backport tool manually.
Manual backport
To create the backport manually run:
backport --pr 3547

Questions ?
Please refer to the Backport tool documentation


Added test names to VS Code console logs for ruleTestRunner

PR checklist

[x] Addresses an existing issue: #3457

Overview of change:
Because some of the logs are to process.stdout, the VS Code F5 test running just shows a lot of "Passed" messages. Not very informative. This adds a folder > folder-style descriptor for the test if running with --verboseResultHandler, which is passed by launch.json.
Is there anything you'd like reviewers to focus on?
Alternately, it could just print everything using the console instead of process.stdout...?

Per https://github.com/palantir/tslint/issues/3457#issuecomment-342241640, switched it to always use console.log except for the diffs.

#3374 tries to get rid of all console.log calls and only use process.stdout.write.


Keyboard support on frontend is gone after UI revamp

A visually impaired friend needs to use keyboard (tab) to navigate the frontend of Osmosis. But after the UI is revamped, keyboard is no more supported, which is not good for accessibility.
Hope UI team can pay more attention to the need for accessibility and re-enable keyboard support.

What specific areas is your friend having trouble navigating? I'm able to navigate much of the controls/buttons

Closing with merge of #576, which brought tab and enter/space interactivity to all controls


local.ERROR: Route [voyager.assets] not defined.

1.6
local.ERROR: Route [voyager.assets] not defined. (View: .../vendor/tcg/voyager/resources/views/master.blade.php)

after composer update this error occurs

try reinstalling voyager. seems like [voyager.assets] is an invalid route on latest voyager. not sure  about your version. and i got same error as "Route [voyager.assets] not defined" when my admin routes where defined on any custom route except web.php.

@SamSolomonOfficial No, It doesn't work. Any update?

Clear the cache. It should works

I fix this by clear my view cache using below command
php artisan view:clear


bosh-init fails behind a firewall / proxy

My first time trying to deploy Cloud Foundry using bosh-init on AWS. The AWS environment is set up according to the instructions here.  I have updated the bosh.yml and replaced all of the PLACEHOLDERS with correct values. My proxies were set to the correct servers in the environment variables http_proxy and https_proxy. I also tried putting these variables in an "env" section in the bosh.yml file. No matter what I tried, I always got the result below. I also tried "bosh-init delete" on this config before trying to deploy again.  When I came home (no proxy), I got past this step although it failed again in a different way... but I haven't dug into that failure yet.
ftcpops [rey-bosh]➟ bosh-init deploy ./bosh.yml
Deployment manifest: '/Users/ftcpops/cloudfoundry/rey-bosh/bosh.yml'
Deployment state: '/Users/ftcpops/cloudfoundry/rey-bosh/bosh-state.json'
Started validating
Downloading release 'bosh'... Skipped [Found in local cache] (00:00:00)
Validating release 'bosh'... Finished (00:00:01)
Downloading release 'bosh-aws-cpi'... Skipped [Found in local cache] (00:00:00)
Validating release 'bosh-aws-cpi'... Finished (00:00:00)
Validating cpi release... Finished (00:00:00)
Validating deployment manifest... Finished (00:00:00)
Downloading stemcell... Skipped [Found in local cache] (00:00:00)
Validating stemcell... Finished (00:00:00)
Finished validating (00:00:01)
Started installing CPI
Compiling package 'ruby_aws_cpi/5e8696452d4676dd97010e91475e86b23b7e2042'... Finished (00:00:00)
Compiling package 'bosh_aws_cpi/81719102fc7b6d06d83f2bd411ab23b998593f4c'... Finished (00:00:00)
Installing packages... Finished (00:00:01)
Rendering job templates... Finished (00:00:00)
Installing job 'aws_cpi'... Finished (00:00:00)
Finished installing CPI (00:00:02)
Starting registry... Finished (00:00:00)
Uploading stemcell 'bosh-aws-xen-hvm-ubuntu-trusty-go_agent/3262.4'... Failed (00:01:27)
Stopping registry... Finished (00:00:00)
Cleaning up rendered CPI jobs... Finished (00:00:00)
Command 'deploy' failed:
creating stemcell (bosh-aws-xen-hvm-ubuntu-trusty-go_agent 3262.4):
CPI 'create_stemcell' method responded with error: CmdError{"type":"Unknown","message":"SSL_connect returned=1 errno=0 state=error: certificate verify failed","ok_to_retry":false}

@ftcjeff seems like your https proxy returns a certificate that cannot be verified by the aws cpi. im assuming you have installed custom ca cert on your machine?

@cppforlife No, this is just how we access the interest at our site. It's a (very) large enterprise, so I have no insight into how they deploy / configure the proxies. We're not given any ca certs for them.

 Hopefully that helps. I tried to scrub all of my PII out of it, but if anyone happens to see something in there please let me know so I can scrub some more. Thanks!
deploy.txt

If you're using https_proxy, pretty sure you'll be needing to configure trusted_certs - I think they'll would some certs somewhere for you to install?


Feature/add GitHub actions

Description:

Init github-actions config
Add test job to workflow
Remove travis file config

issue https://github.com/vutoan266/react-images-uploading/issues/23


All social media links have repeated text for screen readers on the contributors page

The cards on the contributors page have various links to twitter, github etc.
The problem is that the screen reader text is just set to "GitHub", "Twitter" etc. so that means a screen reader only gets a list of links with no real meaning.
Instead they should read "Siddarth Github", "Siddarth Twitter" (where Siddarth is the username of that contributor) etc.
github
[User Name] github

Any questions just ask!

Would love to take this up

@niteshseram assigned you the issue. :)

Thanks will make a PR soon


Getting Started needs to be updated for RN 0.11

Hi, this part particularly isn't up to date anymore:
Add libReactNativeIcons.a (from 'Products' under ReactNativeIcons.xcodeproj) to your project's Build Phases ➜ Link Binary With Libraries phase
And I can't find where to link the binary now by the way ^^
I had too much trouble finding how to fix my packages with the new 0.11 so I decided to start over and here's the first problem...
If anyone's working on 0.11... :-)
Cheers!

I have the same issue with react-native 0.11. I am no longer able to use react-native-icons in my project. I added the dependencies according to the README.

@arunshan Can you share how you are referencing it in your code? And what version of react-native-icons you are using?

I am using the following in package.json
    "react-native": "^0.11.0",
    "react-native-icons": "^0.4.0",

To reference it, I use the following
var {Icon, } = ('react-native-icons');
<Icon
      name='ion|ios-arrow-right'
      size={30}
      color='#777'
      style={styles.lightbulb}
/>

For what it's worth, I followed the 'Getting Started' guide as-is with RN 0.11 and haven't had any problems.

@corymsmith @bmcmahen My app was working fine before with the following version
 "react-native": "^0.4.4",
    "react-native-icons": "0.0.8",

I updated my OS to iOS 9 and also updated react native to the latest version. Then I get the issue mentioned above with react-native-icons.
Am I missing something ?

I'm trying react-native-icons version 0.5.0-rc with react-native 0.12.0-rc and Android emulator and I'm getting this screen:

It's like if it is not detecting Icon as a component.
Cheers,
Miguel

So does libReactNativeIcons.a need to be added now to "Link Binary With Libraries" now w/ > 0.11?
With it included, I get:
node_modules/react-native-icons/ios/ReactNativeIcons/IconTabBarItem/SMXTabBar.m:88:55: No visible @interface for 'RCTWrapperViewController' declares the selector 'initWithContentView:'

You'll have to use 0.4.0 with React Native 0.11.x
On Tue, Sep 29, 2015 at 9:14 PM, studio-dude<EMAIL_ADDRESS>wrote:

So does libReactNativeIcons.a need to be added now to "Link Binary With Libraries" now w/ > 0.11?
With it included, I get:
node_modules/react-native-icons/ios/ReactNativeIcons/IconTabBarItem/SMXTabBar.m:88:55: No visible @interface for 'RCTWrapperViewController' declares the selector 'initWithContentView:'
Reply to this email directly or view it on GitHub:
https://github.com/corymsmith/react-native-icons/issues/97#issuecomment-144270135

Is this still an issue? If not let me me know so I can close this.


Feature Request: Specify custom reference type

Biblatex gives you the opportunity to specify custom input types, referred to as custom[a-f]. It would be great to have the possibility to not only set extra fields but also the type of the entry with BBT so one could use this types (or define own ones).

You mean a facility to generate for example?
@myownreftype{citekey, ..... }

Something like this would be easy to add, but isn't the type field supposed to do the same?

To be honest, I am very new to Biblatex, so I don´t know very well about these things. I just read about the custom reference types like @customa{citekey,...} and thought that would be a good thing to have.
For my use-case type and keyword were the better options to go, as I found out later. Still, I think this is an useful feature, so thank you for adding it!


Problem with HiDPI - xfce, winit, gfx

Hello,
my last XFCE (or something else which happened around the same time) update caused a bit of turbulence in HiDPI handling in my winit/glutin/gfx app, kinda breaking it. I would appreciate some assistance in tracking it down.
In short, it's a gfx based simulation running in a 1280x1024 window by default. Here's how I'm creating the window (extra code omitted)
	let builder = glutin::WindowBuilder::new().with_dimensions(1280, 1024)
	let context_builder = glutin::ContextBuilder::new();

	let (window,
		mut device,
		mut factory,
		mut frame_buffer,
		mut depth_buffer) =
		gfx_window_glutin::init::<formats::ScreenColorFormat, formats::ScreenDepthFormat>(
			builder,
			context_builder,
			&events_loop,
		);

	let (w, h, _, _) = frame_buffer.get_dimensions();
	let hidpi_factor = window.hidpi_factor();

Before the update: w = 1280, h=1024, hidpi_factor=1.0
After the update: w = 2133,h=1706, hidpi_factor=1.666
I'm ok handling a frame buffer that large - in fact I'm even rendering on a 4x MSAA offscreen buffer and then resolving/blitting over - the problem is that the actual client area of the window is still 1280x1024 physical pixels, so a large part of the frame buffer is clipped away on screen.
I have worked the problem around temporarily by enforcing 96DPI for my monitor via xorg.conf (which restores the "before the update" behaviour), but I think it's unreasonable to ask all my users to do the same.
This could well be an issue with my window manager, my desktop compositor, or whatever, but it's upon me to find a workaround while the issue is being resolved - if ever (those things tend to take months or year to make it to distro).
I'd rather like to have an option to opt-out of automatic HIDPI handling by having an option to specify a hidpi factor via the window builder, such as:
let builder = glutin::WindowBuilder::new().with_dimensions(1280, 1024).with_hidpi(1.0) which would bypass the x11 query.
Other ideas?
Thanks
Nico

This should be tracked on winit instead: https://github.com/tomaka/winit/milestone/1

Closing this in favor of tomaka/winit#105


fix(deps): remove typescript-fsa and typescript-fsa-reducers

Checklist

[x] the contributor license agreement is signed
[x] commit message follows commit guidelines
[ ] tests are included
[ ] screenshots are included showing significant UI changes
[ ] documentation is changed or added

Description of change

Doesn't use them anymore, can be removed.

Didn't correctly remove deps, close it.


ARROW-4881: [C++] remove references to ARROW_BUILD_TOOLCHAIN

ARROW_BUILD_TOOLCHAIN has been superceded since the cmake refactor, but a few scripts still set and use it.

Should this be python=%PYTHON% like that

Should this be python=%PYTHON% like that

Since Python is already installed by conda create, you can probably delete the python=3.6 from the conda install invocation.

@kszucs Travis failed because brew couldn't find llvm@7 https://travis-ci.org/apache/arrow/jobs/509210161#L4002 could you restart this please

That happened with multiple PRs, brew has even hit github's abuse detection system - I'd fail again.
Probably cause by the recent llvm upgrade https://github.com/Homebrew/homebrew-core/blob/master/Formula/llvm.rb

Created issue for the travis error: https://issues.apache.org/jira/browse/ARROW-4986


Consider did:plc method addition

https://web.plc.directory/

Resolve bsky handle -> did:plc
https://bsky.social/xrpc/com.atproto.identity.resolveHandle?handle=filipk.bsky.social
or
Settings > Change handle > I have my own domain

Resolve did:plc
curl -s https://plc.directory/did:plc:7l2pjkp6si2qk6niu2tzloed | jq .

see https://github.com/bluesky-social/atproto/discussions/1892


add amq-streams channels

It looks like the amq-stream overlays were removed in #35.  I added back the overlays that are currently available in 4.9 and moved the objects into an operator folder.
@gnunn1 I am assuming the removal was accidental during your cleanup effort but just wanted to double check that I wasn't missing something else.

Adding @gnunn1 as a reviewer for visibility.

LTGM


Get "more like this" working on item pages

@barbarahui this looks like it works! Going to go ahead and close this. Thank you!
Item records from a variety of collections:
https://calisphere-stage.cdlib.org/item/ark:/86086/n2z036ns/
https://calisphere-stage.cdlib.org/item/3c87988e5f37bdeb53856069f859a75f/
https://calisphere-stage.cdlib.org/item/fe36e4715c2fc9ad9ae6cabd5f93c769/


Added Electron-only Minimizing to system tray toggle in settings

Issue #213 requested this, but was closed with only the Tray icon being added without any sort of minimizing/running in the background (which is the only reason a tray icon is useful). Also, there's another fix to Electron error handling.
This option only renders when the program is ran as an Electron app. (Default is disabled).

(sorry for the double PR, accidentally borked the first one)

probably my last PR for a while, this was the last thing I on my todo list

Website version:

Electron version (notice the minimize tray on close toggle, fully implemented):

ill re-open this with just the cherrypicked commits, some of my other changes accidentally leaked into this PR


Update release announcement card with 8th release info

Ready for dev
Please update this text to read:
The 8th Release of the Human Reference Atlas (v2.2) is now available! See what's new in HRA v2.2 in 8th Release Notes.
We will need to route to the new release notes page. More info on that content coming this afternoon!

@bherr2 @axdanbol - I am checking out the new HRA Portal now: It's looking great! I still see this card needs to be updated, please see this issue and reach out if you need anything!

Fixed on production https://humanatlas.io/


Using normal python installation as interpreter does not work

Problem Description
Using normal python installation as interpreter does not work.
What steps reproduce the problem?
Create 3 environments:

Python venv where spyder == 3.3.4 is installed via pip
Python venv where spyder-kernels == 0.4.3 is installed via pip
Normal Python installation (no kind of virtual env) where spyder-kernels == 0.4.3 is installed via pip

Now start spyder from env 1. using spyder3.exe and specify the Python interpreter to use (in preferences), it works for env 2, but not for env3.
When selecting env3 it seems to fall back to the default interpreter (env1) instead.
Tested by running: import sys; sys.executable in the IPython console.
I've tried different versions for spyder, spyder-kernels and have reset Spyder to factory defaults several times.
Versions
Tested on Windows 10.
All environments are based on Python 3.7.2 (64 bit)
Pip freeze (env1)
alabaster==0.7.12
astroid==2.2.5
attrs==19.1.0
Babel==2.6.0
backcall==0.1.0
bleach==3.1.0
certifi==2019.3.9
chardet==3.0.4
cloudpickle==0.8.1
colorama==0.4.1
decorator==4.4.0
defusedxml==0.5.0
docutils==0.14
entrypoints==0.3
idna==2.8
imagesize==1.1.0
ipykernel==5.1.0
ipython==7.4.0
ipython-genutils==0.2.0
isort==4.3.16
jedi==0.13.3
Jinja2==2.10
jsonschema==3.0.1
jupyter-client==5.2.4
jupyter-core==4.4.0
keyring==19.0.1
lazy-object-proxy==1.3.1
MarkupSafe==1.1.1
mccabe==0.6.1
mistune==0.8.4
nbconvert==5.4.1
nbformat==4.4.0
numpydoc==0.8.0
packaging==19.0
pandocfilters==1.4.2
parso==0.3.4
pickleshare==0.7.5
prompt-toolkit==2.0.9
psutil==5.6.1
pycodestyle==2.5.0
pyflakes==2.1.1
Pygments==2.3.1
pylint==2.3.1
pyparsing==2.3.1
PyQt5==5.12.1
PyQt5-sip==4.19.15
PyQtWebEngine==5.12.1
pyrsistent==0.14.11
python-dateutil==2.8.0
pytz==2018.9
pywin32-ctypes==0.2.0
pyzmq==18.0.1
QtAwesome==0.5.7
qtconsole==4.4.3
QtPy==1.7.0
requests==2.21.0
rope==0.14.0
six==1.12.0
snowballstemmer==1.2.1
Sphinx==2.0.0
sphinxcontrib-applehelp==1.0.1
sphinxcontrib-devhelp==1.0.1
sphinxcontrib-htmlhelp==1.0.1
sphinxcontrib-jsmath==1.0.1
sphinxcontrib-qthelp==1.0.2
sphinxcontrib-serializinghtml==1.1.1
spyder==3.3.4
spyder-kernels==0.4.3
testpath==0.4.2
tornado==6.0.2
traitlets==4.3.2
typed-ast==1.3.1
urllib3==1.24.1
wcwidth==0.1.7
webencodings==0.5.1
wrapt==1.11.1
Pip freeze (env2, env3)
backcall==0.1.0
cloudpickle==0.8.1
colorama==0.4.1
decorator==4.4.0
ipykernel==5.1.0
ipython==7.4.0
ipython-genutils==0.2.0
jedi==0.13.3
jupyter-client==5.2.4
jupyter-core==4.4.0
parso==0.3.4
pickleshare==0.7.5
prompt-toolkit==2.0.9
Pygments==2.3.1
python-dateutil==2.8.0
pyzmq==18.0.1
six==1.12.0
spyder-kernels==0.4.3
tornado==6.0.2
traitlets==4.3.2
wcwidth==0.1.7

When selecting env3 it seems to fall back to the default interpreter (env1) instead.

This looks like a PATH issue, so not a problem with Spyder directly.
I'm very sorry but we don't have time to help you debug this because we mainly support Anaconda. So it's up to you to understand the source of this problem.

When selecting env3 it seems to fall back to the default interpreter (env1) instead.

This looks like a PATH issue, so not a problem with Spyder directly.

At least there are no obvious conflicts in the PATH and PYTHONPATH is empty.
For what it is worth, spyder manages to start one process which uses env3 out of a total of 10 python processes, not counting Qtwebengineprocesses:
"env3\pythonw.exe" -m spyder_kernels.console ...

I'm very sorry but we don't have time to help you debug this because we mainly support Anaconda. So it's up to you to understand the source of this problem.

If you are interested, I might continue to look into it and I could post updates if I find something useful.

Sure, if you want to keep us posted about your findings and there's something we can do to solve this issue, that's fine for me.

I'm going to close this one just to clean our backlog a bit, but you're welcome to keep posting here.

The problem might be related to Python 3.7.2. There are no obvious issues in 3.7.3 using the same package versions. Looking at the Python changelog (https://docs.python.org/3/whatsnew/changelog.html) there seems to be significant changes to venv (on Windows) happening in 3.7.2 and 3.7.3.
3.7.3:
https://bugs.python.org/issue35872: Uses the base Python executable when invoking venv in a virtual environment
https://bugs.python.org/issue35873: Prevents venv paths being inherited by child processes
3.7.2:
https://bugs.python.org/issue34977: venv on Windows will now use a python.exe redirector rather than copying the actual binaries from the base environment.


Emoji dataset

Where can I get emoji dataset that your experiment used??
Thanks

I found emoji dataset from https://github.com/davrempe/domain-transfer-net


Update databases.md

Made a few changes:

Added a link for SQL Managed Instance
Updated link and description for synapse analytics
Updated description for power bi

@splitfinity : Thanks for your contribution! The author(s) have been notified to review your proposed change.

Microsoft authors of articles need to make updates through the private repository so the updates can be staged and validated by the current validation rules. After you review staging and fix all validation issues, you can add the sign-off comment to let the PR reviewers know the updates are ready to be merged.It's easy to access the private repo version of your articles in GitHub. Just add -pr to the URL, as follows:
Public repo URL: https://github.com/MicrosoftDocs/azure-docs
Private repo URL: https://github.com/MicrosoftDocs/azure-docs-pr
We have closed this pull request. Please resubmit the updates through the private repo. For more information, [see the contributor guide].(https://docs.microsoft.com/en-us/contribute/)

#Sign-Off

@EdPrice-MSFT: I'm sorry - only the author of this article, @splitfinity, 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.

Can I suggest adding specific Cosmos documentation to mirror the GCP offerings of BigTable, Firestore, Firebase.
Cloud Bigtable - Cosmos DB Cassandra API
Cloud Firestore - Cosmos DB Mongo API
Cloud Firebase Realtime Database - Cosmos DB Change Feed
I'd also include Cosmos DB analytical store against Google Bigtable
Are we missing Google Datastore, for which we would have Cosmos DB SQL API

#Sign-Off

@EdPrice-MSFT: I'm sorry - only the author of this article, @splitfinity, 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.

I moved the commits to the private repo to take advantage of automated metadata and link validation. I'll close this pull request. The new PR will be merged soon.


What is in the version 0.15.4

A new version of Authlib has been released on the pypi but it's nowhere to be found on GitHub tags nor the changelog. Did anything changed or was that version released due to some error?
https://pypi.org/project/Authlib/
Thanks!

Moreover it seems that 0.15.4 is missing recent changes on master, e.g. 49a8d8e53dccc73409a61fecd5a1c760fdf5cf74.

Release note and code will be available after two weeks. It is an early fix version for Authlib plus users.

Any updates on this?

Here are the code diffs between 0.15.3 and 0.15.4, which was published to pypi but code was not pushed here:
diff -r /home/jking/truth/conserv/ctcaas/.tox/py39/lib/python3.9/site-packages/authlib/consts.py /home/jking/.local/lib/python3.9/site-packages/authlib/consts.py
2c2
< version = '0.15.3'
---
> version = '0.15.4'
diff -r /home/jking/truth/conserv/ctcaas/.tox/py39/lib/python3.9/site-packages/authlib/jose/rfc7519/claims.py /home/jking/.local/lib/python3.9/site-packages/authlib/jose/rfc7519/claims.py
61,62c61
<         value = self.get(claim_name)
<         if not option or not value:
---
>         if not option:
64a64
>         value = self.get(claim_name)

I see no other packaging-related changes based on the pypi dist-info.

@lepture will you be making the changes official any time soon?

There is a release note in GitHub releases now.


store: use a more optimized get method in scc.rs

Remove the assertion to avoid double-reserving the same entry.
Replace scc::HashMap::get with scc::HashMap::read as scc::HashMap::get acquires exclusive locks for entry modification whereas scc::HashMap::read acquires shared locks and is more suitable for read-heavy workloads.
@nerdroychan Hi, nice to meet you. This crate looks great for measuring performance of various store types! I figure that the scc adaptor uses a sub-optimal method for get, so this PR replaces it with a more optimal method for read-heavy workloads.

Thank you for submitting the patch! For the set part, currently kvbench does not distinguish between insert and update. A set operation will be a blind write or kind of an upsert. Does scc provides this semantics or are you planning to add it?
Probably it can branch based on the return value of contains to avoid excessive box allocations.

Ah, didn't know that, I'll update that as well and upload a new commit soon!

Merged. Thank you!


Add Mouse Buttons/Gestures to Keyboard remapping

Description of the new feature / enhancement
add the Mouse Scrollwheel function to be mappable in the key remapping options. (I've got a keyboard w/volume knob that I want to remap to use for scrolling in multiple apps).
Scenario when this would be used?
when activating and using Keyboard Manager remap function.
Supporting information
No response

/dup https://github.com/microsoft/PowerToys/issues/1475


reloading breaks easyform

open doc/groovy/EasyFormDemos.ipynb and run the 1st cell
reload the page
run the 1st cell again

this error appears on the JS console, and the "run" button fails:
Could not open comm  --  Error: Class beaker.tag.run not found in registry
    at utils.js:880
    at new Promise (<anonymous>)
    at Object.load_class (utils.js:865)
    at CommManager.comm_open (comm.js:84)
    at i (jquery.min.js:4)
    at Kernel._handle_iopub_message (kernel.js:1223)
    at Kernel._finish_ws_message (kernel.js:1015)
    at kernel.js:1006
    at <anonymous>
(anonymous) @ utils.js:916
Promise rejected (async)
CommManager.comm_open @ comm.js:85
i @ jquery.min.js:4
Kernel._handle_iopub_message @ kernel.js:1223
Kernel._finish_ws_message @ kernel.js:1015
(anonymous) @ kernel.js:1006
Promise resolved (async)
Kernel._handle_ws_message @ kernel.js:1006
i @ jquery.min.js:4
kernel.js:1007 Couldn't process kernel message WrappedError {stack: "Error: Could not open comm↵    at new WrappedError…9561a88cca9375b7d86bf:20123:33↵    at <anonymous>", message: "Could not open comm", error_stack: Array(2)}

classic notebook fixed, leaving open for lab fix.


How can i subscribe to multiple notifications from different services UUID

Hi there. I found the half of the answer.
final UUID serviceUuid = // your service UUID
final Map<UUID, byte[]> genericModel = new HashMap<>();
final Observable<RxBleConnection> connectionObservable = // your connectionObservable

connectionObservable
        .flatMap(connection ->
                connection.discoverServices()
                        .flatMap(services -> services.getService(serviceUuid).map(BluetoothGattService::getCharacteristics)) // get characteristics you're interested in
                        .flatMap(Observable::from) // deal with every characteristic separately
                        .flatMap(characteristic -> connection
                                        .setupNotification(characteristic) // setup notification for each
                                        .flatMap(observable -> observable), // to get the raw bytes from notification
                                Pair::new) // merge characteristic with byte[] to keep track from which characteristic the bytes came
        )
        .subscribe(
                pair -> genericModel.put(pair.first.getUuid(), pair.second),
                throwable -> { /* handle errors */}
        );

But from one service UUID, i need to subscribe chars from two different services UUID. How can i reach that?

Hello!
Thank you for using the library.
This is a general usage question and as such should be posted on stackoverflow with rxandroidble tag—it will be easier to find by other users. Also feel free to check already posted questions as a similar one may be already answered.
Best Regards


Improve implementation of meta_qc_* utils

Close #204. Reviewers can see example tests and output improvements for some original motivating cases here:

https://github.com/nf-osi/dcc-site/issues/139#issuecomment-2501677571
https://github.com/nf-osi/dcc-site/issues/111#issuecomment-2502143842

Typically these functions should be automated in the background when the time comes instead of being manually run. However, to run this manually:
project_id <- "syn1234"
meta_qc_project(project_id)

**Output table is rendered in a markdown report, which can be inserted anywhere that accepts markdown -- such as GitHub issue threads as seen above.
This is essentially done but needs to hang out in the merge queue/blocked until #202 is merged first since it will rely on/need to incorporate the changes in annotation_qc.R made in #202.

Ready for review (main reviewer @allaway). Others for awareness.

@anngvu I tried this project and it says 0 files found for Raw Data (Young) and the subfolders.  I'm wondering if there might be some issues with the subfolders since Raw Data (Young) has many subfolders under neath it.
> meta_qc_project("syn21650484")
Datasets found for QC:
Bulk RNA Sequencing Donor RGCs
Raw Data (Young)
(found 3 files for Bulk RNA Sequencing Donor RGCs)
Found synapse_storage_manifest for dataset named 'Bulk RNA Sequencing Donor RGCs' (syn21650485)!
Downloading files: 100%|██████████| 1.57k/1.57k [00:00<00:00, 4.23kB/s, syn63811146]Downloaded syn63811146 to c:\users\cconrad\.synapsecache\747\148846747\synapse_storage_manifest_rnaseqtemplate.csv
Downloading files: 100%|██████████| 1.57k/1.57k [00:00<00:00, 4.19kB/s, syn63811146]Temp manifest files removed for dataset syn21650485
(found 0 files for Raw Data (Young))
Trying instead: Aim 2, Improving cell engraftment with scaffold; Aim 3, Pig RGCs development
(found 0 files for Aim 2, Improving cell engraftment with scaffold)
(found 0 files for Aim 3, Pig RGCs development)

Ok @anngvu that makes sense!


Add github native code scanning

Pull request checklist:

[x] CHANGELOG.md was updated, if applicable
[x] Documentation in docs/ or install-docs/ was updated, if applicable

This implements githubs new code scanning stuff. By default, the workflow scans:

Every push to the default branch
Every pull request to the default branch
The default branch at 3pm every Sunday

More information can be found below:
https://docs.github.com/en/free-pro-team@latest/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning
https://docs.github.com/en/free-pro-team@latest/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning

Is the CodeQL analyze going to run on every PR (and take so long)?

Is the CodeQL analyze going to run on every PR (and take so long)?

Yes - I can alternatively configure it so that it only runs on every push/weekly so it doesn't hold up the merging of prs?

It's fine since it's not set to be "required" to merge a pull request. As far as I understand it doesn't fail the status check either when the PR introduces a vulnerability, right?


Feature/bug fixes

Fixes #6
Fixes #7
Changes proposed in this pull request:

Convert target to Swift 4
Make sure we finish the dismissal transition, even if the animation get interrupted (don't rely on UIView.animate finished boolean)
Fix retain cycle in ImageViewerDismissalTransition by keeping the reference to the transition context week

Reverted Swift 4 in this branch


[BUG] Notes in 'New' are not included in review queue

Describe the bug
As part of incremental writing, I'm constantly adding new notes to my review queue. The problem is, when I execute the 'Open a note for review' command, the plugin never shows notes in 'New'. It only shows notes that have already been reviewed. This is unexpected behavior and means that new notes are not easily scheduled into the review queue. I have to manually click on each note, one by one, under 'New' and execute a review command (good/easy/hard) to get them scheduled.
This breaks the easy workflow of running 'Open a note for review' via hotkey.
To Reproduce

Tag a new note with the review tag, e.g. #review
Run 'Open a note for review' command repeatedly
The new note never comes up for review

Expected behavior
'New' notes should be treated as a fallback for 'Today'. When you run 'Open a note for review' command, review notes in Today first. When Today is empty, review notes in New. When New is empty, review notes scheduled for the future.
This would restore the easy workflow of running 'Open a note for review' via hotkey, knowing all notes will be reviewed properly.
Versions (please complete the following information):

OS: MacOS
Obsidian version: v0.12.14
Plugin version: v1.6.1
"5.0 (Macintosh; Intel Mac OS X 10_14_6) AppleWebKit/537.36 (KHTML, like Gecko) obsidian/0.10.6 Chrome/87.0.4280.88 Electron/11.1.0 Safari/537.36"

I can confirm this behaviour on Windows as well: Obsidian version: v0.12.12

The fix for this should be available in the next release.

I can confirm this behaviour on Windows as well: Obsidian version: v0.12.12

The recent update has fixed the problem on my installation 👍

It seems that the number in state bar is still wrong? It doesn't count those notes in New.

I don't think that's a regression, it wasn't counting new notes even before support for multiple note queues was added.

@11-check-it-out, @MattSPalmer's right. That only counts notes that have already been scheduled and are due for reviewing.

Closing since this was fixed.


Start of my simple text editor component

Zero To Mastery - Webblocks 2022 📦📦
👉 Please remove the below and replace with your own values, leaving the headers where they are. 👈
PR contains:

Code for my web blocks component for hacktober fest

Breaking changes
None
Screenshots
None

Closing due to unresolved change request. Feel free to resolve and reopen.


Hi-fi Designs - My Reputation (2/20-2/24)

Job to be Done
As an analyst, I want to see the global reputation decay rate and be able to pause my personal decay when I know I won't be able to participate in challenges for an extended amount of time, so that I'm not penalized while I'm away, and don't lose access to marketplaces I've worked hard to enter
As an analyst, I want a place to keep track of rMETRIC I've been issued or slashed, so I can understand how/why my reputation is impacted as I participate in challenges day to day and avoid any surprises (especially slashing)
Requirements (Note how we display in Ecosystem / Metrics)
View Reputation info

View global reputation decay rate: -50% every 90 days
View total rMETRIC decayed for me
View total rMETRIC issued to me
View total rMETRIC slashed from me
View My rMETRIC balance

Manage Reputation decay freezing settings

Freeze decay -- set end date and time for freeze decay (no start input, starts automatically once tx is confirmed)
Confirm -- understand that the app will be view-only until you unfreeze (can't create or claim anything)
Note: we won't support the ability to stop freezing decay yet (if users scream for this we can revisit)

Design

Sandbox: https://www.figma.com/file/66Myyf1MVmY8UKv7BrVUa5/MDAO-App-Designs?node-id=5191%3A36061&t=YZlULntGROevNP9s-0
Dev ready:

Adding @masonchain so that we stay on top of this one.
This one is in your court on the protocol side, Mason. Would you mind leading this one for anything that comes up during the process of integration?

This is all supported by the contracts.
There are some patterns of getting the data necessary that may be weird as it's not reading directly to the contract.
Reputation Metrics

View global reputation decay rate: -50% every 90 days
View total rMETRIC decayed for me
View total rMETRIC issued to me
View total rMETRIC slashed from me
All of these need to be retrieved either shroomDK or simulated in the app like the decay rate calc.

Decay freeze settings

Manage Reputation decay freezing settings
Freeze decay for up to n days? << do we want to limit this?
Set start/end for freeze decay
Stop freezing decay -- decay freezing stops and the app is actionable again

I did not see anywhere in the designs for the admin control of managing the overall decay settings, but that is not entirely necessary just yet.
The freezing decay is all supported but there is a small disconnect with selecting the start date of freezing. When configuring the decay settings, the admin/governor can set a time for when decay begins, or stop all decay by changing the decay rate and interval. While users cannot select a start time to begin their freeze and the freeze begins when they run the transaction.
Additionally, I noticed we do not have any logic for whether a user can unfreeze. Currently on the contracts, you can alter the time you are frozen but cannot just directly unfreeze. I think it adds gamification as someone can freeze their reputation to infinity until they see a request they like, unfreeze, signal, and freeze again indefinitely. We probably need to discuss all the implications of freezing in our next meeting.

@masonchain your comment above is so helpful, thanks for flagging this. we can absolutely update the UI to support freeze for n days as opposed to start/stop. I was also curious if we want to put a limit on that number of days? @drakedanner @nftchance . Mason, I added you to a sync on Monday with design where we are gonna do a final review of the My Reputation screens and we can incorporate some of these changes accordingly!

updated scope 2/27

Freeze decay -- set end date and time for freeze decay (no start input, starts automatically once tx is confirmed)
Confirm -- understand that the app will be view-only until you unfreeze (can't create or claim anything)
Note: we won't support the ability to stop freezing decay yet (if users scream for this we can revisit)


Fix output check on report commands

Closes #5040

We'll try to take a look at it ASAP! Thanks!

Merged manually. Thank you! 👏


Broken IBL reflections

I am using filament for android and I discovered the following issue using an Android 10 device (Huawei P20). I have zipped up the example project that demonstrates this problem here and you can find a video of the issue here
I used the ModelVIewer class to load a glb file containing two reflective spheres into a scene. Then I add a skybox and IBL using the following code:
    private fun createSkybox() {
        val engine = modelViewer.engine
        val scene = modelViewer.scene
        readCompressedAsset("pillars_2k_skybox.ktx").let {
            scene.skybox = KtxLoader.createSkybox(engine, it)
        }
    }

    private fun createEnvironmentLighting() {
        val engine = modelViewer.engine
        val scene = modelViewer.scene
        readCompressedAsset("pillars_2k_skybox.ktx").let {
            scene.indirectLight = KtxLoader.createIndirectLight(engine, it)
            scene.indirectLight?.intensity = 10_000f
        }
    }

I would expect the spheres to fully reflect the IBL from all orientations, but what I find is that there are sections of the spheres which do not reflect the IBL like so:

Initially I assumed this must be a problem with the ktx file, but the file I am using is from this git repo at: docs/webgl/pillars_2k/pillars_2k_skybox.ktx. Additionally there is no tearing or blank sections in the background cubemap. What is most puzzling is that when I rotate the device and the view is destroyed and re-created, the sections of the spheres that do not reflect the IBL are different, as in the below image:

Any help would be much appreciated. Thank you.

How do you create the sphere? The problem could be caused by incorrect normals on the 3D object.

I created the spheres and material in Blender. I just used a default sphere with smooth shading, you can see the setup here:

After exporting to glb I dragged it into https://gltf-viewer.donmccurdy.com/ and the spheres seem to reflect the IBL fully in there:

It looks like you are using pillars_2k_skybox.ktx for both the skybox and the IBL.  Note that cmgen can generate two KTX files: one for the KTX and one for the IBL.  They're not the same thing.

Ah yes good catch @prideout. That KTX file will not work for the reflections. BTW @SamAmco you can also try your glTF directly in Filament on this page: https://google.github.io/filament/viewer/

I see, thanks very much guys. I will close this issue then.


ng generate component [name] --type use to work on 9.0.1 now disappear on 9.0.3

🐞 Bug report
Command (mark with an x)

[x] generate

Is this a regression?

 Yes, the previous version in which this bug was not present was: `"@angular/cli": "^9.0.1",`
I love this feature so much
Description
when I generate component, I can use --type to decide the extension of component. for example:
ng g c home --type=page could generate home.page.ts used to work on angular CLI 9@beta, @9.0.1, now it is disappear on @9.0.3

as document said, it should be there

@hiepxanh, can you run ng version and npm ls @schematics/angular please?
In the first screenshot, I am seeing options which are no longer available since version 9.0.0, I am thinking you are experiencing package hoisting issues.

you are correct, I can't understand the left project was use ng update --all but seem look like it not work correctly, thank you to point this out. I'm closing this issue


colBert Server Down...

Hello, the server of http://ec2-35-87-71-196.us-west-2.compute.amazonaws.com:8893/api/search seems down.  Could you fix it...

It works again! Would you plan to release a stable and formalize version of this server


bin/docker-build should only build the CLI executable for the host platform by default

The objective here is to speed up and simplify the edit-build-test cycle by removing inefficiency in how the CLI executable is built, while still being able to reply on bin/docker-build to ensure that the CLI executable is built with the same version tag as the rest of Conduit.
Currently:

bin/docker-build executes bin/docker-build-cli (and other things, not relevant to this issue).
bin/docker-build-cli executes bin/docker-build-cli-bin
bin/docker-build-cli then does the following things:

3 executables, one for each target platform, are built in a Docker container:RUN CGO_ENABLED=0 GOOS=darwin  go build -o /out/conduit-darwin [...]
RUN CGO_ENABLED=0 GOOS=linux   go build -o /out/conduit-linux [...]
RUN CGO_ENABLED=0 GOOS=windows go build -o /out/conduit-windows [...]

A new Docker container is built, containing just those three output files.
All three executables are extracted out of the Docker image created in step 3.2 into the local filesystem at target/cli/${os}/conduit.

In typical usage of bin/docker-build, we have almost zero use for anything except the CLI executable for the host platform. That is, if I'm running bin/docker-build on Linux in my edit-build-test cycle then I don't care about any of the docker images created above; as far as the conduit executable is concerned, I only care that conduit is built and written to target/cli/linux/conduit. In particular, I never need the conduit images to be built for Windows or Mac. Similarly, somebody running on a Mac doesn't usually need the images built for Linux or Windows.
We should redo this so that the default action of bin/docker-build is to skip as much of the above as possible and directly build target/cli/${os}/conduit where ${os} is the host OS, and only build the other things (the docker images and the executables for other platforms) if/when specifically requested.

I'll take this one. But my 3 week long vacation start tomorrow so it might take a while... :)

@alenkacz what better way to spend vacation than by working on Conduit! 😄

@alenkacz Great! Note that I already removed docker-build-cli, so steps 1 and 2 above are now:

bin/docker-build executes bin/docker-build-cli-bin

@briansmith yep, I already figured, thanks :)


Use the zone from the metadata for creating locality

Current implementation is assuming that the cluster location is "zone" when creating Locality for GCP platform.
However, for the GKE regional cluster, it is not true.
Therefore, this PR proposes to use "metadata" server to get the zone, if the cluster location is not zonal.
Change-Id: I27f1b699f7ea464eb43993eb7870ee15f7ffc8ad

@ingwonsong: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

release-notes_istio
564ef7ad86d3cf8786fe0cdbc6ec6c940049520c
link
true
/test release-notes

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

/test release-notes

@ingwonsong: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

gencheck_istio
52f395e4f17914a15095509ab7c5ed6330b3a770
link
true
/test gencheck

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

@ingwonsong: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

gencheck_istio
52f395e4f17914a15095509ab7c5ed6330b3a770
link
true
/test gencheck

unit-tests-arm64_istio
52f395e4f17914a15095509ab7c5ed6330b3a770
link
true
/test unit-tests-arm64

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

@ingwonsong: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

gencheck_istio
52f395e4f17914a15095509ab7c5ed6330b3a770
link
true
/test gencheck

unit-tests-arm64_istio
52f395e4f17914a15095509ab7c5ed6330b3a770
link
true
/test unit-tests-arm64

unit-tests_istio
52f395e4f17914a15095509ab7c5ed6330b3a770
link
true
/test unit-tests

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

I assume this fixes #50379, right?

Actually, it was not, but I realized that it is great to solve the issue together.
Now, Zone is retrieved from metadata server first, and then if it is failed, we are using the cluster location as a fallback.

@ingwonsong: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

unit-tests_istio
52f395e4f17914a15095509ab7c5ed6330b3a770
link
true
/test unit-tests

unit-tests-arm64_istio
85552ffcec272de3e5d21bf059533a244ef3b311
link
true
/test unit-tests-arm64

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

/retest

@ingwonsong: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-ambient_istio
ebac18eb8f09c1b01cc5b965462f91d99d5a8767
link
true
/test integ-ambient

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

Implementation looks fine to me except the two comments above.

@ingwonsong: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-ambient_istio
ebac18eb8f09c1b01cc5b965462f91d99d5a8767
link
true
/test integ-ambient

gencheck_istio
91f4afc7caf1301448217e26345d22c94ecb6fa2
link
true
/test gencheck

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

@ingwonsong: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-ambient_istio
ebac18eb8f09c1b01cc5b965462f91d99d5a8767
link
true
/test integ-ambient

gencheck_istio
91f4afc7caf1301448217e26345d22c94ecb6fa2
link
true
/test gencheck

unit-tests-arm64_istio
91f4afc7caf1301448217e26345d22c94ecb6fa2
link
true
/test unit-tests-arm64

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

@ingwonsong: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-ambient_istio
ebac18eb8f09c1b01cc5b965462f91d99d5a8767
link
true
/test integ-ambient

gencheck_istio
91f4afc7caf1301448217e26345d22c94ecb6fa2
link
true
/test gencheck

unit-tests-arm64_istio
91f4afc7caf1301448217e26345d22c94ecb6fa2
link
true
/test unit-tests-arm64

unit-tests_istio
91f4afc7caf1301448217e26345d22c94ecb6fa2
link
true
/test unit-tests

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

@ingwonsong: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

unit-tests-arm64_istio
d8f67cf330e6544e29fce3e7dcacc34bf9c2d506
link
true
/test unit-tests-arm64

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

/retest


Create Unit test for “What treatment are you receiving...” Page

“What treatment are you receiving...” Page
a) None -navigate to the “Thank you..” Page
b) Oxygen and fluids -navigate to the “Thank you..” Page
c) Non-invasive ventilation -navigate to the “Thank you..” Page
d) Invasive ventilation -navigate to the “Thank you..” Page
e) Other -navigate optional text filed page
f) Other optional text field - done button

Thank you for creating this issue.
We are reviewing our approach to testing + will update the guidance around testing once that is completed.


:))

You came into a slack channel and dumped your link to this repository without reading the topic of the channel. This shows that you are lazy and you have no respect for the people who are there. I hope you have a bad day.

@deoxxa  and @JonRowe, please act like men, if you are :))

Wait, did you just come back two weeks later to say that? lol.

@deoxxa Not really, just wanna check how quick you will react if I call you :)) Actually, quicker than my puppy 👍


Graph Partition API

Description
This PR introduces enhanced Python and C APIs to trigger graph partitioning for a given backend. These APIs provide an option to the user to infer shapes, dtypes and stypes before partitioning. They add the ability to pass optional arguments to subgraph property.
This PR makes the following modifications to subgraph property:

Added the ability for the subgraph property to preprocess the graph and initialize any custom state that is required during partitioning
Added the ability for the subgraph property to post-process the graph and do things like collect statistics on the quality of partitioning.
Enabled subgraph property to reject creating a sub-optimal subgraph. For example, the subgraph property could reject subgraphs with only one operator in it.

We reuse the existing graph partitioning algorithm and control using subgraph property classes. Since we’re modifying a symbol object, we add this API to the Symbol class. Users will call optimize_for on an existing symbol object to create a new partitioned symbol.
Here is an example showing partitioning without args, which means infer shape/type will NOT be called before partitioning.  It is similar to GetBackendSymbol.
import mxnet as mx
sym, args, aux = mx.model.load_checkpoint('resnet-50', 0)
sym = sym.optimize_for('default')
exe = sym.bind(ctx=mx.cpu(), args=args, aux_states=aux, grad_req='null')

Here is an example showing partitioning with args, which means infer shape/type is called before partitioning.
import mxnet as mx
sym, args, aux = mx.model.load_checkpoint('resnet-50', 0)
sym = sym.optimize_for('default', args)
exe = sym.bind(ctx=mx.cpu(), args=args, aux_states=aux, grad_req='null')

Here is an example showing partitioning with kwargs to set a list of ops to be excluded from subgraphs.
import mxnet as mx
sym, args, aux = mx.model.load_checkpoint('resnet-50', 0)
sym = sym.optimize_for('default', args, excluded_ops=['BatchNorm'])
exe = sym.bind(ctx=mx.cpu(), args=args, aux_states=aux, grad_req='null')

Checklist
Essentials
Please feel free to remove inapplicable items for your PR.

[x] Changes are complete (i.e. I finished coding on this PR)
[x] All changes have test coverage:
Unit tests are added for small changes to verify correctness (e.g. adding a new operator)
Nightly tests are added for complicated/long-running ones (e.g. changing distributed kvstore)
Build tests will be added for build configuration changes (e.g. adding a new build option with NCCL)
[x] Code is well-documented:
For user-facing API changes, API doc string has been updated.
For new C++ functions in header files, their functionalities and arguments are documented.
For new examples, README.md is added to explain the what the example does, the source of the dataset, expected performance on test set and reference to the original paper if applicable
Check the API doc at http://mxnet-ci-doc.s3-accelerate.dualstack.amazonaws.com/PR-$PR_ID/$BUILD_ID/index.html
[x] To the my best knowledge, examples are either not affected by this change, or have been fixed to be compatible with this change

@ZhennanQin for review the compatible  :)

What's the difference between sym.partition('default') and sym.get_backend_symbol('default')?

@ZhennanQin Here in this PR we're trying to do the following things:

Clarify the API/function-names. Initially we wanted the API to be called "sym.partition" since we were going to partition the symbol. But given the latest PR that enables multiple subgraph properties to be specified we dropped this idea. Instead, to users the outcome is that they are "optimizing the symbol, for a specific backend". So now we propose the API to be called "optimizeFor" and it will take the name of the backend. So this way it will be much more understandable to users that they are "optimizing the symbol for a specific backend". For example: sym.optimizeFor("TensorRT") or sym.optimizeFor("MKLDNN") or sym.optimizeFor("EIA"). We expect that users could call this more than once for the same model. For example, users could first optimize for EIA (that would group supported nodes into subgraphs) and then optimize for MKLDNN for the remaining nodes that were not partitioned into subgraphs.

We also want to enable users to pass more configuration options directly to the subgraph property to tailor the partitioning. One example is to provide a better experience for users to provide a blacklist (or list of operators to exclude from subgraphs). Another could be setting the minimum number of nodes allowed in a subgraph (ie. 3).

Enable the API to optionally perform shape/type propagation before partitioning. For example, some backends may only support operators if their inputs are a particular type (ie. FP16 or Int8) or shape (2D, 3D, or 4D).

Currently the subgraph properties are state-less. We want to enable the subgraph properties to have a prepartition and postpartition APIs to do setup or cleanup around the actual partitioning call. This could be used to setup a whitelist of supported operators, or pre-analyze the graph before partitioning begins and Select is called on the Selector.

In this PR we want to enable this functionality for users to more easily use partitioning. In a later PR we want to enable subgraph properties to be dynamically loaded from libraries.

@samskalicky Thanks for the explanation, it helps a lot to understand this PR. Basically, I think sym.optimizeFor('MKLDNN') is the same as current sym.get_backend_symbol('MKLDNN'), so I don't see the reason to duplicate it. Maybe we can directly rename get_backend_symbol to optimizeFor?

Basically, I think sym.optimizeFor('MKLDNN') is the same as current sym.get_backend_symbol('MKLDNN'), so I don't see the reason to duplicate it. Maybe we can directly rename get_backend_symbol to optimizeFor?
@ZhennanQin Thanks for your comments, we'll try and clarify our thought process. Apologies for the lack of clarity in this PR. You are correct in the current status of the code that @mseth10 has committed so far today. The PR is still WIP and more changes are coming, lets not make decisions on what is there today.
Instead lets focus on the items i mentioned before (they will get into the PR description before we attempt to merge, I promise! :-D). We will add more arguments to the optimizeFor API in the coming commits. We need to add arguments to enable us to to do shape/type propagation, and we want to accept arbitrary options that we pass to the subgraph property.
These new API changes will not be compatible with the current get_backend_symbol API.

@mseth10 we also need to add the ability to reject creating a subgraph in the buildsubgraph.cc file:
https://github.com/apache/incubator-mxnet/blob/e98fea3165670157090f2a2f644890452443803c/src/operator/subgraph/build_subgraph.cc#L574
We want to enable the subgraph property to return a null node to say reject

@samskalicky @mseth10 As this PR is still WIP, please ping me when this PR is ready to review. I agree with you that we need a more powerful API to put dtype, shape and ctx into consideration to make partition more accurate.

@ZhennanQin ping for review

I guess we have agreements for all my concerns. So LGTM.

@ZhennanQin can you please approve? @mseth10 has added the "Next steps" in the PR description to save the outcome of our discussions from the PR comments.

@mxnet-label-bot remove [pr-awaiting-review]

@mxnet-label-bot add [pr-awaiting-merge]


Dev

looks good

Thank you for your submission! We require that all contributors sign our Contributor License Agreement ("CLA") before we can accept the contribution. Read and sign the agreement
Learn more about why HashiCorp requires a CLA and what the CLA includes

0 out of 2 committers have signed the CLA.

[ ] root
[ ] 2Wdavidcunliffe

root seems not to be a GitHub user.
You need a GitHub account to be able to sign the CLA. If you already have a GitHub account, please add the email address used for this commit to your account.
Have you signed the CLA already but the status is still pending? Recheck it.


Azure compatibility work for LLM engine

Pull Request Summary
Not quite ready but making a PR because there's some overlapping db credential refresh work with Sean
Test Plan and Usage Guide
just _integration_test training passed

is it possible for us to get an integration test environment on Azure?


Fixes for the giraffe sign form

Don't include moui in giraffe in dev
Correct design for checkboxes in giraffe sign form
Make validation text red
Giraffe styles don't need value from state anymore
Use helper methods for setting thirdparty_optin in state

We might want to do more on the design for validation. Would be nice to not stray too far from legacy though. cc @sandramchung ?
Also we may want to re-test things like collect_volunteers or thirdparty_optin before launching. I'm not sure if that's part of QA?


Different way to add project or data map config in yml

Here is example of adding cayenne-project and datamap in one config:
cayenne:
  createSchema: true
  datasource: defaultds
  configs:
    - cayenne-project1.xml
  maps:
    - location: classpath:dm1.map.xml
      name: map1
      datasource: ds1

To add map we need to set location as classpath:dm1.map.xml
To add project we need to set as cayenne-project1.xml without classpath:
But there are both in the same directory.
We should make common pattern of adding projects or datamap.

This looks like a duplicate of #17. I am all for doing this, but my concern is about backwards compatibility. I don't see an easy way to deprecate the old format gradually, as ResourceFactory URL format also supports URLs without a "protocol" part, that are resolved as files on the file system.
So perhaps this is a 2.0 change.

Closing as a duplicate of #17.


UI/UX enhancement for GA charts

show unique users instead of numbers of visits (or add a toggle to switch datasets?)
enhance legends on smaller screens
https://g0v-tw.slack.com/archives/C2PPMRQGP/p1599708004074400

Related discussion
https://g0v.hackmd.io/yEp9JJtHSyK18bxCQV4dUg#Analytics

TODO:

show aggregated webUser/lineUser stats instead of webVisit/lineVisit
move the description in the legend labels (i.e. web visit/line inquiry) to tooltips and leave only the color coded numbers (theme.palette.info.main for web, theme.palette.primary.main for chatbot)
apply the color coding to distinguish web visit and line inquiry in the tooltip shown when hovering over a certain date on the chart
replace visits with users as see fit


Property-manager CLI requires ~/.edgerc to exist, even when --edgerc parameter is used

The CLI requires ~/.edgerc to exist, even when --edgerc parameter is used to specify a different edgerc location
For example, the below command fails when there is no file present at ~/.edgerc, even though an alternate file is used by the command.
akamai property-manager  activate-version -p my_property --network staging --message 'testing' --edgerc ./myAlternateEdgeRc
The error received is:
PM CLI Error: 'missing_edgegrid_credentials' occurred:
 Can't find edgerc config. Either '/Users/username/.edgerc' or '/Users/username/currentworkingdirectory/edgerc.config' must exist

Creating an empty file at /Users/username/.edgerc or /Users/username/currentworkingdirectory/edgerc.config allows the command to succeed
This is especially impactful when a Jenkins server is using the Jenkins secrets store to manage credentials.  In this case, the ~/.edgerc file does not exist.  Instead, a different file path is generated automatically, and the Jenkins job may not have permissions to create the file at ~/.edgerc.

Josh thanks for the feedback.  Our team has reproduced this issue as well and are working on a fix.

Josh, we tried to reproduce this issue again; We couldn't. The first time when we tried, we had misspelled the "edgerc" file name (which resulted in using a non-existent file) and got the same error you have got here, but when we corrected this we did not get any errors. Can you give us your steps to reproduce the error?
Thank you

@SidHeg We are facing a similar issue when we try to merge the template files.
For example, we expeect the below command to merge the files and NOT to validate it with backend schema.
akamai pipeline merge -n -p www test
However, it errors out with: Can't find edgerc config.
This used to work perfectly fine with older releases.

@SidHeg We are facing a similar issue when we try to merge the template files.
For example, we expeect the below command to merge the files and NOT to validate it with backend schema.
akamai pipeline merge -n -p www test
However, it errors out with: Can't find edgerc config.
This used to work perfectly fine with older releases.


Deal with some style comments hanging over from PR 1043

The PR was merged before we got the chance to deal with https://github.com/alphagov/frontend/pull/1043#discussion_r88240341 and https://github.com/alphagov/frontend/pull/1043#discussion_r88241206. They're
tiny, but so they don't hang around forever, I'm fixing them now.
The answer_controller.rb change was a copy/paste, so fix it at source as well in help_controller.rb.

Welcome back @fofr! ⭐


Weights

When will the weights be available?

Thank you for your attention.
We are finalizing the draft of the technical report and the model weights will be online together with the technical report, hopefully by the end of Friday.

@danil31219as The weights are now available at: https://huggingface.co/DAMO-NLP-SG/VideoLLaMA2-7B .

Hi, what is the difference between Base and Chat weights?

Base refers to the model pre-trained with large-scale caption-only data (i.e., the first-stage model) while Chat model is further fine-tuned from Base model (i.e., the second-stage model).


Schema validation of Data61 apis

Hypothesis
Need a recommended method to validate the banking and common api responses against the cds standards
Description
So far we have been using the docker client-cli image (tag 1.0.0) to help us validate the output of banking and common apis.
https://hub.docker.com/layers/consumerdatastandardsaustralia/client-cli/1.0.0-SNAPSHOT/images/sha256-79bc56af90303c8dc502891f9402c839558b73966fc1e11e526ca0dd9cec8bd9?context=explore
We are noticing that the later versions of this docker image are not being consistent in flagging if the API response is conformant to the standards.
Available Options
We would like to know what is the recommended way to run a schema validation of our API output using the artefacts that are being built for consumer data standards.

@swetaiyer You could use our postman collection found  here. There is some documentation in there how to use it.

This is great! Thank you for sharing the info :)


feat: add github action

I have done some work on bringing github action on current project. In the process of that, I also found some  problems.
First, the test on low version node is not supported now (https://github.com/yunnysunny/superagent/runs/4895023400). Since we use a newest  version of eslint (8.3.0 in fact), it will emit an error when we run it on node 10.x :
Oops! Something went wrong! :(

ESLint: 8.6.0

TypeError: Module.createRequire is not a function
    at Object.<anonymous> (/home/runner/work/superagent/superagent/node_modules/@eslint/eslintrc/dist/eslintrc.cjs:2359:26)
    at Module._compile (/home/runner/work/superagent/superagent/node_modules/v8-compile-cache/v8-compile-cache.js:192:30)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:789:10)
    at Module.load (internal/modules/cjs/loader.js:653:32)
    at tryModuleLoad (internal/modules/cjs/loader.js:593:12)
    at Function.Module._load (internal/modules/cjs/loader.js:585:3)
    at Module.require (internal/modules/cjs/loader.js:692:17)
    at require (/home/runner/work/superagent/superagent/node_modules/v8-compile-cache/v8-compile-cache.js:159:20)
    at Object.<anonymous> (/home/runner/work/superagent/superagent/node_modules/eslint/lib/cli-engine/cli-engine.js:33:5)
    at Module._compile (/home/runner/work/superagent/superagent/node_modules/v8-compile-cache/v8-compile-cache.js:192:30)

We have to reduce the version of eslint , or skip the lint for node 10 , which needs an refactor of our ci code.
Second, the test of browsers failed with such error (https://github.com/yunnysunny/superagent/runs/4895413544):
SAUCE_APPIUM_VERSION=1.7 ./node_modules/.bin/zuul -- test/*.js test/client/*.js
(node:2010) [DEP0022] DeprecationWarning: os.tmpDir() is deprecated. Use os.tmpdir() instead.
- testing: chrome @ Mac 11: 97
- testing: firefox @ Mac 10.12: 96
- testing: safari @ Mac 12: 15
- testing: internet explorer @ Windows 2008: 9 10 11
- restarting: <safari 15 on Mac 12>
- restarting: <internet explorer 10 on Windows 2008>
- restarting: <chrome 97 on Mac 11>
- restarting: <firefox 96 on Mac 10.12>
- restarting: <internet explorer 9 on Windows 2008>
- restarting: <internet explorer 10 on Windows 2008>
- restarting: <chrome 97 on Mac 11>
- restarting: <safari 15 on Mac 12>
- restarting: <firefox 96 on Mac 10.12>
- restarting: <internet explorer 9 on Windows 2008>
- restarting: <chrome 97 on Mac 11>
- restarting: <internet explorer 10 on Windows 2008>
- restarting: <chrome 97 on Mac 11>
- restarting: <internet explorer 10 on Windows 2008>
- restarting: <safari 15 on Mac 12>
- restarting: <chrome 97 on Mac 11>
- restarting: <internet explorer 10 on Windows 2008>
- restarting: <firefox 96 on Mac 10.12>
- restarting: <internet explorer 9 on Windows 2008>
- restarting: <safari 15 on Mac 12>
- restarting: <chrome 97 on Mac 11>
- restarting: <internet explorer 10 on Windows 2008>
- restarting: <internet explorer 9 on Windows 2008>
- restarting: <safari 15 on Mac 12>
- failed: <internet explorer 11 on Windows 2008> (0 failed, 0 passed)
- restarting: <internet explorer 9 on Windows 2008>
- failed: <chrome 97 on Mac 11> (0 failed, 0 passed)

/home/runner/work/superagent/superagent/node_modules/zuul/bin/zuul:332
            throw err.message;
            ^
internet explorer@10: localtunnel server returned an error, please try again
(Use `node --trace-uncaught ...` to show where the exception was thrown)

I'm not familiar with zuul, and have no idea what happened.
Third, the test on http2 also failed(https://github.com/yunnysunny/superagent/runs/4895023445). It showed many errors , all of them with same reason, this is an example :
  1) request
       persistent agent
         should gain a session on POST:
     Uncaught Error [ERR_HTTP2_STREAM_ERROR]: Stream closed with error code NGHTTP2_PROTOCOL_ERROR
      at ClientHttp2Stream._destroy (internal/http2/core.js:2212:13)
      at ClientHttp2Stream.destroy (internal/streams/destroy.js:38:8)
      at Http2Stream.onStreamClose (internal/http2/core.js:518:12)

For the problems above, I drop the test of low version nodes, browsers, and http in the github action's yml.

Is this good to merge?

Yes. All the unsupported tests mentioned above have been ignored. It will show green status after run tests.

I think it's important to merge this request, since current project doesn't have an autotest flow. When another new pull request is been merged, we can't distingish whether it's ok.

v7.1.2 released https://github.com/visionmedia/superagent/releases/tag/v7.1.2

I find some error in ci, when test on node 14, a case was failed:
  1) req.query(Object)
       query-string should be sent on pipe:
     Error: Timeout of 5000ms exceeded. For async tests and hooks, ensure "done()" is called; if returning a Promise, ensure it resolves. (/home/runner/work/superagent/superagent/test/node/query.js)
      at listOnTimeout (internal/timers.js:557:17)
      at processTimers (internal/timers.js:500:7)

https://github.com/visionmedia/superagent/runs/5730870741?check_suite_focus=true

I re-ran the failed build on node v14 in GitHub CI and it failed again, so I will unpublish in the interim until you confirm it is OK or submit a PR to fix

It would be beneficial to move the SAUCE_USERNAME and SAUCE_ACCESS_KEY to use github secrets for the project, then they can be referenced simply as ${{ secrets.SAUCE_ACCESS_KEY}} in the actions file and not directly be part of source.
Not sure if this had been discussed before, but just noted it while reviewing upgrades 7.1.1 -> 7.1.2

The test on browser failed with error message about zuul. I'm not familiar with it, so I just skip the test on browser in CI.

https://github.com/visionmedia/superagent/pull/1716

I re-ran the failed build on node v14 in GitHub CI and it failed again, so I will unpublish in the interim until you confirm it is OK or submit a PR to fix

Try to fix it https://github.com/visionmedia/superagent/pull/1716

@yunnysunny pending results of https://github.com/visionmedia/superagent/actions/runs/2185564459, please follow up if we forget to version bump if successful

Is this package still deprecated ? Looks like this PR has been merged in?

@yunnysunny pending results of https://github.com/visionmedia/superagent/actions/runs/2185564459, please follow up if we forget to version bump if successful

The action has passed. We can merge the request https://github.com/visionmedia/superagent/pull/1717 next.

The test on Node 10 has been fixed with https://github.com/visionmedia/superagent/pull/1722

The test with http2 has been fixed with https://github.com/visionmedia/superagent/pull/1723


Can't install Pycuda

Every time i try to install pycuda it just outputs this:
              ############################
              # Package would be ignored #
              ############################
              Python recognizes 'pycuda.cuda' as an importable package[^1],
              but it is absent from setuptools' `packages` configuration.

              This leads to an ambiguous overall configuration. If you want to distribute this
              package, please make sure that 'pycuda.cuda' is explicitly added
              to the `packages` configuration field.

              Alternatively, you can also rely on setuptools' discovery methods
              (for example by using `find_namespace_packages(...)`/`find_namespace:`
              instead of `find_packages(...)`/`find:`).

              You can read more about "package discovery" on setuptools documentation page:

              - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html

              If you don't want 'pycuda.cuda' to be distributed and are
              already explicitly excluding 'pycuda.cuda' via
              `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
              you can try to use `exclude_package_data`, or `include-package-data=False` in
              combination with a more fine grained `package-data` configuration.

              You can read more about "package data files" on setuptools documentation page:

              - https://setuptools.pypa.io/en/latest/userguide/datafiles.html

              [^1]: For Python, any directory (with suitable naming) can be imported,
                    even if it does not contain any `.py` files.
                    On the other hand, currently there is no concept of package data
                    directory, all directories are treated like packages.
              ********************************************************************************

I have tried updating wheel, pip and other things but nothing helped. am i missing something?

Having the same or a similar problem, my log starts like this:
venv "C:\programs\stable-diffusion-webui_RT\venv\Scripts\Python.exe"
Python 3.10.6 (tags/v3.10.6:9c7b4bd, Aug  1 2022, 21:53:49) [MSC v.1932 64 bit (AMD64)]
Version: v1.3.0-72-gb957dcfe
Commit hash: b957dcfece29c84ac0cfcd5a69475ff8684c531f
Installing requirements
Error running install.py for extension C:\programs\stable-diffusion-webui_RT\extensions\stable-diffusion-webui-tensorrt.
Command: "C:\programs\stable-diffusion-webui_RT\venv\Scripts\python.exe" "C:\programs\stable-diffusion-webui_RT\extensions\stable-diffusion-webui-tensorrt\install.py"
Error code: 1
stdout: Installing pycuda
stderr: Traceback (most recent call last):
File "C:\programs\stable-diffusion-webui_RT\extensions\stable-diffusion-webui-tensorrt\install.py", line 30, in
install()
File "C:\programs\stable-diffusion-webui_RT\extensions\stable-diffusion-webui-tensorrt\install.py", line 23, in install
launch.run_pip(f'install pycuda', "pycuda")
File "C:\programs\stable-diffusion-webui_RT\modules\launch_utils.py", line 124, in run_pip
return run(f'"{python}" -m pip {command} --prefer-binary{index_url_line}', desc=f"Installing {desc}", errdesc=f"Couldn't install {desc}", live=live)
File "C:\programs\stable-diffusion-webui_RT\modules\launch_utils.py", line 101, in run
raise RuntimeError("\n".join(error_bits))
RuntimeError: Couldn't install pycuda.
Command: "C:\programs\stable-diffusion-webui_RT\venv\Scripts\python.exe" -m pip install pycuda --prefer-binary
Error code: 1
stdout: Collecting pycuda
Using cached pycuda-2022.2.2.tar.gz (1.7 MB)
Installing build dependencies: started
Installing build dependencies: finished with status 'done'
Getting requirements to build wheel: started
Getting requirements to build wheel: finished with status 'done'
Preparing metadata (pyproject.toml): started
Preparing metadata (pyproject.toml): finished with status 'done'
Collecting mako
Using cached Mako-1.2.4-py3-none-any.whl (78 kB)
Collecting appdirs>=1.4.0
Using cached appdirs-1.4.4-py2.py3-none-any.whl (9.6 kB)
Collecting pytools>=2011.2
Using cached pytools-2014.2-py2.py3-none-any.whl (51 kB)
Collecting decorator>=3.2.0
Using cached decorator-5.1.1-py3-none-any.whl (9.1 kB)
Requirement already satisfied: MarkupSafe>=0.9.2 in c:\programs\stable-diffusion-webui_rt\venv\lib\site-packages (from mako->pycuda) (2.1.2)
Building wheels for collected packages: pycuda
Building wheel for pycuda (pyproject.toml): started
Building wheel for pycuda (pyproject.toml): finished with status 'error'
Failed to build pycuda
stderr:   error: subprocess-exited-with-error
Building wheel for pycuda (pyproject.toml) did not run successfully.
exit code: 1

Contrary to the readme, it seems you do need cuda toolkit installed for pycuda.

I think this kind of worked but now i get error:
Error loading script: trt.py
Traceback (most recent call last):
  File "C:\Software\stable-diffusion-webui\beta\stable-diffusion-webui\modules\scripts.py", line 263, in load_scripts
    script_module = script_loading.load_module(scriptfile.path)
  File "C:\Software\stable-diffusion-webui\beta\stable-diffusion-webui\modules\script_loading.py", line 10, in load_module
    module_spec.loader.exec_module(module)
  File "<frozen importlib._bootstrap_external>", line 883, in exec_module
  File "<frozen importlib._bootstrap>", line 241, in _call_with_frames_removed
  File "C:\Software\stable-diffusion-webui\beta\stable-diffusion-webui\extensions\stable-diffusion-webui-tensorrt\scripts\trt.py", line 11, in <module>
    import pycuda.driver as cuda
ModuleNotFoundError: No module named 'pycuda.driver'

Ok i just removed pycuda and let it reinstall itself and now it works. Thanks to @merc4derp, it really jut was the toolkit

If I may ask: Where exactly did you remove pycuda?


Disabling favicons for external links doesn't work

Info:

OS: Windows 10+11
Logseq ver: 0.8.8
Plugin ver: 1.5.1
[y ] ⚠ Do i have issue with DISABLED my custom.css?

Description:
Show site favicon for external links? deselect doesn't work
To Reproduce:
deselect Show site favicon for external links? and paste a link that has a favicon
Expected behavior:
No external icon shown and no outgoing requests to favicons.
When you're behind an external logging firewall you maybe don't want to all those requests going out revealing every base URL of a link you have on a page to that firewall.
Screenshots

do you have issue after Logseq restart?

check latest release!

works! Thanks :)


qmmp: 1.2.0 -> 1.2.1

Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools.
This update was made based on information from https://repology.org/metapackage/qmmp/versions.
These checks were done:

built on NixOS
Warning: no binary found that responded to help or version flags. (This warning appears even if the package isn't expected to have binaries.)
found 1.2.1 with grep in /nix/store/bdsg5rzda3rj5k535f56rkbjwsqy4h07-qmmp-1.2.1
directory tree listing: https://gist.github.com/fed0e3b824b6157facab85accd329d15

cc @bjornfor for review

No attempt on x86_64-darwin (full log)
The following builds were skipped because they don't evaluate on x86_64-darwin: qmmp
Partial log (click to expand)

a) For `nixos-rebuild` you can set
  { nixpkgs.config.allowUnsupportedSystem = true; }
in configuration.nix to override this.

b) For `nix-env`, `nix-build`, `nix-shell` or any other Nix command you can add
  { allowUnsupportedSystem = true; }
to ~/.config/nixpkgs/config.nix.

Success on x86_64-linux (full log)
Attempted: qmmp
Partial log (click to expand)
shrinking /nix/store/gn2mclnj21wfyghijk0p8zq7kj30dn4c-qmmp-1.2.1/lib/qmmp/Transports/libmms.so
shrinking /nix/store/gn2mclnj21wfyghijk0p8zq7kj30dn4c-qmmp-1.2.1/lib/qmmp/Engines/libmplayer.so
shrinking /nix/store/gn2mclnj21wfyghijk0p8zq7kj30dn4c-qmmp-1.2.1/lib/qmmp/Ui/libskinned.so
shrinking /nix/store/gn2mclnj21wfyghijk0p8zq7kj30dn4c-qmmp-1.2.1/lib/qmmp/Ui/libqsui.so
shrinking /nix/store/gn2mclnj21wfyghijk0p8zq7kj30dn4c-qmmp-1.2.1/bin/qmmp
strip is /nix/store/j75dgadrff2d1fyc4fczmcgqkid2imdx-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/gn2mclnj21wfyghijk0p8zq7kj30dn4c-qmmp-1.2.1/lib  /nix/store/gn2mclnj21wfyghijk0p8zq7kj30dn4c-qmmp-1.2.1/bin
patching script interpreter paths in /nix/store/gn2mclnj21wfyghijk0p8zq7kj30dn4c-qmmp-1.2.1
checking for references to /build in /nix/store/gn2mclnj21wfyghijk0p8zq7kj30dn4c-qmmp-1.2.1...
postPatchMkspecs


fix(CI/CD) : fix failing chrome installation

[ ] What does this PR do? [Mandatory]
Chrome installation on CentOS is failing beacuse chrome stable channel is down.
This PR adds chrome beta channel which will fix the issue.
[ ] What issue/task does this PR references? [Mandatory]

[ ] Are the tests Included? [Mandatory]

@Raunak1203 Your image is available in the registry. Run docker pull registry.devshift.net/fabric8-ui/fabric8-planner:SNAPSHOT-PR-2598 && docker run -it -p 5000:8080 registry.devshift.net/fabric8-ui/fabric8-planner:SNAPSHOT-PR-2598 and visit http://localhost:5000 to access it.


Problem using inchjs . "Parsing failed."

Hi.
I am beginner in node js and want to use this module for jsdoc code coverage measurement.
It was used for this jsdoc
/**
 * @summary ثبت نام یک سامانه
 * @param {!Object} request.data
 * @param {!String} request.data.username
 * @param {!String} request.data.password
 * @param {!Object} request.headers
 * @param {!String} request.headers.user
 * @return {undefined}
 */

and run in command line with "inches ... .js" but return " [InchJS] Parsing failed.".
Do you know what caused this problem?

@rrrene

If you are using Windows, this is a problem. because the jsdoc folder could not be found inside the nodemodules
This is a bug from the inchjs module. If you test with Linux operating system, there is no problem.
@sahapina

in jsdoc_runner.js  we have a getJSDocCommand  function .  this function return the command for find jsdoc module. but this funtion has a problem in line that do  var out = sh.exec(finder).output . the value out is  FIND: Parameter format not correct