Terminal warning running code when there is an apostrophe's in the program path

@martinohanlon commented on Thu Feb 07 2019
Environment data

VS Code version: 1.30.2 (user setup)
Extension version (available under the Extensions sidebar): 2019.1.0
OS and version: Windows 10 version 1803
Python version (& distribution if applicable, e.g. Anaconda): 3.6.4
Type of virtual environment used (N/A | venv | virtualenv | conda | ...): None
Relevant/affected Python packages and their versions: n/a

Expected behaviour
When I run a Python program using Ctrl F5 I dont expect to see an error.
Actual behaviour
When I run a Python program using Ctrl F5 I see the error / warning in the terminal.
PS C:\Users\Martin O'Hanlon-LT> cd 'c:\Users\Martin O'Hanlon-LT\Documents\temp'; ${env:PYTHONIOENCODING}='UTF-8'; ${env:PYTHONUNBUFFERED}='1'; & 'C:\Users\Martin O''Hanlon-LT\AppData\Local\Programs\Pyt:\Users\Martin O''Hanlon-LT\AppData\Local\Programs\Python\Python36\python.exe' 'c:\Users\Martin O''Hanlon-LT\.vscode\extensions\ms-python.python-20lient' '--host' 'localhost' '--port' '62982' 'c:\Users19.1.0\pythonFiles\ptvsd_launcher.py' '--default' '--client' '--host' 'localhost' '--port' '62982' 'c:\Users\Martin O''Hanlon-LT\Documents\temp\helloworld.py'                                                                                ppData\Local\Programs\Python\Python36\python.exe' 'c:\>> cd 'c:\Users\Martin O'Hanlon-LT\Documents\temp'; ${env:PYTHONIOENCODING}='UTF-8'; ${env:PYTHONUNBUFFERED}='1'; & 'C:\Users\Martin O''Hanlon-LT\Alocalhost' '--port' '62985' 'c:\Users\Martin O''HanlonppData\Local\Programs\Python\Python36\python.exe' 'c:\Users\Martin O''Hanlon-LT\.vscode\extensions\ms-python.python-2019.1.0\pythonFiles\ptvsd_launcher.py' '--default' '--nodebug' '--client' '--host' 'localhost' '--port' '62985' 'c:\Users\Martin O''Hanlon-LT\Documents\temp\helloworld.py'      NBUFFERED}=1; & C:\Users\Martin'.
Set-Location : A positional parameter cannot be found that accepts argument 'Hanlon-LT\Documents\temp; ${env:PYTHONIOENCODING}=UTF-8; ${env:PYTHONUNBUFFERED}=1; & C:\Users\Martin'.
At line:1 char:1
+ cd 'c:\Users\Martin O'Hanlon-LT\Documents\temp'; ${env:PYTHONIOENCODI ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : InvalidArgument: (:) [Set-Location], ParameterBindingException
    + FullyQualifiedErrorId : PositionalParameterNotFound,Microsoft.PowerShell.Commands.SetLocationCommand

Steps to reproduce:

Create a folder with an apostrophe ' in the name
Save a Python program to that folder
Run the Python program

Logs
Output for Python in the Output panel (View→Output, change the drop-down the upper-right of the Output panel to Python)
[blank]

Output from Console under the Developer Tools panel (toggle Developer Tools on under Help; turn on source maps to make any tracebacks be useful by running Enable source map support for extension debugging)
[blank]

@d3r3kk commented on Thu Feb 07 2019
Upstream to VS Code itself, shell quoting for paths sent to the debugger provider.

@weinand
Not sure how this is caused by the extension, the extension is passing the information to the debugger (via the protocol ) to launch the debugger in the terminal.
At this point it is VSC that sets the cd command, i.e. problem lies with VS Code not the extension.
Here's the code:
https://github.com/Microsoft/vscode/blob/314cc521d8ce0c55773850ef520095afde33a62c/src/vs/workbench/parts/debug/node/terminals.ts#L365

@DonJayamanne since we do not know how an extension is implemented, we let the extension author investigate issues like this first. If you are sure that an issue is not an extension issue, just let us know and we take the issue back.

@weinand when I follow these steps, I get:
$ C:/Users/Megan/AppData/Local/Programs/Python/Python39/python.exe c:/Users/Megan/vscode/.vscode/notebooks/meg's/test.py

C:/Users/Megan/AppData/Local/Programs/Python/Python39/python.exe c:/Users/Megan/vscode/.vscode/notebooks/meg's/test.py
C:\Users\Megan\AppData\Local\Programs\Python\Python39\python.exe: can't open file 'c:\Users\Megan\vscode.vscode\notebooks\megs\test.py
C:\Users\Megan\AppData\Local\Programs\Python\Python39\python.exe c:\Users\Megan\vscode.vscode\notebooks\megs\test.py': [Errno 22] Invalid argument

@meganrogge I do not quite understand what you did to verify my fix, but your result from above suggests that you did not use PowerShell.
To recapitulate you have to:

ensure that you use PowerShell in the integrated terminal,
install the Python extension
either create a launch config for running a Python program or open a Python program in the editor
press "Ctrl F5" to "Run Without Debugging".

In the integrated terminal you should see something similar to the PowerShell output from the initial comment. The fix should escape the problematic ' character in the "cd" command by doubling it.


Failed assertion while executing get_inputs ABI transformation test (clk=17) on VM

Error:
FailedAssertion { clk: 17, err_code: 0, err_msg: None }

Somewhere in the following code:
...
export."miden_tx_kernel_sys::get_inputs"
    mem_load.0x00000000
    push.16
    u32wrapping_sub
    dup.0
    dup.0
    push.2147483648
    u32and
    eq.2147483648
    assertz
    add.8
    u32assert
    dup.0
    u32mod.16
    dup.0
    u32mod.4
    swap.1
    u32div.4
    movup.2
    u32div.16
    exec.::intrinsics::mem::load_sw
    dup.1
    dup.0
    push.2147483648
    u32and
    eq.2147483648
    assertz
    add.12
    u32assert
...

To pinpoint the failing op I'm exploring the following options:

Pull out a better error message from the VM;
Execute the VM via the iterator and print the VM state after every op.

@bitwalker I confirmed this is caused by https://github.com/0xPolygonMiden/compiler/issues/174

This is fixed by #242


kstars - INDI Drivers directory

when starting kstars it will popup this error message:
Unable to find INDI Drivers directory: /usr/share/indi
Please make sure to set the correct path in KStars configuration

i must have assumed that the software is broken because of that, maybe it is just a issue for computer-controllable telescope stuff then.
thanks


Constructor issue

I have just used npm update apn to 2.1.1 version and while I did the code changes ... it seems that this happens when trying to run a test push.
TypeError: apn.Provider is not a constructor

Tried uninstalling then installing again, maybe some dependencies were not there. Still same thing. Am I missing something ?
Update, looking into the node_modules/apn/lib folder I can see it's not corresponding to the one in this branch.
Update 2. Nevermind, seems to have been a problem with my package.json configuration.

What is the solution?

@devonauts I deleted the "apn" property from my package.json file and then ran the install script "$ npm install apn --save" again, re-ran my app, and everything was fine. Didn't change anything in the code itself. Hope that helps.


Update organization issue labels

Update the tools in /labels to work from a JSON file configured in that folder.
Modify tools to allow fetching and uploading.
Regularize all of the current repos' labels.

Done. Kinda rewrote all of the tools - and readme - in the process...


Electron page

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)
[x] My pull request targets the master branch of freeCodeCamp.
[x] None of my changes are plagiarized from another source without proper attribution.
[x] My article does not contain shortened URLs or affiliate links.

Thanks for this non-trivial contribution! And good catch with the overzealous translations!


API Product definition cannot be updated

Description:
Update API Product definition option doesn't work.
Steps to reproduce:

Created a product using Pizzashack and Petstore API
Go to definition tab of the Product and try to update it.

Need to remove the UI edit buttons as we don't support this from core level.


Fix global declaration processing

To fix our playground typescript declarations

Please make sure to label your PR with "bug", "new feature" or "breaking change" label(s).
To prevent this PR from going to the changelog marked it with the "skip changelog" label.

Please make sure to label your PR with "bug", "new feature" or "breaking change" label(s).
To prevent this PR from going to the changelog marked it with the "skip changelog" label.

WebGL2 visualization test reporter:
https://snapshots-cvgtc2eugrd3cgfd.z01.azurefd.net/refs/pull/15792/merge/testResults/webgl2playwright/index.html

Visualization tests for WebGPU (Experimental)
https://snapshots-cvgtc2eugrd3cgfd.z01.azurefd.net/refs/pull/15792/merge/testResults/webgpuplaywright/index.html


Add more base styling to accordion pattern

This PR adds some more base styling to the accordion pattern

Bottom border on all but the last accordion section
Adjust spacing within the accordion toggle to increase target area
Right align the accordion icon

I'm not sure why the icons aren't showing up in the nightshade repo at the moment, but the little black square is where it would be.

@ckeisato Reviewed the PR. All that's necessary to fix so we can merge is ironing out those two magic numbers and setting up the accordion-toggle-target area with flexbox. The details can wait until FF.

@ckeisato One small fix but otherwise DTM.


docs: added about signing gpg to old commit

Description
Adding how to signing gpg to old commit.
Checklist:

[x] Securely signed commits
[ ] Component(s) with PHPDoc blocks, only if necessary or adds value
[ ] Unit testing, with >80% coverage
[x] User guide updated
[ ] Conforms to style guide

Thank you.
By the way, is there anyone who uses git commit -S option in real life?
I've never used the option.

Thank you.
By the way, is there anyone who uses git commit -S option in real life? I've never used the option.

@kenjis Yes, -S will be not used if git config --global commit.gpgsign true and git config --global user.signingkey 3AC5C34371567BD2 already set. According to what I have given a note regarding this PR. I before never use too on my old repos, and recently applied in repo community based.


medals: Add basic favs functionality

very basic, only adds the button and that adds and deletes them from db, no Favorite medals tab yet, im waiting for tanza to do packs to see how its done so i can do the same for favs <:

there's a pr for it please review!!
anyway this looks good to me, i think you should use nLoggedIn or something though?

fixed conflict issue with functions.js


ignoring remove_lines_between_uses fixer is useless

Having this .php_cs file...
<?php

return Symfony\CS\Config\Config::create()
    // use SYMFONY_LEVEL:
    ->level(Symfony\CS\FixerInterface::SYMFONY_LEVEL)
    // and extra fixers:
    ->fixers(array(
        'concat_with_spaces',
        'multiline_spaces_before_semicolon',
        'short_array_syntax',
        '-remove_lines_between_uses',
        '-empty_return',
        '-phpdoc_var_without_name',
        '-phpdoc_to_comment',
    ))
    ->finder(
        Symfony\CS\Finder\DefaultFinder::create()
            ->in('src/')
            ->in('tests/')
    )
;

all spaces between my use statements are removed, even if the fixer remove_lines_between_uses are explicitly disabled.
After debugging a little bit the application, I've discovered that there is a fixer that is not doing what really has to do.
From the documentation...

single_line_after_imports [PSR-2]
Each namespace use MUST go on its own line and there MUST be one blank line after the use statements block.

This fixer is removing my empty lines, and it shouldn't.

Hi thanks for reporting,
could you provide the following;
$ php -v
$ php-cs-fixer -v

I'm using version 1.11

@mmoreram please check out #2077 ;)


[BUG]: drizzle-kit instrospect command generates syntax error on varchar column types

What version of drizzle-orm are you using?
0.32.0
What version of drizzle-kit are you using?
0.23.0
Describe the Bug
When exporting the db schemas and relations from a Postgres DB with the drizzle-kit introspect command, the schema.ts output file recognices two syntax errors: 1) when defining the length of a varchar column type, the file has an extra bracket ( '[' ) and an extra parenthesis ( '(' ) back to back, eleminating these characters solves the syntax error. 2) when defining a default value for a varchar type column, the ::character_varying notation is marked as a syntax error, erasing this part of the default value expression solves the syntax error (the end result would be: someColumnDefinition.default("")).
Expected behavior
I think the expected behaviour would be the one already working, but without the syntax errors. I don't know if the ::character_varying should be imported from drizzle-kit, but the intellisense does not provide any type of autocomplete or import suggestion for that part of the expression.
Environment & setup
turborepo 2.0.5, working in development mode for the time being.

Updating now to give it a try!


[fix][doc]: add switch task demo

close #8029

@QuakeWang Thanks.I had fixed those problems.

I had fixed those problems.

I find out we still have discussion in https://github.com/apache/dolphinscheduler/pull/10247#discussion_r882268874

I find out we still have a discussion in #10247 (comment) and I do not have much experience for switch tasks. Maybe you guys should discuss on it

What do you think about it?Do you have more suggestions? @QuakeWang

I solve some upstream change in branch dev

PTAL @zhongjiajie


Revise reduce database size

Description

Fixed SQL queries as compression feature is disabled by default for hypertables in the UMH.
Sample commands for umh_v2 are added.
All commands are executed from the db console and are completed successfully.

Related issues
close united-manufacturing-hub/MgmtIssues/issues/1335
Checklist
You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.

[x] I have read the contributing guidelines and the code of conduct.
[x] I have followed the documentation style.

Additional information
I refered the following docs:

https://docs.timescale.com/api/latest/compression/alter_table_compression/
https://docs.timescale.com/api/latest/compression/add_compression_policy/
https://docs.timescale.com/api/latest/data-retention/add_retention_policy/

Waiting for @DaruZero to review first


Add a formatTimeOffset method

Ref #391
Another go at formatRelativeCount from #389.

It has the fix-205-format-duration branch merged in
It's in the duration module
I've renamed it to formatTimeOffset, which I think is a bit better (but naming is still hard).
It uses formatMessage and Globalize.plural rather than my hacky alternatives
I've included a skeleton implementation of the formatDuration function as per #205 implemented using my formatTimeOffset method

Also I've created this as a pull request against master because otherwise the diff was massive and you couldn't really see what I'd done. I understand that you consider formatDuration to be the real goal here and so may chose to merge this in to fix-205-format-duration (or not at all - but I like to be optimistic).

Thanks for your new PR.

Also I've created this as a pull request against master...

Yeap, better having this PR to compare against master.

It's in the duration module

Ok for now. Let's rename it "relative-time". If this module doesn't add too many bytes, it could live inside the existing date module.

It has the fix-205-format-duration branch merged in
I've renamed it to formatTimeOffset, which I think is a bit better (but naming is still hard).
It uses formatMessage and Globalize.plural rather than my hacky alternatives
I've included a skeleton implementation of the formatDuration function as per #205 implemented using my formatTimeOffset method

Updates... I have updated our API according to what we discussed (https://github.com/jquery/globalize/pull/389#issuecomment-73994259). I've closed #205 in favor of the clean #391. I've rebased my old fix-205-format-duration branch on top of up-to-date master, made the changes according to #391 and pushed it into a new branch called fix-391-relative-time.
Can you rebase your changes on top of fix-391-relative-time please? Use .formatRelativeTime() and relativeTimeFormatter() names instead of your custom-named .formatTimeOffset(). Note, you don't need to implement anything based on Date instances for now (if you don't want to). Keep your implementation based on (number, unit). We can add Date instance support in upcoming commits.

I've done this based on fix-391-relative-time now. Let me know what you think?

Awesome. I've scanned through your code and saw you got the spirit. I will do a better review soon (couple of days).
A quick comment though, make sure you follow jQuery's style guide.

I have left comments inline. Overall looks great. Todo items:

[ ] Fix review comments;
[ ] Make sure code follows jQuery coding style.
[ ] Update README.md accordingly.

Ooops didn't fully understand the git command I was typing and accidently deleted the remote branch.
I think I've covered most of your comments now.

Moving a question about maximumWordOffset option up here.
I can imagine a use case where there's a preference for "1 day ago" over "yesterday". But, is there any use case where one wants yesterday, but not before yesterday? I'm wondering whether or we should use an offset or a boolean (e.g., { useCustomaryWords: false }).

I only speak English so I wouldn't really like to comment on whether there are some circumstances where yesterday is acceptable and before yesterday is not. I suspect it might be very subjective I don't if for example it might be considered more archaic in some languages.
Also I suspect that if some people were implementing a count down they might be tempted to do: "in 2 seconds", "in 1 second", "in 0 seconds", but probably more people would use now for the last item. I don't feel that I can make decision for them though. (Which I've just realised would fall out of my implementation by passing -1)
I think maximumWordOffset provides that kind of flexibility with out making it significantly more complex than passing a boolean.

@jzaefferer, @scottgonzalez do you have any opinion about it 👆?

@mbirtwell one more README update please. On "Pick the modules you need", there's a table where we need to include relative-time as well. Its gzipped size is 0.7KB.

About maximumWordOffset, I tried to benchmark the API of other related libraries. But, useless.

twitter-cldr, Rails, moment.js, and $.timeago don't have such option.
google closure does, but by using different methods. Lots of them actually. Too complicated.

But, is there any use case where one wants yesterday, but not before yesterday? I'm wondering whether or we should use an offset or a boolean (e.g., { useCustomaryWords: false }).

I don't think English has such words. Do you have examples of languages that do? We can try to find native speakers of those languages.

Portuguese has a customary word for "the day before yesterday". I would either use all of them or none at all. German has words for days -2 and 2, which @jzaefferer could express his thoughts.
I think if we don't have a use case, we should favor the simpler option, which is the boolean...

I think if we don't have a use case, we should favor the simpler option, which is the boolean...

Definitely. Let's see what @jzaefferer says (he told me the other day that he'd be away through the end of the week).

Ok and thanks.

@mbirtwell, I've talked with @jzaefferer and he confirmed he doesn't see a case for using a customary word for yesterday and not for before yesterday (similarly in future forms).
Unless you have any different thoughts, let's change the maximumWordOffset into a boolean useCustomaryWords that defaults to true and must be set false to skip the words.

We also need to update examples accordingly. One simple example demonstrating its use is enough.

In the case that useCustomaryWords is false should formatRelativeTime of 0 days output "today" or "in 0 days" or "0 days ago", or fail completely. I feel like if we were to choose "today" as the answer it might make useCustomaryWords a bit misleading but at the same time it is probably what most people want most of the time.

I think of "tomorrow" for options.useCustomaryWords === undefined || options.useCustomaryWords and "in 1 day" for options.useCustomaryWords === false. But, I have no idea how to differentiate "in 0 days" or "0 days ago"... Any ideas?

We also need to update https://github.com/jquery/globalize/blob/master/src/build/node-main.js by including relative-time module.

TODO:

Convert maximumWordOffset option into the boolean useCustomaryWords form.
Update examples.
Inlcude relative-time module in ./src/build/node-main.js.

Alright I agree differentiating between in 0 days and 0 days ago is a new problem, which neither approach solves.
But still it is quite likely that people who do not want to use tomorrow still want to use today. We could provide: { useCustomaryWordsForNonZero: true|false, forZero: "past"|"future"|"customary" } as options with both defaulting to enabling customary. Of course having one as a boolean and the other as a string is a bit ugly we could go further: { forNonZero: "numeric"|"customary", forZero: "past"|"future"|"customary" }

Alright I agree differentiating between in 0 days and 0 days ago is a new problem, which neither approach solves.

I've add it to our TODO list above.

But still it is quite likely that people who do not want to use tomorrow still want to use today

If this it true, I would stick with your initial maximumWordOffset option form instead.

After thinking and scratching for awhile with maximumWordOffset vs useCustomaryWords and how to distinguish "in 0 days" vs. "0 days ago".

"in 0 days" vs. "0 days ago"

Your proposal forZero: "past"|"future"|"customary" seems very sane. I would slightly change it to "zeroDirection": "past"|"future" though (or even with a simpler name "zero": "past"|"future"). Note some units lack the "customary" form for 0, e.g., "hour", "minute", ... Also set "past" as default (I don't have a preference, just guessed one).

maximumWordOffset vs useCustomaryWords

useCustomaryWords can still be used the way we initially thought about it.

For the name of the zeroDirection option what about zeroTense or tenseForZero. I don't like just zero I think that's a bit unclear. Also using a option like this still leaves us with needing an option to control whether or not we prefer a customary word for 0 to a numeric form, which I think should be controllable separately from whether we use customary words for other numbers.

zeroTense seems fine to me.

Also using a option like this still leaves us with needing an option to control whether or not we prefer a customary word for 0 to a numeric form, which I think should be controllable separately from whether we use customary words for other numbers.

Why do you think this needs to be controlled separately?

I don't think I'd ever want "in 0 days" or "0 days ago". I think most people will want to use "today" or switch to a more granular unit when days are less than one. For example, GitHub goes up to "23 hours ago" then switches to "a day ago" then "N days ago." These methods may be lower level than what people will want to use in their apps, preferring methods like momentjs' fromNow(). Base don that, values that seem odd (like "in 0 days") may be fine and it won't be worth the API complexity to avoid them.

Adding more arguments to @scottgonzalez's line of thought:

Applications that need countdown (that could justify "in 0 days" use case) should use .formatUnit() #252 instead.
Applications that really need to customize the messages could customize the data before loading them into Globalize.

Edit: I've added one example to my previous message for clarity.

@mbirtwell can you ping me on IRC #globalize (http://irc.jquery.org/)?

I had a chat with @scottgonzalez and @arschmitz. The three of us agreed on keeping this API in its simplest form. This means dropping both (a) the option to select the preference for customary words (maximumWordOffset or useCustomaryWords) and (b) dropping the option to select the zero tense preference. Therefore, the relative time formatting will always use the available customary words and it will always format 0 using the past tense.
We can always reevaluate the addition of the discussed options in the future depending of the requests.
For now:

Countdown applications (e.g., 3, 2, 1, happy new year) should either use (a) to-be-implemented .formatUnit() #252 or (b) customize the CLDR data accordingly (by removing the customary word fields).
Applications that need complex ways of cherry-picking customary words should customize the CLDR data accordingly (e.g., by removing the customary word for "tomorrow", but keeping the "today").

@mbirtwell, I've updated the above TODO list according to this decision. If you want to chat about it, feel free to add comments or to ping me on IRC.

OK, I'll have a look at that next time I get back to this

Sorry one of my commits (from a week ago) was been created with my work email address. I've signed to CLA for that email address as well now.

@mbirtwell sorry for the delayed response. Thanks for the updates. I have added a couple of review comments.

@mbirtwell it's looking great. Please, just let me know when you have updates.

@mbirtwell thanks for your updates so far.

@mbirtwell, I went ahead and made the final fixes in a new commit.
I want to let you know I really appreciate your work here. Thanks and keep in touch. Your further contributions are welcome.
PS: Although CLA task has been marked as failing. I've checked it manually and it is correct (3/1/2015 8:47:57	Michael Birtwell<EMAIL_ADDRESS>I AGREE).


Update sprig compare

Signed-off-by: zzjin<EMAIL_ADDRESS>

Needs: https://github.com/labring/sealos/pull/2264 to be merged first.

https://github.com/labring/sealos/pull/2265


Changed Arguments / Automated Testing

Changed submit_model & playground arguments
Changed object_oriented module to playground
Implemented basic automated testing protocol for sklearn & keras
Cleaned code (e.g. removed quick_submit)
Tested with pip install --extra-index-url https://test.pypi.org/simple/ --upgrade aimodelsharedev==650.610.401
Attention, this will break backward compatibility!

@hp2500 Is this ready to merge?  I'm assuming it includes all the latest updates needed to use our newest tutorial notebooks.  Need to merge and publish to pypi version to post our notebooks.

@hp2500 Is this ready to merge? I'm assuming it includes all the latest updates needed to use our newest tutorial notebooks. Need to merge and publish to pypi version to post our notebooks.

yes, ready to merge


[Bug] The tooltip arrow is not showing when the property "confine" is set to true

Version
5.4.3
Link to Minimal Reproduction
https://echarts.apache.org/examples/en/editor.html?c=bar-simple&version=5.4.3&code=PYBwLglsB2AEC8sDeAoWsAeBBDEDOAXMmurGAJ4gCmRA5AMYCGYVA5sAE7m0A0J6AE2aMiAbVoBZGL1i0AKgFcqM2gHUqAlXIAWClQDEOEFQGVmphdFoBdEgF8-6MMGAAbSCCKpSsPNuAA7kRgHEqOpCDAeBCQMHTOILz8sPQwAGYQ0DRkoVT24eQ4-F7JFNR0AG6Mrkq0-SR4VEZUhLCiyd4-sEJgIm0AjABMAAw8sCOjsP0ArJMAHJMA7JP9_SsAzMPW4T5l2bQARowcdT52JLZ2ANxAA
Steps to Reproduce

Set tooltip.show to true.
Set tooltip.position to 'top', 'left', 'right' or 'bottom'.
Set tooltip.confine to true.

Current Behavior
When tooltip.confine is set to true the arrow of tooltip is no longer shown.

Expected Behavior
I was expecting the arrow to still display as it does when confine is set to false.

Environment
Modifying the examples provided in https://echarts.apache.org/ . For example: https://echarts.apache.org/examples/en/editor.html?c=bar-simple&version=5.4.3&code=PYBwLglsB2AEC8sDeAoWsAeBBDEDOAXMmurGAJ4gCmRA5AMYCGYVA5sAE7m0A0J6AE2aMiAbVoBZGL1i0AKgFcqM2gHUqAlXIAWClQDEOEFQGVmphdFoBdEgF8-6MMGAAbSCCKpSsPNuAA7kRgHEqOpCDAeBCQMHTOILz8sPQwAGYQ0DRkoVT24eQ4-F7JFNR0AG6Mrkq0-SR4VEZUhLCiyd4-sEJgIm0AjABMAAw8sCOjsP0ArJMAHJMA7JP9_SsAzMPW4T5l2bQARowcdT52JLZ2ANxAA

Any additional comments?
It also happens when I create a function for the property tooltip.position even when it returns 'top' and it would be nice that at least in this case the arrow would still show. I have a case when I use a function to decide if I want it on top or on the right so I can not use simply a string to set that property.

This is intentional. Because with confine, the tooltip position may probably be changed so the arrow won't pointing to the data any more.


Create a BLUR for PowerToys Run

Description of the new feature / enhancement
Is it possible to make a blur on the rest of the windows, or darkness like when you use Windows+Shift+S? It could help us focus on the position of the search bar, creating a better experience overall
Scenario when this would be used?
When running PowerToys Run
Supporting information
No response

Tracked via https://github.com/microsoft/PowerToys/issues/4794


BaseMemory accesses should be bounds checked

See https://github.com/christophwille/csharp-opa-wasm/issues/12.
MemoryBase.WriteString and friends don't actually check to see if the requested address is in-bounds of the current memory size.
This leads to undefined behavior.
The .NET API should be checking the given address to ensure it is in range of what is currently allocated for the memory.

Red herring. I double checked that all accesses with MemoryBase are through Span which will bounds check for us.

Red herring. I double checked that all accesses with MemoryBase are through Span which will bounds check for us.


✨ Mobile | Show LinkedIn against profiles

Hi team
Now that we have the ability to add a LinkedIn profile in Settings, we now need to show these against profiles.
Tasks

[ ] Show a LinkedIn icon on items on the Leaderboard if that user has a LinkedIn profile set

[ ] Maybe show these icons on the Network page as well

[x] On profile pages, show that user's LinkedIn profile and allow them to tap and open that link

Acceptance Criteria

[ ] Meets Definition of Done - https://github.com/SSWConsulting/SSW.Rewards.Mobile/blob/main/_docs/Definition-of-Done.md

Thanks!

Show a LinkedIn icon on items on the Leaderboard if that user has a LinkedIn profile set

Not done.
The purpose of the Leaderboard is to provide visibility and recognition to users, so LinkedIn information doesn't seem to belong there.
We also don't have enough space on the Leaderboard list item to accommodate social media information as we already shorten names and points.
When a user adds their LinkedIn profile, that action will appear on the Activity page.

Maybe show these icons on the Network page as well

The Network page might be the right place to show such information, but the page will require a re-design to accommodate the varying number of social media platforms.

On profile pages, show that user's LinkedIn profile and allow them to tap and open that link

Done, see the screenshot below.

Figure: LinkedIn profile icon which will open a browser when tapped.


Changes from NSLS-II SIX for clearer error messages about timeouts

This is a very volatile, work-in-progress PR to the v1.3.x branch, to save the state of the code used at the NSLS-II SIX beamline in the recent attempts to mitigate the random timeout errors. See https://github.com/NSLS-II-SIX/profile_collection/issues/24 (and https://github.com/NSLS-II-SIX/profile_collection/issues/20?) for the context.

Is this worthwhile to keep open @mrakitin?

@klauer, I think this can be closed, but I'd like to keep the branch around. The fix is not general enough, so in case of a follow-up update there will be a separate PR.


Longitudinal fmriprep with pre-run Freesurfer

Hi all,
In a previous issue (#993), there was a discussion about using fmriprep for longitudinal studies. The question came down to the reusability of Freesurfer outputs. The suggestion was made by @chrisfilo to run Freesurfer first (preferably the BIDS App Freesurfer) and then let fmriprep pull from that.
I've run Freesurfer's recon all for my participants. When I run fmriprep, should I use the --no-fs-reconall option. When I include the flag, the process crashes out with an error (see attached crash text file). When I do not include the flag, the process runs but it's not clear if the freesurfer output is being incorporated.
 The --no-fs-reconall was included for one participant and excluded for one participant. The one where it was included completed.
Please let me know what other files might be needed to identify if freesurfer is getting incorporated as intended.
crash-20180414-015316-root-autorecon1-f42ca378-4525-48ee-ac26-65982571c354.txt

Has there been any update on this? I am also running into an issue of fmriprep not being able to recognize previously run freesurfer outputs for a longitudinal design. I get the "you are trying to re-run an existing subject with (possibly) new input data..." error

I think this is finally going to be possible in the near future with https://github.com/nipy/nipype/pull/3529. We will need assistance from somebody familiar with FreeSurfer longitudinal to implement it, however.


[Blob Storage] BlockBlobClient.downloadToFile hangs indefinitely under poor network conditions

Package Name: @azure/blob-storage
Package Version: 12.14.0
Operating system: linux armv7
[x] nodejs

version: 16.19.1

[ ] browser

name/version:

[ ] typescript

version:

Is the bug related to documentation in

[ ] README.md
[ ] source code documentation
[ ] SDK API docs on https://docs.microsoft.com

Describe the bug
A clear and concise description of what the bug is.
Under poor network conditions, BlockBlobClient.downloadToFile hangs indefinitely.
To Reproduce
Steps to reproduce the behavior:

Emulate poor network environment with this command: sudo tc qdisc add dev eth1 root netem delay 200ms 40ms 10% loss 5% 5% duplicate 1% corrupt 0.1% reorder 5% 10%. Change network adapter name accordingly.
Run sample code below substituting correct parameters. I cannot expose internal credentials.

Expected behavior
A clear and concise description of what you expected to happen.
It should timeout and the result should be recorded in one of the console.log calls in the try catch block.
Screenshots
If applicable, add screenshots to help explain your problem.
const request = {
  url: 'url-to-azure-resource',
  blobFolder: 'folder-of-blobs',
  sasToken: 'sas-token-confidential',
  containerName: 'container-name'
};

// main function calls this function with above object and assume that filePath is valid
async function handleStorageFile(request, filePath) {
  const { url, blobFolder, sasToken, containerName } = request;

  let blobServiceClient = new BlobServiceClient(`${url}?timeout=20&${sasToken}`);
  let containerClient = blobServiceClient.getContainerClient(containerName);
  let blockBlobClient = containerClient.getBlockBlobClient(`${blobFolder}/blob-name`);
  const tempFilePath = filePath + 'blob-name';

  try {
    const downloadToFilePromiseResult = await blockBlobClient.downloadToFile(tempFilePath,0,0,{
      onProgress: (downloading) => {
        console.log('onProgress', downloading);
      },
      maxRetryRequests: 5
    });
    console.log('downloadToFilePromiseResult', downloadToFilePromiseResult);
  } catch (error) {
    console.log(error);
  }
};

Additional context
Add any other context about the problem here.

1 download only. The blob we are trying to download is around 600MB.
To reset network interface, run sudo tc qdisc del dev eth1 root.
Sometimes if it doesn't hang indefinitely, we notice that it tries to download more bytes than the value recorded in properties.contentLength.
Switching to another access method is not feasible in the short term - would appreciate a fix or workaround with SAS tokens.

Hi @EmmaZhu, thanks for the reply. Yes it is blocking us. The settings to emulate poor network condition seem harsh, but that is to reliably reproduce the issue. Some of our clients have not so good network conditions, so sometimes they experience this problem and it becomes our problem if we can't do error handling in the code. I would appreciate the workaround you mentioned since it sounds like a fix on this is not going to be released in the near future.

Hi @hme-hlin ,
The workaround would be split a large blob to small pieces for downloading, any of a single piece failed, just retry on the piece.
Following is a sample shows how to split a large to small piece. Please be noted, it's only a sample without fully test, it's just used to show you the possible workaround logic. Please do make fully validation before using it in your production.
const fd = await fs.open(path, 'w');

  const propertes = await blockBlobClient.getProperties();
  const buffer = Buffer.alloc(4 * 1024 * 1024);
  const count = 4194304;

  for (let offset = 0; offset < propertes.contentLength!;){
    const downloadCount = Math.min(propertes.contentLength! - offset, count);
    offset += downloadCount;
    let retryMax = 3;
    let shouldRetry = true;

    while (retryMax >= 0 && shouldRetry) {
      try {
        await blockBlobClient.downloadToBuffer(buffer, offset, downloadCount, {
          abortSignal: AbortController.timeout(10 *1000), // Abort uploading with timeout in 10 secs
          blockSize: 4 * 1024 * 1024, // 4MB block size
          onProgress: (ev) => console.log(ev),
        });
        shouldRetry = false;
        console.log("downloadToBuffer succeeds");
      } catch (err: any) {
        shouldRetry = true;
      }
      --retryMax;
    }

    // shouldRetry is false, means that download succeeded.
    if (!shouldRetry) {
      await fd.write(buffer, 0, downloadCount, offset);
    }
  }

  await fd.close();

Hi @EmmaZhu , I tested the workaround you provided without poor network conditions, and it seems like the workaround doesn't reliably work at all times. Even if it has been broken down into 4MB chunks, sometimes it still hangs indefinitely. The good news is that now I am getting timeout errors, but it is very inconsistent.
Timeout error message
Error: The operation cannot be completed in timeout.
    at Timeout._onTimeout (/usr/bin/zoltar/CloudApp_IOT/node_modules/@azure/storage-blob/dist/index.js:19126:49)
    at listOnTimeout (node:internal/timers:559:17)
    at processTimers (node:internal/timers:502:7)

Modified sample code
const { promisify } = require('util');
const open = promisify(fs.open);
const write = promisify(fs.write);
const close = promisify(fs.close);

const tempFilePath = 'path-to-target-file';
const fd = await open(tempFilePath, 'w');
const megaBytes = 4;
const blockSize = megaBytes * 1024 * 1024;
const buffer = Buffer.alloc(blockSize);
const abortController = new AbortController();

for (let offset = 0; offset < fileSize;) {
   const downloadCount = Math.min(fileSize - offset, blockSize);
   let retryMax = 3;
   let shouldRetry = true;
   console.log(offset, downloadCount);

   while (retryMax >= 0 && shouldRetry) {
      try {
         console.log('retryMax', retryMax, shouldRetry);
         const downloadToBufferResult = await blockBlobClient.downloadToBuffer(buffer, offset, downloadCount, {
            abortSignal: abortController.signal, // Abort uploading with timeout in 10 secs
            blockSize, // 4MB block size
            onProgress: (ev) => console.log(ev),
         });
         shouldRetry = false;
         console.log("downloadToBuffer succeeds", downloadToBufferResult);
      } catch (err) {
         console.log(err);
         shouldRetry = true;
      }
      retryMax -= 1;
   }
   // shouldRetry is false, means that download succeeded.
   if (!shouldRetry) {
      await write(fd, buffer, 0, downloadCount, offset);
      offset += downloadCount;
   } else {
      abortController.abort();
   }
}

await close(fd);

An update to my previous post. I left it running over night and it did go past the place it was stuck on. It's still not an ideal situation though. For example, if the connection is considered alive, but it takes some time to resume download. I don't think customers usually have a lot of patience but let's be generous and say the customer's willing to wait for 10 minutes. After 10 minutes if the download still isn't resumed then what next?
During this time, there is no indication of progress because onProgress doesn't get triggered. If the customer decides to restart the machine due to a lack of indication, we don't get to save where it was stopped and resume later because the application is essentially force quitted. Sure, there is the workaround you provided, and I could probably add a timeout myself, but all this can be avoided if the SDK would just honor the timeout setting and error out so that some form of error handling can be done.

Hi @hme-hlin ,
Thanks for the update. I agree that the download in SDK should have improvement for poor network environment.  The sample is just a transient workaround. We'll still need to look into the issue and try to make improvement.
Thanks
Emma

Hi @EmmaZhu I'm going to close this issue for now since the workaround you provided works and we are given back the ability to timeout and handle errors, although it is definitely not ideal. I hope that you guys can supply a proper fix for it soon.


[Model] Simplify full namespaces for already included resources

Fixes #565 .
Also fixes a bug where cast type was not properly added when the return type was found via phpdoc.

Simplify full namespaces for already included resources

I didn't realize this until I tried it out: every FQCN which at some point is manually imported, will then not be written as FQCN.
Say if you import \Illuminate\Database\Eloquent\Builder => it will then be written as just Builder. Aliases seem to be also correctly supported.
MAJOR thing, thank you 🙏

I noticed it doesn't cover the case where models are relations, they are still kept in the FQN.
namespace App\Models;

class ModelOne extends …

namespace App\Models;

/**
 *
 * @property-read \App\ModelOne|null $ticket
 */
class ModelTwo extends …
{
    public function modelOne(): HasOne
    {
        return $this->hasOne(ModelOne::class);
    }
}

When I import ModelOne, ide-helper still writes it back as \App\ModelOne.


Split integration tests into separate workflows

We can split the integration tests into separate workflows once referencing local workflow file ref functionality is added.

Doc on how to actually do this in a workflow file

We should also be able to create and run a script during the build portion of the integration workflow to generate the test folder of this repo.

Closed with #10. The integration test generator does what this was intended to do in a slicker way. That script could be modified a little to clean things up but it gets the job done.


[bp-2.3] Comment out tests that may cause ocp api server to degrade

issue reference:

https://github.com/stolostron/multicloud-operators-foundation/issues/684
https://github.com/stolostron/multicloud-operators-foundation/issues/686

/hold

/approve
/lgtm

/unhold


exp rename: Add rename command

Fixes #4793
Dependencies: https://github.com/iterative/dvc/pull/9812 (stems from issue: https://github.com/iterative/dvc/issues/6667)
Add an exp rename docs page, along with the addition of exp rename to the navigational sidebar.

Thanks @omesser and @dberenbaum  for the reviews. I have updated both the original PR and this PR to reflect the changes of removal of --rev and some other minor requested changes.


Our unstable tests loop build should run all tests, and in the same way that our stable builds run

Currently, https://jenkins.mesosphere.com/service/jenkins/view/Marathon/job/public-marathon-unstable/ runs our tests in serial, and only runs unstable tests.
When we mark tests as unstable, they stop failing, as a result. This is not ideal.

https://phabricator.mesosphere.com/D454


Declaration of transformResponseBody() must be compatible

Declaration of Jane\\OpenApiRuntime\\Client\\AmpArtaxEndpointTrait::transformResponseBody(string $body, int $status, Symfony\\Component\\Serializer\\SerializerInterface $serializer) must be compatible with Jane\\OpenApiRuntime\\Client\\Psr7HttplugEndpointTrait::transformResponseBody(string $body, int $status, Symfony\\Component\\Serializer\\SerializerInterface $serializer, ?string $contentType = NULL)

jane-php/json-schema-runtime          v4.4.0                                Jane runtime Library
jane-php/open-api-runtime             v4.4.0                                Jane OpenAPI Runtime Library, dependenc...

Workaround. Add require to composer.json:
        "jane-php/open-api-runtime": "4.2",

This is broken currently. Why is there no composer.lock in docker-php-api?

I've tested on PHP7.1.9 and PHP7.2.4, the issue still remains.

seems like nobody is working on the repo these days.

// Go to this file vendor/jane-php/open-api-runtime/Client/Psr7HttplugEndpointTrait.php // Chage abstract function Declaration from  transformResponseBody(string $body, int $status, SerializerInterface $serializer, string $contentType = null); // TO  transformResponseBody(string $body, int $status, SerializerInterface $serializer);

Workaround. Add require to composer.json:
        "jane-php/open-api-runtime": "4.2",

It works for me, thanks @4n70w4


plex: EasyAudioEncoder binary has the wrong linker

Issue description
After installing plex, things go well until I try to play a video with AC3 audio.  Then I see this in the logs:
May 04, 2017 07:04:35.000 [0x7f12203fd700] ERROR - [Transcoder] [ac3_eae @ 0x28e5a60] EAE timeout! EAE not running, or wrong folder? Could not read '/tmp/pms-88462e58-7912-4406-8d29-ddd80a432a67/EasyAudioEncoder/Convert to WAV (to 8ch or less)/2xsve3k7i5bkyahzcpgco9a4_8725-1-2.wav'
May 04, 2017 07:04:35.000 [0x7f120ffed700] ERROR - [Transcoder] [ac3_eae @ 0x28e5a60] error reading output
May 04, 2017 07:04:35.001 [0x7f12187fe700] ERROR - [Transcoder] Error while decoding stream #0:1: Input/output error

The problem is that somewhere in the install process the EasyAudioEncoder binary was installed with the wrong linker:
$ file "/var/lib/plex/Plex Media Server/Codecs/EasyAudioEncoder-133-linux-ubuntu-x86_64/EasyAudioEncoder/EasyAudioEncoder"
/var/lib/plex/Plex Media Server/Codecs/EasyAudioEncoder-133-linux-ubuntu-x86_64/EasyAudioEncoder/EasyAudioEncoder: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, for GNU/Linux 2.4.0, stripped, with debug_info

Steps to reproduce
Play a video with AC3 audio, that triggers audio transcoding.  Then look in the PMS log in /var/lib/plex.
Technical details

System: 17.09pre106916.c5badb123a (Hummingbird)
Nix version: nix-env (Nix) 1.11.9
Nixpkgs version: 17.09pre106916.c5badb123a

Looks like the codec that plex dynamically downloads just has the wrong interpreter:
$ patchelf --print-interpreter EasyAudioEncoder
/lib64/ld-linux-x86-64.so.2

I can confirm that patching it fixes the issue:
$ patchelf --set-interpreter "$(cat $NIX_CC/nix-support/dynamic-linker)" EasyAudioEncoder

Is there a way we could patch this after plex has downloaded the codec?

This is still a problem (and running patchself manually still fixes it).

@solson Is this still an issue not that #56565 is merged?

I finally got around to updating and testing this, and I can confirm that Plex is automatically downloading new codecs and they are working. Thanks to everyone who worked on this! I think the issue can be closed.

Thank you for looking into this!


toolbarHeight from M3 specs not applied to AppBar

#91605
It seems that the height of the AppBar in M3 is still 56.0, which matches M2, even though the default value is set to 64.0

Closing this as duplicate of https://github.com/flutter/flutter/issues/117903. Please follow-up in that issue for further updates.


Enhanced Recurring Donation: Editing existing RD produces Error Message

Hub Thread
W-8487823
Issue:
Editing an existing Enhanced Recurring Donation record causes an error message to display, even though edited values are saved as expected.
Error:
_Sorry to Interrupt
This page has an error. You might just need to refresh it. First, would you give us some details? (We're reporting this as error ID: 58913069)
Technical Stuff:
[Cannot read property 'apiName' of undefined]
.handleData()@https://coritrial--rdtesting.lightning.force.com/components/interop/recordEditForm.js:1:5057
eval()@https://coritrial--rdtesting.lightning.force.com/components/interop/recordEditForm.js:1:3041
eval()@https://coritrial--rdtesting.lightning.force.com/components/lightning/inputUtils.js:1:1555

Steps to Repro:

In an org with Enhanced Recurring Donations enabled, create or locate an existing RD record.
Click Edit - You can make a change to a field value or not as the error will happen regardless
Click Save
Expected: Record saves and user is taken back to view the RD record
Actual: Error message is displayed, any changes made are applied successfully.
If you can't repeat, try refreshing your browser tab/window. A pattern has been found where the first attempt to edit causes an error, but there's no error produced on subsequent edits (same record or others) until you refresh your browser tab.

The same error occurs when cancelling out of edit, even when you haven't made any changes.  This occurs even when the user has full permissions to Recurring Donation and all fields.

Update: This is a core Salesforce bug and has been transferred away from Salesforce.org scrum teams. Will close this Issue as it will not be resolved by Salesforce.org.
@davidchengIC thanks for adding the nuance, I'll make sure Salesforce core see that.

@coriobriensfdo Is there anywhere we can track this issue with Salesforce.com? I'm running into this same issue and wondering if there's been any progress on it over there. Thanks!

@coriobriensfdo Is there anywhere we can track this issue with Salesforce.com? I'm running into this same issue and wondering if there's been any progress on it over there. Thanks!

@nai888 there isn't a Known Issue for this particular Issue, however Salesforce has resolved the bug in an upcoming release. This should be resolved in the next few weeks, but feel free to re-post here if you don't see that in your org. Sorry for the confusion on this one, we'll make sure there's a KI next time so it's easier to follow.

@nai888 there isn't a Known Issue for this particular Issue, however Salesforce has resolved the bug in an upcoming release. This should be resolved in the next few weeks, but feel free to re-post here if you don't see that in your org. Sorry for the confusion on this one, we'll make sure there's a KI next time so it's easier to follow.

@coriobriensfdo Thanks for the info! Are you referring to Spring '21? I'm running into this issue in a sandbox that's already upgraded.

@coriobriensfdo Thanks for the info! Are you referring to Spring '21? I'm running into this issue in a sandbox that's already upgraded.

It's actually a patch release (Spring '21 Patch 6) so you may already see it resolved in Sandbox :)

It's actually a patch release (Spring '21 Patch 6) so you may already see it resolved in Sandbox :)


News update Pop-up

News update Pop-up
User Story
As a pilot web application user,
I want to see a pop-up of the latest news updates at the end of study time,
So that I can catchup on the latest news that I missed during study time.
Acceptance Criteria
GIVEN the focus timer is running on the application,
WHEN the timer runs out,
THEN a pop up is displayed on the website showing the latest news updates to be read.

completed


Testing drag and drop

Able to get a basic drag and drop example working.  Need to make dramas drag and drop still.

@huywhomustnotbenamed
My updates to the add_angular branch:

Updated the bower.json file, added more dependencies I want to try out.  I think angular-gridster may be a better replacement for Freewall.
*Added a .bowerrc file so bower packages are stored in the vendor folder
*Moved all third party scripts to vendor folder
*Updated config/application.rb to join scripts in vendor folder
*Updated application.js with new requirements
Changed file structure of angular app (app/assets/javascripts/angular) so it's feature focused. So now, models, directives, views for each feature reside in same folder


Update reference to treelite website

treelite.io is no longer a valid site and re-directs users to a parked domain. Re-directing to the documentation is safer at this point.

@hcho3


Allow domain specific variable type

adds a type parameter to most constraint syntax types
separates Variable into its own thing
moves some other things around where they found better homes
moves a bunch of trait implementations into a macro.

This provides library users with the ability to specify their own variables. All the structs associated with constructing constraint syntax now take a type variable that represents the domain specific variable type. Variable itself is moved into its own module and is provided as a default variable type. There's a new module derive_syntax for automatically deriving the necessary machinery to write constraints using a domain specific variable type.
In general one cool thing I think this provides is the ability to run two separate solvers - one for each dimension - and not have the types mix. For example:
pub struct Entity {...}
pub enum XVariable {
  Left(Entity), Width(Entity), Right(Entity)
}
pub enum YVariable {
  Top(Entity), Height(Entity), Bottom(Entity)
}
type XSolver = Solver<XVariable>;
type YSolver = Solver<YVariable>;

^ Here you can't mix constraints from the two axes without triggering a compile time error, which I think I like. Anyway - there's only one test really, so YMMV.

Wait, you want me to maintain this lib now? I don't have permission to publish it. I also don't have much further use for it, as it happens. Maybe you should make your own PR vs the original (easiest if you include my commits and I close mine).

I don't have any preference as to who will maintain the crate, but I forked from yours because it was further ahead and had some extra features. I'll push my branch to the original.


Support for generate and return tool_calls with Anthropic models

The proposed changes include:
1/ Ability to use tools with .generate()
2/ Returning stop_reason and tool_calls to AIMessage when using tools in the response metadata
Support for function call using the generate function not directly implemented in ChatBedrock.
from bedrock import ChatBedrock

chat = ChatBedrock(
    model_id=model_id,
    model_kwargs={"temperature": 0.1},
)

class GetWeather(BaseModel):
    """Get the current weather in a given location"""

    location: str = Field(..., description="The city and state, e.g. San Francisco, CA")

llm_with_tools = chat.bind_tools([GetWeather])
llm_with_tools

messages = [
    HumanMessage(
        content="what is the weather like in San Francisco"
    )
]
ai_msg = llm_with_tools.generate(messages)
ai_msg

Appreciate the work you've done here. With regard to "tool_calls" being populated, I am indeed now seeing expected formatting. However, I have an implementation mimicking the documentation for LangGraph collaborative multi-agent system and seeing odd behavior when using ChatBedrock over ChatOpenAI. In my case, in addition to the entry point node not calling the correct tool, tools are not actually being called at all and I'm having difficulty discerning the root cause. On top of this, I'm getting an "list index out of range"  here:
File "/usr/local/lib/python3.11/site-packages/langchain_aws/llms/bedrock.py", line 235, in prepare_output    text = content[0].get("text")             ~~~~~~~^^^ IndexError: list index out of range
I have verified that simply swapping to the ChatOpenAI model resolves the issue and tool calling works as expected.
If this requires a standalone issue, please let me know and I will get that sorted.

Hi, Is there anything we can do to allow the PR to get merged ?

Hi, is the tool_choice argument of bind_tools method functioning? Because I would like to force the LLM to use a tool, but it does not seem to work. Are there any workarounds to do so? Thank you in advance.

Can this please be reviewed and merged? Can't switch my existing codebase to bedrock due to this error.
# llm = ChatOpenAI(model="gpt-4o", openai_api_key=OPENAI_API_KEY) [WORKS FINE]
# llm = ChatAnthropic(model="claude-3-opus-20240229") [WORKS FINE]
llm = ChatBedrock(
    model_id="anthropic.claude-3-sonnet-20240229-v1:0",
    model_kwargs=dict(temperature=0),
) [ERROR]

ValueError: System message must be a string, instead was: <class 'list'>


Copper tools cannot be repaired with the grindstone

Placing a copper tool in the grindstone UI works, but the original material used to make the tool cannot be placed in the UI with it.  Thus, it's impossible to actually repair the tool.

The grindstone is not designed to repair tools with their material. To do this, as in vanilla minecraft, you need to use an anvil. A grindstone is needed to repair an item with the same item and remove enchantments.
Current versions use vanilla copper ingots to repair, but future versions will have compressed copper ingots.

Got it, thanks!  I'm new to 1.18, and I mistook the working of the grindstone.  :-)


Color Table Window Redesign: Fix loading of filtering selection so it does not require band-aids all over the code

To make saving the color table tag filtering selection saveable and loadable in #17721, I had to jump through a number of hoops.

The color table observer includes a fail-safe in the Update() function that makes sure that the list of color tables and the list of toggles are the same size (it should be a 1 to 1 relationship). This fail-safe should never have to be activated, but there is an issue with loading settings from config/session files, which cause the list of toggles for color tables to be empty when execution reaches this function. The underlying issue (somehow the toggle list is empty when reading from saved settings) needs to be investigated and fixed.

// This should never happen. Resetting the names will reset the active
// array as well, and make very color table active. However, this does
// happen; when loading settings from config/session files, `names` is
// populated but `active` is left empty. Ideally, loading settings
// would correctly preserve which color tables are active, but this
// final guard here works just fine, as which color tables are active
// is calculated after this.
if (names.size() != active.size())
    colorAtts->SetNames(names);

The UpdateNames() function for the Color Table Window has a code block at the end that must be run only once.

static bool run_before = false;
if (!run_before)
{
    // This only needs to happen the very first time for loading options.
    // If visit isn't opened with saved config and guiconfig files, then
    // this is redundant, but doesn't hurt. If it happens more than once
    // then VisIt will crash.
    run_before = true;
    colorAtts->SetChangesMade(true);
    ctObserver.SetUpdate(true);
    Apply(true);
}

This occurs so that the filtered down list of color tables appears in all the buttons. It also only ever needs to happen once, because of the order of execution of functions when loading saved config/session files. Before this band-aid, the buttons didn't get updated with the filtering selection until users clicked something in the color table manager, which is a bug. However, if it happens on every call, VisIt will not only freeze, but you will also be booted off your compute node. Calling Apply() shouldn't happen in UpdateNames(), since it'll circle around (I think?) and call UpdateNames() again. Hence the static bool to force it to happen just the first time. I need to figure out why the color table observer isn't doing it's job when VisIt loads config/session files, fix it, and ideally remove this code.
I have grouped these 2 problems into one issue because they both relate to the loading of saved session/config files. So the things to fix are 1) correctly saving and loading which color tables are "active" (toggled on (appearing in the filtered list)), and 2) switching up the order of execution within the GUI so that the color table observer pays attention properly when info is first loaded from config/session files.

Fix the issues here as much as possible (race condition on start up?) and then think about how the gui could be modified in the future to be more sensible.

Other problems include things like this:
UpdateNames();
colorAtts->SetChangesMade(true);
ctObserver.SetUpdate(true);
Apply(true);

As well as the tagChangesMade and changesMade in the CCPL and CTAtts respectively.


Joining as a viewer doesn't work in Auction sample

When I try to login in Auction sample as a Viewer the "Join Meeting" button doesn't respond while I get in the network response "  "success": true,"

Noting that it works fine when I join as a host
thanks.

Hey, can you share what error you are seeing, which API is failing?
Also do confirm if you are using the right preset for the viewer.

I've tested again, this issue happens when I add participant as livestream_viewer, but it works fine with webinar_viewer


Add content-type to script tag builder.

I'm trying to create my first user in saltcorn's docker image, but I'm not able to send the form back because I have an invalid CSRF. I don't know if this is caused by jQuery being unavailable, but that's as far as I've gotten in troubleshooting. There needs to be a type attribute on the script tags (either application/javascript or text/javascript) for modern browsers (Firefox in particular) to be able to use the scripts. See the snippet below for more details, I think if we add the type here it should work.
https://github.com/saltcorn/saltcorn/blob/03663f5b38f47984143611d29062d2fb9ee0b5fe/packages/saltcorn-markup/builder.ts#L66-L70
See this picture for the error:

This is not causing my failure to create a new user. Please take this issue into consideration, but you can close if necessary.

What was ended up being the issue @colonelpopcorn ?
I'm using the Docker image (Chrome though) without issue.

I still haven't figured it out, but the root of my issue is an invalid CSRF token being passed around. My thought was that if the JS couldn't execute due to strict mime-type checking it could cause the root issue, but I'm not 100% on that.

I


Setting config.platform.php setting to hardcoded 5.3.9 causes issues

doctrine/migrations v1.2.2 requires php >=5.4.0 -> your PHP version (5.5.9-1ubuntu4.14) or value of "config.platform.php" in composer.json does not satisfy that requirement.`

So I believe it should be removed from composer.json (at least for v2.8)
It's also hardcoded as 5.5.9 for the master, which is not obvious what reason for either.

@zerkms Please, check discussion in https://github.com/symfony/symfony-standard/issues/858 about config.platform.php. But you can delete config.platform.php for your project, Symfony SE is simply quick start template for you.

Thanks

see symfony/symfony-installer#236 for a proposal to do this in the installer


Automate disease inferences

We need to  a quicker way of doing this, the flux is too great to manage (it sucks up about a day every time MONDO updates because it is never completely clear where or what the change is.
https://github.com/pombase/curation/issues/3108
when we used   lots of sources to curate diseases,and there was no mapping between the DO term and the human disease we had to maintain by hand.
Now we use MONDO  there should be a way to automate this, since Monarch have connections between human genes and MONDO:Ids and we have orthologs.

Now we use MONDO there should be a way to automate this, since Monarch have connections between human genes and MONDO:Ids and we have orthologs.

Would these inferences be in addition to the existing annotations or would they replace them?

I envisaged for updates.  This isn't super urgent. It was taking quite a lot of time but it seems to not be at the moment.
I think there is potential to get rid of some of the middle mapping and potentially  weed out incorrect mappings, get missing mappings and supply missing associations to MONDO, but this is more of a mini-project.
It might be a good one for Manu.

Mondo has downloadable association working again
https://github.com/monarch-initiative/monarch-app/issues/327
we can work on this together after  paper, apicuron report,

We can chat about this soon. Using the Monarch disease associations cover most of our existing associations:

I suspect the difference is the "correlated" but I'm not sure.
Some of the ones I looked at that are in PomBase,  are correlated, but not causal in MONDO/Monarch.

The MONARCH IDS which have pombe orthologs:
https://www.pombase.org/results/from/id/d3903069-02c0-478e-bd56-c9a394e4979b
I think we should:
a) Take associations primarily from Monarch on a regular basis.

add the causal qualifier
do the same  for correlated
b) figure out which associations are NOT covered by Monarch, and keep them in a separate file. We will still display them, but we will review

oddly cap2 is in the unannotated in Monarch list but it is causal
https://monarchinitiative.org/MONDO:0957545

Some of the 106 come from tandem fusions in fission yeast that I have not properly annotated with human orthologs yet.
eg.
https://www.pombase.org/gene/SPAC1420.04c
https://www.pombase.org/gene/SPAC19B12.13

Some of those missing from  Monarch  are definitely in the "correlated" see, including
alp7 https://www.pombase.org/gene/SPAC890.02c
atg16 https://www.pombase.org/gene/SPBC405.05 https://monarchinitiative.org/MONDO:0012610

The plan is to map the human disease associations from this file to pombe via orthologs:
https://data.monarchinitiative.org/monarch-kg/latest/tsv/gene_associations/gene_disease.9606.tsv.gz
Then drop the Malacards associations.
We'll then compare before and after using the exported disease_association.tsv file:
https://curation.pombase.org/dumps/builds/pombase-build-2024-06-18/misc/disease_association.tsv

I forgot to ask, what reference should be used for the associations/annotations from Monarch?

The code and config is mostly ready to go.  Should I commit the changes for tonight's load or is it better to wait for the weekend?
I've done a test load of the Monarch data locally and got 2351 disease associations in Chado.  We get 2769 associations from MalaCards.
There are also 1546 manual associations in
pombe-embl/external_data/disease/pombase_disease_associations_mondo_ids.tsv

What is the gene coverage? 1480?
I will write a pombe reference.

Draft text for a PB reference:
Disease associations are created by taking human gene-disease causal, and correlated associations created by Monarch  https://monarchinitiative.org/ using the MONDO  disease ontology <https://mondo.monarchinitiative.org/ .
and mapping to fission yeast orthologs https://www.pombase.org/data/orthologs/ using the manually maintained fission yeast/human ortholog table.
We might add this part later if we need to keep any PomBAse annotations
This is supplemented by manually annotated gene-disease connections at PomBase

Draft text for a PB reference:

Thanks.
Can you suggest a title for the reference?  Like "Disease associations from Monarch via human-pombe orthologs" but better.  :-)

"Disease associations from Monarch via human-pombe orthologs"  sounds fine!

The code and config is mostly ready to go.

It's all done now.  I just need to "git push" when we're ready.

OK this can go live.
The next steps are:

add a qualifier "causal" for the associations from this file
download the other file (non causal) . From this one, for the time being, we should only include  those with the qualifier "contributes_to" but  not those with the qualifier "gene_assocated_with_condition (I am trying to find out what this means but nobody has answered yet)
Let me have the list from our "old set" which are no longer covered (it should be small if any)

Re Let me know if you want those lists.
I'll have the lists after step2, they should be smaller

Oddly, the file from Monarch includes some associations for obsolete terms:
MONDO:0012233 is obsolete (consider: MONDO:0018875) - skipping annotation for SPCC18B5.11c
MONDO:0020734 is obsolete (no "replaced_by" or "consider" tag) - skipping annotation for SPBC106.04
MONDO:0012357 is obsolete (no "replaced_by" or "consider" tag) - skipping annotation for SPCC1672.07
MONDO:0007798 is obsolete (consider: MONDO:0600011) - skipping annotation for SPBC14F5.13c
MONDO:0020619 is obsolete (no "replaced_by" or "consider" tag) - skipping annotation for SPCC737.09c
MONDO:0033571 is obsolete (no "replaced_by" or "consider" tag) - skipping annotation for SPAC1556.08c
MONDO:0020610 is obsolete (no "replaced_by" or "consider" tag) - skipping annotation for SPBC543.05c
MONDO:0044222 is obsolete (no "replaced_by" or "consider" tag) - skipping annotation for SPAC2F3.01
MONDO:0014709 is obsolete (consider: MONDO:0100263) - skipping annotation for SPAC17A5.01
MONDO:0020625 is obsolete (no "replaced_by" or "consider" tag) - skipping annotation for SPBC543.05c
MONDO:0009427 is obsolete (consider: MONDO:0600011) - skipping annotation for SPBC14F5.13c
MONDO:0009428 is obsolete (consider: MONDO:0600011) - skipping annotation for SPBC14F5.13c
MONDO:0044256 is obsolete (no "replaced_by" or "consider" tag) - skipping annotation for SPAC2F3.08
MONDO:0020624 is obsolete (no "replaced_by" or "consider" tag) - skipping annotation for SPBC543.05c
MONDO:0044280 is obsolete (no "replaced_by" or "consider" tag) - skipping annotation for SPAC977.17
MONDO:0024544 is obsolete (consider: MONDO:0100259) - skipping annotation for SPCC553.03

download the other file (non causal)

Download then load into Chado?

No problem.  I was just checking that you wanted it loaded.
All the changes are checked in to load the causal associations and the contributes_to associations, with qualifiers attached.
As an example, the htr11 / SPBC1685.05 disease table should look like this tomorrow:

1536 (vs 1470 currently)

After load the contributes_to associations, it's 1551.

Nice increase 1463 -> 1536.
I'll announce this change tomorrow
If you  could let me have the old associations that are not covered by he new, that would be great.
I'm not surprised there are obsolete terms in Monarch. There seems to be a time lag between Mondo releases and monarch updates. I guess they will resolve eventually. These were the things I used to fix manually, but now they should resolve over time. There will probably always be a number which are obsolete at any point.

If there is a PomBAse annotation that is identical to a Monarch annotation but has reference PBREF 0000003
we can drop it....

If you could let me have the old associations that are not covered by he new, that would be great.

No problem.  After the load finishes tonight, I'll compare old and new.

If there is a PomBAse annotation that is identical to a Monarch annotation but has reference PBREF 0000003
we can drop it....

So remove it from the source data file (external_data/disease/pombase_disease_associations_mondo_ids.tsv) or remove it from Chado when loading?

You can remove it from the source, it provides nothing extra.

If there is a PomBAse annotation that is identical to a Monarch annotation but has reference PBREF 0000003
we can drop it....

OK, that's done for tomorrow.
I've removed 670 lines from external_data/disease/pombase_disease_associations_mondo_ids.tsv

OK, that's done for tomorrow.
I've removed 670 lines from external_data/disease/pombase_disease_associations_mondo_ids.tsv

I forgot to commit the change.  I've done that now so I'll check again on Friday morning.
The other changes are on the main site:
https://www.pombase.org/gene/SPBC1685.05

If you could let me have the old associations that are not covered by he new, that would be great.

These are the 1470 genes with MONDO terms from two days ago (uploaded from the old disease_association.tsv):
https://www.pombase.org/results/from/id/ecc08627-b79a-4aaa-800e-51eff3bb091b
These are the 1564 genes annotated now (uploaded from the current disease_association.tsv):
https://www.pombase.org/results/from/id/4b21373a-5642-4ff5-bbb6-1724411229dc
(As a double-check, the same list using an ontology query: https://www.pombase.org/results/from/id/aafa9e7f-1563-43d7-a4b1-25819c2917c6)
Genes that did have an annotation, but don't now (32):
https://www.pombase.org/results/from/id/1e6c9274-e462-4bbc-8623-df0d8943ff3e
Genes that didn't have an annotation two days ago, but do now (126):
https://www.pombase.org/results/from/id/38b48b56-de18-4356-a8e2-5558b4ceab67
I've switched the dev site back to the database from two days ago in case you'd like to check anything about the old annotations.   So fast!
and also not many to check which is good. Will save me lots of time going forward.

I checked the missing ones at OMIM, and although some have tentative assignments, they are inconclusive.

Hi Val.
I meant to ask this yesterday.
There are a 101 genes annotated with "disease susceptibility" (MONDO:0042489):
https://www.pombase.org/results/from/id/567f5173-4849-45c7-bf3f-ed141a990908
Of those, 13 genes don't appear in the "All disease associated genes" (MONDO:0000001) commonly used query:
https://www.pombase.org/results/from/id/a0c8f835-3984-4b57-9c5e-8cef6aa1f5aa
Just to check: is that what we want?

There are a 101 genes annotated with "disease susceptibility" (MONDO:0042489):
https://www.pombase.org/results/from/id/567f5173-4849-45c7-bf3f-ed141a990908
We want to include these

OK, I've changed the query in the config and have set off a re-release of the website.


Potential bug in reading lists from avro?

Line of code: https://github.com/jorgecarleitao/arrow2/blob/c615095dbfb930a247c23423e36118843f71e1d2/src/io/avro/read/deserialize.rs#L136
Feel free to close this issue if my understanding is incorrect here. Referencing the Java Avro implementation, looks like array values are stored/read as blocks and can be read consecutively until a 0 is encountered. (https://github.com/apache/avro/blob/42822886c28ea74a744abb7e7a80a942c540faa5/lang/java/avro/src/main/java/org/apache/avro/io/Decoder.java#L203)
In the Avro deserialisation logic for reading in lists, looks like we are making a call to try_push_valid for each block in a list item, rather than just for the whole item (outside of the loop). Intuitively, it looks like this would be incorrect behavior since blocks are an Avro implementation detail and our validity bitmap is tracking Arrow types (e.g. a list item).
I wasn't able to easily create a list in Avro that is stored as multiple blocks, so as to validate my assumptions, but wanted to open this issue in case it is an obvious bug. Thank you

Hey!
This is an interesting observation. Indeed this is incorrect.
I was also unable to create a file that fulfills this code branch, so could only rely on the spec for this. Fielded #1253 to address it.


About Us

If you would need someone to create and about us section for your project.  I can help you with that.

We already have that, actually :-)

What about frequently asked questions.  I can write that also
On Tue, Oct 16, 2018, 1:13 PM Nicolas Raoul<EMAIL_ADDRESS>wrote:

We already have that, actually :-)
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/commons-app/apps-android-commons/issues/1936#issuecomment-430213760,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AfjhQOgUau8VXhKLRWROGkY1w5e-MrOuks5ulc13gaJpZM4Xb1UO
.

Maybe check out improving the documentation on the wiki


Create ArmstrongNumber.py

This is a python code to test weather the number stored in 'x' is an armstrong number or not.

Follow rules to contribute!!!


[IE11]: Checkbox state and ng-model binding not in sync on calling preventDefault inside click handler

Description
Currently in our application we have a checkbox  with a ng-model binding and a click handler attached to it. We want our checkbox to be checked only if certain business logic is met. To prevent the checkbox from getting checked, we call the event.preventDefault() method inside of our click handler attached to our checkbox element. Though the preventDefault() prevents the checkbox from being checked, but in IE11 it can be observed that the ng-model binding is updated, i.e binded variable has default value set to false, the value now updates to true, but the checkbox state remains unchanged. Also, this can be observed only when we click on the checkbox for the first time, after that on clicking on the checkbox the value remains unchanged if we call preventDefault() method.
🔬 Minimal Reproduction
Here, is the plunker for the issue described above:
http://plnkr.co/edit/FP34eXyPVZu5G9wN?preview
Note
It was observed that before version- 1.7x , the above mentioned issue could be observed in all the browsers. But for angular.js 1.7+ it can only be seen in IE11. Here is the plunker  using version 1.6.0:
http://plnkr.co/edit/oKDonlG8XnKEGn8k?preview
Also, on looking into the source code. It was found that currently for input checkboxes listen to the change event for model updates. Which can be seen here:
https://github.com/angular/angular.js/blob/8aa3389ed66bbf022c6b854f7a64a8c973849843/src/ng/directive/input.js#L2011
It works fine in Chrome/firefox as the change event in these browser is triggered after the click event. So in case we call preventDefault() method in our click  event handler the checkbox state is not changed. However in case of IE11 the change event is triggered before the click event.

Thx for reporting the issue, @Amrender-Singh. I am not sure this is something that would need to be fixed in AngularJS (AngularJS uses the change event - it is expected that cancelling the click event will not necessarily cancel the change event).
In any case, AngularJS is in LTS mode now and this issue does not satisfy the criteria for the issues we are providing fixes for. So, I'm afraid this is not going to be fixed.
If you find a solution or work-around, feel free to post it here for others that might be having the same issue.

The workaround for this issue could be to call the $setViewValue method inside the change event listener of checkbox input inside setTimeout in case of IE only . so the updated checkboxInputType function implementation could be:
function checkboxInputType(scope, element, attr, ctrl, $sniffer, $browser, $filter, $parse) {
  var isIE11 = !!window.MSInputMethodContext && !!document.documentMode;
  var trueValue = parseConstantExpr($parse, scope, 'ngTrueValue', attr.ngTrueValue, true);
  var falseValue = parseConstantExpr($parse, scope, 'ngFalseValue', attr.ngFalseValue, false);

  var listener = function(ev) {
    if (isIE11) {
      setTimeout(function() {
        ctrl.$setViewValue(element[0].checked, ev && ev.type);
      });
    } else {
      ctrl.$setViewValue(element[0].checked, ev && ev.type);
    }
  };

  element.on('change', listener);

  ctrl.$render = function() {
    element[0].checked = ctrl.$viewValue;
  };

  // Override the standard `$isEmpty` because the $viewValue of an empty checkbox is always set to `false`
  // This is because of the parser below, which compares the `$modelValue` with `trueValue` to convert
  // it to a boolean.
  ctrl.$isEmpty = function(value) {
    return value === false;
  };

  ctrl.$formatters.push(function(value) {
    return equals(value, trueValue);
  });

  ctrl.$parsers.push(function(value) {
    return value ? trueValue : falseValue;
  });
}


[v2] Refactor Vivisector

It's time to refactor Vivisector.

Type-specific implementations need to go. We've no reason to differentiate here. Only objects and arrays need listener functionality.
Rework the core API.

Acceptance Criteria
As a consumer...

I should be able to instantiate an event-bound object without any configuration.
a. All mutating methods on that object should emit a default event.

I should similarly be able to instantiate an event-bound object according to a configuration object I have passed to it. For example:
const obj = { a: 1, b: 2 };
const eventedObj = vivisect(obj, {
  onGet: {
    watch: 'get',
    handler: (args) => {
      console.log(`Handler for ${args.type}fired`);
    }
  },
  onSet: {
    watch: 'set',
    handler: ...
  }
});

eventedObj.a; // 'Handler for get fired'

I should be able to register a single callback for each event type (this will change eventually).

I should be able to de-register a callback using the event name for which it was registered.

I should be able to fully revoke all modifications to a Vivisected object.
Example:
eventedItem.revoke();

I should be able to pass actual methods as watch values, provided these methods are valid and applicable to the target object type. For example:
const arr = [1, 2, 3];
const eventedArr = vivisect(arr, {
  onPush: {
    watch: Array.prototype.push,
    handler: ({ type }) => {
      console.log(`Handler for ${type}fired`);
    }
  },
  onPop: {
    watch: Array.prototype.pop,
    handler: (...) {...}
  }
});

eventedArr.push(4); // 'Handler for onPush fired'

I should be able to add event listeners on the object directly.
Proposed API:
a. Adding a handler for a default event:
const eventedArr = vivisect([1, 2, 3]);

eventedArr.addEventListener('push', (args) => { ... });

b. Defining a custom event name:
const eventedArr = vivisect([1, 2, 3]);

eventedArr.addEventListener({
  name: 'onPush',
  watch: Array.prototype.push,
  handler: (args) => { ... }
});

Adding an event listener for an event that has already been registered should overwrite the original handler with the new one:
// we get default `get` and `set` events
const obj = vivisect({ a: 1, b: 2 });
const getHandler = (...) => {...};

// currently, `obj` emits `get` and `set` but nothing is listening to them
obj.addEventListener({
  name: 'get',
  watch: 'get',
  handler: getHandler
});

// we've registered a callback for the existing `get` event

obj.addEventListener({
  name: 'onGet',
  watch: 'get',
  handler: getHandler
});

// the only thing that has changed is the event name

Each event should emit:
a. event name
b. original data
c. new data
d. operation name
e. operation arguments

For now, erroneous operations should log to stdout but no error should be thrown (add TODO tags).

:tada: This issue has been resolved in version 1.4.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


UI Graph View legend displays incorrect information

Leader and oldest node legend texts are shown incorrectly

Assigning to myself through this comment.


List the PackageIdentifier of the package to be added to automation
Nutstore.Nutstore
Details about the application
(Invoke-WebRequest -Uri 'https://app.jianguoyun.com/static/exe/latestVersion' -UserAgent 'NutstoreApp-6.2.4').Content | ConvertFrom-Json | Where-Object {$_.OS -eq 'win-wpf-client'}

Use stVer as PackageVersion and fill in
https://www.jianguoyun.com/static/exe/installer/$ver/NutstoreInstaller_$ver.exe
to get the InstallerUrl.
e.g. https://www.jianguoyun.com/static/exe/installer/5.2.4/NutstoreInstaller_5.2.4.exe

Is UserAgent necessary? I can access it normally.

"pkgid": "nuttyartist.notes",
It seems that the pkgid in /packages/n/nutstore.nutstore.json is wrong.

I've fixed it. Thanks for catching that.

The source URL can be changed to https://www.jianguoyun.com/static/exe/latestVersion which doesn't need custom useragent.
For x64 and x86 installer:
PackageVersion: ($result | Where-Object {$_.OS -eq 'win-wpf-client'}).exVer
InstallerUrl: https://pkg-cdn.jianguoyun.com/static/exe/installer/$ver/NutstoreWindowsWPF_Full_$ver.exe
For arm64 installer:
PackageVersion: ($result | Where-Object {$_.OS -eq 'win-wpf-client-arm64'}).exVer
InstallerUrl: https://pkg-cdn.jianguoyun.com/static/exe/installer/$ver/NutstoreWindowsWPF_Full_$ver_ARM64.exe


TSX files doesn't suggest component properties

This are the only props suggested in the autocomplete, @types for react router are installed, so it should suggest at least path and component.

Repro:
import * as React from "react";
import { Route } from "react-router"

class App extends React.Component {
	render() {
		return (
			<div>
				<Route path="" /*1*/ />
				<Route exact /*2*/ />
				<Route exact={true} /*3*/ />
			</div>
		);
	}
}

For the 3 markers, (1) has a completion that includes "" which is totally nonsensical, and all 3 exhibit the explained behavior.

Non-JSX repro of the same issue:
interface Foo {
    a?: number;
    b?: number;
}

function f<T extends Foo>(x: T) { }

f({/*1*/});

branch with a candidate fix (so I don't forget) is here. Has some issues with the ThisType<T> tag that I need to investigate before opening a PR and seems to regress services behavior for
window.addEventListener("error", event/*1*/ => {
	event.filename;
});

but not
interface EventListenerWithOverloads {
	addEventListener(type: "error", listener: (this: Window, ev: ErrorEvent) => any, options?: boolean | AddEventListenerOptions): void;
	addEventListener(type: "beforeunload", listener: (this: Window, ev: BeforeUnloadEvent) => any, options?: boolean | AddEventListenerOptions): void;
}

declare var ev: EventListenerWithOverloads;

ev.addEventListener("error", event/*1*/ => {
	event.filename;
})

which I'll need to look into as well.
I've long held that getContextualType needed to not be reentrant with inference, and with that branch, that is the case. The effect is that completions are a lot better (they come from the uninstantiated signatures now) and that literal types are retained in calls with errors and that an inferred boolean type can no longer contextual type itself. We've had a bunch of issues that essentially boil down to this same underlying flaw in contextual typing - I'll need to gather them all up along with their test cases.

This has been fixed since #36556 went in.


PSReadLine holds on to thread that Polaris uses

On macOS, Polaris, (which uses Register-ObjectEvent) hangs until you hit a key in the terminal. Then it processes the request.
This looks suspiciously similar to the issue we saw in PowerShell Editor Services that @SeeminglyScience fixed.
I haven't tested on Windows, but I have a feeling this doesn't happen.

Yeah Polaris running as a job works so 3 is at least fine for now....

Got some feedback on this today from a few people. Really should address this somehow... I don't know if I want to go down the "private" contract plan (although I appreciate @lzybkr for adding that). I wonder if I should stop relying on Register-ObjectEvent on unix and just hold on to the prompt and process events in a while loop.
Sucks to have to take away the prompt from the user, but this is what Node.js does today so I'm not too upset.

We could offer two modes maybe?

I opened https://github.com/PowerShell/PowerShell/issues/8478 to see if the PowerShell team has any suggestions or believes it to be a bug.

Thanks @Tiberriver256 😃
I think 2 modes makes sense.

default behavior
-ControlProcess or something to signify that Polaris will hold onto the pipeline thread until stopped

Question from #194 via @mikeTWC1984:

Is there any news on PSReadline/*nix issue?
I'm looking for some work around that allows to use Polaris and keep PSReadline. I guess you mention this can be fixed by replacing Register-ObjectEvent whith a while loop. Is it an easy change? If so, can you show any sample code?
Btw, I noticed that this issue disappears if starting Polaris from VSCode Powershell Integrated console

Moved to keep discussion in one main thread

There have been a few suggestions above and my guess as to why it works in VSCode is because of what SeeminglyScience has done to make it work (as referenced above).
@SeeminglyScience - Do you have the code handy somewhere you used to override the delegate in PSES?

@Tiberriver256 Now that I think about it, the same route PSES takes isn't feasible here.  PSRL only checks for the override at process start (or more specifically, it only checks the first time it calls ReadKey).  In order to override it after that, you'd need to alter a field that isn't part of the private contract PSRL has with PSES.
Even if you did choose to do that, you'd still need to rip out the custom async version of ReadKey in PSES, and ship the native lib UnixConsoleEcho.  All of that is a pretty hefty lift.  I should also stress that it's not supported without getting the PS team to extend the PSRL/PSES private contract to Polaris.
Tbh I'd recommend putting some more attention on dotnet/corefx#25036 over reusing our hacky workarounds.

OK, thanks for the info. It doesn't sound like that ReadKey issues is anywhere close to resolution though. I was looking for a hack just because I want to use Polaris as a back-end for Jupiter like app, so need to keep PSReadline. One of the suggestion above was about running it as job, but didn't work. But it works if running in a separate runspace, so I'll stick to it for now. Other was to use while loop vs event, just not sure how to implement it.
Wondering if switching to a binary module can fix that problem. I played with Universal Dashboard, it has similar feature to generate rest end points from script block. And it seem to work on Linux just fine (he seemed to use kestrel though).

I'll leave my workaround below, in case anybody also looking for options

function New-PolarisServer { param($port=8888)

    $ps = [powershell]::create()

    $info = $ps.AddScript({param($p)

      Remove-Module PSReadline
      New-PolarisGetRoute -Path "/" -Scriptblock {
        $response.send(($PSVersionTable | Select-Object OS, PSEdition, Platform, PSVersion | ConvertTo-Json))
       }
      Start-Polaris -port $p

    }).AddParameter("p", $port).Invoke()

    $AddRoute = { param([string]$route, [scriptblock]$sb, [string]$method="GET")
       $this.ps.Commands.Clear()
       $this.ps.AddCommand("New-PolarisRoute").AddParameters(@{
           Path=$route; ScriptBlock=$sb; Method=$method; Force=$true
          }).Invoke()
    }

    $Dispose = {
      $this.ps.Commands.Clear()
      $this.ps.AddCommand("Stop-Polaris").AddCommand("Clear-Polaris").Invoke()
      $this.ps.Dispose()
    }

    $obj = [PSCustomObject]@{ ps = $ps; info = $info }
    $obj | Add-Member -MemberType ScriptMethod -Name AddRoute -Value $AddRoute
    $obj | Add-Member -MemberType ScriptMethod -Name Dispose -Value $Dispose

    return $obj
}

<# Usage

 $p = New-PolarisServer -port 8000
 $p.AddRoute("/hello", {$response.send("Hello there")} )
 iwr http://localhost:8000/hello
 $p.Dispose()
#>


Error message

Describe the bug
If the token is invalid the user gets:
$ export SUPERVISOR_API_TOKEN=wrong_token
$ ./ha os info
ERRO[0000] Unexpected server response
Unexpected server response

Output of ha --version
see #213

Expected behavior
For me, the error message should tell the user what's wrong (if possible) and not be generic.

This information is not provided from upstream.

The possibility for setting a token is merely used for development and debugging, in the environment where this tool is used, the correct tokens are automatically provided.

Not according to the README. There it's a selling point...

Let's adjust the README to make that clear in that case.

This issue tripped me a bit too, #267 make it print the status code if it is unexpected, which leads to Unexpected server response. Status code: 403. This points much more to an authentication issue like a wrong token...


⚠ Processors has degraded performance

In bcf46ce, Processors ($STATUS_URL) experienced degraded performance:

HTTP code: 200
Response time: 110 ms

Resolved: Processors performance has improved in a7d9ae8.


deps!: upgrade django major version

Thanks for submitting a PR! Please check the boxes below:

[ ] I have run pre-commit to check linting
[ ] I have added information to docs/ if required so people know about the feature!
[ ] I have filled in the "Changes" section below?
[ ] I have filled in the "How did you test this code" section below?
[ ] I have used a Conventional Commit title for this Pull Request

Changes
Please describe.
How did you test this code?

Please describe.

@gagantrivedi just a heads up that I've updated the title of this PR to mark it as breaking


fixed comma issue in README.md

Fix/Feature/Other
Fix

[added comma in the README.md that will increase the ease in copying the commands and make the user to focus on real features ] Description

Hi @RahulAwasthi314 ,
I think something went wrong here. I would suggest opening a new Pull Request to the branch master


Ability to edit WordPress content and push changes as a pull request

As a geoscientist working on the RiskProfiler website, I want to be able launch a local copy of the WordPress website, edit contents (e.g. create training modules) and have the changes be pushed automatically to the Git repository as a pull request so it can be reviewed and deployed with ease.
(This is from an unfinished subtask from Issues #4 and #6.  This goal deserves its own issue.  :grin:)

We could export the site edits as a MySQL database dump, but it would likely be very difficult to merge with future MySQL database dumps from HabitatSeven our upstream website developer.
Maybe there is a better solution out there that can encapsulate the local site edits at a higher level that can be "replayed" and thus cleanly imported by anyone.
To be explored.


Unexpected token errorindex.js:14

I am using bower and gulp for my project. I am having an issue since bower.json file's "main" path was changed from "/build/dat.gui.js" to "index.js" in the 0.6.X versions.
I get Unexpected Token Error in index.js at line 14 when I run my project.

I've changed it back to './build/dat.gui.js'. Thanks for filing the issue


Is this project still alive?

Good evening,
I'm trying to use svg.connectable.js through NPM, and the connection lines appear are nowhere near the SVG elements. Also, I've noticed the example page isn't working.. which leaves me wondering.
This is a great project and I'll sure fork it and help when I've got a bit more time in my hands!
--EDIT--
It just doesnt't work on Chrome. works perfectly on Safari and Firefox...
Thank you,
Pedro Antoninho

From what I remember, there is a simple fix for this: upgrading to the latest svg.js release, and fixing some little things in the code.
It's because Chrome deprecated a functionality used by this library.
I currently don't have time to work on this, but I'd be happy to accept contributions! :sparkles:

It's working now in Chrome too. Thanks, @andrewrota! /cc #19


add go vet etl to check etl dependencies

etl now depends on ndt-server.  This adds go vet on the etl repo to ensure we don't break it.

This change is

Pull Request Test Coverage Report for Build 790

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.2%) to 73.237%

Totals

Change from base Build 786:
0.2%

Covered Lines:
1412

Relevant Lines:
1928

💛  - Coveralls


Add support for almalinux in lisav3

Add new class of almalinux;
Add ID_LIKE support;

LISAv3 test cases "smoke_test", "lsvmbus_count_devices_channels", "timesync_check_unbind_clocksource", "timesync_check_unbind_clockevent" have been passed running on AlmaLinux.

The two commits have the same purpose, they should be merged.


Fix table format for SDXL and add SDXL bandwidth formula

@mrmhodak Hi Miro, this PR fixes a format error and adds SDXL system bandwidth formula. Could you help review it?


Get user's real IP address using package.json proxy

Is this a bug report?
Not sure
I love the use of proxy in package.json and it all works well, though I'd like to get the real user's IP address in the proxy request, though it always gets the local one 127.0.01 (which is understandable).
In Nginx, it is passed through a header such as x-forwarded-for.
I wonder if there's any implementation of passing the real IP address through the proxy?
Did you try recovering your dependencies?

Yes
Which terms did you search for in User Guide?

package.json proxy, react proxy ip address, react get ip address from proxy
Environment

Local environment
OS:  Windows 10
Node:  8.11.2
Yarn:  1.5.1
npm:  5.6.0
Watchman:  Not Found
Xcode:  N/A
Android Studio:  Not Found
Live environment
OS:  Linux 4.4
Node:  10.4.0
Yarn:  1.7.0
npm:  6.1.0
Watchman:  Not Found
Xcode:  N/A
Android Studio:  Not Found
Steps to Reproduce

No real steps here
Expected Behavior

Some documentation or implementation of how to get the user's IP address using the package.json proxy's feature.
Actual Behavior

Didn't find the IP address in the request (live server)
Remote and local addresses were both <IP_ADDRESS>
Reproducible Demo

Not relevant (imo)

Thanks for any help!

You'll be able to define your own proxy middleware in version 2, which should be released soon. See here for details: https://github.com/facebook/create-react-app/pull/5073

Thanks for your response @iansu , that would probably do.

Yeah, you can access the headers through the request object in your middleware function. I'll close this since it's resolved in 2.0.

This is already released under the next beta (just switch to the next tag).


Creation date account

Hi, I know that I already created a similar topic, and it was said that it is impossible to implement, but at that time I did not remember where I saw it, now I found it. DSharpPlus has User has the object CreationTimestamp, with which you can get the date of creation of the account, the examples below.
DateTime CreationDate = discord.GetUserAsync(123456).GetAwaiter().GetResult().CreationTimestamp.Date;
In the end, we get the date -

Try it now :)

Interesting! DSharpPlus is actually grabbing this timestamp off of the user's ID...which they apply to every entity. See: https://github.com/NaamloosDT/DSharpPlus/blob/master/DSharpPlus/Entities/SnowflakeObject.cs
I had completely forgot that the ID's contain this information. You can actually get a user's creation date in Discore currently then. Create a Snowflake instance around their ID (if you don't already have it as a Snowflake). Then call GetTimestamp(). You can either use the Snowflake constructor or actually cast a ulong to a Snowflake to access the method. This is the method I'm talking about.
So for example if you don't just have the raw number and have a user object instead:
DiscordUser someUser;
DateTime creationDate = someUser.Id.GetTimestamp();

Sorry for closing your previous issue, it's been a long time since I wrote the Snowflake file. :)

Yes, thanks )