EKF testing gaps

Overall test coverage is looking good, but there are still a number of gaping holes.

airspeed_fusion.cpp 68.67% https://codecov.io/gh/PX4/ecl/src/master/EKF/airspeed_fusion.cpp
drag_fusion.cpp 0% https://codecov.io/gh/PX4/ecl/src/master/EKF/drag_fusion.cpp
mag_control.cpp 78.15% https://codecov.io/gh/PX4/ecl/src/master/EKF/mag_control.cpp

explicitly test modes other than MAG_FUSE_TYPE_AUTO

optflow_fusion.cpp 0% https://codecov.io/gh/PX4/ecl/src/master/EKF/optflow_fusion.cpp
sideslip_fusion.cpp 0% https://codecov.io/gh/PX4/ecl/src/master/EKF/sideslip_fusion.cpp

Testing the different height modes is another missing piece.

Good to know, thanks @dagar . I'll add a task for myself to remember adding basic coverage of those functions. Also, if anyone else is interested to do it, he/she's more than welcome!


[WIP] github/ci: Add CI reporting

cc @krajshiva - this still needs a bit of upstream work but shouldnt take long


[Decommission Hub] allen-swdb

Summary
Confirmed the request for decommission on this comment: https://github.com/2i2c-org/infrastructure/issues/1440#issuecomment-1252551218
Info

Community Representative: @mabuice
Link to New Hub issue: https://github.com/2i2c-org/infrastructure/pull/1585
Proposed end date: Oct 3rd 2022

Task List
Phase I

[x] Confirm with Community Representative that the hub is no longer in use and it's safe to decommission
[ ] Confirm if there is any data to migrate from the hub before decommissioning

[ ] If yes, confirm where the data should be migrated to

[ ] Confirm a 2i2c Engineer has access to the destination in order to complete the data migration

[ ] If no, confirm it is ok to delete all the data stored in the user home directories

Phase II - Hub Removal
(These steps are decribed in more detail in the docs at https://infrastructure.2i2c.org/en/latest/howto/hubs/delete-hub.html.)

[ ] Manage existing data (migrate data from the hub or delete it)
[ ] Remove the appropriate config/clusters/<cluster_name>/<hub_name>.values.yaml files. A complete list of relevant files can be found under the appropriate entry in the associated cluster.yaml file.
[ ] Remove the associated hub entry from the config/clusters/<cluster_name>/cluster.yaml file.
[ ] Remove the hub deployment

helm --namespace HUB_NAME delete HUB_NAME
kubectl delete namespace HUB_NAME

[ ] Delete the hub's authentication application on auth0, GitHub or CILogon

Phase III - Cluster Removal
This phase is only necessary for single hub clusters.

[ ] Run terraform plan -destroy and terraform apply from the appropriate workspace, to destroy the cluster
[ ] Delete the terraform workspace: terraform workspace delete <NAME>
[ ] Remove the associated config/clusters/<cluster_name> directory and all its contents
Remove the cluster from CI:

[ ] deploy-hubs.yaml
[ ] validate-clusters.yaml

[ ] Remove the cluster from the list of grafana datasources at https://grafana.pilot.2i2c.cloud/datasources
[ ] Remove A record from Namecheap account

@mabuice, can you please confirm the following two items:

Confirm with Community Representative that the hub is no longer in use and it's safe to decommission (double checking because of protocol :wink:).
Confirm if there is any data to migrate from the hub before decommissioning

@mabuice, just a gentle reminder about confirming the items I asked about above. Thanks!

I also assigned this decommission to @yuvipanda since he is going to finish and merge #1585 before the decommission actually happens 😉.

@damianavila I think everything is good.  It's ok to decommission.  Sorry for the late response.
Thanks for everything; this was great.

Thanks for confirming, @mabuice! This will destroy all user data in their home directories irretrievably, hope that's ok :)
Decomission will happen whenever https://github.com/2i2c-org/infrastructure/pull/1736 is reviewed and merged.

It is gone now!

Just FYI, I noticed the GitHub OAuth apps and Namecheap entries for this hub are hanging around, so I will clean those up

so I will clean those up

Thanks @sgibson91!


WFLY-18457 Eliminate new ThreadGroup creation in connector, naming modules

https://issues.redhat.com/browse/WFLY-18457
Follow-up PR with couple of additional cases.

Thanks @TomasHofman, @tadamski and @ropalka


Race condition when initializing variables in control_dependencies

System information
== cat /etc/issue ===============================================
Darwin Mikes-MBP.enversion.com 16.7.0 Darwin Kernel Version 16.7.0: Mon Nov 13 21:56:25 PST 2017; root:xnu-3789.72.11~1/RELEASE_X86_64 x86_64
Mac OS X 10.12.6

== are we in docker =============================================
No

== compiler =====================================================
Apple LLVM version 9.0.0 (clang-9<IP_ADDRESS>)
Target: x86_64-apple-darwin16.7.0
Thread model: posix
InstalledDir: /Library/Developer/CommandLineTools/usr/bin

== uname -a =====================================================
Darwin Mikes-MBP.enversion.com 16.7.0 Darwin Kernel Version 16.7.0: Mon Nov 13 21:56:25 PST 2017; root:xnu-3789.72.11~1/RELEASE_X86_64 x86_64

== check pips ===================================================

== check for virtualenv =========================================
False

== tensorflow import ============================================
tf.VERSION = 1.8.0
tf.GIT_VERSION = v1.8.0-0-g93bc2e2072
tf.COMPILER_VERSION = v1.8.0-0-g93bc2e2072
Sanity check: array([1], dtype=int32)

== env ==========================================================
LD_LIBRARY_PATH is unset
DYLD_LIBRARY_PATH is unset

== nvidia-smi ===================================================
tf_env_collect.sh: line 105: nvidia-smi: command not found

== cuda libs  ===================================================

Describe the problem
Given how Variable and control_dependencies are documented, I would expect the following to work:
with tf.Session() as sess:
    v = tf.Variable(tf.zeros([100,100]))
    with tf.control_dependencies([v.initializer]):
        d = tf.Print(v, [v])
    print(sess.run(d))

But this seems to create a race condition. Sometimes it executes fine, sometimes it errors with FailedPreconditionError: Attempting to use uninitialized value Variable. It is unclear to me if the use of initializers in control_dependencies is valid. If it is not, the documentation should probably better reflect this.
Source code / logs
Full traceback:
Traceback (most recent call last):
  File "/usr/local/lib/python3.6/site-packages/tensorflow/python/client/session.py", line 1322, in _do_call
    return fn(*args)
  File "/usr/local/lib/python3.6/site-packages/tensorflow/python/client/session.py", line 1307, in _run_fn
    options, feed_dict, fetch_list, target_list, run_metadata)
  File "/usr/local/lib/python3.6/site-packages/tensorflow/python/client/session.py", line 1409, in _call_tf_sessionrun
    run_metadata)
tensorflow.python.framework.errors_impl.FailedPreconditionError: Attempting to use uninitialized value Variable
         [[Node: Variable/read = Identity[T=DT_FLOAT, _class=["loc:@Variable/Assign"], _device="/job:localhost/replica:0/task:0/device:CPU:0"](Variable)]]

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "test.py", line 105, in <module>
    print(sess.run(d))
  File "/usr/local/lib/python3.6/site-packages/tensorflow/python/client/session.py", line 900, in run
    run_metadata_ptr)
  File "/usr/local/lib/python3.6/site-packages/tensorflow/python/client/session.py", line 1135, in _run
    feed_dict_tensor, options, run_metadata)
  File "/usr/local/lib/python3.6/site-packages/tensorflow/python/client/session.py", line 1316, in _do_run
    run_metadata)
  File "/usr/local/lib/python3.6/site-packages/tensorflow/python/client/session.py", line 1335, in _do_call
    raise type(e)(node_def, op, message)
tensorflow.python.framework.errors_impl.FailedPreconditionError: Attempting to use uninitialized value Variable
         [[Node: Variable/read = Identity[T=DT_FLOAT, _class=["loc:@Variable/Assign"], _device="/job:localhost/replica:0/task:0/device:CPU:0"](Variable)]]

Caused by op 'Variable/read', defined at:
  File "test.py", line 101, in <module>
    v = tf.Variable(tf.zeros([100,100]))
  File "/usr/local/lib/python3.6/site-packages/tensorflow/python/ops/variables.py", line 235, in __init__
    constraint=constraint)
  File "/usr/local/lib/python3.6/site-packages/tensorflow/python/ops/variables.py", line 397, in _init_from_args
    self._snapshot = array_ops.identity(self._variable, name="read")
  File "/usr/local/lib/python3.6/site-packages/tensorflow/python/ops/array_ops.py", line 142, in identity
    return gen_array_ops.identity(input, name=name)
  File "/usr/local/lib/python3.6/site-packages/tensorflow/python/ops/gen_array_ops.py", line 3187, in identity
    "Identity", input=input, name=name)
  File "/usr/local/lib/python3.6/site-packages/tensorflow/python/framework/op_def_library.py", line 787, in _apply_op_helper
    op_def=op_def)
  File "/usr/local/lib/python3.6/site-packages/tensorflow/python/framework/ops.py", line 3392, in create_op
    op_def=op_def)
  File "/usr/local/lib/python3.6/site-packages/tensorflow/python/framework/ops.py", line 1718, in __init__
    self._traceback = self._graph._extract_stack()  # pylint: disable=protected-access

FailedPreconditionError (see above for traceback): Attempting to use uninitialized value Variable
         [[Node: Variable/read = Identity[T=DT_FLOAT, _class=["loc:@Variable/Assign"], _device="/job:localhost/replica:0/task:0/device:CPU:0"](Variable)]]

Thank you for your post. We noticed you have not filled out the following field in the issue template. Could you update them if they are relevant in your case, or leave them as N/A? Thanks.
Have I written custom code
OS Platform and Distribution
TensorFlow installed from
TensorFlow version
Bazel version
CUDA/cuDNN version
GPU model and memory
Exact command to reproduce

It has been 16 days with no activity and the awaiting response label was assigned. Is this still an issue?

It has been 14 days with no activity and the awaiting response label was assigned. Is this still an issue?


Better error messages when the jest environment is used after teardown by async code

🚀 Feature Proposal
Provide better errors when async code uses the environment after the test suite finished executing. Something like "This method can't be called because the test suite has finished running. This can happen if you forget to return a promise from a test method that performs asynchronous operations."
Motivation
I just spent a while debugging the following issue:
Cannot read property 'runAllTimers' of null
TypeError: Cannot read property 'runAllTimers' of null
    at Object.runAllTimers (/Users/bernie/Documents/GitHub/amara-checkout/node_modules/jest-runtime/build/index.js:969:56)

Caused by a jest.runAllTimers(); in my code. Turns out, this method calls this._environment.fakeTimers.runAllTimers(), and _environment.fakeTimers was null because the environment had been torn down, because the test suite had finished executing.
The root cause was that I'd omitted an await before an async method in a test, and the test method itself was not async.
It would be great to be able to offer an error message that pointed the user to the source of the issue.
Example
n/a
Pitch
Why does this feature belong in the Jest core platform?
It's a tweak to help people use existing functionality correctly.

I'm not likely to have time for a PR in the next month, but I may return to
it if nobody else has picked it up by then.
Since I've been looking through the source I'll leave this thought here for
me or someone else: In terms of implementation, I'd think that on teardown
we could iterate over the properties of the jestObject and replace all
functions with a function that throws an error. That seems more reasonable
than adding conditions in all the places where the code could fail as a
result of the environment being torn down.
On Thu, 4 Oct 2018 at 09:25, Simen Bekkhus<EMAIL_ADDRESS>wrote:

Yeah, that makes sense! We've added similar errors for require after
teardown (#5888 https://github.com/facebook/jest/pull/5888). Wanna send
a PR for it? The code lives in jest-runtime
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/facebook/jest/issues/7099#issuecomment-426929331, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAzNSA3oxkPP1yW_l1mJCdl8qiD5K9vCks5uhcXpgaJpZM4XHjcn
.

Hello, me and another student are trying to fix this issue for a course in college. However, it's our first time working with jest so we are not so sure which files to run to reproduce this issue... Can you please replecate it in repl.it?

I can give a quick start, though.
The relevant code lives here: https://github.com/facebook/jest/blob/b502c07e4b5f24f491f6bf840bdf298a979ec0e7/packages/jest-runtime/src/index.js#L922-L963
WHat you need to do is add a guard around every access on this._environment that throws an explicit error that the environment has already been torn down. You can look at how I solved it in #5888 to get an idea how the error message could look like.
Should probably have a _getTestEnvironemt function that does e.g.
if (this._environment) {
  return this._environment;
}

throw new PrettyError();

What I would do in this case is create an integration test - the setup and teardown of a unit test at this level is quite involved and brittle IMO. Again, I'd like to point you to #5888 (although, not that integrations-tests directory has been renamed to just e2e since that).
File under test: https://github.com/facebook/jest/blob/053b74128d7dbff8ad423e85ff45ea167c23f192/e2e/require-after-teardown/tests/late-require.test.js
Test: https://github.com/facebook/jest/blob/053b74128d7dbff8ad423e85ff45ea167c23f192/e2e/tests/require_after_teardown.test.js
Instead of doing const double = require('../'); you can do e.g. jest.runAllTimers(); (see the repl.it link I provided above). Jest should then throw the PrettyError you create.
Our contributing guide has some more information on how to write and run integrations tests: https://github.com/facebook/jest/blob/053b74128d7dbff8ad423e85ff45ea167c23f192/CONTRIBUTING.md#integration-tests
Does that answer your question?

After creating a test folder and trying  to reproduce locally the error we got this error. Do you know what's happening?

Btw, we also tried with the link in the repl but there is no build folder in jest-runtime.
Thank you for the help!!

@ritanorinho Don't know if you're still stuck, but that happens because node is run on a non-transpiled file. Try to run yarn build in the jest root and you should get a build folder in jest-runtime.


[BUG]

Minecraft, modloader and mod versions
Example:
Minecraft: 1.20.1
Forge: 47.3.10
Soulslike-Weaponry: <IP_ADDRESS>d
Describe the bug
Crashes on Launch because dependency Projectile Damage Attribute is not the right version. Projectile Damage Attribute has a updated version 3.2.3, and soulslike requires 3.2.2. Can this be updated for the new version of Projectile Damage Attribute?
Add logs
-- MOD soulsweapons --
Details:
Mod File: /D:/Minecraft Instances/Mystic Horizons/minecraft/mods/soulslike-weaponry-<IP_ADDRESS>d-1.20.1-forge.jar
Failure message: Mod soulsweapons requires projectile_damage 3.2.2+1.20.1
Currently, projectile_damage is 3.2.3+1.20.1
Mod Version: <IP_ADDRESS>d-1.20.1-forge}
Mod Issue URL: NOT PROVIDED
Exception message: MISSING EXCEPTION MESSAGE
To Reproduce
Steps to reproduce the behavior:

Launch the game with Soulslike Weaponry and Projectile Damage 3.2.3

Expected behavior
Minecraft is able to launch.
Screenshots and videos
If relevant, add screenshots or videos to help explain your problem. For example: a video of you attempting to use a weapon that doesn't work.
Other mods or relevant info
Write down mods you are using you think could cause the issue due to conflicting code or incompatibility.

No, the last time I tested the newest version of projectile damage, it was unstable and crashed the game. As of now, I will force it to use 3.2.3 until I find this issue resolved.


Create GH Pages Branch

Create a branch for GitHub Pages, which will be used to host prototypes and documentation, and include a single index.html placeholder.

Set up at https://planettelex.github.io/Songtracker-Pro/ using the Cayman theme,


Baum abonnieren - feedback onClick

If I click "Baum abonnieren", I'd like to gelt a little Feedback that something actually happened (i.e. the button flashing for a second or something like that)

Baum Abonnieren has now intermediate state on click


harden build

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Comparison is base (5475794) 75.69% compared to head (1a1eccf) 75.69%.
Report is 1 commits behind head on main.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff            @@
##               main      #85   +/-   ##
=========================================
  Coverage     75.69%   75.69%
  Complexity      225      225
=========================================
  Files            14       14
  Lines          1728     1728
  Branches        166      166
=========================================
  Hits           1308     1308
  Misses          340      340
  Partials         80       80

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Fix search results

This branch is already merged into develop. Due to today's GitHub outage (https://www.githubstatus.com/incidents/f0mhbz9xn497), it is not recognized as merged in the web interface, so I'm closing this here.


Bug Bounty

Problem
No link to bug bounty in docs
Solution
Can we add a link under Support & Community to the Hedera Bug Bounty.
https://hedera.com/bounty
Alternatives
No response

Edit Title

The bug bounty link was added to docs.


refactor(secondary-nav): token values and focus fix

What I did

Removed component scaling with user font size preference by replacing em based spacers with space tokens.
Updated font-family stacks with font tokens
Fixed nav bar height not adjusting when logo text wraps to 3 lines
Fixed button background on color-palette="darker"
Fixed focus out handler bug closing menu when clicking on flyout menu

Testing Instructions

View the netlify demo link.  Adjust browser font-size preference, only fonts should scale.
Click / tab around menu make sure menu opens and closes appropriately

Notes to Reviewers
Please double-check any design spec spacing mistakes with XD specs for user error in copying/changing values to token usage.

@zeroedin
One tiny thing, the Menu text is Display instead of Text on small breakpoints.

One tiny thing, the Menu text is Display instead of Text on small breakpoints.

Good catch.  Fixed in https://github.com/RedHat-UX/red-hat-design-system/pull/515/commits/548ba52a32fe9765b7193ab38ea016696e367c1b


test: lint and add tests for helmfile move

Signed-off-by: ankitm123<EMAIL_ADDRESS>

/cc @msvticket @tomhobson @babadofar

It complicates things unnecessarily  that you opened a PR for the same part of the code as #850. I think you should close this and then we can cooperate on #850.

Also I don't what is so bad in needing JX_NO_KUBERNETES=true, where there is already KUBECONFIG=/cluster/connections/not/allowed.

It complicates things unnecessarily that you opened a PR for the same part of the code as https://github.com/jenkins-x-plugins/jx-gitops/pull/850

There were some linting issues as well, which were seen in another PR, I am ok closing this one (let's just copy over the tests and lint fixes)

Also I don't what is so bad in needing JX_NO_KUBERNETES=true,

I dont see the point in using this variable for unit tests. With JX_NO_KUBERNETES, we are not testing parts of the code which are easily tested using the kubernetes fake client (as demonstrated in this PR). Also there have been discussions around moving away from github actions, so this function should be eventually removed imo cc @tomhobson
(apart from codeql and may be codecov, dont see a point in using github actions - testing jx with jx is the right way to go - the v2 way 😬)

But if someone wants to use jx version in their github action then I don't see why we should prevent them from doing that.

In that case, we should have 2 test cases - one with JX_NO_KUBERNETES and one where we test the kubernetes part (using the fake client)

I dont see the point in using this variable for unit tests. With JX_NO_KUBERNETES, we are not testing parts of the code which are easily tested using the kubernetes fake client (as demonstrated in this PR).

Actually this PR demonstrates that it is not easy to test, since the test passes while in reality the code failed in the bdd tests.

Actually this PR demonstrates that it is not easy to test, since the test passes while in reality the code failed in the bdd tests.

That is because we only have one test case - only test the happy path (hence in draft mode) - I would like to replicate the bdd test failure using unit tests tbh (I will search the logs).


Insomnia removes accept header on its own!

I can't type anything in Accept header as it removes it on its own. very annoying!

Insomnia 2020.3.0
MacOS 10.15.5

Hi! Thanks for the report, this has been fixed in 2020.3.3 - please update your client 😄


[Explore]modal cancel button should come before the save button

Screenshot

Description
The "SAVE" button should be the last button in the footer of the modal, just after the "CANCEL" one to make it consistent with the other modals in the project.

I'll be fixing this one @junlincc

I'll be fixing this one @junlincc

please make sure changes apply to both edit and change dataset modal in Explore. thanks! @geido

please make sure changes apply to both edit and change dataset modal in Explore. thanks! @geido

@junlincc it looks like the Change Dataset modal already has the buttons in the right position when you pick a new dataset. Is there anything else you are looking to change?

@junlincc it looks like the Change Dataset modal already has the buttons in the right position when you pick a new dataset. Is there anything else you are looking to change?


Come up with a catchy tag line / description

Slim:

A lightweight templating engine.
Slim is a template language whose goal is reduce the syntax to the essential parts without becoming cryptic.

Jade:

Jade - robust, elegant, feature rich template engine for Node.js

HAML:

Beautiful, DRY, well-indented, clear markup: templating haiku.

In addition to a catch phrase I'd like to come up with a single logo.

That'd be great!

Are we aiming for catchy or informative? Not sure any of those examples are catchy as such :)
If we want to go for informative, maybe something like: "Minimalistic HTML templates for Elixir, inspired by Slim."

Just spitballing:

Tasty templates

Slimed down templates in Elixir

The no-fluff stuff

Less markup, more remarkable

Ooze drippin' good

;)

"Minimalistic HTML templates for Elixir, inspired by Slim."

Works for me.

Updated the project description: "Minimalistic HTML templates for Elixir, inspired by Slim."


Search SDK: Add tests for Lucene regex query

Can one of the admins verify this patch?

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

It looks like you're working at Microsoft (nateko). If you're full-time, we DON'T require a contribution license agreement.

If you are a vendor, DO please sign the electronic contribution license agreement. It will take 2 minutes and there's no faxing! https://cla.azure.com.

TTYL, AZPRBOT;

LGTM 👍


Added a simple onboarding screen.

PR for Adding an Onboarding screen #6
I have used the flutter_card_swipper: ^0.4.0 to create a swiping onboarding screen.
Also, set it as home in main.dart so it opens up first when user starts the app.
Let me know if any changes are required to the description.
Video
https://user-images.githubusercontent.com/53579386/123071211-16266380-d432-11eb-86bc-ff206ea0e788.mp4

I deleted the .flutter-plugins and .flutter-plugins-dependencies so they wouldn't merge on main.


TypeScript: Rename refactoring stops at destructured objects

VSCode Version: 1.1.0-insider
OS Version: Windows 8.1 x64

Steps to Reproduce:

Destructure an object of some known TS class or interface
Rename a member in the class or interface that is referenced in the destructuring statement

Expect: The destructured member name to be updated to matched the renamed symbol
Get: The destructured member is not updated, causing a TS compilation error
See attached gif

This seems to be fixed in VSCode 1.7.2:

import * as React from 'react';

interface IFooProps {
    name: string
    message: string
}

class Foo extends React.Component<IFooProps, any> {
    constructor(props) {
        super(props)
    }

    render(): JSX.Element {
        const {name, message} = this.props
        return <div>{message}</div>
    }
}

Please give a more recent build a try and let me know if you still see this issue.
Thanks

Can confirm it is fixed on current VSCode (1.7.2). Thanks.


Add support for multiple directory levels within stacks

Summary
Add support for multiple directory levels within stacks
Motivation
At some point, having a lot of stacks becomes cumbersome. And some of the stacks are describing similar problems. Just by grouping them in a directory would solve a lot of headaches. Is this possible by tweaking the load paths?
Reference-level explanation
|--app
    |--modules
    |--stacks
        |--dirA
            |--stackA1
            |--stackA2
        |--dirB
            |--stackB1

etc.
Unresolved Questions
It may already be possible to tweak the load path, but I haven't been able to find the documentation on this.

Is multiple levels of directories supported for modules now? Because if not then same thing should be done for modules too.

Totally agree it will help alot organising stack folders with many files. Thanks lot

+1 for this.

+1 for this. We divide our repo per team and some teams have access to their subfolders only. It would turn a lot easier to configure the permissions on that folders for us.
I can run something like terraspace new stack infrastructure/backup/databases and it creates all the folders. But if I use terraspace fmt it doesn't do in cascade, it does only in the top-level folder.


added PowerVC specific flavor settings in REQUIRED_ADVANCED_SETTINGS

These new settings are required for the PowerVC Plugin.

/enhancement

@Kuldip-Nanda that's a lot of new virtual_columns, are you using all of these in reporting?  If so they probably shouldn't be in advanced settings and if not they don't need to be added here
cc @Fryguy

Yeah, as we had discussed, I'm fine with a small handful, but this is a lot.  These should be considered on their utility (80/20 rule on whether the user actually cares about any of this stuff).  If it's mostly used for ad-hoc visualization, maybe it makes more sense to send them to the real dashboard.

I am withdrawing and closing this PR as these settings are not going to be part of Virtual Settings.


An existing connection was forcibly closed by the remote host

I am using Google.Cloud.Storage.V1  version 2.3.0 to upload file from Azure windows VM behind firewall to GCS. I am getting exception "An existing connection was forcibly closed by the remote host".
Code and authentication setting was following this guide.
https://cloud.google.com/storage/docs/reference/libraries#client-libraries-install-csharp
It has been tested working on local and some servers, but not the Azure VM I was trying.
This VM is able to telnet www.googleapis.com 443.
What could be missing here?
System.Net.Http.HttpRequestException: An error occurred while sending the  request. ---> System.Net.WebException: The underlying connection was  closed: An unexpected error occurred on a send. --->  System.IO.IOException: Unable to read data from the transport connection:  An existing connection was forcibly closed by the remote host. --->  System.Net.Sockets.SocketException: An existing connection was forcibly  closed by the remote host    at System.Net.Sockets.Socket.EndReceive(IAsyncResult asyncResult)    at System.Net.Sockets.NetworkStream.EndRead(IAsyncResult asyncResult)    --- End of inner exception stack trace ---    at System.Net.TlsStream.EndWrite(IAsyncResult asyncResult)    at System.Net.ConnectStream.WriteHeadersCallback(IAsyncResult ar)    --- End of inner exception stack trace ---    at System.Net.HttpWebRequest.EndGetRequestStream(IAsyncResult  asyncResult, TransportContext& context)    at System.Net.Http.HttpClientHandler.GetRequestStreamCallback(IAsyncResult ar)    --- End of inner exception stack trace ---    at Google.Cloud.Storage.V1.StorageClientImpl.UploadHelper.CheckFinalProgress() in T:\src\github\google-cloud-dotnet\releasebuild\apis\Google.Cloud.Storage.V1\Google.Cloud.Storage.V1\StorageClientImpl.UploadObject.cs:line 202    at Google.Cloud.Storage.V1.StorageClientImpl.UploadHelper.Execute() in T:\src\github\google-cloud-dotnet\releasebuild\apis\Google.Cloud.Storage.V1\Google.Cloud.Storage.V1\StorageClientImpl.UploadObject.cs:line 154    at Google.Cloud.Storage.V1.StorageClientImpl.UploadObject(String bucket, String objectName, String contentType, Stream source, UploadObjectOptions options, IProgress1 progress) in T:\src\github\google-cloud-dotnet\releasebuild\apis\Google.Cloud.Storage.V1\Google.Cloud.Storage.V1\StorageClientImpl.UploadObject.cs:line 70`

Thanks for reporting the issue. Could I ask a few more questions?

What operating system is the VM? (I'd like to be able to reproduce it.)
Can you give a brief description of the firewall configuration?
Does this happen for every API call, or just upload? (For example, are you able to list the contents of a bucket?)
Are you able to use curl or wget to make a test call? If so, something like this would be interesting:
wget -O- https://www.googleapis.com/storage/v1/b/storage-library-test-bucket/o

@jskeet
This Azure VMScaleset VM running Windows Server 2012 R2.
The application is built on .Net Framework 4.7.2.
The firewall implementation was requested to IT as following
source VMScaleSet IP range
destination www.googleapis.com
port 443.
After IT implemented firewall rules, I am able to telnet www.googleapis.com 443 on VM successful.
The upload method is first call to Google API in the application. I am not sure whether other API call will fail. I don't have much freedom to deploy test app on company's VM Scaleset to try. But by running wget https://www.googleapis.com/storage/v1/b/storage-library-test-bucket/o in powershell on one VM, I am able to get following result.
StatusCode        : 200 StatusDescription : OK Content           : {                       "kind": "storage#objects",                       "items": [                         {                           "kind": "storage#object",                           "id": "storage-library-test-bucket/Café/1490385877705600",                           "selfLink": "https://www.googleapis.com/storag... RawContent        : HTTP/1.1 200 OK                     X-GUploader-UploadID: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx                     Vary: Origin,X-Origin                     Alt-Svc: quic=":443"; ma=2592000; v="4... Forms             : {} Headers           : {[X-GUploader-UploadID, xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx], [Vary,                      Origin,X-Origin], [Alt-Svc, quic=":443"; ma=2592000; v="46,43",h3-Q050=":443"; ma=2592000,h3-Q049=":443"; ma=2592000,h3-Q048=":443";                      ma=2592000,h3-Q046=":443"; ma=2592000,h3-Q043=":443"; ma=2592000], [Content-Length, 2690]...} Images            : {} InputFields       : {} Links             : {} ParsedHtml        : System.__ComObject RawContentLength  : 2690

It might be worth trying to add storage.googleapis.com to the firewall as well. Certainly in the future that's where Storage requests will go anyway; I wouldn't expect it to be used right now, but it's just possible that it might be. (The upload initially requests another URL to use for storing the data - if the server is responding with a storage.googleapis.com, that would probably explain things.)
If that doesn't help, are you able to check the firewall logs? I'd expect attempts to break out of the firewall to be logged, and that could tell us what's going on, potentially.

Ah - I've just thought of something else that could be the problem. It may be while it's trying to get an authentication token. If you can open up access to oauth2.googleapis.com and accounts.google.com, that might help. (I suspect you'd only need one of them, but I'm not sure which right now.)

I am also able to telnet accounts.google.com 443, and telnet oauth2.googleapis.com 443. Those are two URLs in service account key json file, I assume they will be called behind scene by the nuget package.

Yes, the auth happens automatically. Hmm, I'm still confused. Anything in the firewall logs?

it's very challenge for me to access firewall log with our company structure.
I noticed this stackoverflow question claimed different exception threw at same line.
https://stackoverflow.com/questions/55967800/upload-files-to-google-cloud-storage-using-c-sharp
He said port 80 need to be opened. Do you aware any of that?
The other thing I noticed, there is one line in stack trace "at System.Net.TlsStream.EndWrite(IAsyncResult asyncResult)". Could this be a TLS issue?

That Stack Overflow questions says that ports 80 and 443 were blocked - it doesn't say that port 80 needed to be opened. I wouldn't expect port 80 to be needed at all.
I suspect the error is happening during TLS negotiation, but I doubt it's specifically a TLS error... unless you've reconfigured .NET in terms of the TLS versions it supports?

In C# code, we don't specify System.Net.ServicePointManager.SecurityProtocol, so default will be used.
On our Azure VM, server protocols have TLS 1.1 and TLS 1.2 enabled. Client protocols have TLS 1.0, TLS 1.1 and TLS 1.2 enabled.
My understanding is google side support TLS 1.0, 1.1 and 1.2. Not sure what could impact TLS negotiation.

The only time I've seen anything else similar to this was when there was DOS prevention being applied due to huge amounts of traffic from a single VM. Given that this is the first request of the app, I suspect it's not the same. I'm puzzled, and not sure what to do next, to be honest.

Just noticed that actually VM was able to process one document successfully, which is good news. The weird thing is same VM failed processing next document with exception "An existing connection was forcibly closed by the remote host".
Here is additional background info, our application gets deployed on Azure VM ScaleSet. Individual VM from VM ScaleSet pick up documents from queue one at a time, upload that document to GCS, then OCR the document.
For two documents I mentioned, here is the timing
First doc went successful
"StartTime": "2019-11-12T14:44:03.9868338Z",
"EndTime": "2019-11-12T14:44:08.0655703Z"
Second doc failed with exception
"StartTime": "2019-11-12T14:44:08.5014281Z",
"EndTime":  "2019-11-12T14:44:08.7983091Z"
Here is the code to upload document
`
private readonly StorageClient _storage;
public GoogleStorage(string googleProjectId)
{
_projectId = googleProjectId;
_storage = StorageClient.Create();
}
public void UploadObjectFromStream(Stream stream, string bucketName, string objectName, string encryptionKey = null)
{
_storage.UploadObject(bucketName, objectName, null, stream,
new UploadObjectOptions()
{
EncryptionKey = (encryptionKey == null) ? null : EncryptionKey.Create(
Convert.FromBase64String(encryptionKey))
});
}`

The upload code looks fine. I wouldn't expect any problems using the same service key on multiple VMs.
What are the constraints in terms of running diagnostic code? It sounds like things are - entirely reasonably - locked down fairly tightly in your production environment. Do you have a test environment where you can test a little more freely? If there's somewhere you can run arbitrary console applications so we can do more testing, that would be really helpful, but I understand if that's not possible. Aside from anything else, I'd be interested to see if you get the same result using just gsutil to do the upload. That would clarify whether the problem is somewhere in the .NET stack (whether in our library or lower down) or in the network configuration on the VM.

This isn't looks like this client library's problem anymore.
I ran invoke-webrequest in powershell on our Azure VM to reach our GCS bucket, passing access token in header, I got same error message as C# code. The powershell script works on my local.

Exception             : System.Net.WebException: The underlying connection was closed: An unexpected error occurred on a send. ---> System.IO.IOException: Unable to
read data from the transport connection: An existing connection was forcibly closed by the remote host. ---> System.Net.Sockets.SocketException:
An existing connection was forcibly closed by the remote host
at System.Net.Sockets.Socket.EndReceive(IAsyncResult asyncResult)
at System.Net.Sockets.NetworkStream.EndRead(IAsyncResult asyncResult)
--- End of inner exception stack trace ---
at System.Net.TlsStream.EndWrite(IAsyncResult asyncResult)
at System.Net.ConnectStream.WriteHeadersCallback(IAsyncResult ar)
--- End of inner exception stack trace ---
at Microsoft.PowerShell.Commands.WebRequestPSCmdlet.GetResponse(WebRequest request)
at Microsoft.PowerShell.Commands.WebRequestPSCmdlet.ProcessRecord()
TargetObject          : System.Net.HttpWebRequest
CategoryInfo          : InvalidOperation: (System.Net.HttpWebRequest:HttpWebRequest) [Invoke-WebRequest], WebException
FullyQualifiedErrorId : WebCmdletWebResponseException,Microsoft.PowerShell.Commands.InvokeWebRequestCommand
ErrorDetails          :
InvocationInfo        : System.Management.Automation.InvocationInfo
ScriptStackTrace      : at , : line 31
PipelineIterationInfo : {}
PSMessageDetails      :

I tried force to use security protocol to Tls1.2, with [Net.ServicePointManager]::SecurityProtocol = [Net.SecurityProtocolType]::Tls12, same error.
Also tried  [Net.ServicePointManager]::SecurityProtocol = [Net.SecurityProtocolType]::Tls -bor [Net.SecurityProtocolType]::Tls11 -bor [Net.SecurityProtocolType]::Tls12, same error.
I have no idea what else to try.
I'll engage with our IT team see if they know anything about this.
Thanks for your help.

Right - thanks very much for the update. I agree, it's very odd - best of luck with your IT team. I'll close this issue now, but please do add another comment if you'd like it reopened when you have more information.


fix(string): use minlength on arbitraries

Current dependencies on/for this PR:

main

PR #43   👈

This comment was auto-generated by Graphite.


Update introduction.rst

Added brackets to Swift_Message instantiation

On some other places around the docs the brackets are missing too.

@pYr0x, thank you. Created another PR here https://github.com/swiftmailer/swiftmailer/pull/931

Good catch, thanks @chshanovskiy.


add vertex itself to nodes' neighborhood in PSCAN

the neighborhood of each node in PSCAN should cantain itself.

Hi,
Thank you for your pull request.
Is that change somehow justified by PSCAN  paper? Adding vertex itself will change computation results. What is more, there will be no difference between a graph with self-loops and without.

The neighborhood of a vertex is defined in the paper of SCAN:

DEFINITION 1 (VERTEX STRUCTURE)
Let v ∈ V, the structure of v is defined by its neighborhood,
denoted by Γ(v)
Γ(v) = {w ∈ V | (v,w) ∈ E} ∪ {v}
In Figure 1 vertex 6 is a hub sharing neighbors with two clusters.
If we only use the number of shared neighbors, vertex 6 will be
clustered into either of the clusters or cause the two clusters to
merge. Therefore, we normalize the number of common neighbors
by the geometric mean of the two neighborhoods’ size.

If vertex itself  is not contained, similarities of all node pair will be less than the true value.
For example, if two connected vertices have no common neighbors, the similarity will be 0. Which is the same as node pairs which are not connected by an edge.

Awesome. Please fix the compilation issues and the tests then I will be able to merge the pull request.

Sorry I find it hard to compile sparking in my computer, maybe you can manage to fix this pls.

Ok,  please raise an issue for that, I will close pull request because I will be not able to merge it that way.

OK. I will raise an issue.


Show score IA vs Human

Show amount of time the human won
Show amount of time the ia won

@TiagoDanin can i take this one, ?


Ensure file system ACLs of all files/directories are consistent with the type and state of data.

Once data are uploaded, they pass through various states (upload, ingest, processing, QA, publication) and move to various locations on the file system. We want to ensure that file access controls are consistent with HuBMAP policy and best practices each time a change of state or location occurs.
See here for current policy:
https://docs.google.com/document/d/1pE-XxWVWhUHMQapTzX_VbUXHmYm7gRanMWG6BGEiXks/edit

Puppet code written to manage ACLs.
I'm making a replica data tree (same directory layout, same permissions, all data replaced with random 4K data files). This tree will test validation and correction as well as measuring performance. (The current filesystem makes this a very expensive operation, so gathering the "cost" will permit us to propose a run frequency.)

Passed along proposed ACL setup (promoting hubmap and hubseq to Unix GID permissions and other minor tweaks) as well as a script that should be run daily/weekly (depending on how long it takes to complete). It's a security consideration given the protected information, so it is recommended to do this as a backup.
Notes were collected (including copy-and-pastes of the source files) in this doc.


cmd/go: go mod init should be able to specify go/toolchain version

What version of Go are you using (go version)?

go version go1.21rc2 darwin/arm64

What did you do?
Programmatically create a new module with a specified go version and toolchain.
What did you expect to see?
Something like:
go1.21rc2 mod init -go=1.19 -toolchain=1.19 example.com/foo
What did you see instead?
No new flags.
Context
As someone who creates a lot of module programmatically it would be nice if these things could be specified from the command line as they affect how the module can be used. I could post process these files but that seems like something that should be able to be specified up front.
In particular the go version seem very important to be able to specify given its new constraints it applies in 1.21+.

I agree that both of these do work but that don't seem like the best user experience imo. If this is the desired experience I feel like it should be documented in go help mod init. But if the point of the mod sub-commands is being able to edit the go.mod files it feels like it should be able to initialize/edit all parts of the file without outside environment/commands being used.

It feels unintuitive for mod init to create a go.mod it won't natively run.
GOTOOLCHAIN=go1.x go mod init uses the target toolchain to create the go.mod, matching later behavior when in runs in the newly created module

go mod init is intended to get you into a minimal (default) initial state. go get is used to select versions of things.
So I don't think go mod init should have the side-effect of selecting a non-default language or toolchain version.

go mod init is intended to get you into a minimal (default) initial state

I could see this being true for trying to keep it as simple as possible. Just feels odd that I can not get the state I want things in with a single command. Using go get seems fair for setting the go version(although I think this could be documented better) but since you can also declare the toolchain in mod files it seems like there should an similar command for setting the toolchain. Is there a way I am missing?

So I don't think go mod init should have the side-effect of selecting a non-default language or toolchain version.

If there were a flag I would not consider this a side-effect but an explicit handling of what the user wants.

since you can also declare the toolchain in mod files it seems like there should an similar command for setting the toolchain. Is there a way I am missing?

go get<EMAIL_ADDRESS>

Whoops! I obviously did not read https://go.dev/doc/toolchain closely enough. I had tried a similar command but had left out the go in the version. Since there is a way to edit these programmatically I suppose this is good enough for my use case. Thanks for the clear explanation. I will close this out for now but I do think there may be a docs issue in here somewhere. Maybe some examples in the go help mod?!


differential analysis

add valcano to the peptide level.

ma plot VS volcano plot, DESeq2 package, more data visualization ideas from this package: https://www.bioconductor.org/packages/release/bioc/vignettes/cummeRbund/inst/doc/cummeRbund-manual.pdf


Fix ghosting artifacts

What does the pull request do?

Fixes the bug as described in #1687; This will unblock #987 for future implementation.

What is the current behavior?

Immediate and Deferred Renderers doesn't clear the scene context in the proper way, hence the bug's manifestation.

Checklist:

[ ] Added unit tests (if possible)?
[ ] Added XML documentation to any related classes?
[ ] Consider submitting a PR to https://github.com/AvaloniaUI/Avaloniaui.net with user documentation

Fixes #1687
Courtesy of @nc4rrillo , Thanks pal! :smile:

LGTM

@jmacato For Direct2D the backbuffer currently has a pixel format which ignores the alpha mode. This is why you're seeing white where you should see transparent.
You need to change AlphaMode to Premultiplied in SwapChainRenderTarget

@grokys @nc4rrillo any more requested changes here?

@jkoritzinsky I think @jmacato told me this was causing input issues. I need to boot back into Windows to check.


Autocomplete not working on mobile devices

Why this plugin is not working on any mobile device, hasn't anyone faced the same issue?

Relate to https://github.com/caroso1222/amazon-autocomplete/issues/13. Demo works fine on mobile now.


DOMError is captured as [object DOMError]

Do you want to request a feature or report a bug?
bug
What is the current behavior?
When a DOMError is thrown, raven-js logs the error as '[object DOMError]' without any proper messaging. reference: https://github.com/getsentry/raven-js/blob/b8afab1d156467cb2cca0a166385fe9a94aff2cb/dist/raven.js#L413
What is the expected behavior?
The DOMError interface is not actually an instance of Error or an Exception and does not include a stacktrace. Since it doesn't pass the isError check, it's converted to a string and is re-thrown.
Our expected behavior would be to pull out the name property and throw/log as DOMError: ${error.name}, so we can have as much context on the error as possible.
Which versions of Raven.js, and which browser and OS are affected by this issue?
Pretty much every version of both.
Did this work in previous versions of Raven.js?
No
Are you using the CDN (http://ravenjs.com)?
No
Are you using hosted Sentry or on-premises?
Hosted

This is sort of related to #879 - there are a couple situations where we're relying on Object.prototype.toString and either

could be formatting things better (here we get [object DOMError])
blow up when passed an object without a prototype (bad case in #879)

We resolved this in raven-node by using node's util.format, but would need to add an implementation of something similar to raven-js to use the same strategy.
The other possibility for this case in particular is that we should make isError return true when passed a DOMError, but I don't personally understand everything about what makes a DOMError special or what the resulting captureException behavior would be.

So I did some digging on this and I think what we should do is:

Not worry about tackling the bigger picture #879/util.inspect problem here; out-of-the-box util.inspect impls are too big and it's not pressing enough to take on making a thinner/stripped down alternative
Stop special-casing DOMException to pass isError like we started doing in #919 :/
Have some special logic in captureMessage for doing a nicer string formatting of DOMException/DOMErrors along the lines of what you suggested

Regardless of what we actually do, we should try to treat DOMError and DOMException the same way (see "Remarks"](https://msdn.microsoft.com/en-us/library/hh968254(v=vs.85).aspx)), which we're not currently doing. This is sort of tricky because a DOMException is instanceof Error in Chrome, Firefox, Safari but not in Edge or IE. Also, '' + (new DOMException('hi')) gives us "Error: hi" whereas '' + (new DOMError('hi')) just gives "[object DOMError]" as you've observed; we can construct "DOMException: hi" and "DOMError: hi" instead.
Note that we don't re-throw when failing the isError check, we just hand it off to captureMessage where we'll make a synthetic stack trace. If we instead made it pass isError, we won't get a stack trace at all (which is currently the case for DOMException).
So right now, DOMExceptions get a reasonable message but no stack, and DOMErrors get a reasonable stack but no message. We can make both get both.
/cc @graingert - considering reverting #919 because we actually don't get a stack trace for DOMExceptions right now, but we would make a synthetic trace if a DOMException failed isError. Curious if you have thoughts.
Alternative path is to make DOMErrors also pass isError and try to go from there.
/cc @benvinegar

Realized this also relates to #360.

@LewisJEllis I'm okay with special casing DOMException and DOMError rather than, say, JSON-ifying all non-Error-Error objects.

Bump. I get a lot of reports about this error, which occurs only in Safari (iOS/OSX).

@kamilogorek unfortunately, I cannot reproduce the error that occurs in my case. I tried partially to implement this commit https://github.com/getsentry/raven-js/pull/1181/files#diff-a4cb6d8063a6aea4bba2d6f10472b5f4R461 on my project for debugging, but when someone throws this error, JSON.stringify() for [object DOMError] says that this object is empty (json {}).
  captureMessage: function(msg, options) {
      // Convert the message into a string
      var exceptionMessage;
      if (typeof msg === 'object' && msg !== null) {
          exceptionMessage = '' + msg + ': ' + JSON.stringify(msg); // <--
      } else {
          exceptionMessage = '' + msg;
      }
   // ...

    var data = objectMerge(
      {
        message: exceptionMessage
      },
      options
    );

Stacktrace here: https://sentry.io/share/issue/602b3ae3524a4450a80033bfb4b437c6/

Addressed in https://github.com/getsentry/raven-js/pull/1310
Will publish patched version by the end of the week.

Released as 3.25.0

Thanks @kamilogorek!


TPC-H Q13 and Q22

What type of PR is this? (check all applicable)

[ ] 💾 Refactor
[ ] ✨ Feature
[ ] 🐛 Bug Fix
[ ] 🔧 Optimization
[ ] 📝 Documentation
[ ] ✅ Test
[ ] 🐳 Other

Related issues

Related issue #
Closes #

Checklist

[ ] Code follows style guide (ruff)
[ ] Tests added
[ ] Documented the changes

If you have comments or can explain your changes, please do so below.

thanks @ugohuche ! the title says q13 and q22, but you've added a lot more than that - just checking if this was intentional?

Yes that's intentional. I think the other ones it's showing are former commits I've made from this branch which have been merged earlier.

cool thanks - could you do
git fetch upstream
git rebase upstream/main
git push origin HEAD -f

please? that should fix the diff


BUG: Footer logo not functional

The recode hive logo on the footer must redirect the user back to the top. Please let me work on this issue for GSSOC-EXTD. Thanks!

redirect to the home page


compiler warnings mess around with the cursor

Another placeholder issue like #322 — I've seen the cursor jump around in Chrome when there's invalid code in the editor
https://user-images.githubusercontent.com/1162160/230144511-5937a4bc-20ae-4890-8993-08b7d7810e69.mov

This will no longer occur if either of the following is commented out.
https://github.com/sveltejs/learn.svelte.dev/blob/5cc3d078d098a4cf436509c69cdb4b5044655c7f/src/routes/tutorial/[slug]/Editor.svelte#L40
https://github.com/sveltejs/learn.svelte.dev/blob/5cc3d078d098a4cf436509c69cdb4b5044655c7f/src/routes/tutorial/[slug]/Editor.svelte#L133
I found a similar issue to this in the discuss of Codemirror.
https://discuss.codemirror.net/t/bizarre-tab-diagnostic-interaction/5207


feat: add BitVec.toInt_[pos|neg]iff_toNat[large|small]

Feedback on proper naming is much appreciated.

awaiting-review


UTIL Question

any idea how i can include the util position to be  included with the stack?
SAMPLE IS 4 PLAYERS BUT USE UTIL FOR THAT STACK

HI @Denwen12. By default, it does include it in the stack. I did a test run for a 4x3 stack and got correct stacks using the UTIL position.

Oh ok
On Sat, Apr 16, 2022, 12:06 PM Benika @.***> wrote:

HI @Denwen12 https://github.com/Denwen12. By default, it does include
it in the stack. I did a test run for a 4x3 stack and got correct stacks
using the UTIL position.
—
Reply to this email directly, view it on GitHub
https://github.com/DimaKudosh/pydfs-lineup-optimizer/issues/359#issuecomment-1100698298,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ANBWO7UBWBIRX5I2LE5R3ADVFLQRRANCNFSM5TR3H7IQ
.
You are receiving this because you were mentioned.Message ID:
@.***>

For instance,
optimizer.add_stack(TeamStack(4, for_positions = ['1B', '2B', '3B', 'SS', 'OF'],max_exposure =.30))  optimizer.add_stack(TeamStack(3, for_positions = ['1B', '2B', '3B', 'SS', 'OF'],max_exposure =.30))
worked fine for me.  I also tested it with GameStack function and the UTIL position was part of the stack.
Were there any other constraints in your code?

how could one go about forcing a certain position into that UTIL spot?
like only allow C/1B and OF only in all lineups?


Link to the tutorial inside the Wiki is broken

https://github.com/drom/wavedrom/wiki/WaveJSON
has a link which is broken

Probably pointing to both https://wavedrom.com/tutorial2.html and https://wavedrom.com/tutorial.html would be beneficial.

Wiki is significantly outdated. I fixed links to the tutorial.


Issue With Latest Home Assistant Firmware 2021.5.0b5

This issue has occurred which stops Alarmo from Starting up when you look at the page it just shows up as loading and doesn't ever load. In the integration page, it says the error failed to set up. I am on the latest Alamo Version. I love this addon it is amazing. If it is just me having this issue I will reinstall it to see if it makes a difference.
This error originated from a custom integration.
Logger: homeassistant.config_entries
Source: custom_components/alarmo/card.py:37
Integration: Alarmo (documentation, issues)
First occurred: 6:28:49 (1 occurrences)
Last logged: 6:28:49
Error setting up entry Alarmo for alarmo
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/config_entries.py", line 269, in async_setup
result = await component.async_setup_entry(hass, self)  # type: ignore
File "/config/custom_components/alarmo/init.py", line 77, in async_setup_entry
await async_register_card(hass)
File "/config/custom_components/alarmo/card.py", line 37, in async_register_card
hass.data[DATA_EXTRA_MODULE_URL].update(url_set)
AttributeError: 'UrlManager' object has no attribute 'update'
and I also get this error
Logger: homeassistant.components.websocket_api.http.connection
Source: components/websocket_api/connection.py:87
Integration: Home Assistant WebSocket API (documentation, issues)
First occurred: 6:42:52 (5 occurrences)
Last logged: 6:50:19
[139795058424608] Received invalid command: alarmo/users

I think you need to update to v1.5.7 (which was released 2 days ago).
This error suggests you don’t have the latest changes yet

That was it. Sorry To bother you. For some reason, it didn't show up that it needed an update but I did find the latest version and it is working perfectly.


add makefile, and flags to pass options to rebuild index, set custom path, multiple extentions

Thanks for the changes, I think I messed up something and added the commit to a new PR. I will merge that close this one.


Update to work with current wrangler

Thanks for your great wrangler script! It works great, I have added a few changes and fixes to update everything to the current version and compatibility.
I have also made some changes to the default config as I think it would be more applicable to people who just want to upload and forget it. All the changes have comments in the github diff.

Hello @s-crypt! Thank you so much for sharing this!
I'm glad it works for you and that you find the script useful
I'll be happy to merge the changes of course ;-)

Haha, great!
Again, thanks a lot!


confused by device placement on Amazon AWS

First - loving tensorflow.  The tutorials were really great fun to read.   Tensorflow API architecture is clear and amazing.   Hope to do pull requests once I get up to speed.
However, I'm trying to do device placement to do some basic benchmarks to see if it's worth using Amazon at all versus my own computers.  So far, not so promising, but maybe I'm doing something wrong.
From the example here:  http://tensorflow.org/how_tos/using_gpu/index.md
I get the following results.

>>> with tf.device('/cpu:0'):
...   a = tf.constant([1.0, 2.0, 3.0, 4.0, 5.0, 6.0], shape=[2, 3], name='a')
...   b = tf.constant([1.0, 2.0, 3.0, 4.0, 5.0, 6.0], shape=[3, 2], name='b')
...   sess = tf.Session(config=tf.ConfigProto(log_device_placement=True))
...   print sess.run(c)
...
I tensorflow/core/common_runtime/gpu/gpu_device.cc:644] Creating TensorFlow device (/gpu:0) -> (device: 0, name: GRID K520, pci bus\
 id: 0000:00:03.0)
Device mapping:
/job:localhost/replica:0/task:0/gpu:0 -> device: 0, name: GRID K520, pci bus id: 0000:00:03.0
I tensorflow/core/common_runtime/direct_session.cc:111] Device mapping:
/job:localhost/replica:0/task:0/gpu:0 -> device: 0, name: GRID K520, pci bus id: 0000:00:03.0

b: /job:localhost/replica:0/task:0/cpu:0
I tensorflow/core/common_runtime/simple_placer.cc:289] b: /job:localhost/replica:0/task:0/cpu:0
a: /job:localhost/replica:0/task:0/cpu:0
I tensorflow/core/common_runtime/simple_placer.cc:289] a: /job:localhost/replica:0/task:0/cpu:0
MatMul_1: /job:localhost/replica:0/task:0/gpu:0
I tensorflow/core/common_runtime/simple_placer.cc:289] MatMul_1: /job:localhost/replica:0/task:0/gpu:0
[[ 22.  28.]
 [ 49.  64.]]

Looking at that, it looks like it's placing the matmul on the gpu.   I want it on the cpu.  Is that possible?
Also, is matrix_inverse or matmul of say a 5000x5000 matrix a good (but very rough!) benchmark to help evaluate the value of Amazon GPU/CPU large instances?
Thanks again

In your code, it doesn't look like you wrapped the declaration of 'c' within the 'with tf.device()' block, so it doesn't have a device assigned to it.  Because we have an implementation of matmul on GPU, we automatically place the op on GPU.
I bet if you moved  c = tf.matmul(a, b) into the with block,it would probably do wht you expect.
As for the benchmark: GPUs are generally good for large matrix multiplies, so it's not a bad benchmark, but it depends on what you intend to use TensorFlow for.  The best benchmark is a real application :)

Great stuff, vrv.  That was the issue.
So, following that matmul only works for matricies up to 3000x3000 size or so.  I guess that's fine.  However, it doesn't seem to work at all for Matrix Inverse.  Is this just not supported yet?  https://developer.nvidia.com/sites/default/files/akamai/cuda/files/Misc/mygpu.pdf
tensorflow.python.framework.errors.InvalidArgumentError: Cannot assign a device to node 'MatrixInverse_9': Could not satisfy explicit device specification '/gpu:0'

Yeah, matrix inverse has not yet been implemented for GPU, so when you say 'run this on GPU', we can't find an implementation for it and we return that error.

Ok, awesome!   Thanks.   I assume I just need to look at ~/tensorflow/tensorflow/core/kernels/gpu for a list of the gpu supported operations.   I'll work with that.  List looks really exciting.  :D

Ok, I think this is the list.
$ ls gpu | grep -v cwise
adjust_contrast_op_gpu.cu.cc
aggregate_ops_gpu.cu.cc
argmax_op_gpu.cu.cc
avgpooling_op_gpu.cu.cc
batch_norm_op_gpu.cu.cc
bias_op_gpu.cu.cc
cast_op_gpu.cu.cc
check_numerics_op_gpu.cu.cc
concat_op_gpu.cu.cc
constant_op_gpu.cu.cc
conv_ops_gpu.cu.cc
conv_ops_gpu_2.cu.cc
conv_ops_gpu_3.cu.cc
conv_ops_gpu_matmul.cu.cc
dense_update_ops_gpu.cu.cc
l2loss_op_gpu.cu.cc
matmul_op_gpu.cu.cc
maxpooling_op_gpu.cu.cc
maxpooling_op_gpu.h
pad_op_gpu.cu.cc
pooling_ops_common_gpu.h
random_op_gpu.cu.cc
reduction_ops_gpu.cu.cc
relu_op_gpu.cu.cc
reverse_op_gpu.cu.cc
reverse_sequence_op_gpu.cu.cc
slice_op_gpu.cu.cc
softmax_op_gpu.cu.cc
softplus_op_gpu.cu.cc
split_op_gpu.cu.cc
tile_ops_gpu.cu.cc
training_ops_gpu.cu.cc
transpose_op_gpu.cu.cc
xent_op_gpu.cu.cc
Let me know if you want some assist with the docs.  Happy to do a pull request in whatever format you'd like.  Cheers

Those are the list of the files, but some of those files have multiple op implementations in them.
I would love to be able to automatically generate the list of implemented ops for each platform so they don't go out of date.  Maybe one day soon I'll get to doing this :)

(should have a separate feature request for this)


bug: '...valid provider configuration...' error throwing, causing minified bundle in Next to break due to mixing quote style

Is there an existing issue for this?

[X] I have searched the existing issues

Package Version
0.7.4
Current Behavior
App logic breaks, but builds pass due to invalid minification of the wagmi/core bundle. This however could be a bug upstream with next's SWC minification when it comes to processing mixed quote styles. CC'ing @leerob
Expected Behavior
Throwing the error with mixed quote styles flowing correctly into a single string as the logic defines.
Steps To Reproduce
Next.js build with Wagmi ran in production
Link to Minimal Reproducible Example (CodeSandbox, StackBlitz, etc.)
No response
Anything else?

Attached is the patch-package diff.
diff --git<EMAIL_ADDRESS><EMAIL_ADDRESS>index ea7f281..ac3ba3b 100644
---<EMAIL_ADDRESS>+++<EMAIL_ADDRESS>@@ -60,7 +60,7 @@ function configureChains(defaultChains, providers) {

     if (!configExists) {
-      throw new Error([`Could not find valid provider configuration for chain "${chain.name}".\n`, "You may need to add `jsonRpcProvider` to `configureChains` with the chain's RPC URLs.", 'Read more: https://wagmi.sh/docs/providers/jsonRpc'].join('\n'));
+      throw new Error([`Could not find valid provider configuration for chain "${chain.name}".`, `You may need to add "jsonRpcProvider" to "configureChains" with the chain's RPC URLs.`, `Read more: https://wagmi.sh/docs/providers/jsonRpc`].join('\n'));
     }
   }

diff --git<EMAIL_ADDRESS><EMAIL_ADDRESS>index f663fd0..fe763ca 100644
---<EMAIL_ADDRESS>+++<EMAIL_ADDRESS>@@ -60,7 +60,7 @@ function configureChains(defaultChains, providers) {

     if (!configExists) {
-      throw new Error([`Could not find valid provider configuration for chain "${chain.name}".\n`, "You may need to add `jsonRpcProvider` to `configureChains` with the chain's RPC URLs.", 'Read more: https://wagmi.sh/docs/providers/jsonRpc'].join('\n'));
+      throw new Error([`Could not find valid provider configuration for chain "${chain.name}".`, `You may need to add "jsonRpcProvider" to "configureChains" with the chain's RPC URLs.`, `Read more: https://wagmi.sh/docs/providers/jsonRpc`].join('\n'));
     }
   }

diff --git<EMAIL_ADDRESS><EMAIL_ADDRESS>index aa7f69d..0248a19 100644
---<EMAIL_ADDRESS>+++<EMAIL_ADDRESS>@@ -54,7 +54,7 @@ function configureChains(defaultChains, providers) {

     if (!configExists) {
-      throw new Error([`Could not find valid provider configuration for chain "${chain.name}".\n`, "You may need to add `jsonRpcProvider` to `configureChains` with the chain's RPC URLs.", 'Read more: https://wagmi.sh/docs/providers/jsonRpc'].join('\n'));
+      throw new Error([`Could not find valid provider configuration for chain "${chain.name}".`, `You may need to add "jsonRpcProvider" to "configureChains" with the chain's RPC URLs.`, `Read more: https://wagmi.sh/docs/providers/jsonRpc`].join('\n'));
     }
   }

@tmm

I can seem to deploy a wagmi app to Vercel fine (reference repository – deployed site). Do you mind sharing a minimal reproducible repository like mine so we can investigate further – are you passing custom chains/providers in? I can re-open the issue when provided!

@jxom seems there's some issue with swcMinify with my setup, with it disabled this is not a problem. Can't seem to replicate with the same sort of setup with your reference repo, unsure of the reason. My guess is its an upstream issue.
Something is causing the "You may need to add jsonRpcProvidertoconfigureChains w... bit to not escape the ` properly when swcMinify is enabled.
Sorry for the issue!

Hey @jxom @mirshko I had the same issue and created a reproducible repo and deployment website 👇
https://wagmi-next-template-lymktdvd1-tomoima525.vercel.app/
https://github.com/tomoima525/wagmi-next-template/pull/1 (Reproducible branch)
This seems to happen in 12.1.x and below versions of Next.js in conjunction with swcMinify option. I think we can ignore the issue as it's specific to the older version of Next.js


fix LogConfig for containers created before docker 1.12 on daemon start

- What I did
Fix #22536
- How I did it
#21153 rewrite the LogConfig of the container at create time to merge the daemon default log config to the container's LogConfig. It also removed some redundant log driver validations.
But the LogConfig.Type of the container is empty if it was created before docker 1.12 with default log driver. This caused the containers that were created before docker 1.12 with default log driver can't start after upgrade to 1.12. See #22536
Ths PR merges the daemon log config to the container's log config at daemon startup if the container's LogConfig.Type is empty.
- How to verify it

Create a container with docker 1.11 and don't specify th --log-driver argument.
Upgrade to docker 1.12-dev
Check if the container can be started under docker 1.12-dev

- Description for the changelog

- A picture of a cute animal (not mandatory but encouraged)
…rtup
Signed-off-by: Shijiang Wei<EMAIL_ADDRESS>

LGTM

Hm, looks like there's a change in behavior in 1.12, possibly caused by https://github.com/docker/docker/pull/21153 that causes containers to not follow the daemon configuration after they have been created.
In docker 1.11;
$ docker daemon -D &
$ docker run -dit --name foobar busybox
$ docker inspect --format "{{ .HostConfig.LogConfig.Type }}" foobar
json-file

$ docker daemon -D --log-driver=syslog &
$ docker inspect --format "{{ .HostConfig.LogConfig.Type }}" foobar
syslog

In 1.12-dev, the second inspect still outputs json-file, so it appears containers persist the logging-driver that the daemon used when they were created.

@thaJeztah could you help to test this as well?
$ docker daemon -D &
$ docker run -dit --name foobar --log-opt max-file=5 busybox
$ docker start foobar

$ docker daemon -D --log-driver=syslog &
$ docker start foobar

(I'm on mobile now)

On current master, inspect output for both is;
{"Type":"json-file","Config":{"max-file":"5"}}

And the container starts
On docker 1.11, inspect after restarting docker gives;
{"Type":"syslog","Config":{"max-file":"5"}}

strangely, if allows to start that container, and doesn't complain, so it may be docker inspect being wrong there.
Will try with your branch now

With your branch, the container also starts, so it probably uses json-file, as the inspect output says.

@thaJeztah I think the behavior of switch the daemon's log-driver with existing containers is somewhat buggy in docker 1.11. The log-opt of the container seems to be ignored after changing the daemon log-driver.

@mountkin yes, I'm actually leaning towards not allowing --log-opt, unless a driver is specified on the same "level". Currently, for example, it's possible to only set --max-file on a container, which works because json-file is the default, but if the daemon configuration is changed, that will break the container (so upon a daemon restart / reload, containers won't come up again).
For now, it should really be: "container-config = daemon-config + container-config", where container-config overrides daemon options. But it should pick up the current daemon configuration, not the options that were set when the container was created (I think)

I'm actually leaning towards not allowing --log-opt, unless a driver is specified on the same "level".

@thaJeztah that will be a breaking change :smile:  I often use --log-opt without specifying --log-driver.

that will be a breaking change

Yes, I know, so probably not a change we can make. I also understand the convenience of just providing the options you want to change, but it would take all the "guesswork" out of it, and give a more predictable result.

@mountkin @thaJeztah where we here? Should we move to design review?

sorry for the delay; let's do this.
I tested this by creating a container, stopping the daemon, and editing the hostconfig.json, then starting the daemon again, it correctly set json-file in the hostconfig.json.
LGTM


Add CameraGroup Example

Hey, I've been working on a project with Pyglet and ended up writing a new camera system using the graphics group functionality instead of the existing camera example.
I've cleaned up the code and put it into a new example file so others can use it themselves.
The example also includes a "centered" version and a small demo.
I believe this is easier to use and is a bit more minimal compared to the existing example, but I have left the current one as it is right now.
Let me know if there is anything I should change, thanks!

Thanks Lenny, more examples are always good!
I have a similar Group-based camera that I use for parallax effects in side-scrolling games. Maybe we should move the camera examples into the window/ folder, and I can add mine as well?

Yeah that might be a good idea, I'll move them now :+1:


Links are working now with minor changes in code.

Related Issue
Links are working now with minor changes in code.
Description
[Please include a brief description of the changes or features added]
Type of PR

[ ] Bug fix
[ ] Feature enhancement
[ ] Documentation update
[ ] Other (specify): _______________

Screenshots / videos (if applicable)
[Attach any relevant screenshots or videos demonstrating the changes]
Checklist:

[ ] I have performed a self-review of my code
[ ] I have read and followed the Contribution Guidelines.
[ ] I have tested the changes thoroughly before submitting this pull request.
[ ] I have provided relevant issue numbers, screenshots, and videos after making the changes.
[ ] I have commented my code, particularly in hard-to-understand areas.

Additional context:
@arghadipmanna101 solved issue no #1038 plz merge my pr under gssoc24 label.

Work in the present website.

i am working but still giving error

i sync ur website and then use command git pull to ensure updates but giving error while mergeing pr


[Bug]: The Bot's LLM takes only the first document content embeddings from the Vectra data sources when multiple documents are uploaded

Language
Javascript/Typescript
Version
latest
Description
If I upload multiple documents and then ask question related to the last document was uploaded, the Bot LLM returns the response as if only the first document was used as RAG embedding in the response.
Here are the steps to recreate this issue:

Upload the first document and ask any questions related to that document.
Bot will correctly respond with the answer related to the first document content.
Upload the second document containing the different content from the first document and ask any question related to the second document.
Bot will think my question was related to the first document, and therefore the LLM response most likely will be inaccurate.

Additionally, here are some screenshots to illustrate this issue:

Note: the first document is uploaded containing the product invoice from CONTOSO.

This was the result came from analyzing the first document. It shows accurate invoice from CONTOSO.
Now, let's upload the second document, and ask Bot to find the founders (the document contain the Tesla company profile information):

The result came as following:

Here you can see that LLM didn't correctly recognize that the document containing company profile was already uploaded and added to Vectra Local Index.
To help with the debugging logs, here's the debugging output of the functions argument when the async completePrompt(context, memory, functions) function is called in planners/LLMClient.js from planners/ActionPlanner's completePrompt() method:

Here you can see that _data property contains the array of 4 elements, which are embeddings generated by Vectra Local Index containing the 2 copies of the first document and 2 copies of the second document.
Reproduction Steps
1. Upload the first document and ask any questions related to that document.
2. Bot will correctly respond with the answer related to the first document content.
3. Upload the second document containing the different content from the first document and ask any question related to the second document.
4. Bot will think my question was related to the first document, and therefore the LLM response most likely will be inaccurate.
...

@Stevenic could you comment?

@dannygar sorry for the delay. Are these PDF's? I can't see the screenshots but one thing that can happen with PDF's is you could be trying to import an "image only" PDF. Have you verified that you're actually extracting text from these other documents?

Closing due to lack of response.


[4.3-stable]Changing the Boot Splash background color does not reflect in the web export

Tested versions
Godot_v4.3-stable_win64
System information
Windows 10 Pro - Godot_v4.3-stable_win64 - Compatibility
Issue description
Changing the Boot Splash background color does not reflect in the web export. I even tried to Run directly from the Editor but same result. (Run in Browser).
or Export Web build and Check Background
Steps to reproduce
Project Settings -> Application -> Boot Splash -> BG Color -> Set any Color
This change project.godot -> boot_splash/bg_color=Color(1, 0, 0, 1)
Run directly from Editor but same result.
Minimal reproduction project (MRP)
bootsplashbgcolor.zip

At this point, the HTML template changed in 4.3 only supports boot splash image. Expansion to include more parameters from the application/boot_splash setting will require adding more variables passed during export.
For now, I can suggest changing the background using CSS style inside Head Include field, for example:
<style>
#status { background-color: red; }
</style>

or even more fancy:
<style>
#status { background: radial-gradient(circle, rgba(15,15,121,1) 0%, rgba(25,224,56,1) 100%); }
</style>


Upgrade to<EMAIL_ADDRESS>

What are you trying to accomplish with this PR?
Continuation of this PR
The point of PR #899 was to update the slate-tools package's dependencies to include node-sass 4.10.0, but, as @t-kelly pointed out, node-sass 4.11.0 is a stable release and is probably more reliable.
Please provide a link to the associated GitHub issue.
#778
Checklist
For contributors:

[ ] I have updated the docs to reflect these changes, if applicable.

For maintainers:

[ ] I have :tophat:'d these changes.

Thanks!


scipy.optimize.minimize with method=SLSQP does not minimize successfully

Hi, hopefully I'm actually doing something wrong with jax or scipy here, but...
import jax.numpy as np
import numpy as onp
from scipy.optimize import minimize

def run(np):
    def rosen(x):
        return np.sum(100.0 * (x[1:] - x[:-1] ** 2.0) ** 2.0 + (1 - x[:-1]) ** 2.0)

    x0 = np.array([1.3, 0.7, 0.8, 1.9, 1.2], dtype='float32')
    bounds = np.array([[0.7, 1.3]] * 5)
    return minimize(rosen, x0, method='SLSQP', options={'ftol': 1e-9, 'disp': True})

print(run(onp).x)
print(run(np).x)

This example has the following output:
Optimization terminated successfully.    (Exit mode 0)
            Current function value: 7.969820110544395e-11
            Iterations: 29
            Function evaluations: 221
            Gradient evaluations: 29
[0.999999   0.99999821 0.9999967  0.99999373 0.9999876 ]
/Users/kratsg/.virtualenvs/pyhf/lib/python3.7/site-packages/jax/lib/xla_bridge.py:130: UserWarning: No GPU/TPU found, falling back to CPU.
  warnings.warn('No GPU/TPU found, falling back to CPU.')
Optimization terminated successfully.    (Exit mode 0)
            Current function value:<PHONE_NUMBER>679688
            Iterations: 1
            Function evaluations: 7
            Gradient evaluations: 1
[1.29999995 0.69999999 0.80000001 1.89999998 1.20000005]

where:

numpy: [0.999999   0.99999821 0.9999967  0.99999373 0.9999876 ]
jax.numpy: [1.29999995 0.69999999 0.80000001 1.89999998 1.20000005]

I do not understand why (1) the results are different and (2) why there are so few iterations for jax.numpy case. I suspect this is what's causing differences in the minimization result.
NB: I got this example from scipy docs https://docs.scipy.org/doc/scipy/reference/tutorial/optimize.html#nelder-mead-simplex-algorithm-method-nelder-mead
/cc @lukasheinrich @matthewfeickert (affects diana-hep/pyhf#377)

Thanks for asking this, and the beautiful runnable example!
I think the issue is just 64bit vs 32bit. JAX by default maxes out at 32bit values for ints and floats. We chose that as a default policy because a primary use case of JAX is neural network-based machine learning research. That's different from ordinary NumPy, though, which is very happy to cast things to 64bit values. In fact, that's why we made 32bit the system-wide maximum precision by default: because otherwise users might get annoyed by the NumPy API promoting things to 64bit values all the time, when they're trying to stay in 32bit for neural net training!
To enable 64bit values, I ran your script like this:
$ JAX_ENABLE_X64=1 python issue936.py
Optimization terminated successfully.    (Exit mode 0)
            Current function value: 7.96982011054e-11
            Iterations: 29
            Function evaluations: 221
            Gradient evaluations: 29
[0.999999   0.99999821 0.9999967  0.99999373 0.9999876 ]
/usr/local/google/home/mattjj/packages/jax/jax/lib/xla_bridge.py:130: UserWarning: No GPU/TPU found, falling back to CPU.
  warnings.warn('No GPU/TPU found, falling back to CPU.')
Optimization terminated successfully.    (Exit mode 0)
            Current function value: 7.96982011054e-11
            Iterations: 29
            Function evaluations: 221
            Gradient evaluations: 29
[0.999999   0.99999821 0.9999967  0.99999373 0.9999876 ]

When that 64bit flag is switched on, jax.numpy follow's numpy's precision semantics very closely, and as you can see it causes the numerics to agree here.
Another way to set that flag is by doing something like this at the top of your main .py file:
from jax.config import config
config.update("jax_enable_x64", True)

You can see a bit more in the short gotchas section of the readme, and in the gotchas notebook.

That project looks really awesome, and we want to make JAX work great with it. Please don't hesitate to open issues like this one as you run into any issues or bugs!

Thanks very much for your prompt feedback @mattjj! This helps and we really appreciate it. :+1:

I think the issue is just 64bit vs 32bit.

I knew about this policy. I'm curious how we still managed to get 64-bit precision on the numpy side with 32b arrays? Is there a way to force 32b for the optimization then if it's still working in 64b? I would assume setting the array's dtype to 32b would correctly set things up.
    x0 = np.array([1.3, 0.7, 0.8, 1.9, 1.2], dtype='float32')

To enable 64bit values, I ran your script like this:

I'll look into the gotchas as well and run our failing test (more complicated minimization) with the 64b switch and see if that happens to resolve things there.

That project looks really awesome, and we want to make JAX work great with it. Please don't hesitate to open issues like this one as you run into any issues or bugs!

Thanks!

I'm curious how we still managed to get 64-bit precision on the numpy side with 32b arrays?

My guess is that somewhere NumPy or scipy.optimize.minimize is promoting to 64bit precision here, even if you feed in a 32bit input. Indeed, the output in both cases (with JAX_ENABLE_X64=0) is float64, but perhaps more of the calculations are being done in 32bit precision (namely the evaluation of the objective function) when using jax.numpy without enabling 32bit values.
This experiment seems like some evidence in that direction:
import jax.numpy as np
import numpy as onp
from scipy.optimize import minimize

def run(np):
    def rosen(x):
        return np.sum(100.0 * (x[1:] - x[:-1] ** 2.0) ** 2.0 + (1 - x[:-1]) ** 2.0)

    x0 = np.array([1.3, 0.7, 0.8, 1.9, 1.2], dtype='float32')
    bounds = np.array([[0.7, 1.3]] * 5)
    result = minimize(rosen, x0, method='SLSQP', options={'ftol': 1e-9, 'disp': True})
    print(result.x.dtype)
    print(rosen(result.x).dtype)

run(onp)
run(np)

In [1]: run issue936.py
Optimization terminated successfully.    (Exit mode 0)
            Current function value: 7.96982011054e-11
            Iterations: 29
            Function evaluations: 221
            Gradient evaluations: 29
float64
float64
jax/lib/xla_bridge.py:130: UserWarning: No GPU/TPU found, falling back to CPU.
  warnings.warn('No GPU/TPU found, falling back to CPU.')
Optimization terminated successfully.    (Exit mode 0)
            Current function value:<PHONE_NUMBER>68
            Iterations: 1
            Function evaluations: 7
            Gradient evaluations: 1
float64
float32  # different!

My guess is that somewhere NumPy or scipy.optimize.minimize is promoting to 64bit precision here, even if you feed in a 32bit input. Indeed, the output in both cases (with JAX_ENABLE_X64=0) is float64, but perhaps more of the calculations are being done in 32bit precision (namely the evaluation of the objective function) when using jax.numpy without enabling 32bit values.

Interesting! This is not obvious behavior... I'll dig into this a bit, thanks!


with is different from how it's portrayed in readme

Issue
Considering the example code from the readme:

Expected behavior
Expected label  to have type UILabel
Actual behavior
label is of type Void:

Current workaround
adding return $0 below $0.textColor = .red however, this results in a lot of unneeded boilerplate when with is used often.
Proposed solution
Replacing with(UILabel()) with update(UILabel) in the readme. Since update does result in the expected behavior.

+1 just experienced this.

@stephencelis the README example is misleading. The with() function always returns void unless you return something from within. That's why the example is incorrect. Not sure why you closed @lvnkmn 's PR.

Thanks for the README update!


Ability to mark all previous versions of the crate as insecure

When an security vouln. is fixed, it would be great to create just one crate review that marks all previous versions as potentially insecure.

What I'm thinking about:
Command to mark a version as containing a security fix:
cargo crev review --security-fix <crate> [<version>]

That would mean, any/any major/any minor version is potentially affected.
In the proof it will look like this:
security-fix: <range>

Where <range> can be one of: all, major, minor, patch. It is not as flexible, as full list of ranges that were affected, but that's usually hard to determine/reason about, and if necessary can be simulated by producing multiple proofs.
While I'm at it, I wonder if it would be worthwile to generalize the whole thing to mean "important fix/update".
Sometimes there are important things totally borked in previous versions, and from the perspective of the downstream user, it can be all combined to one "just upgrade, trust me".
I need to think about terminology here. Maybe just advisory: <range>, or fixes: <range>, or important-fix: <range>.

advisory:
  range: <range>
  severity: <level>

version: -1
date: "2019-04-22T21:53:15.382584127-07:00"
from:
  id-type: crev
  id: ZLBAs8cpEy-sIP0ORhOzrxcBxVJQx4Ie6I-b5SLkXE4
  url: "https://github.com/dpc/crev-proofs-test"
package:
  source: "https://crates.io"
  name: base64
  version: 0.5.2
  digest: wMN3VR6EWaI5i7BCYScLsbC1irWcLsEc3TAouoaGoK8
review:
  thoroughness: none
  understanding: none
  rating: positive
advisory:
  affected: major
  critical: false
comment: "https://github.com/RustSec/advisory-db/blob/master/crates/base64/RUSTSEC-2017-0004.toml"

Landed in master along with cargo crev query advisory [...] and cargo crev review <package> --advisory major.

Landed in master


feat: updated get images script without branch checkout for track/1.7

Used by CVE scanning workflows and can be used to collect images URL for airgapped setup. Script is specific for track/1.7 branch to capture all images for that branch. Branch is handled in kubeflow-ci and bundle automation using bundle file.
Summary of changes:

Re-designed get images script to retrieve all images for current branch. Branch management is done outside of this script.

Work is handled in https://github.com/canonical/kubeflow-dashboard-operator/pull/145
Closing.


Chapter3 fixes

Hi Richard and Mark,
More minor typesettting ideas  for chapter 3.
All the best,
David

Hi Richard,
No problem! The double quotes ("+", "-", ...) were a compromise: The existing 1.6 has single quotes as you say, but the single quotes in asciidoc give emphasised text with no quotes. Some sort quotes are needed (so the commas are not in the list!) - can quotes be escaped?
David

Re. including previous chapter's changes - oops, sorry. I probably did that with chapters 4 and 5, too. Won't happen again (touch wood).
David

To get rid of the extraneous commit you need to rebase. Assuming you have upstream pointing at this repo, origin pointing at your fork, and a clean checkout in your local repo:
$ git checkout chapter3_fixes
$ git fetch upstream
$ git rebase upstream/master
$ git push origin +chapter3_fixes


[BUG] Use DefaultAzureCredential with serviceconnection in ado pipeline receive 401

Library name and version
Azure.Identity 1.6.0
Describe the bug
I use DefaultAzureCredential to init CosmosClient
new CosmosClient(endpoint, new DefaultAzureCredential(), options)
in a c# console app, and run the app in ado pipeline with a service connection.
Sometimes it will get 401 error with the following error message:
Provided AAD token was issued by the authority [72f988bf-86f1-41af-91ab-2d7cd011db47] which is not trusted by this database account.
The pipeline can be retried successfully after serval changes.
From the error message， it seems defaultAzurecredential does not use the service connection defined in ado pipeline to get AAD which is in another AAD
tenant (which is should not be 72f988bf-86f1-41af-91ab-2d7cd011db47)
Expected behavior
CosmosClient should have authority to perform action.
Actual behavior
Provided AAD token was issued by the authority [72f988bf-86f1-41af-91ab-2d7cd011db47] which is not trusted by this database account.
Reproduction Steps
In descirbe.
Environment
No response

Thank you for your feedback.  Tagging and routing to the team member best able to assist.

I believe this issue also affects Azure Pipelines (the issue is discussed here: actions/virtual-environments#5908)

Hi @RetYn - DefaultAzureCredential is not aware of the service connection, so you'd need to either pass it to the credential in code, or have the pipeline stash the service connection secrets into the environment such that the credential can find them. See the docs here for details:
https://github.com/Azure/azure-sdk-for-net/tree/main/sdk/identity/Azure.Identity#environment-variables


Update azureps-vm-tutorial.yml

Typo 'displace' should read 'display'

Docs Build status updates of commit d25f9d9:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs-conceptual/azps-4.7.0/azureps-vm-tutorial.yml
:white_check_mark:Succeeded
View (azps-4.7.0)

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel


field map overlays

layers for fields map.

Show fields for approved projects which will be in-use at the same time as project.
same but include proposed/non-approved projects as well.

clicking on a field from the layer should say which project, timeline and crop.

Fields for approved projects has been added, we'll stop there for now.  Adding more will be pretty simple if other scenarios appear.


Work around duplicate name failure

publish error: Error in daemon: You already have a stream claim published under the name 'nicolas-hofer-das-globale-monopoly'. Use --allow-duplicate-name flag to override.

this is happening more often now with the latest changes to allowing more characters. It should still be able to find a unique name regardless of if there's a publish entry or not.


Studio App gets stuck at "Confirm New Site Configuration"

This the output at the dojo console:
>>  [%add-site name=%blog host='blog.rodrigo.systems' path=/ title='blog']

Clicking next won't do anything.

F12 in browser, shows this in the browser console:
main.c6f28cae.js:2 Error: Ship unexpectedly closed the connection
    at onclose (main.c6f28cae.js:2:181608)
    at main.c6f28cae.js:2:177150
    at u (main.c6f28cae.js:2:147185)
    at Generator._invoke (main.c6f28cae.js:2:146938)
    at Generator.next (main.c6f28cae.js:2:147548)
    at pt (main.c6f28cae.js:2:171307)
    at o (main.c6f28cae.js:2:171511)


Use a real editor for lepiter page title elements

They should also:

have a + button for adding a snippet at the beginning (like snippets),
and display when a page title is already taken.

Cheers

Page title on a duplicated name:


Unable to setup Docker Registry with persistence enabled

Is this a request for help?:
YES
Is this a BUG REPORT or FEATURE REQUEST? (choose one):
BUG REPORT
Version of Helm and Kubernetes:
Helm version:
Client: &version.Version{SemVer:"v2.11.0", GitCommit:"2e55dbe1fdb5fdb96b75ff144a339489417b146b", GitTreeState:"clean"}
Server: &version.Version{SemVer:"v2.11.0", GitCommit:"2e55dbe1fdb5fdb96b75ff144a339489417b146b", GitTreeState:"clean"}

Kubernetes version:
Server Version: version.Info{Major:"1", Minor:"11", GitVersion:"v1.11.3", GitCommit:"a4529464e4629c21224b3d52edfe0ea91b072862", GitTreeState:"clean", BuildDate:"2018-09-09T17:53:03Z", GoVersion:"go1.10.3", Compiler:"gc", Platform:"linux/amd64"}

Which chart:
Docker registry (stable)
What happened:
Docker registry not deploying due to timeout while attaching volumes. Here's what I am seeing:
Events:
  Type     Reason            Age                 From                   Message
  ----     ------            ----                ----                   -------
  Warning  FailedScheduling  22m (x5 over 22m)   default-scheduler      pod has unbound PersistentVolumeClaims (repeated 4 times)
  Normal   Scheduled         22m                 default-scheduler      Successfully assigned docker-reg/docker-private-registry-docker-registry-d49dc6fdd-d6slh to <IP_ADDRESS>
  Warning  FailedMount       2m6s (x9 over 20m)  kubelet, <IP_ADDRESS>  Unable to mount volumes for pod "docker-private-registry-docker-registry-d49dc6fdd-d6slh_docker-reg(cef52eea-eb07-11e8-85c9-b06ebfd124ff)": timeout expired waiting for volumes to attach or mount for pod "docker-reg"/"docker-private-registry-docker-registry-d49dc6fdd-d6slh". list of unmounted volumes=[data]. list of unattached volumes=[auth data docker-private-registry-docker-registry-config default-token-xc4p7]

What you expected to happen:
Docker registry should be deployed without such issues.
How to reproduce it (as minimally and precisely as possible):
Run:
helm install stable/docker-registry \
--namespace docker-reg \
--name docker-private-registry \
--values values.yml

Anything else we need to know:
values.yml config:
# Default values for docker-registry.
# This is a YAML-formatted file.
# Declare variables to be passed into your templates.
replicaCount: 1

updateStrategy:
  # type: RollingUpdate
  # rollingUpdate:
  #   maxSurge: 1
  #   maxUnavailable: 0

podAnnotations: {}

image:
  repository: registry
  tag: 2.6.2
  pullPolicy: IfNotPresent
# imagePullSecrets:
    # - name: docker
service:
  name: registry
  type: ClusterIP
  # clusterIP:
  port: 5000
  # nodePort:
  annotations: {}
  # foo.io/bar: "true"
ingress:
  enabled: false
  path: /
  # Used to create an Ingress record.
  hosts:
    - chart-example.local
  annotations:
    # kubernetes.io/ingress.class: nginx
    # kubernetes.io/tls-acme: "true"
  tls:
    # Secrets must be manually created in the namespace.
    # - secretName: chart-example-tls
    #   hosts:
    #     - chart-example.local
resources: {}
  # We usually recommend not to specify default resources and to leave this as a conscious
  # choice for the user. This also increases chances charts run on environments with little
  # resources, such as Minikube. If you do want to specify resources, uncomment the following
  # lines, adjust them as necessary, and remove the curly braces after 'resources:'.
  # limits:
  #  cpu: 100m
  #  memory: 128Mi
  # requests:
  #  cpu: 100m
  #  memory: 128Mi
persistence:
  accessMode: 'ReadWriteOnce'
  enabled: true
  size: 10Gi
  storageClass: 'rook-ceph-block'

# set the type of filesystem to use: filesystem, s3
storage: filesystem

# Set this to name of secret for tls certs
# tlsSecretName: registry.docker.example.com
secrets:
  haSharedSecret: ""
  htpasswd: "huhuma:$2y$05$bnLaYEdTLSpXXXXz2ULza2Ob.XXXXXXXXar9WUujiGzuaZ7TIsTK2W"
# Secrets for Azure
#   azure:
#     accountName: ""
#     accountKey: ""
#     container: ""
# Secrets for S3 access and secret keys
#   s3:
#     accessKey: ""
#     secretKey: ""
# Secrets for Swift username and password
#   swift:
#     username: ""
#     password: ""

# Options for s3 storage type:
# s3:
#  region: us-east-1
#  bucket: my-bucket
#  encrypt: false
#  secure: true

# Options for swift storage type:
# swift:
#  authurl: http://swift.example.com/
#  container: my-container

configData:
  version: 0.1
  log:
    fields:
      service: registry
  storage:
    cache:
      blobdescriptor: inmemory
  http:
    addr: :5000
    headers:
      X-Content-Type-Options: [nosniff]
  health:
    storagedriver:
      enabled: true
      interval: 10s
      threshold: 3

securityContext:
  enabled: true
  runAsUser: 1000
  fsGroup: 1000

priorityClassName: ""

nodeSelector: {}

tolerations: []

The pvc gets provisioned correctly and is also bound:
root@gamman4:/home/devops/rke-k8s/helm-docker-reg# kubectl get pvc -n docker-reg
NAME                                      STATUS   VOLUME                                     CAPACITY   ACCESS MODES   STORAGECLASS      AGE
docker-private-registry-docker-registry   Bound    pvc-ce4cb46d-eb07-11e8-9b5d-2cfda16d3cfd   10Gi       RWO            rook-ceph-block   28m

The issue was with openebs storage. Resolved by - https://docs.openebs.io/docs/next/tsgiscsi.html


Add AppProfileIdOption for bigtable Data API.

The App Profile Id is optional, so let's pass it as an option, instead of having a Table constructor with and without an app_profile_id field. The default value will be the empty string.
namespace google::cloud::bigtable {
struct AppProfileIdOption {
  using Type = std::string;
};
} // namespace google::cloud::bigtable

So, our connection methods all look like:
Foo(std::string const& app_profile_id, std::string const& table_name, FooArgs...);

They have been in our public API for a few days, but have not been released yet.
I think we should drop the app_profile_id parameter, and instead pass the value in the OptionsSpan as an AppProfileIdOption.


Issues 880

General

FormSchema support nest field when 'field' value type is NamePath(same as Ant Design Vue Form.Item 'name' parameter),  #880
change FormSchema 'field' and necessary method parameter type from string to NamePath
removeSchemaByFiled mothod only support only one fileld(string[] parameter uesed to nest property)
Form component document need to update
✏ Mark the necessary items without changing the structure of the PR template.

[x] Pull request template structure not broken

Type

ℹ What types of changes does your code introduce?

👉 Put an x in the boxes that apply

[x] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[x] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[x] This change requires a documentation update

Checklist

ℹ Check all checkboxes - this will indicate that you have done everything in accordance with the rules in CONTRIBUTING.

👉 Put an x in the boxes that apply.

[x] My code follows the style guidelines of this project
[x] Is the code format correct
[x] Is the git submission information standard?
[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[x] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes
[x] Any dependent changes have been merged and published in downstream modules

这个为什么close了呀？vben现在真是一坨


Retrying failed jobs causes PHP memory exhaustion errors when dealing with thousands of failed jobs

Laravel Version
10.34.2
PHP Version
8.1.26
Database Driver & Version
No response
Description
A project I'm working on has 300k failed jobs. When I try to run artisan queue:retry it results in an error...
PHP Fatal error:  Allowed memory size of 536870912 bytes exhausted
After looking into how the RetryCommand works, I realized that rather than querying just the IDs from the failed jobs table, it loads the entire table and then plucks the ID column. No matter how high I set the memory limit, the server won't be able to handle loading all 300k failed jobs into memory.
This is a very inefficient way to load the failed job IDs. Any thoughts on how this could be improved without breaking anything?
Steps To Reproduce

Populate the failed_jobs table with 300k failed jobs
Run php artisan queue:retry

A similar issue was reported in #33874.