What is the expiry time on the access token - it isn't 2 days like the documentation says

I get a token and then I use it every now and again. When I go to use it 26 hours after the email login, it fails on 'token expired'. Anyone have better experience with the life span of the access token? Also the documentation says that the refresh token has a lifespan of 30 days. Anyone have verification of this? This is the documentation that I am referring to: https://support.wyze.com/hc/en-us/articles/16129834216731-Creating-an-API-Key

If you take the jwts and decode them, it looks like the access token is just under 2 hours currently and the refresh is 28 days:

print(b64decode(f"{at.split('.')[1]}=="))
b'{"aud":["oauth2-resource","native_oauth2_resource"],"user_id":"","user_name":"","scope":["native"],"iss":"https://auth.wyze.com","created_at":1720391946,"exp":1720397946,"authorities":["USER"],"jti":","client_id":"*"}'
1720397946-1720391946
6000
(1720397946-1720391946) / 3600
1.6666666666666667

print(b64decode(f"{rt.split('.')[1]}"))                                                                                b'{"aud":["oauth2-resource","native_oauth2_resource"],"user_id":"","user_name":"","scope":["native"],"ati":"","iss":"https://auth.wyze.com","created_at":1720906453,"exp":1723325653,"authorities":["USER"],"jti":"","client_id":"******"}'
1723325653-1720906453
2419200
(1723325653-1720906453) / 86400
28.0


'only' and 'ignore' do not work as expected

Documentatio at: http://babeljs.io/docs/usage/options/ is misleading. Looking at the code from
https://github.com/babel/babel/blob/master/packages/babel-core/src/util.js#L114
If only setting is set then ignore is completely ignored. Documentation should reflect this to prevent anyone from accidentally attempting to use both settings which would lead to a hard to identify error.
Also I don't want to open a phabricator account so could someone bring this up on the chat / buglist / feature list for me.
Thanks.

It pretty much stands to reason that you wouldn't whitelist something only to blacklist it and that whitelisting is more explicit than blacklisting, but I don't see a problem with being specific.

Also I don't want to open a phabricator account so could someone bring this up on the chat / buglist / feature list for me.

I don't blame you, but:

I think you can sign in to the Phabricator with your GitHub account.
This is the buglist for the documentation, so this is actually the correct place. If you thought there was a bug in the behavior of the options the Phabricator tracker would be the right place.

@jmm Yes a small footnote would help. We don't want people wondering why its not working now do we. Any Idea when the change will make it into the documentation so I can close this?

👎


FR: Add e-commerce example that uses pop-over purchase sheet

Feature request to add an e-commerce pop-over sheet for completing a purchase (customizing) from a product detail page. AliExpress, for instance, uses this pattern, once you click "buy now".
Should be possible with amp-bind, but definitely worth flagging any barriers that need implementation in amphtml
/cc @sebastianbenz @kul3r4

Happy to take a look, which step of the purchase do you mean? "Review your order", "payment" or "done"? The page loads very very slow for me

(note that we can hold off on this until after I/O :)
If I open the link on mobile (I forgot to mention to use mobile—sorry about that!), I land here:

When I click "buy now" a sheet pops up from the bottom:

Which allows you to configure your purchase with additional options, without leaving the page.
The idea is to demo this general interaction of a popover sheet to configure the purchase with details not available on the main product page. I'm not sure what page has "review your order", "payment", or "done" on it — maybe that's on the desktop version?

Yes, that was on desktop. Sounds good, thanks for the snapshots!


Adds an hours command to bot

the initial hours implementation is setup to scrape the library public
website using Watir. the reasoning for this is as follows:

There is no single JSON feed to query directly
The existing 'json' feeds still require significant processing which
would heavily overlap, and add many dependencies to, the JS-based
implementation on the public website
We cannot do a 'normal' Mechanize/Nokogiri query directly because the
hours data is rendered completely by JS. So not available in the DOM.

A dependency is added to phantomjs for Watir. This allows for headless
browsing. Since this dependency is slow/heavy, a local hours file is
cached for the current day to speed up additional queries. I think it's
the best option we have "for now"

Coverage remained the same at 96.552% when pulling 17c0ace584bee22d853eb7e835e019848564eb53 on feature/no-todos into b953aacc52f86f55d9a76feca995a3e14d593db0 on develop.


Global search bar (cmd + k)

What problem are you trying to solve?
currently, there is no way to search through all the information crowd.dev stored
What's your suggested solution?
Make all workspace content searchable (with cmd+k)
Examples (if relevant)
No response
Is anything blocking this from being implemented? (if relevant)
No response
Definition of Done
No response

duplicate

duplicate


hyp_dateFromISO8601String: Not converting to millisecond precision

For example, when using Sync to map the string 2016-05-06T19:04:19.911Z to NSDate, then using NSDateFormatter.stringFromDate to convert back to a string, I get 2016-05-06T19:04:19.000Z.

Damn, this should be straightforward though. Feel free to submit a PR.

Well, not that straightforward ;).  The C functions you were using (strptime and mktime don't support millisecond precision, so I had to use NSDateFormatter instead.  #104

@bonebox I guess you're right! I went for the C functions because using NSDateFormatter is really slow compared to doing it with C. Since dates are so common this change could increase the parsing time considerably. 😞

Also the date parsing code is pretty bad documented. Sorry for that.

Microsecond support is missing, although that's probably not critical.
https://github.com/hyperoslo/NSManagedObject-HYPPropertyMapper/pull/105

Yeah, I figured that was why you weren't using it. I first tried something like your solution but couldn't get it to work like I wanted. Anyway, thanks for updating it!


Is there a way to not block for event handlers?

The problem:

place order -> PlaceOrderCommand() -> OrderPlacedEvent() -> handling outside of the aggregate
The bold part should not block the place order but it does. I am using AxonServerEventStore, and TracingCommandGateway. Maybe there is a way to configure this so I command gateway doesn't have to wait?

In the picture, I should be able to get my result at 4.2s, but it is only returned at 6.4s after the event handling thing which is in a projection

Hi @Sam-Kruglov, trying to follow your train of thought here.
What is the exact problem you're experiencing?
So, would you mind breaking it down in (1) what you are trying to do, (2) what you are expecting to see happening in this scenario and (3) what is actually happening?
Based on that, I think I can help you out further with this.

Preconditions:

The time required to receive an API call, to publish the command, handle the command, and publish an event takes 4.2 seconds.
The time required to handle an event by all projections takes 2.2 seconds.

I am trying to place an order, to get an event published and an id returned to the caller.
Get an id back after 4.2 seconds.
Getting an id back after 6.4 seconds.

Hi Sam,
if event processing is done through Subscribing Event Handlers, they will be processed in the thread that published the events. Hence, a longer processing time will mean longer publication (and command handling) time.
If, however, you assign handlers to a tracking processor (which is default as of Axon 4, when using an Event Store), then processing is always asynchronous.
I'm closing the issue as it currently doesn't seem to require any changes in code. Feel free to continue commenting.

Thanks, @abuijze!
Do you think putting even handling in a separate unit if work would be a bad idea?

Strictly speaking, events are always handled in their own Unif of Work, but when it is handled in the same thread, then the "inner" unit of work is connected to the "outer" one. But that implementation details ;-)
It's definitely not a bad idea. There are pros and cons to both approaches. We do recommend async by default (that's why it's the default since Axon 4). In specific usecases, it is beneficial to not have to deal with async behavior and be able to handle everything in the same (acid) transaction.


Add MathJax equation to Murphy_thetas (in both continuous and probability)

Actually, on further reflection, I am not sure that a formula is needed specifically for murphy_thetas. I will close this issue, but if it anyone thinks it is needed, please reopen (or open a new issue).


feat: add ability to rename native wallets

Description
Add the ability to rename native wallets

Replaced the Forget? button with a DeleteIcon
Added a EditIcon button for the rename action
Added a dedicated step in the modal (with new nickname and password to decrypt wallet)
Handling of the rename action

See video below for visual details.
Notice
Before submitting a pull request, please make sure you have answered the following:

[x] Have you followed the guidelines in our Contributing guide?
[x] Have you checked to ensure there aren't other open Pull Requests for the same update/change?
[x] Do all new and existing tests pass? Does the linter pass?

Pull Request Type

[ ] :bug: Bug fix (Non-breaking Change: Fixes an issue)
[ ] :hammer_and_wrench: Chore (Non-breaking Change: Doc updates, pkg upgrades, typos, etc..)
[x] :nail_care: New Feature (Breaking/Non-breaking Change)

Issue (if applicable)
closes #498
Screenshots (if applicable)
https://user-images.githubusercontent.com/5672954/147755638-eae1e681-1b92-4b2f-a941-bd4c7be6b06e.mov

@theoboldfrazier thank you for your feedback.
I wrapped the 2 icons inside a Box as suggested.

🔥 🇫🇷

The edit button needs to be on the right next to the delete button not weirdly floating in the middle. Can you make a screenshot where there are multiple wallets with both short and very long names?
What is the character limit on name?

You don't have any validations for the "name" input. What happens if they input an empty name is given? What if the name is crazy long? is HTML escaped?


WIP: Check remote for org secrets permissions

Currently org secrets can only be set by a DRONE_ADMIN.  This PR attempts to lay the groundwork for validating permissions for a user against the remote.
Fully implemented for github remote.
Please let me know if approach looks acceptable, if I missed anything, etc ... feedback completely welcome!! 😃

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.

I have not tested it but so far LGTM

I'm going to work on trying it out for reals next week.  If anyone else can do that too I'd appreciate it.
Thanks for all the eyeball reviews!

I stopped:

attaching more data to the context probably isn't necessary

😄
I rebased from master also which included a caching fix I was running into.
I tested this in a dev environment with a github instance and it all seemed to work!
@bradrydzewski @tboerger @donny-dont Want to take another quick look?

LGTM thanks for this!


requirements: Upgrade python-social-auth to latest version

Fixes #3403

Automated message from Dropbox CLA bot
@sinwar, it looks like you've already signed the Dropbox CLA. Thanks!

Merged, thanks @sinwar!!


Add area of ellipse under conic section

Is your feature request related to a problem? Please describe.

A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]

Describe the solution you'd like

area of ellipse is already available but i would like to the formula and calculator in this section so that all the formulaes will be at one place

Go ahead
Deadline 22 May,2021


Added event replicator and unit tests

What is this PR for?
Added code for event replicator that will replicate event data from CDF and store in a Lakehouse table, with the table path and name configurable.
Also added unit tests for the event replicator.
What does the code do?

The code for the event replicator is in "event.py".
Adjusted config to incorporate configurations for event replicator including batch size and abfss table path
Added unit tests for the replicator in "tests/unit/test_event.py"

How do I verify the changes made?

Copy the ".env.example" to ".env" and populate proper values for all environment variables. The environment variable that's specifically for event replicator is EVENT_TABLE_NAME
The default batch size in "example_config.yaml" is set to 5. Change the batch size if needed.
[optional] In "main.py", comment out thread creation for other replicators to focus resources on the event replicator
Run poetry run cdf_fabric_replicator example_config.yaml to run the event replicator

Run poetry run pytest tests/unit/test_event.py to verify that all unit tests pass

verified event were properly replicated in the lakehouse table:

as well as the unit tests verification:


[feature] auto-update for graphs in prometheus's web interface

Right now graphs in the built-in web interface are rendered once, at a particular point in time. It'd be great if the graphs had a feature to allow themselves to auto-update; say, by refreshing once every 30 or 60 seconds.

This is already supported in console templates, look at the widget in the lower right corner.

Is this on master, but not in a release by chance?

This has been there for over a year.

Then I am confused; I don't see any widgets in the lower-right hand corner of the console tab.

You're looking at the expression browser then, which doesn't have such a feature.
Keep in mind the expression browser is intended for ad-hoc usage.

Yes indeed, however even in local dev being able to quickly glance at a
graph without needing to refresh can be very handy.
On Mon, Jul 18, 2016 at 9:36 AM, Brian Brazil<EMAIL_ADDRESS>wrote:

You're looking at the expression browser then, which doesn't have such a
feature.
Keep in mind the expression browser is intended for ad-hoc usage.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/prometheus/prometheus/issues/1817#issuecomment-233330111,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAADBJ8tbmCLCtAKxHMfND6-Cd6q1f6aks5qW4FpgaJpZM4JOtKN
.

--
"I disapprove of what you say, but I will defend to the death your right to
say it." -- Evelyn Beatrice Hall (summarizing Voltaire)
"The people's good is the highest law." -- Cicero
GPG Key fingerprint: D1B3 ADC0 E023 8CA6

Grafana can do quick dashboards like that, and has auto-reloading.

Hi, did you fix problem this auto update prom_right_table_head?

No, the expression browser still has no auto refresh. Ironically, in the first years of Prometheus, it did have auto refresh, but then someone decided that it wasn't important enough when porting some code and wanting to keep the built-in UI minimal. Not sure if we'd want to add it back, I don't have a strong opinion on it.

Considering Grafana is the tool of choice, should we close this off as wont fix?

Grafana, is separately project with mysql/sqllite backend and additional load to node, vm, server. Prometheus console small, light and suitable, and i use it in my project. Can you fix it?

@brian-brazil , any news?

Hello everyone!
Any updates? Maybe somebody can share some workaround?
I have tried to update whole page. But It looks not pretty well.
Thanks!

@brian-brazil May I help you? or not do?

I have the feeling all such features would be better suited for a UI rewrite than to keep adding to the existing code base.

Waiting for a Prometheus way to do it, you can use a barbaric solution with a browser addon (i.e. tab-auto-refresh for Firefox)

Any update for this issue ?

I see my last comment on this issue being from 2017. Now more than two years later, I am more leaning towards not doing this in Prometheus. Why, although it can be useful for a small subset of users? I think it already goes into the dashboarding use case, and if we go into that direction, then with equal right we could introduce color options, axes unit labels, different chart types, etc. And outside of dashboarding use cases I don't see many people needing this. Keeping the built-in UI simple and not overloaded is a value per se IMO, so I'm for keeping the UI scoped to ad-hoc exploration of data. Grafana is great for dashboarding and extremely easy and light-weight to set up.
I still don't feel super strongly about it, but every feature also comes with a cost along multiple dimensions (even for users), and I'm not sure enough users would need this in Prometheus.

I agree with Julius. In addition to that, we have seen with grafana that
auto refresh is not that simple:
https://github.com/prometheus/prometheus/issues/2364 . I do not wish to
open the same Pandora's box in Prometheus since grafana solved it already.
Le jeu. 26 déc. 2019 à 16:46, Julius Volz<EMAIL_ADDRESS>a
écrit :

I see my last comment on this issue being from 2017. Now more than two
years later, I am more leaning towards not doing this in Prometheus. Why,
although it can be useful for a small subset of users? I think it already
goes into the dashboarding use case, and if we go into that direction, then
with equal right we could introduce color options, axes unit labels,
different chart types, etc. And outside of dashboarding use cases I don't
see many people needing this. Keeping the built-in UI simple and not
overloaded is a value per se IMO, so I'm for keeping the UI scoped to
ad-hoc exploration of data. Grafana is great for dashboarding and extremely
easy and light-weight to set up.
I still don't feel super strongly about it, but every feature also comes
with a cost along multiple dimensions (even for users), and I'm not sure
enough users would need this in Prometheus.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/prometheus/prometheus/issues/1817?email_source=notifications&email_token=AACHHJSUA2TETXP225GFQWLQ2TGT7A5CNFSM4CJ22KG2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEHVXH3I#issuecomment-569078765,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AACHHJXGFWZFFCFYFGMWLBDQ2TGT7ANCNFSM4CJ22KGQ
.

Thanks for update:).  I tried grafana , it provides page-refresh feature and nice dashboard .

Great!
Closing this for now, see above for the reasoning.


Unable to add password authentication for riak control on browser in ubuntu 22.04

Enabled riak-admin security.
Enabled riak.auth.mode=userlist
Enabled SSL for riak server https://<IP_ADDRESS>:8098
Installed riak_kv 2.2.2
Installed nginx reverse proxy
Install certbot for SSL
We have done this configuration till now but still not able to enable password authentication for riak
Please help to resolve this issue. My team solving this error from last 3 weeks.

Thanks & Regards,
Namrata T.

@martinsumner I have done all the installations which you said but still I am not able to enable the password authentication. I created the Openssl and generate ssl and gave the path to riak.conf file still not able to access riak https://localhost:8098


Licensing concern!

The file LICENSE.txt contains the Apache 2.0 license. However, the file DISCLAIMER.txt says the rover cant be modified, distributed, or used commercially without prior approval. This is in conflict with the Apache 2.0 license.

Looks like the license is written approval for commercial use. There's no conflict, the license just overrides the disclaimer.

Wouldn't it make more sense to remove that section of the desclaimer to avoid future confusion ?

@NatTuck While that may be correct, we don't want uncertainty. In addition, by downloading you agree to both the Apache 2 license and the disclaimer.

I'm working with the legal team to get this resolved in a way that's more clear and concise.  Thanks for bringing this to our attention.

hi everyone, I manage our Advanced IT Research and Open Source office at NASA JPL. Our position is that the license chosen overrides the disclaimer. We have approval to license this software under the Apache License, version 2, which allows others to do what they wish (even build commercial software on it). That should supersede the attached disclaimer which are artifacts of an evolving OSS release process that we are trying to improve.
You may cite this comment should the need arise, which I doubt it will (ever). Enjoy the OSS rover and great work @vssystemluba and team!


browserify not work

Because of browser's polyfill, Buffer is object and will be considered as dictionary whenbencode.encode.
example:
const data = { error: Uint8Array.from([101, 114, 114, 111, 114]) }
const result = bencode.encode(data)
console.log(result)

The expected result is d5:error5:errore, but the real result is d5:errordi0e:i101ei1e:i114e....
  switch (typeof data) {
    case 'string':
      encode.buffer(buffers, data)
      break
    case 'number':
      encode.number(buffers, data)
      break
    case 'object':
      data.constructor === Array
        ? encode.list(buffers, data)
        : encode.dict(buffers, data)
      break
    case 'boolean':
      encode.number(buffers, data ? 1 : 0)
      break
  }

typeof will return 'object' for Buffer, if browser's polyfill works.

Sorry that it took that long.
I'm not an expert with browserify and I'm not really sure on how we could fix this.
Detecting "Uint8Array" and handle it as an buffer seems to be wrong for cases where people actually want it to be an array of ints. We can't check for valid utf-8 chars anyway.
Personally I'd tend to say "We don't care about browserify, fix this in 'userland'." But thats not the best way to handle it I guess.
@jhermsmeier any ideas on this?

Well, I guess we should check for typed arrays with value.buffer instanceof ArrayBuffer and then at least handle them as lists, not dicts.
Thinking about it, @feross might have run into similar issues with this in WebTorrent?
I'll explore this further later today.

@jhermsmeier In WebTorrent, we're careful to not pass in Buffer properties to bencode.encode.
Right now, Buffer is being treated like a dictionary, which doesn't make sense.  A good solution to this problem is to treat a Buffer like a string. You can detect a buffer with Buffer.isBuffer(), then call buffer.toString(). Or, treating them like arrays is reasonable too.

could #64 close this issue now?

could #64 close this issue now?

Looks like it.

Oh, yeah, great!


Test view inputs in interface tests

Possible test to add to https://github.com/JuliaMath/AbstractFFTs.jl/pull/116
Note that this PR is to #116's branch (i.e. basically a code suggestion, but needed to do it this way since the test file was previously unchanged)

Seems good and useful to me :+1:


Remove download from travis

Codecov Report

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

@@           Coverage Diff           @@
##           master      #75   +/-   ##
=======================================
  Coverage   98.23%   98.23%
=======================================
  Files          16       16
  Lines         226      226
=======================================
  Hits          222      222
  Misses          4        4

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 34d1972...00955bc. Read the comment docs.


Fix color theming bugs

Alaska Airlines Pull Request
Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change.
Resolves:
Summary:
Please summarize the scope of the changes you have submitted, what the intent of the work is and anything that describes the before/after state of the project.

Update dependencies
Fix small issues with the color theming tokens

Type of change:
Please delete options that are not relevant.

[ ] New capability
[x] Revision of an existing capability
[ ] Infrastructure change (automation, etc.)
[ ] Other (please elaborate)

Checklist:

[x] My update follows the CONTRIBUTING guidelines of this project
[x] I have performed a self-review of my own update

By submitting this Pull Request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
Pull Requests will be evaluated by their quality of update and whether it is consistent with the goals and values of this project. Any submission is to be considered a conversation between the submitter and the maintainers of this project and may require changes to your submission.
Thank you for your submission!
-- Auro Design System Team

Summary by Sourcery
Fix color theming issues in checkbox components by updating the theming tokens to ensure consistent appearance across various states, including focus, hover, and error.
Bug Fixes:

Correct color theming tokens for checkbox components to ensure consistent theming across different states such as focus, hover, and error.

:tada: This PR is included in version 3.1.0-beta.2 :tada:
The release is available on:

npm package (@beta dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Use netatalk 2.x release tarballs

I noticed that you're using the bleeding edge of my netatalk 2.x fork in this script https://github.com/danmons/retronas/blob/main/ansible/templates/install_netatalk2x/install_netatalk2x.sh.j2
You may want to consider using a release tarball instead, e.g. https://github.com/rdmark/netatalk-2.x/releases/tag/netatalk-2-230301
I don't really have a development or testing process in my fork, so I may break things in HEAD at any time. The release tarballs have a modicum of quality assurance in place.
Now, I didn't confirm if this script is actually in use or not, so please ignore this if it's an abandoned script.

Optional, but you may also want to consider pivoting to upstream netatalk 2.2.8 https://github.com/Netatalk/netatalk/releases/tag/netatalk-2-2-8
I've spent the last year gradually bringing upstream up to speed with my 2.x fork. There are still some marginal advantages to 2.x, mostly around code quality and maintainability.

Thanks for the heads up.  I'll add a line or two in there to checkout the latest tag (which looks to line up with your release tarballs) so we're not always compiling main/HEAD.
Great to hear you're pushing upstream back into line as well.  I'll take a look at that when I get some time.

I've switched to pulling the latest netatalk-2-* tag while fixing #316


BUG: Backwards incompatibility in 1.12.0: scipy.array not defined

Describe your issue.
I discovered that updating scipy to 1.12.0 breaks some libraries I use. In this case the offending code seems to be in plotly. The reason seems to be that the previous version, 1.11.4, exported scipy.array, which is the same as numpy.array, and these libraries have imported array from there instead of from numpy.
I do not know if you consider this a bug, but at least FYI.
Reproducing Code Example
import scipy
scipy.array

Error message
Traceback (most recent call last)
File ~/proj/waste/.venv/lib/python3.11/site-packages/scipy/__init__.py:137, in __getattr__(name)
    136 try:
--> 137     return globals()[name]
    138 except KeyError:

KeyError: 'array'

During handling of the above exception, another exception occurred:

AttributeError                            Traceback (most recent call last)
File <frozen runpy>:198, in _run_module_as_main(mod_name, alter_argv)

File <frozen runpy>:88, in _run_code(code, run_globals, init_globals, mod_name, mod_spec, pkg_name, script_name)

File ~/proj/waste/topic_analysis.py:69
     65     fig.write_html("hierarchy.html", auto_open=True)
     68 if __name__ == "__main__":
---> 69     main()

File ~/proj/waste/topic_analysis.py:63, in main()
     60 IPython.embed()  # type: ignore[no-untyped-call]
     62 logger.info("Plotting hierarchy")
---> 63 fig = topic_model.visualize_hierarchy(hierarchical_topics=hierarchical_topics)
     64 logger.info("Writing hierarchy to hierarchy.html")
     65 fig.write_html("hierarchy.html", auto_open=True)

File ~/proj/waste/.venv/lib/python3.11/site-packages/bertopic/_bertopic.py:2802, in BERTopic.visualize_hierarchy(self, orientation, topics, top_n_topics, custom_labels, title, width, height, hierarchical_topics, linkage_function, distance_function, color_threshold)
   2734 """ Visualize a hierarchical structure of the topics
   2735
   2736 A ward linkage function is used to perform the
   (...)
   2799 style="width:1000px; height: 680px; border: 0px;""></iframe>
   2800 """
   2801 check_is_fitted(self)
-> 2802 return plotting.visualize_hierarchy(self,
   2803                                     orientation=orientation,
   2804                                     topics=topics,
   2805                                     top_n_topics=top_n_topics,
   2806                                     custom_labels=custom_labels,
   2807                                     title=title,
   2808                                     width=width,
   2809                                     height=height,
   2810                                     hierarchical_topics=hierarchical_topics,
   2811                                     linkage_function=linkage_function,
   2812                                     distance_function=distance_function,
   2813                                     color_threshold=color_threshold
   2814                                     )

File ~/proj/waste/.venv/lib/python3.11/site-packages/bertopic/plotting/_hierarchy.py:141, in visualize_hierarchy(topic_model, orientation, topics, top_n_topics, custom_labels, title, width, height, hierarchical_topics, linkage_function, distance_function, color_threshold)
    138 distance_function_viz = lambda x: validate_distance_matrix(
    139     distance_function(x), embeddings.shape[0])
    140 # Create dendogram
--> 141 fig = ff.create_dendrogram(embeddings,
    142                            orientation=orientation,
    143                            distfun=distance_function_viz,
    144                            linkagefun=linkage_function,
    145                            hovertext=annotations,
    146                            color_threshold=color_threshold)
    148 # Create nicer labels
    149 axis = "yaxis" if orientation == "left" else "xaxis"

File ~/proj/waste/.venv/lib/python3.11/site-packages/plotly/figure_factory/_dendrogram.py:94, in create_dendrogram(X, orientation, labels, colorscale, distfun, linkagefun, hovertext, color_threshold)
     91 if distfun is None:
     92     distfun = scs.distance.pdist
---> 94 dendrogram = _Dendrogram(
     95     X,
     96     orientation,
     97     labels,
     98     colorscale,
     99     distfun=distfun,
    100     linkagefun=linkagefun,
    101     hovertext=hovertext,
    102     color_threshold=color_threshold,
    103 )
    105 return graph_objs.Figure(data=dendrogram.data, layout=dendrogram.layout)

File ~/proj/waste/.venv/lib/python3.11/site-packages/plotly/figure_factory/_dendrogram.py:148, in _Dendrogram.__init__(self, X, orientation, labels, colorscale, width, height, xaxis, yaxis, distfun, linkagefun, hovertext, color_threshold)
    145 if distfun is None:
    146     distfun = scs.distance.pdist
--> 148 (dd_traces, xvals, yvals, ordered_labels, leaves) = self.get_dendrogram_traces(
    149     X, colorscale, distfun, linkagefun, hovertext, color_threshold
    150 )
    152 self.labels = ordered_labels
    153 self.leaves = leaves

File ~/proj/waste/.venv/lib/python3.11/site-packages/plotly/figure_factory/_dendrogram.py:346, in _Dendrogram.get_dendrogram_traces(self, X, colorscale, distfun, linkagefun, hovertext, color_threshold)
    337 Z = linkagefun(d)
    338 P = sch.dendrogram(
    339     Z,
    340     orientation=self.orientation,
   (...)
    343     color_threshold=color_threshold,
    344 )
--> 346 icoord = scp.array(P["icoord"])
    347 dcoord = scp.array(P["dcoord"])
    348 ordered_labels = scp.array(P["ivl"])

File ~/proj/waste/.venv/lib/python3.11/site-packages/scipy/__init__.py:139, in __getattr__(name)
    137     return globals()[name]
    138 except KeyError:
--> 139     raise AttributeError(
    140         f"Module 'scipy' has no attribute '{name}'"
    141     )

AttributeError: Module 'scipy' has no attribute 'array'

SciPy/NumPy/Python version and system information
Before update (old version where this works):

1.11.4 1.26.3 sys.version_info(major=3, minor=11, micro=4, releaselevel='final', serial=0)
Build Dependencies:
  blas:
    detection method: pkgconfig
    found: true
    include directory: /usr/local/include
    lib directory: /usr/local/lib
    name: openblas
    openblas configuration: USE_64BITINT= DYNAMIC_ARCH=1 DYNAMIC_OLDER= NO_CBLAS=
      NO_LAPACK= NO_LAPACKE= NO_AFFINITY=1 USE_OPENMP= HASWELL MAX_THREADS=2
    pc file directory: /usr/local/lib/pkgconfig
    version: 0.3.21.dev
  lapack:
    detection method: pkgconfig
    found: true
    include directory: /usr/local/include
    lib directory: /usr/local/lib
    name: openblas
    openblas configuration: USE_64BITINT= DYNAMIC_ARCH=1 DYNAMIC_OLDER= NO_CBLAS=
      NO_LAPACK= NO_LAPACKE= NO_AFFINITY=1 USE_OPENMP= HASWELL MAX_THREADS=2
    pc file directory: /usr/local/lib/pkgconfig
    version: 0.3.21.dev
  pybind11:
    detection method: config-tool
    include directory: unknown
    name: pybind11
    version: 2.11.0
Compilers:
  c:
    commands: cc
    linker: ld.bfd
    name: gcc
    version: 10.2.1
  c++:
    commands: c++
    linker: ld.bfd
    name: gcc
    version: 10.2.1
  cython:
    commands: cython
    linker: cython
    name: cython
    version: 0.29.36
  fortran:
    commands: gfortran
    linker: ld.bfd
    name: gcc
    version: 10.2.1
  pythran:
    include directory: ../../tmp/pip-build-env-lzd6dam0/overlay/lib/python3.11/site-packages/pythran
    version: 0.14.0
Machine Information:
  build:
    cpu: x86_64
    endian: little
    family: x86_64
    system: linux
  cross-compiled: true
  host:
    cpu: x86_64
    endian: little
    family: x86_64
    system: linux
Python Information:
  path: /opt/python/cp311-cp311/bin/python
  version: '3.11'

After update:

1.12.0 1.26.3 sys.version_info(major=3, minor=11, micro=4, releaselevel='final', serial=0)
Build Dependencies:
  blas:
    detection method: pkgconfig
    found: true
    include directory: /usr/local/include
    lib directory: /usr/local/lib
    name: openblas
    openblas configuration: USE_64BITINT= DYNAMIC_ARCH=1 DYNAMIC_OLDER= NO_CBLAS=
      NO_LAPACK= NO_LAPACKE= NO_AFFINITY=1 USE_OPENMP= HASWELL MAX_THREADS=2
    pc file directory: /usr/local/lib/pkgconfig
    version: 0.3.21.dev
  lapack:
    detection method: pkgconfig
    found: true
    include directory: /usr/local/include
    lib directory: /usr/local/lib
    name: openblas
    openblas configuration: USE_64BITINT= DYNAMIC_ARCH=1 DYNAMIC_OLDER= NO_CBLAS=
      NO_LAPACK= NO_LAPACKE= NO_AFFINITY=1 USE_OPENMP= HASWELL MAX_THREADS=2
    pc file directory: /usr/local/lib/pkgconfig
    version: 0.3.21.dev
  pybind11:
    detection method: config-tool
    include directory: unknown
    name: pybind11
    version: 2.11.1
Compilers:
  c:
    commands: cc
    linker: ld.bfd
    name: gcc
    version: 10.2.1
  c++:
    commands: c++
    linker: ld.bfd
    name: gcc
    version: 10.2.1
  cython:
    commands: cython
    linker: cython
    name: cython
    version: 3.0.8
  fortran:
    commands: gfortran
    linker: ld.bfd
    name: gcc
    version: 10.2.1
  pythran:
    include directory: ../../tmp/pip-build-env-wkrrblds/overlay/lib/python3.11/site-packages/pythran
    version: 0.15.0
Machine Information:
  build:
    cpu: x86_64
    endian: little
    family: x86_64
    system: linux
  cross-compiled: false
  host:
    cpu: x86_64
    endian: little
    family: x86_64
    system: linux
Python Information:
  path: /opt/python/cp311-cp311/bin/python
  version: '3.11'

scipy.array is one of the things that was removed in gh-19067 after a long deprecation.
What this means for you is that your plotly version is not yet compatible with SciPy 1.12.0. Either upgrading plotly will fix this, or you'll need to wait for a release, depending on whether they've fixed it yet or not.

aha, https://github.com/plotly/plotly.py/pull/4487. So it's fixed on plotly main now, just need to wait for a new release from them before you can upgrade your SciPy version.

@rgommers it looks like those removals are missing from https://docs.scipy.org/doc/scipy/release/1.12.0-notes.html#expired-deprecations, which was pointed out over at plotly.

@rgommers it looks like those removals are missing from https://docs.scipy.org/doc/scipy/release/1.12.0-notes.html#expired-deprecations, which was pointed out over at plotly.

Ah, that looks like an oversight. We can fix that retroactively.
Doesn't look like it would have made a difference here of course; the real change comes from actually paying attention to deprecation warnings.


[BUG] When we add another management network to VM and save. VM keeps in Starting state

Describe the bug

When we add a new management network to the virtual machine which already have an external vlan on it. (Without stop VM first)
After we save it and restart VM, the VM keep in Starting state

And event have FailedMount and FailedMapVolume error

To Reproduce
Steps to reproduce the behavior:

Create a cluster network
Create a network config on the cluster network and set uplink NIC to All nodes
Create a external vlan network vlan101
Create a VM and set external vlan vlan101
Wait the VM in Running state
Edit the VM
Add new network and set management network
Click save and restart VM

Expected behavior

Should be able to start VM correctly after adding the management network to VM
Support bundle

supportbundle_fe5a95fb-b45e-4d62-87e6-b1cdba8bb20d_2023-03-30T08-39-45Z.zip
Environment

Harvester ISO version: v1.1.2-rc5
Underlying Infrastructure (e.g. Baremetal with Dell PowerEdge R630): 4 nodes kvm machines

Additional context
Add any other context about the problem here.
This issue did not happen when we add management network on VM have vlan1 network
Workaround
Stop the VM and click start again. The VM can start in Running state correctly

@TachunLin I tried this in v.1.3.1 (different iterations with similar steps) and do not see any issues.Possibly should have been fixed by https://github.com/harvester/harvester/pull/3741.Please let me know your views.


Fix #60: restore build with GHC 7.10 - 8.8

Fix #60: restore build with GHC 7.10 - 8.8

good bye (for a long while) to the very recent LANGUAGE extensions BlockArguments and ImportQualifiedPost
import (<>) from semigroups in testsuite for GHC <= 8.2
guard ghc-option -Wcompat under impl(ghc >= 8.0) conditional
document supported GHC versions in tested-with field

Thank you! Those extensions are not that important to break compatibility with older GHC versions. Not sure about 7.x (does anybody still use it?), but 8.x must be supported.

Thanks for the quick action!

Not sure about 7.x (does anybody still use it?)

I don't know (Ubuntu LTS 18.04 is on GHC 8.0.2);;; but as long as it is no effort, I think GHC 7.10 can be supported as well.
(I am maintaining some old packages, so I have all major GHCs from 7.0 installed...)


Reconnecting a client

Are there any recommended code snippets for implementing reconnecting a client if it disconnects from the server?

It looks like doing something to the extent of works inside of the  onClose() method:
    new Thread(() ->
    {
        this.reconnect();
    }).start();


10 HotLoader does not work

Sample 10 HotLoader does not work (fresh install, no changes made on my end). When a change is made in the code, the hot loader does not update the app in the browser. I have to refresh the page. Any ideas please how to fix this?

@Nasdan Does the pull request fix this hot loader issue?

What changes did you do? Could you create a step by step summary about how to reproduce it?

@crsanti @Nasdan  I did not change anything. Simply checkout this repo and run npm install and then npm start and you will see that when you update a component, the hot reload will happen ONLY in the console, but you will NOT be able to see the change in the actual component UNLESS you hit hard refresh (F5). Let me know if you can reproduce it.


Generate noSuchMethod forwarders for private member without user-defined noSuchMethod

Consider the following example:
// ======== foo.dart ========
import './bar.dart';

class Foo implements Bar {}

main() {
  baz(new Foo());
}

// ======== bar.dart ========
class Bar {
  void _f() {}
}

void baz(Bar bar) {
  print("${bar._f.runtimeType}");
}

Function baz from bar.dart correctly assumes the presence of method _f in objects of class Bar, and that the method can be torn off.  However, in the example above it's not possible without generating a noSuchMethod forwarder for _f (with a name visible only in bar.dart).  When run, the program above results in the following output:
$ out/ReleaseX64/dart /tmp/foo.dart
Unhandled exception:
NoSuchMethodError: Class 'Foo' has no instance getter '_f'.
Receiver: Instance of 'Foo'
Tried calling: _f
#0      Object.noSuchMethod (dart:core/runtime/libobject_patch.dart:46:5)
#1      baz (file:///tmp/bar.dart:6:16)
#2      main (file:///tmp/foo.dart:6:3)
#3      _startIsolate.<anonymous closure> (dart:isolate/runtime/libisolate_patch.dart:279:19)
#4      _RawReceivePortImpl._handleMessage (dart:isolate/runtime/libisolate_patch.dart:165:12)

Currently, noSuchMethod forwarders are generated only in the presence of a user-defined noSuchMethod in the class.  This mechanism should be extended for concrete classes that should have implementations of private members defined by their interfaces in other libraries, even when they don't have a user-defined noSuchMethod.
Note that if a user-defined noSuchMethod is given to Foo in the example above, the program works as expected and prints out the following:
$ out/ReleaseX64/dart /tmp/foo.dart
() => void

Triaged: punting out of stable

An update to nosuchmethod-forwarding.md is available in this CL, awaiting reviews.

Work is started.

The fix is being worked on in CL 79209.


create a windows platform issue tracker I know Windows is close but issue tracker of that may be open source :))

don't read this title like stupid peoples, this is only place I can talk while most of developers hear..
hi, for rational and intelligence system feed backing is needed ....

Maybe bring this up at https://techcommunity.microsoft.com/t5/Windows-10/ct-p/Windows10 ?


(#1572) Record aging improvements

Help improve #1572 but was not able to find the root cause for the unmarshal error. @amangale if you can provide more insight, I might be able to reproduce it but I was not able to.
Closes #1572

Coverage increased (+0.05%) to 39.624% when pulling 07a6fc9484c125e364ea02cdf17debbd77914414 on 1572-record-aging-improvements into f0a381a524a6d37e3e023496ea1dec0bac0e4f95 on ethereum-master.


[Proposal] Expand limits for breaks, pls

There are only 2 break periods available to add. It is impossible to add more.
Sometimes it is like that:
Here I manually added breaks via raw tags editor. It shows correctly in the app though

Thanks, I didn't think a venue would have so many breaks. I've increased the limit to four for the next version.


Exposing the verify functionality

The code needed to parse and verify SLSA files exists, but the functionality is not yet accessible from the command-line.
Regardless of the high level approach wrt to SLSA, TOML etc, I definitely need that functionality for the plan of using this tool outlined in: https://github.com/project-oak/oak/pull/2519#issuecomment-1030234644
How should we move forward with this? :) cc @rbehjati @tiziano88

This is left as a TODO in the README.
The idea is that verify is a library that can be used by anyone in any go project. Adding a command line tool on top of it sounds fine to me.

I'm glad that that is acceptable. How would propose going about doing that? I'm aware it's a TODO down the road atm. It is also blocking functional requirement for https://github.com/project-oak/oak/pull/2519#issuecomment-1030234644, so we'll it sooner for that

I think we just need a simple CLI tool in cmd/verify/ similar to cmd/build/main.go.
The verify tool will take a SLSA provenance file, so I think the CLI can be added right after merging #16. Right?

That would be possible, yes :)


The default subject is bintray, not 'jcenter`

The code is good, typo is in the doc only.

merged. Thanks !


Move the default implied on date for nodejs-compat-v2

Push back the date where nodejs-compat implies nodejs-compat-v2
@dom96 @vickykont ... this would need to go out into a release this week.

The date is intended to align with the start of birthday week.


Update security_groups_driver.py

hyperv_networking:9.0.0
*OpenStack fails to add the VMNetworkAdapterExtendedACL populated by security groups while attaching interface to the provisioned Hyper-V virtual machine or at the time of provisioning and generate Error - too many values to unpack at line 90  for ip, mac in self._sg_members[remote_group_id][ethertype].
**Patch included

Thank you for your contribution!
This GitHub repository is just a mirror of https://opendev.org/openstack/networking-hyperv, where development really happens. Pull requests proposed on GitHub are automatically closed.
If you are interested in pushing this code upstream, please note that OpenStack development uses Gerrit for change proposal and code review.
If you have never contributed to OpenStack before, please see:
https://docs.openstack.org/contributors/code-and-documentation/quick-start.html
Feel free to reach out to the First Contact SIG by sending an email to the openstack-discuss list with the tag '[First Contact]' in the subject line. To email the mailing list, you must first subscribe which can be done here:
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-discuss


Repo sync for protected CLA branch

The pull request is created from main637939335099273283sync_temp to main to fix git push error for protected CLA branch

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


Custom Environment

I would like to share non-serialisable objects across workers/threads. What is the recommended way to do so? Do I need to create my own /bin/worker, WorkerProcess, WorkerThread and WorkerFactory or is there a more simple way of creating a new (or populating existing) environment?

Why do you need to share such an object?

I try to implement a job queue with amphp/parallel. The job queue has a runner (worker) which is  responsible to execute jobs. The runner and jobs are designed to share the same execution context.
This context can vary based on a job queue configuration, but literally it can hold instances of any type (including resources, closures, anonymous classes, etc). For example, by default, runners and jobs share the same logger and queue instances.
I can recreate these instances in Task::run() on every call via custom (serializable) factories, but seems like an environment object suites better in this case, as I can build context objects only once per worker and simply share them via the task environment.

Sharing resources and closures with multiple processes isn't really possible. PHP is shared nothing. But I have to say I'm not really familiar with amphp/parallel yet. I'll defer to @trowski.

Sharing resources and closures with multiple processes isn't really possible. PHP is shared nothing.

True. That is why I want to recreate them per process and then share with all tasks running by this process via environment (check this line). I'm just looking for an easy way to inject my resources to this environment (or replace it with my custom one). For example, like it's done for other services:
Loop::setState(TASK_ENV_IDENTIFIER, $myEnvironemnt);

https://github.com/amphp/parallel/blob/master/lib/Worker/functions.php#L64-L75

Environment is just a simple "global" key/value store with an optional TTL (expiration) on keys. If you want to share something that cannot be serialized amongst tasks, it should be stored in the Environment object given to Task::run(). Generally the easiest way to do this is to have the run method of each task check for the existence and create it if necessary.
<?php

class ExampleTask implements Task {
    const DB_KEY = ExampleTask::class . "-db";

    public function run(Environment $environment) {
        $db = $environment->get(ExampleTask::DB_KEY);

        if ($db === null) { // DB connection didn't exist.
            $db = new Database; // Unserializable object.
            $environment->set(ExampleTask:: DB_KEY, $db);
        }

        // Use $db for task.

        return $serializableTaskResult;
    }
}

Note that the instance of Environment is per-worker, so in this example there will be a database connection in each worker.
If you want to create a custom implementation of Environment, you'll then have to create a copy of bin/worker and your own instance of Worker and WorkerFactory creating a worker using that PHP script. I may consider making this sort of thing easier to implement in a future version (will be tagging this lib after Amp v2 is officially released)… but generally BasicEnvironment should do everything necessary.

@trowski Thank you for the explanation and links. Actually, I was also thinking about checking environment for the existence and create objects in Task::run() if they miss. And, indeed, it seems like the easiest way to achieve what I need. Thanks :)


Invalid document key: '_________20230101_txt-1'. Keys cannot start with a leading underscore.

If you do "pwsh . \Јscripts\prepdocs.ps1" will change only the Japanese part of the filename in the DATA to underscores.
What is used is a text file.

Related: https://github.com/Azure-Samples/azure-search-openai-demo/issues/334
cc @tonybaloney We saw this issue when experimenting with non-ASCII filenames, I believe.

@pamelafox
Thank you.
I have tried but the error is not resolved.
Message: The request is invalid. Details: actions : 0: Invalid document key: '_______20230322_txt-0'. Keys cannot start with a leading underscore. 1: Invalid document key: '_______20230322_txt-1'. Keys cannot start with a leading underscore. 2: Invalid document key: '_______20230322_txt-2'. Keys cannot start with a leading underscore.
Exception Details:      (InvalidDocumentKey) 0: Invalid document key: '_______20230322_txt-0'. Keys cannot start with a leading underscore. Parameters: actions
Code: InvalidDocumentKey
Message: 0: Invalid document key: '_______20230322_txt-0'. Keys cannot start with a leading underscore. Parameters: actions     (InvalidDocumentKey) 1: Invalid document key: '_______20230322_txt-1'. Keys cannot start with a leading underscore.
Code: InvalidDocumentKey
Message: 1: Invalid document key: '_______20230322_txt-1'. Keys cannot start with a leading underscore. (InvalidDocumentKey) 2: Invalid document key: '_______20230322_txt-2'. Keys cannot start with a leading underscore.
Code: InvalidDocumentKey
Message: 2: Invalid document key: '_______20230322_txt-2'. Keys cannot start with a leading underscore.

We haven't decided the best fix for it yet, but you can try changing line 226 in prepdocs.py create_section function to:
"id": re.sub("[^0-9a-zA-Z_-]","_",f"file-{filename}-{i}"),
That only works if the non-japanese parts of the filenames are unique enough. Otherwise I think we need to hash the filename to make it a unique ID with only ASCII characters.

@pamelafox
Thank you.
I have tried but the error is not resolved.
File "C:\works\azure-search-openai-demo\scripts\prepdocs.py", line 236
"id": re.sub("[^0-9a-zA-Z_-]","_",f"file-{ファイル名}-{i}"),{filename}-{i}"),
^
SyntaxError: EOL while scanning string literal

It looks like you made a different change than my suggestion, introducing a syntax error. Can you try making the exact change?

I've proposed a fix in https://github.com/Azure-Samples/azure-search-openai-demo/pull/418

I've merged my proposed fix from that PR, please try that out @ikka86 and comment on this issue if you still have issues. Thanks for letting us know!

Thanks.
I got the following error on azd up.
UnicodeDecodeError: 'utf-8' codec can't decode byte 0x8a in position 0: invalid start byte

Can you provide the full error / traceback?


Safe path library

Hello,
Any thoughts on having Relude.File use something like http://hackage.haskell.org/package/path instead of FilePath?

Hi @srid, thanks for the proposal. But we don't have plans to depend on any of the filepath libraries. One of the relude goals is minimalism, specifically:

We don't force users of relude to stick to some specific lens or text formatting or logging library.

Same goes for path libraries. There are multiple safe path libraries, and none of them is the de-facto standard in the Haskell world. We don't even expose pieces of the filepath and directory libraries which are boot libraries, for these particular reasons.


Missing walletPubKey function

Area
[] Plutus Foundation Related to the GHC plugin, Haskell-to-Plutus compiler, on-chain code
[x] Plutus Application Framework Related to the Plutus application backend (PAB), emulator, Plutus libraries
[] Marlowe Related to Marlowe
[] Other Any other topic (Playgrounds, etc.)
Describe the feature you'd like
There used to be a function called walletPubKey in Wallet.Emulator.Wallet but it's being removed in this commit due to the change of WalletId type.
But now the definition of walletPubKeyHash is essentially converting the Wallet into a MockWallet and calculate the PubKeyHash, it should be possible to define a walletPubKey function.
https://github.com/input-output-hk/plutus-apps/blob/eabb8c01bea0f6f476c01dde89b408c397de3ed5/plutus-contract/src/Wallet/Emulator/Wallet.hs#L131-L137

I can open a PR if you'd like


Rotation option/method available?

Is there any way i can rotate the displayed image? If not this would certainly be a nice feature!

Need to check if it is possible with transform: rotate() without effecting the zoom and pan.

Check this out #96! Thanks for this nice plugin!


(PDB-1199) Remove timestamps from factset hash calculation

Submitting the same factset more than once causes the factset hash to
change even though it's payload is still the same. This patch removes
those fields from the hash calculation.

@wkalt this was a fix that you originally sent over with some stuff I needed to add on

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://jenkins.puppetlabs.com/job/platform_puppetdb_intn-sys_pr/494/


Request URL variable always return empty array

After multiple exports, the variable in the request consistently produces an empty array.

Each URL parameter, such as :token, should be recognized as a variable.
After investigating the issue, I found that in the RouteProcessor class, the processRequest function is still searching for {params} enclosed in curly braces. However, the current implementation now uses :params with a colon.

Please update the regex in the processRequest function to handle :params correctly.

Route::delete('/user/tokens/{token}', [User\TokenController::class, 'delete']);
in postman I have to call this route by DELETE http://myweb.com/user/tokens/:token
So, currently I extend RouteProcessor class to my own with this custom code:
// in processRequest function
'url' => [                 'raw' => '{{base_url}}/' . $uri,                 'host' => ['{{base_url}}'],                 'path' => $uri->explode('/')->filter()->all(),                 'variable' => $uri                     ->matchAll('/(?<=:)[a-zA-Z0-9_]+(?=\??)/m')                     ->transform(function ($variable) {                         return ['key' => $variable, 'value' => ''];                     })                     ->all(),

@siddiqar am I understanding this correctly?
You'd like {token?}

To be :token instead?

If I am understanding you correctly, I think it might be better to keep them as-is since this is the way Laravel exports the routes.
In Postman you can highlight part of a URL and set it as a variable to make it configurable.

cc: @tomirons


🔧 fix: Improve Assistants File Citation & Download Handling

Summary
Thank you @jimgoo for reporting this here: https://github.com/danny-avila/LibreChat/discussions/2247
This change addresses the handling of file citations provided by the assistant and improves the overall user experience when downloading and accessing referenced files within the application.
Implemented improvements to the file citation handling and download experience:

Properly handle assistant file citations within the processMessages function, ensuring accurate source attribution as well as handling mismanaged undefined basename condition.
Add a sources list to display referenced files from file citations.
Enhance the file download UX, making downloaded files accessible within the application for seamless user experience.
Refactor processOpenAIImageOutput to correctly handle different outputs for images from OpenAI.
Create addFileToCache helper to consistently add files to the cache across the frontend.
Refactor to add ImageFile parts to the cache when processing the content stream.

Change Type

[x] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)

Testing
To test these changes, you can try reproducing the original steps highlighted in this discussion: https://github.com/danny-avila/LibreChat/discussions/2247
Checklist

[x] My code adheres to this project's style guidelines
[x] I have performed a self-review of my own code
[x] I have commented in any complex areas of my code
[x] I have made pertinent documentation changes
[x] My changes do not introduce new warnings
[x] I have written tests demonstrating that my changes are effective or that my feature works
[x] Local unit tests pass with my changes
[x] Any changes dependent on mine have been merged and published in downstream modules

Thanks @danny-avila, amazing work you’ve done with LibreChat, what an incredible project!

Thanks @danny-avila, amazing work you’ve done with LibreChat, what an incredible project!

Thank you for checking it out!


Bug: webpack's UMD global detection is incompatible with strict mode JavaScript

Do you want to request a feature or report a bug?
This is a bug.

What is the current behavior?
Please consider the following contrived webpack config:
module.exports = {
  entry: './my-lib.js',
  output: {
    filename: './my-bundle.js',
    libraryTarget: 'umd'
  }
};

When webpack creates my-bundle.js, it wraps the contents of my-lib.js in a UMD template. The template used by webpack is out of date, and uses an obsolete technique to detect the global object.
If the current behavior is a bug, please provide the steps to reproduce.

Clone the example project at https://github.com/cdata/webpack-example.
npm install
webpack
Review the contents of the generated my-bundle.js artifact

The current technique for global object detection in use by webpack is visible on line 10 of my-bundle.js:
/*  1 */ (function webpackUniversalModuleDefinition(root, factory) {
/*  2 */         if(typeof exports === 'object' && typeof module === 'object')
/*  3 */                 module.exports = factory();
/*  4 */         else if(typeof define === 'function' && define.amd)
/*  5 */                 define([], factory);
/*  6 */         else {
/*  7 */                 var a = factory();
/*  8 */                 for(var i in a) (typeof exports === 'object' ? exports : root)[i] = a[i];
/*  9 */         }
/* 10 */ })(this, function() {
//          ^--- obsolete global object detection

What is the expected behavior?
The UMD template used to wrap my-lib.js should use the global object detection technique used in the most up-to-date UMD reference templates. For example, the webpack UMD wrapper around my-bundle.js should look like:
/*  1 */ (function webpackUniversalModuleDefinition(root, factory) {
/*  2 */         if(typeof exports === 'object' && typeof module === 'object')
/*  3 */                 module.exports = factory();
/*  4 */         else if(typeof define === 'function' && define.amd)
/*  5 */                 define([], factory);
/*  6 */         else {
/*  7 */                 var a = factory();
/*  8 */                 for(var i in a) (typeof exports === 'object' ? exports : root)[i] = a[i];
/*  9 */         }
/* 10 */ })(typeof self !== 'undefined' ? self : this, function() {
//          ^--- correct global object detection

If this is a feature request, what is motivation or use case for changing the behavior?
The old UMD wrapper template used by webpack is not compatible with strict mode JavaScript.
Historically, it was not possible to load non-strict JavaScript as strict mode JavaScript without the script deliberately using the "use strict"; pragma. However, it is now possible to do this in browsers with <script type="module" src="my-bundle.js>.
UMD cannot dynamically import and export via ECMAScript Modules (ESM). However, it is still possible and useful to import UMD-wrapped libraries as leaf-nodes in an ESM dependency graph (accepting that they will probably export their modules to the detected global object). This is particularly helpful during the current transitional period, where the broader JavaScript ecosystem begins to adopt the new language-native module syntax.
The change required to make UMD-wrapped bundles compatible with strict mode is very small and is known to be compatible with a wide variety of scenarios. If webpack were to use the latest UMD templates, it would unlock authors to make use of a significant number of existing JavaScript libraries as leaf nodes in an ESM dependency graph without modification.
Please mention other relevant information such as the browser version, Node.js version, webpack version and Operating System.
I tested the example project mentioned above with:

Node.js v8.6.0
webpack v3.0.0-rc.2
OSX v10.12.6

Yep, send a PR.


WebApiContrib.Core.Formatter.Protobuf -  Can't configure RuntimeTypeModel

I use a surrogate to add support for DateTimeOffset to protobuf-net, such as this:
RuntimeTypeModel.Default.Add(typeof(DateTimeOffset), false).SetSurrogate(typeof(DateTimeOffsetSurrogate));
The input and output formatters create their own RuntimeTypeModels but don't provide any access to change the configuration.

I think I'm running into this as well. Not deserializing properly and I think this is the issue.

Actually, just figured it out. The Model is available statically. Just add this:
ProtobufInputFormatter.Model.Add(typeof(DateTimeOffset), false).SetSurrogate(typeof(DateTimeOffsetSurrogate));

Thanks, that worked for me.


[BUG] run the environment preparing script will delete exist docker

Describe the bug
run the environment preparing script.
./scripts/prepare_env.sh
During running this script will delete my existing docker instance, without warning or checking if docker exists.
Really confused.

Hi @panjunjun, could you please provide us more detail about your issue? e.g., OS version, docker verison.


Cake Extension for VS Code no longer fully working in 1.25.0 release

The Cake extension for Visual Studio Code is no longer able to find Tasks that are defined within .cake files, within the latest release of Visual Studio Code 1.25.0.  This was working previously in 1.24.0.
Has something changed that we need to update in our extension?

VSCode Version: 1.25.0
OS Version: Windows 10 1803 17134.112

Steps to Reproduce:

Install and open VS Code 1.24.0 - choco install vscode --version 1.24.0
Install Cake Extension - https://marketplace.visualstudio.com/items?itemName=cake-build.cake-vscode
Open an empty folder for testing
Open command palette and type cake
Select Cake: Install sample build file
Open command palette and type Run Task

This will show:

Install and open VS Code 1.25.0 - choco install vscode --version 1.25.0
Install Cake Extension - https://marketplace.visualstudio.com/items?itemName=cake-build.cake-vscode
Open an empty folder for testing
Open command palette and type cake
Select Cake: Install sample build file
Open command palette and type Run Task

This will show:

Does this issue occur when all extensions are disabled?: Yes/No
N/A.  This is specifically affecting code in an extension that was working previously.

Can reproduce it. Will investigate why this is happening. Checked npm and TS and their tasks still work as expected.

@gep13 I was able to track it down and the cake extension is actually missing a taskDefinition in the package.json. In the past I wrongly let these tasks slip through but they caused problems when they were customized in the tasks.json (they couldn't be correctly mapped to the real task). I fixed bugs around this and as a effect tasks with a missing task definition are dropped. I should throw an exception if this happens.
To fix this you need to add the following to the package.json:
    "taskDefinitions": [
      {
        "type": "cake",
        "required": ["script"],
        "properties": {
          "script": {
            "type": "string",
            "description": "The script to execute"
          }
        }
      }
    ]

I am sorry about that. I will also add code that will throw if you try to create a task that has a missing task definition.

Let me know if this fixes your problem.

@dbaeumer thank you so much for figuring this out!  I will get a release out as soon as possible.

It might be a good idea to document taskDefinitions in https://code.visualstudio.com/docs/extensionAPI/extension-points. Looks like currently it's only mentioned in passing in https://code.visualstudio.com/docs/extensionAPI/vscode-api#TaskDefinition  :-)

@dbaeumer I have just released a new version of the Cake Extension (0.11.3) with the fix that you suggested, and it at least partially works.  For example, if I follow the steps outlined above, I get the following:

NOTE: I added another task just for testing purposes.  However, if I open another folder in vscode, in this case, the source code for the extension itself, I get the following:

It doesn't seem to be showing the tasks from within the build.cake file, but rather only showing npm, which I am assuming is due to the presence of the package.json file in the repository.
Is this a related issue to what you have told us about already, or is there something else missing in the Cake Extension.  Thanks in advance!

@gep13 are your changes available on a branch then I can have a look.
@matklad good point.

@dbaeumer you can see the changes that I made in this commit here:
https://github.com/cake-build/cake-vscode/commit/5cd4777f30d09b8f21815b0a42f2351db5365968

@gep13 the reason for this is that your cake-build workspace has a tasks.json file of version 0.1.0 in it. Task providers never worked with tasks version 0.1.0 (even before VS Code version 1.25). Simply remove the file or migrate it to task version 2.0.0 and your cake tasks will show up.

@dbaeumer thank you again for your continued help with this.  Everything seems to be working now.


Timeouts in recommends checks (in nonlinear queries) are reported incorrectly

The context doesn't say that the timeout occurred in the recommends check, so it appears that the main function check timed-out instead.

Sure, I will try to resolve this one.

Here's an example,
❯ ./tools/rust-verify.sh ~/ETH/Src/verified-nrkernel/page-table/main.rs --verify-module spec --verify-function ArchExec::entry_base --log-all
note: verifying module spec

error: possible arithmetic underflow/overflow
   --> /Users/andreal/ETH/Src/verified-nrkernel/page-table/spec.rs:188:19
    |
188 |         let res = base + offset;
    |                   ^^^^^^^^^^^^^

note: assert_nonlinear_by has been running for 2 seconds
   --> /Users/andreal/ETH/Src/verified-nrkernel/page-table/spec.rs:184:9
    |
184 |         assert(0 <= idx * self@.entry_size(layer) < 0x1_0000_0000) by (nonlinear_arith)
    |         ^^^^^^

note: assert_nonlinear_by has been running for 4 seconds

error: assert_nonlinear_by: Resource limit (rlimit) exceeded; consider rerunning with --profile for more details
   --> /Users/andreal/ETH/Src/verified-nrkernel/page-table/spec.rs:184:9
    |
184 |         assert(0 <= idx * self@.entry_size(layer) < 0x1_0000_0000) by (nonlinear_arith)
    |         ^^^^^^

error: aborting due to 2 previous errors

verification results:: verified: 1 errors: 1
❯ ./tools/rust-verify.sh ~/ETH/Src/verified-nrkernel/page-table/main.rs --verify-module spec --verify-function ArchExec::entry_base --log-all --no-auto-recommends-check
note: verifying module spec

error: possible arithmetic underflow/overflow
   --> /Users/andreal/ETH/Src/verified-nrkernel/page-table/spec.rs:188:19
    |
188 |         let res = base + offset;
    |                   ^^^^^^^^^^^^^

error: aborting due to previous error

verification results:: verified: 1 errors: 1


List releases

Added new command to list available releases, done together with @atakanyenel

Do we plan to support installing all releases using this CLI? If not I don't see any value from this command. If I'm not able to do anything else with the release from CLI I could as well go to GitHub releases page.

My feeling is that we should be able to install an older version even with the newest CLI version. Otherwise, I need to start downgrading my client just because I need to install an older cluster...
So I added the option already in the install command to specify the release version, it identifies the config yaml to download from github by the CLI. For that, I wanted to have an easy way to see available versions and later leverage the functionality to also pick just the latest.
Maybe lets have the command for now and let's see later how to integrate into the install command in a convenient way


Refactor Storage

Currently, many SD calls report success but actually fail. A rewrite is necessary.
Investigate https://github.com/greiman/SdFat

Done as of b2534a0954ec9e6e8b9622537583e1a4b946c340


Markets Filters [follow ons]

We have mocks for a few extra pieces that should smooth the rougher edges on markets.
https://www.figma.com/design/cuSW3HCchxWeKC8CEvn029/Markets-Page-%26-Watchlist?node-id=1118-1578&node-type=frame&t=lOadxXVRus99U0ce-11
and mobile: https://www.figma.com/design/cuSW3HCchxWeKC8CEvn029/Markets-Page-%26-Watchlist?node-id=1118-3104&node-type=frame&t=lOadxXVRus99U0ce-11
Sorting by market cap, volume, price change.

Ascending and descending too.

Implement all sorting / filtering options that are available natively from coingecko APIs  / portals API

Something I wanted to add here was my experience inside the markets page. It is a hit or miss of loading 1-click defi opportunities on BNB as well as Arbitrum. Sometimes opportunities load, sometimes not. Shared more here: https://ptb.discord.com/channels/554694662431178782/1293593369800605716/1293593374674386988

yeah @hpayne1 heard. noticing the same.

to fix your trouble check this solution click
maybe this will solve your problem.


fix vulnerabilities

Was this tested???  I still see the message..
C:\repos\cbus-web>npm install
npm WARN deprecated<EMAIL_ADDRESS>Modern JS already guarantees Array#sort() is a stable sort, so this library is deprecated. See the compatibility table on MDN: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Array/sort#browser_compatibility
npm WARN deprecated<EMAIL_ADDRESS>See https://github.com/lydell/source-map-resolve#deprecated
npm WARN deprecated<EMAIL_ADDRESS>This SVGO version is no longer supported. Upgrade to v2.x.x.

added 1441 packages, and audited 1444 packages in 15s

203 packages are looking for funding
  run `npm fund` for details

6 high severity vulnerabilities

To address all issues (including breaking changes), run:
  npm audit fix --force

Run `npm audit` for details.

C:\repos\cbus-web>npm audit
# npm audit report

nth-check  <2.0.1
Severity: high
Inefficient Regular Expression Complexity in nth-check - https://github.com/advisories/GHSA-rp65-9cf3-cjxr
fix available via `npm audit fix --force`
Will install<EMAIL_ADDRESS>which is a breaking change
node_modules/svgo/node_modules/nth-check
  css-select  <=3.1.0
  Depends on vulnerable versions of nth-check
  node_modules/svgo/node_modules/css-select
    svgo  1.0.0 - 1.3.2
    Depends on vulnerable versions of css-select
    node_modules/svgo
      @svgr/plugin-svgo  <=5.5.0
      Depends on vulnerable versions of svgo
      node_modules/@svgr/plugin-svgo
        @svgr/webpack  4.0.0 - 5.5.0
        Depends on vulnerable versions of @svgr/plugin-svgo
        node_modules/@svgr/webpack
          react-scripts  >=2.1.4
          Depends on vulnerable versions of @svgr/webpack
          node_modules/react-scripts

6 high severity vulnerabilities

To address all issues (including breaking changes), run:
  npm audit fix --force

C:\repos\cbus-web>git show
commit c62d17ea79574ce8e4a8e392c9926325acb86d96 (HEAD -> dev, origin/dev, origin/HEAD)
Merge: aa077f7 a39841e
Author: Amy Bedinghaus<EMAIL_ADDRESS>Date:   Fri Jul 29 15:06:17 2022 -0400

    Merge pull request #8 from FCCColumbus/fix_vulnerabilities

    fix vulnerabilities

Simply running npm audit fix --force will not work.  You will go into an infinite "fix" loop that will continually show vulnerabilities.
My research showed that this is caused by a known bug with nth-check.  The workaround now is to put "nth-check": ">=2.0.1" in the dependencies section of package.json.
Unfortunately this bug has been around for months.  No idea when it will be fixed.....

@readysetagile My bad, I did not independently verify the fix.  Just to clarify, is that one of the roles of the PR reviewer, to pull down the feature branch and manually test before merging?  I know we don't currently have anyone in a QA role.
@koto253 are you still seeing the issue as well?  See John's comment above about nth-check.  We may need to create a new PR to fix this issue.

@amyngb up for discussion, however, my take is that the dev who is introducing the commit should at least check that the problem is solved before committing.  We should establish these team agreements before going much farther.  To your point, since we don't have any dedicated QA, we might want to also introduce a Peer Review with the Code Review.  Netlify automatically creates an environment with the PR which would be nice in this situation.  That's another discussion...
The other unique thing about this PR (not previously mentioned) is that it introduced 2 changes.  This is dangerous, especially in this case because the second change "broke the build".  You can see that with a npm run test that a variable is undefined.

Even though this is a issue/non-issue, we still need to keep on top of it, especially if we run automated tools to do security checks.
What I did was cherry-picked this commit,  used the recommendations here, and got found 0 vulnerabilities.  Let's try this and close this issue.

Looks like the latest build / audit has fixed this.  closing this issue


additional constructs for marking things as independent

currently, in contexts where independence information can be useful (e.g. for doing elbo with non-reparameterizable rvs), our only construct for marking things as independent is map_data. so, for example, in a code snippet like
z_1 = pyro.sample("z1", diagnormal, ng_zeros(1), ng_ones(1))
z_2 = pyro.sample("z2", diagnormal, ng_zeros(1), ng_ones(1))

pyro will impute a (possible) dependence of z2 on z1.  it would be great to have a clean way to mark z1 and z2 as independent. one way would be for the user to do so very explicitly:
pyro.mark_ind(target_rv="z2", ["z1"])

this, however, is potentially very tedious and error-prone. another option is to generalize map_data.
so, for example, we might do something like
sample_z_1 = lambda: pyro.sample("z1", diagnormal, ng_zeros(1), ng_ones(1))
sample_z_2 = lambda: pyro.sample("z2", diagnormal, ng_zeros(1), ng_ones(1))
pyro.do_independent(sample_z_1, sample_z_2)

map_data could then be a special case of this construct. just like for map_data it would be relatively straightforward to consume the information in pyro.do_independent and make use of the encoded independencies. there may also be other pythonic ways to introduce a similar construct: decorators, or with statements, or something else.
down the line we may still want fancier code that automatically generates fine-grained DAGs from the pytorch computational flow. but something like pyro.do_independent might be a good idiom for the mid-term (and would probably remain useful in the long-term, since fine-grained DAG imputation may not always be correct/complete).

i'm going to close this because we seem to be pretty happy with the functionality we have from irange and iarange. will reopen if necessary


feature add @layer support to all components

[x] aria-only
[x] aspect-ratio
[x] auto-grid
[x] avatar
[x] badge
[ ] base
[ ] breadcrumbs
[x] button
[ ] card
[ ] code
[x] container
[ ] control
[ ] details
[ ] dialog
[ ] form
[ ] gradient
[ ] hashlink
[ ] input-group
[ ] list
[ ] menu
[ ] pagination
[ ] print
[ ] progress
[ ] range
[ ] scroll-slider
[ ] scrollbar
[ ] section
[ ] stretched-link
[ ] table
[ ] transform
[ ] transition

Skipping base for v1, will be added in v2 instead


Improve script

Purpose

$subject

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

Comparison is base (71e6477) 25.56% compared to head (1772f00) 80.10%.
Report is 63 commits behind head on main.

Additional details and impacted files
@@             Coverage Diff             @@
##             main    #1762       +/-   ##
===========================================
+ Coverage   25.56%   80.10%   +54.54%
===========================================
  Files         262        9      -253
  Lines       30326      548    -29778
  Branches     5122      246     -4876
===========================================
- Hits         7752      439     -7313
+ Misses      22312      109    -22203
+ Partials      262        0      -262

Flag
Coverage Δ

adapter
?

common-controller
?

config-deployer-service
?

idp-domain-service
80.10% <ø> (ø)

router
?

Flags with carried forward coverage won't be shown. Click here to find out more.
see 253 files with indirect coverage changes

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


operator ipfs-operator (0.0.2)

Signed-off-by: Oleg<EMAIL_ADDRESS>Thanks for submitting your Operator. Please check the below list before you create your Pull Request.
New Submissions

[x] Are you familiar with our contribution guidelines?
[x] Have you packaged and deployed your Operator for Operator Framework?

[x] Have you considered whether you want to use semantic versioning order?
[x] Is your submission signed?
[x] Is operator icon set?

Updates to existing Operators

[x] Did you create a ci.yaml file according to the update instructions?
[x] Is your new CSV pointing to the previous version with the replaces property if you chose replaces-mode via the updateGraph property in ci.yaml?
[x] Is your new CSV referenced in the appropriate channel defined in the package.yaml or annotations.yaml ?
[x] Have you tested an update to your Operator when deployed via OLM?
[x] Is your submission signed?

Your submission should not

[x] Modify more than one operator
[x] Modify an Operator you don't own
[x] Rename an operator - please remove and add with a different name instead
[x] Modify any files outside the above mentioned folders
[x] Contain more than one commit. Please squash your commits.

Operator Description must contain (in order)

[x] Description of the managed Application and where to find more information
[x] Features and capabilities of your Operator and how to use it
[x] Any manual steps about potential pre-requisites for using your Operator

Operator Metadata should contain

[x] Human readable name and 1-liner description about your Operator
[x] Valid category name1
[x] One of the pre-defined capability levels2
[x] Links to the maintainer, source code and documentation
[x] Example templates for all Custom Resource Definitions intended to be used
[ ] A quadratic logo

Remember that you can preview your CSV here.
--
1 If you feel your Operator does not fit any of the pre-defined categories, file an issue against this repo and explain your need
2 For more information see here

Creating this PR since the bot auto-merged my previous PR before I was completed with it. This is the completed version and is fine to merge.

/merge possible

/merge possible


Support for Cloud SQL databases in database viewer

Just a feature request.
Thanks to cloud-sql-jdbc-socket-factory, it's very easy to connect to Cloud SQL from any Java application, including IntelliJ. I currently use it effectively by manually setting up a data source driver which is just the normal mysql-connector-j, with the socket factory jars on the classpath as in the below screenshot. I suspect it would be quite easy to implement this straight into the cloud tools plugin so users don't have to manually set up this driver. Ideally, it would list Cloud SQL databases and when a user selects one, the data source gets configured, along with the socket factory. It'd be extremely useful for users IMO.

thanks @anuraaga
I agree that this would be useful. I'll keep this open to track and consider with our other features in the pipeline.
Thanks for the suggestion.


sendMail doc

Add a doc to the Reference section that goes more in-depths on sendMail:

buildSendMail options

defaultFrom
configPath
transport

configuring your transport

recommended email service providers
using env variables for secrets

sendMail options

component
html override
REST api
list

@psugihara close?


Proper tagging for versions

This will make package maintaining for distro maintainers easier (or just third-party packagers).

Done. Added tags for v1.0, v1.1, and v1.2. I'll follow the same convention for the cuts used for future public builds.


multiple select placeholder late bind fix

before fix

after fix

Hi,
Thanks for submitting this PR could you clean up the dist folder?
Thanks.

dist folder cleaned.

Can you revert your past commit? Please revert back the dist folder before the changes, when releasing a new version it will be updated.
Sorry for the extra work maybe is was not clear enough.

clean and completed.

Hi @SarperMUTLUBAY  could you merge the master in your branch and see if the issue is fixed?
Thanks

hi @Jefiozie my repository now synced origin repository and build succedded.

Thanks, had a look again on your change. The only thing you changed is the css off the searchInput"right? Is this making the binding do strange stuff?

@Jefiozie yes, it causes the search input to load late bindings.

@SarperMUTLUBAY can you share a plunker with a non working example? So I can have a look and see the problem and the fix you applied?


Update keyboard shortcuts to meet new Style guidelines

… keys

Why:
Closes #13878

What's being changed:

Check off the following:

[ ] I have reviewed my changes in staging (look for "Automatically generated comment" and click Modified to view your latest changes).
[x] For content changes, I have completed the self-review checklist.

Writer impact (This section is for GitHub staff members only):

[ ] This pull request impacts the contribution experience

[ ] I have added the 'writer impact' label
[ ] I have added a description and/or a video demo of the changes below (e.g. a "before and after video")

@AnilSeervi
Thanks so much for opening a PR! I'll get this triaged for review :zap:


Console not useful to diagnose

The start.ps1, since it uses the default Select-Object functionality, does not show the entire output because it defaults to a Format-List with limited column widths. Either use an explicit Format-Table with -Wrap or use Format-List, something by which we can see the entire Message value.
transactional-database_1  | TimeGenerated           EntryType Message
transactional-database_1  | -------------           --------- -------
transactional-database_1  | 10/8/2018 7:58:34 PM FailureAudit Login failed for user 'sa'. Reason: Failed...
transactional-database_1  | 10/8/2018 7:58:34 PM FailureAudit Login failed for user 'sa'. Reason: Failed...
transactional-database_1  | 10/8/2018 7:58:34 PM FailureAudit Login failed for user 'sa'. Reason: Failed...
transactional-database_1  | 10/8/2018 7:58:34 PM FailureAudit Login failed for user 'sa'. Reason: Failed...

Yes, I can reproduce this issue.
Thanks for sharing the solution with us.


add new methods

Adds NLsolve andersson and newton raphson to the nonlinear benchmarks.
Adds the Sundials KINsolve.
Also make the printouts prettier.

Once merged I think we got all the solvers. Then I will go through the figures to see if I can make them a bit prettier (mainly move the legend so that it doesn't cover any results)

[Warn] Solver Newton Trust Region returned retcode MaxIters.
[Warn] Solver Levenberg-Marquardt returned retcode MaxIters.
Error: BoundsError: attempt to access 1×7 Matrix{Int64} at index [[1, 4, 5,
 6, 7, 8, 9]]

seems like the lengths are being measured oddly?

yeah, checking now

It might be nice to add to the bottom a summary of the failures as a general robustness check.

Sounds good, can add something like that in next PR when I fix up the plots a bit


Add CRD for Tenants

This fixes #491
Changes:

Add new CRD to manage tenants in opensearch
Added code for the controller to watch and reconcile the CRD
Added tests for the controller code
Doc changes

Also, is this feature is supporting all OpenSearch versions ? it will get hurt in case of changing tenants configurations in future OS versions ?

Yes, it supports all the versions till now. The API was based on what the official OpenSearch API provides.
https://opensearch.org/docs/latest/security/access-control/api/#tenants

@idanl21 Are you fine with merging this?

HEy @swoehrl-mw
Sorry for the delay, yeah looks good to me
im merging it


The source code of the website

Heya!
This is the current source code for the website.
This currently contains: the page that is currently on the domain, the home page, the compatibility page (still WIP), an update script for the database in rust (for the comp page), a php search script (also for the comp page), and the mdBook (for the wiki).
What do i still need to do? Finish the compatibility page and create the download page.
Also, a lot of the paths are incorrect and will be fixed once i am certain where we are gonna put the site (that seems to be github pages now?).

@ultimaweapon ^

Oh also, gonna need perms to point the Pages to the obliteration.net url.

Thanks for the PR. I might take a couple of days to review this due to my full time job. I'll try to finish the review as fast as possible.

@ultimaweapon Also, just wanna say... Sorry.
I think I was mainly worried that we'd have to completely redo the website to make it work with Github Pages but... Well, let's just say that slluxx, the person who stumbled upon our argument... Actually helped describe how we could make it work with Github Actions.

Yeah still gotta add csp for xss, but because its still in development i haven't done that yet. I don't think a js framework is gonna be needed, i can just add a csp to the html.


Flutter - how to send/cancel follow request & how to accept/decline that follow request (Firestore)?

Hello! I'm using Flutter and Firestore, and I want to allow userA to send/cancel a follow request to userB, and enable userB to accept/decline that follow request. How can I do that? Thanks a lot!

For questions, try one of the other resources at flutter.dev/community. The issue tracker is for bug reports and feature requests.


WIP Clean up defaults and move sp variables

The variables for federation should not have example strings and
should have useful default values.
The group, role, mapping, and protocol, federation variables will be moved
into the sp section since they are considered to be variables intended for
service providers.

Can one of the admins verify this patch?

"ok to test" to accept this pull request for testing
"test this please" for a one time test run
"add to whitelist" to add the author to the whitelist

ok to test


support ariadne recommendations

adapt the code to the new LwJson format which now supports Ariadne recommendations
Tested on https://github.com/lacework-dev/code-analysis-test-repo/pull/307

Could you please perhaps address these minor cosmetic suggestions? It would be nice to keep the same terms as used in lwjson.go, as much as possible. Thanks!

Thanks for the carefully review, I have addressed the comments and ensured the test passes again!


L5 Support?

Hello, does it support L5?

not currently

We just launched our L4 app and I'm swamped, so can't port now. We use this package in our app and it is working great. Someone is welcome to port L5, in the mean time.


foundryup fails because of testdata/lib/forge-std

Component
Foundryup
Have you ensured that all of these are up to date?

[ ] Foundry
[X] Foundryup

What version of Foundry are you on?
No response
What command(s) is the bug in?
foundryup -C a71e084368822d3a658731d4e5e853213767ec91
Operating System
Linux
Describe the bug
This commit: https://github.com/foundry-rs/foundry/commit/12ad1c1ffab410fce96d577270cbb167f72fdb6e added a submodule that doesn't go anywhere, now git submodule update --init --recursive fails, and specifically fails when running foundryup with a previous commit, since it needs to use git.
Here is the error I get:
fatal: No url found for submodule path 'testdata/lib/forge-std' in .gitmodules
foundryup: command failed: git submodule update --init --recursive

As a suggestion, would it be possible to some kind of limited CI test that foundryup actually works so its functionality doesn't regress in the future?

oh my bad, overlooked that.
the submodule should be removed. nice catch


webpack-hot-middleware run error under https

Our dev environment had upgraded from HTTP to https, but  when I use the config of ?path=http//localhost:XXXX under the entry in webpack.config.js ,
webpack.config.js
'index': [
    'webpack-hot-middleware/client?path=http//localhost:' + siteConfig.port + '/__webpack_hmr',
    './js/index'
  ],

There are some  mixed content error thrown :
Mixed Content: The page at 'https://corp.dinghuo123.com/index.html#/order/indent?_k=i76wt3' was loaded over HTTPS, but requested an insecure EventSource endpoint 'http://localhost:9898/__webpack_hmr'. This request has been blocked; the content must be served over HTTPS.

so ,I change the config of HTTP to https like this：
webpack.config.js
'index': [
    'webpack-hot-middleware/client?path=https//localhost:' + siteConfig.port + '/__webpack_hmr',
    './js/index'
  ],

But another error been thrown.
GET https://localhost:9898/__webpack_hmr net::ERR_CONNECTION_CLOSED

Can anyone have some prompt?

I am running into the same problem. I would like to be able to use HTTPS for development but it is giving me the same error.
https://<IP_ADDRESS>/__webpack_hmr net::ERR_CONNECTION_REFUSED

@andrewgbliss is the server running on port 443? If not you'll need the port number in there

@glenjamin I have my node process running on 3000 and using nginx for a proxy running on port 80 for http and 443 for https.
I have noticed though that if I put:
webpack-hot-middleware/client?noInfo=false&path=http://<IP_ADDRESS>:3000/__webpack_hmr
And I go straight to port 3000 it works a lot faster than going through nginx. But I am not sure how to get it working with https

Ooooh, I just realised - <IP_ADDRESS> is invalid for a request address, it's only a valid value for listening addresses.
Use <IP_ADDRESS> or the hostname in the client config instead.

@glenjamin It worked. Thank you. I changed it to:
webpack-hot-middleware/client?noInfo=false&path=http://<IP_ADDRESS>:3000/__webpack_hmr
And I was able to use https with it. I am not sure about the OP though. You shouldn't have to change it to https right?

You shouldn't have to, but it should work with either.

Hi,
I.m also facing the same problem. I want my local to render in browser using https. I have updated my changes as discussed in the above, but still i'm facing the issue.

But when i use webpack-dev-server if i add "webpack-dev-server -d --hot --https  --port 443" my application is rendering in https.
Can anyone help how to work on webpack-hot-middleware using https.

Hello, same here, does anyone resolved it?


Add release notes for 6_1_0 Major update

Build have been started:
https://github.com/nova-wallet/nova-wallet-android-releases/actions/runs/4751509841


Can we run app and server component separately!!

Dear Team,
Can i run app and server component separately, since i wanted server component to be deployed in load balance using HA Proxy and run app component using AWS cloud-front.
Please help us in steps to install server component only in load balance
Thanks

It is related to that: https://github.com/edumeet/edumeet/issues/677  ?
Or do you want to separate media-nodes from signalling? This is not possible yet - have a look at feathttps://github.com/edumeet/edumeet/tree/feat-media-node which should do this if finished

Got it from #683
Thanks
Naresh


Integration with sklearn

Hi, are you thinking of updating this classifier to integrate it with sklearn ?

Yes! In TODO.md -> TODO Extras, I listed some actions to have a chance to do that. Certainly, will start in contrib mode.
The Random Forest method and variations in Scikit-Learn is very well designed. There are a well structured chain of classes, turning able any custom variant preserving the framework standards.
A possible strategy is:

Develop a version based on the Scikit-Learn basic classis, full compatible with the framework. Keep a standalone Python package.
Publish a article about the method. (important to have some confidence from other developers)
Propose for enter the contrib.
Just wait if the method will be really used.

Sure, I have not so high expectations, the idea is to improve my dev skills. My method works very well with real problems, but I'm not thinking that method will be famous enough to be accepted to Scikit-Learn hall of the Random Forest models.


strings: EqualFold doc could be clearer

The doc for EqualFold says:

EqualFold reports whether s and t, interpreted as UTF-8 strings, are equal under Unicode case-folding.

I have been using Go for over five years now and had no idea what "Unicode case-folding" was until about three minutes ago. Previously I had implemented this by calling strings.ToLower on each side, which is slow and unnecessary. More commonly I believe the EqualFold functionality is known as "case insensitive matching." Users who are searching the strings documentation for the phrase "case insensitive" will find nothing, when they should be finding this function.
Scanning Github this seems like a common mistake:
https://github.com/sachin-varade/network/blob/5d4ab4a3757603b8c0ba9a9df7bc9e0ff92ad102/app/utils/setup/chaincode/processors/read_ledger.go#L172
https://github.com/projectriri/bot-gateway/blob/d4402bd4ac0d4478bd86e585ca83e9d3fc1c140e/converters/cqhttp-ubm-conv/cqhttp-ubm-conv.go#L79
Several Go vetters/linters have checks for this construction that suggest using EqualFold instead:
https://github.com/dominikh/go-tools/blob/1da3061645b400d55be4855f104d8a68ca0a61e5/staticcheck/testdata/src/CheckToLowerToUpperComparison/CheckToLowerToUpperComparison.go
StackOverflow answers suggesting the use of EqualFold have 35,000 views and 10,000 views, respectively.
https://stackoverflow.com/q/24836044/329700
https://stackoverflow.com/q/30196780/329700

I agree that this doc can be made clearer. How about adding a clause to say that it basically does a more general form of case-insensitive matching? Something like:

EqualFold reports whether s and t, interpreted as UTF-8 strings, are equal under Unicode case-folding, a generalization of case-insensitivity.

I opened PR for this, fixing also docs for EqualFold() in bytes package.
Formally, better word here seems to be "caseless" (as the section 13.3 of Unicode Standard) but I picked up more conventional "case insensitive"
This is my first PR


Add note for compatibility with gulp 3.x

Reference to comment in #1445 - adding note to let folks know this only works with the latest published gulp-cli version

Thanks!


cmd/compile: erroneously allows promoted-method calls on function-scoped declared pointer types

cmd/compile erroneously accepts the file below. go/types and gccgo correctly reject it.
package p

type T int

func (T) M() {}

func f() {
	type P *struct{ T }
	var p P
	p.M()
}

This is fixed on dev.regabi.

This is fixed on dev.regabi.


[feature] Add support for pipx

Could you please add support for pipx as additional package manager?
pipx stores its virtual environments at  ~/.local/share/pipx/venvs/PACKAGE by default (see https://github.com/pypa/pipx/blob/ac647404902c46019c4cf2da46dc225c5404d986/docs/how-pipx-works.md), as far as I know on each platform.

This should be very simple to do in the new version of the plugin I'm working on in the regexp branch. You can also add it yourself there if you write a fd command that will pick them up. It's still under heavy development but just wanted to let you know if you want to try it out.

Pipx support has been added now to the regexp version of the plugin, and its ready for general use now. Try it out. :)