Light2D Android GLES2 wrong shadow

Bugsquad edit: Reopened from https://github.com/godotengine/godot/issues/2482.
Godot version
3.3.2
System information
Xiaomi Redmi Note 7, Android 10, GLES2
Issue description
Videos should explain the problem.
Its only on Android when using GLES2. On Win10 GLES2 is working fine.
Android GLES2:
https://user-images.githubusercontent.com/42713365/123272703-4b9a8200-d502-11eb-8663-69cd4ad13e5d.mp4
Android GLES3:
https://user-images.githubusercontent.com/42713365/123273329-da0f0380-d502-11eb-8720-9e3655f2ce1b.mp4
Steps to reproduce
See example project or create a new project (GLES2) where the light is not that close to the occluder.
Minimal reproduction project
Light2D_Shadow_Bug.zip

Can you please update your post with hardware specifications?
The issue looks like a precision issues in the 2D Shadow buffer. This could be a result of your device not supporting floating point textures. When floating point textures aren't supported Godot defaults to using an 8-bit per channel rgba buffer and encodes the floating point value in the four channels. If that is the case, then we know to look in the float->RGBA conversion code for a possible bug.

Also try setting the project setting "rendering/gles2/compatibility/enable_high_float.Android" to true if it isn't set already
This already solves the problem for me.
So does this mean that enable_high_float.Android is enabled for all GLES3 devices but not automatically for GLES2 because of compatibility?

This already solves the problem for me.

Great! I guess this is a documentation issue rather than a bug

So does this mean that enable_high_float.Android is enabled for all GLES3 devices but not automatically for GLES2 because of compatibility?

Kind of. Devices that support OpenGL ES 3.0 have to support  high precision floats in shaders. Devices that only support OpenGL ES 2.0 don't have to support high precision, but they can, it just has to be enabled with a special flag. Enabling high precision floats has a performance impact, so it isn't requested by default.


Language NASM page should including information on input/output format

https://github.com/Codewars/codewars.com/wiki/Language-NASM
I'm looking at this and there are no information how are inputs/outputs handled. Which registers contain the input arguments? What is their layout? edi, esi, then...? What if there are more than 4 arguments? Are they stored on the stack? How big is the stack? Similarly, where should the output be stored?
There is an example but it's not illustrative, and it is not sufficient as definition.

I just fixed the example to use 64 bit registers. For more information, see https://en.wikipedia.org/wiki/X86_calling_conventions#System_V_AMD64_ABI and https://wiki.osdev.org/System_V_ABI#x86-64 .

I found a nice tutorial series https://github.com/0xAX/asm . It uses NASM on Linux so it should be very similar. The first one is https://0xax.github.io/asm_1/
I don't think there's anything specific to the runner, but let me know if you need more information.

I think the ABI doesn't guarantee that higher bits of 32-bit operands in 64-bit registers are zeros, although C compilers usually do so. It doesn't affect the result in the wiki addition example, but in general 32-bit registers should be used for ints.

Thanks, I reverted and added comment. Feel free to add anything helpful on that page.


Firefox not rendering some colours correctly

There's a few characters who have odd colour bugs that work fine on Edge,
Orcane, Hodan, Forsburn, Olympia, Etalus, Sylvanos and Shovel Knight all have a few stray pixels that appear in random colours and can't display correctly

Can't reproduce, and Firefox is the browser I develop with! Is your Firefox updated?
The random colors on the image provided are actually the shiny parts used by the golden and champion skins, which shouldn't be visible as all other skins paint over those.

That's so odd! It is updated and I've also tested this on 2 seperate computers both with it fully updated and in troubleshooting mode with all extensions enabled
I really have no idea what it could possibly be then, but thanks for your reply! Love the tool

The only other thing I can think of is graphics drivers (the image is generated with shaders using WebGL2). Make sure graphic drivers are updated, I guess? I also tried on 3 different computers and didn't see the issue.


Update virtual-machines-planned-maintenance.md

Adding region pairs for planned maintenance with an image.

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

This seems like a small (but important) contribution, so no contribution license agreement is required at this point. Real humans will now evaluate your PR.

TTYL, AZPRBOT;


Vim9: 'ignorecase' is wrongly used for comparators that use strings at the script level

Describe the bug
In Vim9 script, the 'ignorecase' option is wrongly used for comparators that use strings at the script level.
To Reproduce
Run this shell command:
vim -Nu NONE -S <(cat <<'EOF'
    vim9script
    set ic
    let str = 'aBc'
    echo str =~ 'abc'
EOF
)

1 is echo'ed.
Expected behavior
0 is echo'ed, because 'ignorecase' should be ignored:
https://github.com/vim/vim/blob/b146e01a7e41bf5787a2b5ccc6c340ed6001f308/runtime/doc/vim9.txt#L345
Environment

Vim version: 8.2 Included patches: 1-1253
OS: Ubuntu 16.04.6 LTS
Terminal: XTerm(356)

Additional context
The issue disappears in a :def function:
vim9script
set ic
def Func()
    let str = 'aBc'
    echo str =~ 'abc'
enddef
Func()

v:false

0 is echo'ed, because 'ignorecase' should be ignored:

Actually, to be consistent with a :def function, I think v:false should be echo'ed, instead of 0.


Navigation Sidebar

User Story
As an analyst I want a navigation sidebar so that I can go between pages of an application, assessments, history, and more later.
Acceptance Criteria

[x] Dashboard icon is fa-chevron-left; fixed width (fa-fw); colour is #38598A
[x] Application icon is clipboard-list from font-awesome; fixed width (fa-fw);colour matched to text
[x] Assessments icon is check-double from font-awesome; fixed width (fa-fw);colour matched to text
[x] History icon is clock-rotate-left from font-awesome; fixed width (fa-fw); colour matched to text

[x] Visible on application pages
Given that an analyst is on a page about an application (application, assessment, history, more to come later in the roadmap)
then they will see a navigation sidebar on the left side.

[ ] Pages linked
Given that an analyst sees the navigation sidebar
when they click on application
then they will be directed to the application page
when they click on assessments
then they will be directed to the eligibility assessment page
when they click on history
then they will be directed to the history page.

[x] Current page
Given that an analyst is on a page with the sidebar
then the current page in the sidebar will be bolded
and have a background colour of F1F2F3

[x] Hover
Given that an analyst is on a page with the sidebar
when they hover over a page
then the background of that link will change to F8F8F8

[x] Responsive -- just show the icons when <1007px
Given that an analyst is on a page with the navigation sidebar
when the viewport is <1007px
then the words of the navigation sidebar will not visible
and only the icons will be visible

[x] Sticky
Given that an analyst is on a page with the navigation sidebar
when they scroll
then the navigation sidebar will scroll to the top of the viewport and stick there.

Sticky - risk is that menu gets taller than view port & can't view bottom. Consider the importance of this....

[x] Hide icon from screen readers
Given that an analyst is using a screen reader
when they are on a page with the navigation sidebar
then the icon will not be read because the aria-hidden="true" attribute

Wireframe
Prototype
For each button:

Padding above & below is 8px
Padding on left is 8px
Spacing between icon & text is 8px

Margin between each button is 4px
If font size is 16, width is 139px
If font size is 18, width is 152px

[ ] Pages linked
Given that an analyst sees the navigation sidebar
when they click on application
then they will be directed to the application page
when they click on assessments
then they will be directed to the eligibility assessment page
when they click on history
then they will be directed to the history page.

In the meantime, since some of these pages aren't done, how do we want this to work?

@AntBush Would it be better to have blank pages or add these links when we build the respective pages?

Honestly, I'm not sure, I think the links being added in when we build the respective pages is a good idea since adding in new links would be a 1-pointer added in while we're making the pages. We could probably make the UI now and hide them behind a feature flag too.
If it just goes to a blank page it could be confusing for the users, especially if it's never clear as to when the page is now populated.

I removed the "except when they hove on the Dashboard link"  from the hover acceptance criteria, the dashboard link should still have a hover state to show that it's clickable, and should have the same hover effect as the other links

@MarsRomer @zoeyli-46 @elliottSlee slight visual bug made it in when I fixed something else. The padding to the right of the icon should be a bit larger. I will fix that but let me know if there is anything else you notice thanks.

Will the padding be there at smaller screen sizes so that it's even padding on either side when it's just icons?

No it'll actually just be increased on the text element.

Current page should be bolded, it currently isn't


feat(curriculum): create debugging quiz

Checklist:

[x] I have read and followed the contribution guidelines.
[x] I have read and followed the how to open a pull request guide.
[x] My pull request targets the main branch of freeCodeCamp.
[x] I have tested these changes either locally on my machine, or GitPod.

Closes #56208

This is a great start! Looks like there's a few things missing code tags.
Also you should never commit directly to your main branch when contributing to a repository.

Thank you for pointing that out! I’ll make sure to remember this moving forward and avoid committing directly to the main branch.

Hi @nayanmapara. Congrats on your first pull request (PR)! 🎉
Thank you for your contribution to the page! 👍
We are happy to accept these changes and look forward to future contributions. 📝

Note for future - it is recommended to make changes on a separate branch, rather than the main branch. See more about it in point 3 at https://contribute.freecodecamp.org/how-to-contribute-to-the-codebase/#contributing-to-the-codebase.

Thank you, looking forward to future contributions. 😄
Will keep it in mind to make changes on a separate branch. 💯


[Compute] Encrypted Disks on Virtual Machines

Bug Report
SDK version: v18.0.0
Package: github.com/Azure/azure-sdk-for-go/services/compute/mgmt/2017-12-01/compute
$ go version
go version go1.10.3 darwin/amd64

:wave:
I've spent a couple of days looking at how we'd support encrypted disks within Virtual Machines. As a part of this I've taken two approaches:

Provisioning a Virtual Machine and then on-boot encrypting brand new disks by specifying the EncryptionSettings struct.
Provisioning a Virtual Machine and then encrypting the Data Volume (I've also tried both the OS disk and "all", but Data should be quicker) using a Virtual Machine extension (using Terraform, but this should be no different in an ARM Template):

resource "azurerm_virtual_machine_extension" "disk-encryption" {
  name                 = "DiskEncryption"
  location             = "West Europe"
  resource_group_name  = "some-resource-group"
  virtual_machine_name = "some-virtual-machine"
  publisher            = "Microsoft.Azure.Security"
  type                 = "AzureDiskEncryptionForLinux"
  type_handler_version = "1.1"

  settings = <<SETTINGS
{
  "KeyVaultURL": "/subscriptions/00000000-0000-0000-0000-000000000000/resourceGroups/[name]/providers/Microsoft.KeyVault/vaults/[name]",
  "VolumeType": "DATA",
  "EncryptionOperation": "EnableEncryptionFormatAll",
  "KeyEncryptionKeyURL": "https://[name].vault.azure.net/keys/[name]/[version]",
  "KeyEncryptionAlgorithm": "RSA-OAEP"
}
SETTINGS
}

Unfortunately in both cases the CreateOrUpdate method in the SDK/API call times out after ~40m returning the rather unhelpful error (wrapped by Terraform in this case):
azurerm_virtual_machine.managed: Still creating... (40m50s elapsed)

Error: Error applying plan:

1 error(s) occurred:

* azurerm_virtual_machine.managed: 1 error(s) occurred:

• azurerm_virtual_machine.managed: Code="" Message=""

Looking in the Portal - there's a slightly more descriptive error but the Virtual Machine enters a Failed state with a description that it's Failed but may eventually boot (however I didn't see this boot even after leaving it overnight). Is there a way to work around this hard-timeout from the Compute API? Whilst it'd be possible to poll on the Compute API's Get method ourselves, I can't help but feel polling on a Failed state could lead to other issues? It's worth noting that the documentation for disk encryption mentions the encryption process can take an extended period (3h-days depending on the amount of data involved), but that wiping the data disk should be significantly quicker.
Is there an example available for Disk Encryption of a Virtual Machine that I'm overlooking?
Thanks!

@tombuildsstuff we have this sample for disk encryption: https://github.com/Azure-Samples/azure-sdk-for-go-samples/blob/master/compute/encryption.go
Let us know if it helps.

@tombuildsstuff was the sample useful for you ?

hey @vladbarosan I've not had a chance to circle back to this yet unfortunately, but that example 404's and I can't see it in the last few commits, is there another link? Thanks!

Hey @tombuildsstuff . @joshgav  refactored the repo a little since then. I think this is what you are looking for https://github.com/Azure-Samples/azure-sdk-for-go-samples/blob/master/compute/vm_test.go

@vladbarosan so checking the code sample that'll have the same issue mentioned above where the Compute API returns that this has entered the Failed state (but may eventually boot) - at least for Windows machines (whereas the code sample's for Linux). My understanding is that this is running Bitlocker which encrypts asynchronously (and eventually causes the Compute API to return a hard status of Failed, but which has a message in the portal of "may eventually boot")?
Is there a sample available for encrypting machines at boot too? Sorry to be awkward here 🙃

@tombuildsstuff coming back to this ? are you still blocked. we dont have a sample for enrypting machines on boot.
Regarding Windows please note that you can't encrypt the data volume without encrypting the OS volume first. ( See here  )
Let us know if there is any specific ask we would want for the compute team.

from a consumer of both azure and terraform (via the sdk for go), whats being done to move this forward?

This would be of really interest of all of us i think.

hey guys, this thread had diverged in a couple directions, can you let us know of a specific ask here please?
There is a sample for linux here.
Is that what you are looking for ? or is there any specific API call that is failing ?


Convert filenames to use snake_case by default.

Salvages https://github.com/godotengine/godot/pull/47275.
Pending proposal.

Will try to merge with https://github.com/godotengine/godot/pull/56848 which supersedes this.


Update README.md

2015-04-14T15:13:09.746726+00:00 app[web.1]: [ActiveJob] Enqueued SmallBuildJob (Job ID: 0b511c3e-d38f-4231-a1ca-a61fcb7a0e25) to SuckerPunch(medium) with arguments: {"number"=>1, "action"=>"synchronize", "pull_request"=>{"changed_files"=>4, "head"=>{"sha"=>"900a57544a1f53f0e8ccc27d35b45cd9c0898bda"}}, "repository"=>{"id"=>21122849, "full_name"=>"shinnyx/kaltura_box", "owner"=>{"id"=>"shinnyx", "login"=>1018860, "type"=>"User"}}}
2015-04-14T15:13:09.769988+00:00 app[web.1]: [ActiveJob] [SmallBuildJob] [0b511c3e-d38f-4231-a1ca-a61fcb7a0e25] Performing SmallBuildJob from SuckerPunch(medium) with arguments: {"number"=>1, "action"=>"synchronize", "pull_request"=>{"changed_files"=>4, "head"=>{"sha"=>"900a57544a1f53f0e8ccc27d35b45cd9c0898bda"}}, "repository"=>{"id"=>21122849, "full_name"=>"shinnyx/kaltura_box", "owner"=>{"id"=>"shinnyx", "login"=>1018860, "type"=>"User"}}}
2015-04-14T15:13:09.776955+00:00 app[web.1]: [ActiveJob] [SmallBuildJob] [0b511c3e-d38f-4231-a1ca-a61fcb7a0e25]   User Load (1.8ms)  SELECT "users".* FROM "users" INNER JOIN "memberships" ON "users"."id" = "memberships"."user_id" WHERE "memberships"."repo_id" = $1 AND ("users"."token" IS NOT NULL)  [["repo_id", 4]]
2015-04-14T15:13:09.954687+00:00 app[web.1]: [ActiveJob] [SmallBuildJob] [0b511c3e-d38f-4231-a1ca-a61fcb7a0e25] ** [Raven] Sending event 467a99e1c26847808e329464b04ed0ec to Sentry
2015-04-14T15:13:10.176263+00:00 app[web.1]: [ActiveJob] [SmallBuildJob] [0b511c3e-d38f-4231-a1ca-a61fcb7a0e25] ** [Raven] Unable to record event with remote Sentry server (Raven::Error - Unknown transport scheme '')
2015-04-14T15:13:10.176336+00:00 app[web.1]: [ActiveJob] [SmallBuildJob] [0b511c3e-d38f-4231-a1ca-a61fcb7a0e25] ** [Raven] /app/vendor/bundle/ruby/2.2.0/gems/sentry-raven-0.9.4/lib/raven/client.rb:77:in `transport'
2015-04-14T15:13:10.176372+00:00 app[web.1]: [ActiveJob] [SmallBuildJob] [0b511c3e-d38f-4231-a1ca-a61fcb7a0e25] ** [Raven] /app/vendor/bundle/ruby/2.2.0/gems/sentry-raven-0.9.4/lib/raven/client.rb:36:in `send'
2015-04-14T15:13:10.176377+00:00 app[web.1]: [ActiveJob] [SmallBuildJob] [0b511c3e-d38f-4231-a1ca-a61fcb7a0e25] ** [Raven] /app/vendor/bundle/ruby/2.2.0/gems/sentry-raven-0.9.4/lib/raven/base.rb:69:in `send'
2015-04-14T15:13:10.176439+00:00 app[web.1]: [ActiveJob] [SmallBuildJob] [0b511c3e-d38f-4231-a1ca-a61fcb7a0e25] ** [Raven] /app/vendor/bundle/ruby/2.2.0/gems/sentry-raven-0.9.4/lib/raven/base.rb:107:in `block in capture_exception'
2015-04-14T15:13:10.176484+00:00 app[web.1]: [ActiveJob] [SmallBuildJob] [0b511c3e-d38f-4231-a1ca-a61fcb7a0e25] ** [Raven] /app/vendor/bundle/ruby/2.2.0/gems/sentry-raven-0.9.4/lib/raven/base.rb:128:in `send_or_skip'
2015-04-14T15:13:10.176489+00:00 app[web.1]: [ActiveJob] [SmallBuildJob] [0b511c3e-d38f-4231-a1ca-a61fcb7a0e25] ** [Raven] /app/vendor/bundle/ruby/2.2.0/gems/sentry-raven-0.9.4/lib/raven/base.rb:101:in `capture_exception'
2015-04-14T15:13:10.176515+00:00 app[web.1]: [ActiveJob] [SmallBuildJob] [0b511c3e-d38f-4231-a1ca-a61fcb7a0e25] ** [Raven] /app/app/jobs/buildable.rb:9:in `rescue in perform'
2015-04-14T15:13:10.176535+00:00 app[web.1]: [ActiveJob] [SmallBuildJob] [0b511c3e-d38f-4231-a1ca-a61fcb7a0e25] ** [Raven] /app/app/jobs/buildable.rb:3:in `perform'
2015-04-14T15:13:10.176555+00:00 app[web.1]: [ActiveJob] [SmallBuildJob] [0b511c3e-d38f-4231-a1ca-a61fcb7a0e25] ** [Raven] /app/vendor/bundle/ruby/2.2.0/gems/activejob-4.2.1/lib/active_job/execution.rb:32:in `block in perform_now'
2015-04-14T15:13:10.176576+00:00 app[web.1]: [ActiveJob] [SmallBuildJob] [0b511c3e-d38f-4231-a1ca-a61fcb7a0e25] ** [Raven] /app/vendor/bundle/ruby/2.2.0/gems/activesupport-4.2.1/lib/active_support/callbacks.rb:117:in `call'
2015-04-14T15:13:10.176604+00:00 app[web.1]: [ActiveJob] [SmallBuildJob] [0b511c3e-d38f-4231-a1ca-a61fcb7a0e25] ** [Raven] /app/vendor/bundle/ruby/2.2.0/gems/activesupport-4.2.1/lib/active_support/callbacks.rb:117:in `call'
2015-04-14T15:13:10.177113+00:00 app[web.1]: [ActiveJob] [SmallBuildJob] [0b511c3e-d38f-4231-a1ca-a61fcb7a0e25] Performed SmallBuildJob from SuckerPunch(medium) in 407.03ms


Compilation errors in 2018.1.6f

I couldn't compile Windows standalone due to error 'unrecognized identifier 'SHADOW_COORDS' ' which happened anytime UNITY_LIGHT_ATTENUATION is called.  Google led me to try wrapping every call like this:
#if defined (SHADOWS_SCREEN) || defined (SHADOWS_DEPTH) || defined (SHADOWS_CUBE)
UNITY_LIGHT_ATTENUATION(attenuation, input, input.posWorld.xyz);
#else
float attenuation = 1;
#endif
That allowed me to compile but unfortunately I don't think that worked correctly as it seems to have affected lighting quality even when clearly fully supported.

Hey, I'm not getting any compilation errors on latest with Unity 2018.2 so closing this :)


[libsodium] Rework CMake build to match autoconf

Describe the pull request
The goal of this PR is to get this port's CMake buildsystem to match the behaviour of the project's autoconf buildsystem. The autoconf build is careful to ensure that CPU intrinsics are only enabled for translation units that do runtime detection of available CPU features. This PR achieves this by separating the library into CMake object libraries that can each have separate compile flags. I also used CMake interface libraries to define groups of common compiler flags.
I also tried using some of the new vcpkg_* functions in the portfile and converted CONTROL file over to a manifest file. I was somewhat confused by the original ports/libsodium/sodiumConfig.cmake.in file, so I converted it over to match the one I saw on the sqlite3 port.

What does your PR fix? Fixes #14134

Which triplets are supported/not supported? Have you updated the CI baseline?

I've tested x64-windows and x64-linux. I used this repo to test the consumption of the package: https://github.com/pathcore/vcpkg-libsodium-avx512

Does your PR follow the maintainer guide?

I hope so! I tried to modernize the port using some of the new features so it is possible I didn't follow all the new recommendations.

Thanks for improve it!

I found a tool to inspect an elf and print the x86 extensions used within [1]. I ran it on a binary we're generating internally to confirm that the x86 extensions are actually being used.
➜  ~/.cargo/bin/elfx86exts <redacted>
MODE64 (call)
SSE2 (pxor)
SSE1 (movaps)
CMOV (cmovs)
AVX (vmovdqa)
NOVLX (vpxor)
SSSE3 (pshufb)
SSE41 (pinsrb)
AVX2 (vinserti128)
CPU Generation: Unknown

I then took this binary and ran it on a machine that didn't support SSSE3, SSE41, and AVX2 and it still worked, so I'm pretty confident that this new build system lights up the x86 extensions in a portable way.
[1] https://github.com/pkgw/elfx86exts

/azp run

There was a legitimate error in the windows-static builds that I addressed last night with https://github.com/microsoft/vcpkg/pull/16730/commits/71fddf76cb153b35946bb026b8f1dadb3f778c38, but I'm also seeing some errors from the various builds along the lines of...
Convert-Path: /agent/_work/1/s/scripts/azure-pipelines/analyze-test-results.ps1:424
Line |
 424 |  … t_hash = build_test_results( Convert-Path "$logDir\$($triplet).xml" )
     |                                 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
     | Cannot find path '/agent/_work/1/a/xml-results/x64-linux.xml'
     | because it does not exist.

##[error]PowerShell exited with code '1'.
##[error]PowerShell wrote one or more lines to the standard error stream.
##[error]Convert-Path: /agent/_work/1/s/scripts/azure-pipelines/analyze-test-results.ps1:424
Line |
 424 |  … t_hash = build_test_results( Convert-Path "$logDir\$($triplet).xml" )
     |                                 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
     | Cannot find path '/agent/_work/1/a/xml-results/x64-linux.xml'
     | because it does not exist.

Is there a recommended way to reproduce this locally?


proxy variables

adding commented out proxy variables

@cpt-redbeard
Why do need to add those commented out variables?
We are referring to the full list of supposed environment variables that could be added throw the values YAML file?
https://docs.aquasec.com/docs/enforcer-optional-variables

Hey @cpt-redbeard
Can you please add a few words PR and explain it?
And please remove from this PR the proxy changes, we are working on some changes in this aae. shortly


error: Failed to load ressource

The kirby (as it is here) - executed locally (just opening the index.html) produces the following error for me (using chrome/safari):
kirby locally.log
I attach the log.
The tests however starts and can be used locally but the error seems to lead to a server timeout when used with expfactory.
This is super strange and I don't understand what is happening here :D
kirby server.log
To make it even more hard to understand: It worked until earlier this week (on the server).
Maybe one of the expfactory-components changed?
I also attach the dockerfile I use.
 Let's start with the issue in the browser. I tested for Firefox (no errors in the console) and then Chrome (I reproduced your issues) and for the latter, regardless of the error it seemed to function without issue. So, a first option is just to use Firefox, or be okay with having the messages in the console with Chrome. If you want to take a shot at fixing chrome, likely we just need to try following the instructions and reloading the audio context (see here https://developers.google.com/web/updates/2017/09/autoplay-policy-changes#webaudio) but then you'd need to check for the browser being used and make sure it's chrome. The last errors appear to be missing .map files, which could easily be added to the repository! Do you want to try some of these out and do a PR to the repository? I'd be happy to add any fixes.

Hi Vanessa,
I solved the issue by removing the divs from preloading but loading them inside the plugin.
Since the kirby is not time-sensitive I guess we can go with that.
I'm not a hundred percent sure though what exactly was the problem the html-preloading was causing on the server.

Great! If you think the experiment is better and others would benefit from your changes, please open a PR.


Allow custom command role ACL files on classpath in Static Role API Checker

Commit Message
This commit has a small refactoring of cloud-plugin-acl-static-role-based
to allow it to read files on the classpath that might have a different name
than "commands.properties". It also allows more than one file to be read from.
Rationale: Third-party plugins may want to keep their API command access level
configuration separate from the main file so as to reduce configuration
maintenance work during packaging and deployments.
Testing Performed
Ran the simulator locally and connected to it with Cloudmonkey. Ran sync and then executed some API commands to verify that they are not blacklisted (i.e. not found because CS could not read the file on the classpath).

Looks like the Oracle VM3 build failed in the pul request check. Is that a problem on the master branch currently?

LGTM, though we need to test it by producing packages. In theory, the /etc/cloudstack/management should be on classpath so this should work.

Is there anything I can do to assist with the testing?

@ProjectMoon can you share any test results? Is the spring xml gets into the compiled jar from users' perspective, how may I configure a different properties file, any docs in this regard?

This would be a step-by-step way of how I tested the change. We will use mycommands.properties as the example.

Add the new properties file name to the list in the Spring XML and then compile CloudStack.
Create mycommands.properties.in in client/tomcatconf. Build should move this to WEB-INF/classes after compilation as mycommands.properties.
Move some commands from commands.properties.in to mycommands.properties.in
Build and run client with Jetty server.
Use cloudmonkey sync command to verify it's reading all 479 commands in from both files.

@ProjectMoon my concern here is -- you're still making changes in the XML to make it work during build time, is there a way to make it configurable like rabbitmq plugin so one can add the xml at some place in  /etc/cloudstack/management to change/add file names in the XML. (pardon my ignorance, I'm not well versed with spring)

Yes, that is correct it would need to be done during build time. I can add a way to make the list of files configurable. I think it would be best to make a properties file that has a key and a comma-separated list of files to find on the classpath.
I don't want to stick make a new properties file with just one line though. Are there any properties file that go into /etc/cloudstack/management where I could stick this key-value?

@ProjectMoon can you rebase and re-submit the PR, the travis tests seems to be failing.

Pull request branch has been updated.

@weizhouapache a [SF] Jenkins job has been kicked to build packages. It will be bundled with  KVM, XenServer and VMware SystemVM templates. I'll keep you posted as I make progress.


I cannot use paper-dropdown-menu inside paper-step

Unfortunately i cannot use paper-dropdown-menu element inside paper-step. Its options cannot get selected. Any ideas why this happens?

Thank you for using paper-steps.
Can you create an example with JSbin to reproduce it? Is the paper-steps set to vertical or horizontal? Also, you might check if there are any elements with a higher z-index than your paper-dropdown-menu which might cause the element to be un-clickable.

@fakiolinho I have found the cause of this problem and will have a patch for it soon. Thanks for reporting the issue.


Update for 1.19.2?

No issue, love the mod and am incredibly grateful for you and the team's hard work on the other mods. Just curious if an update for 1.19.2 for fabric is possible?

Hi there,
Hopefully today (GMT).
Thanks.

Release for 1.19.2 has been made available on Modrinth and Github, pending approval on Curseforge.

Thank you so much! Anyway to donate to the cause?

I appreciate it, but I am not accepting donations currently. 😃


Tokenized BLEU considered harmful - Discussion on community-based process

https://github.com/huggingface/nlp/blob/7d1526dfeeb29248d832f1073192dbf03ad642da/metrics/bleu/bleu.py#L76 assumes the inputs are tokenized by the user.  This is bad practice because the user's tokenizer is usually not the same as the one used by mteval-v13a.pl, the closest thing we have to a standard.  Moreover, tokenizers are like window managers: they can be endlessly customized and nobody has quite the same options.
As @mjpost reported in https://www.aclweb.org/anthology/W18-6319.pdf BLEU configurations can vary by 1.8.  Yet people are incorrectly putting non-comparable BLEU scores in the same table, such as Table 1 in https://arxiv.org/abs/2004.04902 .
There are a few use cases for tokenized BLEU like Thai.  For Chinese, people seem to use character BLEU for better or worse.
The default easy option should be the one that's correct more often.  And that is sacrebleu.  Please don't make it easy for people to run what is usually the wrong option; it definitely shouldn't be bleu.
Also, I know this is inherited from TensorFlow and, paging @lmthang, they should discourage it too.

I second this request. The bottom line is that scores produced with different reference tokenizations are not comparable. To discourage (even inadvertent) cheating, the user should never touch the reference. The v13a tokenization standard is not ideal, but at least it has been consistently used at matrix.statmt.org, facilitating comparisons.
Sacrebleu exposes all its data sources and additionally provides an API to accessing the references, which seem to fit within the spirit of your codebase.

Didn't we have a slide and discussion at WMT admitting that, for production-quality models, BLEU doesn't correlate with human eval anyway?

Yes, there are slides like that at WMT every year :) BLEU correlates with human judgment only at coarse levels, and it seems to be getting worse when people try to use it to do model selection among high-performing neural systems.
However, the point isn't whether BLEU is a good metric, but whether your BLEU score can be compared to other BLEU scores. They only can be compared if you use the same reference tokenization (similar to how you can't compare LM perplexities across different segmentations). sacrebleu was an attempt to get everyone to use WMT's reference tokenization (meaning, your system has to first remove its own tokenization) so that you could just compare across papers. This also prevents scores from being gamed.

I do not consider as a sufficient solution switching this library's default metric from BLEU to the wrapper around SacreBLEU.
As currently implemented, the wrapper allows end users to toggle SacreBLEU options but doesn't pass along the SacreBLEU signature. As @mjpost showed in Post18, it's simply not credible to assume that people will stick to the defaults, therefore, the signature is necessary to be explicit about what options were used.
In addition to the v13a or intl options for the SacreBLEU tokenize argument, which was pointed out earlier, papers frequently differ on whether they lowercase text before scoring (lowercase) and the smoothing method used (smooth_method). BLEU scores can differ substantially (over 1 BLEU) just by changing these options.
Losing the SacreBLEU signature is a regression in reproducibility and clarity
(Perhaps this should belong in a separate issue?)

Thanks for sharing your thoughts. This is a very important discussion.
Also one of the first items on our mid-term roadmap (we will try to clean it and share it soon) is to introduce mechanisms to get high-quality traceability and reproducibility for all the processes related to the library.
So having the signature for sacrebleu is really important!
Regarding BLEU, I guess we can just remove it from the canonical metrics included in the repo itself (it won't prevent people to add it as "user-metrics" but at least we won't be promoting it).
On a more general note (definitely too large for the scope of this issue) we are wondering, with @srush in particular, how we could handle the selection of metrics/datasets with the most community-based and bottom-up approach possible. If you have opinions on this, please share!

Yeah, I would love to have discussions about ways this project can have an community-based, transparent process to arrive at strong default metrics. @kpu / @mjpost do you have any suggestions of how that might work or pointers to places where this is done right? Perhaps this question can be template for what is likely to be repeated for other datasets.

I think @bittlingmayer is referring to Figure 6 in http://statmt.org/wmt19/pdf/53/WMT02.pdf .  When you look at Appendix A there are some cases where metrics fall apart at the high end and some where they correlate well.  en-zh is arguably production-quality.
This could evolve into a metrics Bazaar where the value add is really the packaging and consistency: it installs/compiles the metrics for me, gives a reproducible name to use in publication (involve the authors; you don't want a different sacrebleu hash system), a version number, and evaluation of the metrics like http://ufallab.ms.mff.cuni.cz/~bojar/wmt19-metrics-task-package.tgz but run when code changes rather than once a year.

While a Bazaar setup works for models / datasets, I am not sure it is ideal for metrics ? Ideal from my perspective would be to have tasks with metrics moderated by experts who document, cite, and codify known pitchfalls (as above^) and make it non-trivial for beginners to mess it up.

@srush @thomwolf
ModelFront could provide (automated, "QE-based") evaluation for all the pretrained models you host.  Not bottom-up and not valid for claiming SoTA, but independent, practical for builders and not top-down.
For that I would also suggest some diverse benchmarks (so split it out into datasets with only user-generated data, or only constants, or only UI strings, or only READMEs) which tease out know trade-offs.  Even hypothetical magic eval is limited if we always reduce it to a single number.
Realistically people want to know how a model compares to an API like Google Translate, Microsoft Translator, DeepL or Yandex (especially for a language pair like EN:RU, or for the many languages that only Yandex supports), and that could be done too.

Very important discussion.
I wanted to ask which is a good practice.
Sacrebleu should be used on top of the tokenized output, or detokenized(raw) text?

Very important discussion.
I wanted to ask which is a good practice.
Sacrebleu should be used on top of the tokenized output, or detokenized(raw) text?

Use sacrebleu on detokenized output and raw unmodified references.

Use sacrebleu on detokenized output and raw unmodified references.


Extracting OpenTelemetry Data from GitHub Repositories and Organizations using Sample-Trace2-Otel-Collector

How can I extract OpenTelemetry data at the repository, organization, and project levels from GitHub using the Sample-Trace2-Otel-Collector tool?

The tool is designed to capture performance data on Git commands as they run.  You can create a custom collector on your local system (and maybe share it with your team/organization) and collect Git perf data in a database or OTEL data store of your choosing.  Then you can post-process the data (using whatever tooling your database/data store provides.
For more information, see:

https://github.blog/2023-10-16-measuring-git-performance-with-opentelemetry/
https://github.com/git-ecosystem/trace2receiver/tree/main/Docs

This is not a tool to extract repository or performance data from GitHub.
Hope this helps.


Integrate model A into LangChain framework

From this issue, we want to integrate modelA into LangChain framework so we could feed voice as input to interact with LLM.

Demo colab in https://github.com/Cockatoo-AI-Org/Cockatoo.AI/pull/51

https://github.com/Cockatoo-AI-Org/Cockatoo.AI/pull/51


$network rules do not work on Windows

Steps to reproduce:

Add 93.184.216.*$network (it should block example.org)
Open example.org

Expected
Connection reset
Actual result
It's possible to open the website

core/pull-requests/1291

It seems that they are now dropping packets instead of rejecting connections

Also, here's a crash related to this: https://sentry.adguard.com/adg/adguard-windows/issues/26262/?query=is:unresolved
Steps to reproduce

Add <IP_ADDRESS>$network to the user filter
Restart protection ($network rules aren't applied without a restart -- another bug)
Try opening example.org
Page loading will hang (due to https://github.com/AdguardTeam/CoreLibs/issues/927#issuecomment-506804711)
Open user filter and edit the rule, change it to @@<IP_ADDRESS>$network
AdGuard will crash


refactor: optimize and improve the cax-campanydata.tsx

Description

Improved and optimized cax-companyData.tsx to ensure maintainability, scalability, and performance.
Changelog entry:

Refactor, optimise and reorganise the code in cax-companyData.tsx file [#317](https://github.com/eclipse-tractusx/portal-frontend-registration/pull/317)

Why

Reusability: Refactoring the code can make it more modular and reusable, reducing code duplication and improving maintainability.
Performance: Optimizing the code will improve the page's rendering speed and overall performance, leading to a better user experience.
Readability and Understandability: Improving code organization, naming conventions, and commenting will make the code easier to understand and maintain.
Testability: By breaking down the code into smaller, more manageable pieces, we can improve test coverage and make it easier to write unit tests.

Issue

https://github.com/eclipse-tractusx/portal-frontend-registration/issues/316

Checklist

[x] I have performed a self-review of my own code
[x] I have successfully tested my changes locally

@shubhamv-ss pls address translation comment from Lavanya. Also fix sonar cloud issue. Rest looks fine to me

Since @shubhamv-ss is leaving the project from Cofinity-X side, please request changes from either me or @JordanGerada3.
Shubham still offered to support if he is needed.


Brave Search is no longer themed

Is there an existing issue outlining your problem?

[X] I am using the latest version of the provided userstyle.
[X] I have searched the existing issues and they do not solve my problem.

What userstyles are you seeing the problem on?
lbl:brave-search
Describe your problem.
Brave Search is no longer themed at all.
Attach screenshots.

What browser(s) are you seeing the problem on?
Firefox v124.0.1
Any additional comments?
No response

Could accent color also be added as well since you are rewriting it? I never really liked the Brave Search theme for some reason always


Chat with me button on profile

Depends on https://github.com/solid/chat-pane/pull/45

To do: This requires the logged in user to grant the visited pod Write+Control access to their own pod. To resolve this, we should have a list of deployed chat apps that can receive a 'create' action, and see if the user has any of those as a trusted app. If they don't, the button can still offer to send the other user an invite, without creating the chat room (leaving that up to the other person)


Is it availble to switch from ssr to blazor in browser after all the wasm and dlls downloaded?

(asked above)

Thanks for contacting us, @juepiezhongren.
This should be possible today and we'll add docs covering this in the future: https://github.com/aspnet/Docs/issues/11366


Stuck on Waiting for login to finish...

Need more info

@Edouard127 having the same issue. I just put in the file this
[{"username: "", "password": ""}]

Yet it doesn't log anything in the console and doesn't seem to be working

You have to use an actual account

You have to use an actual account

Obviously, I did.
Anyhow, I now managed to make it work. It was a network issue, but it didn't log anything.

You have to use an actual account

Obviously, I did. Anyhow, I now managed to make it work. It was a network issue, but it didn't log anything.

It's missing a " in your json, now it notify you if there's a bad json config


More flexible disable comments for promql/series

Codecov Report

Merging #320 (16421f7) into main (3e4d981) will increase coverage by 0.02%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##             main     #320      +/-   ##
==========================================
+ Coverage   95.57%   95.60%   +0.02%
==========================================
  Files          72       72
  Lines        5791     5820      +29
==========================================
+ Hits         5535     5564      +29
  Misses        193      193
  Partials       63       63

Impacted Files
Coverage Δ

internal/checks/promql_series.go
99.41% <100.00%> (+0.02%)
:arrow_up:

internal/parser/models.go
92.83% <100.00%> (+0.34%)
:arrow_up:

Help us with your feedback. Take ten seconds to tell us how you rate us.


fix(sec): upgrade golang.org/x/net to 0.7.0

What happened？
There are 1 security vulnerabilities found in golang.org/x/net v0.0.0-20210825183410-e898025ed96a

CVE-2022-41723

What did I do？
Upgrade golang.org/x/net from v0.0.0-20210825183410-e898025ed96a to 0.7.0 for vulnerability fix
What did you expect to happen？
Ideally, no insecure libs should be used.
How can we automate the detection of these types of issues?
By using the GitHub Actions configurations provided by murphysec, we can conduct automatic code security checks in our CI pipeline.
The specification of the pull request
PR Specification from OSCS

@sugusd good catch! Could you fix DCO?


Missing attachto documentation

I found attachto module in helpers folder, but there is no description. Only tests.
I offer to add description for attachto.

Yes that would be great :+1:  It's useful for implementing modals and similar things.

I've found this in 2015 Gitter messages:
attachTo is a function that makes it possible to declare that a vnode should be attached to something else than it's parent.
It contains the low level functionality of react-portal.
Very simple modal example demonstrates how to use it.


python311Packages.twilio: 8.5.0 -> 8.6.0

Diff: https://github.com/twilio/twilio-python/compare/refs/tags/8.5.0...8.6.0
Changelog: https://github.com/twilio/twilio-python/blob/8.6.0/CHANGES.md
Description of changes

Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
23.11 Release Notes (or backporting 23.05 Release notes)

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

[ ] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 249196 run on x86_64-linux 1

5 packages built:

home-assistant-component-tests.twilio
python310Packages.twilio
python310Packages.twilio.dist
python311Packages.twilio
python311Packages.twilio.dist


Unused argument in default initial step of adaptive integrators

In AdaptiveStepsize(Field)Integrator, method initializeStep has a fourth argument mapper that is not used

Good catch, thanks!


Get consumption data API - The consumed quantity didn't match with the v1 usage report

Following with the document: https://msdn.microsoft.com/en-us/library/azure/mt219001
SubscriptionType: PAYG
Billingcycle: 12th to 11th every month
=Issue Description=
From the v1 usage report, there are two parts: the up-side is the total consumed quantity by sub-category this month, and the down-side is the daily consumed quantity. That means by sum of the daily consumed quantity will be equals to the total consumed quantity.
However, we found the the response of daily consumed from API is not totally match with the v1 usage daily report, then the monthly consumed will also not match.
=Sample Request=
https://management.azure.com/subscriptions/{subscription-Id}/providers/Microsoft.Commerce/UsageAggregates?api-version=2015-06-01-preview&reportedStartTime=2018-05-12T00%3A00%3A00%2B00%3A00&reportedEndTime=2018-06-12T00%3A00%3A00%2B00%3A00&aggregationGranularity=Daily&showDetails=false
=Partial Response=
{
"name": "Daily_BRSDT_20180512_0000",
"type": "Microsoft.Commerce/UsageAggregate",
"properties": {
"usageStartTime": "2018-05-11T00:00:00+00:00",
"usageEndTime": "2018-05-12T00:00:00+00:00",
"meterName": "IP Address Hours",
"meterCategory": "Networking",
"meterSubCategory": "Reserved IP",
"unit": "Hours",
"meterId": "26ce34b7-67b3-480d-9d1b-54a7fb80f67a",
"infoFields": {},
"quantity": 6.5999999999999994
}
},
{
"name": "Daily_BRSDT_20180512_0000",
"type": "Microsoft.Commerce/UsageAggregate",
"properties": {
"usageStartTime": "2018-05-11T00:00:00+00:00",
"usageEndTime": "2018-05-12T00:00:00+00:00",
"meterName": "IP Address Hours",
"meterCategory": "Networking",
"meterSubCategory": "Reserved IP",
"unit": "Hours",
"meterId": "26ce34b7-67b3-480d-9d1b-54a7fb80f67a",
"infoFields": {},
"quantity": 5.79999999999999947
}
},
The above response from API show the consumed quantity on 2018-05-11 of Reserved IP was 6.59999 + 5.79999 = 12.399
=V1 Usage Report=
The consumed quantity show on usage report on 2018-05-11 is 21.2
https://vmtestdiag0703.blob.core.windows.net/reservedip/reservedip.PNG
=Question=
Is there any old API version can be used to get the same consumed quantity with v1 usage report ? Or any workaround to make the total consumed quantity same with the v1 usage report? Thanks.

@jackting73 could you provide us with the  documentation link you were referring to ?

Hi @Adam-Smith-MSFT
Following with the Get consumption data

@jackting73 I just assigned @femsulu to help route your request to the appropriate group.

Hi @femsulu
My billing cycle is from 5-12-2018 to 6-11-2018, but the invoice include partial usage from previous cycle on 5-11-2018 which should NOT be in this billing cycle.
Quick Summarize the issues here:

The invoice is based on the v1 usage report to sum of the daily usage because v1 is correct, however the sum of daily usage of v2 usage report is not the same with v1, and the worst thing is it seems the API is aligned with v2 usage report ... (Here takes the backup service as example)
to sum of v1 daily usage is equals to the monthly v1 usage report
to sum of the v2 daily usage is NOT equals to the monthly v2 usage report

I know the difference of reported & actual usage. So, the example here is 5-12-2018 to 6-11-2018. When pull a larger windows(ex: 5-9-2018 to 6-14-2018) than whittle it down to the right billing cycle (5-12-2018 to 6-11-2018), then sum of the total usage from API never equals to the invoice because of the partial usage from 5-11-2018 which make the API no chance to match the invoice.

Is there any API can be used to map with the v1 usage report ?

@jackting73 thanks for summarizing your issues with usage discrepancy between the v1 or v2 reports. The best path to resolve this issue and answer your question will be to raise a support request with the Billing team via Azure mgmt Portal's help&support blade as shown below. please do not hesitate to ping if you have any additional questions.

@jackting73
We will now close this issue. If there are further questions regarding this matter, please reopen it and we will gladly continue the discussion.

Regarding Consumed Quantity and Quantity sum from utilization, equality is still valid. I am not able to correctly split Invoice line items resources from Partner Center with Utilization resources quantity, because the Quantity sum from Utilization is less the quantity from line items in invoices


Salary do not exist

Pycharm python manage.py runserver
error Salary do not exist
idea?

There is no salary field.


Empty response on graphql request

Empty response on graphql request
When sending a graphql POST request to the apollo-server, I receive nothing but an empty response.
Context
Since this is my first ever project using Apollo (trying to set it up with Meteor, React, apollo-client and apollo-server using express), I'm just trying to connect a front end with the Fortunecookie api.
This is what I figured out so far:

The first sign of an error is the following: "Can't find field fortuneCookie on object (ROOT_QUERY) {}.↵Perhaps you want to use the 'returnPartialData' option?". When I went looking for this in the Redux Devtool, I found my query as such:

query: {
    id: "ROOT_QUERY",
    typeName: "Query",
    selectionSet: { ... }
}

Next I went looking for the actual request I sent to the server:

{"query":"{\n  fortuneCookie {\n    fortune\n  }\n}\n","operationName":""}

Which gave nothing in response.
Setup
Since the task I want to complete is fairly simple, my setup is too. The query I want to execute runs perfectly fine on GraphiQL, which leads me to believe my server is running as it should.
ApolloProvider
import React, {Component} from 'react'

import { ApolloProvider } from 'react-apollo'
import client from '/imports/api/apollo/client/client'

export default MainLayout = ({content}) => {
    return (

            <ApolloProvider client={client}>
                {content}
            </ApolloProvider>

    )
}

Child Component
The {content} child set in the <ApolloProvider /> is the <TestComponent /> displayed below. This is set using kadira's FlowRouter and react-mounter, nothing special there.
import React, {Component} from 'react'
import {graphql} from 'react-apollo'
import gql from 'graphql-tag'
const TestComponentWithoutData =  class TestComponentWithoutData extends Component {
    render() {
        const {loading, data} = this.props.data
        return (

                { loading? 'loading...' : data.fortuneCookie}

        )
    }
}

const FORTUNE = gql`{
  fortuneCookie{fortune}
}`

const withFortune = graphql(FORTUNE)
export default TestComponent = withFortune(TestComponentWithoutData)

Extra Screenshots
During a conversation on the apollo slack channel, I took some screenshots. They might provide some extra insights.
The ApolloClient object:

The HTTP request (response is empty):

First an APOLLO_QUERY_INIT action is stored:

Next an APOLLO_QUERY_ERROR action:

I hope I provided enough information. Please bare with me that chances are my setup is just wrong and there is nothing funky going on with the apollo stack. This is my first project after all.
EDIT: I realise I said my server seems to be running fine, but because there isn't any response returned from my request I thought this issue belonged in the apollo-server repo.

Have you tried opening /graphiql on your server and trying to run a query from there?

Just a guess here, but could it be that you're sending the request to the route that's serving graphiql? Unrecognized token '<' kind of suggests that you're getting html, not an empty response.
Do you have other queries that work fine?
Since this could be due to a lot of different reasons (error on the server, error on the client, wrong setup, etc.) it would be useful if you could create a repo with a reproduction for us. It sounds like your project is already pretty minimal, so if you can just put that in a github repo it would be fine.

@stubailo Yes, the same fortuneCookie query runs perfectly fine in GraphiQL.
@helfer It's very likely my setup is just wrong. I'll make a new Repo right away and share it here!

@helfer I just published the project as is to a new remote: https://github.com/JeroenBe/no-response/tree/develop , as you said, its in super early stages anyway ;)

@JeroenBe  the problem seems to be with your client configuration. You should use the network interface when creating a client (you created a variable but never used it).
export default client = new ApolloClient({
	networkInterface: createNetworkInterface('/graphql', {
    credentials: 'same-origin',
	}),
	shouldBatch: false
	});

You need to just direct to the /graphql and not to the full path, but I am not quite sure why... anyone up here can shed some light? (in return to a good the response I will PR the documentation...)

@Tallyb Thanks for the reply!
It didn't really solve the problem though. I placed a screenshot of the ApolloClient object in my bugreport, as you can see the default uri is already defined as '/graphql'. I tried it with your code nonetheless, but without any results.
Does it work on your end?

@helfer In regards to sending the request to graphiql, here's the code that defines both the graphql and graphiql route:
app.use('/graphql',  apolloExpress(req => ({
        schema: executableSchema,
        context: {
            Cookies: new Cookies({connector: fortuneCookieConnector})
        },
        graphiql: true
})))

app.use('/graphiql', graphiqlExpress({
    endpointURL: '/graphql'
}))

The ApolloClient uses '/graphql' as its uri, as shown in the screenshot of the ApolloClient object above.

One more thing that I did is install the whatwg-fetch polyfill and import
it.
On Sun, Aug 21, 2016, 16:12 Jeroen<EMAIL_ADDRESS>wrote:

@helfer https://github.com/helfer In regards to sending the request to
graphiql, here's the code that defines both the graphql and graphiql route:
app.use('/graphql',  apolloExpress(req => ({
schema: executableSchema,
context: {
Cookies: new Cookies({connector: fortuneCookieConnector})
},
graphiql: true
})))
app.use('/graphiql', graphiqlExpress({
endpointURL: '/graphql'
}))
The ApolloClient uses '/graphql' as its uri, as shown in the screenshot
of the ApolloClient object above.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/apollostack/apollo-server/issues/103#issuecomment-241256567,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AHC0j3LZHxyYEuBDpytlWMpds9pVf2Iyks5qiE7QgaJpZM4JpLJ4
.

@Tallyb Could you show me how you're using whatwg-fetch? I'm not sure what do do with it :s

npm install --save whatwg-fetch
on your client definition file (client.js)
import 'whatwg-fetch';
Did you notice that on my example above I removed the localhost:4000 from the client definition?

Ok, so I installed whatwg-fetch (and what since it's a peer dependency) and importing it, but I still receive the same error. If the code works on your end, would you mind making a PR to the repo I shared? (https://github.com/JeroenBe/no-response/tree/develop)

It looks like your request is going to the meteor server instead of the GraphQL server. Install the http-proxy-middleware package from npm and add these two lines somewhere in your server startup code:
import proxyMiddleware from 'http-proxy-middleware';
WebApp.rawConnectHandlers.use(proxyMiddleware('http://localhost:4000/graphql'));

having the same problem. graphiql is working but not my front-end query. repo: https://github.com/jktunney/newgivefit/tree/apollo

ok - here is what I did:
on client.js:
export default client = new ApolloClient({
	networkInterface: createNetworkInterface('//localhost:4000/graphql', {
    credentials: 'same-origin',
	}),
	shouldBatch: false
	});

Then I added cors support as described in the docs:
http://docs.apollostack.com/apollo-server/tools.html#corsSupport
so server js now has:
import cors from 'cors';

const app = express().use('*', cors());

Need also npm install cors of course (pun-intended)

@helfer @Tallyb Yes! Both solutions are working!
Could you elaborate as to why these are working and which one is best practice?
Thanks btw!

You were simply sending the query to the wrong server. The GraphQL server is on port 4000, but you sent the query to port 3000, which is the Meteor server. You can either directly call the GraphQl server (CORS) or proxy through the Meteor server. Either is fine, and it probably doesn't matter for your setup.

By the way, with the new Apollo Server you can use it with connect directly, no proxy required.

@stubailo Do you mean by using the cors package as suggested by @Tallyb?

No I'm saying you can do WebApp.connectHandlers.use('/graphql', apolloExpress(...)) and then no cors required.

@stubailo but using connect will still redirect calls to GraphQL server via the meteor server, which can impact load and performance, right?

Oke, so now I have the following code in my server.js file:
const app = express() //running on port 4000
// ...
WebApp.connectHandlers.use('/graphql',  apolloExpress(req => ({
        schema: executableSchema,
        context: {
            Cookies: new Cookies({connector: new FortuneCookieConnector()})
        },
        graphiql: true
})))

In stead of:
app.use('/graphql',  apolloExpress(req => ({
        schema: executableSchema,
        context: {
            Cookies: new Cookies({connector: new FortuneCookieConnector()})
        },
        graphiql: true
})))

this gives me Cannot POST /graphql? on GraphiQL, when I define GraphiQL in the same way:
WebApp.connectHandlers.use('/graphiql', graphiqlExpress({
    endpointURL: '/graphql'
}))

I get following error when requesting GraphiQL: Cannot GET /graphiql
I'm guessing I have to reference the location of the actual express server, where would I do this?

You shouldn't need express at all anymore - I'll look into this more soon.

@stubailo Yes! I removed all references to express which did the trick!
Thanks everyone for the responses! @stubailo @helfer @Tallyb

Oh, glad it worked out!

@Tallyb just saw your comment - I can't think of any reason this would have a performance disadvantage compared to using something else.

@stubailo my thought is that if you go via meteor server, it needs to handle your request and then redirect it to the Apollo Server, while using the direct access to the Apollo Server, does not require the Meteor Server to handle it at all. If they are on different machines, and with high load of users, it can be significant. Am I missing something here?

@JeroenBe  can you post your solution? i'm having a similar issue and it would be much appreciated. thanks!

@jktunney Yea of course!
In the end I went with @stubailo's solution. In my server.js I removed all express references/dependencies. and replaced it with WebApp.connectHandlers, e.g.:
import express from 'express'
const app = express()

app.use(bodyParser.json())

app.use('/graphql', new ApolloExpress( ... ))
// ... etc etc etc

became:
WebApp.connectHandlers.use(bodyParser.json())
WebApp.connectHandlers.use('/graphql', new ApolloExpress( ... ))
// ...

And on the client, my client is defined as such:
import ApolloClient from 'apollo-client'

export default client = new ApolloClient();

The problem in my case was the graphql requests being sent to the meteor server, not the express or graphql server. Meteor doesn't know what to do with them, hence the error. Obviously there are multiple ways of solving this (I listed them up in my initial post).
Hope this helps!

ok, i'm still not getting it. i'm using node and express however...
here is my server:
`var webpack = require('webpack');
var WebpackDevServer = require('webpack-dev-server');
var express = require('express');
var graphql = require('graphql');
var graphqlTools = require('graphql-tools');
var apollo = require('apollo-server');
var apolloExpress = apollo.apolloExpress;
var graphiqlExpress = apollo.graphiqlExpress;
var bodyParser = require('body-parser')
var proxyMiddleware = require('http-proxy-middleware');
var cors = require('cors');
//Material UI
global.navigator = { navigator: 'all' };
var schema = require('./app/data/schema');
var compiler = require('./webpack.config');
//GraphQL Stuff
var PORT = 8080;
var graphqlServer = express();
graphqlServer.use('/graphql', bodyParser.json(), new apolloExpress({
schema: schema
}));
graphqlServer.use('/graphiql', graphiqlExpress({
endpointURL: '/graphql',
}));
graphqlServer.listen(PORT, () => console.log(
GraphQL Server is now running on http://localhost:${PORT}/graphql
));
var app = new WebpackDevServer(compiler, {
contentBase: "/public/",
publicPath: "/static/",
stats: {colors: true}
});
app.use(proxyMiddleware('http://localhost:3010/graphql'));
app.use("/", express.static("static"));
app.listen(3000);
console.log("The App Server is running.")
`
here is my client `import React from 'react';
import { render } from 'react-dom';
import { browserHistory, IndexRoute, Router, Route } from 'react-router';
//Redux stuff
import thunkMiddleware from "redux-thunk";
import { Provider } from 'react-redux';
import { bindActionCreators, createStore, applyMiddleware } from 'redux';
//Local imports
import { queryReducer } from './reducers/reducer';
import routes from './config/routes';
import configStore from './store/configStore';
//Material UI qualms
import MuiThemeProvider from 'material-ui/styles/MuiThemeProvider';
import injectTapEventPlugin from "react-tap-event-plugin";
import ApolloClient, { createNetworkInterface, addTypename } from 'apollo-client'
import { ApolloProvider } from 'react-apollo'
injectTapEventPlugin();
//Create store middleware
/const createStoreWithMiddleware = applyMiddleware(thunkMiddleware)(createStore);/
const client = new ApolloClient({
networkInterface: createNetworkInterface('localhost:8080/graphql', {
credentials: 'same-origin',
}),
shouldBatch: false
})
console.log("client");
console.log(client);
console.log("client");
const Application = () => (

);
render(

,
document.getElementById('app')
);
`
here is my react component with my apollo query:
`import React, { Component } from 'react';
import { graphql } from 'react-apollo';
import gql from 'graphql-tag';
import GridComponent from './GridComponent';
class GridContainer extends React.Component {
render() {
	console.log("props")
	console.log(this.props)
	const workouts = this.props.data.workouts;

	return (
		<GridComponent workouts={workouts} />
	)
}

};
const GET_WORKOUTS = gql  query getWorkouts {      workouts { title, date, time, location, author, contentSnippet, tags, day, image, avatar, id }    };
const withWorkouts = graphql(GET_WORKOUTS);
const GridContainerWithData = withWorkouts(GridContainer)
export default GridContainerWithData;`
graphiql is working:

when i go to my graphql route in my browser it returns:

when i navigate to my route that renders the GridContainerWithData it shows this error in the console:

i've tried all the different solutions above, barring using connectHandlers (not using Meteor)... very frustrated because it seems like it should be a simple solution. i'd appreciate any help!

@jktunney could you commit your latest changes to your repo? I cloned it but it seems the repo you have online is not up to date with the code you shared here.

@JeroenBe the repo should be updated at this branch: https://github.com/jktunney/newgivefit/tree/apollo

@jktunney Ok, so after running the project and logging the actual error it throws, it seems the error you receive is slightly different than the one I got:
"Network error: JSON Parse error: Unexpected identifier \"Cannot\""
I'm not sure if your problem is caused by the same issue as mine :s

@JeroenBe how were you able to produce that error?

@jktunney the error field is part of your response. One the first render the error field is obviously undefined since the query is still loading: true. When loading: false or loading: undefined (in case of an error), the component will rerender.
on this line, you try to access your workouts, but since the query failed with an error you get thrown an exception. I removed this line and in stead logged this.props.data.error.

very strange... when i swap this
class GridContainer extends React.Component {

	render() {
		console.log("props")
		console.log(this.props)
		const workouts = this.props.data.workouts;

		return (
			<GridComponent workouts={workouts} />
		)
	}
};

for this:
class GridContainer extends React.Component {
	constructor(props) {
		super(props)
	}
	render() {
		console.log("props")
		console.log(this.props)
		const workouts = this.props.data.workouts;
		console.log("workouts")
		console.log(workouts)

		return (

				hello world

		)
	}
};

i get:

but when i try to pass "workouts" to my GridComponent component, I get:

I'm concerned that this thread might be related to several different issues at this point.


add sonatype as deployment destination

prep for #30 again, a release version is still required

trying close + reopen...

Codecov Report

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

@@            Coverage Diff            @@
##             master      #46   +/-   ##
=========================================
  Coverage     92.12%   92.12%
  Complexity      656      656
=========================================
  Files            83       83
  Lines          1804     1804
  Branches         79       79
=========================================
  Hits           1662     1662
  Misses          110      110
  Partials         32       32

Impacted Files
Coverage Δ
Complexity Δ

...b/dynodao/processor/schema/DynamoSchemaParser.java
100% <ø> (ø)
6 <0> (ø)
:arrow_down:

Continue to review full report at Codecov.

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


patch for removing the kubevirt client-go

As requested by @naiming-zededa , this is a PR against poc-dec3 that removes any dependency on kubevirt.io/client-go, and thus the dependency hell issues that came with it.

@naiming-zededa feel free to merge this, or just use this as a reference base. When you are done, though, please close it, so I can delete my branch.

Also, there still is an issue with go mod tidy, but it is not directly related to the kubevirt issues:
go: finding module for package k8s.io/metrics/pkg/client/clientset/versioned
go: finding module for package github.com/lf-edge/eve/pkg/kube/cnirpc
go: found k8s.io/metrics/pkg/client/clientset/versioned in k8s.io/metrics v0.29.2
go: finding module for package github.com/lf-edge/eve/pkg/kube/cnirpc
go: github.com/lf-edge/eve/pkg/pillar/cmd/zedrouter imports
        github.com/lf-edge/eve/pkg/kube/cnirpc: module github.com/lf-edge/eve@latest found (v7.4.0-master-private+incompatible), but does not contain package github.com/lf-edge/eve/pkg/kube/cnirpc

I will try and fix it up, but be aware it is there.

Oh, I see what it is. You depend on a package from github.com/lf-edge/eve/pkg/kube/cnirpc. This is not just another "package" in the go sense, but an entirely different container build.
As far as I can tell, it is consumed in multiple places in pillar - pkg/pillar/nireconciler, pkg/pillar/types, pkg/pillar/cmd/zedrouter - as well as one other place, in kube package itself - pkg/kube/eve-bridge.
Maybe it belongs in eve-libs?
Actually, reading it through, it is all just 16 statically defined types, and all pretty common things in CNI. Do we need a custom library and types for it at all? I think almost everything would be covered by https://pkg.go.dev/github.com/containerd/go-cni and https://pkg.go.dev/github.com/containernetworking/cni/pkg/types ?


Implements phone auth support for Admin node.js SDK.

Adds phoneNumber to UserRecord and UserInfo.
Implements new API for looking up users by phone number: getUserByPhoneNumber
Adds the ability to pass the phoneNumber property when creating a new user,
or updating an existing one via createUser and updateUser.
This includes the ability to delete the phone number for a specified user.
Defines the new related auth errors:
auth/invalid-phone-number and auth/phone-number-already-exists.

I believe we also need to update index.d.ts right?

Thanks for catching the missing definitions in index.d.ts. I added those. I also added detailed response for getAccountInfoByPhoneNumber. More detailed checks on parsing is adding for getUserByPhoneNumber.

LGTM

LGTM with one minor suggestion.


Permission for rarabaolaza on mock-security-realm

Description
Requesting deploy permission grant to @raul-arabaolaza in repository https://github.com/jenkinsci/mock-security-realm-plugin, already approved by @stephenc , see https://github.com/jenkinsci/mock-security-realm-plugin/pull/7#issuecomment-640514503
Submitter checklist for changing permissions
Always

[X] Add link to plugin/component Git repository in description above

For a newly hosted plugin only
This does not apply

[ ] Add link to resolved HOSTING issue in description above

For a new permissions file only
This does not apply

[ ] Make sure the file is created in permissions/ directory
[ ] artifactId (pom.xml) is used for name (permissions YAML file).
[ ] groupId / artifactId (pom.xml) are correctly represented in path (permissions YAML file)
[ ] Check that the file is named plugin-${artifactId}.yml for plugins

When adding new uploaders (this includes newly created permissions files)

[X] Make sure to @mention an existing maintainer to confirm the permissions request, if applicable
[X] Use the Jenkins community (LDAP) account name in the YAML file, not the GitHub account name
[X] Make sure to @mention the users being added so their GitHub account names are known if they require GitHub merge access (see below).
[X] All newly added users have logged in to Artifactory at least once

Reviewer checklist (not for requesters!)

[ ] Check this if newly added person also needs to be given merge permission to the GitHub repo (please @ the people/person with their GitHub username in this issue as well). If needed, it can be done using an IRC Bot command
[ ] Check that the $pluginId Developers team has Admin permissions while granting the access.
[ ] In the case of plugin adoption, ensure that the Jenkins Jira default assignee is either removed or changed to the new maintainer.
[ ] If security contacts are changed (this includes add/remove), ping the security officer (currently @daniel-beck) in this pull request. If an email contact is changed, wait for approval from the security officer.

There are IRC Bot commands for it
IRC Bot command](https://jenkins.io/projects/infrastructure/ircbot/#github-repo-management)

[ ] Check that the $pluginId Developers team has Admin permissions while granting the access.
[ ] In the case of plugin adoption, ensure that the Jenkins Jira default assignee is either removed or changed to the new maintainer.
[ ] If security contacts are changed (this includes add/remove), ping the security officer (currently @daniel-beck) in this pull request. If an email contact is changed, wait for approval from the security officer.

There are IRC Bot commands for it

I am the active maintainer but retroactive :+1: for this PR in case of emergencies


performance improvements

fixed unnecessary object references
avoid unnecessary array_merges
speedup travis builds
speedup tests

@bighappyface are you willing to review this one?

related tweet which shows the measured improvements:
https://twitter.com/digitalkaoz/status/778573654712061952

some more context:

at best you would drop the public blackfire comparison link so we can see exactly whats going on.

mh thats not really an option, i profiled it within our proprietary application... ill create a dedicated comparison

Hey @shmax I have merged #308
@digitalkaoz would you please rebase this PR on master and resolve conflicts. I will approve/merge/bump once all is green.

@bighappyface ok rebased, should be all green in a few minutes!

@bighappyface should be green now

@shmax im getting some weird errors in my builds (which werent there before your merged PR) any idea where Undefined property: JsonSchema\Constraints\UndefinedConstraint::$schemaStorage comes from? cant find it anywhere in the code

@digitalkaoz per travis the stack for this warning is
1) JsonSchema\Tests\Constraints\AdditionalPropertiesTest::testInvalidCases with data set #0 ('{\n                  "prop":"1...     }', '{\n                  "type":"o...     }', null, array(array('', '', 'The property additionalProp i...erties', 'additionalProp')))

Undefined property: JsonSchema\Constraints\UndefinedConstraint::$schemaStorage

/home/travis/build/justinrainbow/json-schema/src/JsonSchema/Constraints/UndefinedConstraint.php:63
/home/travis/build/justinrainbow/json-schema/src/JsonSchema/Constraints/UndefinedConstraint.php:41
/home/travis/build/justinrainbow/json-schema/src/JsonSchema/Constraints/Constraint.php:181
/home/travis/build/justinrainbow/json-schema/src/JsonSchema/Constraints/SchemaConstraint.php:30
/home/travis/build/justinrainbow/json-schema/src/JsonSchema/Validator.php:36
/home/travis/build/justinrainbow/json-schema/tests/Constraints/BaseTestCase.php:41

there you go:
https://github.com/justinrainbow/json-schema/blob/master/src/JsonSchema/Constraints/UndefinedConstraint.php#L63

@staabm thanks. i had to rebase once more, should be fixed now

getting some weird errors in my builds

Ah, sorry about that--snuck another PR in there ahead of you. I don't have any more surprises, so happy merging...


move codecov config to root dir

Codecov Report

Merging #27 (3b693c9) into master (7b9ac26) will decrease coverage by 0.70%.
The diff coverage is 25.00%.

@@            Coverage Diff             @@
##           master      #27      +/-   ##
==========================================
- Coverage   69.47%   68.77%   -0.71%
==========================================
  Files           4        4
  Lines         249      253       +4
==========================================
+ Hits          173      174       +1
- Misses         61       63       +2
- Partials       15       16       +1

Impacted Files
Coverage Δ

pkg/vault/vault.go
70.11% <25.00%> (-2.18%)
:arrow_down:

Continue to review full report at Codecov.

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


Use Port Forwarding to Access Applications in a Cluster

https://kubernetes.io/docs/tasks/access-application-cluster/port-forward-access-application-cluster/
This guide using one of these playgrounds in place of having a real cluster

If you do not already have a cluster, you can create one by using minikube or you can use one of these Kubernetes playgrounds:
Katacoda
Play with Kubernetes

Did those writing the guides try the sandboxes suggested and see that they are actually able to run the commands within the sandbox environment?
None of them work for these purposes

Thanks for reporting the bug. There's a change in progress for the examples. This issue might duplicate with #28500 , and will be fixed once the PR #28530 is merged.

I believe this one has been resolved.
/close


Typo in Comparative Pathway Tool results page

To learn how to filer, sort, manipulate, refine, and save data within PATRIC feature tables,
"filer" should be "filter."

Well, this is somewhat systematically spread. I have fixed four different places and will deploy soon.
https://github.com/PATRIC3/patric3_website/commit/c13a9e38b763fd1b004b5001ad7aeff08243a4e5

available on production now.


Rework tabline for tabs and buffers

This PR is a continuation of #1684. It fixes #1468 (and the now-closed #488).
The main work is done in the new file (autoload/airline/extensions/tabline/builder.vim), which extends the interface defined in autoload/airline/builder.vim. The code uses new variables:

g:airline#extensions#tabline#overflow_marker - the symbol to show to the side of the tab/buffer titles when there are more that don't fit. This defaults to g:airline_symbols.ellipsis.
g:airline_symbols.ellipsis - this defaults to ...
g:airline#extensions#tabline#center_active - whether to show the active tab/buffer in the middle(-ish) of the tabline (as in #1674), or to the right. This defaults to 0 (keeping roughly the old behaviour for buffers).

Currently, this brings several improvements on the old version:

the tabline now scrolls when tabs are showing, so that the selected tab is always visible
it should be able to handle any dividers, even if they are different widths
it (tries to) expand the rest of the tabline to get the actual non-title contents

this makes supporting content around the titles much easier (e.g. for tabs)
this also means that the divider, ellipsis, etc. can be any expression and the spacing should still work

it supports tabs and buffers equally well, and they now use the same code (via the new class)
the currently active tab can be placed in the middle of the tabline (by setting g:airline#extensions#tabline#center_active to 1)

I've left it off by default to make this PR less disruptive; it would be simple to switch the default and/or remove the option completely if this is the way to go

There are a few limitations:

this code is much more complicated than the original and #1674
I haven't been able to find a nice way to include @ruipgpinheiro's formatting fix from #1674 yet
some of the expressions defined in :help 'statusline' aren't supported by the tabline expansion
the class doesn't handle splits next to/before the title list properly

these cases don't come up in the tabs/buffer code at the moment

Screenshots (tabs):

first tab

tab in the initial strip

tab in the middle

tab with long names (overflow)

tab in the final strip

last tab

let g:airline_powerline_fonts=1

wider terminal (g:airline#extensions#tabline#center_active=1)

wider terminal (g:airline#extensions#tabline#center_active=0)

dividers of different non-1 widths

Original:

tab not in the final strip

tab in the final strip

Screenshots (buffers):

first

middle

last

wide

Original:

cc/ @ruipgpinheiro

I think I'm finished with this. 4b1913a implements @ruipgpinheiro's formatting fix, and also reclaims the overflow marker's space if it's not going to be shown.

I have been using this PR for a while and I had no problems with it so far. Thank you, it is a really cool improvement! :+1:

I've pushed a couple of commits to 'fix' when the buffer code doesn't detect any buffers and/or the active buffer. The underlying bug is still there (and I'm not sure how/whether to fix it), but now the behaviour is always at least as good as master, and there are no errors.
To reproduce, open a Netrw buffer with vim /path/to/directory/. airline#extensions#tabline#buflist#list doesn't detect this buffer, and so the tabline has no titles to display. There is similar behaviour for different combinations of files and Netrw buffers; I think this should handle them all gracefully now.

Is this ready for being included now?

From my side, yes. I've been using it for the last 2 weeks and haven't hit any bugs (barring the one I fixed last night).
Obviously, I'm happy to make any changes that are needed before merge.

okay, let's merge it then.

Did this PR introduce the buffer counting from 0 instead of from 1?

Thanks @slabua, I've opened PR #1702 with a bugfix. Sorry for missing it in my tests.


FUTURES POSITION INFORMATION PROBLEM

Even though I have typed the symbol, I was unable to get the information on the precise pair. The response includes every pair that is in futures markets.
I can get the set value from a response list like writing response[0], still, it is just a temporary solution because the number represents the crypto changes constantly.

this repo use the old api /fapi/v1/positionRisk, this api not support the symbol argument
binance new api /fapi/v2/positionRisk support symbol, the this repo not update

Even though I have typed the symbol, I was unable to get the information on the precise pair. The response includes every pair that is in futures markets.
I can get the set value from a response list like writing response[0], still, it is just a temporary solution because the number represents the crypto changes constantly.

this repo use the old api /fapi/v1/positionRisk, this api not support the symbol argument
binance new api /fapi/v2/positionRisk support symbol, this repo need update


[Q]Delete organization

Hello, somehow my account has an organization and I cannot view and access to my personal project.
How can I fix this issue?

Hello @Moon1x21 , happy to help. Could you please provide your ORG name and WandB Username? And the Personal Project you are looking for. Thanks!

Thank you for respond! My user name is moonjooeun4741, and the ORG name is juneinoct. For the personal project, I cannot access to all of my personal project. I guess this is because my account is changed as an organization account.. Thanks!

Hi @Moon1x21 , our team made some recent changes and as of April 24, 2024, all new sign-up’s default entity are set to a team entity, and the personal entities are hidden as part of these new changes. Did you sign up after that date for W&B?

Hi @Moon1x21 , this issue has been fixed on our end. You should now be able to access your personal account as before. Please let us know in case of any further queries.


Refactor group settings code.

First commit is to fix the code being called unnecessary in a loop when it would be fine to just call it once.
Second commit is a small optmiziation for computing variables only if necessary.
Third commit is to extract a new function to avoid code duplicaton.
Fourth and Fifth commits are to optimize computing setting values in stream objects.
Sixth commit is to use common template for user group permission settings.
Last commit is to set up setting widgets using a loop.

Fixes:  Includes some follow-ups for #32361.

Self-review checklist

[ ] Self-reviewed the changes for clarity and maintainability
(variable names, code reuse, readability, etc.).

Communicate decisions, questions, and potential concerns.

[ ] Explains differences from previous plans (e.g., issue description).
[ ] Highlights technical choices and bugs encountered.
[ ] Calls out remaining decisions and concerns.
[ ] Automated tests verify logic where appropriate.

Individual commits are ready for review (see commit discipline).

[ ] Each commit is a coherent idea.
[ ] Commit message(s) explain reasoning and motivation for changes.

Completed manual review and testing of the following:

[ ] Visual appearance of the changes.
[ ] Responsiveness and internationalization.
[ ] Strings and tooltips.
[ ] End-to-end functionality of buttons, interactions and flows.
[ ] Corner cases, error conditions, and easily imagined bugs.

This is a great cleanup, merged, thanks @sahil839!


Use Path for file paths instead of FilePath

Using a more type safe path structure would likely benefit us in a few ways, so we should use
this instead

This is now closed as of the latest commit to master


The DefaultSubmodel has not default kind INSTANCE

When you create a ned DefaultSubmodel and call getKind() you will get null

@sebbader-sap This reminds me of the issue of setting default values for some properties as defined in the specification in the constructor which we discussed some time ago. I am quite sure you implemented this feature in the generator, however, the latest code generated does not seem to have this.
Has this functionality somehow been lost or disabled?

indeed. Most likely because my branch with this feature in the generator faced a lot of problems with the latest metamodel version, so I went back to a later state.

Or I expect default information in the ontology, which I have added manually to the aas-specs ontology... Don't remember.

see https://github.com/sap-contributions/aas4j/pull/3

Fixed with latest release milestone-04


How to bind a variable to the model?

Is your feature request related to a problem? Please describe.
I want to bind a variable(maybe a property in an object) and a field in model. I hope, when this variable changes, the field in model can change sync.
Additional context
The simple example, there only one input:
import {Component, OnInit} from '@angular/core';
import {FormGroup} from '@angular/forms';
import {FormlyFieldConfig, FormlyFormOptions} from '@ngx-formly/core';

@Component({
    selector: 'formly-app-example',
    templateUrl: './app.component.html',
})
export class AppComponent implements OnInit {
    form = new FormGroup({});
    model = {};
    options: FormlyFormOptions = {};
    fields: FormlyFieldConfig[] = [];

    dataBus = {
        value: 'value'
    }

    ngOnInit(): void {
        // I know this is wrong, but how can can I bind mode and this variable?
        this.model = {
            firstName: this.dataBus.value
        };
        this.fields = [
            {
                key: 'firstName',
                type: 'input',
                defaultValue: 'This is a default value',
                templateOptions: {
                    label: 'First Name (initialized via default value)',
                },
            }
        ];
    }

    update() {
        // When the value changes, I hope the mode changes sync
        this.dataBus.value = 'new value';
    }
}

@aitboudad Can you help? Thanks!!

Another simple scene，I want to update the value in a template, how can I do?

this.root_fields = [
    {
        template: '
Personal data
',
    },
    {
        className: 'span-desc',
        template: `<span>some text: ${this.updateText}</span>`,
    }
];

get updateText() {
    return this.dataBus.text;
}

sorry don't have too much time to check your request , see https://github.com/ngx-formly/ngx-formly/issues/2057#issuecomment-579724475

@aitboudad Thanks for your reply! By the way in #2057, now I can update the text in template.
When you have any time, can you help me see the first question? How to bind a variable to a field in the model.
Thank you very much!

@aitboudad Hello, please forgive me for asking again! It is because this problem blocked the development progress of our project.
I will waiting for your reply online. Thanks again!


The minimal value of history-max option

helm version:
version.BuildInfo{Version:"v3.6.3", GitCommit:"d506314abfb5d21419df8c7e7e68012379db2354", GitTreeState:"clean", GoVersion:"go1.16.5"}
kubectl version:
Client Version: version.Info{Major:"1", Minor:"22", GitVersion:"v1.22.1", GitCommit:"632ed300f2c34f6d6d15ca4cef3d3c7073412212", GitTreeState:"clean", BuildDate:"2021-08-19T15:45:37Z", GoVersion:"go1.16.7", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"22", GitVersion:"v1.22.1", GitCommit:"632ed300f2c34f6d6d15ca4cef3d3c7073412212", GitTreeState:"clean", BuildDate:"2021-08-19T15:39:34Z", GoVersion:"go1.16.7", Compiler:"gc", Platform:"linux/amd64"}

Cloud Provider/Platform (AKS, GKE, Minikube etc.): minikube
According to the helm document.
--history-max int              limit the maximum number of revisions saved per release. Use 0 for no limit (default 10)
So I assume the minimal value for history-max is 1. However, when I run command helm upgrade  -i --history-max 1 to install the chart more than 1 time, I realize the history length of that release is more than 1. The history-max 1 behavior is consistent with history-max 2.
helm history example -n <ns>
REVISION	UPDATED                 	STATUS    	CHART                	APP VERSION	DESCRIPTION
2       	Fri Sep 17 21:10:57 2021	superseded	xxx	1.0        	Upgrade complete
3       	Fri Sep 17 21:11:39 2021	deployed  	xxx	1.0        	Upgrade complete

This is working as intended. --history-max 1 will retain one release OTHER than the release currently deployed. This allows the user to issue a helm rollback. Helm must retain at least one revision to ensure a clean upgrade.