Release Google.Cloud.BareMetalSolution.V2 version 1.0.0

Changes in this release:
No API surface changes; just dependency updates and promotion to GA.

Created release for Google.Cloud.BareMetalSolution.V2-1.0.0


fix: update langchain dependency to version 0.2.9

Pull Request Checklist
Note to first-time contributors: Please open a discussion post in Discussions and describe your changes before submitting a pull request.
Before submitting, make sure you've checked the following:

[x] Target branch: Please verify that the pull request targets the dev branch.
[x] Description: Provide a concise description of the changes made in this pull request.
[ ] Changelog: Ensure a changelog entry following the format of Keep a Changelog is added at the bottom of the PR description.
[ ] Documentation: Have you updated relevant documentation Open WebUI Docs, or other documentation sources?
[ ] Dependencies: Are there any new dependencies? Have you updated the dependency versions in the documentation?
[ ] Testing: Have you written and run sufficient tests for validating the changes?
[ ] Code review: Have you performed a self-review of your code, addressing any coding standard issues and ensuring adherence to the project's coding standards?
[x] Prefix: To cleary categorize this pull request, prefix the pull request title, using one of the following:

BREAKING CHANGE: Significant changes that may affect compatibility
build: Changes that affect the build system or external dependencies
ci: Changes to our continuous integration processes or workflows
chore: Refactor, cleanup, or other non-functional code changes
docs: Documentation update or addition
feat: Introduces a new feature or enhancement to the codebase
fix: Bug fix or error correction
i18n: Internationalization or localization changes
perf: Performance improvement
refactor: Code restructuring for better maintainability, readability, or scalability
style: Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc.)
test: Adding missing tests or correcting existing tests
WIP: Work in progress, a temporary label for incomplete or ongoing work

Description
When running docker compose build on the dev branch, getting this error (see snippet below)
I've done this build on multiple machine with the same error.
updated langchain version based on error and now it builds. (not sure why this hasn't been seen already - think it broke 3 days prior with langhchain-community version bump)
Snippet of build output from docker compose build
72.96 Successfully installed MarkupSafe-2.1.5 filelock-3.13.1 fsspec-2024.2.0 jinja2-3.1.3 mpmath-1.3.0 networkx-3.2.1 numpy-1.26.3 pillow-10.2.0 sympy-1.12 torch-2.4.0+cpu torchaudio-2.4.0+cpu torchvision-0.19.0+cpu typing-extensions-4.9.0
72.96 WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager. It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv
79.82   × No solution found when resolving dependencies:
79.82   ╰─▶ Because langchain-community==0.2.9 depends on langchain>=0.2.9 and you
79.82       require langchain==0.2.6, we can conclude that your requirements and
79.82       langchain-community==0.2.9 are incompatible.
79.82       And because you require langchain-community==0.2.9, we can conclude that
79.82       the requirements are unsatisfiable.
80.02 chown: cannot access '/app/backend/data/': No such file or directory

Changed
update langchain python dep to 0.2.9

Bumped, Thanks!


update  auto-recompile-wait

The option auto-recompile-wait is currently causing performance issues in many places.
What should be done

[ ] make this an environment setting
[ ] set the default to 0.1 s

Hey team! Please add your planning poker estimate with ZenHub @andraskvr @arnaudsjs @FloLey @Hugo-Inmanta


TcpKeepalive::with_retries() doesn't seem to load and can't be used.

Hello. I'm quite new to your crate. I am liking that it actually has keepalive functionality. Unfortunately, it doesn't seem to be working as described. I checked the docs and some example code. Here is how the example put it:
let keepalive = TcpKeepalive::new().with_time(Duration::from_secs(4)).with_interval(Duration::from_secs(1)).with_retries(4);
This is the error it gives:

no method named with_retries found for struct TcpKeepalive in the current scope

The only problem with this is the compiler doesn't recognize with_retries() as being part of TcpKeepalive. I checked you documentation and it's there, clear as a bell. It does have OS specific targeting, but I am using it on a Debian server, which should be fine. I even checked the source and found it there.
I'm not sure what the problem is. Maybe it's not detecting the OS as linux, I'm not sure.

TCP keepalive is not available on all platforms, so it's behind the all feature. Did you try enabling that?

Ah, thanks. still new to rust and didn't understand the feature system.
I wonder, maybe a suggestion. I could see cases where people would like functionality like this in OSs that support it and remove it in ones that don't. As the method can be daisy chained, to have two versions to protect OSs that don't support it, you would have to duplicate all the calls. Could something like a flag parameter be possible? Like, for methods that face tighter restrictions, an additional bool parameter could be supplied. If false is passed, the method fires, but simply returns self instantly, otherwise if true is passed then the functionality does what it normally would. This way, the additional parameter is a signal that this method is different from others and requires special attention. At the same time, the programmer can do OS detection or whatever and set a flag for the call. this way, there only needs to be one daisy chained call as the method, no matter the flag, won't cause it to fail. It will simply have functionality or it won't.
One aspect I like about a method like this is that each method requiring special attention flags your attention through an extra bool parameter. A feature flag likely changes things for a lot of calls, but i may only be focused on this one when I set the flag, but I may then accidentally use another restricted method and not know it's restricted unless I specifically look for it in the documentation.
Just a thought.

Ah, thanks. still new to rust and didn't understand the feature system.

If you haven't already, https://doc.rust-lang.org/cargo/reference/features.html is worth a read.

I wonder, maybe a suggestion. I could see cases where people would like functionality like this in OSs that support it and remove it in ones that don't. As the method can be daisy chained, to have two versions to protect OSs that don't support it, you would have to duplicate all the calls.

What do you mean with duplicating the calls? You can use something like the following to make OS specific calls.
let keepalive = TcpKeepalive::new().with_time(Duration::from_secs(4)); // Options on all OSs.
#[cfg(target_os = "linux")]
let keepalive = keepalive.with_interval(Duration::from_secs(1)); // Linux only.
let keepalive = keepalive.with_retries(4); // More options for all OSs.

Could something like a flag parameter be possible? Like, for methods that face tighter restrictions, an additional bool parameter could be supplied. If false is passed, the method fires, but simply returns self instantly, otherwise if true is passed then the functionality does what it normally would. This way, the additional parameter is a signal that this method is different from others and requires special attention. At the same time, the programmer can do OS detection or whatever and set a flag for the call. this way, there only needs to be one daisy chained call as the method, no matter the flag, won't cause it to fail. It will simply have functionality or it won't.

I don't want to pretend we support a certain call only to make it a no-op, it's just lying to the users (of this library) and it's not something I want to do. Furthermore the code might depend on the changed functionality that now doesn't work for some platforms, but it's not clearly indicated on what platforms it doesn't work.

One aspect I like about a method like this is that each method requiring special attention flags your attention through an extra bool parameter. A feature flag likely changes things for a lot of calls, but i may only be focused on this one when I set the flag, but I may then accidentally use another restricted method and not know it's restricted unless I specifically look for it in the documentation.
Just a thought.

Since the problems seems to be resolved I'm going to close, feel free to reopen or comment.


2019 cell phone purchase

https://github.com/130s/hut_10sqft/issues/345 for my Google Pixel (32GB) has become unbearable (it makes me not to go out without carrying a mobile battery). Time to resolve that issue, or get a new phone.

Interested in buying Pixel 4.
Btw, Google's online store offers "Trade-In" program where I can get a refund by shipping back my old phone. I just evaluated my Pixel 32GB, then it's estimated only for $47. No-no. I rather keep it as a backup for whatever purpose.

Joined a waitlist on google.com.

Waitlist didn't seem to do anything to me. Just ordered Pixel 4 separately, sometime in October.


minor typo in help output

Super minor, just figured I would fix it rather than just point it out.

Thanks!


SemisupervisedTranslationTask cannot run on multi-GPU mode

🐛 Bug

When I run the semisupervised translation task with muliti-gpu, hangs and runs the following error: RuntimeError: arguments are located on different GPUs. And BacktranslationDataset doesn't work with multiple workers as reported in #805
To Reproduce
Steps to reproduce the behavior (always include the command you ran):
export CUDA_VISIBLE_DEVICES=0,1,2,3
python train.py $DATA --task semisupervised_translation -a multilingual_transformer ....
Environment

fairseq Version (master):
PyTorch Version 1.5
OS (e.g., Linux): Ubuntu
How you installed fairseq (pip, source): source
Build command you used (if compiling from source): pip install -e ./
Python version: 3.7
CUDA/cuDNN version: cuda 10.2
GPU models and configuration: Quadro RTX 6000

The above commits didn't fix the issue and #805 is still an issue


Android Studio: Ignore .cxx directories in v3.5

Android Studio 3.5 introduced .cxx directories containing CMake configuration
directories, similar to .externalNativeBuild.

@rcdailey any links to StackOverflow discussions or other documentation about this change?

Thanks for responding. I apologize if it seems like I have ignored your template, that was not my intention. I did not provide a link to a site that documents the .cxx directory because I couldn't find one. I did look, though. Unfortunately, Android Studio 3.5 is so new and C++ usage in it so niche that I'm not able to find any search results that describe the change.
However, I am observing that Android Studio is creating these directories when you have C++ & CMake support in your project. It seems to be similar to or a replacement of the .externalNativeBuild directories that were there before.
Is this not enough to accept this change?

👍

I contacted the developers on the Android Studio team. They confirmed this is an official change. It's the renamed version of the former .externalNativeBuild directory. However it isn't in the release notes.

@shiftkey It's already been about 1 month since I opened this PR. How many more months do I need to wait for a merge for a 1 line change?

Because the developer is neglecting my PR (there are over 100 open already), I moved my PR to the gitignore.io repository in hopes of getting this merged quicker:
https://github.com/toptal/gitignore/pull/236
I'm very disappointed in the PR process in this repo. The developers need to streamline this process. Closing this PR in favor of the one linked above.

@rcdailey apologies for not getting back to you sooner.
The reason why I ask questions and chase as much detail as possible is that this repository is used in a lot of places, and changes without a thorough review have the ability to break users environments, and I'm the one left to pick up the pieces.
I'm sorry that you felt that closing out the PR here was necessary to grab my attention. In the future, in the absence of external links, it'd be great to heave someone from the Android Studio team chime on a PR like this to give it a 👍.

@shiftkey I attempted to grab your attention via direct mention. Others have commented on the PR, which should have generated a notification for you. I did my best to follow up with the required information you asked for, even though it wasn't there. IMHO, due diligence was done. It's been a month, I'm moving on. FWIW, in the Topal repository my PR was merged in the same day.
Also Re: Android Developers - They do not have the time to come to this repo and directly comment to explain a change that wasn't in their release notes. That's not a reasonable request for you to make. Also most folks won't have direct contact with them like I do, so how else are they to know to come here?
Your PR process and requirements are too strict and unreasonable. I think in cases where your requirements cannot be met exactly, you should accept explanations like the one I have given. Or even do  your own personal research if you are uncomfortable with it. But either way, without continued feedback and communication from you on active PRs, none of this matters.
As I said before, I really feel like you need to automate this process somehow. Either that, or streamline it by making your requirements less strict, being more proactive (and active in general) on PRs. Not sure exactly what needs to be done, but I'm sure you can figure something out.

@rcdailey thanks for clarifying. We'll see what I can do but I only have so many hours in the day to spend on the multitude of OSS projects I maintain.
Please also read about https://github.com/github/gitignore/pull/1815 about the time I broke Azure deployments to understand why I'm conservative these days about what I accept to this project.

I found the following statement on the official Android NDK dev docs:

Note: Older versions of the Android Gradle Plugin placed these files in the .externalNativeBuild directory rather than the .cxx directory.

So the change seems legit to me. But it might be good to move the change up next to the .externalNativeBuild rule...


Initial import of Android sources

Adds the basic support for Perspex rendering on Android.
Currently supports devices running API 15 (ICS 4.0.3) or higher.

Test Support Mostly Working
Path Drawing Mostly Working

##Hor it works
Perspex.Android extends the Activity class and create an activity that soft a Canvas, a static instance of itself (PerspexActivity), and a PerspexView which is an extension og View that currently extends IWindowImpl, IRenderTarget, and IPlatformHandle
When OnDraw() is called on our VIew, we save passed Canvas to the static instance of our PerspexActivity. When then Tell the IWindowImpl (our PerspexView) that it needs to draw itself. Because our PerspexView is also an IRenderTarget, our view will create the needed DrawingContext, taking the Canvas we set earlier, and then draw on that.
:dancers:

Pulled request tot he wrong branch.


Clarify Blazor static asset location

Fixes #17109
Internal Review Topic (links to Static Assets section)

@Rick-Anderson Let's take care of this on our end ... DR is 🏃😅.


Created TextArea component.

Added the test cases on following scenarios:
Test text area component is rendered or not.
Should allow label value for text area component.
Should allow text area with prefix.
Should allow text area with suffix.
Should allow text area with minlength,
Should allow text area with maxlength.
Should allow text area with placeholder.
Should not allow invalid values.

asdfsadfasdf


lib/repository2: add support for docker v2.2 and OCI

This commit adds support for the docker v2.2 image format and OCI image
format. When the remote registry supports the docker v2 HTTP API,
docker2aci will add the media types for v2.1, v2.2 and OCI to the Accept
header on the manifest request, and handle the returned manifest version
accordingly.

Right now docker2aci is relying on the docker hub rewriting manifests into the v2.1 schema for it.
Also I want to write a test or two for this before it gets merged, so that will come next week.

@iaguis @s-urbaniak review?

@s-urbaniak switched to using a single buffered channel, as per your suggestion

@dgonyeo that was quick ;-) thanks for the quick update. How did you test this locally? I'd like to play with it tomorrow morning.

I pointed it at the docker hub (i.e. ./bin/docker2aci docker://nginx) and used print statements to see that my new code paths were being hit. Not graceful, but works.
For the tests I'm going to write this week I intend to spin up a local distribution, but docker2aci gets upset when the local distribution responds to its https request with http, so I might need to tweak --insecure-allow-http to support that.

@s-urbaniak how's it look now:

a buffered channel is used to receive results from the goroutines started up
the closers and files, if not nil, have a deferred close (realized we could also leave the files open here if an error was hit a few lines down)
If the err is not nil, it's put in a list
After getting the responses from each goroutine, if the list of errors is not empty, return the first error that was encountered

@dgonyeo :+1: ... those dreaded resources ;-)
Another idea I had to omit those if closer/file != nil checks: we could also return a https://golang.org/pkg/io/ioutil/#NopCloser in case of an err .. but I leave that to you if that makes code any "prettier".
lgtm from my side, didn't make it to test today though, will do so tomorrow.

@dgonyeo out of curiosity: why do we need to bubble up those response bodies (closer) up through the channel? Can't we close them earlier?

@s-urbaniak: those response bodies can't be closed until the copier.PrintAndWait call finishes, as the CopyProgressPrinter is still copying data from them. Maybe it would be cleaner to have the CopyProgressPrinter have a function like CloseAllInputs that could be called after the transfers are complete.

bump - what's left? more review?

Still lgtm from my side, just had a small implementation question.

Just realized that I never correctly added the annotations to the new manifest after doing the v2.2 -> AppC manifest conversion, so just updated this commit to fix that.

And just added a commit that tweaks the tests to run them against a local registry in addition to running them on local files. The tests aren't as comprehensive as I wanted, but I couldn't find an easy way to generate/seed the registry with differing versions of docker images. This at least hits the fetching logic a few times.

@s-urbaniak final review?

Found two small nits

Couple of nits but also LGTM overall

Oh, also added a gitignore because things in test/ were cluttering my git status.

@dgonyeo ping, is it ready for merge?

I believe it is.

@dgonyeo @s-urbaniak

Sorry for the delay, I was confused who is supposed to merge.


Is there support for events and tags?

We have this feature request in our backlog but we still do not have any ETAs to it.


Remove Volto

It has been merged into FontTools as fonttools voltLib.voltToFea.

Do you think Volto should be removed, or perhaps simply frozen and deprecated?

I don't have a strong opinion either way, but if you want to keep it I can make it import the FontTools module, so ut becomes basically a glorified alias.

Maybe I will just retain the Volto folder and update the readme to direct users to FontTools.


Opt-in to preflight styles

Currently, preflight global styles are injected as a sensible default to an app-level styling approach.
This is a bit aggressive and could be more useful if it could be added by the developer.
benefit

named export from package, like injectPreflight or similar

benefit-react

<Preflight /> component

Related: https://www.styled-components.com/docs/api#createglobalstyle


Error building app after upgrading to ember-cli 2.11.1

I'm kinda stumped because it looks to me like ember-impagination is using ember-cli 2.11.1. Also, ember-template-compiler does not appear to be a bower package.
Error: Cannot find module 'path-to-my-project/bower_components/ember/ember-template-compiler.js'
    at Function.Module._resolveFilename (module.js:440:15)
    at Function.Module._load (module.js:388:25)
    at Module.require (module.js:468:17)
    at require (internal/module.js:20:19)
    at Class.module.exports.htmlbarsOptions (path-to-my-project/node_modules/ember-impagination/node_modules/ember-cli-htmlbars/ember-addon-main.js:99:25)

Hmm, adding "ember": "~2.11.1" to bower.json seems to take care of the issue. But I'm pretty sure that's not supposed to be needed anymore. I'm gonna close this but I'd be interested in any insight folks anyone might have.

Interesting! I'm going reopen this because that means we have an unneeded bower dep.

Just hit this too.

What version of ember-impagination are you using?
I recommend upgrading ember-impagination to the 1.0.0-aplha.6 release if upgrading your ember applications. There are a few breaking changes which need to be documented in a "Migration Guide". Checkout the demo page for some code examples to get you moving in the right direction. Please let me know how I can help and the migrations you run into.

As far as I can tell this is no longer an issue.


Crosshair Alpha Proof of Concept

This is a proof of concept for a feature I've been wanting as I find the stock crosshair a little hard to distinguish sometimes.
It could easily be extended to allow full RGBA customization, but I was hoping to find a way to display a preview of the color within the menu before implementing that.
Thoughts?
Thanks for the awesome project!

You might have to either make a new menu control for that or add an extra MENUITEMFLAG_ that causes the menu rendering routines to color the menu item with a color supplied in one of the menuitem param fields, for example for sliders.

Thanks, that helped a lot!
Pushed changes to add full RGBA customization and a preview label.

Found a way to add a simple colored box for the preview.

I've merged the unsigned int PR, so you can use that here.

@fgsfdsfgs
Thanks! New config type is swapped in now.


Add updateCheckoutState mutation

Quick Info

Issue
Schema updates
New type/mutation

#44
:+1:
:+1:

[ ] Add updateCheckoutState mutation: This set any current_order valid state and accept a state String argument.

There are several problems to trigger the  checkout state_machine after the order status update (like via next!)
It's simple to trigger an event in the state machine, but not all the statuses are managed by a transition event.
Now, we have these transition events declared:
cancel, return, resume, authorize_return, complete, payment_failed
All other statuses are managed by before and after transitions hooks.
For more information about how events and transition hooks work in state_machine, you can refer here: StateMachine::Machine#event
This situation doesn't allow us to properly validate the order status update (for example, I could update an address status to payment without errors).
Considering that this isn't a priority mutation, for the moment, we close the PR.


current head of main prints help text instead of connecting

$ git rev-parse --short HEAD && cargo run --release --bin fwd -- coder.bwm
a40a493
   Compiling fwd v0.9.0 (/Users/bwm/repos/fwd)
    Finished release [optimized] target(s) in 6.67s
     Running `target/release/fwd coder.bwm`
usage: fwd [options] (<server> | browse <url> | clip [<file>])

To connect a client to a server that has an `fwd` installed in its path, run
`fwd <server>` on the client, where <server> is the name of the server to
connect to.

On a server that already has a client connected to it you can use `fwd browse
<url>` to open `<url>` in the default browser of the client.

On a server that already has a client connected to it you can use `fwd clip`
to read stdin and send it to the clipboard of the client, or `fwd clip <file>`
to send the the contents of `file`.

Options:
    --version    Print the version of fwd and exit
    --sudo, -s   Run the server side of fwd with `sudo`. This allows the
                 client to forward ports that are open by processes being
                 run under other accounts (e.g., docker containers being
                 run as root), but requires sudo access on the server and
                 *might* end up forwarding ports that you do not want
                 forwarded (e.g., port 22 for sshd, or port 53 for systemd.)

Should be fixed with 604f31d8e68f9c6ee3f9a286d0cf7e9074cd4f22


Allow AxisArrays that are missing dimensions and/or names?

I'm still just reading the code (and getting a better feel for staged functions!). On @mbauman's question in the code on allowing missing names, I think we should make axes names mandatory or give defaults. However, we should allow the user to leave out the axes (default to nothing for each). A user might only want the Axis() indexing capability. If folks agree, it would be good to flip the order on the following constructor as follows:
stagedfunction AxisArray{T,N}(A::AbstractArray{T,N}, names::(Symbol...), axes::(AbstractVector...))

Then we need defaults of nothing for each axes. Can you have a staged function with default arguments?

Yup, I agree.  We can make the constructors fancier.  Axes and their names are different enough that we should be able to support all flavors here.  If they're axis names are omitted, I currently give them row/col/page defaults.
I think it's most sensible to allow shorter axes and axesnames than the dimensionality of the array.  If you want to name some intermediate dimension, you gotta name all of the ones to its left, too.  Same with the axes.


Rendering navigation twice using Fresca theme

Issue Summary
If my understanding is correct, I can use {{navigation}} helper anywhere I want in theme and it will always render navigation, but that's not happening when Fresca theme is used. My friend is using this theme for his blog http://lifehacky.ghost.io, where Fresca tries to render navigation twice on page, top, where is rendered correctly, and bottom, where it tries to iterate over @blog.navigation to render navigation, but the URLs are not rendered properly using {{url}} helper - URL is just http://lifehacky.ghost.io. When I tried to use {{navigation}} on bottom instead of iteration over @blog.navigation, menu is not rendered at all.
I guess it has probably something to do with #5841
Ghost.io hosted site
Browser: Safari & Chrome
OS: Mac
Technical details:

Ghost Version: Ghost.io hosted site
Node Version: N/A
Browser/OS: Safari & Chrome on Mac
Database: N/A

Hey @rbukovansky!
Thanks for your report.
Closing, because this report is a duplicate of https://github.com/TryGhost/Ghost/issues/5162.


Vm migrate statemachine fix

The Vm migrate automate state machine fails with the following error:
Class [unknown/VM/Lifecycle] not found in MiqAeDatastore
The parse_provider_category automate method sets provider_category to cloud or infrastructure based on the available object information. The method sets the provider_category to "unknown" when it is not able to determine the correct type.
The automate method change was to add the vm_migrate object processing.
Also fixed some related state machine path issues resulting from the domain restructure.

@tinaafitz Can you describe the problem being solved?  Is it just the typos, or is it completely missing?

@Fryguy - Added problem description.


Hyperlink on Arrow icon in Google doc is not working.

@vdua  Please suggest how to add hyperlink on arrow icon in Google doc.

@2016DigiTech what is the preview URL for the above page?


I'm getting an error: ChildProcessError

How can i fix this problem.
ChildProcessError: convert /tmp/188b775e-8611-4e99-adb8-7956e6d71896.png -thumbnail 200x200> /tmp/thumb_188b775e-8611-4e99-adb8-7956e6d71896.png` failed with code 1
at ChildProcess.<anonymous> (/user_code/node_modules/child-process-promise/lib/index.js:132:23)

at emitTwo (events.js:106:13)

at ChildProcess.emit (events.js:191:7)

at maybeClose (internal/child_process.js:920:16)

at Socket.<anonymous> (internal/child_process.js:351:11)

at emitOne (events.js:96:13)

at Socket.emit (events.js:188:7)

at Pipe._handle.close [as _onclose] (net.js:509:12)`

Same issue with me, did u manage to solve it.

@abdulwahabone No, I did not.

@abdulwahabone  there is a solution here.
https://stackoverflow.com/questions/44479085/childprocesserror-for-image-moderation-firebase-function


Request Permissions

Permissions should be requested as dialog / via user action.
Chrome emits a "Violation" warning on automatic permission requests.

Firfox even blocks them (see restricting-notification-permission-prompts-in-firefox/) and shows only one icon in the search bar.


markers-update-example example cannot update marker position in 0.7.13 version

From @samuelpfchoi on April 16, 2015 4:33
markers-update-example example cannot update marker position during dragging the marker in 0.7.13 version
Copied from original issue: tombatossals/angular-leaflet-directive#685

From @samuelpfchoi on April 16, 2015 8:54
It seems that the change of lat & lng is updated to model object (_genDispatchMarkerEvent function).
is it intentional? and how can I sync the data back to original marker object or how can I get the model object. Thanks


Enable coverage

Nyc is much simpler to setup and use.
Moved coveralls to only CI.

Sorry!I  rest it? Sent from my Huawei phone-------- Original message --------From: Bogdan Chadkin<EMAIL_ADDRESS>Sun, Feb 14, 2021, 7:36 PMTo: svg/svgo<EMAIL_ADDRESS>Subscribed<EMAIL_ADDRESS>Re: [svg/svgo] Enable coverage (#1323)
Merged #1323 into master.
—You are receiving this because you are subscribed to this thread.Reply to this email directly, view it on GitHub, or unsubscribe.


remove test dependencies from setup.py

lines 37 and 38 define testing dependencies outside of requirements_tests.txt which will cause failures when releasing on conda-forge.
Also, is nose the canonical test suite? I thought many of the pysal packages had migrated to pytest, but could be wrong

see, e.g. https://github.com/conda-forge/staged-recipes/pull/8350

Addressed in #28


Status reports only shown in terminal, not on the Web interface.

Hi There,
I really like this tool. It is quite easy to spin up and powerful.
However, I have an issue of the statistic report. When I run a simple test on my Mac with 10 simulated users against my restful api server, everything seems fine except that the Web interface does not provide live status. In fact, the Web interface does not provide any status at all. The status report only shows up when I Ctrl+C to terminate the program in the terminal. Something like this below.
I've searched online for a while, but couldn't find an answer how to make the Web interface alive.
Could you help? Really appreciate your time.
Anakun
[2015-08-12 12:28:00,793] /INFO/locust.main: Shutting down (exit code 0), bye.
Name # reqs # fails Avg Min Max | Median req/s
POST /research/api/v1/auth/signUp 5 5(50.00%) 5320 998 10135 | 6400 0.40
Total 5 5(100.00%) 0.40
Percentage of the requests completed within given times
Name # reqs 50% 66% 75% 80% 90% 95% 98% 99% 100%
POST /research/api/v1/auth/signUp 5 6400 7900 7900 10000 10000 10000 10000 10000 10135
Error report
occurences Error
5 POST /research/api/v1/auth/signUp: '"HTTPError('409 Client Error: Conflict',)"'

You are not seeing any live status because all you requests are failing with '409' from you application under test. In fact, you would see these results on 'Errors' tab of the Web interface.
I guess you are signing up with the same user, hence you are getting 409 Conflict. Correcting this should solve the issue for you

Hi Vividh,
Thanks for your quick response. Actually, the conflict is part of the test.
Thanks again!!
Kun


CORE-10416 : Maximize normalization in metaInf dir of Jars, minimize cache misses.

When calculating gradle cache, ignore changes in the metaInf dir of jars, any properties here that change from build to build will result in cache misses and sub-optimal performance of remote/local caching.
This only affects Gradles caching mechanism and how cache keys are inspected and has no bearing on published artifacts / what is produced in a jars metaInf.
When observing build-cache misses Dokka task was also adding overhead for each run due to the changing module version, set this to cordaVersion or RELEASE_VERSION if it exists, which does not add the dynamically injected suffix, this ensures these tasks are up-to-date if no dokka related change has occurred.
Similar runtime os where i have captured some build scan data in the description: https://github.com/corda/corda-runtime-os/pull/3304

LGTM @ronanbrowne can you add the value-gain observed by this change ?

PR slipped through my radar, But the difference is  about 17 Gradle tasks approx 1 min saved in corda-api (varies per execution based on other factors also )
but some comparisons of buid scans here
post change https://gradle.dev.r3.com/c/tc3uv2gfjvipw/wuc6qsxixa2sw/task-inputs?cacheability=cacheable
pre-change: https://gradle.dev.r3.com/c/qjl53jx6ztmqa/i4gnsc5dd4bkc/task-inputs?cacheability=cacheable
The main take away is is the same control scenario, we were able to get a build to take advantage of the case so that 44 tasks were executed (this is quite low)


How can i convert my own LiDAR point-cloud data rather than the data from KITTI ?

Any info on this?


Climate - Melissa - turn_on doesn't work

Home Assistant release with the issue:
0.99.3

Last working Home Assistant release (if known):
before 0.96 (most likely)
Operating environment (Hass.io/Docker/Windows/etc.):
Hass.io

Component/platform:
/components/melissa/

Description of problem:
service climate.turn_on does not turn the device on. It doesn't send any command from Melissa to the HVAC unit. Tested with Lovelace Thermostat card and from Developer Tools -> Services.
Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant):
melissa:
  username: xxxx
  password: !secret melissa_password

Traceback (if applicable):

Additional information:
Not sure when this broke, but as no major changes to Climate or Melissa have been done except in 0.96, I think that's the culprit.

I'm aware of this, just have not had the time to fix it (my own system is broken :'( asw.), Its not a big fix I'm sure.


Refactor email harvest to not use instantiate DeferredIMAP forever.

This change is

Changes Unknown when pulling d73bd46fa2c90b755e69da53c9d955c995c956ec on ropable:master into ** on parksandwildlife:master**.

Changes Unknown when pulling 553c5a4de86b1bbe552298a639e171d5a262c604 on ropable:master into ** on parksandwildlife:master**.


break readme out to multiple files

It's getting a bit lengthy.  Would be better to break it out to multiple .md with an index so people can get the information the want

see wiki


is there a method or api to control  search/replace widget show or hide ?

monaco-editor version: 0.10.1
Browser: chrome 65.0.3325.181
OS: Windows 7
Steps or JS usage snippet reproducing the issue:

I want to hide this widget after user save there content ,is there a method or api to control  search/replace widget show or hide ?

You could execute a command, e.g. editor.trigger('closeFindWidget') or reach into the find controller and close it e.g. editor.getContribution('editor.contrib.findController').closeFindWidget()

thanks,I use editor.trigger('keyboard','closeFindWidget') clsoe it


Calibration Example of Complex Model

Hello,
Following the suggestion from @cpfiffer  from this issue, here I'm posting a self-contained script with a complex model whose calibration with Turing I may not be able optimize properly.
Unfortunately I am not a domain expert in MCMC or ADVI, so the best I could do was to try all the techniques and gridsearching all the arguments in the tutorials. I also implemented the suggestions received in these issues:

Type inference in Turing model when using vectorized ~
:forwarddiff backend with type specification goes OOM
Inference using :reversediff, :tracker and :zygote performs worse than :forwarddiff

but I think that the amount of domain expertise required to properly tune the samplers and the ADVI is probably worth a question. This issue may of course be used as an example on how to tune Turing to calibrate models with over 30 parameters and  around 15 time series to reproduce.
I would then like to present here a proxy to our model, and a calibration pipeline with ( I hope!) as many details as possible already set up , so that if you think it's appropriate you may help us optimize its calibration as much as Turing allows, exploring Turing's parameters and functionalities surely better and more efficiently than what I managed to.
Our model is an age-stratified S_E_I_H_ICU_R_D epidemiological model, with 32 parameters in total. We have 5 age classes, and the data we would like to calibrate the parameters against are 5 time series of hospitalizations ( one per age class), 5 time series of ICU occupancies and 5 time series of cumulated deaths.
Here is the code:
using DifferentialEquations
using Memoization, Turing, ReverseDiff, Zygote
using DiffEqParamEstim , Optim

using Distributions
import Statistics

using Bijectors                                            # to use the more advanced interfaces of ADVI
using Bijectors: Scale, Shift

using Plots
pyplot()

using BenchmarkTools

# # I leave these commented for now, but I noticed that performance varies largely by playing with them.
# Turing.setredcache(false)
# Turing.setadbackend(:forwarddiff)

# define the epidemiological model as a DifferentialEquations.jl. the model is wrapped by a closure that allows to specify the last 32-12 = 20 parameters values. In this way, the 32-parameters model effectively becomes a 12-parameters model. The first 20 may be initialized with a previou ssuccessful calibration. This may  let one reduce calibration times when testing.
function SEIH_ICU_RD!(; calibrated_parameters::Vector{Float64})
    function parameterized_SEIH_ICU_RD!(du,u,p,t)

        # passed parameters
        if length(calibrated_parameters) == 0
            β,                                                      # the transmissibility
            ϵ,                                                      # incubation period
            λ_IR_1, λ_IR_2, λ_IR_3, λ_IR_4, λ_IR_5,                 # age-stratified delays from infected to recovered ( without going through hospitlazation)
            λ_IH_1, λ_IH_2, λ_IH_3, λ_IH_4, λ_IH_5,                 # age-stratified delays from infected to hospitalized
            λ_HICU_1, λ_HICU_2, λ_HICU_3,λ_HICU_4, λ_HICU_5,        # age-stratified delays from hopsitalized to ICU
            λ_HR_1, λ_HR_2, λ_HR_3, λ_HR_4, λ_HR_5,                 # age-stratified delays from hospitalized to recovery
            λ_ICUD_1, λ_ICUD_2,  λ_ICUD_3, λ_ICUD_4, λ_ICUD_5,      # age-stratified delays from ICU to death
            λ_ICUR_1, λ_ICUR_2, λ_ICUR_3, λ_ICUR_4,  λ_ICUR_5 = p   # age-stratified delays from ICU to recovery
        else
            β,
            ϵ,
            λ_IR_1, λ_IR_2, λ_IR_3, λ_IR_4, λ_IR_5,
            λ_IH_1, λ_IH_2, λ_IH_3, λ_IH_4, λ_IH_5 = p

            λ_HICU_1, λ_HICU_2, λ_HICU_3,λ_HICU_4, λ_HICU_5,
            λ_HR_1, λ_HR_2, λ_HR_3, λ_HR_4, λ_HR_5,
            λ_ICUD_1, λ_ICUD_2,  λ_ICUD_3, λ_ICUD_4, λ_ICUD_5,
            λ_ICUR_1, λ_ICUR_2, λ_ICUR_3, λ_ICUR_4,  λ_ICUR_5 = calibrated_parameters
        end

        # group parameters by age classes
        λ_IR  =  [λ_IR_1, λ_IR_2, λ_IR_3, λ_IR_4, λ_IR_5]

        λ_IH   = [λ_IH_1, λ_IH_2, λ_IH_3, λ_IH_4, λ_IH_5]

        λ_HICU = [λ_HICU_1, λ_HICU_2, λ_HICU_3, λ_HICU_4, λ_HICU_5]

        λ_HR   = [λ_HR_1, λ_HR_2, λ_HR_3, λ_HR_4, λ_HR_5]

        λ_ICUD = [λ_ICUD_1, λ_ICUD_2,  λ_ICUD_3, λ_ICUD_4, λ_ICUD_5]

        λ_ICUR = [λ_ICUR_1, λ_ICUR_2, λ_ICUR_3, λ_ICUR_4, λ_ICUR_5]

        # State variables

        # Susceptibles
        S       =   @view u[5*0+1:5*1]
        # Exposed
        E       =   @view u[5*1+1:5*2]
        # Infected
        I       =   @view u[5*2+1:5*3]
        # Hospitalized
        H       =   @view u[5*3+1:5*4]
        # ICU occupancy
        ICU     =   @view u[5*4+1:5*5]
        # Cumulated Recovered
        R       =   @view u[5*5+1:5*6]
        # Daily Deaths ( age disaggregated)
        D       =   @view u[5*6+1:5*7]
        # Daily Hospistal admissions ( all those who get transfered to ICU are first admitted to the hospital )
        AdH     =   @view u[5*7+1:5*8]
        # Daily ICU admissions
        AdICU   =   @view u[5*8+1:5*9]

        # State variables differentials
        dS       =   @view du[5*0+1:5*1]
        dE       =   @view du[5*1+1:5*2]
        dI       =   @view du[5*2+1:5*3]
        dH       =   @view du[5*3+1:5*4]
        dICU     =   @view du[5*4+1:5*5]
        dR       =   @view du[5*5+1:5*6]
        dD       =   @view du[5*6+1:5*7]
        dAdH     =   @view du[5*7+1:5*8]
        dAdICU   =   @view du[5*8+1:5*9]

        # Force of infection
        Λ =  β * μ .* [sum([C_5[i,j]*(I[j])/N_5[j] for j in 1:size(C_5)[1]]) for i in 1:size(C_5)[2]]  #β

        # System of equations

        @. dS   = - Λ*S

        @. dE   = Λ*S - ϵ*E

        @. dI   =  ϵ * E - ((1 - η )*λ_IR + η* λ_IH)*I

        @. dH   = η* λ_IH * I - (χ * λ_HICU + ( 1- χ ) * λ_HR ) * H

        @. dICU = λ_HICU * χ * H - (δ_ICU * λ_ICUD + (1 - δ_ICU) * λ_ICUR) * ICU

        @. dR   = (1 - η ) * λ_IR * I + (1-χ)*λ_HR*H + (1-δ_ICU)*λ_ICUR*ICU

        @. dD   =  δ_ICU*λ_ICUD*ICU

        @. dAdH     =  η * λ_IH * I

        @. dAdICU   =  λ_HICU * χ * H

    end
end;

Model initial conditions, contact matrix and population:
# Initial conditions.
# contact matrix

const C_5 = [2.87954   3.07131  2.21196  0.343359  0.256795;
             2.93036   4.6993   5.49855  1.01668   0.233958;
             1.53385   3.99626  2.88881  1.00161   0.631737;
             0.597362  1.85386  2.51295  1.41536   0.943012;
             0.402476  0.38432  1.42786  0.849536  7.48054e-5 ]

# age-stratified population
const N_5             = [922868, 967257, 1330871, 530458, 588825]
# number of age classes
const num_age_classes = length(N_5)
# initial infected
const I₀              = repeat([5],num_age_classes)
# initial susceptibles
const S₀              = N_5 .- I₀
# initial exposed
const E₀              = [0 for n in 1:num_age_classes]
# initial hospitalized
const H₀              = [0 for n in 1:num_age_classes]
# initial ICUs
const ICU₀            = [0 for n in 1:num_age_classes]
# initial recovered
const R₀              = [0 for n in 1:num_age_classes]
# initial deaths
const D₀              = [0 for n in 1:num_age_classes]
# initial hopsitalizal admissons
const AdH₀            = [0 for n in 1:num_age_classes]
# initial ICU admissions
const AdICU₀          = [0 for n in 1:num_age_classes]
# collect initial condition in an array for the SEIH_ICU_RD! model
const B = vcat([S₀, E₀, I₀, H₀, ICU₀, R₀, D₀, AdH₀, AdICU₀ ]...);

Model initial parameter values:
# Model intial parameter values.

# The following values have been derived from literature and consitute the initial condition for the parameters ( epidemiological delays) to be calibrated
const P = [ 0.15,
            0.1724137931034483,
            0.5, 0.5, 0.5, 0.5, 0.5,
            0.11834005925895003, 0.11834005925895003, 0.11834005925895003, 0.12104523689190094, 0.12104523689190094,
            0.3846153745721452, 0.3846153745721452, 0.3846153745721452, 0.3846153745721452, 0.3846153745721452,
            0.1111111111111111, 0.1111111111111111, 0.1111111111111111, 0.1111111111111111, 0.1111111111111111,
            0.08522883763258698, 0.08522883763258698, 0.08522883763258698, 0.08522883763258698, 0.08522883763258698,
            0.04947445517352199, 0.04947445517352199, 0.04947445517352199, 0.04947445517352199, 0.04947445517352199 ]

#The following values have been derived from literature and consitute the initial condition for the parameters ( epidemiological delays) that must remain constant and thus they are not to be calibrated

# susceptibility
const μ     = [ 0.4759758925436791 ,0.8266397761918497 ,0.8280047127031845 ,0.8108310931308417 ,0.7399999999999999]

# hospitalization rate
const η     =  [0.0027585284135976107 ,0.032802784575350706 ,0.10232295466653041 ,0.20404289877803708 ,0.261949855298025]

# ICU fraction
const χ     = [ 0.05 ,0.053934808432505525 ,0.1401166566857344 ,0.35206205203805013 ,0.6069703305850978]

# ICU conditioned fatality rate
const δ_ICU =  [0.007842851966738704, 0.018512721107622265, 0.06495525917707529, 0.1850599579504777, 0.45689350535412815];

Model parameter priors
# model uninformative priors

const priors = [ Uniform(0.11, 0.29) ,
                Uniform(0.08608442196509436, 0.4459389648119829) ,
                Uniform(0.05, 0.95) ,Uniform(0.05, 0.95) ,Uniform(0.05, 0.95) ,Uniform(0.05, 0.95) ,Uniform(0.05, 0.95) ,
                Uniform( 0.05756513737673442, 0.8451135758017284) ,Uniform(0.05756513737673442, 0.8451135758017284) ,Uniform(0.05756513737673442, 0.8451135758017284) ,Uniform(0.05699050074851731, 0.978307745097927) ,Uniform( 0.05699050074851731, 0.978307745097927) ,
                Uniform(0.0717764830429439, 20.0) ,Uniform(0.0717764830429439, 20.0) ,Uniform(0.0717764830429439, 20.0) ,Uniform( 0.0717764830429439, 20.0) ,Uniform(0.0717764830429439, 20.0) ,
                Uniform(0.06825938566552901, 0.11976047904191617) ,Uniform(0.06825938566552901, 0.11976047904191617) ,Uniform( 0.06825938566552901, 0.11976047904191617) ,Uniform(0.06825938566552901, 0.11976047904191617) ,Uniform(0.06825938566552901, 0.11976047904191617) ,
                Uniform(0.033601109960270686, 0.6397852910389515) ,Uniform( 0.033601109960270686, 0.6397852910389515) ,Uniform(0.033601109960270686, 0.6397852910389515) ,Uniform(0.033601109960270686, 0.6397852910389515) ,Uniform(0.033601109960270686, 0.6397852910389515) ,
                Uniform( 0.015723763849568886, 1.397487888396577) ,Uniform(0.015723763849568886, 1.397487888396577) ,Uniform(0.015723763849568886, 1.397487888396577) ,Uniform(0.015723763849568886, 1.397487888396577) ,Uniform( 0.015723763849568886, 1.397487888396577) ]

Time span and time interval we are going to calibrate and solve within:
# time span
const t = 1:30
# time interval
const T = (1.0, 30.0)

Hard coded calibration data. Each timeseries coresponds to an age class.
# calibration data
const H_calibration_data = vcat([
                            [ 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.005517056827195221, 0.005517056827195221, 0.005517056827195221, 0.005517056827195221, 0.019309698895183275, 0.019309698895183275, 0.03586086937676894, 0.03861939779036655, 0.04413645461756177, 0.10758260813030682, 0.16551170481585664, 0.23999197198299213, 0.4082622052124464, 0.799973239943307, 0.7503197284985501, 1.026172569858311, 1.0868601949574586, 1.282715712322889, 1.906143133795949, 1.8978675485551562, 2.474399986997057, 3.3957484771386586, 4.369509007138616, 5.536366526090404],
                            [ 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.06560556915070141, 0.06560556915070141, 0.06560556915070141, 0.06560556915070141, 0.22961949202745494, 0.22961949202745494, 0.4264361994795592, 0.45923898405490987, 0.5248445532056113, 1.2793085984386776, 1.9681670745210424, 2.8538422580555114, 4.854812117151904, 9.512807526851704, 8.922357404495392, 12.202635862030462, 12.924297122688179, 15.253294827538078, 22.66672414156734, 22.568315787841286, 29.424097764089584, 40.38022781225672, 51.95961076735552, 65.83518864272887],
                            [ 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.20464590933306082, 0.20464590933306082, 0.20464590933306082, 0.20464590933306082, 0.7162606826657129, 0.7162606826657129, 1.3301984106648952, 1.4325213653314257, 1.6371672746644865, 3.990595231994686, 6.139377279991825, 8.902097055988145, 15.1437972906465, 29.673656853293817, 27.83184366929627, 38.06413913594931, 40.31524413861298, 47.58017391993664, 70.70516167457251, 70.39819281057292, 91.78369033587778,<PHONE_NUMBER>9449893,<PHONE_NUMBER>9178417,<PHONE_NUMBER>1572652],
                            [ 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.40808579755607416, 0.40808579755607416, 0.40808579755607416, 0.40808579755607416, 1.4283002914462595, 1.4283002914462595, 2.6525576841144822, 2.856600582892519, 3.2646863804485933, 7.957673052343446, 12.242573926682224, 17.751732193689225, 30.19834901914949, 59.17244064563075, 55.49966846762609, 75.9039583454298, 80.39290211854662, 94.87994793178724,<PHONE_NUMBER>5562364,<PHONE_NUMBER>592895,<PHONE_NUMBER>0389927,<PHONE_NUMBER>9576366,<PHONE_NUMBER>6441074,<PHONE_NUMBER>475204],
                            [ 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.52389971059605, 0.52389971059605, 0.52389971059605, 0.52389971059605, 1.833648987086175, 1.833648987086175, 3.405348118874325, 3.66729797417235, 4.1911976847684, 10.216044356622975, 15.7169913178815, 22.789637410928176, 38.7685785841077, 75.96545803642725, 71.2503606410628, 97.4453461708653,<PHONE_NUMBER>8742185,<PHONE_NUMBER>1358162,<PHONE_NUMBER>1093528,<PHONE_NUMBER>4504122,<PHONE_NUMBER>0232844,<PHONE_NUMBER>7186877,<PHONE_NUMBER>920716,<PHONE_NUMBER>831362]
                            ])

const ICU_calibration_data = vcat([
                            [ 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.1, 0.1, 0.15000000000000002, 0.65, 0.8500000000000001, 1.5, 1.9000000000000001, 2.25, 2.5, 3.3000000000000003, 3.75, 4.8500000000000005, 6.75, 7.5, 8.55, 9.3, 10.3, 11.350000000000001],
                            [ 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.10786961686501105, 0.10786961686501105, 0.16180442529751657, 0.7011525096225718, 0.9168917433525939, 1.6180442529751657, 2.0495227204352098, 2.4270663794627487, 2.696740421625276, 3.5596973565453647, 4.045110632437915, 5.231676417953036, 7.281199138388246, 8.09022126487583, 9.222852241958444, 10.031874368446028, 11.110570537096137, 12.243201514178754],
                            [ 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.2802333133714688, 0.2802333133714688, 0.4203499700572032, 1.8215165369145472, 2.381983163657485, 4.203499700572031, 5.324432954057907, 6.305249550858048, 7.0058328342867195, 9.24769934125847, 10.50874925143008, 13.591315698516237, 18.91574865257414, 21.01749850286016, 23.95994829326058, 26.061698143546597, 28.864031277261283, 31.806481067661707],
                            [ 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.7041241040761003, 0.7041241040761003, 1.0561861561141503, 4.576806676494652, 5.9850548846468525, 10.561861561141503, 13.378357977445905, 15.842792341712256, 17.603102601902506, 23.23609543451131, 26.40465390285376, 34.15001904769086, 47.52837702513677, 52.80930780570752, 60.20261089850657, 65.48354167907732, 72.52478271983833, 79.91808581263739],
                            [ 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 1.2139406611701955, 1.2139406611701955, 1.8209109917552933, 7.8906142976062705, 10.318495619946662, 18.209109917552933, 23.064872562233713, 27.313664876329398, 30.348516529254887, 40.060041818616455, 45.522774793882334, 58.87612206675448, 81.9409946289882, 91.04554958776467,<PHONE_NUMBER>3005171,<PHONE_NUMBER>8882819,<PHONE_NUMBER>0053013,<PHONE_NUMBER>428172]
                                ])

const D_calibration_data = vcat([
                            [ 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.01568570393347741, 0.03137140786695482, 0.03921425983369352, 0.03921425983369352, 0.10195707556760315, 0.13332848343455797, 0.1646998913015128, 0.2039141511352063, 0.3607711904699804, 0.46272826603758355, 0.635271009305835, 0.8705565683079962, 1.0430993115762477, 1.2077992028777604],
                            [ 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.03702544221524453, 0.07405088443048906, 0.09256360553811133, 0.09256360553811133, 0.24066537439908944, 0.3147162588295785, 0.38876714326006756, 0.4813307487981789, 0.8515851709506241, 1.0922505453497136, 1.4995304097174034, 2.0549120429460714, 2.4621919073137613, 2.8509590505738287],
                            [ 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.12991051835415057, 0.25982103670830115, 0.32477629588537643, 0.32477629588537643, 0.8444183693019787, 1.1042394060102798, 1.364060442718581, 1.6888367386039573, 2.9879419221454633, 3.8323602914474417, 5.261375993343099, 7.210033768655356, 8.639049470551013, 10.003109913269594],
                            [ 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.3701199159009554, 0.7402398318019108, 0.9252997897523885, 0.9252997897523885, 2.4057794533562102, 3.146019285158121, 3.886259116960032, 4.8115589067124205, 8.512758065721973, 10.918537519078184, 14.989856593988693, 20.541655332503023, 24.61297440741353, 28.499233524373565],
                            [ 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.9137870107082563, 1.8275740214165126, 2.2844675267706407, 2.2844675267706407, 5.939615569603666, 7.767189591020179, 9.594763612436692, 11.879231139207333, 21.017101246289894, 26.95671681589356, 37.00837393368438, 50.715179094308226, 60.766836212099044, 70.36159982453573]
                                ])

You may check that the model compiles and runs correctly
# you may check it works
problem = ODEProblem(SEIH_ICU_RD!(calibrated_parameters = Float64[]) , B, (1.0, 120.0), P)
solution = solve(problem, Tsit5(), saveat = 1:120);
plot(solution.t, [slice[6] for slice in solution.u ])

And we can also optimize it via ModelingToolkit.jl:
# and you can toolktize it to get 5x better solve performance
fast_problem = ODEProblem(modelingtoolkitize(problem), B, (1.0, 120.0), P)
fast_solution = solve(fast_problem, Tsit5(), saveat = 1:120);
plot(fast_solution.t, [slice[6] for slice in fast_solution.u ])

Now to the calibration. We will show that the model is "calibratable" with these data by using Optim via DiffeentialEquations.jl. It may also be useful to get starting values for other optimization algorithms.
# prepare data ( and convert them to Int)
const optim_data = convert(Array,convert(Array, VectorOfArray([Array{Int64,1}(floor.(data)) for data in vcat(H_calibration_data, ICU_calibration_data, D_calibration_data) ]))')

# define indexes w.r.t. compare the data
const save_idxs = vcat(5*3+1:5*4, 5*4+1:5*5 ,5*6+1:5*7);

# set bounds for FminBox
const lower = [uniform.a for uniform in priors];
const upper = [uniform.b for  uniform in priors];

problem = ODEProblem(SEIH_ICU_RD!(calibrated_parameters = Float64[]) , B, T, P)
fast_problem = ODEProblem(modelingtoolkitize(problem), B, T, P; jac = true, sparse = true)
cost_function = build_loss_objective(fast_problem,Tsit5(),L2Loss(t,optim_data), maxiters=5*10^7,verbose=true, save_idxs=save_idxs)

result_Optim = @time Optim.optimize(  cost_function,lower,upper, P, Optim.Fminbox(BFGS()) ,Optim.Options(show_trace = false , iterations =  200,time_limit = 180)) # will take approx 1 minute and a half.

One may plot the simuated trajectories using the calibrated parameters togheter with the data used to calibrate
# get calibrated parameters
const P_optim = result_Optim.minimizer;

# get the soluton with calibrated parameters
const optim_calibrated_solution = solve(fast_problem , Tsit5(); p = P_optim , saveat = 1:30 );

# plot solution using calibrated parameters togheter with calibration points
# check that calibration was somewhat successful: please keep in mind that the data are fake, and the time series that are poorly reproduced by  the model tend to have a maximum value of <10, so they are probably ignored by the loss during calibration. Anyway there are techniques to account for it, but we'll omit them here for the sake of simplicity.
plots =[]
for (i, idx) in enumerate(save_idxs)
    p = plot(optim_calibrated_solution.t , [optim_calibrated_solution.u[j][idx] for j in t], size = (1400, 3000), label = "simulated")
    plot!(optim_calibrated_solution.t , optim_data[i,:], seriestype = :scatter , label = "data")
    push!(plots, p)
end
plot(plots..., layout = (length(plots), 1))

now let's try to calibrate using NUTS. This is the Turing model we are using:
# now let's write down the turing model we are currently using
@model function turing_model(data::Array{Int64,2} , problem::ODEProblem, priors , save_idxs::Array{Int64,1} ,  𝒯::Tuple{Float64,Float64} , ::Type{T} = Float64  ) where {T}
    σ ~ InverseGamma(2, 3)

    p ~ arraydist(priors)

    predicted::Vector{Vector{T}}  = solve(problem, Tsit5(), p = p, saveat=𝒯[1]:𝒯[2]).u

    # when the solve doesn'y converge, predicted has length 1. We detect it, and return -Inf loglikelihood to reject the sample.
    if length(predicted) == size(data, 2)
        for i = 1:length(predicted)
            data[:,i] ~ MvNormal(predicted[i][save_idxs], σ)
        end
    else
        Turing.@addlogprob! -Inf
        return
    end

end

Let's calibrate the model:

# instamtiate turing model
tur_mod = turing_model(optim_data, fast_problem, priors, save_idxs, T )

# sample from posterior. It takes approx 5 minutes
chain = @time sample(tur_mod, NUTS(), 1000)   # using MCMCThreads() over multilple chains seriously slows it  down. Should one use MCMCDistributed() preferably?

Get the parameters and check it correctly calibrated the  time series:

# get the parameters
P_turing = vcat([Statistics.mean(chain["p[$i]"]) for i in 1:32])

# evaluate the solution with such parameters
const turing_calibrated_solution = solve(fast_problem , Tsit5(); p = P_turing , saveat = 1:30 );

# plot
plots =[]
for (i, idx) in enumerate(save_idxs)
    p = plot(turing_calibrated_solution.t , [turing_calibrated_solution.u[j][idx] for j in t], size = (1400, 3000), label = "simulated")
    plot!(turing_calibrated_solution.t , optim_data[i,:], seriestype = :scatter , label = "data")
    push!(plots, p)
end
plot(plots..., layout = (length(plots), 1))

We can also try ADVI

advi = ADVI(10, 10000)
q = @time vi(tur_mod, advi)  #about 80 seconds

Sample from the multivariate posteriors and plot the simulations togheter with the data
# sample from the posterior
extractions_advi = [rand(q) for i in 1:10000] ;

#evaluate the parameter values
P_advi = [Statistics.mean([extraction[i] for extraction in extractions_advi]) for i in 2:33]

# get the advi calibrated solution
const advi_calibrated_solution = solve(fast_problem, Tsit5(); p = P_advi , saveat = 1:30 );

# plot advi results
plots =[]
for (i, idx) in enumerate(save_idxs)
    p = plot(advi_calibrated_solution.t , [advi_calibrated_solution.u[j][idx] for j in t], size = (1400, 3000), label = "simulated")
    plot!(advi_calibrated_solution.t , optim_data[i,:], seriestype = :scatter , label = "data")
    push!(plots, p)
end
plot(plots..., layout = (length(plots), 1))

So trying also other models it seems that NUTS performs generally better than ADVI, but we are far from sure.
How would you calibrate this 32-parameter model? What exact setup would you use? Could you please present your practical reasoning, so that non-domain experts may try to reproduce it in other scenarios?
Thanks in advance

Completely unrelated comment: you should specify save_idxs as a keyword argument to solve.

Completely unrelated comment: you should specify save_idxs as a keyword argument to solve.


If the server is closed, the game.html should return to the homepage

Current code exits on every error, I think, need to make sure it only works on server close.

I'll doc your code for you this time ;)

I just had this issue again, but in chrome


alibabacloud: use NextToken and MaxResults to list instance types

Currently, there is no paging query used to retrieve instance types. When there are many instance types, some instances can not obtain ENI and IPPerENI limits. The cilium operator log is as follows.
level=warning msg="Unable to maintain ip pool of node" error="Unable to determine limits" instanceID=<ID> name=<NAME> subsys=ipam

This patch fixes this problem by using NextToken and MaxResults for paging query.
Fix bug in AlibabaCloud where instance type limits could not be determined

/test

/test

Hi @christarazi @sayboras , please help to see if this PR can be merged.

@haozhangami Could you rebase on PR on latest main so we can re-run the CI?

@haozhangami Could you rebase on PR on latest main so we can re-run the CI?

Done

/test


get_ntp_peers() for Pluribus

https://github.com/napalm-automation/napalm-base/pull/13

Can you enable the test?


New custom metrics functionality

After talking today with @jservonnat we discussed a clearer path forward for custom metrics.. On a 1.1, 1.5, 2.0 release timeline..  Considering changes in milestones:
Stage 1 - 1.1 milestone timeline (using current obs/model seasonal climatologies):

[ ] Add new variables (@jservonnat has tested this for jet latitude - should this be included in standard suite?)
[x] Add new obs through custom obs dictionary (@doutriaux has fixed with #244)
[ ] Handling multiple custom metrics through a new dictionary (@doutriaux has proposed fix #243 in response to #220)
[ ] Pass complete variable name to compute_metrics (#229, #240)
[ ] Add variable to JSON output file (#226)
[ ] Append info for default and custom_metrics at bottom of JSON file (#221)

Stage 2 - 1.5 milestone timeline:

[ ] Using regional masks (land surface - vegetation) ; consider interactions with ILAMB - IPSL will provide rapid feedback on this, they want to do this now with IPSL output (Note interpolation with integer vegetation zones will not work here)

Stage 3 - 2.0 milestone timeline (new input data formats):

[ ] Using timeseries inputs (obs/models)
[ ] Working with native grid data (as above, land-surface and also ocean transports etc when interpolation doesn't make sense..)

It's likely there is some interaction with the list above and #87, #219, #232

I think for 2.0, we should switch the obs to an esgf-served format. Should we create an issue for this?

I forgot those points:

[] handling multiple custom compute_metrics functions (related with #220)
[] pass the complete variable name to the compute_metrics function (#229)
[] provide detailed information about the calculated metrics at the bottom of the json file (#221)

For you guys @doutriaux1 @durack1 @gleckler1: after the development (currently in test) of the metric on the latitude of the jets I would like to move on with metrics on sea ice and some others on the ocean. However, there is quickly the need to use multiple variables (for example, to calculate the sea ice volume). Also, that would be better to do those computations on the native grid.
I would be happy to help on the development of a version of the Metrics Package that could do all those things (in parallel of the official, working version). So here is my point: are you guys ready to start working on those functionalities (pretty much stage 3 of the milestones defined by @durack1 above) or you prefer to leave it for later on? If you are at least ready to discuss about the ways those functionalities can be developed, I'll be happy to put my hands in the code to try to implement them.
Let me know!


Sig fix

Please check if the PR fulfills these requirements

[x] This PR addresses an already opened issue (for bug fixes / features) #128
[x] Tests for the changes have been added (for bug fixes / features)

What kind of change does this PR introduce? (Bug fix, feature, docs update, etc.)

Copy compute signature to call method of Indicator class.
Add tests

Pull Request Test Coverage Report for Build 367

2 of 2 (100.0%)  changed or added relevant lines in 1 file are covered.
1 unchanged line in 1 file lost coverage.
Overall coverage decreased (-0.2%) to 84.906%

Files with Coverage Reduction
New Missed Lines
%

xclim/utils.py
1
95.77%

Totals

Change from base Build 366:
-0.2%

Covered Lines:
630

Relevant Lines:
742

💛  - Coveralls


add ros2 control hardware

adapt to ros2_control

ros2 launch mgs1600gy_bringup hardware.launch.py dev:=
This command above can launch ros2_control mgs1600gy hardware.

@m12watanabe1a
I finished implementation.


API to call methods from component

Would be good we have a service to cal the methods from a a component.
Ex:
ScrollToService.to(href ,targetSelector, scrollableElementSelector, scrollYTarget, offset);

Good idea. I will work on this the next weekend.

Hello, we have this :D?

Sorry, i  have a lot to do at work at the moment. Since i'm busy at work i can't make any promises, but i'll try to work on this(and others :-)) issue as sooner as possible.


Dependencies update. Clippy polish.

Hello there!
I've made some efforts to keep gbdt-rs up to date. Any feedback is welcome!
Motivation

time 0.1 is really outdated.
Modern clippy detects a lot of non-critical warnings in gbdt-rs.
One of the doc-tests is broken.

Plan

[x] Update dependencies: rand, cfg-if.
[x] Remove extra dependency: replace time by std (output LGTM).
[x] Pass all tests.

Thanks for the contribution!

@npatsakula do you need us cargo publish it?

@dingelish that would be nice of you!

cargo publish is done. Thanks again!


comments to latest PR

https://github.com/LLazyEmail/markdown-regex/pull/163
https://user-images.githubusercontent.com/1469198/180204707-6fde03a1-cc80-451d-9022-ab33baf61d67.mp4

added #171

some files still without content, such as
br
em
empty-ol
empty-ul
paragraph
Also, please check if i was correct whith files, wich have long content text. Such as
header
image
link
ol-list
strong

will take a look

br located in #171

em also have necessary data, #215

paragraph, few paragraphs added

we have few headers here: https://raw.githubusercontent.com/LLazyEmail/markdown-regex/main/tests/header/content.md
done.

images get fixed
done

link is fine

ol-list is fine
strong is fine
@Olgalex im closing this task, but please do a sync of your version as i did some code changes.
Can you also take a look through all files and confirm here that all content.md files have necessary data inside?


Improve / refactor tests

A suggestion for a few things that could be improved:

Always use wrap (see https://github.com/apollostack/apollo-client/pull/634/commits/32f953d1a1069b653f54d11f686dd40d01bf3fe9) in query observers, or return promises from tests, so we don't have to wait on timeouts and get unhelpful errors when they fail.

Refactor QueryManager tests into several describe sections, maybe in separate files?

Also re-use query, variable and result arguments to ramp down the verbosity.

Use sinon's timing stuff everywhere rather than using timeouts.

It may not be a good idea to do the sinon stuff, see https://github.com/apollostack/apollo-client/pull/635#discussion_r80025786


Declaration of Cachable::newBelongsToMany should be compatible with Model::newBelongsToMany

Describe the bug
I got the below error when I installed on laravel 8.
Warning: Declaration of GeneaLabs\LaravelModelCaching\Traits\Cachable::newBelongsToMany(GeneaLabs\LaravelModelCaching\EloquentBuilder $query, Illuminate\Database\Eloquent\Model $parent, $table, $foreignPivotKey, $relatedPivotKey, $parentKey, $relatedKey, $relationName = NULL) should be compatible with Illuminate\Database\Eloquent\Model::newBelongsToMany(Illuminate\Database\Eloquent\Builder $query, Illuminate\Database\Eloquent\Model $parent, $table, $foreignPivotKey, $relatedPivotKey, $parentKey, $relatedKey, $relationName = NULL) in /var/www/jianghu_entertain/app/Models/BaseModel.php on line 14

Environment

PHP: 7.4.11
OS: Ubuntu 18.04
Laravel: 8.10.0
Model Caching: 0.11.0

Additional context

Hi @harrisdt15f, just curious, why did you close this? I want to make sure I have everything covered.
Thanks :)


metric for enformer

Hello, can I ask how you find of the human pearson R is 0.625 for validation, and 0.65 for test? Couldn't find any information in the paper. Is there any other place that records this?

Sorry for reviving and old thread, but I'd also like to know where these correlation numbers come from with respect to the original paper. It looks like @jstjohn did the correlation analysis here. Would be able to shed some light on the question?

I don't think the calculation of Pearson correlation coefficient in the Enformer TensorFlow version is correct (at least in the pipeline they provided:). They first calculated the covariance and standard deviation of the true and predicted values within each batch, but did not calculate the Pearson correlation coefficient. Instead, they waited until all batches had calculated the "temporary values" before calculating the Pearson correlation coefficient for the "population". There is no doubt that the "temporary values" are nonlinear, so this will introduce erroneous results.

Let's assume the data are as follows:
batch1 : input1, target1
batch2 : input2, target2
batch3 : input3, target3
The idea behind calculating Pearson correlation coefficient using the original TensorFlow version of the enformer is as follows:
cor(c(input1,input2,input3),c(target1,target2,target3))
The idea behind calculating Pearson correlation coefficient using the original Pytorch version of the enformer is as follows:
mean(cor(input1,target1),cor(input2,target2),cor(input3,target3))
I think the second option is reasonable.

Why is the second better? Here each input and target is a different batch along the sequence axis. Taking the global correlation of points is a correlation metric while the mean of subsequence correlations (with arbitrary cut points even) is something else that needs more justification in my opinion. Sent from my iPhoneOn Sep 29, 2024, at 7:40 AM, Eli @.***> wrote:
Let's assume the data are as follows:
batch1 : input1, target1
batch2 : input2, target2
batch3 : input3, target3
The idea behind calculating Pearson correlation coefficient using the original TensorFlow version of the enformer is as follows:
cor(c(input1,input2,input3),c(target1,target2,target3))
The idea behind calculating Pearson correlation coefficient using the original Pytorch version of the enformer is as follows:
mean(cor(input1,target1),cor(input2,target2),cor(input3,target3))
I think the second option is reasonable.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: @.***>

Sorry, I think you're right. Calculating the correlation based on batches and then taking the average is not a good idea as it ignores the global distribution of the data.

Why is the second better? Here each input and target is a different batch along the sequence axis. Taking the global correlation of points is a correlation metric while the mean of subsequence correlations (with arbitrary cut points even) is something else that needs more justification in my opinion. Sent from my iPhoneOn Sep 29, 2024, at 7:40 AM, Eli @.> wrote: Let's assume the data are as follows: batch1 : input1, target1 batch2 : input2, target2 batch3 : input3, target3 The idea behind calculating Pearson correlation coefficient using the original TensorFlow version of the enformer is as follows: cor(c(input1,input2,input3),c(target1,target2,target3)) The idea behind calculating Pearson correlation coefficient using the original Pytorch version of the enformer is as follows: mean(cor(input1,target1),cor(input2,target2),cor(input3,target3)) I think the second option is reasonable. —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: @.>

Interesting.  Taking the mean after splitting on a nuisance variable on the other hand could make a ton of sense. That could help control for confounding for example. You could cut the data up by something you don’t want to be included in your correlation measurement. Chromosome boundary for example, maybe GC percent bucket or some other feature you think is a nuisance variable that is not biologically meaningful. Then you could calculate correlation within each group and average. Smaller groups though might be noisier which would make real signals harder to detect. Just some other thoughts!Sent from my iPhoneOn Sep 29, 2024, at 7:07 PM, Eli @.***> wrote:
Sorry, I think you're right. Calculating the correlation based on batches and then taking the average is not a good idea as it ignores the global distribution of the data.
2e3d512f6e1e61a2916bf4584a93309.jpg (view on web)
Why is the second better? Here each input and target is a different batch along the sequence axis. Taking the global correlation of points is a correlation metric while the mean of subsequence correlations (with arbitrary cut points even) is something else that needs more justification in my opinion. Sent from my iPhoneOn Sep 29, 2024, at 7:40 AM, Eli @.> wrote: Let's assume the data are as follows: batch1 : input1, target1 batch2 : input2, target2 batch3 : input3, target3 The idea behind calculating Pearson correlation coefficient using the original TensorFlow version of the enformer is as follows: cor(c(input1,input2,input3),c(target1,target2,target3)) The idea behind calculating Pearson correlation coefficient using the original Pytorch version of the enformer is as follows: mean(cor(input1,target1),cor(input2,target2),cor(input3,target3)) I think the second option is reasonable. —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: @.>
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: @.***>

Thanks! That helps a lot!


Automated Package Upgrade

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


[AERIE-1906] Resolve LGTM errors

Tickets addressed: AERIE-1906
Review: By commit
Merge strategy: Merge (no squash)

Description
Resolves LGTM errors reported here.
Verification
All tests passing.
Documentation
None.
Future work
Resolve LGTM warnings (see https://lgtm.com/projects/g/NASA-AMMOS/aerie/alerts/?mode=tree).

By the way, the Javadoc for SerializedValue still refers to its ancient previous name, SerializedParameter. Could you update that in this PR by any chance? 🙏

By the way, the Javadoc for SerializedValue still refers to its ancient previous name, SerializedParameter. Could you update that in this PR by any chance? 🙏

Done :)

There's an interesting failure I'm looking into now:
Method 'gov.nasa.jpl.aerie.merlin.protocol.types.SerializedValue gov.nasa.jpl.aerie.merlin.protocol.types.SerializedValue.of(double)' must be InterfaceMethodref constant
java.lang.IncompatibleClassChangeError: Method 'gov.nasa.jpl.aerie.merlin.protocol.types.SerializedValue gov.nasa.jpl.aerie.merlin.protocol.types.SerializedValue.of(double)' must be InterfaceMethodref constant
	at gov.nasa.jpl.aerielander.mappers.seis.ChannelRateValueMapper.serializeValue(ChannelRateValueMapper.java:42)
	at gov.nasa.jpl.aerielander.mappers.seis.ChannelRateValueMapper.serializeValue(ChannelRateValueMapper.java:12)
	at gov.nasa.jpl.aerie.merlin.framework.Registrar$1.serialize(Registrar.java:57)
	at gov.nasa.jpl.aerie.merlin.driver.engine.SimulationEngine.serializeProfile(SimulationEngine.java:616)
	at gov.nasa.jpl.aerie.merlin.driver.engine.SimulationEngine.computeResults(SimulationEngine.java:455)
	at gov.nasa.jpl.aerie.scheduler.simulation.IncrementalSimulationDriver.getSimulationResultsUpTo(IncrementalSimulationDriver.java:152)
	at gov.nasa.jpl.aerie.scheduler.simulation.SimulationFacade.computeSimulationResultsUntil(SimulationFacade.java:249)
	at gov.nasa.jpl.aerie.scheduler.solver.PrioritySolver.getConflicts(PrioritySolver.java:503)
	at gov.nasa.jpl.aerie.scheduler.solver.PrioritySolver.satisfyGoalGeneral(PrioritySolver.java:425)
	at gov.nasa.jpl.aerie.scheduler.solver.PrioritySolver.satisfyGoal(PrioritySolver.java:286)
	at gov.nasa.jpl.aerie.scheduler.solver.PrioritySolver.solve(PrioritySolver.java:245)
	at gov.nasa.jpl.aerie.scheduler.solver.PrioritySolver.getNextSolution(PrioritySolver.java:112)
	at gov.nasa.jpl.aerie.scheduler.AerieLanderRulesTest.schedule(AerieLanderRulesTest.java:43)
	at gov.nasa.jpl.aerie.scheduler.AerieLanderRulesTest.firstRule(AerieLanderRulesTest.java:51)

Not familiar with must be InterfaceMethodref constant, will dig deeper.

IncompatibleClassChangeError is like NoSuchMethodError in that it should only ever happen because you compiled code against one version of a class and then loaded it into a JVM with another. Make sure that your model JARs have been recompiled.

Ahh that's right! This JAR is likely the one that's causing this snag: scheduler/src/test/resources/gov/nasa/jpl/aerie/scheduler/aerie-lander-0.11.1-SNAPSHOT.jar.

Will diagnose the e2e test failures next week. I'm unable to get the e2e tests to pass on develop with:
$ docker-nuke aerie ; gradle clean assemble && docker-compose build && docker-compose up

followed by (in a separate shell):
$ cd e2e-tests
$ npm install && npm test

This results in:
  15 failed
    src/tests/health.test.ts:10:3 › Health › Hasura is healthy =====================================
    src/tests/mission-models.test.ts:8:3 › Mission Models › Upload mission model .jar file to the gateway
    src/tests/mission-models.test.ts:15:3 › Mission Models › Create mission model using the jar_id returned from the gateway
    src/tests/mission-models.test.ts:28:3 › Mission Models › Delete mission model ==================
    src/tests/scheduler.test.ts:16:3 › Scheduling › Upload jar and create mission model ============
    src/tests/scheduler.test.ts:34:3 › Scheduling › Create Plan ====================================
    src/tests/scheduler.test.ts:47:3 › Scheduling › Create Simulation ==============================
    src/tests/scheduler.test.ts:58:3 › Scheduling › Create Scheduling goal =========================
    src/tests/scheduler.test.ts:83:3 › Scheduling › Get Plan Revision ==============================
    src/tests/scheduler.test.ts:90:3 › Scheduling › Create Scheduling Specification ================
    src/tests/scheduler.test.ts:104:3 › Scheduling › Create Scheduling Specification Goal ==========
    src/tests/scheduler.test.ts:118:3 › Scheduling › Run scheduling ================================
    src/tests/scheduler.test.ts:135:3 › Scheduling › Get Plan ======================================
    src/tests/scheduler.test.ts:144:3 › Scheduling › Delete plan ===================================
    src/tests/scheduler.test.ts:152:3 › Scheduling › Delete mission model ==========================

Finally got the e2e tests figured out here :) Also note that #238 has been pulled out of this PR.


Is it possible to disable docblockr for //

In Javascript, I really like docblockr completing comments when I use /** however, it's also continuing comment blocks when I use // -- which I don't like. Is it possible to disable auto-comment-blocking for // comments? I'd like those to always be single-line.
Current behaviour:

Type //
Press Enter
Atom will create a new line with //

Desired behaviour:

Type //
Press Enter
Atom creates a blank new line

yes just untick the "Extend double slash" options in the package settings


Select line on go to definition

Feature_Name
Highlight
Description of the feature
It's currently quite hard to see what line go to sends you too, as the scrolling can sometimes be incorrect and there may be multiple functions of the same name and it is pain to check parameters. I would like to request that the line is selected so it's easier to see please :)

https://user-images.githubusercontent.com/21371686/147870774-31c53041-75b8-41fd-928c-5de2b69f4679.mp4
Something like this? Its already implemented in the 3X branch, but its only in a pre-release state at the moment.

Exactly! sorry i didn't know this was already in dev but thank you for letting me know

NP, most of this stuff only is mentioned in the discord and on the temp tracking repo.
Also for awareness, I'm not currently adding anything new to the 2X releases myself. PR's are welcome but I'm spending my time getting 3X to be ready for general usage. Got a ways to go but it'll be worth it in the end.

Good luck and thank you for your response 🙏
Sent from my iPhone

On 2 Jan 2022, at 08:54, Matt @.***> wrote:

NP, most of this stuff only is mentioned in the discord and on the temp tracking repo.
Also for awareness, I'm not currently adding anything new to the 2X releases myself. PR's are welcome but I'm spending my time getting 3X to be ready for general usage. Got a ways to go but it'll be worth it in the end.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.
You are receiving this because you authored the thread.


CRM case stage not moving On-prem

Hi Microsoft community,
I am working on a case in Microsoft CRM and as as expected when you save a case on one stage it is supposed to move to next stage automatically I Configured my workflow and business Process flows to work accordingly, it is working on the cloud but not On-Prem, I download this workflow tool-msdyncrmWorkflowTools (<IP_ADDRESS>), which allows to move to next stage but it is failing On-prem. The previous workflow tool was working but it had phased out and needed an update but when i download this latest version the function to move to the next stage automatically had stopped moving, anybody with a solution.?

Hi Vaakura,
I need more details about your workflow, about your customizations, and about your CRM versions.
Please share me more details in order to try to help you.
thanks

Hi Demianrasko
My workflow is as any general concept to make the case move automatically when users meet required information, but it only moves after I refresh the page, I tried putting a time-bound with a java script code but it did not work, the CRM Version is  1612 (<IP_ADDRESS>) (DB <IP_ADDRESS>) on-premises,any comments,or solutions from your side??

Hi Demianrasko
My workflow is as any general concept to make the case move automatically
when users meet required information, but it only moves after I refresh the
page, I tried putting a time-bound with a java script code but it did not
work, the CRM Version is 1612 (<IP_ADDRESS>) (DB <IP_ADDRESS>) on-premises,any
comments,or solutions from your side??
On Wed, May 2, 2018 at 7:34 PM, Demian Adolfo Raschkovan <
<EMAIL_ADDRESS>wrote:

Hi Vaakura,
I need more details about your workflow, about your customizations, and
about your CRM versions.
Please share me more details in order to try to help you.
thanks
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/demianrasko/Dynamics-365-Workflow-Tools/issues/74#issuecomment-386058638,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AWjmQ_1cYsDEf_oJgkRImA1El5X6gAS6ks5tue4jgaJpZM4TGfHk
.

--
Vaakura Muhuka
Software Developer in the ERP Section
Software Services
Green Enterprise Solutions (Pty) Ltd
p: +264 753 8366
m: +264 818 477 316
f: +264 61 402 652
a: Unit 1 Garthanri Park, c/o Thorpe & Voigts Street,
P.O.Box 23719, Windhoek, Namibia
w: www.green.com.na
e<EMAIL_ADDRESS>

Hi Vaakura,
not sure how can I help. This should work as expected in online, so maybe you need to open a case with Microsoft to see if they can help.
I don't have an onprem environment to test this, sorry.
thanks


Getting decimal value from cells

Am attempting to load a number from a basic XLS file into a decimal. No matter what number format is used in the Excel file cell, the value comes out as a double. Some of the times, the value comes out correctly and can be converted, but as it's a floating point I sometimes get floating point issues.
ExcelDataReader has the method GetDecimal, inherited from IDataRecord. That suggests it should be possible. However, within XlsxWorksheet, the only place that seems to set the Cell Value is the result of calls to ConvertCellValue. That method does not appear to ever return decimals. Am I reading that correctly?
Is there anyway to avoid issues caused by returning doubles? I would really like to avoid having to perform rounding on the data being read.

Hi!
Are you reading XLS or XLSX?
In XLS files, numeric values are physically stored as doubles, and ExcelDataReader returns exactly the same binary value that Excel uses internally. (this is true in ExcelDataReader 3.0 and newer, earlier versions converted to string and back - make sure you are using a recent version!)
In XLSX, numeric values are serialized as strings in XML, and I was pretty sure Excel uses doubles internally and thus the value could be "safely" deserialized back into a double as well. But I'm only guessing here. One could make an argument to parse numeric values in XLSX into decimal instead for improved precision, although would be a breaking change. A small todo is checking the OpenXml spec which XSD type is specified for numeric values, this would typically correlate to a .NET type.
(IDataRecord is loosely based on what you might expect to get back from a general database store, and does not indicate any particular features of the Excel file format.)

I have the same issue. I have a column with three values
41083.27
94416.60
37599.20
Looking at it in Excel I see this number both in the input box and the cell itself. If I increase decimal places shown I do not see anything unexpected as detailed below.
When I read them in using AsDataSet or more directly I get
41083.270000000004
94416.60
37599.200000000004
If I take the file and save as csv, I get the numbers I expect without additional decimal places.
It turns out that this file came from a third party. If I open it, go to each cell, add a 0 and then backspace it out (thus made no real change) and save the file (simply saving the file isnt enough) it fixes the issue. Numbers come in as expected. If I only do it to one cell, it only fixes that one cell.  The original file had this issue and a test file which was a cut down of that original file with only the bad rows in it also had the issue.
I can't very well tell clients to do that whenever there is an issue in the validation of my reading of the data. So to "fix" it I read the formatted value of the cell. While not perfect, because there is the chance the format for the cell removes decimal places the person wants us to read in, we can justify this position better than telling the client to fix the data corruption, corruption they cannot readily see in Excel.
Ive attached a zip file. The issue is in the Gross Salary column. saveasnochanges.xsl shows the problem in the first and third rows. oncecell.xsl shows the third row fixed by as I stated, putting a 0 in the cell data and then backspacing it out again, (therefore making no real changes) and saving.
Temp.zip

@jrigsby
From a quick test, it looks like Excel always truncates numbers to 15 digits. So if you enter a number like<PHONE_NUMBER>23456789 it gets changed to<PHONE_NUMBER>23456000, or 1.23456789123456789 gets changed to 1.23456789123456 even though they can be represented as a 64 bit floating-point value just fine, which is what Excel uses internally to store numbers as @andersnm wrote above. This seems to be done both before a value is formatted to be shown and when a cell edit is committed. The tool that created the attached file probably just saved the value as is from however it calculated it.
Would be a big change and we'd have to be careful to get the behavior correct in all cases if we decide to attempt to emulate Excel, and probably make it something you opt-in to. I'm not sure it is worth it at all really.

I have the same issue, or at least potentially as I thought it was a floating point issue hence Im adding it to this report. If it should be its own I apologize. I have a column with three values
41083.27 94416.60 37599.20
Looking at it in Excel I see this number both in the input box and the cell itself. If I increase decimal places shown I do not see anything unexpected as detailed below.
When I read them in using AsDataSet or more directly I get 41083.270000000004 94416.60 37599.200000000004
If I take the file and save as csv, I get the numbers I expect without additional decimal places. If I save as to Xlsx and use EPPlus to read, I get the same extra decimal places.
It turns out that this file came from a third party. If I open it, go to each cell, add a 0 and then backspace it out (thus made no real change) and save the file (simply saving the file isnt enough) it fixes the issue. Numbers come in as expected. If I only do it to one cell, it only fixes that one cell. The original file had this issue and a test file which was a cut down of that original file with only the bad rows in it also had the issue.
I can't very well tell clients to do that whenever there is an issue in the validation of my reading of the data. So to "fix" it I read the formatted value of the cell. While not perfect, because there is the chance the format for the cell removes decimal places the person wants us to read in, we can justify this position better than telling the client to fix the data corruption, corruption they cannot readily see in Excel.
Ive attached a zip file. The issue is in the Gross Salary column. saveasnochanges.xsl shows the problem in the first and third rows. oncecell.xsl shows the third row fixed by as I stated, putting a 0 in the cell data and then backspacing it out again, (therefore making no real changes) and saving.
Temp.zip

You are getting these numbers 41083.270000000004 94416.60 37599.200000000004 because EPPlus applying default formatting and it adds numbers at the end.
You can use number formatting like given below where # means optional
ws.Cells[row, col].Style.Numberformat.Format = "##0.##########";

Or
// Find out column index
int index1 = GetColumnByName(workSheet, "Premium $");
workSheet.Column(index1).Style.Numberformat.Format = "##0.##########";
int index = GetColumnByName(workSheet, "Discount $");
workSheet.Column(index).Style.Numberformat.Format = "##0.##########";

static int GetColumnByName(ExcelWorksheet ws, string columnName)
{
    if (ws == null) throw new ArgumentNullException(nameof(ws));
    return ws.Cells["1:1"].First(c => c.Value.ToString() == columnName).Start.Column;
}


Replace the CircleCI build status badge with GHA badges

We no longer use CircleCI to test/build the tbtc code. We need to
replace the CircleCI build status badge in the projec'ts README with
the similiar badge for GitHub Actions build.
The badge has been replaced with the Solidity build badge (showing
status of the last Solidity workflow executed on master branch and
triggered by the push event).
The badges is displayed using shields.io tool, which was already
used for the Discord and docs badges.
Refs:
https://github.com/keep-network/keep-core/pull/2502
https://github.com/keep-network/keep-ecdsa/pull/835

Once this PR gets merged, we will need to update the #810 (changing branch used to display badges from master to main).
If the #845 gets merged before the #810, the aforementioned change would need to be done as part of #809.

@michalinacienciala please remember to update https://github.com/keep-network/tbtc/pull/810


Miniflux isn't sending API requests to external services

Actual behaviour
Miniflux isn't sending API requests to external services (both Wallabag and Shaarli, both self-hosted)
Expected behaviour
Sending the API request
Steps to reproduce

Install up-to-date releases of Miniflux, Shaarli, and Wallabag
Enable Wallabag and Shaarli's external services with properly configured parameters
Bookmark an item in Miniflux

Configuration

Miniflux version: 1.2.3
Database type and version: sqlite
PHP version: 7.1.11
OS: Windows 10 client, Fedora 26 server
Browser: Firefox

The issue was caused by an improperly configured hosts file on my end


代码优化

Coverage decreased (-0.2%) to 98.324% when pulling 18a695c081ca1dc8edd705ca07151a83585b911f on yangyan1012775:master into ce4a9c468708dd3d5bccc93116d7e03125d25a8f on rugao-web-fullstack:master.


Trying to override attributes on chef-client with --with-env

Version:
knife-push 1.0.2
Environment: ChefDK 0.19.6 on Windows server 2008; Chef server latest on Ubuntu 16.04.1 LTS
Scenario:
Trying to override attributes on chef-client with --with-env
Steps to Reproduce:

Develop a sample cookbook and try to print version defined in attributes file.
example : default['app_version'] = "1.8.91" (attributes/default.rb)
puts node['app_version'] (recipes/default.rb)
Run knife job start chef-client myhost --with-env '{"app_version": "1.8.111"}}' to override the attribute defined in cookbook

Attribute sent with --with-env should override default attribute in cookbook
Actual Result:
Default attribute in cookbook is not overwritten by --with-env attribute
Result : knife job completes without any error. But --with-env is not working

I got it. This is working as a OS environment variable on the chef-client node.
What's missing here is a clear documentation. The way we access it inside chef recipe should have been explained with example.
Here is how i use it inside attributes:
default['app_version'] = ENV['app_version'] ? ENV['app_version'] : "1.8.91"
and pass this as
knife job start chef-client  --with-env '{"app_version": "1.8.111"}}'


Increase the size of the bootloader

allows mbed-os export build CI to pass after merge of cmsis5

@sg- FYI

The STM32 parts that the Nucleo and Ublox use have 4x16K then 1x64K then 128K blocks in that order. So we can't use 192K, we have to go to 256K.


freesmug-chromium 46.0.2490.71

Thank you for the contribution. It was merged directly as 79ffdfae0fd059d0314fd7059bf04c2b91672ca2 to keep commit history cleaner. Your contribution is still credited to you.


Automated cherry pick of #6412

Cherry pick of #6412 on release-5.27.
/cc  @josephbaylon

Will try to auto merge this PR once all tests and checks are passing. This might take up to an hour.

Trying to auto merge this PR.

Pull Request successfully merged
SHA: 6a27b4e1d137de90b8f4d42ccd6dee0d16ffc5e3


CAMEL-10086 added GenericFileEndpoint.(include|exclude)Pattern for a …

…better reusage
This is part 2 of CAMEL-10086.
It follows on the suggestion from the ticket description:
GenericFileEndpoint could contain also excludePattern as well.
Please note couple of things:

This PR might not be considered complete because:

I'm not sure if javadoc should be added on the new methods in GenericFileEndpoint
Also I have only checked that the existing tests work as before and didn't investigate if/what needs to be updated
Any suggestions related to the above 2 lines would be appreciated

I have raised this PR to get a validation that this approach is good and can continue in this direction
This PR also contains some other cleanup that I noticed could be done

Its probably a little better to do separate commits for code changes and polish updates. Thats easier to review.

Thanks for the PR it has been merged. Do you mind closing this?

@davsclaus yeah, that makes sense and (usually, but apparently not always) I do the same.
Closing this as it the PR has been merged.


merge

Sorry, trying to figure out gmp not found error
On Wed, Jan 1, 2020, 6:41 PM PastaPastaPasta<EMAIL_ADDRESS>wrote:

@PastaPastaPasta requested changes on this pull request.
NACK, wrong repo
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/dashpay/dash/pull/3260?email_source=notifications&email_token=AKK2KUT4UQRG63QKXOD6PUDQ3US27A5CNFSM4KB5IUMKYY3PNVWWK3TUL52HS4DFWFIHK3DMKJSXC5LFON2FEZLWNFSXPKTDN5WW2ZLOORPWSZGOCQO73EA#pullrequestreview-337509776,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AKK2KUQJ2PDZKF66VCKCJ3TQ3US27ANCNFSM4KB5IUMA
.


Update KSCrash 1.13.6, Enable searchThreadNames

Current coverage is 82.22% (diff: 100%)

Merging #107 into master will increase coverage by 0.01%

@@             master       #107   diff @@
==========================================
  Files            27         27
  Lines          1905       1907     +2
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
+ Hits           1566       1568     +2
  Misses          339        339
  Partials          0          0

Powered by Codecov. Last update a97c710...f510c1c


Add ability for attachments sent to the mailbox to be added to the cleo ticket.

Currently, if someone sends an email to an endpoint of one of our mailbox services, we ignore any attachments. It has been requested by the subMIT help team that we make this possible, because sometimes users attach screenshots, etc.
Of course, the nature of attachments (especially images) is not great for us being able to generate a response, since images are not easily processed into text to feed into A2rchi. However, we need to make sure they at least carry over into the cleo ticket.

turns out we already have this compatibility, it just was a currupted file from the user