Can not pull or push to User-Cert protected remote Git

Issue Type: Bug
Steps to reproduce

Have a git respitory which is hosted on a user cert protected environment
have an entry in the gitconfig file:

	sslCert = "<path_to_folder>/crt.pem"
	sslKey = "<path_to_folder>/key.pem"
	sslCertPasswordProtected = true

try to push and pull
results in

git pull --tags origin master
Missing or invalid credentials.
Error: Bad status code: 500
    at ClientRequest.<anonymous> (/Applications/Visual Studio Code.app/Contents/Resources/app/extensions/git/dist/askpass-main.js:1:2250)
    at Object.onceWrapper (events.js:291:20)
    at ClientRequest.emit (events.js:203:13)
    at HTTPParser.parserOnIncomingClient [as onIncoming] (_http_client.js:575:27)
    at HTTPParser.parserOnHeadersComplete (_http_common.js:116:17)
    at Socket.socketOnData (_http_client.js:449:22)
    at Socket.emit (events.js:203:13)
    at addChunk (_stream_readable.js:295:12)
    at readableAddChunk (_stream_readable.js:276:11)
    at Socket.Readable.push (_stream_readable.js:210:10)
fatal: unable to access 'https://git.host.com/some/repo.git/': unable to set private key file: '<path_to_folder>/key.pem' type PEM

(v1.45.1)
fatal: unable to access 'https://git.host.com/some/repo.git/': unable to set private key file: '<path_to_folder>/key.pem' type PEM

(v1.44.2)
Prio to Version 1.44 this worked without a problem. It still works in a normal console, but it's rather tedious not to be able to do it from within vscode.
I've tried restarting vscode without all extensions, but the error still persists.
If i downgrade to v1.43.2 it works again.
VS Code version: Code 1.45.1 (5763d909d5f12fe19f215cbfdd29a91c0fa9208a, 2020-05-14T08:33:47.663Z)
OS version: Darwin x64 19.2.0

System Info

Item
Value

CPUs
Intel(R) Core(TM) i7-8850H CPU @ 2.60GHz (12 x 2600)

GPU Status
2d_canvas: enabledflash_3d: enabledflash_stage3d: enabledflash_stage3d_baseline: enabledgpu_compositing: enabledmetal: disabled_offmultiple_raster_threads: enabled_onoop_rasterization: disabled_offprotected_video_decode: unavailable_offrasterization: enabledskia_renderer: disabled_off_okvideo_decode: enabledviz_display_compositor: enabled_onviz_hit_test_surface_layer: disabled_off_okwebgl: enabledwebgl2: enabled

Load (avg)
2, 2, 2

Memory (System)
16.00GB (0.57GB free)

Process Argv
--disable-extensions

Screen Reader
no

VM
0%

Extensions disabled

Still happens with VSCode Version: 1.46.1 (cd9ea6488829f560dc949a8b2fb789f3cdc05f5d, 2020-06-17T21:17:14.222Z)
Git Version is 2.27.0

This is fixed if Terminal Authentication for Extensions -> Git is set to false. Default is true.
Still weird why this was not an issue before version 1.44.
Should this issue be closed because of this? @joaomoreno

Yes, if you use certificate authentication with HTTPS, you need to disable the Terminal Auth. 👍

@joaomoreno Alright. But this is not documented and worked without this setting before 1.44. Furthermore, the visual GIT-Client (not in the integrated Terminal) still produces this error, even with the setting set to false.
This both worked prior to Version 1.44.x ...

You can also disable the github.gitAuthentication setting and that should get the visual git client working again.

You can also disable the github.gitAuthentication setting and that should get the visual git client working again.

This does not seem to fix it. I still get the "Missing or invalid credentials" error (immediatly after trying to pull something), with the same error as above.
Error: Bad status code: 500
    at ClientRequest.<anonymous> (/Applications/Visual Studio Code.app/Contents/Resources/app/extensions/git/dist/askpass-main.js:1:2250)
    at Object.onceWrapper (events.js:291:20)
    at ClientRequest.emit (events.js:203:13)
    at HTTPParser.parserOnIncomingClient [as onIncoming] (_http_client.js:575:27)
    at HTTPParser.parserOnHeadersComplete (_http_common.js:116:17)
    at Socket.socketOnData (_http_client.js:449:22)
    at Socket.emit (events.js:203:13)
    at addChunk (_stream_readable.js:295:12)
    at readableAddChunk (_stream_readable.js:276:11)
    at Socket.Readable.push (_stream_readable.js:210:10)
fatal: unable to access 'https://git.host.com/some/repo.git/': unable to set private key file: '/<PATH_TO_FILE>/key.pem' type PEM```

That's odd 🤔 Maybe github.gitAuthentication requires a VS Code restart? Does it work if you restart VS Code after changing that setting?

That's odd 🤔 Maybe github.gitAuthentication requires a VS Code restart? Does it work if you restart VS Code after changing that setting?

Sorry for the late reply @joaomoreno :
no, it doesn't change anything :( i still get the same error as above.
it doesn't bother me as much, as i'm not regularly using it


obsolete GO:0042801 polo kinase kinase activity/ gene product specific

just spotted this term.
It doesn't seem appropriate, especiallt as we don't have a term "polo kinase activity",
and since it only has one EXP annotation it hasn't been used for the majority of "polo kinase kinases".
Could this be obsoleted to prevent annotation inconsistency.

I think then with only one annotation, we can forgo the need for an obsoletion alert. Do  you agree @ukemi ?

Wait; I'm seeing more than just one EXP in Amigo

I only see 2 in QuickGO:
http://www.ebi.ac.uk/QuickGO/GTerm?id=GO:0042801#term=annotation
I think an obsoletion  notice is always good, might educate curators not
to request gene product specific terms...
On 10/03/2017 15:44, Harold Drabkin wrote:

Wait; I'm seeing more than just one EXP in Amigo
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/geneontology/go-ontology/issues/13145#issuecomment-285702644,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AHBLKJF6Yq8UiYbRt8sZf9dzEyEvE_7wks5rkW_mgaJpZM4MZHZU.

--
University of Cambridge
PomBase http://www.pombase.org/
Cambridge Systems Biology Centre http://www.sysbiol.cam.ac.uk/Investigators/val-wood

Yes, I DO see these two; neither EXP:
I will send out the notice.
UniProtKB:O94804	Serine/threonine-protein kinase 10		GO:0042801		UniProt	NCBITaxon:9606	TAS		PANTHER:PTHR24361		PMID:12639966	20110902
UniProtKB:B7ZR30	Serine/threonine-protein kinase 10-A		GO:0042801		UniProt	NCBITaxon:8355	IDA				PMID:9831560	20110902

Obsoleted


Arg-completer respect namespaces?

tl;dr:
using an alias, importing foo:bar as f:bar via use foo f will result in edit:completion:arg-completer[foo:bar] not running, and instead calling edit:completion:arg-completer[f:bar].
I'm writing a elvish library for xbps, and have a file, ~/.elvish/lib/xbps.elv.  This is convenient, as all the commands are now very quick to type. However, in xbps.elv, I want to define an arg-completer. It seems that for a function foo, to work in my shell, I have to write edit:completion:arg-completer[x:foo]. edit:completion:arg-completer[xbps:foo] and edit:completion:arg-completer[foo] do not work. The arg-completer code is in xbps.elv.
Is there a way to write argument completion that survives a import alias?

I can't speak to whether the arg-completer should automatically recognize x:foo as an alias for xbps:foo but note that for interactive use you can use the recently introduced edit:add-var to define foo as an interactive alias for xbps:foo. So one solution is to use foo in the arg-completer definition and edit:add-var foo~ $xbps:foo~ to put the command in the interactive namespace.

It would be interesting if there was a way, within the module, to know the name/alias with which it is being loaded. Then the completer definitions could be set automatically using the correct names.
As a workaround, you can do the mapping by hand after loading the module. For example, for the epm: completions:
[~]|> use epm e
[~]|> keys $edit:completion:arg-completer | each [k]{
        if (str:has-prefix $k epm:) {
          edit:completion:arg-completer[(str:replace epm: e: $k)] = $edit:completion:arg-completer[$k]
        }
      }

@krader1961 's solution is a good one, I was unaware of the update. Closing this issue.


Get route from string pattern...

Thank you so much for this library, its so awesome work!
My question:
I create routing...
const api_routes = createRouting({
  entity: {
    ...segment`entity`,
    children: {
      show: {
        ...segment`/show/${arg("uuid")}`,
      }
    },
  },
});

then attach it to controller with nestjs lib
@Controller()
export class HtmlController {
  @Get(api_routes.entity.show.pattern)
  async entity_show(){...}
}

then tests... can inspect and receive what patters?
const ctrl_path = Reflect.getMetadata(PATH_METADATA, HtmlController.prototype.entity_show)
const route_by_path = QUESTION_FN(ctrl_path);
const response = await request(app.getHttpServer())
   .get(route_by_path({ :uuid: "my test value"}))

I would like to match string from controler => api_routes specyfic route
get autocomplete of :uuid argument (or other arguments if they applied to route)

@konowrockis  do you think it is feasible at the moment?

Closing due to inactivity


Add localStorage

Re: https://github.com/Project-OSRM/osrm-frontend-v2/issues/108, storage baselayer and small components user selections.
/cc @tristen @TheMarex

tracking here https://github.com/Project-OSRM/osrm-frontend-v2/pull/119


Add Godoc to README

thanks for this! ❤
clearly we need better notifications set up for this repo. sorry for the bad PR hygiene. I'll make sure PRs/comments are hooked up to our dev channel in Slack


[Help]: When performing the sbas.plot_scenes (AOI) operation, there is a deviation between the SLC image and the image selected by ASF

Describe the problem you met
When performing the sbas.plot_scenes (AOI) operation, there is a deviation between the SLC image and the image selected by ASF
OS and software version
If applicable, what operating system and software version you are using?
OS: Colab
GMTSAR version:
Reproduce the problem
“GasteinValley_weighted_v2_200days_80%“，Follow your steps, when previewing the image before Reframe Scenes (Optional), the size of the SLC image is different from the preview in ASF
Log file
[ 109.8794, 25.8309 ]；
[ 110.0766, 24.7612 ]；
[ 110.947, 25.0326  ]；
[ 111.1918, 25.8248 ]；
[ 111.0354, 26.0816 ]；
[ 109.8794, 25.8309 ]；
Here is my selected range
Screenshot
If applicable, attach a Screenshot to help us understand your case

[Please note that if no new responses are made over six months from users, the issue will get closed]
[Also if this is a general question that's not particlarly related to GMTSAR, such as "how to correct atmospheric noise" or "how to intepret my interferogram", consider using the discussions page]

Sentinel-1 scene includes 3 subswaths, but you selected the only one. It seems you need all the 3 to cover your area.

Sentinel-1 scene includes 3 subswaths, but you selected the only one. It seems you need all the 3 to cover your area.
Thank you very much for your help. After adjustment, the research area can now be included

Sentinel-1 scene includes 3 subswaths, but you selected the only one. It seems you need all the 3 to cover your area.

Thank you very much for your help. After adjustment, the research area can now be included


Support watching multiple files

Description
My typst code is very complicated so I have both a main document and a unit-test-like document.
I would like to be able to run typst watch main.typ tests.typ
Use Case
This is useful when sharing typst modules between projects.

You can try having a third file combined.typ with just
#include "main.typ"
#include "tests.typ"

and then run typst watch combined.typ. It automatically watches all files you depend on.

Awesome idea but unfortunately this doesn't work because both files call a #set document(...) — the main book because of its metadata, and the tests because they need to set date: none for deterministic/reproducible results.
error: document set rules must appear before any content

After more experimentation, no unfortunately this doesn't work.
Reproduction:
// This is all.typ
#include "main.typ"
#include "test.typ"

// This is main.typ
#import "backend.typ" as backend: *
#hello

// This is test.typ
#import "backend.typ" as backend: *
#hello

// This is backend.typ
#let hello = "HELLO"

Firstly, running typst watch all.typ once and killing after one round, creates only one pdf:
> typst watch all.typ
watching all.typ
writing to all.pdf

[16:10:21] compiled successfully in 5.02ms
^C

> ls -l
total 56
-rw-------@ 1 golly  staff  10969 13 Oct 16:10 all.pdf
-rw-------@ 1 golly  staff     60 13 Oct 16:09 all.typ
-rw-------@ 1 golly  staff     45 13 Oct 16:09 backend.typ
-rw-------@ 1 golly  staff     64 13 Oct 16:09 main.typ
-rw-------@ 1 golly  staff     64 13 Oct 16:09 test.typ

Secondly, when watch is running and I modify backend.typ, it again only updates all.pdf. I expect it to generate main.pdf and test.pdf too.
> ls -l
total 56
-rw-------@ 1 golly  staff  11148 13 Oct 16:13 all.pdf
-rw-------@ 1 golly  staff     60 13 Oct 16:09 all.typ
-rw-------@ 1 golly  staff     47 13 Oct 16:13 backend.typ
-rw-------@ 1 golly  staff     64 13 Oct 16:09 main.typ
-rw-------@ 1 golly  staff     64 13 Oct 16:09 test.typ

You can run typst watch separately for each document in separate terminal tabs/windows

That has its own problems, especially on a laptop with a tiny screen.


decouple client certificates from authentication

This allows the usage of client certificates to be independent of
authentication.  It is possible that the usage of client certificates
eliminate the need for any authentication, or that they provide
other benifits.
This patch restructures the incoming and outgoing server setup pages
so that client certificates can be set as long as the connection uses
TLS/SSL.  If the user chooses client certificates for authentication
it will prompt for certificate only if there isn't one already set.
Mixing password and client certificates works, and this builds upon
other work that allows these settings to coexist in the imap/smtpURI.
This also give the certificate spinner a little more polish.

label looks like other labels
some indentation
the cancel button only appears if there is something to cancel

Happy to get feedback.  I reviewed the other attempts at this, and the only thing
that this lacks is the ability to use auth external without tls/ssl, which I could
implement, but I don't think there's a valid use case for that.
This PR requires a new decoder/encoder that can full persist these serversettings, as
the old uri format isn't up for the job.  I'm happy to help coding a the new encoder/decoder
as well as a preference migrations routine if that help is desired.

Nice :+1:
Can you please rebase on main and also update AccountSetupBasics to allow specifying a password and using a client certificate at the same time?

done.  let me know if you want me to flatten the commits.

Thanks :+1:


service providers, consumers datas are displayed

Services providers,consumers data's are displayed.
Language changes are implemented.

Coverage increased (+0.07%) to 71.646% when pulling 0f8f7982645c4b4b08b947592ac3c44c5318363e on vibakar:master into a80b8c3e80cb58f1f0afae8e9b49d43f109b1e81 on ServiceComb:master.

Codecov Report

Merging #91 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master      #91   +/-   ##
=======================================
  Coverage   67.32%   67.32%
=======================================
  Files          18       18
  Lines        3936     3936
=======================================
  Hits         2650     2650
  Misses       1128     1128
  Partials      158      158

Impacted Files
Coverage Δ

server/service/rule.go
71.51% <0%> (-0.3%)
:arrow_down:

server/service/instances.go
66.75% <0%> (+0.13%)
:arrow_up:

Continue to review full report at Codecov.

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

changes done

Coverage decreased (-0.07%) to 71.512% when pulling 38f33b0be21141a06d480b8c9a81ae2f874e2f25 on vibakar:master into a80b8c3e80cb58f1f0afae8e9b49d43f109b1e81 on ServiceComb:master.


Plugin not processing

Hello,
I'm running into a problem: I recently wanted to compress my JS files so I installed the plugin. Apparently, it's not working for some reason (same thing with brunch-clean-css). Could you please open my eyes on what I am doing wrong, please?
Here is my package.json
{
  "dependencies": {
    "javascript-brunch": "1.7.1",
    "css-brunch": "1.7.0",
    "coffee-script-brunch": "1.8.0",
    "stylus-brunch": "1.8.0",
    "jade-brunch": "1.8.1",
    "uglify-js-brunch": "1.7.7",
    "clean-css-brunch": "1.7.1",
    "coffeelint-brunch": "1.7.0"
  }
}

And my config.coffee:
module.exports.config =
    files:
        javascripts:
            joinTo:
                'javascripts/app.js': /^app/
                'javascripts/vendor.js': /^vendor/
            order:
                # Files in `vendor` directories are compiled before other files
                # even if they aren't specified in order.
                before: [
                    'vendor/scripts/jquery-1.11.0.js'
                    'vendor/scripts/underscore-1.5.2.js'
                    'vendor/scripts/backbone-1.1.0.js'
                    'vendor/scripts/backbone.babysitter.js'
                    'vendor/scripts/backbone.projections.js'
                ]

        stylesheets:
            joinTo: 'stylesheets/app.css'
            order:
                before: ['vendor/styles/normalize.css']
                after: ['vendor/styles/helpers.css']

        templates:
            defaultExtension: 'jade'
            joinTo: 'javascripts/app.js'

    plugins:
        uglify:
            mangle: false
            compress:
                global_defs:
                    DEBUG: false
        cleancss:
            keepSpecialComments: 0
            removeEmpty: true

I think this could come from the fact I'm using Coffee to write JS and Stylus to write CSS (for clean-css' case) but I didn't manage to 1°) be 100% sure it's the reason 2°) found a solution for that.
Thank you in advance!

The command is now
brunch build -p
brunch watch -p

-P is for mapping ports


How to chain a validation (check constraints) on parsed data?

Hi, I'm wondering how to return a custom String error message if a constraint on parsed data is not respected (such as only few u8 values are authorized, useful for a PNG decoder I'm trying to do).
What I mean is I whish I could do something like this:
// Does not compile since cannot convert String to Err<(&[u8], ErrorKind)>
fn parse_color_type(input: &[u8]) -> IResult<&[u8], ColorType> {
    let (input, color_type_u8) = be_u8(input)?;
    let color_type = ColorType::try_from(color_type_u8)?; // The Err is a String
    Ok((input, color_type))
}

Is there some combinator or function I did not find that would enable me to plug this kind of constraint validation on the parsed data?

Rust version : 1.36.0
nom version : 5.0.0

Seems like that's always after formalizing an issue that you find an answer ... sorry for the noise. The solution was simply to use the map_res combinator like so:
let (input, color_type) = map_res(be_u8, ColorType::try_from)(input)?;


integrate appearance modal into profile

e.g. events only on change, but changes are applied automatically

ah, keep modal, but make button more prominent


是否有新版本更新？

你好，是否有新版本更新呢？

Please write in English.

Hello, is there a new version of the update do? Are there plans to add new features?   from google Translate  :)

Nowin currently has lowest priority of all my OSS projects. Mainly because I expecting Kestrel will be able to replace it soon.


Updates in setup.py for pypi installation

Cleaned the setup.py and other config files in order to make installation via pip install tofu work without imposing a previous installation of Cython or numpy or having to add pre-compiled files. Seems to be working on sample project (https://github.com/lasofivec/sampleproject).
Added wheel packaging in travis CI.
Left requirements.txt even if unnecessary.

Hello @lasofivec! Thanks for opening this PR. We checked the lines you've touched for PEP 8 issues, and found:

In the file setup.py:

Line 27:1: E303 too many blank lines (3)
Line 27:80: E501 line too long (80 > 79 characters)
Line 33:80: E501 line too long (80 > 79 characters)
Line 145:80: E501 line too long (80 > 79 characters)


remove vim junk

Coverage remained the same at 27.523% when pulling ddabea52b4fac4ceac82d877c06127c19aef9031 on l29ah:master into f2ce052a902cd6c1a4c2d81dac37ce025e79e073 on OpenBazaar:master.


Openstack Do Not Merge

This is a preview which violates the commit guidelines of heptio's contributing.md.

/hold


[BUG] Atlas entries do not show on fresh install

Describe the bug
On a fresh pip install of either brainrender-napari or brainglobe when I open brainrender there is no atlases in the atlas viewer. I have never used brainglobe before, so maybe this is the expected behavior? Documentation makes me think otherwise.
Expected behaviour
There would be a list of atlases I can click on as according to the tutorial.
Screenshots

Computer used (please complete the following information):
napari: 0.4.19.post1
Platform: Windows-10-10.0.22631-SP0
Python: 3.10.14 | packaged by conda-forge | (main, Mar 20 2024, 12:40:08) [MSC v.1938 64 bit (AMD64)]

Thanks for reporting @TimMonko
You're right, the tutorial is out-of-sync with the latest version. The widget currently only shows the atlases you have already downloaded.
Our plan is to have two separate `brainrender-napari widgets - one for downloading atlases, and one for visualising them.
To get it to work in the meantime, you should be able to use the command line to download the atlas you're interested in. For example, for the Allen Mouse atlas at 50 um resolution, you would do:
brainglobe install -a allen_mouse_25um

Then you should be able to close and reopen napari, and continue the tutorial from step 3.


feat: added  label overrides on AccountProfileInfo

Part of: #409
Impact: minor
Type: feature
Component
AccountProfileInfo now has overrides when i18next will be implemented (see #409)
Breaking changes
No breaking chances, all added fields are optional
Testing

Add a new prop editAccountButtonText or to <AccountProfileInfo />
Add the value "test" to editAccountButtonText
Button should display "test" when test is given as a value to the prop. When the prop editAccountButtonText is not added, it should default to the values given in default props

🚀 Preview deployed
Built with commit b84ebafd229778d6af10fa1f7a64ffc27c7deebf
https://deploy-preview-441--stoic-hodgkin-c0179e.netlify.com

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


[MM-61121] Add diagnostics data to the Support Packet

Summary
When a Support Packet gets generated, the plugin now includes diagnostics data via a diagnostics.yaml file into the Packet.
Example content of jira/diagnostics.yaml:
version: 4.1.1-rc1+7536b5d
instance_count: 0
server_instance_count: 0
cloud_instance_count: 0
subscription_count: 0
connected_user_count: 0

Requires https://github.com/mattermost/mattermost/pull/28833 on the server side
Ticket Link
https://mattermost.atlassian.net/browse/MM-61121

/update-branch

Error trying to update the PR.
Please do it manually.

@Kshitij-Katiyar Gentle reminder to review the PR :wink:

Per discussion with @raghavaggarwal2308, QA testing will happen post-merge.


Chat demo does not work on Android because of maxStorageBufferBindingSize

On my Pixel 7 Android device, the maxStorageBufferBindingSize limit is only 128. Sadly https://webllm.mlc.ai/#chat-demo requires 1024 for the Llama-2-7b-chat-hf-q4f16_1 model as seen below when run on Chrome for Android.
As it is possible with an Android app (https://llm.mlc.ai/#android), would it be possible to lower this limit so that more Android devices can access and play with https://webllm.mlc.ai/#chat-demo? Note that WebGPU support is coming to Android soon. See https://groups.google.com/a/chromium.org/g/blink-dev/c/YFWuDlCKTP4/m/97C4LCBUBgAJ

It seems related to https://github.com/apache/tvm/pull/14640

How can the Chrome team assist you in addressing this limitation? The maxStorageBufferBindingSize WebGPU limit is actually derived from Vulkan's maxStorageBufferRange limit.

Get it, let us look a bit into it and see if it is possible to get a variant of small model that fit into this limit. In the meantime, I feel that the vulkan driver should be able to lift some of the limit, but of course that would require changes to the vulkan driver end

Hi @beaufortfrancois, the demo now has three models (ones with -1k suffix) that should be able to run with 128MB: https://webllm.mlc.ai/

First of all, thanks for providing those models!
I've just tried the Llama-2-7b-chat-hf-q4f16_1-1k model in Chrome Canary for Android where WebGPU is enabled by default and as you can see below, the never-ending answer seems wrong when asking "Which color is the dress?". Is this an issue in the model or in the implementation?
Note that it works great on "Apple M1 Pro" device.
https://github.com/mlc-ai/web-llm/assets/634478/177d4dcb-8889-4938-b4f5-c80255f6a68c

that model depends on shader-f16 feature, which only existed in chrom canary (and not chrome stable AFAIK), so not sure if it works on android. If it is possible to get the console output, it will also help us see what is going on

shader-f16 is shipping in Chrome 120. See https://groups.google.com/a/chromium.org/g/blink-dev/c/AsKn-UwMYAE/m/4FKB-x_QAQAJ
I'm unable to get logs as Chrome is now crashing with this model. Sorry ;( I've tried several times.

Do you mind trying out RedPajama-INCITE-Chat-3B-v1-q32-1k?

It works great with RedPajama-INCITE-Chat-3B-v1-q4f32_1-1k.

It is possible that the model crashes in Llama, we are hitting quite a bit of limit in Llama2 model, and in iOS we had to rely on 3bit quantization. So likely 3B model would be preferred choice.
Glad that RedPajama-INCITE-Chat-3B-v1-q4f32_1-1k works, perhaps you can also try RedPajama-INCITE-Chat-3B-v1-q4f16_1-1k to test f16 support

Glad that 3B model works, this is the first running example webgpu native LLM on mobiles AFAIK, thank you @beaufortfrancois  for pushing this

It is possible that the model crashes in Llama, we can hit VRAM limit in Llama2 models(that goes beyond 4GB) when using 4 bit quantization, and in iOS we had to rely on 3bit quantization to stay in memory budget. On android we can sometimes get Llama2 4bit model working but that also requires to go beyond 4GB VRAM limit and the depending on the system limit and phone's capability it can crash.

🥳  I was finally able to get logs!
[FATAL] /ssd1/cfruan/packages/tvm-unity/src/runtime/memory/memory_manager.cc:108: InternalError: Check failed: (offset + needed_size <= this->buffer.size) is false: storage allocation failure, attempted to allocate 8396800 at offset 0 in region that is 8388608bytes
put_char @ worker.360c8a9c.js:669

Uncaught (in promise) DOMException: Failed to execute 'mapAsync' on 'GPUBuffer': Device is lost

Hopefully this will help.

So likely 3B models are good choice to demo LLM on android/webgpu, or if later we have 2bit model variants. Glad that RedPajama-INCITE-Chat-3B-v1-q4f32_1-1k works, perhaps you can also try RedPajama-INCITE-Chat-3B-v1-q4f16_1-1k to test f16 support

Glad that 3B model works, this is the first running example of webgpu native LLM on mobile phone AFAIK, thank you @beaufortfrancois for pushing this. Love to share this with broader community and let us know how we can help

I'm also really happy 😄  to see WebLLM running on Android without any flag ;)

The error log indeed indicate possible OOM ("gpu get lost") because the model is too VRAM demanding

The error log indeed indicate possible OOM ("gpu get lost") because the model is too VRAM demanding

Is there a way at the runtime to know this device won't work properly? Is there a GPU adapter limit ( https://gpuweb.github.io/gpuweb/#gpusupportedlimits) you could tie this to? The two other ones work great.

We need to know the total amount of VRAM that can be allocated. In Vulkan I think should corresponds to PhysicalDeviceMemoryProperties  and memory heap size.
Note that there is also a system cap, since we are using unified memory in ARM chips, the SoC can have 8G but may limit the gpu to only use 4G.
I am not sure if there is an exact correspondence in the spec. maxBufferSize limits the size of buffer we can allocate per alloca, but we need total allocable memory size .

In the meantime, it is possible to react to "out-of-memory" GPU errors. See https://gpuweb.github.io/gpuweb/#error-scopes
device.pushErrorScope('out-of-memory');
// ...
device.popErrorScope().then((error) => {
  console.error(error.message);
});

We need to know the total amount of VRAM that can be allocated. In Vulkan I think may corresponds to PhysicalDeviceMemoryProperties  and memory heap size. Note that there can also be a system cap, since we are using unified memory in ARM chips, the SoC can have 8G but may limit the gpu to only use 4G.

From what I understand, exposing this raw value won't be possible in WebGPU due to obvious privacy concerns.

It's not clear to me if reacting to "out-of-memory" GPU errors should happen in WebLLM or in Apache TVM?

Will take a look later this week!

@CharlieFRuan Did you have a chance to look at it?

@beaufortfrancois I looked into it but had trouble replicating the OOM  webGPU error on my device (a Macbook)...
Could you help me triage a bit? Specifically, do you see this piece of log every time the issue happen?
[FATAL] /ssd1/cfruan/packages/tvm-unity/src/runtime/memory/memory_manager.cc:108:
InternalError: Check failed: (offset + needed_size <= this->buffer.size) is false:
storage allocation failure, attempted to allocate 8396800 at offset 0 in region that is 8388608bytes
@ worker.360c8a9c.js:669

From my understanding, whenever you see this log, it means that we have caught the error, and the UI would tell the user about Generate error (like the screenshot below):

Therefore, under what circumstance do you encounter the demo just output gibberish without raising an error like your earlier comment?

I've just tried the Llama-2-7b-chat-hf-q4f16_1-1k model in Chrome Canary for Android where WebGPU is enabled by default and as you can see below, the never-ending answer seems wrong when asking "Which color is the dress?". Is this an issue in the model or in the implementation?
Note that it works great on "Apple M1 Pro" device.
screen-20231113-091318.mp4

Thank you! Let me know if I misunderstood something.

Hi @beaufortfrancois, thanks for the confirmation; I just got my hands on a Samsung Galaxy S23 to try to reproduce and hopefully catch the OOM error (after concluding that non-mobile devices perhaps cannot reproduce the OOM error).
However, when I go to webgpureport.org, requestAdapter says failed (leading to failure of web-llm), and logs above say:
webgpu request with adapterOptions: {"powerPreference": "high-performance"} failed: Cannot read properties of null (reading 'isFallbackAdapter')
webgpu request with adapterOptions: {"powerPreference": "low-power"} failed: Cannot read properties of null (reading 'isFallbackAdapter')
webgpu request with adapterOptions: {compatibilityMode: true} failed: Cannot read properties of null (reading 'isFallbackAdapter')

webgpu appears to not be supported

I set webgpu to enabled in chrome://flags, using the latest chrome version 119.0.6045.163. I wonder if you happen to know about the error above and whether Galaxy S23 supports webgpu at all... Otherwise, I might have to guesstimate the implementation and hope that it catches the error.
Thanks in advance! Besides, I might have limited availability until next week because of Thanksgiving.

WebGPU is available without a flag in Chrome Canary for Android.

Thanks in advance! Besides, I might have limited availability until next week because of Thanksgiving.

Enjoy 🦃

@CharlieFRuan Did you have a chance to look at this issue?

@beaufortfrancois Unfortunately not yet... Sorry for the delay, have been caught up with various other things. But this is still something in my mind and I'll see if I can do it this weekend/early next week.

@beaufortfrancois Got Android development workflow going; and was able to crash. Tried the device.pushErrorScope() and it's not able to catch the error for me before it crashes; at least on the web-llm side. Though the error should be inside reload(), around the fetchNDArrayCache(). Did you have to do anything to get the log "mapAsync on GPUBuffer device is lost"? Or you were just running the demo, and it is based on luck whether it throws the error? I might need to look into TVM to catch the error.

Or you were just running the demo, and it is based on luck whether it throws the error?

Exactly. I was "just" running the demo.

WebGPU will ship in Chrome 121 on Android in 2 weeks and it'd be nice if WebLLM demo does not crash, or at least, can handle it. Let me know how I can help further @CharlieFRuan

Thanks for the timeline! Will keep you updated.

Those are exciting news, thank you for sharing them @beaufortfrancois !
I got the 3B param model running on Android via the app I've been developing and would be interested to get the 7B Llama2 model working as well :) If I can help you with debugging or otherwise, please let me know @CharlieFRuan

Hey @patnorris, thanks for your interest and for offering help! However, as of now, it does not seem to be possible to run Llama 2 7B (even the 1k context length) on Android via Chrome. Perhaps you could check out https://llm.mlc.ai/docs/deploy/android.html.
@beaufortfrancois  https://github.com/mlc-ai/web-llm/pull/256 is my attempt to address this issue. We tried various ways of catching the crash, including propagating error from tvm and using device.lost.then. However, they don't seem to be reliable and Chrome would keep asking for memory until it crashes (with the "Aw Snap" crash page).
As a result, we decided to disable such models altogether on the demo page for Android so that users do not experience crashing. We predict whether the device would crash based on what maxStorageBufferBindingSize is used (assuming that if it is 128MB, then this device cannot run large models).
Currently, only 1k-context-length Redpajamas are selectable for Android. I will add more before Chrome 121 shipping.
Feel free to review and leave comments on that PR.

I just tried https://webgpureport.org/ on a Pixel 7 with Chrome Canary 122.0.6233.0, which worked as expected. Then I updated to 122.0.6237.0, which also worked as expected. It's possible that an intermediate Canary build broke WebGPU but if so it appears to be resolved now. Thus is the nature of nightly builds. :shrug:
I'll take a look on my end and see if there's some way for us to reliably catch this crash and surface it as a device loss. If it's being communicated through Vulkan according to spec then I think it really should already be firing. It's possible that it's provoking some deeper, system-level crash, though, and if that's the case I don't know how much we can do about it.

@toji Thanks for chiming in! Canary is working on my Android again!
Regarding the crash, please let me know if you need any information from me.

For info, here's the final output of adb logcat when Android kills Chrome Canary when I can't interact with it anymore:
lmkd  Kill 'com.chrome.canary:privileged_process0' (7798), uid 10386, oom_score_adj 0 to free 5161192kB rss, 183376kB swap; reason: device is low on swap (377032kB < 3145724kB) and thrashing (412%)
lmkd  Kill 'com.chrome.canary' (7685), uid 10386, oom_score_adj 0 to free 61488kB rss, 97804kB swap; reason: device is low on swap (613764kB < 3145724kB) and thrashing (477%)
lmkd  Kill 'com.chrome.canary:sandboxed_process0:org.chromium.content.app.SandboxedProcessService0:0' (7766), uid 90000, oom_score_adj 0 to free 49872kB rss, 429792kB swap; reason: device is low on swap (598584kB < 3145724kB) and thrashing (316%)
system_server  WIN DEATH: Window{2440115 u0 com.chrome.canary/com.google.android.apps.chrome.Main}

@beaufortfrancois let us know if there is anything you need from our end. Seems was due to android chrome taking too much memory. I wonder if limiting the models to 3b models help

@toji may have insights. From what I understand there's not much you can do from the web app side.

get it, maybe @CharlieFRuan can also confirm once we redeploy the latest that filters out the models, so we only run small models on android

@tqchen Yep, redeployed already:

great, @beaufortfrancois feel free to let us know if the latest version works for you and if you need anything from us

I still see all the models when going to https://webllm.mlc.ai/ in Chrome Canary for Android. Is that expected?

Hmm this is not expected... Could you share the log? or try clearing cache (not sure it'd help)

The limit of model is determined by max storage buffer binding size; if it is <= 128MB, then we limit the model. I'd expect your Android has 128MB; would be nice to confirm this from the log.

maybe related to browser cache

Looking at about:gpu, I can see maxStorageBufferRange is<PHONE_NUMBER> (2GB), and https://webgpureport.org now says the maxStorageBufferBindingSize WebGPU limit on my Pixel 7 device is<PHONE_NUMBER> (almost 2GB) with Chrome Canary (122.0.6250.0).
Source: https://source.chromium.org/chromium/chromium/src/+/main:third_party/dawn/src/dawn/native/Limits.cpp;l=58;drc=8e8525164710883e3af381a5c6fea4c8847a90c0

Hmm that is interesting... My Galaxy S23 is still 128MB with the same Chrome Canary version.
Good news is that I am guessing your Pixel 7 can run the regular Redpajama (not 1k version). On the other hand we might need to rely on some other approximation for the available vRAM.

I confirm RedPajama-INCITE-Chat-3B-v1-q4f16_1 works: prefill: 1.2083 tokens/sec, decoding: 4.3987 tokens/sec

Thanks for the confirmation; we'll try to come up with another solution for limiting model selection on Android phones with 2GB maxStorageBufferBindingSize

Hmm that is interesting... My Galaxy S23 is still 128MB with the same Chrome Canary version.

Out of curiosity, what is the maxStorageBufferRange  Vulkan limit value in about:gpu for your Galaxy S23 device?

wonder if we can rely on adapter info, at least for example in mac it will show up as gpu apple. maybe for android we have a special gpu vendor type?

Here's the GPU adapter info from https://webgpureport.org on my Pixel 7 device:

Here is our Galaxy S23's:

Out of curiosity, what is the maxStorageBufferRange  Vulkan limit value in about:gpu for your Galaxy S23 device?

134217728, so 128MB as well

I think we should be able to tell mobile gpus by looking at the vendor field and architecture field :)

FYI https://twitter.com/quicksave2k/status/1747884713757282450

OOM errors in createBuffer() are now able to be caught in webllm npm 0.2.36 via https://github.com/mlc-ai/web-llm/pull/402. If createBuffer() does not suffice, will follow up with more error catching in tvmjs. Thanks!
Redeployed https://webllm.mlc.ai/ as well.


Fixed spelling of Progressive.

I noticed some mis-spelled and misnamed words in the ProgressiveImage component.

I looked into why there was an error in the Travis CI build and found this SO:
https://stackoverflow.com/questions/39011223/travis-ci-build-failure-due-to-failed-to-execute-openssl-command


Remove unnecessary calls to check if process.version > 0.8

In lib/aspects.js the following check is done in two places:
if(process.version.split('.')[0] == 'v0' && process.version.split('.')[1] < 8){}

This isn't needed because Node Application Metrics doesn't versions before 0.10 (there is an install time check for this), so the check is redundant.

Resolved by PR #52


npm run demo:wasm fails

Thanks for the nice work, I have a problem with "npm run demo:wasm" after build , the error on my ubuntu18 is
`

<EMAIL_ADDRESS>demo:wasm /home/zaikun/technology/bazel-emscripten
RUN_DEMO=wasm node ./hello-world/javascript/examples/demo.js

module.js:549
throw err;
^
Error: Cannot find module '../dist/wasm/umd'
at Function.Module._resolveFilename (module.js:547:15)
at Function.Module._load (module.js:474:25)
here is the log
16 error owner ls Couldn't get owner data bazel-emscripten
17 verbose stack Error: Not found : bazel-emscripten
17 verbose stack     at makeError (/usr/share/npm/node_modules/npm-registry-client/lib/request.js:264:12)
17 verbose stack     at CachingRegistryClient. (/usr/share/npm/node_modules/npm-registry-client/lib/request.js:252:14)
17 verbose stack     at Request._callback (/usr/share/npm/node_modules/npm-registry-client/lib/request.js:172:14)
17 verbose stack     at Request.self.callback (/usr/share/npm/node_modules/request/request.js:198:22)
17 verbose stack     at emitTwo (events.js:126:13)
17 verbose stack     at Request.emit (events.js:214:7)
17 verbose stack     at Request. (/usr/share/npm/node_modules/request/request.js:1082:10)
17 verbose stack     at emitOne (events.js:121:20)
17 verbose stack     at Request.emit (events.js:211:7)
17 verbose stack     at IncomingMessage. (/usr/share/npm/node_modules/request/request.js:1009:12)
18 verbose statusCode 404
19 verbose pkgid bazel-emscripten
20 verbose cwd /home/zaikun/technology/bazel-emscripten
21 error Linux 5.4.0-86-generic
22 error argv "/usr/bin/node" "/usr/bin/npm" "owner" "ls" "bazel-emscripten"
23 error node v8.10.0
24 error npm  v3.5.2
25 error code E404
26 error 404 Not found : bazel-emscripten
27 error 404
28 error 404 'bazel-emscripten' is not in the npm registry.
29 error 404 You should bug the author to publish it (or use the name yourself!)
30 error 404 Note that you can also install from a
31 error 404 tarball, folder, http url, or git url.
32 verbose exit [ 1, true ]
`
Seems the owner issue ?

did you run npm i then npm run rollup?


Slash command perms v2

Closes: #2184
Upstream: discord/discord-api-docs@4a3b20a

Nuke batchEditApplicationCommandPermissions (https://discord.com/developers/docs/interactions/application-commands#batch-edit-application-command-permissions)
update JSDocs Comments (like, a lot, probably will revert unnecessary comments changes next commit)
Add id to upsertApplicationCommands options

Can you rebase this PR to #2238?

Can you rebase this PR to #2238?

@itohatweb resolved merge conflicts

I'M too lazy to review


Hyperlinks from headings

Not sure if Markdown supports this. md2pptx currently seems not to do this. Labeled as a bug because I think Markdown should support it and so should md2pptx

Fixed in v1.7.1. Was bad RegEx parsing the heading line.

Fixed in v1.7.1. Was bad RegEx parsing the heading line.


added new postUpgradeCb check for CSCwe21982

folks,
can you please review this pull request?
Thanks,
welkin

Updated pytest output:
[Check  1/1] Post Upgrade Callback Integrity... Re-run script after APICs are upgraded and back to Fully-Fit  POST UPGRADE CHECK REQUIRED
[Check  1/1] Post Upgrade Callback Integrity... Re-run script after APICs are upgraded and back to Fully-Fit  POST UPGRADE CHECK REQUIRED
[Check  1/1] Post Upgrade Callback Integrity...                                                                                PASS
[Check  1/1] Post Upgrade Callback Integrity...                                                                                PASS
[Check  1/1] Post Upgrade Callback Integrity...                                                                   FAIL - OUTAGE WARNING!!
  Missed Objects       Impact
  --------------       ------
  infraImplicitSetPol  Infra implicit settings will not be deployed

  Recommended Action: Contact Cisco TAC with Output
  Reference Document: https://datacenter.github.io/ACI-Pre-Upgrade-Validation-Script/validations/#post-upgrade-callback-integrity

[Check  1/1] Post Upgrade Callback Integrity...                                                                                PASS
[Check  1/1] Post Upgrade Callback Integrity...                                                                   FAIL - OUTAGE WARNING!!
  Missed Objects       Impact
  --------------       ------
  fvSlaDef             IPSLA monitor policy will not be deployed
  infraImplicitSetPol  Infra implicit settings will not be deployed

  Recommended Action: Contact Cisco TAC with Output
  Reference Document: https://datacenter.github.io/ACI-Pre-Upgrade-Validation-Script/validations/#post-upgrade-callback-integrity

[Check  1/1] Post Upgrade Callback Integrity...                                                                                PASS
[Check  1/1] Post Upgrade Callback Integrity...                                                                   FAIL - OUTAGE WARNING!!
  Missed Objects                   Impact
  --------------                   ------
  fvSlaDef                         IPSLA monitor policy will not be deployed
  infraAssocEncapInstDef           VLAN for missing Mo will not be deployed to leaf
  infraImplicitSetPol              Infra implicit settings will not be deployed
  infraRsConnectivityProfileOpt    VPC for missing Mo will not be deployed to leaf
  infraRsToInterfacePolProfileOpt  VLAN for missing Mo will not be deployed to leaf

  Recommended Action: Contact Cisco TAC with Output
  Reference Document: https://datacenter.github.io/ACI-Pre-Upgrade-Validation-Script/validations/#post-upgrade-callback-integrity

[Check  1/1] Post Upgrade Callback Integrity...                                                                                PASS
[Check  1/1] Post Upgrade Callback Integrity...                                                                   FAIL - OUTAGE WARNING!!
  Missed Objects                   Impact
  --------------                   ------
  compatSwitchHw                   Unexpected 64/32 bit image can deploy to switches
  fvSlaDef                         IPSLA monitor policy will not be deployed
  infraAssocEncapInstDef           VLAN for missing Mo will not be deployed to leaf
  infraImplicitSetPol              Infra implicit settings will not be deployed
  infraRsConnectivityProfileOpt    VPC for missing Mo will not be deployed to leaf
  infraRsToInterfacePolProfileOpt  VLAN for missing Mo will not be deployed to leaf

  Recommended Action: Contact Cisco TAC with Output
  Reference Document: https://datacenter.github.io/ACI-Pre-Upgrade-Validation-Script/validations/#post-upgrade-callback-integrity


Update sbt to 1.7.1

Updates org.scala-sbt:sbt from 1.6.2 to 1.7.1.
GitHub Release Notes - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Files still referring to the old version number
The following files still refer to the old version number (1.6.2).
You might want to review and update them manually.
joern-cli/frontends/kotlin2cpg/build.sbt

Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.scala-sbt", artifactId = "sbt" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "@monthly" },
  dependency = { groupId = "org.scala-sbt", artifactId = "sbt" }
}]

labels: library-update, early-semver-minor, semver-spec-minor, old-version-remains, commit-count:1

Superseded by #1587.


Polyfill is included in all scripts, even if they will not be run in an extension context

Currently, we add the browser polyfill to all files ending in .ts. This works nicely to make sure it's available in content scripts, but has limitations. Namely, adding a script tag to the page and referencing a JS file from the extension will try to load the polyfill, and fail because the script is being loaded in the normal world and without access to browser APIs.
We should probably make which files to polyfill configurable or do some sort of AST search for a call to browser.

Starting looking at this. @typescript/sandbox does provide a way of getting the AST, but it only returns it for the current program, rather than letting you pass in individual files. This seems to cause some errors to be thrown that I need to look in to further.


Initial Gitlab CI support [gitlab-ci-dev]

This PR introduces a first implementation of a Gitlab pipeline for MFEM.
In particular, this pipeline is setup to:

perform some static checks (code style and documentation)
build MFEM prerequisites
build MFEM for different configurations
perform sanity checks
run baseline test and share the diff

TODO:

[X] use existing style test (introduced by #1244)
[x] validate baseline update mechanism and restrict it to master branch
CANCELLED: fix jobs triggered when pipeline failed early. Bug in Gitlab
[x] fix concurrency issue on baseline test (mfem link naming): will solve itself by adding baseline test in mfem (no need to call tests from an outside repo)
[x] print diff in the logs (style check and baseline check)

PR
Author
Editor
Reviewers
Assignment
Approval
Merge

#1203
@adrienbernede
@tzanio
@acfisher + @tzanio
12/19/19
⌛due 03/07/20
⌛due 03/14/20

LGTM

@acfisher and @v-dobrev, reminder that the reviews for this PR are due in a week

@mfem/reviewers -- this PR will affect the review process, so please take a look and provide your input to @adrienbernede and @acfisher.

I suggest updating CONTRIBUTING.md to give some basic info about how to use/check the Gitlab CI features.

@barker29
I updated CONTRIBUTING.md, please let me know if that’s what you expected.

@tzanio @acfisher
We are experiencing some issues with Gitlab mirroring.
Basically, since we filter out branches that are not "approved", Gitlab fails to create them and considers each failure as an error. Eventually, Gitlab blocks mirroring because of those recurring errors. This does not happen when the mirror repo has just been created. Which is why it appeared to be working in December.
In short, error handling in Gitlab is at fault here, and @tgmachina will be discussing possible improvements with the Gitlab team.
If this PR is accepted, I think we should still merge it. However the Gitlab CI would not be working until further notice.
In the meantime, we could create another MFEM repo on Gitlab (not a mirror repo), in which branches can be pushed to trigger the pipeline. This would be a manual process, but anyone with an LC Gitlab account could trigger tests when necessary. Scaling isn’t guaranteed though.

@adrienbernede
Currently, the result of that error handling is that mirroring for the repo stops--would it suffice right now to re-enable it periodically in GitLab? It's also not ideal, but maybe easier for one person to just turn it back on in lieu of maintaining another repo that is having CI triggered on it manually, just a thought.
I spoke with the GitLab team today and they agree that this is a priority. I'll open an issue with them and we'll work on getting the fix made in GitLab server. Meanwhile, I could work on patching the offending code myself in our own instance.

I first I thought that mirroring was paused if too many errors occurred during one mirroring attempt.
Umpire case proved me wrong. One error interrupts the mirroring. After several interruptions, the mirroring is paused.
Re-enabling mirroring would NOT make it to work again, even for a little while. I was also confused by the false positive we sometimes get (mirroring marked as successful in settings page, but marked as failing on project page).

Delaying by a week to give folks time to address the above issue.

LGTM

@adrienbernede it looks like the lib builds are failing?

LGTM

LGTM

LGTM

Maybe that's too much to ask, but can we have a GitLab badge like the Travis and Appveyor one at https://github.com/mfem/mfem/blob/master/CONTRIBUTING.md?

LGTM

LGTM

@adrienbernede -- I don't see a run for this at https://lc.llnl.gov/gitlab/mfem/mfem/pipelines... am I missing something?

Looking at this again, I wonder if it is better to merge as is with the baseline test only so the team can get used to running it, and add longer tests later?

@tzanio, I should have shared my changes on Friday...
I changed the way I manage the allocation to allow the addition of sample-runs-baseline. The consequence is that it is much more difficult to get resource on daytime. But the run-samples-baseline are here, and I just have to wait hours between each "validation" cycle.
I also added some comments in the yaml files, but plan on describing the pipeline more thoroughly. What is the best place to document it?
If you want to merge the baseline only version, I can add a commit doing the necessary, removing the sample-runs-baseline and moving back to debug queue for more responsiveness.

LGTM

@tzanio, this is working for me, however I’m not sure why I have differences in baseline test (except because of timing).

LGTM

LGTM

Merged in next for testing...

Adding a few extra days for approval...

@tzanio sorry for the forced push, I had a merge with master in my diverged history. I cherry-picked your changes. This time it was carefully done.

LGTM

Baseline and rebaseline have been extensively tested to check if it would work on master, and check if the commit works. I used a clone to emulate the behavior on master, and tested to rebaseline in another tests repository.

Adding a bit more time to review...

LGTM

Is this ready to go @adrienbernede and @acfisher ?

I am on a mirroring issue with this branch...

LGTM

Is the mirroring up and running?  I don't see a pipeline launch under the latest magic word.

Is the mirroring up and running? I don't see a pipeline launch under the latest magic word.

It’s not working, I am talking with @tgmachina about this.

LGTM

@tzanio No change since the last mirroring, so sing-off won’t have effect here.
Let me push the changes requested by @acfisher so that you can play with it.

LGTM

The PR is now fully functional from my perspective, let’s see how it scales!

Reminder: Sign-off does not "trigger" CI, but allows it, so that the next time mirroring happens, CI will be triggered.
Mirroring can be forced on CI side, which I did to speed-up the process here.

Looks like it is in good shape.  Lets get this pulled in asap.

Merged in next for testing...

I "parmetis" build in the pipeline -- not sure why it is there -- we can probably remove it.

I think Tzanio mentioned it as well. I was assuming MFEM_USE_MPI implied parmetis.
@acfisher Do you remember what was the intention?

Some TPLs depend on parmetis but mfem does not depend on it directly. The parallel mfem build requires just serial metis.

We can change that later... I think for now the goal is for folks to get experience with GitLab.


avante stop generating and freezes

i dont know if its an issue with my hardware or avante itself. but, sometimes, when I was prompting, claude would just stop responding and I had to close my tmux server because I can't do anything on the nvim window. after I start the server again, and tried to prompt again, it shows this error

Claude is overloaded.

Same issue.
Is there a way to not crash and freeze nvim but instead show an error message or close the avante window?
My current workflow now is killing nvim and restart the process?

Hmm there is a bug with suggestion timer atm to cause overloading. I will look into this during the weekend or so

The cause being overloaded can't be right.
I just put in my first 10 dollars.
Fired up avante and got this on my first message.

Similar bug report https://github.com/yetone/avante.nvim/issues/598

I saw this error for the first time today (10AM PST on a Friday). It was temporary and resolved itself after some time.

I think this is just API up time, I saw it this morning too, then not this afternoon


Build failure: fprintd

Steps To Reproduce
Steps to reproduce the behavior:

build fprintd 1.94.3

Build log
https://gist.github.com/philipwilk/f0267008a77c47e373d53ba80dd6b4c7
Additional context
Fails in tests
Notify maintainers
@abbradar

Metadata
Please run nix-shell -p nix-info --run "nix-info -m" and paste the result.
[philip@nixos-thinkcentre-tiny:~]$ nix-shell -p nix-info --run "nix-info -m"
 - system: `"x86_64-linux"`
 - host os: `Linux 6.10.0, NixOS, 24.11 (Vicuna), 24.11.20240721.68c9ed8`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.23.3`
 - channels(root): `"nixos-23.05"`
 - nixpkgs: `/nix/store/afawjm6nv8m5aagkcqxlxgrr5qpyh6cm-source`

Add a :+1: reaction to issues you find important.

Built successfully on my machine on both current master (25e9685b9aaf0ea1b3654a1909711399a3b0020f) and 68c9ed8bbed9dfce253cc91560bf9043297ef2fe.
But your build and 2 builds on hydra in the past month failed on same test:
https://hydra.nixos.org/build/268452290
https://hydra.nixos.org/build/264762179
Seems to be this issue:
https://gitlab.freedesktop.org/libfprint/fprintd/-/issues/129
and test_removal_during_enroll is just flaky.

Is it possible for us to skip this specific test? I've had fprintd fail to build multiple times because of flakey tests and it's getting quite annoying.

As far as I know not possible without patching out that test or skipping full test suite:
https://github.com/mesonbuild/meson/issues/6999
But considering how frequent these are it may be a time for patching it out.


Is the<EMAIL_ADDRESS>email still valid?

In one of the FAQ's<EMAIL_ADDRESS>is listed as a contact for questions but I am getting a bounce back when I contact it.

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

ID: 63228b08-f4f2-36ca-4941-cb3ac92d6c09
Version Independent ID: 228109d7-20cf-56cd-dc0d-86ff4f0cd7eb
Content: FAQ for Azure Import/Export service
Content Source: articles/storage/common/storage-import-export-service-faq.md
Service: storage
Sub-service: common
GitHub Login: @alkohli
Microsoft Alias: alkohli

@nastassiar Thank you for your feedback . We will investigate and update this thread.

@nastassiar Thanks for bringing this to our attention. Your feedback has been shared with the content owner for further review.

@nastassiar Thank you for bringing this to our notice! I have removed the DL and updated the article. The change should go live after 10 AM today. Thanks!
#please-close


Silas

simplified folder names: msa_trim. to msa,

added querry for mmseqs

evaluate mmseqs profiles with train and negative seqs

possibility to add test sequences, sequences not part of profile.

deactivated hmmer, but can be run by snakemake [options] hmmer

@chris-rands i merged my changes

Did you run ./test.sh in .test successfully? I'm getting an error; seems to be linked to the relative paths used and an added .; i can fix this, but just wanted to check whether or not you saw the same thing?
Input targets: ['family2', 'family1']
Building DAG of jobs...
MissingInputException in line 141 of /home/cegg/rands/scripts/Github_profile_pipeline/profiles_from_protein_families/rules/mmseqs.smk:
Missing input files for rule get_negative_evaluation_fasta:
../data/family2..fa

No, sorry I didn't tested it.

I haven't been able to fix all the tests unfortunately; I started working on this on a new branch https://github.com/chris-rands/profiles_from_protein_families/commit/a53f96949d5c06dc7779afcc4901a53c6cf96e53
where I have fixed some of the path issues, but I'm still getting failures related to the new mmseqs rules and not sure exactly how you intended things to run.
Are you able to fix the tests so that ./test.sh runs successfully?


formula: bump -s -w as default std_go_args

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

[x] Have you successfully run brew typecheck with your changes locally?
[x] Have you successfully run brew tests with your changes locally?

We have used -s -w for std_go_args for quite some time, now bump it to be std_go_args.

Do you have a list of formulae that use std_go_args but don't currently use -s -w?

Do you have a list of formulae that use std_go_args but don't currently use -s -w?

almost every go formulae are using -s -w

The reason I ask: are any of the ones that don't use it intentional? Have we confirmed they work with -s -w? There used to be a concern that -s -w might have broken a few formulae, but things have changed and this might no longer be the case.
If it's very few left, then it should be easy to test.

There used to be a concern that -s -w might have broken a few formulae

IIRC the concern was about debugging the binary, TBH, I dont think that would justify us to add the flags and ship the release binary. :)

I think the related core PR is ready to go as well.

Do you have a list of formulae that use std_go_args but don't currently use -s -w?

To answer this myself: about 25% of std_go_args formulae don't use these flags.

To answer this myself: about 25% of std_go_args formulae don't use these flags.

Thanks @Bo98.
@chenrui333 I'd like to see those formulae retested shortly after this PR is merged or preemptively modified to remove those flags until they can be added in later.

@chenrui333 I'd like to see those formulae retested shortly after this PR is merged or preemptively modified to remove those flags until they can be added in later.

yeah, totally, we can kick of the mass tests to see how the flags play out and then merge the linked syntax change PR.

Do you have a list of formulae that use std_go_args but don't currently use -s -w?

To answer this myself: about 25% of std_go_args formulae don't use these flags.

I see your point now. make sense

I will update the PR this weekend (also we can handle this PR after we are done with sonoma bottles :) )

Informally, we could consider the month around when bottling happens as a soft "code freeze" on anything build environment related.

I think this makes a lot of sense and am all for it.

@chenrui333 What's the latest here?

Yeah I would be more comfortable making this change after mass bottling is complete, so any potential issue doesn't spread quickly to everything we bottle and instead only apply to formulae being updated.

@Bo98 is this "done"?

will work on this over the weekend. :)

@chenrui333 Ok, thanks. For future reference: we'd rather folks focused on completing existing PRs and addressing comments on them before opening new ones, thanks.

fair point.

I will reopen this one after getting #16126 merged first

(my current thinking is that we should just update all the ldflag usage in homebrew-core w/o too much thinkings about the if/else handlings, after all, the default -s -w wont disrupt the build flow if there would be duplicate if used by others)


Roll Engine from 07afcf7d0f12 to 592993cdbebe (13 revisions)

https://github.com/flutter/engine/compare/07afcf7d0f12...592993cdbebe
2021-02-23<EMAIL_ADDRESS>Roll Skia from e82436f5c353 to 98f85d0e45f1 (15 revisions) (flutter/engine#24571)
2021-02-23<EMAIL_ADDRESS>Roll Fuchsia Mac SDK from Fote78jZn... to 0c-7C5noH... (flutter/engine#24568)
2021-02-23<EMAIL_ADDRESS>Roll Fuchsia Linux SDK from c9naFjip3... to 8unxeSvw2... (flutter/engine#24566)
2021-02-23<EMAIL_ADDRESS>Roll Dart SDK from 2d30896744b5 to a476002dba33 (2 revisions) (flutter/engine#24562)
2021-02-23<EMAIL_ADDRESS>Roll Skia from bd9740074445 to e82436f5c353 (4 revisions) (flutter/engine#24567)
2021-02-22<EMAIL_ADDRESS>Roll Skia from cc75fa8f958b to bd9740074445 (10 revisions) (flutter/engine#24559)
2021-02-22<EMAIL_ADDRESS>[macos] Make metal the default rendering backend on macOS >= 10.14 (flutter/engine#23967)
2021-02-22<EMAIL_ADDRESS>Roll Dart SDK from f78bd85cda0c to 2d30896744b5 (9 revisions) (flutter/engine#24554)
2021-02-22<EMAIL_ADDRESS>Roll Skia from cad4709ca475 to cc75fa8f958b (13 revisions) (flutter/engine#24553)
2021-02-22<EMAIL_ADDRESS>Restore call to setFilterQuality (flutter/engine#24542)
2021-02-22<EMAIL_ADDRESS>Roll Fuchsia Mac SDK from YBiCU3Z3r... to Fote78jZn... (flutter/engine#24541)
2021-02-22<EMAIL_ADDRESS>Roll Fuchsia Linux SDK from -8KkhcJ3h... to c9naFjip3... (flutter/engine#24539)
2021-02-20<EMAIL_ADDRESS>Roll Fuchsia Mac SDK from 5vi8TQldn... to YBiCU3Z3r... (flutter/engine#24535)
Also rolling transitive DEPS:
fuchsia/sdk/core/linux-amd64 from -8KkhcJ3hYTq to 8unxeSvw26l3
fuchsia/sdk/core/mac-amd64 from 5vi8TQldnD6E to 0c-7C5noHq4b
If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/flutter-engine-flutter-autoroll
Please CC<EMAIL_ADDRESS>on the revert to ensure that a human
is aware of the problem.
To report a problem with the AutoRoller itself, please file a bug:
https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/master/autoroll/README.md

Closing this roll to kick off a new one following the plugins roll.

Commit queue failed; closing this roll.


Turbo not working on windows

Verify canary release

[X] I verified that the issue exists in the latest Turborepo canary release.

Link to code that reproduces this issue
https://github.com/jaspreet-singh-96/test-repo
What package manager are you using / does the bug impact?
pnpm
What operating system are you using?
Windows
Which canary version will you have in your reproduction?
1.13.3-canary.0
Describe the Bug
I am getting this error when running any turbo command in windows. For example turbo dev --parallel or turbo build.

It works fine on macos and linux. Works fine whe running individual packages using pnpm filter.
Expected Behavior
Should start all packages in dev mode.
To Reproduce
run turbo dev --parallel in root directory.
Additional context
I have tested this with both latest stable release and canary release. Below is output with verbosity level 2

I pretty sure this line is producing the error, which is odd as I believe Root is a predefined cert store location.
I'm not sure if this is the best way to go about finding the default cert store, but it worked on my machine. Could you verify that the following commands work in Powershell and that the directories exist?
cd Cert:\
cd .\\LocalMachine\
cd .\Root\
ls

Sorry for delay. Yes, these commands work in Powershell below is the output for last cmd

I just noticed you're running the command from the H: drive. Could you try running a turbo command from the C: drive? Is there anything special to the H: drive that could be relevant?

H drive is where I keep all my projects. Its an external drive that I use between my desktop and laptop

I tried running it from C drive and got same issue.

I'm at a loss as to why the upstream dependency would be failing to load the cert store. Do you have any issues/special configuration for setting up TLS connections with other programs?
One thing I'm curious about is if you get the same error with 1.12?

I don't know what was wrong. I did a clean install of windows and its working now.

@chris-olszewski  file is there and what i want to do is clone and run https://github.com/withastro/astro


[BUG] search.max_buckets is not evaluated correctly for terms agg

Describe the bug
The search.max_buckets setting (ref) is used to control the maximum number of aggregation buckets allowed in a single search response.
For terms aggregations the way in which the bucket count is calculated is that sub-aggregation buckets are counted first, and then if their parent bucket is pruned from the candidate list the sub-aggregation bucket count is then subtracted. This means that it is not really accurately counting the number of buckets, see reproduction section below for an example.
More broadly speaking, I'm not sure if this search.max_buckets setting is actually useful. I think the setting can have 2 uses:

Limit the response size of a given search request -- This isn't quite working correctly as shown by this issue
Stop bad aggregations from taking up too many resources -- Most aggregation types do not enforce this max_buckets setting at the shard level, it's only evaluated during reduce on the coordinator level which is after a lot of the resource intensive portions of the search request are already completed.

Somewhat related:

#12916

Related component
Search:Resiliency
To Reproduce

Go to '...'
Click on '....'
Scroll down to '....'
See error

Expected behavior
The following was done with the noaa opensearch-benchmarks workload but it's not specific to that data.
Set cluster setting:
{
    "persistent": {
        "search.max_buckets": 2
    }
}

This search request does not hit the max buckets limit
{
    "size": 0,
    "aggs": {
        "station": {
            "terms": {
                "field": "station.id",
                "size": 1,
                "shard_size": 1
            },
            "aggs": {
                "date": {
                    "terms": {
                        "field": "date",
                        "size": 1,
                        "shard_size": 1
                    }
                }
            }
        }
    }
}

Neither does this one
{
    "size": 0,
    "aggs": {
        "station": {
            "terms": {
                "field": "station.id",
                "size": 1,
                "shard_size": 1
            },
            "aggs": {
                "date": {
                    "terms": {
                        "field": "date",
                        "size": 1,
                        "shard_size": 2
                    }
                }
            }
        }
    }
}

However, this one does:
{
    "size": 0,
    "aggs": {
        "station": {
            "terms": {
                "field": "station.id",
                "size": 1,
                "shard_size": 2
            },
            "aggs": {
                "date": {
                    "terms": {
                        "field": "date",
                        "size": 1,
                        "shard_size": 1
                    }
                }
            }
        }
    }
}

In all 3 of these cases the response size on the coordinator is only 2 buckets.
Additional Details
Plugins
Please list all plugins currently enabled.
Screenshots
If applicable, add screenshots to help explain your problem.
Host/Environment (please complete the following information):

OS: [e.g. iOS]
Version [e.g. 22]

Additional context
Add any other context about the problem here.

search.max_buckets could be more treated as a circuit breaker construct which limits any bad aggregation query from taking up too many resources, specially memory. I have seen this working in favor of JVM heap utilization on clusters, preventing rogue query from taking the whole node down.
Coverage and accuracy is definitely an issue as pointed by @jed326, especially in case of pruning and should be addressed first.

Renaming this issue to focus on the bug specific to terms aggregations. I think there is still some work aside from that we can do to make the search.max_buckets setting more consistent across aggregation types but that can be a follow-up.


Bug: dimension value not being validated for empty strings

Expected Behavior
When adding a dimension to my metrics, I should get a warning if the dimension value is invalid aka an empty string ("") or undefined/null, and the dimension should not be added to the EMF blobs emitted by the utility.
Current Behavior
Currently the utility doesn't validate the input but only enforces types. In practice this means it's unlikely customers can pass undefined or null unless they're suppressing the warning, but can pass an empty string and generate an EMF blob that will have the invalid dimension.
Code snippet
import { Metrics } from '@aws-lambda-powertools/metrics';

const metrics = new Metrics();

export const handler = async () => {
  metrics.addDimension('FunctionName', '');
  metrics.addMetric('CustomMetric', 'Count', 1);
  metrics.publishStoredMetrics();
};

Steps to Reproduce

Run the code above
Observe that the EMF blob emitted has an empty dimension
Verify that the processed metric in CloudWatch does not include any dimensions

Possible Solution
We should: 1/ validate the input when adding a dimension, 2/ emit a warning if invalid, and 3/ don't add the dimension to the EMF blob
Powertools for AWS Lambda (TypeScript) version
latest
AWS Lambda function runtime
20.x
Packaging format used
npm
Execution logs
{
  "_aws": {
    "Timestamp":<PHONE_NUMBER>245,
    "CloudWatchMetrics": [
      {
        "Namespace": "default_namespace",
        "Dimensions": [
          [
            "service",
            "FunctionName"
          ]
        ],
        "Metrics": [
          {
            "Name": "CustomMetric",
            "Unit": "Count"
          }
        ]
      }
    ]
  },
  "service": "service_undefined",
  "FunctionName": "",
  "CustomMetric": 1
}

From the BelieveInServerless Discord server, a customer was having issues while passing a value typed as any which at runtime was a number and that caused the same behavior described above.
Another +1 for runtime validation.

Ok, let's do it 🙂

import { Metrics } from '@aws-lambda-powertools/metrics';
class EnhancedMetrics extends Metrics {
addDimension(name: string, value: string | undefined | null): void {
if (!value || value.trim() === '') {
console.warn(
Invalid dimension value provided for "${name}". Skipping dimension.
);
return; // Skip adding the invalid dimension
}
super.addDimension(name, value);
}
}
const metrics = new EnhancedMetrics();
export const handler = async () => {
metrics.addDimension('FunctionName', ''); // Invalid, will be skipped
metrics.addDimension('ServiceName', 'MyService'); // Valid, will be added
metrics.addMetric('CustomMetric', 'Count', 1);
metrics.publishStoredMetrics();
};


Draft for using conditional asserts by redirecting to a common method

This is an idea for a potential solution for #971.
I had an initial idea to use ByteBuddy, but then came up with this.
This allows to use ignoreWhen (the name of the method doesn't really matter) multiple times. Otherwise, we would be creating a new instance on every call to ignoreWhen and you can't reuse them. i.e. if you call once then the second time will be ignored.
e.g.
From one of the examples in the issue:
// more complex (if obj4 is negative should be -10, if positive should be 100, ignore zero)
assertThat(obj4)
    .ignoreWhen(i -> i < 0).isEqualTo(-10)
    .ignoreWhen(i -> i > 0).isEqualTo(100);

with the approach here it will work as excepted. Otherwise, it won't work because ignoreWhen will create a new object every time.
The approach in the PR allows doing that.
In addition to the implementation, I have also added some tests to see how this can be done. If you like the approach I can go ahead and implement it for the entire API and add the needed test methods to BaseTestTemplate.

I just thought of another idea that could reuse the doAssert methods. In theory we can simplify the Assumptions and SoftAssertions proxy to only intercept the doAssert methods and wrap the consumer and rethrow the appropriate exception.
In addition to that, we could even look into an option of providing a wrapper of the consumers in the current classes. Something similar to the TaskDecorator that Spring has.

So what I'm saying is defining ignoreWhen in AbstractAssert is not great, thinking out loud we could simply define it in a new interface (IgnorableAssert ?) and let the AbstractXxxAssert implement it. That way no API pollution.

We might give special attention to AbstractObjectAssert, it is probably a common superclass candidate for custom assertions. If we let it implement IgnorableAssert we might have a similar issue like in AbstractAssert.


Several Questions about Paper

Thank you for your excellent work! I have a few questions about the paper.

After using proxy distance, it is indeed possible to perform more robust distance estimation, but for inactive tracks, the overlap area between positive(same) and negative(different) matches is still large. How to solve the problem of difficulty of matching after occlusion.
I have seen different thresholds for active and inactive tracks in your previous version of the paper, but not in the latest version. Is the threshold still set like this?

Thank you very much!!

Hey and thanks for the questions!

Making it smaller could be addressed with several ideas, for example, you could try to use modal bounding boxes only and try to find correspondences between the modal bounding box and previous detections of a track. However, we did not investigate this idea further.
We still use different thersholds (see "Different handling of active and inactive tracks" in Sec. 3.2 of the paper), but we do not use this formula anymore :)
Hope those answers helped you!


[ibmTooltip]: Toggling on mobile device

Detailed description
While clicking on ibmTooltip on mobile device, tooltip is been toggled.
"carbon-components": "^10.20.0",
"carbon-components-angular": "^3.54.2"
Also, getting next error in console:

any updates?

Can you port fix into 3.x.x?


B 20116 app reducer redux form main

[!IMPORTANT]
Upstream

Integration PR

Warnings

:warning:
This PR does not include changes to unit tests, even though it affects app code.

  Generated by :no_entry_sign: dangerJS against 1a0b1ec1617b92c07cee00db15f009c390010139


Project name reference in invoice

It would be very useful for administrative purpose to have the project name reperence printed on the invoices

@nunopato could you look into this?

This was implemented already.


⚠ Processors has degraded performance

In 9ade999, Processors ($STATUS_URL) experienced degraded performance:

HTTP code: 200
Response time: 232 ms

Resolved: Processors performance has improved in 45e22e3.


Metrics for circuit breaker outlier detection

(This is used to request new product features, please visit https://discuss.istio.io for questions on using Istio)
Describe the feature request
Expose metrics about the number of pods evicted when the circuit breaker is triggered using outlier detection. I see that there is already a metric exposed when the connectionPool option is used istio_requests_total{response_code="503", response_flags="UO"}
Affected product area (please put an X in all that apply)
[ ] Docs
[ ] Installation
[ ] Networking
[ ] Performance and Scalability
[x] Extensions and Telemetry
[ ] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure

can you share more details?

Think this would be a good feature as well. Currently there isn't a metric that tells us when the circuit breaker for outlier detection trips.
Closest metric I can get is istio_requests_total{response_code="503", response_flag="UH"}. But that label "response_flag" with value "UH" is not unique to outlier detection being the cause of the issue.
I think what OP is requesting would be that the metrics for outlier detection will have the same metrics when the circuit breaker trips based on the connection pool, so it's response_flag is "UO" as well.

So I was snooping around the istio-proxy prometheus metrics endpoint, /stats/prometheus. It already exposes the metric.
envoy_cluster_outlier_detection_ejections_enforced_total{cluster_name="outbound|8000||httpbin.qa.svc.cluster.local"} 1
Think this might be useful to monitor for the outlier detection.
My current Istio version was outdated, updating it to ver 1.15.0 made the metric available.

@Danial968 I just upgraded istio to 1.15.0 but I still don't see those metrics. Is there any special config that you used in order to enable the outlier detection?

@reda-ayoub Don't think I used any special config, just did a fresh install in a test cluster. I checked the metric by port forwarding the istio-proxy's metric endpoint. http://localhost:15090/stats/prometheus


Minor issues in the Computer Graphics chapter

I have some suggestions for few minor changes I think could be made to the graphics chapter to make it more understandable:

[x] In section 12.2 Before the block interactives it would be good to explicitly say what directions negative and positive numbers will move the box in.

[x] The first interactive is quite confusing when you start using it, because of how the camera moves and how it is difficult to understand whether you are moving or if the block is moving.
I'm not sure how or if this actually needs to be changed in any way (since it already explains in the description that the camera follows the box) but if anyone has any ideas it could be worth exploring them! Maybe adding visible axes?

[ ] In section 12.2 starting from the "Swapping coordinates" interactive the idea of how the image is being rotated around the x and y axes needs to be explained more clearly. When I first read it I thought the word "rotated" had been used incorrectly and it should have been "mirrored".
I think some of this part needs re-writing and maybe should be divided into "rotation" and then "swapping coordinates. The interactive chould have 3 phases - rotating around x axis only, rotating around y axis only, and then both.

[ ] In section 12.2.3 3D Transforms the word "vector" is used without being defined or explained. In this context it is about using vectors for translation (not vector graphics). The concept of a vector should probably be explained here.

In section 12.2 starting from the "Swapping coordinates" interactive the idea of how the image is being rotated around the x and y axes needs to be explained more clearly. When I first read it I thought the word "rotated" had been used incorrectly and it should have been "mirrored".
I think some of this part needs re-writing and maybe should be divided into "rotation" and then "swapping coordinates. The interactive chould have 3 phases - rotating around x axis only, rotating around y axis only, and then both.

It's not even both, it's a y-axis rotation (i.e mirror/flip), then a z-axis rotation. It's definitely not a "simple rotation transformation"

In section 12.2 starting from the "Swapping coordinates" interactive the idea of how the image is being rotated around the x and y axes needs to be explained more clearly. When I first read it I thought the word "rotated" had been used incorrectly and it should have been "mirrored".
I think some of this part needs re-writing and maybe should be divided into "rotation" and then "swapping coordinates. The interactive chould have 3 phases - rotating around x axis only, rotating around y axis only, and then both.

This was probably a misinterpretation by the original author:
The shape in the interactive used to be an arrow - which was symmetrical about the y axis.
When you swap x and y of a shape that's symmetrical you flip it about the x=y axis, which – if it's symmetrical – happens to look exactly the same as a rotation.

Now that the shape is asymmetrical it's obvious that a rotation isn't what the text describes. We need to find a new way of telling the user to change the coordinates so that the shape rotates and doesn't flip

In section 12.2.3 3D Transforms the word "vector" is used without being defined or explained. In this context it is about using vectors for translation (not vector graphics). The concept of a vector should probably be explained here.

Vectors are first used early on in 12.2.1 but are only named in teacher notes. Perhaps instead of a pseudo-explanation of a matrix within the content we should have proper jargon busters for Matrix and Vector

Another issue:

[ ] The content mentions point (3, 1) as the rightmost corner of the shape. This refers to the original arrow. The rightmost point of the current shape is (2, 3)

Vectors are first used early on in 12.2.1 but are only named in teacher notes. Perhaps instead of a pseudo-explanation of a matrix within the content we should have proper jargon busters for Matrix and Vector

A jargon buster would be great for this

Now that the shape is asymmetrical it's obvious that a rotation isn't what the text describes. We need to find a new way of telling the user to change the coordinates so that the shape rotates and doesn't flip

Further to this: A clockwise rotation of 90 degrees that the text intends can be obtained by multiplying the points by the matrix:
| 0 1|
|-1 0|
(x, y) -> (-y, x)
wikipedia
i.e. Swap the coordinates but multiply the new x coordinate by -1


Display issues when using Cluster Manager to exec into Windows pod

What kind of request is this (question/bug/enhancement/feature request): Bug
Issue description:
When using the UI to exec into a Windows pod commands like dir cause screen artifacts and unusual cursor locations
Environment:
Replicated on RKE provisioned Windows cluster v1.19.3
Rancher v2.5.5
Steps to reproduce (least amount of steps as possible):
Run mcr.microsoft.com/dotnet/core/samples:aspnetapp
Exec into pod using Cluster Manager
Run dir
Run cls
Actual behavior:
Cursor at unexpected position after dir, and cls doesn't clear the screen
Expected behavior:
Cursor should be at the bottom with the matching prompt after dir.  Screen should be cleared after cls
Additional notes:
Execute shell doesn't work at all for Windows pods in Cluster Explorer.
gz#14892

Internal reference: SURE-2766

Most likely caused by the terminal emulation

Along with seeing what the component can do with Powershell, we need a way to spin up Windows nodes. Maybe Azure since Digital Ocean & Linode don't have that option...

Closing - won't fix.


patches_vrn1

Hi,
I'm working on archaeological patches, starting with prehispanic architecture.
Also, I have added a map to visualize the patches.
Cheers!
Diana

Nice jobs ^^


"platformio lib" doesn't show source url

platformio lib search json shows you only the vague descriptions from library.json files, with library "64" for instance being, ""Benoit Blanchon": An elegant and efficient JSON library for embedded systems"
platformio lib show 64 won't show you anything at all until you've installed it.  This is... not very nice.  Where is it going to be installed from?  What code is this?
Even after installing it, ``... show 64``` still only shows the author's provided url, not the source url at all.  In this case for instance, you get:
(.env27)karlp@teros:~/src/hoho$ platformio lib show 64
Json
----
Authors: Benoit Blanchon http://blog.benoitblanchon.fr
Keywords: json, rest, http, web
Frameworks: arduino
Platforms: atmelavr, atmelsam, timsp430, titiva, teensy, freescalekinetis, ststm32, nordicnrf51, nxplpc, espressif, siliconlabsefm32
Version: ab2502f7b8

An elegant and efficient JSON library for embedded systems

(.env27)karlp@teros:~/src/hoho$

Benoit's blog is interesting, but it's not useful to say where the code is coming from.  The git version is included, but it should be including the source url, or some form of the entire "repository" section of the library.json block.

---
Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/29559562-platformio-lib-doesn-t-show-source-url?utm_campaign=plugin&utm_content=tracker%2F2014790&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F2014790&utm_medium=issues&utm_source=github).

How about http://platformio.org/#!/lib/show/64/Json ?
Yes, CLI isn't informative. Do you have propositions?

How about platformio lib info %ID% ? I hope that in PlatformIO 3.0 we will allow to use names instead IDs.

I'd like show or info to be a single command, showing info including the installed state if possible, I don't see any real benefit in having a separate command to see the full details of a package that has been installed vs one that hasn't.
Thanks for the prompt response!

See example:

http://docs.platformio.org/en/latest/userguide/lib/cmd_show.html


net/smtp: Add 'From' header to smtp/example_test.go

I was following the ExampleSendMail example to send mails, but it showed the error of send mail error: 550 MIME message is missing 'From' header. And I see the document of smtp.SendMail, it says

... The msg headers should usually include fields such as "From", "To", "Subject", ...

And it works for me after I added the 'From' header in the msg.
Note: The SMTP server I used is SendGrid.

@googlebot I signed it!


Perses Refactor

I'm going to use this PR to keep track of refactoring tasks (which will help with the API design) and link PRs back to this issue so we can have everything in one place.

[ ] remove * imports
[ ] import the openeye toolkit in the functions/classes that use it (instead at the top of the time)
[ ] format code with black and enforce formatting on the CI
[ ] remove utils folder

Feel free to mention more!

@mikemhenry Sounds great!
It's best if we could go with small, easily reviewable PRs that @dominicrufa @jaimergp and I can help review and get merged quickly.
We also need to get some outstanding PRs (#748 especially, maybe others from @dominicrufa and @zhang-ivy) merged ASAP! @dominicrufa @zhang-ivy can you get those in ASAP? Tap @mikemhenry to help if needed.
We should close any other outstanding PRs if they're not going to be merged in before the refactor.

Hello!
Reassessing how much output goes to debug/info/warning might be a low effort improvement, currently so much is printed out that it’s hard to follow


Ability to specify Authorization header

Hi!
Ws seems very cool and useful, thank you!
This pr adds the ability to specify authorization header, like
curl -H 'Authorization: Bearer $TOKEN' ...

please consider merging!
Best wishes,
Vladimir

It seems browsers don't allow users to tweak headers in websocket requests.. (they're not exposed in the WebSocket object) so seems a bit off-standard, isn't it?  Is it still useful for server-2-server comms?


"sleep" was never awaited - runtime warning

When I try to fetch data on some asins using:
api.query(asins, stats=None, domain='US', history=True,
offers=None, update=None, to_datetime=True,
rating=True, out_of_stock_as_nan=True, stock=False, product_code_is_asin=True)
I am getting the error below:
RuntimeWarning: coroutine 'sleep' was never awaited
  asyncio.sleep(tdelay)

Also, the console just outputs every second that there are no tokens left instead of waiting for tokens to fill up.
Any idea on what is going on?

Are you using Keepa 1.3.0 or higher?
On 1.3.0, the async and sync interfaces were separated, so you can use the synchronous interface to not have those warnings.
If you wish to use the async interface just create an instance of keepa.AsyncKeepa('ENTER_ACTUAL_KEY_HERE')
I believe you can add wait=True to your parameters for it to wait.

Yes, I am using the latest API. making wait=TRUE helped with the error, but still I get a print every second of how many seconds wait to fill the tokens.
Below what I am doing in a nutshell. Not very familar with async.
accesskey = '' # enter real access key here
api = keepa.Keepa(accesskey)
asins = ['', '', '', '' ...] #long list of asins here

        products = api.query(asins, stats=None, domain='US', history=True,
                    offers=None, update=None, to_datetime=True,
                    rating=True, out_of_stock_as_nan=True, stock=False,  product_code_is_asin=True, wait=True)

Depending on your keepa subscription you will have a larger amount of tokens.
If you query the entire list of asins in one go, you might consume all your available tokens in one go (you can even be below zero).
Does the issue still happen for, let's say, a list of 2 or 3 asins?

I understand that. But the API in the past consumed all the tokens, and would yield a single message saying: "Waiting 600 seconds for new tokens". And waited. Which was fine.
Now it sends multiple messages:
"Waiting 600 seconds for new tokens"
"Waiting 599 seconds for new tokens"
"Waiting 698 seconds for new tokens"
etc
etc

I have no idea

I was still having this issue, so I think it should be re-opened.
I fixed the problem by changing https://github.com/akaszynski/keepa/blob/d75a0da77a5639777dd8c9dc4139844137c59d9d/keepa/interface.py#L415
to time.sleep.  I don't think async.sleep does anything in the synchronous keepa class


[feat][sql] Support metadata store url

This refers to #18209 and part of the commits is included in #18207.
Although it seems hard to integrate with the RocksDB metadata store backend which is the original purpose for this patch as described in #18209, this patch migrates Pulsar SQL dependency of metadata store to the PIP-45 proposed model. And now we can use etcd metadata store backend at least and reduce dependencies to legacy logics.
cc @merlimat @gaoran10 @nicoloboschi @Jason918 @lhotari
Documentation

[ ] doc
[ ] doc-required
[x] doc-not-needed
[ ] doc-complete

Matching PR in forked repository
PR in forked repository: https://github.com/tisonkun/pulsar/pull/12

/pulsarbot run-failure-checks

/pulsarbot run-failure-checks

/pulsarbot run-failure-checks

cc @Jason918 @codelipenghui I think this patch is ready for merge now :)


Forwarding option will not stick

I cannot get forwarding under plugins to work. Every time I save the configuration it reverts back to blank, and the slider is to the left (off position).
Win10 x64, using latest version 0.4.3

I seem to be experiencing the same problem. Sometimes I can get it to save and other times I can't.
Domains will only save and update if I change the resolvers which won't save but instead revert back to their previous setting. Similarly I've managed to update the resolver but only by making a change to the domains which sometimes also revert back.
Trying multiple combinations, it seems completely random whether or not you can get the values to save or not.
Also Windows 10 x64 tested using the x86 and x64 Simple DNSCrypt 0.4.3

Thanks for reporting, i will check this.


iOS App Crash . The crash info is SIGSEGV(11),and some info is _Z7isasciii

Environment
Environment:
OS: macOS High Sierra 10.13.2
Node: 9.4.0
Yarn: 1.7.0
npm: 5.6.0
Watchman: 4.9.0
Xcode: Xcode 9.4 Build version 9F1027a
Android Studio: 3.0 AI-171.4408382
Packages: (wanted => installed)
react: ^16.3.0-alpha.1 => 16.3.2
react-native: 0.54.4 => 0.54.4
Description
I got the crash info with error stack:
 0	libobjc.A.dylib objc_retain + 16 1	ewelinkDemo isascii(int) + 3569736 2	libsystem_blocks.dylib _Block_copy + 140 3	libdispatch.dylib __dispatch_Block_copy + 68 4	libdispatch.dylib _dispatch_async$VARIANT$mp + 56 5	ewelinkDemo isascii(int) + 3567732 6	CoreFoundation __signalEventSync + 216 7	CoreFoundation __cfstream_solo_signalEventSync + 244 8	CoreFoundation __CFStreamSignalEvent + 308 9	CFNetwork SocketStream::dispatchSignalFromSocketCallbackUnlocked(SocketStreamSignalHolder*) + 64 10	CFNetwork SocketStream::socketCallback(__CFSocket*, unsigned long, __CFData const*, void const*) + 148 11	CFNetwork SocketStream::_SocketCallBack_stream(__CFSocket*, unsigned long, __CFData const*, void const*, void*) + 88 12	CoreFoundation ___CFSocketPerformV0 + 1336 13	CoreFoundation ___CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__ + 24 14	CoreFoundation ___CFRunLoopDoSource0 + 88 15	CoreFoundation ___CFRunLoopDoSources0 + 176 16	CoreFoundation ___CFRunLoopRun + 1044 17	CoreFoundation CFRunLoopRunSpecific + 436 18	Foundation -[NSRunLoop(NSRunLoop) runMode:beforeDate:] + 300 19	ewelinkDemo isascii(int) + 3572528
I think app was crash in the isascii function,but I don't know the reason. Please help ,thanks!!

I saw the app crash ,when send a http request , in my log. And it has CFNetwork in the error stack.So I think it could happen in RCTnetwork


"Fortnite was not started correctly" when injecting cobalt on latest  (26.00)

I think this is due to the Push Widget pattern being outdated, as i tried PlataniumV2 and when injected it says "third pattern outdated", i checked plataniumv2's code and the third pattern is push widget

first of all don't use latest on private servers because afaik you WILL get hwid banned

first of all don't use latest on private servers because afaik you WILL get hwid banned

i suppose he would know the consequences + dont spread rumors lmfao this is false

Resolved


Add import cycle detection

Since we do not use real stack, it does not seem obvious for me to detect a cycle of length longer than 2.

Cycle reporting added

Thanks for working on this. I had originally intended for the map that is being passed down to be used for import cycle detection. If it's not used, then please remove it, a slice is probably the better solution.
Please also add a test.

No problem, I will add tests and remove original stack tomorrow.
It will increase complexity of checking to O(n), but people with very big dependency graph will have bigger problems than that.

I doubt any import chain will be long enough that checking a slice in O(n) is going to pose a problem...

That was why I added the map in the first place. Why not use the map, the
code is all there, just no check before recursing.
If a cycle is detected just return an error. We can say how the cycle was
formed, but we can do that later as an improvement.
On Thu, 14 May 2015 08:43 Kamil Kisiel<EMAIL_ADDRESS>wrote:

I doubt any import chain will be long enough that checking a slice in O(n)
is going to pose a problem...
—
Reply to this email directly or view it on GitHub
https://github.com/constabulary/gb/pull/84#issuecomment-101839765.

I've added tests for different cycle lengths (to cover it correctly from algorithm perspective) so we have 1, 2, 4.
1 - edge case
4 - to be sure that we are not stuck on detecting just the cycle of length 2 (I can imagine people forgetting about cycles longer than 2)
I know that the way of testing if goroutine is not the nicest one, but using time.AfterFunc and asserting after a second did not work for me.
Also, if somebody know how to do error checking better, please teach me, I had to be sure that I am getting my error, not some other (like package not found).

Thanks for fix this.
Sorry, the test is not acceptable. Testing with time is unreliable. I think putting a panic if the stack size grows above say 100 would be a decent way of testing this.
Please drop the test and I'll merge this. Also edit the issue description and add the text
 Fixes #83

No problem, sir!