@azure/openai Azure OpenAI API call not working when enabled stream mode

Package Name:  @azure/openai
Package Version:  ^1.0.0-beta.1
Operating system: macOSX (ARM)
[ ] nodejs v18.12.1

version:

[ ] browser

name/version:

[ ] typescript

version:

Is the bug related to documentation in

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

Describe the bug
I am trying to use the @azure/openai  package and trying to enable the streaming mode. Stream seems to be supported in the typescript types.
To Reproduce
Steps to reproduce the behavior:

Modify the getChatCompletions call for streaming

const result = await client.getChatCompletions(
                deploymentId,
                newPrompt,
                { stream: true, maxTokens: 150, temperature: 0.9 }
            )

But i get the following Error
operations.js:138 Uncaught (in promise) TypeError: Cannot read properties of undefined (reading 'completion_tokens')     at _getChatCompletionsDeserialize (operations.js:138:1)     at getChatCompletions (operations.js:151:1) _
Screenshots

Hi, thanks for reaching out! Check out this sample for streaming chat completions: https://github.com/Azure/azure-sdk-for-js/blob/main/sdk/openai/openai/samples/v1-beta/javascript/listChatCompletions.js

How do I get a normal ReadableStream similar to what openai return and why did you change the whole APIs?

Hi @FrancescoSaverioZuppichini, @azure/openai supports a minimum version of NodeJS 14 and the browser and currently ReadableStream has been supported in NodeJS since v16.5. We are considering updating the API to return a ReadableStream directly after we drop support for v14 and v16.0 - v16.4.

thanks, why did you just match the openai sdk - this is crazy. With all due respect, what is even the point of using an inferior sdk based on something what worked better then now openai have enterprise features?

@FrancescoSaverioZuppichini Thanks for the feedback. I looked at the openai-node library and found that the chat completions operation returns a custom Stream type that implements the Async Iterable protocol. Here is how it can be used which is pretty similar to how @azure/openai's listChatCompletions can be used. Could you point me towards where can you get a ReadableStream in openai-node?
I also created the following sample that demonstrates using ReadableStream, could you please try it and let me know if it works?
https://github.com/Azure/azure-sdk-for-js/blob/3f0758c7fb9e1c4c092d5ca08655e20154943641/sdk/openai/openai/samples/v1-beta/javascript/readableStream.js#L26-L38

thanks a lot, I was trying something similar. Was wondering if that will basically first await for all the events and then return the stream.
Let me test it out, if that is okay I can PR the README on this repo with this example


fix(deps): update undici

Fails with wasm error on Node-API Client tests.
Example:
FAIL src/__tests__/integration/happy/browser/test.ts
  ● Test suite failed to run

    RangeError: WebAssembly.Instance(): Out of memory: wasm memory

      at Object.<anonymous> (../../node_modules/.pnpm/undici@4.4.5/node_modules/undici/lib/client.js:400:16)
      at Object.<anonymous> (../../node_modules/.pnpm/undici@4.4.5/node_modules/undici/index.js:3:16)

Because we import both LibraryEngine and BinaryEngine files and undici tries to load the wasm even if not instantiated / needed

Integration available with 2.30.0-integration-undici-4.1

Opened an issue at undici asking for input: https://github.com/nodejs/undici/issues/988

replaced by https://github.com/prisma/prisma/pull/8842


fix unit test

Signed-off-by: yxxhero<EMAIL_ADDRESS>fix unit test
@mumoshu
BTW, I don't find the place where the helm installs in tests ci. Could you tell me?

@yxxhero Are you looking for this? https://github.com/helmfile/helmfile/blob/main/.github/workflows/ci.yaml#L120-L124

@mumoshu https://github.com/helmfile/helmfile/blob/44c26e6639989b7a55ff4d85e52aec280ec477c1/.github/workflows/ci.yaml#L11-L12
this ci stage requires helm, but I can't find helm install logic.


HELM-243: fix attribute node search modal in Grafana 6.7

This PR fixes the attribute node search popup to render properly and to react when searches happen. The fix is to make sure everything is happening in Angular promises and the chains complete, and also for the search input to be selected when the modal opens.
@agalue I think this fixes your issue, if you don't mind testing it out.
https://issues.opennms.org/browse/HELM-243

Also, good news!  I tried it in Grafana 7.1 and it still works there.

:D Yeah, still some work to do for 7, but I was glad it still worked there.


removed client calls from workflowIT and generalIT

https://github.com/dockstore/dockstore/issues/2970
Continuing the process of migrating relevant tests to dockstore_cli.
Note that some tests make sense to have in both repos, so for the ones I kept in this repository I have converted them from using Client.main calls to API calls. The tests are testing the same general ideas, though will not be exactly the same.
I will have a PR in the dockstore_cli repo as well with the new tests.

Looks like I am getting that DAG 390 vs 391 issues again.

 Here is an overview of what got changed by this pull request:

Coverage increased per file
===========================
+ dockstore-webservice/src/main/java/io/dockstore/webservice/helpers/EntryLabelHelper.java  9
+ dockstore-webservice/src/main/java/io/dockstore/webservice/resources/DockerRepoTagResource.java  27
+ dockstore-webservice/src/main/java/io/dockstore/webservice/helpers/QuayImageRegistry.java  11
+ dockstore-webservice/src/main/java/io/dockstore/webservice/helpers/BitBucketSourceCodeRepo.java  26
+ dockstore-webservice/src/main/java/io/dockstore/webservice/helpers/AbstractImageRegistry.java  2
+ dockstore-common/src/main/java/io/dockstore/common/PipHelper.java  68
+ dockstore-webservice/src/main/java/io/dockstore/webservice/core/Tag.java  11
+ dockstore-webservice/src/main/java/io/dockstore/webservice/resources/ResourceUtilities.java  9
+ dockstore-webservice/src/main/java/io/dockstore/webservice/core/Image.java  39
+ dockstore-webservice/src/main/java/io/dockstore/webservice/core/Checksum.java  46
+ dockstore-webservice/src/main/java/io/dockstore/webservice/helpers/SourceCodeRepoFactory.java  9

Complexity increasing per file
==============================
- dockstore-webservice/src/main/java/io/dockstore/webservice/resources/DockerRepoTagResource.java  2

See the complete overview on Codacy

Looks like I am getting that DAG 390 vs 391 issues again.

Sigh... I spent a little time trying to reproduce it, but couldn't.

It usually goes away if you run it again.
I wonder if I should change the test to check for greater than 389 and then log a ticket to narrow it down.

 Here is an overview of what got changed by this pull request:

Complexity increasing per file
==============================
- dockstore-webservice/src/main/java/io/dockstore/webservice/resources/DockerRepoTagResource.java  2

See the complete overview on Codacy


Multithreading support

This might be a feature request or a question depending on the feature's state.
Can Leto handle multiple GraphQL requests to the endpoint in parallel? Or does the second request need to wait for the first to complete?
Say we first requests coming and taking 5 seconds because it is computationally expensive. After 1 second, another request comes. Does the second request wait for 4 seconds before it is handled?
If parallel processing is not possible, I would like to request this feature.

Hi, thanks for your question!
Sorry for the delay I was not available for a few days.
Concurrent processing works by default since the resolvers can be async, they would use Dart's threads to schedule work. Within a single request, mutations execute resolvers in series following the GraphQL specification and queries execute them concurrently. But multiple different requests will be handled concurrently in a single core (using Dart's scheduling).
Parallel processing (multiple cores) is also possible, but you need to make sure the necessary state is share if it needs to be shared or just create a bunch of executors and schedule each request in parallel with Dart isolates. If the server is horizontally scalable you could probably use an executor for each isolate and there should not be any problems.
Also you probably would want to investigate how shelf (or the web server you are using) would interact with multiple cores. I have not benchmark these changes to make sure they would improve performance significantly.
Please let me know if I missed something or if there is something more I could help you with.


Impl FromStr for Locale

Fixes #9

Awesome 😊 maybe squash the commits?

usually they go like "clippy", "WIP", "clippy omg please", "damn you clippy", ... :D


Can't connect on a subdirectory

Summary
Install mattermost inside a subdirectory like https://example.tld/mattermost/ and the app will not be able to connect.
Environment Information

Device Name: One Plus 5
OS Version: Android 8.1.0
Mattermost App Version: 1.11.0
Mattermost Server Version: 5.1.0

Steps to reproduce
Install mattermost inside a subdirectory like https://example.tld/mattermost/ and the app will not be able to connect.
Expected behavior
Able to connect on a subdirectory.
Observed behavior
If I move it to the main directory, it's working perfectly.
Inside a subdirectory, it's working perfectly for the webversion.

Hi @Grummfy, thank you for reporting this 👍
I'm wondering if this is a backwards compatibility issue as I couldn't find a ticket related to this issue and this feature was well tested last release. I'll ask our QAs for help in testing this and we'll let you know the feedback.

Hi @Grummfy,
Our QAs tested this and weren't able to repro the issue.
Are you seeing any errors in logs from around the time the issue occurs?

in fact, it's a network error, bad configuration from my side. Sorry for the error and thanks for the work


Correct Microsoft, Azure, JavaScript, and Python typos

Correct typos with some minor drive-bys.

@xixian73, @guywi-ms
Can you also review the proposed changes?
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

@xixian73, @guywi-ms
Can you review this old PR and determine whether it needs to be closed or merged?

I sent an email to the content owners today.

@cn0151 @guywi-ms - Can you please review the articles that belong to you and let us know if this content is okay to merge?
Note: I have assigned cn0151 per request from @@xixian73

@rageking8,
Some of these articles have been updated since the pull request was created, and they no longer exist in the repo. You can remove those files from this PR to resolve the merge conflicts, or you can submit a new PR that doesn't include those files. Thanks for your contribution.


vue 2.0 can't use filter in v-html

DON'T WORK

CAN WORK, but html code escaped.
{{item.latestMessage.content | deluxe}}

This is expected. Filters only work in interpolations ({{}}) in Vue 2.0


prevent oscrecv from blocking matlab

it will be helpful if oscrecv doesn't block matlab (i.e. add drawnow to while loop used for polling)

Fixed in 14beacf6fe78b4bf3c21c0d5af735eda5af427bf


Host instances and best known solutions

In the long term, we could make a separate repository to maintain the instances and best known solutions.

Using Github Actions we can make this process mostly automated.
Templates can streamline the submission process
We need to write a validator for each problem type. See #27

https://github.com/PyVRP/Instances takes care of this.


Add missing part in the Git users command

Also add notes to fix the issue when 'authors-transform.txt' file encoding is not correct and author is not found.

@ShaneZhengNZ : Thanks for your contribution! The author, @hkamel, has been notified to review your proposed change.

The update that's requested in the PR appears to be reflected in master. We'll close the pull request.


Identity Platform: Tenants & Tokens

Coverage increased (+2.7%) to 35.681% when pulling d88aa1291d9e21a42e8ee4bd5d15ea7fd346df3f on feature/tenants into 889bbd3ca2184ac9619dddc439fb345fbec28a4e on main.


Unreadable images for pages with names like Murciélago

If considering page Lamborghini_Murciélago, images are downloaded in folder /stwdata/Lamborghini_Murciélago but browser tries to open /stwdata/Lamborghini_Murci%C3%83%C2%A9lago.

:+1:


Added details

This CL adds some details to the meta[name='theme-color'] feature following https://github.com/Fyrd/caniuse/pull/5939/

Thanks!


Add space between icon and text in buttons

In buttons, the icon could probably be a few more pixels away from the button text.
Probably the easiest way to implement this is to add a margin, but if we find other places where it'd be nice to add space between an icon and its corresponding text, we might also be able to add the desired space within IcoMoon.

If we implement this using CSS, I think we'll probably want to include a[role="button"] elements.

Addressed in #171.


Helper party status events

This adds an API route for helper parties to post their status to, as it changes, and a test to validate that it works. It also includes an API key, so that the management layer can validate the status update from the helper party is valid.
Next steps for queuing:

Have the helper parties POST to the endpoint when their status changes.
Have the management layer start queries server side, and start the next in the queue when the current one finishes.

Note: In the long run, we've undecided where this state should live, and which direction information should flow. Regardless, this will likely require self deploying the management layer. We'll need to do this in the next few months, but until we agree on a more robust design doc, this way will work.

Summary by CodeRabbit

New Features

Introduced a new API endpoint to update the status of a query.
Added integration tests for the POST updateStatus API route.
Implemented validation for API keys.
Added a new table helper_party_query_status_updates with security policies.
Added Supabase client utilities for server-side rendering.

Configuration

Jest and Prettier configurations updated for better development workflow.
Added new dependencies for testing and Babel presets.
Updated next.config.js to include experimental option forceSwcTransforms.

Database

Seed data updated with new entries and hashed API keys.
SQL migrations added for new table creation and security policies.

Testing

Added comprehensive tests for new API functionalities.

it only took 14 commits debugging github actions, but the test now passes in CI


Help! I want to modify mode buttons on my fan

my circulator got four modes.  direct, natural, smart, sleep.
And if i able mode buttons on plugin settings via homebridge ui x, it displays four switches on homekit.
i want to make it displays only natural mode switch and it should be toggle switch between only direct and natural. How can i manage to change these?

Hi,
a similar issue has already been discussed here: https://github.com/merdok/homebridge-miot/issues/337
This is not possible directly currently since a switch can only display two states, what would you do with the intermediate states?
Nevertheless, you can at least reduce the numer of switches to only those which you really need. Have a look a propertyControl to accomplish that.


Update Databricks Notebook for Tools 24.02

Databricks Tools Demo Notebooks should be updated to support latest version of
Issues

Qualification notebook file is corrupted.
Virtual env setup is incorrect.
Platform argument is not passed correctly in the P/Q tools.

Notebooks have been updated to Spark RAPIDS Tools v24.06.0


[Feature] Use vela-cli to simplify the process of deploy OCM

Is your feature request related to a problem? Please describe.
Use kubectl vela to simplify the process of deploy OCM.

Use  kubectl vela to specify the master cluster

kubectl vela cluster init --config=./kube/hub-kubeconfig

Register slave cluster

kubectl vela cluster register cluster1

Describe the solution you'd like
ocm already has an installation tool https://github.com/open-cluster-management-io/clusteradm, We can import and use the functions in this repo. but we will merge the clusteradm join and clustardm accept to one step kubectl vela cluster register.

we will just write a doc to do that

refer to https://github.com/oam-dev/kubevela/pull/2599


Project explorer window is empty in Spyder 3.0.0b6

Description of your problem
I have recently upgraded spyder 3.0.0b4 to 3.0.0b6 and in the process the content of the project explorer window has disappeared.
What do you see instead?
The project explorer window is empty and the address bar with the button to select the workspace next to it has gone.
Versions and main components

Spyder Version: 3.0.0b6
Python Version: 2.7
Operating system: Windows 10

Dependencies
jedi >=0.8.1     :  0.9.0 (OK)
matplotlib >=1.0 :  1.5.1 (OK)
nbconvert >=4.0  :  4.2.0 (OK)
numpy >=1.7      :  1.11.1 (OK)
pandas >=0.13.1  :  0.18.1 (OK)
pep8 >=0.6       :  1.7.0 (OK)
pyflakes >=0.5.0 :  1.2.3 (OK)
pygments >=2.0   :  2.1.3 (OK)
pylint >=0.25    :  1.5.4 (OK)
qtconsole >=4.2.0:  4.2.1 (OK)
rope >=0.9.4     :  0.9.4 (OK)
sphinx >=0.6.6   :  1.4.1 (OK)
sympy >=0.7.3    :  1.0 (OK)

Projects have been rewritten almost from scratch. The old workspaces are gone and now you need to create a project from the Projects menu in the main window. After you do that, the project explorer will show a file tree view of your current project.
Sorry for the inconveniences, but we don't plan to support the workspaces concept in Spyder 3.0.

OK.
Thanks a lot for the explanation.

No prob :-) Hope you enjoy our new projects support.


Support STAC 1.0

Improvement
Update to STAC spec 1.0 (beta.???)
Notes + Context
Looks like STAC spec is aiming to have 1.0-RC1 by end of July: https://github.com/radiantearth/stac-spec/milestones
In either case its close enough that we should start supporting it.
We'd like to do this before we start maintaining large catalogs in Franklin to avoid migration concerns.
Explicitly we're not worrying about supporting any possible data migration from 0.9 to 1.0 as part of this issue.
This issue is in two parts:

[ ] Investigate the changes and document likely impact in this issue
[ ] Implement the changes to roll over to new version

In general, this should be upgrade or removal of things that are currently part of stac4s and avoid adding new support.
I think that means removing the existing asset extension (rather than adding support for the new collection asset extension), ignoring the changes to the projections extension since we don't currently support it, and handling improvements to the label and eo extensions. This heuristic might not cover the whole changelog, but I think it should be a good starting place.


get content-length

I want set content-length to give client, but i can't get size after compression, what should i do?thanks

Because compression modifies the body and changes the size, the content length is removed since it will have the incorrect value after compression.


Color argument out of order when len(col) == len(values)

Hi @mgymrek,
I was playing around with the swarm plots (looks great by the way, thanks :) ). I noticed that when trying to color each point individually, the color always seem out of place (i.e. it colors the wrong point).
This small code snippet, which tries to color the highest value differently, produces the error:
from beeswarm import *
import matplotlib.pyplot as plt
import numpy as np
d1 = np.random.normal(size=100)

max_d1 = max(d1)
d1_colors = ["grey" if x != max_d1 else "red" for x in d1]

bs, ax = beeswarm([d1], method="swarm", labels=["sample 1"], col=d1_colors)

Looking deeper into the code, I saw that this line seems to be responsible: https://github.com/mgymrek/pybeeswarm/blob/master/beeswarm/beeswarm.py#L210
The sort makes the values list out of sync with the col list.
Any chance of a fix coming :)?
P.S. I'm on Python 3.4, Linux, running Matplotlib 1.4.3

Hi @bow,
Thanks for pointing this problem out! The problem was not that particular line, but was due indeed to the data frame being sorted, making it out of sync with the function that called it and assumed the output is returned in the original order. This commit should fix it. Let me know if this solves your issue.

Hi @mgymrek,
This fixes the issue indeed. Thanks :)!


Update uv.h

This is not enough to map a new errno. You need to add it also to include/uv-errno.h, and to docs/src/errors.rst.
Also, please update the commit log according to CONTRIBUTING.md.


Typeahead doesn't close when clicking outside

In this demo typeahead doesn't close when clicking outside of it. This behaviour sounds intuitive after using most dropdown components. See also  this comment.

Fixed in #168. Available in re-com 2.2.0.
Closing.


Question about GPU memory usage

Thanks for sharing this excellent work！
Here are two questions:

I tried to train re10k_dl3dv_512x512 on an A6000 and got CUDA out of memory error even though batch_size was set to 1. How much GPU memory is needed for this training condition?
It seems two datasets will lead to batch_size*2. How to avoid this problem? (like random choose dataset while training)

Thanks for sharing this excellent work！ Here are two questions:

I tried to train re10k_dl3dv_512x512 on an A6000 and got CUDA out of memory error even though batch_size was set to 1. How much GPU memory is needed for this training condition?
It seems two datasets will lead to batch_size*2. How to avoid this problem? (like random choose dataset while training)

Could you please tell me the minimal requirement of CUDA memory for testing re10k_dl3dv_512x512? Thank you very much!


client: fix bundle index

Fix #16

You shouldn't amend commits and force push in a PR, you mess with the historical record. You can choose to squash when the PR is merged

I think it's just preference. Personally if the change is trivial, I prefer to make commit log identical to the subject.

I think it's just preference. Personally if the change is trivial, I prefer to make commit log identical to the subject.

I agree with @njaremko, you should use squash and merge.


Where does Cattaz store persistent data? [Docker]

Hello, in the Docker container, where does Cattaz store any created documents? Is there a single file path I can just create a volume bind mount to in order to persist the data between container recreation?

Also, is there an environment variable to allow me to change the websocket port used by the app? In the docker-compose.yml file I can easily change the websocket listener like so:
ports:
  - "17011:1234"
  - "80:8080"

However the Cattaz web application seems hardcoded to check port 1234 for the websocket. :)

Hi kawaii,

where does Cattaz store any created documents?

If you use master branch, Cattaz does not persist documents for now.
If you use leveldb branch (#6), Cattaz stores documents at ./y-leveldb-databases/.

is there an environment variable to allow me to change the websocket port used by the app?

Currently not.
It is a good idea to make ports configurable.
Would you like to make a PR or shall I do it for you?

Port numbers are now configurable.
You can find documentation at http://cattaz.io/build/#/doc/usage.
Could you try it?

@ohtake thank you! I have tested it and the fuctionality works as intended. :slightly_smiling_face:


Opening speed and initial caching

This supercedes #3 and is directly intended to address h5netcdf performance issues.
We want to make sure we don't spend too much time instantiating file instances and we get the timing right for reading properties including b-trees.  Will report information here.

Initial performance results with the current b-tree caching scheme (on variable instantiation in pyfive):
File Opening Time Comparison  da193o_25_day__grid_T_198807-198807.nc (ms)
h5py:    0.177002
pyfive:  0.150879
Variable instantiation for [tos]
h5py:    0.094238
pyfive:  0.434082
Access and calculation time for summation
h5py:   497.699707
pyfive: 520.595459
Total times
h5py:   497.970947
pyfive: 521.180420

File Opening Time Comparison  ch330a.pc19790301-def-short.nc (ms)
h5py:    0.095703
pyfive:  0.207275
Variable instantiation for [UM_m01s16i202_vn1106]
h5py:    0.073975
pyfive:  0.063965
Access and calculation time for summation
h5py:    8.051025
pyfive:  7.377930
Total times
h5py:    8.220703
pyfive:  7.649170

(This code is deliberately ensuring the tests are done from memory, not from disk, because file caching is hard to address. Small differences in time will matter in practice.)

Some more figures, now including s3 access, where we will also have to think a bit about the influence of caching to be sure of what we are seeing, but for now:
File Opening Time Comparison  da193o_25_day__grid_T_198807-198807.nc  (ms, S3=False)
h5py:    0.155029
pyfive:  0.158936
Variable instantiation for [tos]
h5py:    0.093018
pyfive:  0.422119
Access and calculation time for summation
h5py:   504.198730
pyfive: 505.630127
Total times
h5py:   504.446777
pyfive: 506.211182

File Opening Time Comparison  ch330a.pc19790301-def-short.nc  (ms, S3=False)
h5py:    0.093994
pyfive:  0.191895
Variable instantiation for [UM_m01s16i202_vn1106]
h5py:    0.076172
pyfive:  0.067627
Access and calculation time for summation
h5py:   10.077148
pyfive:  7.379150
Total times
h5py:   10.247314
pyfive:  7.638672

File Opening Time Comparison  da193o_25_day__grid_T_198807-198807.nc  (ms, S3=True)
h5py:   16532.587891
pyfive:  0.408936
Variable instantiation for [tos]
h5py:    0.476074
pyfive:  2.509277
Access and calculation time for summation
h5py:   15575.990723
pyfive: 25531.353027
Total times
h5py:   32109.054688
pyfive: 25534.271240

File Opening Time Comparison  ch330a.pc19790301-def-short.nc  (ms, S3=True)
h5py:   16700.600098
pyfive: 68445.999023
Variable instantiation for [UM_m01s16i202_vn1106]
h5py:   66742.625977
pyfive:  0.409912
Access and calculation time for summation
h5py:   22.507080
pyfive: 20.614990
Total times
h5py:   83465.733154
pyfive: 68467.023926

Ah, yes, well that really wasn't fair, because pyfive came second and got the benefit of caching, so here's some farer data which avoids reusing cached data:
(h5play) bnl28@MX6H7D9YGP bnl % python opening_speed.py
File Opening Time Comparison  da193o_25_day__grid_T_198807-198807.nc  (ms, S3=False)
h5py:    0.201941
pyfive:  0.191927
Variable instantiation for [tos]
h5py:    0.108957
pyfive:  0.396967
Access and calculation time for summation
h5py:   526.242733
pyfive: 533.447742
Total times
h5py:   526.553631
pyfive: 534.036636

File Opening Time Comparison  ch330a.pc19790301-def-short.nc  (ms, S3=False)
h5py:    0.129938
pyfive:  0.221729
Variable instantiation for [UM_m01s16i202_vn1106]
h5py:    0.090837
pyfive:  0.066280
Access and calculation time for summation
h5py:    6.794214
pyfive:  6.704807
Total times
h5py:    7.014990
pyfive:  6.992817

File Opening Time Comparison  da193o_25_day__grid_T_198807-198807.nc  (ms, S3=True)
h5py:   18064.429760
pyfive: 17285.735846
Variable instantiation for [tos]
h5py:    0.346184
pyfive:  4.059792
Access and calculation time for summation
h5py:   15244.802713
pyfive: 15527.326107
Total times
h5py:   33309.578657
pyfive: 32817.121744

File Opening Time Comparison  ch330a.pc19790301-def-short.nc  (ms, S3=True)
h5py:   16712.314129
pyfive: 84538.033009
Variable instantiation for [UM_m01s16i202_vn1106]
h5py:   50832.113028
pyfive:  0.406981
Access and calculation time for summation
h5py:   22.121906
pyfive: 26.489019
Total times
h5py:   67566.549063
pyfive: 84564.929008

These results are somewhat perplexing though: if we look at the S3 data (given the first file is simple and small, the second is complex and bigger), and recognise that this is a calculation that requires all the data to move across home broadband, we see that the different ways of lazily loading things impact on either the opening or the variable instantiation, but scatter gun finding of information in the hdf5 file impacts strangely in the complex file. We should try a nicely packed version of it as well!

The expected advantage here is that the pyfive library is completely threadsafe and we can do what we like in parallel with it. Next step is to see if that is a real advantage or not.


Whitening transform that supports mean subtraction

I added a Whitening class that builds on the LinearTransformation class, but this one further supports pixel-wise zero centering using a mean vector computed offline, which is essential for ZCA whitening.

Hi,
Thanks for the PR!
It looks like most of the code is taken from the LinearTransformation layer.
Can't we instead have a Normalize layer before the LinearTransformation in order to obtain the same results?

Thanks for the reply!
I think the Normalize layer is meant to normalize each channel separately - however, sometimes before we use ZCA we need a feature-wise normalization (i.e. pixel-wise). If you think this is better solved by a Normalize layer and a 'LinearTransformationlayer, then we should probably modify theNormalize` layer since right now it only says it supports channel-wise normalization.

Indeed, currently Normalize only supports passing around the same values for the channel normalization.
Still, I think it's simpler to have the user write a basic Normalilze that performs pointwise subtraction, than have an almost duplicate implementation of LinearTransformation.

Maybe we could combine this mean subtraction feature into LinearTransformation and change it to a more suitable name? Unless pixel-wise mean subtraction is really uncommon for deep learning, otherwise they will need such a Transform which is currently not supported.

Sorry for the delay in replying.
I would be ok with adding the addition operation into LinearTransformation, but then it shouldn't be called LinearTransformation anymore, but AffineTransformation.
What about the following:

add an addition coefficient to LinearTransformation, and rename it to AffineTransformation
make LinearTransformation call AffineTransformation, and deprecate LinearTransformation

Could you do those changes?

Closing in favor of #793


Parse Plutus transactions

Parsing plutus transaction includes showing

collateral return
total collateral

We do not show datum hash, inline datum, inline datum, reference inputs, collateral inputs, redeemer or required singers

I guess just the fixture doesn't reflect a real plutus tx, but I'd expect some script addresses to be involved in the tx as outputs, and also datum fields - shouldn't showing such info already be part of this PR?

We do not show datum hash, inline datum, inline datum, reference inputs, collateral inputs, redeemer or required singers

I'd expect that info to be visible to the user in a final version of the snap. Is this something we plan to deal with in a follow up PR/next milestone?

We do not show datum hash, inline datum, inline datum, reference inputs, collateral inputs, redeemer or required singers

I'd expect that info to be visible to the user in a final version of the snap. Is this something we plan to deal with in a follow up PR/next milestone?

Would be for showing that next to the outputs in the "main" UI, or down below next to raw tx and other tx details? We discussed this and decided to now show datum because trezor does not show it either.

Merged into develop


Bug fix -- all remote packages should be referenced as local

Currently if you accidentally install the packages from npm, such as npm install flowise-components, you will be stuck as both yarn and npm will constantly use the public version instead of the local version.
This issue cost me several hours to diagnose when my build would successfully work, but no changes would be seen. It's especially dangerous during version changes of packages which is when you'll notice it happen the most.
To solve this, package.json supports local dependencies via the file: notation. Using this instead of * ensures the package comes from the local one, not any global one that happens to be around.

@automaton82 I ran into the same issue today, here's how I resolved it:

Run yarn link in packages/ui
Run yarn link in packages/components
Run yarn link flowise-ui flowise-components in packages/server,

Thank you for sharing that information! I like this permanent fix more 😄 but I get there's a risk.

I'm closing this PR, it's not correct. As of today it fails for me because it copies both flowise-components and flowise-ui into $/packages/server/node_modules and those do not have their icons (among other problems).
If * is used instead this doesn't happen (they aren't copied), and if the problem arises then the above suggestion to use yarn link should suffice.


Possible use of palladiumFF2 with four coordinated Zinc

It is possible to use assign_v2.py with a four coordinated Zinc for the common type of zinc fingers?
An example is available?
Thanks.
Saverio

Dear Saverio,
your message ended up in the spam folder, and I just saw it while clearing
the spam. Please accept my apologies for such a long delay.
As for the answer to your question, you will need to make a series of
changes in the assignv2.py program, and it's not an easy task.  However, if
you'd like, we can work on it together.
Thanks,
Baris
xavgit @.***>, 25 Haz 2024 Sal, 20:30 tarihinde şunu
yazdı:

It is possible to use assign_v2.py with a four coordinated Zinc for the
common type of zinc fingers?
An example is available?
Thanks.
Saverio
—
Reply to this email directly, view it on GitHub
https://github.com/bkurt00/palladiumFF2/issues/1, or unsubscribe
https://github.com/notifications/unsubscribe-auth/A5EYGNFX657ZZ5WHC5M32ILZJGSLTAVCNFSM6AAAAABJ4JP6LGVHI2DSMVQWIX3LMV43ASLTON2WKOZSGM3TGMRUHAYDIOA
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

Hi,
I should like to use assignv2.py to model zinc fingers in protein because
using the ZAFF Modeling Tutorial (https://ambermd.org/tutorials/advanced/tutorial20/ZAFF.php ) Ihave had problems with a ZN-C-C_HIE-HID.


Updated import paths to reflect new locations.

Some dependencies have moved to new locations.

great, thanks!


The security support of python 3.7 will be ended in June, 2023

Is your feature request related to a problem? Please describe.
According to the python community, the security support of python 3.7 will be ended on 27 June, 2023. So, it would be better to stop supporting python 3.7 in OpenMetadata, because we won't guarantee updates in python 3.7 if vulnerabilities are found. Let's discuss the plan to stop supporting python 3.7.

https://devguide.python.org/versions/
Describe the solution you'd like
We will support python 3.8 or later.
Describe alternatives you've considered
N/A
Additional context
N/A

Hey @yu-iskw thank you for opening thi issue. We won't stop support for Python 3.7 as some critical cloud infrastructure that clients may use still have requirements around this version (i.e. AWS MWAA https://github.com/open-metadata/OpenMetadata/issues/8359). By support here we mean adding logic in the code that is only supported from python 3.8+.
We do have an open issue arounding adding tests for Python 3.10/3.11 https://github.com/open-metadata/OpenMetadata/issues/8359. We'll also be adding messaging around the recommended Python version to use.

@TeddyCr Alright. I close the issue.


npmjs.com page has wrong information

Information at https://www.npmjs.com/package/react-native-live-stream is wrong.

npm/yarn information is about react-native-orientation-locker. It should be about react-native-live-stream.
iOS framework integration is about react-native-aliyun-push. It should be about react-native-live-stream.
yarn is misspelled as yard.

I had updated it at v1.0.1


Update README.md

I endorse this PR. We need a maintainer of @uber-archive to land this, cc @sectioneight.


Accept input from Gitlab Web Hooks

Gitlab allows the creation of project web hooks to trigger external events when an event occurs, including "push events" and "tag push events". Please implement configurable support for these web hooks so I can (almost) immediately see Gitlab updates in Packages.
Please see this page for documentation: https://gitlab.com/gitlab-org/gitlab-ce/blob/master/doc/web_hooks/web_hooks.md

This was added in 3.0.4

Thanks, @bdandoy.


Project import generated by Copybara.

Project import generated by Copybara.

35fd3f0167 has bypassed this PR, shouldn't be needed anymore.


Use py4j launch_gateway to launch Java server.

Right now, when creating a ScienceWorldEnv object, a Java server needs to be started via a call to subprocess.Popen .
This PR proposes to use py4j's helper function to launch and manage the java server on its own. The benefits are two folds:

There's no need to manually assign a port. The proposed code will automatically find one available and use it.
When the main Python process terminates, crashes, or gets interrupted, the associated java process is automatically killed hence avoiding creating zombie processes.

This PR contains breaking changes. Instantiating a ScienceWorldEnv object no longer needs threadNum, nor launchServer.
Also, this PR makes issue #21 irrelevant.
I based my code on https://www.py4j.org/advanced_topics.html#using-py4j-without-pre-determined-ports-dynamic-port-number

Thank you very much for this work! I've been running off this branch for the past week or so, and it's been working well. I've been able to remove heuristics used to choose ports, and there are no longer any zombie Java processes. The change to package.sh will be very useful as well and you got to it before I could do something similar. I'm looking forward to this being merged.
This is a minor problem, but I wonder if you know how to use a debugger with this. I was previously using the following patch, but it doesn't work anymore with the new architecture:
diff --git a/scienceworld/scienceworld.py b/scienceworld/scienceworld.py
index 4291c39..20655ba 100644
--- a/scienceworld/scienceworld.py
+++ b/scienceworld/scienceworld.py
@@ -67,7 +67,7 @@ class ScienceWorldEnv:
     # Launches the PY4J server
     def launchServer(self, serverPath):
         print("Launching ScienceWorld Server (Port " + str(self.portNum) + ") -- this may take a moment.")
-        cmd = "nohup java -cp " + serverPath + " scienceworld.runtime.pythonapi.PythonInterface " + str(self.portNum) + " >/dev/null 2>&1 &"
+        cmd = "nohup java -agentlib:jdwp=transport=dt_socket,server=y,suspend=n,address=5005 -cp " + serverPath + " scienceworld.runtime.pythonapi.PythonInterface " + str(self.portNum) + " >/dev/null 2>&1 &"

         subprocess.Popen(cmd, cwd=BASEPATH, shell=True)
         # The sleep command here is to give time for the server process to spawn.

I got the green light from Peter and I was planning to merge it today :). I'm afraid you will have to rebase your PRs though.
That's a debugger for the JVM? I'll test it out later today, to see what we can do about it.

I got the green light from Peter and I was planning to merge it today :).

Good to hear!

I'm afraid you will have to rebase your PRs though.

I'm not surprised. I can do it easily, though.

That's a debugger for the JVM? I'll test it out later today, to see what we can do about it.

I don't entirely understand it because I'm not very familiar with the Java and Scala ecosystems, but I believe it sets up a built-in JDK debug server that I can attach an external debugger (e.g., IntelliJ) to. It's better than print-line debugging, but if you don't know how to handle it, don't worry about getting it to work. I was just hoping it's something you had figured out already.


Fixes #426 - Replace crypto.randomUUID with something simpler

Submitted is a pull request for issue #426 reported by me.
This fix might work better for backwards compatibility among mobile users.

@smonn @afraser I pushed again to increase the "good enough" aspects, its now prefixed with the current datetime to reduce the likelihood of a randomized id collision


Update configure-connect-to-azure-storage.md

Clarifying the section about how the mounts work to be consistent with the actual usage and the Azure CLI explanations. https://docs.microsoft.com/en-us/cli/azure/webapp/config/storage-account

@phillipsj : Thanks for your contribution! The author(s) have been notified to review your proposed change.

#sign-off

@ktoliver : Thanks for your contribution! The author(s) have been notified to review your proposed change.


Is there any way to auto close the tooltip when navigating away from the fragment in the same activity?

I added the following to the ViewTooltip class.
public class ViewTooltip {
private static ArrayList allToolTips = new ArrayList<>();
public static void hideAllVisibleToolTips() {
for (TooltipView tip: allToolTips) {
tip.removeNow();
}
}
then in the Tooltip constructor I added (right above setWithShadow(true);)
allToolTips.add(TooltipView.this);
You can then call this function ViewTooltip.hideAllVisibleToolTips() when navigating away from your fragment.
It works well for me.

Nice! In which version will this be available?
I am currently using 1.1.5 and I solved it in a dirty way by saving the instance of tooltip as a member variable in Fragment instead of local. So that on certain events I can check if it's not null and call closeNow on it.

I didnt have any plans to push the change.  Someone is welcome to if they'd like.
What I wrote above is really everything that's needed to make it work.
Whenever I load a new fragment I just call
ViewTooltip.hideAllVisibleTooltips()
In my code and they get removed.

If you set tooltip on rootView like this, it'll hide automatically when parent view is not visible.
ViewTooltip.on(context, relView, imgDot)...


fix(costmodels): Set pagination to compact in the wizard

closes #1118

[x] Price list

[x] Sources

Codecov Report

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

@@           Coverage Diff           @@
##           master    #1124   +/-   ##
=======================================
  Coverage   75.24%   75.24%
=======================================
  Files         228      228
  Lines        4408     4408
  Branches      833      833
=======================================
  Hits         3317     3317
  Misses        973      973
  Partials      118      118

Continue to review full report at Codecov.

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


X.A.DynamicWorkspaceGroups: TopicSpace support

Description
This adds viewTopicGroup and a corresponding prompt. This is similar
to viewWSGroup, but it calls switchTopic instead of W.greedyView,
in order to run the topic action on the workspace.
Checklist

[x] I've read CONTRIBUTING.md

[x] I've considered how to best test these changes (property, unit,
manually, ...) and concluded: it works

[x] I updated the CHANGES.md file

[x] I updated the XMonad.Doc.Extending file (if appropriate)

Awesome! take your time with it, this isn't at all urgent

This is a failing of the respective topic actions, just spawning a terminal and not thinking about the workspaces at all. They should instead spawn this via spawnOn or similar functionality. I think this will probably occur often enough that it's at least worth noting in the docs somewhere.

That's definitely something that needs to be mentioned


AVD Emulator not working anymore on Bumblebee

I just updated Android Studio to Bumblebee and I really REGRET it. Emulator doesn't work anymore
Whenever I launch it they just get stuck in this

Running from the console works fine...

I have the same problem. I'm working with macOS version of Bumblebee. So far I Invalidated the cache, restored the layout, and removed the emulators' folder from the SDK folder, but nothing solved the problem yet.  I've managed to launch the emulators from the command line but that is just tedios.

Ok it started working for me, I just uncheked this option @Sbenari  no idea what is happening tbh

When I run it from the command line I get this:
~ emulator -avd Pixel_3a_API_32_arm64-v8a
[8676713984]:ERROR:android/android-emu/android/qt/qt_setup.cpp:28:Qt library not found at ../emulator/lib64/qt/lib
Could not launch '/Users/edmiro/../emulator/qemu/darwin-x86_64/qemu-system-aarch64': No such file or directory

Do this ./emulator -avd Pixel_3a_API_32_arm64-v8a
On Thu, Jan 27, 2022 at 2:56 PM Edgar Miró @.***> wrote:

When I run it from the command line I get this:
~ emulator -avd Pixel_3a_API_32_arm64-v8a
[8676713984]:ERROR:android/android-emu/android/qt/qt_setup.cpp:28:Qt library not found at ../emulator/lib64/qt/lib
Could not launch '/Users/edmiro/../emulator/qemu/darwin-x86_64/qemu-system-aarch64': No such file or directory
—
Reply to this email directly, view it on GitHub
https://github.com/google/android-emulator-m1-preview/issues/76#issuecomment-1023586763,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ARSBA4K2IS633EZF3JQGTJLUYGPNNANCNFSM5M6UPYLA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you were mentioned.Message ID:
@.***>

--
Steve Ben-Ari
www.extrapix.com
www.amazon.com/shops/EXTRApix
http://stores.ebay.com/Surplus-Plus-1--
Honda Shadow 2005 Ice

@jeanlst unfortunately it didn't work for me. the "Launch in tool window" was already checked. it didn't work either checked or unchecked.

Go to your SDK tools and Uncheck/Uninstall the current Android Emulator tool. Then try and launch your created virtual device. This will launch the Component Installer, prompting you to install the Android Emulator once again. Click Ok. Wait for download, and finish. Launch the emulator without being prompted by the component installer this time. Worked like a charm after I had tried and failed with everything else.

It doesn't work. Also, I already have the adb in the PATH environment variable.

Do this ./emulator -avd Pixel_3a_API_32_arm64-v8a
On Thu, Jan 27, 2022 at 2:56 PM Edgar Miró @.> wrote: When I run it from the command line I get this: ~ emulator -avd Pixel_3a_API_32_arm64-v8a [8676713984]:ERROR:android/android-emu/android/qt/qt_setup.cpp:28:Qt library not found at ../emulator/lib64/qt/lib Could not launch '/Users/edmiro/../emulator/qemu/darwin-x86_64/qemu-system-aarch64': No such file or directory — Reply to this email directly, view it on GitHub <#76 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/ARSBA4K2IS633EZF3JQGTJLUYGPNNANCNFSM5M6UPYLA . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub. You are receiving this because you were mentioned.Message ID: @.>
-- Steve Ben-Ari www.extrapix.com www.amazon.com/shops/EXTRApix http://stores.ebay.com/Surplus-Plus-1-- Honda Shadow 2005 Ice

It doesn't work. Also, I already have the adb in the PATH environment variable.

Same issue, M1 Max. It did work and started failing with the emulator 31.2.6 update. Launching in its own window works.

I confirm that launching the emulator on its own windows is working a charm.

Unchecking the launch in a tool window works for m1. Was not expecting this bug from bumblebee 🥲.
Thanks for the help @jeanlst

non of the fixes above worked for me. I have MacBook Pro 13" 2020 with Quad-Core i5. very disappointed.

I had to delete the device multiple times... than I restarted Android Studio with the tool window option unchecked and in the end it worked... Mac M1 Max

To overcome issue

Uncheck "Launch in a Tool window" under emulator in preferences section
Restart the OS to take effect
Goto Android Studio and run your preferred device

By the way, I am using Mac M1 pro with Apple silicon chip - macOs 12.1 and Android Studio Bumblebee 2021.1.1

If you want to run the emulator in tool window one bypass that i found is to launch the emulator then from activity monitor quit the emulator process. A window appears asking if you want to save state. Close that window and the emulator will show up in tool window. The downside is that you have to force quit emulator from activity monitor when you are done using it.

The same problem has occurred to me.
The Android Studio Log causes the following errors.
2022-01-31 22:02:58,660 [2659455]   INFO - manager.EmulatorProcessHandler - Emulator: /Users/hyun/Library/Android/sdk/emulator/emulator -netdelay none -netspeed full -no-snapstorage -avd Pixel_3_API_28 -qt-hide-window -grpc-use-token -idle-grpc-timeout 300
2022-01-31 22:02:58,952 [2659747]   INFO - manager.EmulatorProcessHandler - Emulator: WARNING | cannot add library /Users/hyun/Library/Android/sdk/emulator/qemu/darwin-aarch64/lib64/vulkan/libvulkan.dylib: failed
2022-01-31 22:02:58,955 [2659750]   INFO - manager.EmulatorProcessHandler - Emulator: INFO    | Warning: QMetaObject::connectSlotsByName: No matching signal for on_new_posture_requested(int) ((null):0, (null))
2022-01-31 22:02:58,955 [2659750]   INFO - manager.EmulatorProcessHandler - Emulator:
2022-01-31 22:02:58,955 [2659750]   INFO - manager.EmulatorProcessHandler - Emulator: INFO    | Warning: QMetaObject::connectSlotsByName: No matching signal for on_dismiss_posture_selection_dialog() ((null):0, (null))
2022-01-31 22:02:58,955 [2659750]   INFO - manager.EmulatorProcessHandler - Emulator:
2022-01-31 22:02:58,955 [2659750]   INFO - manager.EmulatorProcessHandler - Emulator: INFO    | Warning: QMetaObject::connectSlotsByName: No matching signal for on_new_resizable_requested(PresetEmulatorSizeType) ((null):0, (null))
2022-01-31 22:02:58,955 [2659750]   INFO - manager.EmulatorProcessHandler - Emulator:
2022-01-31 22:02:58,955 [2659750]   INFO - manager.EmulatorProcessHandler - Emulator: INFO    | Warning: QMetaObject::connectSlotsByName: No matching signal for on_dismiss_resizable_dialog() ((null):0, (null))
2022-01-31 22:02:58,955 [2659750]   INFO - manager.EmulatorProcessHandler - Emulator:
2022-01-31 22:02:58,955 [2659750]   INFO - manager.EmulatorProcessHandler - Emulator: INFO    | configAndStartRenderer: setting vsync to 60 hz
2022-01-31 22:02:58,955 [2659750]   INFO - manager.EmulatorProcessHandler - Emulator: INFO    | added library /Users/hyun/Library/Android/sdk/emulator/lib64/vulkan/libvulkan.dylib
2022-01-31 22:02:59,023 [2659818]   INFO - b.PhysicalDeviceChangeListener - emulator-5554 connected
2022-01-31 22:02:59,023 [2659818]   INFO - mpl.AdbDeviceFileSystemService - Device connected: emulator-5554
2022-01-31 22:02:59,029 [2659824]   INFO - manager.EmulatorProcessHandler - Emulator: INFO    | Started GRPC server at <IP_ADDRESS>:8554, security: Local+token
2022-01-31 22:02:59,029 [2659824]   INFO - manager.EmulatorProcessHandler - Emulator: INFO    | Advertising in: /Users/hyun/Library/Caches/TemporaryItems/avd/running/pid_31104.ini
2022-01-31 22:02:59,679 [2660474]   WARN - ea.emulator.EmulatorController - android.emulation.control.EmulatorController/getDisplayConfigurations call failed - FAILED_PRECONDITION: The multi-display feature is not available
2022-01-31 22:04:59,030 [2779825]   WARN - n.process.BaseOSProcessHandler - Process hasn't generated any output for a long time.
If it's a long-running mostly idle daemon process, consider overriding OSProcessHandler#readerOptions with 'BaseOutputReader.Options.forMostlySilentProcess()' to reduce CPU usage.
Command line: /Users/hyun/Library/Android/sdk/emulator/emulator -netdelay none -netspeed full -no-snapstorage -avd Pixel_3_API_28 -qt-hide-window -grpc-use-token -idle-grpc-timeout 300
java.lang.Throwable: Process creation:
	at com.intellij.execution.process.BaseOSProcessHandler.<init>(BaseOSProcessHandler.java:33)
	at com.android.tools.idea.avdmanager.EmulatorProcessHandler.<init>(EmulatorProcessHandler.java:36)
	at com.android.tools.idea.avdmanager.EmulatorRunner.start(EmulatorRunner.java:66)
	at com.android.tools.idea.avdmanager.AvdManagerConnection.continueToStartAvd(AvdManagerConnection.java:572)
	at com.android.tools.idea.avdmanager.AvdManagerConnection.continueToStartAvdIfAccelerationErrorIsNotBlocking(AvdManagerConnection.java:507)
	at com.android.tools.idea.avdmanager.AvdManagerConnection.lambda$startAvd$4(AvdManagerConnection.java:497)
	at com.google.common.util.concurrent.AbstractTransformFuture$AsyncTransformFuture.doTransform(AbstractTransformFuture.java:213)
	at com.google.common.util.concurrent.AbstractTransformFuture$AsyncTransformFuture.doTransform(AbstractTransformFuture.java:202)
	at com.google.common.util.concurrent.AbstractTransformFuture.run(AbstractTransformFuture.java:118)
	at com.google.common.util.concurrent.DirectExecutor.execute(DirectExecutor.java:30)
	at com.google.common.util.concurrent.AbstractFuture.executeListener(AbstractFuture.java:1213)
	at com.google.common.util.concurrent.AbstractFuture.complete(AbstractFuture.java:983)
	at com.google.common.util.concurrent.AbstractFuture.set(AbstractFuture.java:746)
	at com.google.common.util.concurrent.TrustedListenableFutureTask$TrustedFutureInterruptibleTask.afterRanInterruptibly(TrustedListenableFutureTask.java:131)
	at com.google.common.util.concurrent.InterruptibleTask.run(InterruptibleTask.java:133)
	at com.google.common.util.concurrent.TrustedListenableFutureTask.run(TrustedListenableFutureTask.java:78)
	at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
	at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
	at java.base/java.util.concurrent.Executors$PrivilegedThreadFactory$1$1.run(Executors.java:668)
	at java.base/java.util.concurrent.Executors$PrivilegedThreadFactory$1$1.run(Executors.java:665)
	at java.base/java.security.AccessController.doPrivileged(Native Method)
	at java.base/java.util.concurrent.Executors$PrivilegedThreadFactory$1.run(Executors.java:665)
	at java.base/java.lang.Thread.run(Thread.java:829)
2022-01-31 22:05:03,834 [2784629]   INFO - manager.EmulatorProcessHandler - Emulator: ERROR   | detected a hanging thread 'QEMU2 main loop'. No response for 105077 ms
2022-01-31 22:05:03,834 [2784629]   INFO - manager.EmulatorProcessHandler - Emulator: ERROR   | detected a hanging thread 'QEMU2 CPU0 thread'. No response for 105078 ms
2022-01-31 22:06:48,900 [2889695]   INFO - manager.EmulatorProcessHandler - Emulator: ERROR   | detected a hanging thread 'QEMU2 main loop'. No response for 105069 ms
2022-01-31 22:06:48,900 [2889695]   INFO - manager.EmulatorProcessHandler - Emulator: ERROR   | detected a hanging thread 'QEMU2 CPU0 thread'. No response for 105069 ms
2022-01-31 22:06:53,906 [2894701]   INFO - manager.EmulatorProcessHandler - Emulator: ERROR   | detected a hanging thread 'QEMU2 main loop'. No response for 110073 ms
2022-01-31 22:06:53,907 [2894702]   INFO - manager.EmulatorProcessHandler - Emulator: ERROR   | detected a hanging thread 'QEMU2 CPU0 thread'. No response for 110073 ms
2022-01-31 22:06:58,907 [2899702]   INFO - manager.EmulatorProcessHandler - Emulator: ERROR   | detected a hanging thread 'QEMU2 main loop'. No response for 115076 ms
2022-01-31 22:06:58,907 [2899702]   INFO - manager.EmulatorProcessHandler - Emulator: ERROR   | detected a hanging thread 'QEMU2 CPU0 thread'. No response for 115076 ms
2022-01-31 22:07:03,910 [2904705]   INFO - manager.EmulatorProcessHandler - Emulator: ERROR   | detected a hanging thread 'QEMU2 main loop'. No response for 120081 ms
2022-01-31 22:07:03,911 [2904706]   INFO - manager.EmulatorProcessHandler - Emulator: ERROR   | detected a hanging thread 'QEMU2 CPU0 thread'. No response for 120081 ms
2022-01-31 22:07:08,915 [2909710]   INFO - manager.EmulatorProcessHandler - Emulator: ERROR   | detected a hanging thread 'QEMU2 main loop'. No response for 125082 ms
2022-01-31 22:07:08,915 [2909710]   INFO - manager.EmulatorProcessHandler - Emulator: ERROR   | detected a hanging thread 'QEMU2 CPU0 thread'. No response for 125082 ms
2022-01-31 22:07:13,919 [2914714]   INFO - manager.EmulatorProcessHandler - Emulator: ERROR   | detected a hanging thread 'QEMU2 main loop'. No response for 130085 ms
2022-01-31 22:07:13,919 [2914714]   INFO - manager.EmulatorProcessHandler - Emulator: ERROR   | detected a hanging thread 'QEMU2 CPU0 thread'. No response for 130086 ms

@stefalda, when you say "delete the device multiple times", what do you mean by that?  so far non of the above fixes worked for me Device Manager won't open, I can only use the command line to launch devices or use the Device selector. but I can't open the Device Manager to manage my devices.

I have found though that the Virtual Device Manager does open from the "Welcome to Android Studio" window

.

@Sbenari  I couldn't delete from the interface because it said that the emulator was in use, so I chose to "show in finder", close Android Studio and delete the folder...

If you get emulator is in use error, go to: /Users//.android/avd/
then open the folder of the emulator you use and run: *rm .lock

For the time being, m1 chip users can do the following:

Uninstall emulator in android studio by going to sdk tools and uncheck emulator option and then click apply.
Download canary Dolphin version Android studio
When you will open device manager in the new android studio, it will ask to install emulator. Install it.
The emulator installed is of older version which does not have this bug.
Now, you can uninstall the canary version of Dolphin Android studio and use Bumblebee stable or continue using Dolphin.

@stefalda @edgarmiro @sibylantoninobajeli @jeanlst @inemtsev
I ended up reverting back to Arctic Fox and all sorts of problems disappeared including AVD Manager not working, COCOAPODS errors, and various other problems. Bumblebee is just not a stable release yet!

According to https://developer.android.com/studio/releases/emulator
31.2.7 (February 1, 2022)
[Bug fix] Emulator hanging error on M1 machines.

Under Windows if you undock the emulator into a separate window, as it used to work, it is frozen to the middle of the screen. It cannot be moved or resized, not by the mouse, Alt-space M, or any of the Windows controls. Nice improvement.

In the latest update, this has been fixed. 31.2.7

I confirm, the update for emulator version 31.2.7 works like a charm.

Standalone window for the emulator is still locked to the center of the screen.

Not working on emulator API version 32.

this solution works - https://stackoverflow.com/questions/70864465/why-device-manager-dont-open/70866555

Unchecking the launch in a tool window works for me.

I had a similar issue with the emulator as well. In my case it works perfectly fine using Pixel 5 API 30 on it but as soon as I go to Pixel 4 and API 24 or Nexus API 21, the open for awhile and disappear. I can see that the process is running in the background and even the dropdown menu shows it as online, it's just not in the tool menu.
Detaching the emulator from the tool window solved the issue for m as well.

To overcome issue

Uncheck "Launch in a Tool window" under emulator in preferences section
Restart the OS to take effect
Goto Android Studio and run your preferred device

By the way, I am using Mac M1 pro with Apple silicon chip - macOs 12.1 and Android Studio Bumblebee 2021.1.1

You literally saved my 3 days. I did everything. Tried different solutions. Even uninstalled android, gradle and android studio. I don't thing, I left any solution. Finally restarting worked for me :D


Approximate concordia with equal-length segments

Currently, the concordia line is drawn by breaking it into equal lengths of t and approximating with bezier curves. As has been previously suggested by @noahmclean, it would be better to generate equal-length segments instead.

@noahmclean, you mentioned that you had code for creating equal-length concordia segments in #27. Do you still have that code? I'm interested in implementing this in Topsoil before writing an overview of how we plot everything.

Here's a sketch for what I had in mind, though I can't find where I implemented this code originally.  The document has an outline of the algorithm I was using, and then a worked problem with a particularly nasty Tera-Wasserburg view.  It hasn't been proofread closely -- let me know if there are any typos/mistakes or if you think of a better way of doing this.  And a last note: I wouldn't spend too much time looking for exponential-optimized algorithms, as we'll be using this frequently for functions that don't have simple exponential forms as well.
Apparently Github doesn't like pdf and tex attachments, and I don't know how to Git, so here are the docs in a Google Drive folder:
https://drive.google.com/folderview?id=0B8o2Mni1YcPFMkEzQnJSZllBQTQ&usp=sharing

After playing with this on my machine in Python, it seems perfect. I used the same quality measure as you (max(dists) / min(dists)). After a few cases (most quite tough), I found the algorithm needed no more than 55 iterations to bring the quality below 1 + 10e-13. :sunglasses:
I'll add this in this week and there should be a big performance boost, since we'll need a lot less Bezier segments with this feature to attain the same (or higher!) visual quality.

yeah - progress through collaboration!
On Tue, Oct 27, 2015 at 12:07 AM, John Zeringue<EMAIL_ADDRESS>wrote:

After playing with this on my machine in Python, it seems perfect. I used
the same quality measure as you (max(dists) / min(dists)). After a few
cases (most quite tough), I found the algorithm needed no more than 55
iterations to bring the quality below 1 + 10e-13. [image: :sunglasses:]
I'll add this in this week and there should be a big performance boost,
since we'll need a lot less Bezier segments with this feature to attain the
same (or higher!) visual quality.
—
Reply to this email directly or view it on GitHub
https://github.com/CIRDLES/Topsoil/issues/219#issuecomment-151370044.

--
Jim Bowring
C. Richard Crosby Distinguished Teaching Co-Chair
Principal Investigator, www.CIRDLES.org, www.github.com/cirdles
Computer Science
College of Charleston
66 George Street
Charleston, SC 29424
Google Voice:<PHONE_NUMBER> (preferred)
Google Email<EMAIL_ADDRESS>Office:
Harbor Walk East (360 Concord Street) Room 308
843.953.0805
http://stono.cs.cofc.edu/~bowring/
<EMAIL_ADDRESS>R. Buckminster Fuller (1972):
If humanity is to survive aboard our planet, it must become universally
literate and preoccupied with inherently cooperative Comprehensive
Anticipatory Design Science in which every human is concerned with
accomplishing the comfortably sustainable well-faring of all other humans.


Enhance RGW config options

Allow for enhanced configurability of the civetweb parameters
Add switch to enable CNAME bucket resolution (ie. some.website.com.objects.example.com) where bucket name is "some.website.com"
Ability to enable RGW usage logging and its associated configuration parameters which are detailed at http://docs.ceph.com/docs/jewel/man/8/radosgw/#usage-logging
Add switch to enable S3-style static website hosting.

jenkins test ansible2.2-docker_cluster

jenkins test ansible2.2-dmcrypt_journal_collocation

jenkins test ansible2.2-centos7_cluster

rebased ^

jenkins test this please


Bump k8s to 1.19.4 and controller-runtime to  v0.7.0-alpha.6

Description of the change:
The following changes have been made:

Bump versions of:

Controller runtime to v0.7.0-alpha.6
Kubernetes dependencies to v0.19.4
Helm to v3.4.1
Operator-lib to the commit having the updated c-r version
Ginko/gomega to latest versions

In Ansible:

Update AnsibleReconciler to accept context.Context in order to implement Reconciler interface of controller-runtime.
Update informerCache in internal/ansible/predicate/ to accept a context instead of stop channel.
Make necessary modifications to use client.Object instead of runtime.Object.

In Helm:

Update HelmReconciler to accept context.Context in order to implement Reconciler interface of controller-runtime.

Unit tests:

Modify tests in internal/kubebuilder/filesystem and internal/kubebuilder/machinery to contain single RunSpec handler per package (in accordance to the changes made in recent Ginko version)

In OLM integration:

Make changes to use client.Object instead of runtime.Object in client API calls.
ConfigMapList is not of type client.Object. Update tests to use configmaps instead of configmapLists in registry.go.

Modified k8s version in Makefile to 1.19.4.
Added changelog.

NOTE: This would be updated to use controller-runtime 0.7.0. Creating this PR, so that it would be easier to bump to a stable release later.
Motivation for the change:
Support higher versions of k8s and controller-runtime.
Checklist
If the pull request includes user-facing changes, extra documentation is required:

[x] Add a new changelog fragment in changelog/fragments (see changelog/fragments/00-template.yaml)
[ ] Add or update relevant sections of the docs website in website/content/en/docs

@varshaprasad96 you can change the manager option's (for both ansible and helm) LeaderElectionResourceLock to ConfigMapsResourceLock to get current behavior.

closing and reopening for ci


Update owners & Year in contributing

As title

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@f5be13e). Click here to learn what that means.
The diff coverage is n/a.

@@           Coverage Diff            @@
##             master   #5620   +/-   ##
========================================
  Coverage          ?   37.8%
========================================
  Files             ?     322
  Lines             ?   47474
  Branches          ?       0
========================================
  Hits              ?   17949
  Misses            ?   26937
  Partials          ?    2588

Continue to review full report at Codecov.

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


🐛 bug: Anthropic model integration Issue: Header requirement error and failed responses

Description
I have encountered an issue with the Anthropic model integration on Mattermost using the mattermost-plugin-ai. After following the documentation for installing the module and configuring it to use the Anthropic model, I am unable to receive any responses due to errors.

The errors encountered are as follows:

"error [2024-03-05 21:05:43.872 +01:00] failed to get github plugin status caller="app/plugin_api.go:988" plugin_id=mattermost-ai error="not found"
"error [2024-03-05 21:05:44.256 +01:00] Streaming result to post failed caller="app/plugin_api.go:988" plugin_id=mattermost-ai error="non 200 response from anthropic: 400 Bad Request Body: {"type":"error","error":{"type":"invalid_request_error","message":"anthropic-version: header is required"}} github.com/mattermost/mattermost-plugin-ai/server/ai/anthropic.(*Client).Completion.func1 github.com/mattermost/mattermost-plugin-ai/server/ai/anthropic/client.go:132 runtime.goexit runtime/asm_amd64.s:1650"
"error [2024-03-05 21:05:44.281 +01:00] Failed to generate title caller="app/plugin_api.go:988" plugin_id=mattermost-ai error="failed to get title: failed to send query to anthropic: non 200 response from anthropic: 400 Bad Request"

Here is my configuration:

Self-Hosted
Mattermost Version: 9.4.2
Database Schema Version: 117
Build Number:<PHONE_NUMBER>
Database: Postgres

It seems like there is an issue with the plugin not properly sending or including the required anthropic-version header when making requests to the Anthropic model, resulting in a 400 Bad Request error.
Additionally, I have tested the Anthropic API directly through my Python scripts, and it works as expected, which indicates that the issue might be specifically related to the mattermost-plugin-ai configuration or its interaction with the API. I suspect that the problem may arise from a missing header configuration in the plugin code. It seems that the req.Header.Set("anthropic-version", "<VERSION>") might not be properly set in the server/ai/anthropic/client.go file, which could lead to the observed 400 Bad Request error due to the missing anthropic-version header. Including this header configuration might resolve the issue.
I would appreciate any guidance or a fix for this issue.

I've added the following line:
req.Header.Set("anthropic-version", "2023-06-01")
to the following functions (server/ai/anthropic/client.go):
func (c *Client) CompletionNoStream(...)
func (c *Client) Completion(prompt string) ...

After implementing this change, the previous error was resolved. However, I encountered a new issue:
error [2024-03-07 20:38:14.246 +01:00] websocket request handling error caller="wsapi/websocket_handler.go:58" action=user_typing seq=3 user_id=xxxxxxxxxxxxxxxxx error_message="Invalid channel_id parameter." error="websocket: user_typing: Invalid channel_id parameter."
error [2024-03-07 20:38:15.016 +01:00] failed to get github plugin status caller="app/plugin_api.go:988" plugin_id=mattermost-ai error="not found"

@McHarryDentaire Fixed with #147, thanks for reporting this! Decided to do a bit of overkill and update the whole client to use the newer Messages API.
As for your other error, that should not effect the operation of the plugin, it is occurring because you don't have the Github plugin installed. Are you experiencing operational issues or just the log message? Try with #147 and let me know if that works.

@crspeller Great, thank you. It works like a charm.
Regarding the GitHub plugin not being installed, I'm not experiencing any operational issues, just seeing this error log.

Great! https://github.com/mattermost/mattermost-plugin-ai/pull/148 will remove that unnecessary error log.

I got the same issue using ollama server with qwen 14b LLM. The error message is "websocket: user_typing: Invalid channel_id parameter."


fix Firefox bug

The motivation is that the getting started page was not working in some cases in Firefox.
This line of code appears to be at best a no-op, at worst fails in Firefox, since "event" is undefined.

By analyzing the blame information on this pull request, we identified @JoelMarcey and @hramos to be potential reviewers.

Good find. I thought event was something magical when I saw that in the code. Chrome didn't care. Firefox did :)

@facebook-github-bot shipit

Something went wrong when importing this pull request. Please cc someone from the team at fb to help with importing this.

@facebook-github-bot shipit

Thanks for importing. If you are an FB employee go to Phabricator to review.


⚠ Samsung has degraded performance

In 5cc2056, Samsung (https://samsung.com) experienced degraded performance:

HTTP code: 200
Response time: 2607 ms

Resolved: Samsung performance has improved in ed80635.


Any way to make it work for React 17 ?

Hi.
The active-table-react package works fine on a React 17 project but the package-lock.json lists its dependency being react 18. I there any way to make that dependency fixed?

Hi @s-bose, I'm trying to understand the nature of your problem. Do you mean that your project is importing two react libraries: 17 and 18? Hence, is the issue itself the matter of resultant project size due to two react packages or are there errors on your end. Any information to help me understand this better will help, thankyou!

Hello. What I'm trying to say is that when installing active-table-react in a react 17 project it works just as intended except the active-table-react package in my project's node_modules has also installed its own react package inside its own node_modules. It is not messing up the main react 17 in my project but can you please make the react dependency a peer dependency? Maybe that would fix it?
Apologies for the confusion. I'm comparatively new to the react ecosystem.

Ok, so to my understanding its a two React library problem?

Yep, I'll investigate to find the best solution

Thanks mate. Cheers!

Just to note, once I do have the solution, I'll need to fully test it out across which may take some time. I should have this all settled in 1-2 hours, I'll report on my progress in this thread.

I believe this concludes the work for this issue, nevertheless if you believe something may need to be changed feel free to comment below and reopen this thread :)
Once again, thankyou very much for raising the issue and letting me know about this fantastic optimization opportunity!
Just to note, the official release date for this component will be at the end of this month or the start of next, hence why the component is using the 0.0.x version increments. If you find any bugs or have suggestions for improvements, DO NOT HESITATE to raise new issues and I will be very happy to discuss them accordingly :)
Thanks again! 💯

Thank you so much for responding so fast and taking my thoughts into consideration. Appreciate the effort! 💯


Update selectors.md

Added a component example, with a template, to make it clear how the selectors can work

What kind of change does this PR introduce? (check at least one)

[ ] Bugfix
[ ] Feature
[ ] Code style update
[ ] Refactor
[ ] Build-related changes
[x] Other, please describe:
Documentation modification

Does this PR introduce a breaking change? (check one)

[ ] Yes
[x] No

If yes, please describe the impact and migration path for existing applications:
The PR fulfills these requirements:

[x] It's submitted to the dev branch.
[ ] When resolving a specific issue, it's referenced in the PR's title (e.g. fix #xxx[,#xxx], where "xxx" is the issue number)
[ ] All tests are passing: https://github.com/vuejs/vue-test-utils/blob/dev/.github/CONTRIBUTING.md#development-setup
[ ] New/updated tests are included

If adding a new feature, the PR's description includes:

[ ] A convincing reason for adding this feature (to avoid wasting your time, it's best to open a suggestion issue first and wait for approval before working on it)

Other information:

I have added two different ways to define the component, and I wasn't sure which one would be preferred.  The main point I was trying to clarify was how the ref and name selectors can be used to select elements, with an example. Totally understand if this is too different to other testing documentation and not needed. While I'm getting more into the vue testing space, I found a bit of confusion here and thought an example would help 👍

The failed CI test looks to be related to code styling, for 7 pages, One of them I have modified. Pulling the docker image and running the prettier to determine what's wrong with the styling to fix it

Unfortunately I can't find the project files in the docker image, I suspect they're added as part of the implementation details in CircleCI's 'attaching workspace' step. I haven't setup this project locally, just changed the file in github's editor. If it's needed I can set it up locally, but  I don't want to spend more time on this, unless someone from vuejs can let me know if it's worth it.
So I guess, bump


Create built-in Flappy Bird clone game.

Work is moved to CP58 branch.

All changes merged to master.


Update defaults for Twitter Bootstrap 3

When this library was created, Twitter Bootstrap was at version 2, so the default divider element / was used. Twitter Bootstrap 3 uses pseudo elements for this, so it's not needed anymore, and should default to null (so it isn't even rendered at all). We should also update the default breadcrumbs class to be just breadcrumb instead (which is the Bootstrap class in both 2 and 3 - not sure why we didn't use that from the start).
In fact, since pseudo-elements are the "correct" way to do this (there's nothing semantic about having a divider in HTML, at least in my opinion), we should likely just remove the divider functionality.
As both of these (removing dividers and changing the default CSS class) are BC breaks, we won't do this before v4.0.0. Not sure when that's gonna happen, but I'll let this issue stay here so we don't forget about it.
If anyone has any input on this (or a good argument on why it shouldn't be done), feel free to comment!

I think this will not going to break too much (or nothing), since if you use this Breadcrums, you MUST solve this manually by removeClass('breadcrums'), addClass(breadcrumb') and also setDivider(null).
There is not need to remove $divider, since (due flexibility of Breadcrums to add and remove classes and divider) you can use it as standalone, using your own style and CSS classes instead of Bootstrap if you like to.
Changes in that commit just default to Bootstrap style.
So, I think a minor release, clarifying this changes in readme and sources, will compliance semver.

That's true in case of users who use Bootstrap - but we can't make that generalization, and for non-Bootstrap users who rely on the default class value, this would break their styling. As a user of any other library, I hate it when a minor update breaks something in my app, and I don't want to do that to other people.
Regarding the BC break - I understand that there are certain assumptions that need to be made about reasonable use cases when using semantic versioning - because strictly speaking, anything you do might be a breaking change for someone - but in this case, I don't think it's unreasonable for people to not be using Bootstrap :)
As for removing the divider, the purpose is to simplify the library, because this can be achieved with CSS alone (as Bootstrap 3 does it, for example), and in my opinion, it's the correct (semantic) way to do it.

You are right. That divider should be added in CSS in any case.
Well... In the mean time, I'll inherit from it in other class and set
default state in my constructor.
Hehe... This is a good utility.
~nelson6e65
El 25/04/2016 00:57, "Miloš Levačić"<EMAIL_ADDRESS>escribió:

That's true in case of users who use Bootstrap - but we can't make that
generalization, and for non-Bootstrap users who rely on the default class
value, this would break their styling. As a user of any other library, I
hate it when a minor update breaks something in my app, and I don't want to
do that to other people.
Regarding the BC break - I understand that there are certain assumptions
that need to be made about reasonable use cases when using semantic
versioning - because strictly speaking, anything you do might be a breaking
change for someone - but in this case, I don't think it's unreasonable for
people to not be using Bootstrap :)
As for removing the divider, the purpose is to simplify the library,
because this can be achieved with CSS alone (as Bootstrap 3 does it, for
example), and in my opinion, it's the correct (semantic) way to do it.
—
You are receiving this because you commented.
Reply to this email directly or view it on GitHub

Oh... well, no. Because I was intended to use it from Laravel package.
:disappointed:
~nelson6e65

Not really - the creitive/laravel4-breadcrumbs and creitive/laravel5-breadcrumbs packages are there for Laravel integration, but all they really do is configure a shared Breadcrumbs instance (and a facade for people who use that) so that you can access it throughout the app (and take advantage of automatic dependency resolution, etc.)
This package itself (creitive/breadcrumbs) started out as a Laravel-specific package (at version 1), but was refactored to make it standalone starting from version 2 (at that point, the Laravel-specific bridge packages were introduced).
If you are unsure about using the package in a non-Laravel context, feel free to ask and I'll do my best to help out.

Well.. I made this defaults in my base Controller:
<?php

use Breadcrumbs;
use Illuminate\Routing\Controller as BaseController;

abstract class Controller extends BaseController
{
    // protected $breadcrumbs = null;
    public function __construct()
    {
        Breadcrumbs::setCssClasses('breadcrumb')
            ->setDivider(null)
            ->add('', '/');
    }
}
?>

And spread like that in inherited controllers.
In my layout:
{!! $breadcrumbs or Breadcrumbs::render() !!}

Sure, that's how you'd use it with Laravel - but if I understood correctly, you don't want to use it with Laravel? I am not sure where the confusion is coming from, so if you have a specific question, please ask and I'll try to help you - additionally, you might want to create a new issue, as this one is specifically about changing the defaults in a future version.
Thanks for using this library and for making it better! :)

No, no. I want to use it in my Laravel project.
Originally I was thinking about to create a ˋBreadcrumb2 extends Breadcrumbsˋ class and set defaults (like I did in example commit) in this inherited class and the use it. But, Laravel package uses ˋBreadcrumbsˋ, not  my ˋBreadcrumbs2ˋ. So, it was not going to work. Jaja. So, the las example code was the way to set this defaults in shared $breadcrums from my base Controller. So, now is set to default bootstrap in a Laravel context. :smile:

Ah, that's what you wanted.
You can do that a bit more elegantly if you like. Assuming you're using the creitive/laravel5-breadcrumbs package, you can extend its service provider, and configure that one in config/app.php instead of the one that comes with the package.
Something like this:
<?php

namespace Nelson\Breadcrumbs;

use Creitive\Breadcrumbs\Breadcrumbs;
use Creitive\Breadcrumbs\BreadcrumbsServiceProvider as BaseServiceProvider;

class BreadcrumbsServiceProvider extends BaseServiceProvider
{
    /**
     * {@inheritDoc}
     */
    public function register()
    {
        $this->app['breadcrumbs'] = $this->app->share(function ($app) {
            $breadcrumbs = new Breadcrumbs();

            $breadcrumbs->setCssClasses('breadcrumb');
            $breadcrumbs->setDivider(null);
            $breadcrumbs->add('', '/');

            return $breadcrumbs;
        });

        $this->app->alias('breadcrumbs', 'Creitive\Breadcrumbs\Breadcrumbs');
    }
}

Now when you use the Breadcrumbs facade, or if you use Laravel's automatic dependency injection, everything will be preconfigured, and you won't have to do it manually in your base controller.
Also, not sure if the add() method should be called in the service provider, this depends on your project I guess - if you have that in all breadcrumbs as the first crumb, I guess it's okay, otherwise, you might want to leave that in your base controller.

Ah, yes. I'll check it this tomorrow if I can implement that instead.
And yes, I added first element because it was the base controller. Anyway,
I can reset breadcrumbs in other controller constructor if I need to...
Because this plugin is nice! :smile:
Well... I think I'll left controller implementation, waiting this update. o/


Handle customUnitOutOfPolicy violation

Details
Implement the plan in this design doc section to add RBR logic for the bottom-up flow.
Fixed Issues
$ https://github.com/Expensify/App/issues/46753
PROPOSAL: N/A
Tests

Create a distance expense on NewDot and submit it to a new account
Update the default USD rate for workspaces
Comment out the allowed writes check in Web-E because CreateWorkspaceFromIOUPayment already does too many on main
Log in to NewDot as the payer account
Choose to pay the expense with a business bank account, which will set up a new workspace. After clicking the button you can close out of the bank account flow since all we care about is moving the expense to a new workspace.
Verify there is an unread workspace chat with a green dot, open it
Verify there is a red dot on the expense report preview, open it
Verify there is a red dot and violation message on the rate row
Update the rate to the default on the policy
Verify the rate updates successfully and all red dots are cleared

Run the same test but for tracking an expense
Offline tests

Run the same flow as above, but go offline before updating to the workspace rate.
Verify it looks good optimistically.
Go online and verify the rest of the test steps above.

Run the same test but for tracking an expense
QA Steps
No QA

[ ] Verify

PR Author Checklist

[x] I linked the correct issue in the ### Fixed Issues section above
[x] I wrote clear testing steps that cover the changes made in this PR

[x] I added steps for local testing in the Tests section
[x] I added steps for the expected offline behavior in the Offline steps section
[x] I added steps for Staging and/or Production testing in the QA steps section
[x] I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[x] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
[x] I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).

[x] I included screenshots or videos for tests on all platforms
[x] I ran the tests on all platforms & verified they passed on:

[x] Android: Native
[x] Android: mWeb Chrome
[x] iOS: Native
[x] iOS: mWeb Safari
[x] MacOS: Chrome / Safari
[x] MacOS: Desktop

[x] I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
[x] I followed proper code patterns (see Reviewing the code)

[x] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
[x] I verified that the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
[x] I verified that comments were added to code that is not self explanatory
[x] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[x] I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method

[x] If any non-english text was added/modified, I verified the translation was requested/reviewed in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message: https://expensify.slack.com/archives/C01GTK53T8Q/p1723566468387289

[x] I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
[x] I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is approved by marketing by adding the Waiting for Copy label for a copy review on the original GH to get the correct copy.
[x] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[x] I verified the JSDocs style guidelines (in STYLE.md) were followed

[x] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[x] I followed the guidelines as stated in the Review Guidelines
[x] I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
[x] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[x] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[x] I verified that if a function's arguments changed that all usages have also been updated correctly
[x] If any new file was added I verified that:

[x] The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory

[x] If a new CSS style is added I verified that:

[x] A similar style doesn't already exist
[x] The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG))

[x] If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
[x] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[x] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[x] If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
[x] If the PR modifies the form input styles:

[x] I verified that all the inputs inside a form are aligned with each other.
[x] I added Design label so the design team can review the changes.

[x] If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
[x] If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.

Screenshots/Videos
I (Neil) only tested on Mac Chrome because all the changes are platform independent.

Android: Native

Android: mWeb Chrome

iOS: Native

iOS: mWeb Safari

MacOS: Chrome / Safari
Online test

Offline test

MacOS: Desktop

Hi yeah, I'm taking it over since I think it's easiest to test if you can modify the backend rate while testing.

Ok, I think this is ready to go. It's a (hopefully) beautiful collaboration between @paultsimura and I!

Hi yeah, I'm taking it over since I think it's easiest to test if you can modify the backend rate while testing.

Should I do something here @neil-marcellini ? Thank you.

Hi yeah, I'm taking it over since I think it's easiest to test if you can modify the backend rate while testing.

Can I test @neil-marcellini? For the checklist.

Ah right, you won't be able to test very easily due to the need to change the backend. I'll request only an internal review.

Testing now, can we resolve conflicts?

Reviewer Checklist

[x] I have verified the author checklist is complete (all boxes are checked off).
[x] I verified the correct issue is linked in the ### Fixed Issues section above
[x] I verified testing steps are clear and they cover the changes made in this PR

[x] I verified the steps for local testing are in the Tests section
[x] I verified the steps for Staging and/or Production testing are in the QA steps section
[x] I verified the steps cover any possible failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[x] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)

[x] I checked that screenshots or videos are included for tests on all platforms
[x] I included screenshots or videos for tests on all platforms
[x] I verified tests pass on all platforms & I tested again on:

[x] Android: Native
[x] Android: mWeb Chrome
[x] iOS: Native
[x] iOS: mWeb Safari
[x] MacOS: Chrome / Safari
[x] MacOS: Desktop

[x] If there are any errors in the console that are unrelated to this PR, I either fixed them (preferred) or linked to where I reported them in Slack
[x] I verified proper code patterns were followed (see Reviewing the code)

[x] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick).
[x] I verified that the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
[x] I verified that comments were added to code that is not self explanatory
[x] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[x] I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method
[x] I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
[x] I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
[x] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[x] I verified the JSDocs style guidelines (in STYLE.md) were followed

[x] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[x] I verified that this PR follows the guidelines as stated in the Review Guidelines
[x] I verified other components that can be impacted by these changes have been tested, and I retested again (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar have been tested & I retested again)
[x] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[x] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[x] If a new component is created I verified that:

[x] A similar component doesn't exist in the codebase
[x] All props are defined accurately and each prop has a /** comment above it */
[x] The file is named correctly
[x] The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
[x] The only data being stored in the state is data necessary for rendering and nothing else
[x] For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
[x] Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
[x] All JSX used for rendering exists in the render method
[x] The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions

[x] If any new file was added I verified that:

[x] The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory

[x] If a new CSS style is added I verified that:

[x] A similar style doesn't already exist
[x] The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG)

[x] If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
[x] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[x] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[x] If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
[x] If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:

[x] I verified that all the inputs inside a form are aligned with each other.
[x] I added Design label and/or tagged @Expensify/design so the design team can review the changes.

[x] If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
[x] If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.
[x] I have checked off every checkbox in the PR reviewer checklist, including those that don't apply to this PR.

Screenshots/Videos

Android: Native

Android: mWeb Chrome

iOS: Native

iOS: mWeb Safari

MacOS: Chrome / Safari

MacOS: Desktop

:hand: This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

🚀 Deployed to staging by https://github.com/youssef-lr in version: 9.0.35-0 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

@neil-marcellini @youssef-lr Can you pls confirm if we need to QA it? There are steps but also no QA note

bump on https://github.com/Expensify/App/pull/47136#issuecomment-2350742911
@neil-marcellini @youssef-lr

🚀 Deployed to production by https://github.com/grgia in version: 9.0.35-7 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

@neil-marcellini @youssef-lr Can you pls confirm if we need to QA it? There are steps but also no QA note

Yes it is no qa. I'll put it in the title next time.