Why does register-version.js still mentions 1.1.1?

It was just an oversight with the last release. See the comments on this commit:
https://github.com/dustinfarris/ember-django-adapter/commit/92b466b132df3b56610e5ee21ac1d8f0714402c6

Thanks for letting me know!
--

Am 08.04.2016 um 18:20 schrieb Ben Konrath<EMAIL_ADDRESS>Closed #156.
—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub


xephero layout won't resize

I've loaded the xephero html into a cactbot overlay and resized the overlay to the width I want, but the actual content does not resize with the overlay -- it just stays a small size taking up only a small corner of the available space.  Am I missing something? Does CSS need to be edited somewhere?

I prefer to have my dps meter to not be super huge if it doesn't need to be.  If folks have long names, it will take up up to the width you specify, but otherwise be as small as it needs to be.
If you want to make it bigger, create a file called cactbot/user/xephero.css and add this in it:
#overlay {
  width: 100%;
}

That I just fixed in d1e158a, sorry.

Is there more to be fixed here, other than the ellipses issue?


Publishing an invalid Wasm doesn't throw

It should throw.

What do you mean by invalid WASM--an invalid WASM file, you mean? The Workers API has nothing like a validator for uploading WASM (only js scripts) so I think this feature may be blocked by the API performing WASM validation (unless we want to introduce validation logic in Wrangler, and therefore spread validation logic across code bases. I am strong against that).

this should be implemented in the api.


vim --version hangs on GitHub Actions Windows runner

Steps to reproduce
First, prepare the following GitHub Actions workflow for reproducing this issue.
name: Bug
on: push

jobs:
  bug:
    runs-on: windows-latest
    steps:
      - run: Invoke-WebRequest https://github.com/vim/vim-win32-installer/releases/download/v9.1.0631/gvim_9.1.0631_x64.zip -OutFile gvim_9.1.0631_x64.zip
      - run: Expand-Archive gvim_9.1.0631_x64.zip unzipped
      - run: unzipped/vim/vim91/vim.exe --version

Then push the workflow to your remote repository on GitHub.
The workflow hangs at the following step without any output to stdout and stderr:
- run: unzipped/vim/vim91/vim.exe --version

This is my reproduction: https://github.com/rhysd/misc/actions/runs/10131456929/job/28014171927
I'm maintaining the action to setup Vim for testing plugins on CI. The repository has a CI workflow for weekly check. On the last week it ran successfully but this week it didn't.
I noticed that vim.exe --version hung. I manually bisected this issue with versions of Vim released on vim-win32-installer.

9.1.0631 hangs
9.1.0626 doesn't hang
9.1.0618 doesn't hang

So I guess there was some regression on Vim after 9.1.0626.
Related to: https://github.com/rhysd/action-setup-vim/issues/37
Expected behaviour
I expected that the workflow ran successfully with outputting the version information.
Version of Vim
9.1.0631
Environment

Operating system: Windows (windows-latest runner on GitHub Actions)
Shell: Powershell
$TERM: Nothing

Logs and stack traces
No response

I enabled VIMDLL in the latest version of vim-win32-installer. Now the core part of Vim is in vim{32,64}.dll and (g)vim.exe is just a small executable file to load the DLL.
This might be related, but I don't know why it happens. The executable file passed our CI in vim-win32-installer and worked in my local environment.

@k-takata Thanks for the explanation.
I downloaded gvim_9.1.0631_x64.zip and unarchived it by unzip. And I tried to find the vim{32,64}.dll but I could not find it. Could you tell me where the DLLs are included in the released assets?
$ cd /path/to/vim/vim91/
$ find -E . -type f -regex '.*\.dll$'
./libintl-8.dll
./GvimExt32/libintl-8.dll
./GvimExt32/libiconv-2.dll
./GvimExt32/gvimext.dll
./libsodium.dll
./winpty64.dll
./libiconv-2.dll
./GvimExt64/libintl-8.dll
./GvimExt64/libiconv-2.dll
./GvimExt64/gvimext.dll

@k-takata Thank you for the explanation. As you said, I confirmed that the latest v9.1.0631 asset has the DLL file. Someone confirmed that the vim.exe worked fine on Windows machine locally as well. So I believe this is an issue related to the environment on GitHub Actions.

GitHub Actions runs the following command exactly. It may reproduce this issue locally (I currently don't have Windows machine personally so I cannot try it...):
C:\Program Files\PowerShell\7\pwsh.EXE -command ". 'vim --version'"

I've just connected to GHA via Remote Desktop and found the reason:

Now vim.exe and gvim.exe share the same core, so OLE is enabled even in vim.exe.
Please add the following line before running vim --version:
unzipped/vim/vim91/vim.exe -silent -register

Ah, nice catch. I confirmed the command fixed this issue in my repro.
I'm honestly not familiar with the mechanism on Windows. Is the following command needed to be run once when install Vim?
unzipped/vim/vim91/vim.exe -silent -register

Is the following command needed to be run only once just after installing Vim?

Yes. You can also see the example in the CI script of vim-win32-installer:
https://github.com/vim/vim-win32-installer/blob/3373cc66f7a576ca50e087cb3fc899673b70611a/appveyor.bat#L268-L273

@k-takata I have a project that builds an msi installer from the nightly, the action hung this morning while installing the msi as a test.
The msi executes the following custom action as an elevated process during installation:
"[INSTALLDIR]gvim.exe" -silent -register

However that now fails for some reason, disregards the -silent parameter, and opens a message box.
Do you think this is related?

@k-takata Thanks for the clarification! I will update my action to avoid the GUI dialog. Closing.

@jcasale It looks like a different issue. Is vim64.dll (or vim32.dll) included in the msi package?

and opens a message box.

What message?

Hi @k-takata The correct dll is included, and I was seeing the same message box as the OP.
I didn't realize other custom actions were invoking vim.exe to perform string replacements before the extension was registered.
Reordering them so the extension is registered first solved the problem, thank you very much.


cook gpu support don't work?

I have mesos 1.4.0 on 1 hosts with registered 0/1 GPU in agent. Cook 1.11 is also registered but it gets no offers. Without gpu it get offers. I've tryied adding ":gpu-enabled true" to config.edn in :mesos and :scheduler sections without luck... any clues?

Hey @dPeS, can you explain what you mean by this:

Without gpu it get offers

In other words, what are you changing in your environment to make Cook receive offers?

all I change is: ec2 instance type - I have ansible code that provisions host is the same way
I think that:
http://mesos.apache.org/documentation/latest/gpu-support/#framework-capabilities
has sth to do with that

to be precise... cook works normal (cs submit sleep 10) on m4.xlarge instance but don't work on p2.xlarge which has gpu (nvidia driver) and auto registered 1 GPU in mesos agent

Can you provide the configuration file you started cook with?
On Tue, Mar 20, 2018, 6:36 AM dPeS<EMAIL_ADDRESS>wrote:

to be precise... cook works normal (cs submit sleep 10) on m4.xlarge
instance but don't work on p2.xlarge which has gpu (nvidia driver) and auto
registered 1 GPU in mesos agent
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/twosigma/Cook/issues/765#issuecomment-374549882, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ABZnHWDZv0JGqJ7x3r5NPgHBN1v9YzNFks5tgNulgaJpZM4Sr0BZ
.

sure...
config.edn.txt
run-local.sh.txt

as I said I've tryied to add ":gpu-enabled true" in different places without luck

@dPeS Would you mind adding :enable-gpu-support true directly beneath :failover-timeout-ms and re-running? It sounds like you may have had an incorrect key name.

@wyegelwel sure, will do asap and back to you, thanks for tip!

You're welcome, good luck!
On Tue, Mar 20, 2018, 4:48 PM dPeS<EMAIL_ADDRESS>wrote:

@wyegelwel https://github.com/wyegelwel sure, will do asap and back to
you, thanks for tip!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/twosigma/Cook/issues/765#issuecomment-374751142, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ABZnHaoYdzCNSMp9f51PbfQsfw1MD87mks5tgWsNgaJpZM4Sr0BZ
.

@wyegelwel well I have two infos: bad and good...
bad: placing :enable-gpu-support true in config didn't helped
good: with that: https://github.com/twosigma/Cook/pull/772 it works

I'll take good and bad to only bad :)
Thanks for tracking down that bug and I'm glad it is working for you now.
On Wed, Mar 21, 2018, 11:09 AM dPeS<EMAIL_ADDRESS>wrote:

@wyegelwel https://github.com/wyegelwel well I have two infos: bad and
good...
bad: placing :enable-gpu-support true in config didn't helped
good: with that: #772 https://github.com/twosigma/Cook/pull/772 it works
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/twosigma/Cook/issues/765#issuecomment-374971718, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ABZnHbokh-hxfgxuaH5uOX1KUAJ0Lp0-ks5tgm0bgaJpZM4Sr0BZ
.

sure, np - thanks for great tool! cheers Daniel

Closed with #772


Update README.md

Add notes on shortcut key to navigate between suggestions.

Thanks for the update @kwokhou!


Online Food Ordering Website

Describe the project
It's a online food ordering website created through HTML,CSS and javascript.
Issue Type:

[ ] Bug Report
[x] Feature Request
[ ] Documentation
[ ] New Project

Additional context
Add any other context or screenshots about the project here.
Watch it at Loom
https://www.loom.com/share/5bc1b79a19f644a0997d8a28874dac6a
Screenshots

If applicable, add screenshots to help explain your problem.

This project is already present in the repo


Different way of determining what tree a player is chopping

Determine what a player is chopping by storing all the tiles of trees in a HashMap and querying it with the tile that the player is facing. This should speed up the original code while also using a bit more memory (probably still negligible?). I don't believe there are any cases in forestry where the target of chopping isn't the tile in the direction you're facing.
There also is some other stuff in here to tidy up some code but that can be picked through if needed.

Wasn't expecting anyone to contribute to this to be honest, but I'm glad you did. I didn't consider to store the tiles to do a linear lookup instead of looping through each tree. Your changes also resolved the micro-stutters faced as described in #13 in cases where you load in lots of players chopping. I didn't notice any stutters anymore especially during rising roots. From the basic profiling I did obviously performance increased and memory was negligible like you said, it was basically on par with current master so not an issue.
Everything looks good and I didn't find any issues except for one:
This PR (228f01261d1c7123fbc213890d3be00d3e3031c9)
https://github.com/Infinitay/tree-count-plugin/assets/6964154/7c9e99a8-ded1-4d5b-a493-c4548f4b12ef
As you can see there are times where it doesn't recognize the player is chopping a tree immediately after moving. It doesn't matter if you walk one tile or run more than one tile (which was shown in the video).
Master (06c9d452e22a66c448a1c6fe6577c70ee174012d)
https://github.com/Infinitay/tree-count-plugin/assets/6964154/38901914-5642-474d-a44d-90cffc1cd8ef
Couldn't replicate the issue in master. However, I do feel like it happens in some form minus the issue. If you want closely it feels like the overlay stutters sometimes, so I think it happens but it corrects itself
If I had to guess, there's an issue regarding orientation changing

https://github.com/Infinitay/tree-count-plugin/assets/6964154/7d79493c-0bbc-4ce0-b144-1ae7f33f07bc
Honestly I'm not seeing a fix immediately. The issue seems to be within #findClosestFacingTree. As you can see, my version also has an issue, but it corrects itself. However, in your version it doesn't update at all. Which is odd because in the logs it recognizes the new direction and finds the right tree, however the overlay fails to render.
I thought the issue was due to the orientation map not being updated properly (see https://github.com/Infinitay/tree-count-plugin/pull/15/files#diff-6baa5773d3e67cd998c466bbe8727d5c50750de4945399e1567119bbb3621d70R381 and in master too, my mistake) because closetTree would be null and it would return out of the method without updating the playerOrientationmap. However, after moving the update to the appropriate location within #onPlayerOrientationChanged, it still was facing the same issue.
Even more odd, when I move playerOrientationMap.put(player, player.getOrientation()); (https://github.com/Infinitay/tree-count-plugin/pull/15/files#diff-6baa5773d3e67cd998c466bbe8727d5c50750de4945399e1567119bbb3621d70R381) into #onPlayerOrientationChanged and place it right after removeFromTreeMaps(player); (https://github.com/Infinitay/tree-count-plugin/pull/15/files#diff-6baa5773d3e67cd998c466bbe8727d5c50750de4945399e1567119bbb3621d70R342) because #removeFromTreeMaps also removes the orientation, it breaks my version too. To reiterate, I moved the orientation map update to be within #onPlayerOrientationChanged and right after we remove the old orientation. I've tried updating the orientation map with both the orientation from the event and by referencing the local player. Honestly, can't even figure out why it breaks master.

Would you mind updating your PR to master? I tested it out locally on my end and the issue was resolved. I'll approve the PR when the conflict is resolved. Feel free to further test it just to confirm I didn't ruin things even further, but everything seemed good to me.

Rebase was fairly straight forward. Didn't have much time to test though.

LGTM from the brief testing I did. I'll go ahead and merge your changes. Thanks again for improving the code!


IBC marker creation missing metadata

Summary of Bug
Marker metadata for markers created automatically for IBC denoms unexpectedly have the chain-id set to unknown
Version
v1.17.0-rc1
Steps to Reproduce
See ibc/5284F2F6A518924A0CBCA19B428DB5914625DD944B71C50932654D53BAE4F46A for an example.
provenanced query bank denom-metadata --denom ibc/5284F2F6A518924A0CBCA19B428DB5914625DD944B71C50932654D53BAE4F46A -t --node=https://rpc.test.provenance.io:443

metadata:
  base: ibc/5284F2F6A518924A0CBCA19B428DB5914625DD944B71C50932654D53BAE4F46A
  denom_units: []
  description: eth-wei from chain unknown
  display: unknown/eth-wei
  name: unknown/eth-wei
  symbol: ""
  uri: ""
  uri_hash: ""

example transaction - https://explorer.test.provenance.io/tx/26D1DF31C02BE7E236179FD01C496F78497CEAC3A70B0244FE34572304308B97/18469885

For Admin Use

[ ] Not duplicate issue
[ ] Appropriate labels applied
[ ] Appropriate contributors tagged
[ ] Contributor assigned/self-assigned

Seems like the kind of thing we will end up updating via governance to fill in extra data that isn't given... while we are in here we should verify the process applied if these values are already set (via governance for example)

@jtalis The testnet upgrade to v1.17.0-rc2 has fixed this issue.  The description is modified from <denom> from chain <chain-id> to <denom> from <chain-id>.  Therefore, the  ibc/5284F2F6A518924A0CBCA19B428DB5914625DD944B71C50932654D53BAE4F46A marker has a denom description of eth-wei from axelar-testnet-lisbon-3.


[CPS-759]fix: use O_TRUNIC flag when updating config file

What this PR does / why we need it:
When updating the filebeat config file, some content from the old file could persist to the new one. Solved by using O_TRUNIC flag when updating config file
Which issue(s) this PR is related to (optional, link to 3rd issue(s)):
Fixes #
Reference to #

Special notes for your reviewer:
/cc @caitong93 @supereagle

Release note:

NONE

/lgtm

/cherry-pick release-1.1-wanda

/cherrypick release-1.1-wanda


Geo coordinates are the other way around

LAT is LON and LON is LAT.
if you use how the documentation tells you to - you are in wrong location.
this doesnt work (points not to NY):
https://linvi.github.io/tweetinvi/dist/streams-v1.1/filtered-stream-filters.html
stream.AddLocation(new Coordinates(-74, 40), new Coordinates(-73, 41));

this works
stream.AddLocation(new Coordinates(40, -74), new Coordinates(41, -73));

if you examine Coordinates object it shows LAT number in LON field and vice versa.
I think we settled this ages ago and it did work in older versions. Please stop changing the core behaviour. I wasted an hour trying to figure whats wrong after upgrade to v5

Sorry about this. I unified all the methods across Tweetinvi in 5.0 to use the same order for the parameters.


Canvas to image outputs black images on device with low RAM

I'm trying to export my page to PDF. Everywhere it works fine, but on Macbook Air the browser (tested chrome and firefox, newest versions) freezes and after a while it gives me pdf with just first one or two pages that looks ok and rest is black.
I know that this is not really html2canvas problem, I'm just hoping you have encoutered similiar problem already and can help me somehow.
My steps:

preformat markup to pages, so it will be aligned to pdf pages exatly as I want
convert markup via html2canvas to canvas
export canvas to images via canvas.toDataURL("image/jpeg", 0.9)
put these images into jsPDF

The problem occurs in the moment when I try export canvas to image. Canvases are fine, and after export the last few images are black. I'm pretty desperate here, because I don't even know how to detect that user is low on RAM and disable this feature for him.
Any help/suggestion appretiated.

Is this still an issue with v1.0.0? If so, could you please share an example on jsfiddle.


Conv error when passing sharded input in Segformer

Describe the bug
Conv error (possible number overflow) when passing a sharded input, while it passes with interleaved input
To Reproduce
Steps to reproduce the behavior:

Go to branch mbahnas/segformer_wh_optim
Run pytest tests/ttnn/integration_tests/segformer/test_segformer_encoder.py

Expected behavior
purest to Pass
Screenshots

Please complete the following environment information:

OS: [e.g. Ubuntu 20.04]
Version of software (eg. commit)

Additional context
Add any other context about the problem here.

I've tweaked the code of the test in order for it to pass with shared code-path
https://github.com/tenstorrent/tt-metal/tree/pjosipovic/segformer_wh_optim
This one is not conv related.

I confirm, thanks @pavlejosipovic


Screen width, height, and FOV function and Rotation(?) for the AR Goggles/Controller

Describe your idea
Function(s) to get the width/height (getsize) in pixels of the players screen allowing a few things:

Centered display stuff on the AR Goggles such as cross hair display stuff
Centered display stuff on screen edges (Matching the hotbar, middle of sides, etc)
Paired with a getFOV and getRotation functions (These for some reason display in my game but always return 0) you could draw "blocks" that aren't really there (the visuals would be limited for certain) for intance an overlaid floor map could be drawn, this would of course require getting the players position which could be done many ways

Function to get the FOV of the player

Combined with a getSize and rotation and position this lets you compute positions in 3d space back to the player

Rotation get functions would also be helpful however it seems these may already be present as they show in my game on the AR controller peripheral, however they don't really work in anyway just returning 0 constantly and not throwing an argument error.
These functions could all either use a AR Goggle id (visible on the goggle), grab only the latest goggle assigned to the controller, or could use a player name and return nil if that player isn't wearing goggles bound to that block.
There are clear problems here like players with different FOVs and game display sizes all wearing goggles bound to one block. I also don't know if it's even possible. Still it would be very cool to have functions like this to draw centered to the screen and be able to draw stuff that appears in the world.
Describe alternatives you've considered if you've any
The only alternative I really have is players have to manually enter their FOV and game display size into the controlling computer somehow which while it works is very limiting.
Additional context
No response
Linked Issues
No response

Here's a possible solution for handling multiple players: You could potentially return a numerically indexed table that is numerically ordered based on the order of paired glasses. So, the first pair would always be entry 1 in any returned table. If the player is out of range or not present, it could just return 0 or something within the entry.
Just a thought.


Remove support for callbacks in models

Callback support adds unneeded complexity. Models should be exclusively promise based version ^4.1.0. https://github.com/node-oauth/node-oauth2-server/issues/20#issuecomment-943633108

I agree, however

this will be breaking, thus a new major release imo
all tests will have to be manually checked against false-positives and false-negatives
some tests may require to be updated
if we use promises we can also safely write async functions as they should be natively supported with node >= 12
then we can also use async functions for async mocha units
I still would like to get the release management issue resolved first

@jankapunkt By next major version do you mean v5?  As far as I understand that's  the migration to TypeScript correct? If thats the case it would be nice to do this before all that happens. I think removing support for callbacks can happen now, as we move from v3 to v4.
We don't really have to do much, just update the documentation and perhaps put a warning message if people try to use callbacks: "support for callbacks has been deprecated—we recommend using Promises in your models since this may have adverse effects in future minor releases". Since we've officially removed callback support at v4 and have given people fair warning we should be ok to remove callbacks at any time during the v4 lifecycle.

Vice verca this means if we don't break big changes then we can easily do this as 4.1.0

@jankapunkt, @HappyZombies I found some time to work on this a bit today. I removed bluebird and promisify-any on the abstract-grant-type.js. Restricted the tests.
If you get some time take a look and let me know if you have any questions/concerns: https://github.com/node-oauth/node-oauth2-server/commit/4a360eee835feeb6899740d01cf76692b466523e. If all looks good I'll continue to chip away at this.

@jwerre do you mind open a draft PR so we don't forget you working on this? I will check it out later but I want to focus on some of the security-related issues for the next days.

Callback support dropped in 5.0.0 see #190


tray icons not visible in polybar

I have disabled the bar and also set force_no_tray=1 in the bar config. I have corectrl and nm-tray on the tray and bothof them are running in the backgroudn just not visible on the tray

when I am using the default bar, there is still not tray. i have it in the module section

tray doesn't save icons between reloads.

I does not show icon even when I launch hypr
On Sun, 12 Feb 2023 at 14:55, Vaxry @.***> wrote:

tray doesn't save icons between reloads.
—
Reply to this email directly, view it on GitHub
https://github.com/hyprwm/Hypr/issues/105#issuecomment-1427053409, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AYO4G4P4ZIWRLFS5Z4HEZUTWXD2WRANCNFSM6AAAAAAUZGPGGE
.
You are receiving this because you authored the thread.Message ID:
@.***>


"Huruiești", "Căpotești", "Florești", "Fundoaia", "Ocheni", "Perchiu", "Prădaiș" are villages in "Huruiești" common, "BACĂU" county

Description : When user is typing the villages in the search bar, the locations should appear in the dropdown menu correctly spelled and with localities information (as in Law nr. 2 din 16 februarie 1968)
Preconditions : the website (https://peviitor-ro.github.io/ui.orase/) is up and runing.
After every step delete the text you typed from the search bar.

Steps 1: Click on the search bar and write "Huruiești"
Expected result: In the drop down menu you find "Huruiești, Bacău"

Steps 2: Click on the search bar and write "Căpotești"
Expected result: In the drop down menu you find "Căpotești, Bacău (Huruiești)"

Steps 3: Click on the search bar and write "Florești"
Expected result: In the drop down menu you find "Florești, Bacău (Huruiești)"

Steps 4: Click on the search bar and write "Fundoaia"
Expected result: In the drop down menu you find "Fundoaia, Bacău (Huruiești)"

Steps 5: Click on the search bar and write "Ocheni"
Expected result: In the drop down menu you find "Ocheni, Bacău (Huruiești)"

Steps 6: Click on the search bar and write "Perchiu"
Expected result: In the drop down menu you find "Perchiu, Bacău (Huruiești)"


Renamed Repos:Commits#get to #list for consistency and added alias

Added support for the branchortag optional parameter
Added support for additional optional parameters according to
official API documention
Replaced pry-debugger with pry-byebug gem

https://confluence.atlassian.com/display/bitbucket/commits+or+commit+resource
I've been having a few fixes and updates in my fork for some weeks. I am sending them over since I saw that this gem got all lively again :smile:
I'll send the next ones shortly.

Thanks @ispyropoulos for all your help! :+1:


change DDD abbreviation for yesterday, today and tomorrow

"Ysd", "Tdy" and "Tmw" look more natural than "Yes", "Tod" or "Tom".

@TalhaAwan  Great idea!! Definitely an improvement 😄


Mimic LevelSystem and ClassSystem hook

Implementation was ported from Kotlin: https://github.com/EndlessCodeGroup/Mimic/tree/d952ac9/mimic-bukkit/src/main/kotlin/impl/skillapi
Closes #168

Awesome work man. Looks great. I'll merge that in and we'll get that implemented in the next published build!


Calling to all our fellow translators

Hi friends,
Before we release v9.0.0 we would like to have all translations finished.
We're calling for help to:

[ ] :fr: @MonsieurMan
[x] :de: @jens1o
[x] :it: @mariotsi @sabinrimni
[ ] :jp: @kimushu
[x] :brazil: @cgarbin
[ ] :ru: @ksvitkovsky
[ ] :cn: @iFun @g-plane
[x] :es: @robertohuertasm
[ ] :tr: @kendinikertenkelebek

Btw, if you happen to be Korean or Taiwanese and want to support this project by providing proper translations for your language, get in touch with us by answering to this thread. We'll be very glad to talk to you! 😉

Italian 👍🏻

It seems that the translation progress has been moved to Crowdin, right?

Yes. you can login with GitHub credentials.

Hi Jimi,
https://crowdin.com/project/vscode-icons-i18n doesn't show any pending
string for Portuguese.
Looks like you approved several suggestions earlier today. Seems like it's
all in sync now.
Christian
On Mon, Jul 22, 2019 at 7:09 AM Jimi (Dimitris) Charalampidis <
<EMAIL_ADDRESS>wrote:

Hi friends,
Before we release v9.0.0 we would like to have all translations finished.
We're calling for help to:

🇫🇷 @MonsieurMan https://github.com/MonsieurMan
🇩🇪 @jens1o https://github.com/jens1o
🇮🇹 @mariotsi https://github.com/mariotsi @sabinrimni
https://github.com/sabinrimni
🇯🇵 @kimushu https://github.com/kimushu
🇧🇷 @cgarbin https://github.com/cgarbin
🇷🇺 @ksvitkovsky https://github.com/ksvitkovsky
🇨🇳 @iFun https://github.com/iFun @g-plane
https://github.com/g-plane
🇪🇸 @robertohuertasm https://github.com/robertohuertasm
🇹🇷 @kendinikertenkelebek https://github.com/kendinikertenkelebek

Btw, if you happen to be Korean or Taiwanese and want to support this
project by providing proper translations for your language, get in touch
with us by answering to this thread. We'll be very glad to talk to you! 😉
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/vscode-icons/vscode-icons/issues/2158?email_source=notifications&email_token=ABVWN2MVAZZU5S4FEMKGEYTQAWIOZA5CNFSM4IFXOVQKYY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4HATM6PQ,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABVWN2PRVXN5PQ7Y7VIDLGDQAWIOZANCNFSM4IFXOVQA
.

Yes. Those translators that have the checkbox checked means that they are OK.

updated

Turkish translations are updated.

Thanks @kendinikertenkelebek!


Notification bell icon does not change position when switching to a section without a sidebar

Description
When switching between sections, notification bell icon should always accept the default position, regardless of whether there is a sidebar in the section or not.
Steps to reproduce

Go to VM section
Click on any VM card/string to open the sidebar
Go to "View logs" section

Actual result
Notification bell icon does not change position
Expected result
The icon is located in the default position (top right corner of the window)
Environment

Browser:
- [ ] Chrome version XX
- [ ] Firefox version XX
- [ ] Opera version XX
- [ ] Chromium version XX
- [ ] Safari version XX
- [ ] IE version XX
- [ ] Edge version XX

Others:

Connected REQ ID
REQ_GEN_003
Screenshots

To test:
REQ_GEN_003

Lack: 1
The additional problem described by Elena is not completely fixed.
The number of unread notifications shifted down [FF, Edge]
Steps:

Perform any action that is displayed in the notification bell.

Actual result: The digit is shifted down (see screenshot)
Expected result: The digit is displayed in the center of its area.
Environment:

Mozilla Firefox ( ver. 61.0.1 [x64] )
Microsoft Edge ( ver. 41.16299.785.0 )

Screenshot:

Tested on 1459


orderbook disappears after some time

Describe the bug
Directly after logging in, an orderbook is visible for pairs that are selected. But after 2-4 minutes, the orders in the orderbook all disappear.
To reproduce
Steps to reproduce the behavior:

Log in
Go to Exchange tab
Select a pair with orders (CHIPS/KMD)
See that orders appear, but disappear after a while ( <5 min )

System info

OS & version: MacOS Catalina

Noticed that when I do a trade, that the orderbook reappears when a swap has finished.

This issue is not related to HyperDEX GUI, but to the underlying mm2.0. Leaving it open for now for when the underlying issue is fixed


irmin-pack: refactor mapping file

This is a follow up to #2025.

Consolidate mapping file code
Use our Ao abstraction
Tidy code in places
Automatically handle mmap endianess. Closes #2027

Codecov Report

Merging #2034 (a526d54) into main (4cf3731) will decrease coverage by 0.03%.
The diff coverage is 84.09%.

@@            Coverage Diff             @@
##             main    #2034      +/-   ##
==========================================
- Coverage   64.56%   64.52%   -0.04%
==========================================
  Files         129      129
  Lines       15576    15569       -7
==========================================
- Hits        10056    10046      -10
- Misses       5520     5523       +3

Impacted Files
Coverage Δ

src/irmin-pack/unix/errors.ml
30.00% <ø> (ø)

src/irmin-pack/unix/gc.ml
9.24% <0.00%> (+0.15%)
:arrow_up:

src/irmin-pack/unix/import.ml
90.00% <ø> (ø)

src/irmin-pack/unix/mapping_file.ml
91.42% <86.27%> (-1.91%)
:arrow_down:

src/irmin-pack/unix/dispatcher.ml
71.08% <88.88%> (-2.19%)
:arrow_down:

src/irmin-pack/layout.ml
86.66% <100.00%> (+5.41%)
:arrow_up:

src/irmin-pack/unix/file_manager.ml
82.72% <100.00%> (-0.89%)
:arrow_down:

src/irmin-pack/unix/utils.ml
92.00% <100.00%> (-1.11%)
:arrow_down:

src/irmin-pack/mem/irmin_pack_mem.ml
53.48% <0.00%> (-2.33%)
:arrow_down:

bench/irmin-pack/trace_replay.ml
41.80% <0.00%> (-1.35%)
:arrow_down:

... and 5 more

:mega: Codecov can now indicate which changes are the most critical in Pull Requests. Learn more


Dev/updates for mvp2 adept api

Updates to work with latest ADEPT TA1 API.

FYSA @billray0259 , planning to merge this soon but please take a look if you like.  Made a few tweaks to the run_chat_baseline.py script to enable running against the latest TA1 ADEPT code.


[full-ci] fix issue-7257

Description

Fix the error when the user trying to overwrite a file with an empty file
Related Issue

Fixes https://github.com/owncloud/ocis/issues/7257

Motivation and Context

How Has This Been Tested?

test environment: local
test case 1:
test case 2:
...

Screenshots (if appropriate):
Types of changes

[X] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Technical debt
[ ] Tests only (no source changes)

Checklist:

[X] Code changes
[ ] Unit tests added
[ ] Acceptance tests added
[ ] Documentation ticket raised:

4193

reva pr already merged https://github.com/cs3org/reva/pull/4193


Update cheatsheet.md

improve on pr #26053
use idiomatic secret name in example

/cc @sftim

/cc @sftim

/assign @onlydole

/assign @onlydole

/lgtm
/approve
Thanks for @sftim's comment which made this a breeze to review! <3


Add more LTS version to CI matrix

another piece of overdue maintenance

this pr is ready, we're just holding off till release plan is set up so we benefit from automation for it

as #872 landed, merging this to test out release-plan cc @void-mAlex


Added converter commands

USAGE
nem2-cli converter <subcommand>

SUBCOMMANDS
namespaceNameToId     - Namespace name -> NamespaceId coder.
numericStringToUInt64 - Numeric string -> UInt64 coder.
payloadToTransaction  - Payload -> Transaction coder.
privateKeyToPublicKey - Private key -> Public key coder.
publicKeyToAddress    - Public key -> Address coder.
stringToKey           - String -> UInt64 coder.

Feel free to propose new commands as new issues :)

In the command names, I think that "coder" should be deleted, or renamed to converter


Validate-Job returns an error when the optional document-format attribute is not included in the request

Reported by Smith via email - when ippserver isn't configured with a default document-format value, the Validate-Job request sent by a CUPS client is rejected based on the lack of a document-format value, which is a bug.

The root cause seems to be that ippserver assumes "document-format-default" = 'application/octet-stream' if it isn't explicitly specified, but won't find it in "document-format-supported" unless the user has explicitly specified that. If "document-format-default" is explicitly specified to be one of the document formats in "document-format-supported", or if "document-format-supported" includes 'application/octet-stream', then the bad behavior isn't observed and the Validate-Job operation is successful.
In other words, this will fail:
ATTR mimeMediaType    document-format-supported    image/jpeg,image/pwg-raster
but adding this will cause it to start working:
ATTR mimeMediaType   document-format-default   image/pwg-raster
or alternately appending 'application/octet-stream' to the list of supported document formats like so:
ATTR mimeMediaType    document-format-supported    image/jpeg,image/pwg-raster,application/octet-stream

[master 952fc03] Don't require/test document-format for Validate-Job operation (Issue #18)


Provide Polymer event that is fired when controller is ready

Polymer provides a lifecycle that can be used to trigger custom methods on start / attach of a component. See  https://www.polymer-project.org/1.0/docs/devguide/registering-elements
It would be good if we could provide the same functionality for an event that is triggered once the controller (proxy) is ready.

https://github.com/canoo/dolphin-platform-polymer/pull/7
https://github.com/canoo/dolphin-platform-polymer/pull/8


DevTest Labs artifact - Windows AD domain join

Added DevTest Labs artifact to join a Windows VM to a specified Active Directory Domain. Requires that the Windows operating system can resolve the domain name and the domain controller via DNS.

Hi @jamesbannan, I'm your friendly neighborhood Azure Pull Request Bot (You can call me AZPRBOT). Thanks for your contribution!

In order for us to evaluate and accept your PR, we ask that you sign a contribution license agreement. It's all electronic and will take just minutes. I promise there's no faxing. https://cla.azure.com.

TTYL, AZPRBOT;

@jamesbannan, Thanks for signing the contribution license agreement so quickly! Actual humans will now validate the agreement and then evaluate the PR.
Thanks, AZPRBOT;


Still cannot get this sample running.

I modified this example to support https and changed action.json to:
  "actions": [{
    "name": "actions.devices",
    "deviceControl": {
    },
    "fulfillment": {
      "conversationName": "ioBroker"
    }
  }],
  "conversations": {
    "ioBroker" :
    {
      "name": "ioBroker",
      "url": "https://iobroker.pro:447/smarthome"
    }
  }
}

The name of my action is "ioBroker", the name of project is "iobrokerhome"

After I start my server I can browse the Devices:

Then I register the Action with:
gactions update --action_package action.json --project iobrokerhome
And no errors.
I go to the Google Home App and try to activate this action:

Yes. I took the pronunciation as "house broker", because I have no lack to use IOBroker/IO-Broker/I.O.Broker.

and get this "nothing saying" error after I login:

This is what I see in the console of my server:
GET /service-worker.js 304 1.947 ms - -
POST: /login  { username: 'rick',
  password: 'oldman',
  redirect: '',
  client_id: 'ghome-iobroker',
  redirect_uri: 'https%3A%2F%2Foauth-redirect.googleusercontent.com%2Fr%2Fiobrokerhome',
  state: 'CrwCQUxWM2ROUzRJa1NJTkdBbHByeEp3S2ZIbzhwTldURHY2UFJiQU1sdfsfsfsNHTTdmdUhYaUVUUTNPLWNVQlhhb0hqVk9hWWg1UVZuay1nbWhTWlZhaFBxUkdXQkI0cElTN3l5Uk92R1ZGZmVJclZ1dnEtRTBSa1YwbDdqa1dsdEo5RHhzbGl0b2lfX2hEcVJkLTZZazl4bUk0cnZYZlJ4ckJCUDZjdmtfM2xFMmUtN21TYkRnMkFSSWM4SVNaNmE4RG9lNUJUbTlHWHk3WHZUQW1BdHRhcVU2RnJNQ3h6bHhFWDhodnl1XzY2V3NmN0lQZ1BES2t6MjFqaFc5bml6a3VrNVMxUTRXUldreUwwRFVFei1ndTFDSjhqVkljc1UtT3dya0hBNHVmZ1BlbFByanJGbRIcYXNzaXN0YW50LWhhbmRvZmY6Ly9jb21wbGV0ZSI7aHR0cHM6Ly9vYXV0aC1yZWRpcmVjdC5nb29nbGV1c2VyY29udGVudC5jb20vci9pb2Jyb2tlcmhvbWUqEWRvZ2Fmb3hAZ21haWwuY29tMhBpb2Jyb2tlcmhvbWVfZGV2' }
getUser rick
logging in  { uid: '1234',
  name: 'rick',
  password: 'oldman',
  tokens: [ 'psokmCxKsdfsfLeYd1' ] }
login successful  rick
authCode successful  9lxxndxenwgfssdf00s04g4c
POST /login 302 6.759 ms - 1440
/token query {}
/token body { grant_type: 'authorization_code',
  code: '9lxxndxenwgfssdf00s04g4c',
  redirect_uri: 'https://oauth-redirect.googleusercontent.com/r/iobrokerhome',
  client_id: 'ghome-iobroker',
  client_secret: 'somePassword' }
getClient ghome-iobroker, somePassword
return getClient { clientId: 'ghome-iobroker', clientSecret: 'somePassword' }
client { clientId: 'ghome-iobroker', clientSecret: 'somePassword' }
handleAuthCode {}
getClient ghome-iobroker, somePassword
return getClient { clientId: 'ghome-iobroker', clientSecret: 'somePassword' }
getAccessToken =  { uid: '1234',
  accessToken: 'psokmCxKjfhk7qHLeYd1',
  refreshToken: 'psokmCxKjfhk7qHLeYd1',
  userId: '1234' }
return getAccessToken =  { token_type: 'bearer',
  access_token: 'psokmCxKjfhk7qHLeYd1',
  refresh_token: 'psokmCxKjfhk7qHLeYd1' }
respond success { token_type: 'bearer',
  access_token: 'psokmCxKjfhk7qHLeYd1',
  refresh_token: 'psokmCxKjfhk7qHLeYd1' }
POST /token 200 5.508 ms - 100
GET /service-worker.js 304 2.572 ms - -
GET /bower_components/polymer/polymer.html 200 3.188 ms - 142409

And no following outputs...
How can I see what the Action is trying to do and if there are any errors on the google side in the log?
Where can I find the Log of action?
Help me. I am facing this problem till Februar 2017 and still no progress.

I'm currently looking into a few developers seeing this error after successfully authenticating.

Can it be because of port 447 and not 443?

Changed everything to 443... Still no lack.
German, English... nothing work

If it can help, I can let the action run and you can test yourself.

You can share the project with me, although I have thus far been unable to reproduce the errors. I have been investigating internally.

@Fleker Not sure if this is related, but on my Local Ubuntu box and the request-sync request is hitting 403 "Forbidden" error.
To avoid 403 I had to enable "HomeGraph API" from google developer console, which I know is not required/captured according to the documentation. After enabling this API now the request-sync is hitting 400 "Bad Request", so not sure what is causing this as of yet.
Any insights for further investigation?

The Request Sync documentation does mention enabling the API.
Have you linked your account to the Assistant? If you haven't done that, the REQUEST_SYNC command will be denied since there's no user to request it for.

@Fleker thanks for the doc. Should have read this instead of just blindly following the instructions on GitHub README.
The account linking from my iOS Google Assistant app keeps failing with "Something Went Wrong". The node server log shows authentication was successful using rick/oldman.

Yeah I'm aware of that issue.

It is very important for me to get this action running.
So you cannot reproduce the error, it is very hard for you to get it fixed.
May be I can help you with online session?  Team viewer, hangout, Skype, slack session with me?

I understand. I'm trying to identify the issue now and potential fixes. Until I have a better idea of where the failure is happening or reproduce it, an online session may not be too helpful.
Can you try this out:
In your action package, add a locale like en-US and redeploy.

{
  "actions": [{
    "name": "actions.devices",
    "deviceControl": {
    },
    "fulfillment": {
      "conversationName": "automation"
    }
  }],
  "conversations": {
    "automation" :
    {
      "name": "automation",
      "url": "https://<NGROK_DOMAIN>.ngrok.io/smarthome"
    }
  },
  "locale": "en-US"
}

@Fleker same issue with account linking (Something went wrong) after adding "locale" : "en-US" & redeploy.
Do you think it could be a timezone issue here with the local server that is simulating the Device Manufacture Cloud?

@GermanBluefox: I hope this helps a little bit: I have it running. It should not be a problem with locale, it works in german. I had also problems or misunderstanding with the ngrok.io tunnel and so took a subdomain and nginx as reverse proxy. I also had to manage let's encrypt certs.

@grabbman
Please explain me a little bit.

I have it running and I had the same error message.

That means: you have google action running with Google Home and it works, although you see the same error message?
And you use this action with letsencrypt certificate on some public host?

@GermanBluefox
I had this message, now it connects ans shows me the devices and i can controll them from google home mini.

@grabbman
Sorry. I still do not understand.
And have you done to eliminate the message? Set locale?

@GermanBluefox  können wir irgendwie anders kommunizieren? Allerdings bin ich grad beim reifenwechsel. Ich habe am Code nix verändert, ausser meine URL angepasst

I still have a problem with locale: "en-US" and with "de-DE"
I tried all combinations. Switched andorid to english and locale to "en-US"/"de-DE". Switched android to German tested again...
Nothing.

@grabbman  You can write me your Whatsapp oder Telegram on<EMAIL_ADDRESS>Or just use email to communication.

It may be helpful to share your project with my email to see whether I can reproduce the error and hopefully understand why some developers are experiencing this issue.

Let's continue discussion in issue #58


Update metric name from input/output tokens to input/output sequence lengths

Change the metric names to align across NVIDIA teams. This PR only includes changing the input and output token name to ISL/OSL:

Input token --> Input sequence length (ISL)
Output token --> Output sequence length (OSL)

The PR changes include:

Update LLM metrics in llm_metrics.py
Update console display
Update README
Update default plot names
Update few other files in the codebase that uses input/output token metric name.

This PR does NOT include changing CLI option names (such as --synthetic-input-token-mean) as that is a major breaking changes to our tool.
Before:

After:

CI ref: 15752543

Is this PR going to update the exporter's too?
I see the tests were updated and they must be passing now but that makes me think the exporter tests are not doing what they are supposed to.

@debermudez Where in the exporter do you think needs to change? Atm I don't see anywhere in the exporter code that requires a change. All the changes in the exporter tests are either expected results or inputs to the exporter.

@debermudez Where in the exporter do you think needs to change? Atm I don't see anywhere in the exporter code that requires a change. All the changes in the exporter tests are either expected results or inputs to the exporter.

Discussed offline. Design was more stable than i realized and @nv-hwoo did a great job updating the rest.


Movinet Colab 'TypeError'

Click to expand!
Issue Type
Build/Install
Have you reproduced the bug with TF nightly?
Yes
Source
source
Tensorflow Version
2.9.2
Custom Code
No
OS Platform and Distribution
No response
Mobile device
No response
Python version
3.9.16
Bazel version
No response
GCC/Compiler version
No response
CUDA/cuDNN version
No response
GPU model and memory
No response
Current Behaviour?
Hello, I'm reporting an issue I'm getting when simply trying to run the extended moving tutorial in google Colab. I'm not entirely sure of the other information, but without changing anything and just trying to run the tutorial, I cannot import from official.projects.movinet.modeling import movinet. The 'TypeError' reads: 'ABCMeta' object not subscriptable and can't find any solution to fixing it.

Standalone code to reproduce the issue
https://colab.research.google.com/github/tensorflow/models/blob/master/official/projects/movinet/movinet_tutorial.ipynb

Relevant log output
No response

@Cdukes30  I was able to import the  'movinet' from 'official.projects.movinet.modeling' using the stable versions of tf-models-official and tensorflow_datasets on colab, please find the gist here and let us know if the issue persists.
Thank you!


[android_intent] Android Code Inspection and Clean up

Description

Handle deprecation & unchecked warning as error

Avoiding uses or overrides a deprecated API in FlutterBackgroundExecutor.java

Related Issues
flutter/flutter#65970
Checklist
Before you create this PR confirm that it meets all requirements listed below by checking the relevant checkboxes ([x]). This will ensure a smooth and quick review process.

[x] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[x] My PR includes unit or integration tests for all changed/updated/fixed behaviors (See Contributor Guide).
[x] All existing and new tests are passing.
[x] I updated/added relevant documentation (doc comments with ///).
[x] The analyzer (flutter analyze) does not report any problems on my PR.
[x] I read and followed the Flutter Style Guide.
[x] The title of the PR starts with the name of the plugin surrounded by square brackets, e.g. [shared_preferences]
[x] I updated pubspec.yaml with an appropriate new version according to the pub versioning philosophy.
[x] I updated CHANGELOG.md to add a description of the change.
[x] I signed the CLA.
[x] I am willing to follow-up on review comments in a timely manner.

Breaking Change
Does your PR require plugin users to manually update their apps to accommodate your change?

[ ] Yes, this is a breaking change (please indicate a breaking change in CHANGELOG.md and increment major revision).
[x] No, this is not a breaking change.

If it passes pre-submit then you're good

@dnfield
merge conflict(s) fixed .
Thank you


Add OpenSearch gateway

Library for communicating with the OpenSearch cluster:
This functionality should support different clusters versions.

@ido-opster I think that the first version of this is done, right? we can close this if so, and open more specific issues as needed in the future.


[MAINT]: build fails during anicca step

Describe the need
When running the build command, the anicca diff fails
SDK Version
No response
API Version
N/A
Relevant log output
No response
Code of Conduct

[X] I agree to follow this project's Code of Conduct

This is blocking updates to the spec currently.
I linted the OpenAPI spec using redocly and it found some issues.
While some of the issues it reported are valid, they are safe to ignore, like ones from the security-defined, operation-4xx-response.
Some others, generated by the spec rule, show many different places in the spec that aren't valid.

The type field must be defined when the nullable field is used.

Those errors may or may not be the cause of anicca failing but would be a good start

Unfortunately anicca is no longer maintained. But it was the only tool I found back in the days that was capable of diffing the OpenAPI versions of GitHub's huge specifications. Maybe there is a new tool out there that could be used instead, it's been a while since I checked.

In the mean time that we find another tool, could we disable it to get updates working again?

you mean disabling generating the diff files? Okay with me, is it the only thing we use anicca for? It's been a long while since I looked into it

Yeah, it's the only thing anicca is used for. We don't process the diff files further down the pipeline currently anyways

okay then, let's disable it for now 👍🏼 thanks for checking

I could always see if @xuorig would be willing to transfer ownership of the repo, but one of the reasons it's public archive is because he made loads of amazing progress on it but went on to new adventures and I simply didn't have the time to put into getting it the rest of the way.  I doubt I'd be able to continue pushing forward on it.
I've asked some of our Microsoft friends who work with large OpenAPI schema sets to see if there are any alternatives out there - we tried close to 10 different tools before deciding to roll our own.  We have used openapi-diff with some success if we think this is an important step to protect our users. I personally don't have a solid opinion on the real benefits on having this step here.

I personally don't have a solid opinion on the real benefits on having this step here.

I think that the diff files should ideally be generated in https://github.com/github/rest-api-description/, and they should be released with proper release notes. That way a much larger consumer base would benefit and the Octokit team wouldn't need to continue maintaining the process.
Reviewing the OpenAPI differences is a time consuming effort, having proper changelogs would save a lot of time, we wouldn't need to create them by hand. Or at least we would have a great baseline to start with that is not a code diff too large too handle for github.com 🤣

I love that line of thinking @gr2m. I'll start the conversation with the owners of that repo.

Hey folks, I'd be open to reviving Anicca if there is interest / still not a better solution.
I tried fixing it today and I'm currently blocked by this: https://github.com/github/rest-api-description/issues/3001

I tried fixing it today and I'm currently blocked by this: github/rest-api-description#3001

Hey @xuorig let me look into the OpenAPI issue.  Sorry for the trouble there.


ThreadLocal storage in the engine

The use of ThreadLocal storage in the cql-engine is causing issues when running CQL in parallel. The default Java task scheduler is such that the thread executing the CQL may not be the same thread the Context was initialized on. For example, you may create a ThreadPool with 8 threads, and 100 different contexts, and those are allocated across all those threads.
Honestly this sounds like a bug in the Java task scheduler to me, the contract for ThreadLocal is that it's, well, ThreadLocal, so not having the access synchronized to the same thread seems like a pretty clear violation of that contract. But that's not something we have control over.

Not a bug in the contract for ThreadLocal. The ThreadLocal contract is related to hardware threads, as opposed to software fibers/coroutines/continuations. The CompletableFutures framework allows scheduling tasks on a main thread, which may then be processed on "background" threads. By default a queue is created for each hardware thread, and the queue is processed sequentially. If another thread finishes first, it can "steal" work from another thread's queue.
https://docs.oracle.com/javase/8/docs/api/java/util/concurrent/ForkJoinPool.html

IOW, the current implementation works fine if the user handles all the creation of Threads themselves. It doesn't work when the Java infrastructure is allowed to do that for you.

Here's a nice explanation of the issue too:
https://www.baeldung.com/java-threadlocal#threadlocalsand-thread-pools

Included in 1.5.7 release


Look into where data- attributes can be removed in favor of conditional react render

As part of the refactor, I'm going through these on a case by case basis. It's not always better to use conditional rendering. Sometimes it's cleaner to use data-.


Exception handling middleware example not behaving as expected

I have copied the exception handling sample from here https://github.com/Azure/azure-functions-dotnet-worker/blob/main/samples/CustomMiddleware/ExceptionHandlingMiddleware.cs however the result I get it not as I would expect.  I am getting the whole HttpResponse object back as json in the body of the response. The actual data I pass in to WriteAsJsonAsync is appearing Base64 encoded in the body property of the response.  Also the response code is always 200, rather than the value I set.
e.g. I am seeing the body of response as follows:
{
  "method": "",
  "query": {},
  "statusCode": "400",
  "headers": {
    "Content-Type": "application/json; charset=utf-8"
  },
  "enableContentNegotiation": false,
  "cookies": [],
  "body": "eyJtZXNzYWdlIjoi...dCBleGlzdC4ifV19fQ=="
}

Passing my desired response object directly into the InvocationResult Value does give me the expected response body and seems much simpler.
However neither method seems to enable me to set the response status code.

Hi @Alan-Hinton
The HttpRequestData.CreateResponse method creates an instance of HttpResponseData with the default status code, which is 200 OK. That is the reason you are seeing the JSON data as the result with 200 OK response status code. If you want to return a different status code, use a the overload which takes the HttpStatusCode value.
Keep in mind that, the WriteAsJsonAsync overload you are using will not use the status code of the HttpResponseData instance you are passing to it, due to this known issue.  We plan on fixing that in the next major release of the worker package. Until then, you need to use the overload which takes the status code.
The below sample will produce a response with 500 status code.
var httpReqData = await context.GetHttpRequestDataAsync();
if (httpReqData != null)
{
    var newHttpResponse = httpReqData.CreateResponse(HttpStatusCode.InternalServerError);
    await newHttpResponse.WriteAsJsonAsync(new { FooStatus = "Failed!" }, newHttpResponse.StatusCode);

    // Update invocation result.
    context.GetInvocationResult().Value = newHttpResponse;
}

We will update the sample to avoid the confusion. Thanks!  Let us know if you still run into issues.

The above method is showing the same behaviour for me i.e. I am getting the whole HttpResponseData object returned as the body of the response and I am still getting a 200 response code.

Can you share a minimal repro in a GitHub repo link?

If I do curl in verbose mode then the problem is clearer
curl -X POST "http://localhost:7071/api/throw-exception" -H  "accept: */*" -d "" -v
Note: Unnecessary use of -X or --request, POST is already inferred.
*   Trying <IP_ADDRESS>:7071...
* Connected to localhost (<IP_ADDRESS>) port 7071 (#0)
> POST /api/throw-exception HTTP/1.1
> Host: localhost:7071
> User-Agent: curl/7.79.1
> accept: */*
> Content-Length: 0
> Content-Type: application/x-www-form-urlencoded
>
* Mark bundle as not supporting multiuse
< HTTP/1.1 200 OK
< Content-Length: 196
< Content-Type: application/json; charset=utf-8
< Date: Tue, 21 Jun 2022 15:41:19 GMT
< Server: Kestrel
<
{"method":"","query":{},"statusCode":"404","headers":{"Content-Type":"application/json; charset=utf-8"},"enableContentNegotiation":false,"cookies":[],"body":"eyJNZXNzYWdlIjoiVGVzdCBtZXNzYWdlIn0="}* Connection #0 to host localhost left intact

You can see it is returning a 200 status and then the full HttpRequestData object as json.  That json does happens to include a value called 'status code' with the value 404, but that is not the status of the result i.e. standard web clients would not see that result.  I expect it to just return the object passed to WriteAsJsonAsync i.e. the exception message "Test Message".

Took another look at the issue. You are not getting the desired behavior(404 status code for http response and exception message as the body of the response) because you are not using the correct return type for your http trigger function. You are using void as the return type for the ThrowException method. If you want to return a valid http response from your function, you should use HttpResponseData as the return type of your function.
The below code should work.
[Function("ThrowException")]
public HttpResponseData ThrowException(
    [HttpTrigger(AuthorizationLevel.Anonymous, "post", Route = "throw-exception")] HttpRequestData req)
    => throw new System.Exception("Test message");

My previous comment was based on testing with the incorrect function code(with void as return type) 🤦
Let us know if you still run into issues. We will consider adding an analyzer to prevent users from using incorrect return types, in the future.

The issue regarding multiple bindings was mentioned in https://github.com/Azure/azure-functions-dotnet-worker/issues/530#issuecomment-1011712725, but not addressed in the PR that was accepted. The proposed workaround has to make assumptions about the field names used in the complex type returned for the function, as PropertyOutputBindingsInfo does not include any type information (only names of properties in the privat field _propertyNames).
So based on the code from the aforementioned comment, one could do something like this hack:
public static class FunctionContextExtensions
{
    public static void SetInvocationResult(this FunctionContext context, HttpResponseData response)
    {
        var keyValuePair = context.Features.SingleOrDefault(f => f.Key.Name == "IFunctionBindingsFeature");
        var functionBindingsFeature = keyValuePair.Value;
        var bindingFeatureType = functionBindingsFeature.GetType();

        var outputBindingsInfo = bindingFeatureType
            .GetProperty("OutputBindingsInfo")!
            .GetValue(functionBindingsFeature);
        var outputPropertyNames = (List<string>?)outputBindingsInfo?
            .GetType()
            .GetField("_propertyNames", BindingFlags.NonPublic | BindingFlags.Instance)?
            .GetValue(outputBindingsInfo);

        // Assume the complex type has a HttpResponseData-field named "HttpResponse"
        if (outputPropertyNames != null && outputPropertyNames.Contains("HttpResponse"))
        {
            var outputBindings = (Dictionary<string, object>)bindingFeatureType
                .GetProperty("OutputBindingData")!
                .GetValue(functionBindingsFeature)!;
            outputBindings.Add("HttpResponse", response);
        }
        // No output bindings defined
        else
        {
            context.GetInvocationResult().Value = response;
        }
    }
}

This assumes that the functions returns a complex type like this:
public class AuthorizationResponse
{
    [CosmosDBOutput(....)] // Or whatever
    public MyDocumentType MyDocument { get; set; }
    public HttpResponseData HttpResponse { get; set; } // <-- must be named "HttpResponse"
}

Any middleware wanting to override the output can then do some like:
var request = await context.GetHttpRequestDataAsync();
var response = request.CreateResponse();
await response.WriteAsJsonAsync( .... );
context.SetInvocationResult(response);

This is broken for the composite function return value. I am trying to craft an authorization middleware that short circuits HTTP requests and invoking this
var response = httpRequestData.CreateResponse(HttpStatusCode.Forbidden);
context.GetInvocationResult().Value = response;

having function returning composite return for multiple bindings results in 200 always, e.g.
        return new ComplexResponse
        {
            HttpResponse = ...
            ServiceBusResponse = ...
        };

This is fixed now and will be available in the next preview version of worker package we will publish (hopefully next week). Once the package is out, I will share an example of how to handle this use case.

For handling composite response type, please refer this sample. You need worker package 1.9.0 or above to get this fix.

Took another look at the issue. You are not getting the desired behavior(404 status code for http response and exception message as the body of the response) because you are not using the correct return type for your http trigger function. You are using void as the return type for the ThrowException method. If you want to return a valid http response from your function, you should use HttpResponseData as the return type of your function.
The below code should work.
[Function("ThrowException")]
public HttpResponseData ThrowException(
    [HttpTrigger(AuthorizationLevel.Anonymous, "post", Route = "throw-exception")] HttpRequestData req)
    => throw new System.Exception("Test message");

My previous comment was based on testing with the incorrect function code(with void as return type) 🤦
Let us know if you still run into issues. We will consider adding an analyzer to prevent users from using incorrect return types, in the future.

I also ran into this issue with the odd behaviour when return type was null. It left me scratching my head for quite a while. I agree, it's very unintuitive!

This issue has be marked as closed, but I believe the original issue still exists.  I have updated my minimal example to all the latest packages and copied the changes from the sample.  But I am still seeing the same behaviour: if an http triggered functions with void  or bare Task return type throws an exception the request results in a 200 response and the whole http response is returned as json.
i.e. this request returns the wrong status code and response
C:\Code>curl "http://localhost:7071/api/throw-exception" -H "accept: */*" -d "" -v
*   Trying <IP_ADDRESS>:7071...
* Connected to localhost (<IP_ADDRESS>) port 7071 (#0)
> POST /api/throw-exception HTTP/1.1
> Host: localhost:7071
> User-Agent: curl/7.83.1
> accept: */*
> Content-Length: 0
> Content-Type: application/x-www-form-urlencoded
>
* Mark bundle as not supporting multiuse
< HTTP/1.1 200 OK
< Content-Length: 208
< Content-Type: application/json; charset=utf-8
< Date: Wed, 19 Oct 2022 19:33:06 GMT
< Server: Kestrel
<
{"method":"","query":{},"statusCode":"500","headers":{"Content-Type":"application/json; charset=utf-8"},"enableContentNegotiation":false,"cookies":[],"body":"eyJGb29TdGF0dXMiOiJJbnZvY2F0aW9uIGZhaWxlZCEifQ=="}* Connection #0 to host localhost left intact

whereas the endpoint that has a non-void return type gives the correct 500 response
C:\Code>curl "http://localhost:7071/api/throw-exception-and-return/true" -H "accept: */*" -d "" -v
*   Trying <IP_ADDRESS>:7071...
* Connected to localhost (<IP_ADDRESS>) port 7071 (#0)
> POST /api/throw-exception-and-return/true HTTP/1.1
> Host: localhost:7071
> User-Agent: curl/7.83.1
> accept: */*
> Content-Length: 0
> Content-Type: application/x-www-form-urlencoded
>
* Mark bundle as not supporting multiuse
< HTTP/1.1 500 Internal Server Error
< Content-Type: application/json; charset=utf-8
< Date: Wed, 19 Oct 2022 19:35:16 GMT
< Server: Kestrel
< Transfer-Encoding: chunked
<
{"FooStatus":"Invocation failed!"}* Connection #0 to host localhost left intact

This very much seems like a bug.  There doesn't seem to be any reason I shouldn't be able to have a request with a void return type.

@kshyju I think @Alan-Hinton is correct. Why isn't it possible to use a void or Task as return type?
I've updated @Alan-Hinton sample project with extra test functions (see below) and all seem to work except void and Task.
So HttpResponseData is mandatory as return type if you don't have your own?
// Bug???
[Function("ThrowExceptionVoid")]
public void ThrowExceptionVoid(
    [HttpTrigger(AuthorizationLevel.Anonymous, "post", Route = "throw-exception-void")] HttpRequestData req)
    => throw new System.Exception("Test message");

// Bug???
[Function("ThrowExceptionTask")]
public Task ThrowExceptionTask(
    [HttpTrigger(AuthorizationLevel.Anonymous, "post", Route = "throw-exception-task")] HttpRequestData req)
    => throw new System.Exception("Test message");

// Correct expected behavoir
[Function("ThrowExceptionAndReturn")]
public MyResponseType ThrowExceptionAndReturn(
    [HttpTrigger(AuthorizationLevel.Anonymous, "post", Route = "throw-exception-and-return/{returnUsefullData}")] HttpRequestData req,
    bool returnUsefullData)
    => returnUsefullData
        ? throw new System.Exception("Test message")
        : new MyResponseType();

// Correct expected behavoir
[Function("ThrowExceptionHttpResponseData")]
public HttpResponseData ThrowExceptionHttpResponseData(
    [HttpTrigger(AuthorizationLevel.Anonymous, "post", Route = "throw-exception-httpresponsedata")] HttpRequestData req)
    => throw new System.Exception("Test message");

// Correct expected behavoir
[Function("ThrowExceptionTaskHttpResponseData")]
public Task<HttpResponseData> ThrowExceptionTaskHttpResponseData(
    [HttpTrigger(AuthorizationLevel.Anonymous, "post", Route = "throw-exception-task-httpresponsedata")] HttpRequestData req)
    => throw new System.Exception("Test message");

@LockTar Can you open a new issue so we can discuss the current design and future plans there?

See https://github.com/Azure/azure-functions-dotnet-worker/issues/1619#issuecomment-2223974185


Latest bc-fips <IP_ADDRESS> along with java 11 leads to StackOverflowError when attempted to initialize the BCFIPS provider

During a current upgrade of the bouncy castle fips libs to latest version (bc-fips 1.0.2 -> <IP_ADDRESS>) we have experienced the following issue. Failure to initialize the BCFIPS provider due to StackOverflowError.
Exception in thread "main" java.lang.StackOverflowError
at java.base/java.util.Dictionary.(Dictionary.java:55)
at java.base/java.util.Hashtable.(Hashtable.java:239)
at java.base/java.util.Properties.(Properties.java:206)
at java.base/java.util.Properties.(Properties.java:174)
at java.base/java.security.Provider.(Provider.java:262)
at java.base/sun.security.ssl.SunJSSE.(SunJSSE.java:138)
at java.base/sun.security.ssl.SunJSSE.(SunJSSE.java:126)
at java.base/com.sun.net.ssl.internal.ssl.Provider.(Provider.java:52)
at java.base/sun.security.jca.ProviderConfig.getProvider(ProviderConfig.java:183)
at java.base/sun.security.jca.ProviderList.getProvider(ProviderList.java:266)
at java.base/sun.security.jca.ProviderList.getIndex(ProviderList.java:296)
at java.base/sun.security.jca.ProviderList.getProviderConfig(ProviderList.java:280)
at java.base/sun.security.jca.ProviderList.getProvider(ProviderList.java:286)
I have been able to isolate and reproduce the issue with a simple java app. It seems to be also dependent on the specific java version to be used.
Following are more details on the steps to reproduce and the observations:
I. Reproduction of StackOverflowError
Prerequisites:
1/ Have the following java version as runtime
openjdk version "11.0.11" 2021-04-20 LTS
OpenJDK Runtime Environment Zulu11.48+21-CA (build 11.0.11+9-LTS)
OpenJDK 64-Bit Server VM Zulu11.48+21-CA (build 11.0.11+9-LTS, mixed mode)
2/ Have the following provider list in an override of the java.security file passed to the java app
security.provider.1=org.bouncycastle.jcajce.provider.BouncyCastleFipsProvider C:DEFRND[HMACSHA512(256)];HYBRID;ENABLE{ALL};
security.provider.2=org.bouncycastle.jsse.provider.BouncyCastleJsseProvider fips:BCFIPS
security.provider.3=com.sun.net.ssl.internal.ssl.Provider BCFIPS
security.provider.4=sun.security.provider.Sun
security.provider.5=org.jcp.xml.dsig.internal.dom.XMLDSigRI
3/ Use bc-fips <IP_ADDRESS> version. ( Also it would need to have a bctls-fips jar for the BouncyCastleJsseProvider .We used bctls-fips-<IP_ADDRESS> version )
4/ Have a java program which calls Security.getProviders() as a first call in its main method.
5/ Run the java app in fips strict mode
This will produce the above exception.
The behavior seems to be dependent also on the version of java used. We have done further testing with a prior java version:
openjdk version "11.0.2" 2019-01-15
OpenJDK Runtime Environment 18.9 (build 11.0.2+9)
OpenJDK 64-Bit Server VM 18.9 (build 11.0.2+9, mixed mode)
With the above version of java the BCFIPS provider loaded successfully but the BouncyCastleJsseProvider has not been initialized and was missing.
We have also tested the above scenarios with the previous version of the bc-fips ( 1.0.2 ) and it had no problems.
Debugging the app it seemed to be related to a change into the ECPoint class and the addition of getTestRandom().
I have attached also the repro app source code and the related java.security override settings and scripts to start the app.
bc-fips repro.zip

This is fixed in bc-fips-<IP_ADDRESS> - available in early access should be in GA in next month.

Looking forward to the fix here and thanks so much for your work!
Any idea if the GA release for <IP_ADDRESS> is on track to release soon?

It's still with NIST, which is unexpected, but it seems things are going very slowly at the moment.

Ok, thanks for the update!

For reasons which I won't go into we ended up moving to <IP_ADDRESS> - this is now available in Maven Central and at https://www.bouncycastle.org/fips-java

I updated to bc-fips <IP_ADDRESS> and am still facing this exact issue.

The workaround didn't work for me. So just like @isaacjensen , I am using bc-fips-<IP_ADDRESS> but having the same StackOverFlowError when running the keytool command to convert the keystore type from JKS to BCFKS.
openjdk: 11.0.17
command: keytool -importkeystore -srckeystore /etc/ssl/certs/java/cacerts.orig -srcstoretype JKS -srcstorepass changeit -destkeystore /etc/ssl/certs/java/cacerts -deststorepass changeit -deststoretype BCFKS -providerClass org.bouncycastle.jcajce.provider.BouncyCastleFipsProvider --providerpath /usr/lib/jvm/java-11-openjdk-amd64/jar/bc-fips-<IP_ADDRESS>.jar
To me, it looks like a version issue. My colleague used openjdk-8 and he doesn't not have the issue when running the same command. @dghgit @peterdettman
We have a tight timeline for a Fedramp certification and this is critical for our java base image. Is it possible to revisit this ticket?

it's probably not the same issue. Do you have anything meaningful by way of a stack trace?

@dghgit I actually forgot to mention my java.security settings:
security.provider.1=org.bouncycastle.jcajce.provider.BouncyCastleFipsProvider
security.provider.2=org.bouncycastle.jsse.provider.BouncyCastleJsseProvider fips:BCFIPS
security.provider.3=SUN
security.provider.4=SunRsaSign
security.provider.5=SunEC
security.provider.6=SunJSSE BCFIPS
security.provider.7=SunJCE
security.provider.8=SunJGSS
security.provider.9=SunSASL
security.provider.10=XMLDSig
security.provider.11=SunPCSC
security.provider.12=JdkLDAP
security.provider.13=JdkSASL
security.provider.14=Apple
security.provider.15=SunPKCS11

and
keystore.type=BCFKS

The StackOverFlowError happens when I append "BCFIPS" for the SunJSSE provider. If I removed it, error is gone, but I do need it appended for ssl to use FIPS provider.
The stack trace is exactly same as the author has.

Okay, easy fix, you should be able safely delete the SunJSSE. The experimental FIPS mode became a no-op in Java 9, they no longer try to keep it SP 800-52 compliant so in this case you cannot use it in any case.

@dghgit thanks! I assume you meant that I remove the entire line of provider.6 right? The keytool command did go through after I did that, but then I get the following error when using maven to download the dependencies. It might be related to the removal but I'm not sure. I am pretty new to crypto/fips, so would appreciate some insight here. thanks.
[ERROR]     Unresolveable build extension: Plugin kr.motd.maven:os-maven-plugin:1.6.2 or one of its dependencies could not be resolved: Failed to read artifact descriptor for kr.motd.maven:os-maven-plugin:jar:1.6.2: Could not transfer artifact kr.motd.maven:os-maven-plugin:pom:1.6.2 from/to central (https://repo.maven.apache.org/maven2): Transfer failed for https://repo.maven.apache.org/maven2/kr/motd/maven/os-maven-plugin/1.6.2/os-maven-plugin-1.6.2.pom: java.security.NoSuchAlgorithmException: Default SSLContext not available -> [Help 2]
[ERROR]     Non-resolvable import POM: Could not transfer artifact com.google.cloud:libraries-bom:pom:26.0.0 from/to central-repo (https://repo.maven.apache.org/maven2): Transfer failed for https://repo.maven.apache.org/maven2/com/google/cloud/libraries-bom/26.0.0/libraries-bom-26.0.0.pom @ line 12, column 16: java.security.NoSuchAlgorithmException: Default SSLContext not available -> [Help 3]
[ERROR]     'dependencies.dependency.version' for com.google.cloud:google-cloud-spanner-jdbc:jar is missing. @ line 110, column 15
[ERROR]     'dependencies.dependency.version' for com.google.cloud:google-cloud-pubsub:jar is missing. @ line 114, column 15

(btw, I replaced bcprov with bc-fips in google-cloud-spanner-jdbc and google-cloud-pubsub for FIPS compliance, hopefully that was the right thing to do)
Some more stack traces:
Caused by: java.security.NoSuchAlgorithmException: Default SSLContext not available
    at sun.security.jca.GetInstance.getInstance (GetInstance.java:159)
    at javax.net.ssl.SSLContext.getInstance (SSLContext.java:168)
    at javax.net.ssl.SSLContext.getDefault (SSLContext.java:99)
    at javax.net.ssl.SSLSocketFactory.getDefault (SSLSocketFactory.java:123)
    at javax.net.ssl.HttpsURLConnection.getDefaultSSLSocketFactory (HttpsURLConnection.java:335)
    at org.apache.maven.wagon.providers.http.wagon.shared.AbstractHttpClientWagon.createConnManager (AbstractHttpClientWagon.java:369)
    at org.apache.maven.wagon.providers.http.wagon.shared.AbstractHttpClientWagon.<clinit> (AbstractHttpClientWagon.java:295)
    at org.apache.maven.wagon.providers.http.HttpWagon$__sisu1$$FastClassByGuice$$fd3b369a.newInstance (<generated>)

@dghgit  to add, I only started to get all these issues after I tried to convert the keystore type to BCFKS.
Previous, in java.security, I kept the default keystore.type=pkcs12 and kept "security.provider.6=SunJSSE", everything was working fine. But I guess I have to do the conversion for FIPS compliance.

check that the classpath doesn't have both BC FIPS and non-FIPS jars on it, and that the JVM concerned is properly configured to support the BCJSSE. The BCJSSE definitely provides a default context.

@dghgit Thank you!
The errors were from "mvn clean package" command.
I was reminded by your suggestion to check if "JVM concerned is properly configured to support the BCJSSE", so I set system property "-Djava.security.debug=jca" to see some debug messages, and it turned out neither BCFIPS and BCJSSE were not loaded!
ProviderConfig: Error loading legacy provider org.bouncycastle.jsse.provider.BouncyCastleJsseProvider
java.lang.ClassNotFoundException: org.bouncycastle.jsse.provider.BouncyCastleJsseProvider
	at java.base/jdk.internal.loader.BuiltinClassLoader.loadClass(BuiltinClassLoader.java:581)
	at java.base/jdk.internal.loader.ClassLoaders$AppClassLoader.loadClass(ClassLoaders.java:178)
	at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:522)
	at java.base/sun.security.jca.ProviderConfig$ProviderLoader.legacyLoad(ProviderConfig.java:385)
	at java.base/sun.security.jca.ProviderConfig$ProviderLoader.load(ProviderConfig.java:362)
	at java.base/sun.security.jca.ProviderConfig$3.run(ProviderConfig.java:248)
	at java.base/sun.security.jca.ProviderConfig$3.run(ProviderConfig.java:242)

My understanding is that Maven needs to know where the two jars are located in order to search for these two classes. I am trying to figure out how to make Maven do that. Kindly let me know if you have different thoughts. Thanks!


Fix #711 issue with multiple superscripts.

The previous code incorrectly implemented TeXbook rules. First off,
the font metrics at issue should be those for the superscript/
subscript style, not the main style. Secondly, the metrics should be
scaled by the font size.
This changes some screenshotter tests (and they look more like TeX
now).

Thanks for the PR.  Big improvement in the vertical position of subscripts.
Before:

After:

Before:

After:

Before:

After:

Before:

After:

Before:

After:


GitHub Issue #166: capture_error_stacktraces is not used

Implementation of capture_error_stacktraces in 1.2.0.
This PR is based on PR https://github.com/rollbar/rollbar-php/pull/178 to pull in changes to generateErrorWrapper

Ready for review.

LGTM, a couple minor questions but this looks basically good to go.

@ezarowny suggested to check out how Sentry deals with local variables in stack frames. I think it's worth a shot so I'll do some research


connected refused when running soft-serve as a container

Description
I try to use docker to run soft-serve. The container create successfully, and I am sure  environment variables are set correctly.
Then I try to connect to the TUI via ssh, something very bad happened.
What I expect to see
TUI views.
What actually happened
Connection refused.

My config
OS
Ubuntu 20.04 LTS.
OS environment variables

docker-compose.yml
---
version: "3.1"
services:
  soft-serve:
    image: charmcli/soft-serve:latest
    container_name: soft-serve
    volumes:
      - ~/soft-serve/data:/soft-serve
    ports:
      - 27017:23231
    restart: unless-stopped
    environment:
      - SOFT_SERVE_INITIAL_ADMIN_KEY=<My public key>

Others
btw, Charm is so cooooooool!

set all the five env variables,  it works.

Thank you for the feedback!


Re-work dropdown selectors to typeahead inputs

The current dropdown selectors aren't very functional at the moment. I'd love to switch these out for an input element with typeahead completion.
Requirements:

[ ] Make the dropdowns into text fields
[ ] Add a label above
[ ] Make sure there's an arrow that indicates there are options that show up once you click it
[ ] Use the same styling if possible
[ ] Filter the options as you type in the input field

Here's an example of a variation of this: https://codepen.io/hmps/pen/FzIsu -
Up for grabs if anyone wants to try sorting this one out.

Hey! I'm interested in working on this. To make it clear the dropdown selectors you're referring to are the tag selectors?

Awesome! Throughout the site on some pages you'll see these filter buttons at the top of the page. If you hover on these you'll see lists of tags, etc. These should be switched out to the new style

For reference, these are the ones I'm talking about. There are more of them on other pages as well, all of them need switching out of course.

Got it, thanks! I'll try to do it within the next few days

Yeah, the "design" solution I made that times is not ideal (nor beautiful) 😅

By the way, should I use plain css or tailwind?
Related: #88

I think that's still up for discussion, most likely we're going to go with plain old CSS.

Oh okay, I see, thanks!
One more thing, I found this library, svelte-select, that seems to have the desired outcome?
Here's an example they have: https://svelte.dev/repl/3e032a58c3974d07b7818c0f817a06a3?version=3.20.1
I think the Multi example is applicable to our situation?

Yes! This looks perfect! If we just wrap it in our own component that implements a label feature I think we're good to go. We also have to make sure the functionality still works, of course.

Great! Thanks for the quick reply :)

Does the sorting component not work for you also when ran in dev mode? But, when built and in preview, it works.
Here's a pic of the broken dev sort:

I want to know if this is only for me. I think this bug also affects svelte-select since it doesn't work in dev mode, but magically works when built.
One more thing, I tested svelte-select in another sveltekit project and it seemed to work there. Very weird never encountered this.

@paolotiu  I have the sum bug in dev mode.

Yeah really weird, I'll try to investigate a bit more.

Found the problem!!!!
it's at src/lib/stores/metatags.ts.
Originally it imports the type with the function like this.
import { Writable, writable } from 'svelte/store

Apparently, vite doesn't like that and proceeds to break stuff. This only happens in dev because when built all type imports are removed.
Here's the fix:
import type { Writable } from 'svelte/store';
import { writable } from 'svelte/store';

Thanks @paolotiu 🧡

Thanks @kevmodrome! Looking forward to more contributions.
Also, loving the podcast!


Inherit explicit null as override when decoding json/yaml

json.decode doesn't respect nulls properly.
The following example does work as expected:

schema Temp:
    x: int
    y?: int = x

correct: Temp = {x = 1} | {y = None}
incorrect: Temp = {x = 1} | json.decode('{"y": null}')

result:
correct:
  x: 1
  y: null

incorrect:
  x: 1
  y: 1

We can actually further simplify the request here, which should include this scenario:
m: Temp = json.decode('{"x": 1, "y": null}')
Coming from raw JSON there is no way to explicitly disable optional (but defaulted) values in a schema.

having some option like json.decode('{}', convert_null_to_none=True) would be nice

This actually yields some odd behavior:
schema MyObj:
    x: int
    y?: int = 9

temp: MyObj = json.decode('{"x": 1, "y": null}')

schema Child:
    parent: MyObj = {y = 2}

output = Child{
    parent: temp
}

The above does not yield the same results as:
schema MyObj:
    x: int
    y?: int = 9

schema Child:
    parent: MyObj = {y = 2}

output = Child{
    parent:  json.decode('{"x": 1, "y": null}')
}

Gotcha that makes sense thanks for the clarification! And as always thanks for the prompt responses :). In regards to this question Is there anyway to cast it to the type I want? Or a way I can do this with a plugin? Or is this something that might be supported in the future?
If willing I’m happy to open a PR related to this if there’s a clear path forward. Maybe passing an optional type to the decode functions?

Hmm, so you're saying now that it returns a type, but before you mentioned it returns a dict? In either case there seems to be no current solution to what I'm looking to do?
Specifically I want to consume yaml where a user can set a value to null, even if the value in the schema has a default. I think the below example shows the problem more clearly:
import json

schema SomeSchema:
    foo?: str = "default"

obj1 = json.decode('{"foo": null}')
obj2 = {foo = None}

inst1: SomeSchema = json.decode('{"foo": null}')
inst2: SomeSchema = {
    foo = None
}

val = obj1 == obj2

yields:
obj1:
  foo: null
obj2:
  foo: null
inst1:
  foo: default
inst2:
  foo: null
val: true

This shows 2 objects that are equal but have different behavior. This seems like a bug to me, or at the very least a feature deficit. A simple solution could be adding an optional param to decode to enforce explicit nulls.


Overflowing in debug build

Is this intend to use release mode turning off overflow checking?

I have never tested debug builds before. I completely forgot that debug mode has panic on overflow whereas release mode does not
Could you share the steps to reproduce the overflow? Then, I can check if the overflow is intentional (in which case it should use the overflowing arithmetic methods) or unintentional (which may cause buggy behavior in release mode).

Just any current level recipe? They panic in either quality_upper_bound_solver or https://github.com/KonaeAkira/raphael-rs/tree/main/solvers/src/step_lower_bound_solver

Fixed with be9c18dfbac222f973bbbce53224d670805baa2a.
Thanks for the report! :)


Can you explain why dimension of model output is 225, and dimension of SMPL  skeleton is 24*3 ?

I want to convert pkl of output to character animation, but the dimension is not matched, how can i do that?

I want to convert pkl of output to character animation, but the dimension is not matched, how can i do that?

225 = 6pad + 3trans + 216pose
216pose=24x9=24x3x3
24x3---->24x9

I want to convert pkl of output to character animation, but the dimension is not matched, how can i do that?

225 = 6pad + 3trans + 216pose
216pose=24x9=24x3x3
24x3---->24x9

thank you very much ,but how can I do inverse processing: 24x9---->24x3
then ,I can finish next generating animation.

why 24*9

why 24*9

scipy.spatial.transform.Rotation.from_rotvec:     24x3------>24x9

225 = 6pad + 3trans + 216pose

@CuberFan pad as in padding? If so, why do you need padding here?

why 24*9

the size of rotation matrix is 3*3


Add option to batch events

This is a good v1 - what about implementing the "eventUploadPeriodMillis" flag?

@curtisliu added eventUploadPeriodMillis, PTAL

nice, LGTM


Use terminal link providers to links in tracebacks

https://code.visualstudio.com/updates/v1_49#_terminal-link-providers
Not only for jumping to specific positions from a traceback, but potentially to stdlib docs as appropriate (including to the right version based on the selected environment).
E.g.
Traceback (most recent call last):
  File "/home/brettcannon/scratch/Some Python test space/whatever.py", line 4, in <module>
    spam()
  File "/home/brettcannon/scratch/Some Python test space/whatever.py", line 2, in spam
    import blah
ModuleNotFoundError: No module named 'blah'

could link to:

Source lines
spam to the def line
ModuleNotFoundError to the exception's docs

Traceback (most recent call last):
  File "/home/brettcannon/scratch/Some Python test space/whatever.py", line 3, in <module>
    os.path.exists({})
  File "/usr/lib/python3.8/genericpath.py", line 19, in exists
    os.stat(path)
TypeError: stat: path should be string, bytes, os.PathLike or integer, not dict

chould probably link to:

The file lines (only the second one to /usr/lib/python3.8/genericpath.py does)
exists to the docs for os.path.exists() (and this is probably one of the most complicated examples based on how it's exposed via genericpath through os.path)
The docs for os.path.exists()?
The docs for os.stat()?
TypeError could link to the exception's docs

Problems to solve to open up as much linking as possible would include:

Parsing a file to find out where e.g. spam is defined to link to it (but which could be a step towards partial IntelliSense)
Resolving function names back to their docs (only useful when they are extension modules as otherwise the traceback should end up traversing into the source enough to get us what we are after)
Mapping stdlib source back to their documentation (which would probably involve generating a static mapping of file paths and names to their docs; sphinx's index files which are publicly accessible for cross-referencing would help here)
Bonus points for making this all work offline if someone has Python's docs cached locally

Closing as dup of https://github.com/microsoft/vscode-python/issues/20088.


Chriche/optional

Use a utility Optional type for class member variables that are not required and have no default value specified

Use a utility Optional type for class member variables that are not required and have no default value specified

Could mention the schema members that you've updated to use Optional.


Preprocessing code for Chinese

Do you have any suggestions for Chinese data preprocessing?
For example, text normalization, g2p, etc.
From your experience, will the accuracy of the g2p model have great impact on the model performance ?

These are what I'm gonna try:

using text normalization to preprocess all the text
using jieba to replace TransfoXLTokenizer
using pypinyin + ipa to replace phonemize
train BPE tokenizer. I'm also wondering maybe using initials and finals as sup-phoneme.

Any other suggestions? Thanks!

When I trained the multilingual PL-BERT (English, Japanese, Chinese), I tried two preprocessing methods for Chinese and didn't notice any difference in terms of quality for the downstream TTS tasks (possibly also because the AiShell dataset is simple and just like VCTK where no clear context or emotions are there).
The simplest way is character-level P2G, i.e., you treat each character as a grapheme. You should also take into account the change of pronunciations (heterophones) given different contexts (for example, "了" can be read both as "liao" and "le" depending on the context).
Another more complicated way is to represent graphemes at the word level. For example, you treat "了" (particle) as a grapheme, but you treat "了解" as another grapheme (instead of two graphemes, "了" and "解"). This probably helps for Japanese too, as a lot of graphemes can be shared between Chinese and Japanese.
For me, I used tokenizer = BertTokenizer.from_pretrained("uer/gpt2-chinese-cluecorpussmall") tokenizer and used pypinyin with the conversion table here to convert characters into IPA. Luckily Chinese pronunciations are easier than Japanese as the pronunciations don't change depending on the context but only on the word. Once you know the word, the pronunciations are always the same unlike in Japanese. So once you get the tokenized words, you can convert them individually to pinyin and then to IPA.
I don't think there's any need to train a BPE tokenizer. Not sure what it is for.
I will leave this issue open in case someone else needs to train a PL-BERT in Chinese.

I've tried tokenizer = BertTokenizer.from_pretrained("uer/gpt2-chinese-cluecorpussmall") and got some wrong output:
tokenizer.tokenize('这是一句中文文本，时间是2023年7月12日。')
output: ['这', '是', '一', '句', '中', '文', '文', '本', '，', '时', '间', '是', '202', '##3', '年', '7', '月', '12', '日', '。']
digits like '2023' '7' '12' should be read out, and '2023' may should not to be treated seperately, so maybe I've need to use a Text Normalization module first.
Also, you've mentioned to treat "了解" as another grapheme, this requires a chinese tokenizer. May I know which tokenizer did you use?
I'm quite surprise that there is no difference in terms of quality for the downstream TTS tasks, cause when we input wrong graphme it hurts naturalness a lot. May I know how do you evaluate the output chinese speech? Does the result outperform the baseline that is not pretrained on large-scale corpus?
Thanks!

@TinaChen95 You can use tokenizers here https://fengshenbang-doc.readthedocs.io/zh/latest/index.html that has word-level tokenization instead of character-level. It is true that you will need to normalize the date and numbers to their reading. As for the performance in the Mandarin dataset, I only tested it on AiShell dataset which is similar to VCTK that does not have any emotion or context, so the difference is probably not that big. I could not find any Chinese audiobook or emotional speech dataset with contexts like LJSpeech or LibriTTS, so if you know any that I can test on please let me know. Also since the PL-BERT is eventually fine-tuned with the TTS model, as long as the phonemes are correct in the TTS dataset, the incorrect phonemization during pre-training indeed has little effect. This is only confirmed for English datasets however, but I believe similar things should hold true for Chinese.


added SQL query for Transaction Fee stats

Added stats for getting transaction fees

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


Issues getting running

Hi Team,
I am having issues getting the example running.  I was able to successfully get everything running until 5.  I am able to get gulp running.  But here is the following error output.
dsalins:web-visualizations dsalins$ gulp
[11:21:19] Using gulpfile ~/Documents/SVNRepositories/Stanford_Wearables/web-visualizations/gulpfile.js
[11:21:19] Starting 'clean'...
[11:21:19] Finished 'clean' after 21 ms
[11:21:19] Starting 'default'...
[11:21:19] Starting 'generate-component-styles'...
[11:21:19] Starting 'generate-concatenated-styles'...
[11:21:19] Starting 'generate-component-scripts'...
[11:21:19] Starting 'generate-concatenated-script'...
[11:21:19] Finished 'default' after 57 ms
src/charts.js: line 460, col 9, 'xScale' was used before it was defined.
src/charts.js: line 461, col 9, 'yScale' was used before it was defined.
src/charts.js: line 462, col 9, 'yScaleCallback' was used before it was defined.
src/charts.js: line 468, col 9, 'xAxis' was used before it was defined.
src/charts.js: line 472, col 9, 'yAxis' was used before it was defined.
src/charts.js: line 474, col 9, 'yLabel' was used before it was defined.
src/charts.js: line 480, col 9, 'drag' was used before it was defined.
src/charts.js: line 488, col 9, 'wheelCallback' was used before it was defined.
src/charts.js: line 495, col 9, 'plots' was used before it was defined.
src/charts.js: line 515, col 9, 'pointPlot' was used before it was defined.
src/charts.js: line 531, col 9, 'secondaryYAxes' was used before it was defined.
src/charts.js: line 672, col 9, 'colorScale' was used before it was defined.
src/charts.js: line 673, col 9, 'legend' was used before it was defined.
src/charts.js: line 712, col 11, 'hidePanZoomHint' was used before it was defined.
src/charts.js: line 750, col 9, 'pzi' was used before it was defined.
src/charts.js: line 751, col 9, 'pziXAxis' was used before it was defined.
src/charts.js: line 850, col 9, 'clearZoomLevelButtonActiveStates' was used before it was defined.
src/charts.js: line 854, col 9, 'toolbar' was used before it was defined.
src/charts.js: line 963, col 11, 'showHoverPointTooltip' was used before it was defined.
src/charts.js: line 996, col 11, 'pointer' was used before it was defined.
src/charts.js: line 1004, col 11, 'pointerMove' was used before it was defined.
src/charts.js: line 1046, col 11, 'tip' was used before it was defined.
22 errors
src/charts.js: line 460, col 9, 'xScale' was used before it was defined.
src/charts.js: line 461, col 9, 'yScale' was used before it was defined.
src/charts.js: line 462, col 9, 'yScaleCallback' was used before it was defined.
src/charts.js: line 468, col 9, 'xAxis' was used before it was defined.
src/charts.js: line 472, col 9, 'yAxis' was used before it was defined.
src/charts.js: line 474, col 9, 'yLabel' was used before it was defined.
src/charts.js: line 480, col 9, 'drag' was used before it was defined.
src/charts.js: line 488, col 9, 'wheelCallback' was used before it was defined.
src/charts.js: line 495, col 9, 'plots' was used before it was defined.
src/charts.js: line 515, col 9, 'pointPlot' was used before it was defined.
src/charts.js: line 531, col 9, 'secondaryYAxes' was used before it was defined.
src/charts.js: line 672, col 9, 'colorScale' was used before it was defined.
src/charts.js: line 673, col 9, 'legend' was used before it was defined.
src/charts.js: line 712, col 11, 'hidePanZoomHint' was used before it was defined.
src/charts.js: line 750, col 9, 'pzi' was used before it was defined.
src/charts.js: line 751, col 9, 'pziXAxis' was used before it was defined.
src/charts.js: line 850, col 9, 'clearZoomLevelButtonActiveStates' was used before it was defined.
src/charts.js: line 854, col 9, 'toolbar' was used before it was defined.
src/charts.js: line 963, col 11, 'showHoverPointTooltip' was used before it was defined.
src/charts.js: line 996, col 11, 'pointer' was used before it was defined.
src/charts.js: line 1004, col 11, 'pointerMove' was used before it was defined.
src/charts.js: line 1046, col 11, 'tip' was used before it was defined.
22 errors
[11:21:21] gulp-notify: [Gulp notification] Scripts copy task complete
[11:21:21] Finished 'generate-component-scripts' after 1.36 s
[11:21:21] gulp-notify: [Gulp notification] Scripts concat task complete
[11:21:21] Finished 'generate-concatenated-script' after 1.36 s
[11:21:21] gulp-notify: [Gulp notification] Concatenated styles task complete
[11:21:21] Finished 'generate-concatenated-styles' after 1.39 s
[11:21:21] gulp-notify: [Gulp notification] Component styles task complete
[11:21:21] Finished 'generate-component-styles' after 1.43 s
dsalins:web-visualizations dsalins$
Then I open the example/charts.html and the data does not load.
Please advise.

Hi Denis,
Glad to see that you are trying out the library. What version of the source did you download? was it the master branch? Development? A release?
Thank you,
Jasper

If you are just running the chart example from your file system, you will get a CORS error when it tries to load the json. You can fix this by running gulp watch and visiting http://localhost:8080/examples/charts.html
Does that help?
Thanks,
Jasper

Awesome.  Thank you for that help.
If I could advise, to add that part in the readme tutorial also.  That
resolved my issue.
thanks.
-Denis
On Wed, Feb 17, 2016 at 12:39 PM, Jasper Speicher<EMAIL_ADDRESS>wrote:

If you are just running the chart example from your file system, you will
get a CORS error when it tries to load the json. You can fix this by
running gulp watch and visiting http://localhost:8080/examples/charts.html
Does that help?
Thanks,
Jasper
—
Reply to this email directly or view it on GitHub
https://github.com/openmhealth/web-visualizations/issues/10#issuecomment-185393566
.

--
Denis N. Salins
Cell:<PHONE_NUMBER>
<EMAIL_ADDRESS>http://about.me/Denis.Salins


Remove option on paymaster interface

This PR is based on #42

My interpretation of this pull request:

This PR removes the unused PaymasterRequestOption type.