Returning to paginated page after save

I'm working with version 3.6, and my clients are trying to go through a paginated list, edit one item, and when they click Save, they are always returned to the first page of the paginated list, as opposed to the one which they are on.
Is there any way in which we can remember the paginated page they were on? Thanks,

not 100% what you are looking for but if you set
'persistent_table' => true,
in config\backpack\crud.php, whenever the user tries to see a list-page, backpack loads both the previous pagination and filtration (that last one can be sometimes confusing for clients)

Hi Tim,
Is this only on the latest version? I'm running a client project with CRUD
3.4
I can see the code in more recent versions, which is great news it has been
covered. Having used Backpack for the last two years on numerous projects,
its great to keep finding new items.
Steve
On Tue, 4 Jun 2019 at 14:01, Tim Bertens<EMAIL_ADDRESS>wrote:

not 100% what you are looking for but if you set
'persistent_table' => true,
in config\backpack\crud.php, whenever the user tries to see a list-page,
backpack loads both the previous pagination and filtration (that last one
can be sometimes confusing for clients)
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/Laravel-Backpack/CRUD/issues/1900?email_source=notifications&email_token=AAKQVCRNQXF4JP5XWEIZFADPYZRUDA5CNFSM4HS2P2G2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODW4PTII#issuecomment-498661793,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAKQVCUNGMYB27MQB3MTYD3PYZRUDANCNFSM4HS2P2GQ
.

--
Steve Cross
Director
UK HQ. 01962 670 190 | Mobile. 07876 668 747 | From Germany.<PHONE_NUMBER>7
Email<EMAIL_ADDRESS>| Web. www.sprechen.co.uk / www.geekabit.co.uk
Legal Disclaimer - This message and any attachments should only be read
by those persons to whom it is addressed and be used by them for its
intended purpose. Sprechen Ltd cannot accept liability for statements made
which are clearly the sender's own and not made on behalf of Sprechen Ltd.
Replies to this email address may be subject to interception or monitoring
for operational reasons or for lawful business purposes.

It has been added since 3.5, see https://github.com/Laravel-Backpack/CRUD/blob/master/CHANGELOG.md#350---2018-09-22

Hello @stevecrossuk , i hope @timbertens solution worked for you.
As times goes by we need to clean up issues tracker, and this is more like a general question than a bug report.
If you think i'm wrong please feel free to reply.
BR,
Pedro

This was the perfect solution. Thanks guys. Much appreciated
Steve Cross
CEO
UK HQ. 01962 670 190 | Mobile. 07876 668 747 | From Germany.<PHONE_NUMBER>7
Email<EMAIL_ADDRESS>| Web. www.sprechen.co.uk
Legal Disclaimer - This message and any attachments should only be read by those persons to whom it is addressed and be used by them for its intended purpose. Sprechen Ltd cannot accept liability for statements made which are clearly the sender's own and not made on behalf of Sprechen Ltd. Replies to this email address may be subject to interception or monitoring for operational reasons or for lawful business purposes.

On 24 Jun 2019, at 18:15, Pedro Martins<EMAIL_ADDRESS>wrote:
Hello @stevecrossuk , i hope @timbertens solution worked for you.
As times goes by we need to clean up issues tracker, and this is more like a general question than a bug report.
If you think i'm wrong please feel free to reply.
BR,
Pedro
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.


Running SCENARIOs: Omit "SCENARIO" in selection

Say I have some SCENARIO defined like so:
SCENARIO("foo", "[foo][bar][baz]") {
    // ...
}

I argue that the intuitive interface for selecting to run only the tests for this specific scenario is: ./test_executable foo.
However, given that the SCENARIO binding prepends its descriptor with Scenario: , we're required to instead select for the specific scenario like so: ./test_executable "Scenario: foo", which seems less than ideal.

Thanks. Was wondering why my test scenario wouldn't run. Explains it.
Similar issue with the GIVEN, WHEN, THEN macros.


Tabs.Recyclerlistview

Feature request
It would be nice to have a Recyclerlistview component to optimise tabs.
https://github.com/Flipkart/recyclerlistview

With the upcoming migration to Fabric in the RN world, I think recyclerlistview might soon be deprecated (or at least will need a full rewrite)
That being said, it might be possible to just create your own wrapper for it using https://github.com/PedroBern/react-native-collapsible-tab-view/blob/main/src/FlatList.tsx as a guideline.


Azure ducumentation

Azure documentation issue guidance
Thanks for opening an issue in the Azure technical documentation repository.
We use GitHub issues as the primary channel for customer and community feedback about the Azure documentation.
Creating an issue
We prefer that you create documentation feedback issues using the Feedback link on the published article - the feedback control on the doc page creates an issue that contains all the article details so you can focus on the feedback part.
You can also create a feedback issue here in the repo. If you do this, please make sure your issue lists:

[ ] The relevant Azure service or technology.
[ ] A link to the published documentation article that you have feedback about.
[ ] Clear, specific feedback that the author can act on.

Pull requests and article contributions
If you know the change that is needed in an article, we encourage you to submit the changes directly using a pull request. If the change is large, or if you want to contribute an entire article, follow these guidelines:

[ ] Don't surprise us with a big pull request or a pull request with a new article! Submit an issue that describes the details of the proposed large change or new article.
[ ] Include the service or technology area.

We'll route the issue to the appropriate content team for review and discussion.
Tech support and product feedback
If you would like to contact Microsoft about other things, such as product feedback or tech support, please review these guidelines:

If you need technical support using Azure, the paid and free support options are described here: https://azure.microsoft.com/support/options/.

Each article in the Azure technical documentation contains a product feedback button - it's best to submit product feedback directly from a relevant article. Otherwise, you can submit product feedback for most Azure products in the following product feedback forum: https://feedback.azure.com/forums/34192--general-feedback.

@knbz Thanks for posting here.
It looks like you have posted this comment for testing.
please let me know if you are looking for other information.

@knbz Did you got a chance to look at the above comment

@knbz Is there any update

I will close this out for now. If you need additional help please let me know and we can reopen and continue.


JAMstack : A Complete Beginner's Guide

This post is a great tutorial for beginner's looking to understand what Jamstack is. It covers the history and foundations of JAMstack and explains the architecture. It includes a comparison of the traditional workflow vs Jamstack workflow and highlights the advantages of using Jamstack for developrs. It also provides a step-by-step guide on how to build a website using JAMstack using a real-time example for readers to use as a reference.
https://buttercms.com/blog/what-is-jamstack

Awesome, thanks for that!

@pineapple-content thank you, added to the site.


Fix ( #9002 ) UI - updated loading experience for table / page seamlessly

Closes #9002
Describe your changes :

I worked on issue #9002

Type of change :

[x] Improvement

Frontend Preview (Screenshots) :

Checklist:

[x] I have read the CONTRIBUTING document.
[x] I have commented on my code, particularly in hard-to-understand areas.
[x] I have added tests that prove my fix is effective or that my feature works.
[x] All new and existing tests passed.

Reviewers
@open-metadata/ui

Closing this as lost track of it.


Can't build project when source generator is referenced on MacOS

I'm trying to use the source generators in my project, and referencing from nuget is working on Windows, but on MacOS the build fails due to a missing native library reference.
Build log: https://github.com/davidwengier/Trains.NET/pull/158/checks?check_run_id=1304612100#step:4:814
Error:

CSC : error SI0000: Error in the SvgSourceGenerator generator: 'System.TypeInitializationException: The type initializer for 'Svg.Skia.SKSvgSettings' threw an exception. ---> System.TypeInitializationException: The type initializer for 'SkiaSharp.SKImageInfo' threw an exception. ---> System.DllNotFoundException: libSkiaSharp assembly: type: member:(null) [/Users/runner/work/Trains.NET/Trains.NET/src/Trains.NET.Rendering.Skia/Trains.NET.Rendering.Skia.csproj]

This also fails on my MacBook Pro, so it's not just GitHub Actions. I'm guessing there is some way to specify in the nuget package to copy the native dependencies into the source generator package, but I don't know what it is :)

Does this compile https://github.com/wieslawsoltes/SourceGenerators/tree/master/samples/Svg.Skia.SourceGenerator.NuGet

No, I get the same error compiling that project locally. I've attached a binlog in case it helps:
msbuild.binlog.zip

I am integrating this repo into https://github.com/wieslawsoltes/Svg.Skia and moving to net5.0 target.


missing f in the beginning of the line making preprocess_images impossible

https://github.com/facebookresearch/ContactPose/blob/7ff94879d8a570c2bbf8e990ac4b0576b0aa2bfb/scripts/preprocess_images.py#L25

Thank you for reporting this, @bastien-datalchemy!


[BUG] spiral_sweep ignores turns for left-handed spirals

Describe the bug
Some time in the past 4 months spiral_sweep() stopped producing left-hand spirals with a negative turns argument.
skin.scad's spiral_sweep() details this in its documentation as how to create a left-handed spiral:
//   If turns is positive the path will be right-handed;  if turns is negative the path will be left-handed.
Code To Reproduce Bug
// pulling directly from spiral_sweep's Example 1:
include <BOSL2/std.scad>
poly = [[-10,0], [-3,-5], [3,-5], [10,0], [0,-30]];
xdistribute(spacing=50) {
    spiral_sweep(poly, h=200, r=50, turns=3,  $fn=36);
    spiral_sweep(poly, h=200, r=50, turns=-3, $fn=36);
}

...which yields the following model:

Expected behavior
In the example above, I'd expect to have two spirals moving in opposite directions.
Additional context

OpenSCAD Version: 2021.01 on Windows 10 Home (22H2) 19045.2546
Other libraries used: BOSL2 is from whatever BOSL2-master.zip represented on or about 2023/01/27

Hmmm.  Weird.  This seems to have been the interaction of a bug where a negative height caused the spiral direction to flip, which caused me to "fix" spiral_sweep because I didn't know the negative heighit was happening.  So I think I have a fix for this.

Agreed, most recent BOSL2-master.zip repairs this. Thanks!


Add function to create a new titled section

Example included.

Great stuff, Jonas!  Could you perhaps also add a unit test (see tests/) for this?

I have been using:
char tmp[large_enough];
sprintf(tmp, "section-name \"%s\" {\n}", title);
cfg_parse_buf(cfg, tmp);
Which is kind of ugly...

Hmm, I think attempts to add a pre-existing section should fail.
Maybe add a flags argument to get selective behavior?

@peda-r Yeah this is cleaner.
Hmm, you're right and it also touches upon a related problem of mine. A global CFGF_OVERWRITE flag could control overwriting anything, good idea!

I was thinking a flags argument to the new function, but I guess I don't care deeply about where the flags are specified...

I just zoomed out a bit: a user that wants to add a section likely also want to be able to add other things as well.

Unit test added.
I agree that the default for adding a pre-existing section should fail. But should it be a flag or not to override this behaviour?

@jonasj76 Thanks! :)
Yeah I think we should have a global flag, like this:
if (cfg->flags & CFGF_IGNORE_UNKNOWN)
    clear_current_opt()
if (set_value() fails)
     errno = EEXIST;
     return NULL;

or something, but I guess it could also be an option flag. I don't have a strong opinion on either one.  With a global flag we could let it cascade down on all options on cfg_init() so the code only needs to check opt->flags ...

Added commit to fail when adding a pre-existing section.

Awesome, thanks!
Like we discussed AFK today, adding a global and/or per-setting CFGF_OVERWRITE can be added later.


Add A* pathfinding algorithm

Summary
I've written the current A* to return the full path from start to finish, unlike the Dijkstra that simply computes all costs, stopping if the goal is found. Additionally, I could add in the computed cost of the path.
I've added a test that validates a basic usage, although there should be a proof that the heuristic drives the pathfinding.
Performance-wise, the tracking of previous nodes to later rebuild the path from start to finish adds on the Dijkstra's performance cost, otherwise it's roughly equivalent.
Sidenotes
Some work could be done to allow more flexibility in terms of data-structures used by the algorithm, as it currently requires that node IDs be Eq + Hash when we could have another version only requiring Ord which would use trees instead of hashmaps.
Questions

Should the path returned be the list of node IDs or the actual edge IDs?
Should there be bench tests on the A* vs the Dijkstra when H(x) = 0 to measure the cost of tracking the path?
Should the pathfinding algorithms be reworked to share some common "flexible" interface?

(fixes #138)

This looks really good. I've worked down PR queues in other repos but I'm sorry I haven't had much progress in petgraph. It's going to happen, but a bit late.

This is where I think of something like the inverse of an iterator (Think instead of Iterator::next we have a generalization of Vec::push, something that eats elements) -- so that the user could submit both a vector for path and for edges, if they wanted to save both those.

Thanks for the update!
Concerning the generalization of Vec::push, since the path is reconstructed from finish to start, I need to reconstruct the path otherwise the user would have to handle each path component in reverse order.
Maybe Path<G> can be structured with a few iterators on things like: node ids, edge ids? I feel like there should be some kind of all-purpose Path type that would be returned by the various pathfinding functions.

Ah the path idea, do you mean we use a bit more opaque type?
Say if we store the node ids, we can take the path and the graph and make an iterator that gives the edge ids and so on?

(replying to your comment about the Path type)
Precisely. Only problem with that is that although both G::NodeId and G::EdgeId are Copy, the opaque type would have to borrow a G.

Can you elaborate on that problem?
I guess parallel edges existing means that we can't give an unambiguous path in terms of edges indices, too. Unless we save them, which sounds simple to do.

NVM, I forgot about the IntoEdges::edges() method.
Would something like this work?
impl<G:GraphBase> Path<G> {
  fn node_ids(&self) -> impl Iterator<Item=G::NodeId> {
    unimplemented!();
  }

  fn edge_ids(&self) -> impl Iterator<Item=&[G::EdgeId]> {
    unimplemented!();
  }
}

I'm also thinking that yielding &[G::EdgeId] will be awkward to use, as people generally expect only a unique path from source to target. Not to mention that 90% of the time people don't use parallel edges.
Another option instead of yielding a &[G::EdgeId] is to yield an enum NodeConnection (apologies for the awful name), which would look something like this:
enum NodeConnection<G: GraphBase> {
  OneEdge(G::EdgeId),
  MultipleEdges(Vec<G::EdgeId>),
}

impl<G: GraphBase> NodeConnection<G> {
  fn as_one_edge(&self) -> Option<G::EdgeId> {
    if let NodeConnection::OneEdge(edge_id) = *self { Some(edge_id) } else { None }
  }

  fn as_multiple_edges(&self) -> Option<&[G::EdgeId]> {
    if let NodeConnection::MultipleEdge(ref edge_ids) = *self { Some(edge_ids) } else { None }
  }
}

One important note: when re-reading my implementation, I noticed that the heuristic's signature is FnMut(G::NodeId) -> K. Shouldn't it take a G::EdgeRef, as it's called edge_cost?
In that case, we should only have to handle parallel edges if two edges have the same cost, and are therefore both visited during the A*.
Here's the problem with that: the Visitable trait only defines a Map that takes G::NodeId and not G::EdgeId. Therefore there's no way we'll encounter parallel edges if we use Visitable::Map.

I don't think parallel edges should be a problem for the algorithm, only a problem if one wants to use nodes to identify the edge ids that were in the path.
Isn't the heuristic function standard? Like wikipedia says, it should be a function that takes a node x and returns an estimate of the distance from x to the goal.
Btw, I saw a different Rust astar algo (would link if I had the URL handy) that was using a callback to determine if a given node was the goal, instead of taking a goal node. It is more flexible that way..

The usual rule applies: Don't overengineer it :smile:

Ok I just re-checked the wikipedia article and re-read some things, you're 100% right about H taking a node.
Using a callback is much more flexible. I've added one in the latest version. I'm still having trouble with handling parallel edges and like you said, things are getting a little over-engineered now 😅.
Would you be ok with the current version, simply returning a list of node ids?

This looks good. I want to include this in the 0.4.x release series. I might put out a point release before this merges, though.

You might have seen my other recent fixups, seeing that I prioritize non-breaking changes. New algo is good..

I think this should return the path cost as well. Either the whole score map, or just the cost for the found path.
Sorry for not looking at this with my full attention. Low complexity is good, but we need to align it a bit with dijkstra.
Also for inspiration we can alsways look in boost::graph: http://www.boost.org/doc/libs/1_46_0/libs/graph/doc/astar_search.html  Looking there it's very clear that petgraph is not boost::graph, in terms of type parameters.

Sorry for not looking at this with my full attention.

No problem, I was actually glad this was getting some attention. 😄
I think returning the predecessor map is a bit heavy API-wise, the user is likely uninterested in the algorithm's intermediate steps and more interested in the final result (eg. the path cost). Do you think a return type of (Vec<G::NodeId>, K) would do the trick?

Yes. Just an impulse, cost should probably be field 0 in the tuple. I imagine we can add a more configurable astar later.

Thanks!

This is alrady implemented in https://docs.rs/petgraph/0.4.12/petgraph/algo/fn.astar.html, could anyone sumup what is the relation to petgraph crate?


Test

What this PR does / why we need it:
Its tests something
Which issue this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged): fixes #
Special notes for your reviewer:
Release note:

/test e2e

/ok-to-test

/test e2e


Interface with Jinx or "glediator"

Could be done by writing an application that reads TMP2 data from a file. Similar to playing a file from the SD card, like the LED controllers.

I could also implement the Tmp2.net protocol to receive data from the local network!


Bayou: Bulk transfer tool for both FT and NFT #onFlow

Grant category
Please select one:

Open source maintenance

Description
Problem statement
With the blooming of DAOs, bulk transfer is an increasingly important feature for community operation in Web3. It would be annoying and inefficient for an operator to send tokens to the recipients one by one.
Currently, we have built a tool named bayou for the bulk transfer of Fungible tokens, and it works well so far:

Launched for more than 4 months
More than 20 tokens supported
Support the check for accounts with invalid format or invalid account setting.
Support uploading recipients by using CSV

but there is still no universal NFT bulk transfer tool now, and we want to add this to bayou!

Target audience

The community operators / DAO core members #onFlow

Evidence for the need

The lack of NFT bulk transfer tools #onFlow

Proposed solution
We are going to add some features to bayou to support the NFT bulk transfer and improve user experience:

Support transfer to .find and .fn domains
Support Lost&Found and Flowns Inbox to allow the transfer to accounts with invalid settings
Bulk transfer multiple kinds of NFT to one account
Bulk transfer multiple NFTs of one kind to multiple accounts
Advanced mode for users to bulk transfer customized Fungible Tokens (customized tokens should be recorded in the signer's account)
Advanced mode for users to bulk transfer customized NFTs (customized tokens should be recorded in the signer's account)

The NFT bulk transfer feature is not only an input field for users to input tokenIDs, but comes with a much more user friendly click-to-choose UI, like what's on drizzle:

Impact

In what ways does this benefit the broader Flow developer ecosystem?

This tool will make the builders and operators in the ecosystem work in a more efficient manner.

Milestones and funding

Note: You can leave the USD proposal empty / "TBD". Please consider adoption and/or maintenance milestones at the end of your project.

Milestone
Deliverables
Timeline
Risks
USD proposal

1 - Support .find and .fn domain(both display and whitelist)
Function available on website
1 week
May need support from .find and .fn teams
2000

2 - Support Lost&Found and Flowns Inbox to allow the transfer to  accounts with invalid settings
Function available on website
1 week
May need support from flowns and flowty teams
2000

3 - Bulk transfer multiple kinds of NFT to one account
Function available on website
2 weeks

4000

4 - Bulk transfer multiple NFTs of one kind to multiple accounts
Function available on website
2 weeks

4000

5 - Advanced mode for users to bulk transfer customized Fungible Tokens (customized tokens should be recorded in the signer's account)
Function available on website
1 week

2000

6 - Advanced mode for users to bulk transfer customized NFTs  (customized tokens should be recorded in the signer's account)
Function available on website
2 weeks

4000

7 - Maintenance
Fix bugs/ Support / Cloud Service Maintenance
Indefinitely

4000

Team

Name
Role
Bio
Contact

Lanford33
Full-Stack Engineer
...
email<EMAIL_ADDRESS>discord: lanford33#2178

@alxflw Hi, I have split #68 into two applications, this one is for Bayou, and #68 is for Drizzle, thank you!

great, thank you @LanfordCai

Hi @LanfordCai!
On this proposal, could you please include an adoption milestone (similar to your other proposal) and also propose a specific timeframe for how long you intend to support against the Maintenance milestone?  Thanks!

Hi, @chrisackermann !
I have added the adoption milestone and the timeframe.
For the adoption, Bayou send the fund/NFTs directly by using a single Transaction instead of calling a contract, so it's hard to record how many uses now(But as far as I know, people from some teams, including Flow team are using it). If you think it's necessary to record the adoption condition, I will try to change it to a contract, but in this way, other people will easily know the fund is distributed by bulk transfer tool. Or I will add a button, people can click it to sign a message to show "Like" to Bayou, in this way the record might not be that precise.
For the timeframe, in fact, I'll maintain it as long as I can.

Hi @LanfordCai - we've reviewed and just had a few small follow-up questions for you:

Would you be able to share some more thoughts on how developers might use this?
Have you thought about integration with wallets (i.e. a bulk transfer button)?

Hi @LanfordCai, thanks for your patience! I just wanted to let you know that we've accepted your proposal and will be following up directly via email with next steps. Thanks!


[Installation]: Installation with OpenVINO get dependency conflict Error !!!

Your current environment
The output of `python collect_env.py`
Collecting environment information...
The cache for model files in Transformers v4.22.0 has been updated. Migrating your old cache. This is a one-time only operation. You can interrupt this and resume the migration later on by calling `transformers.utils.move_cache()`.
0it [00:00, ?it/s]
WARNING 07-09 11:48:31 _custom_ops.py:14] Failed to import from vllm._C with ImportError('libcuda.so.1: cannot open shared object file: No such file or directory')
PyTorch version: 2.3.0+cu121
Is debug build: False
CUDA used to build PyTorch: 12.1
ROCM used to build PyTorch: N/A

OS: Ubuntu 22.04.4 LTS (x86_64)
GCC version: (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0
Clang version: Could not collect
CMake version: version 3.30.0
Libc version: glibc-2.35

Python version: 3.10.14 (main, May  6 2024, 19:42:50) [GCC 11.2.0] (64-bit runtime)
Python platform: Linux-6.5.0-41-generic-x86_64-with-glibc2.35
Is CUDA available: False
CUDA runtime version: No CUDA
CUDA_MODULE_LOADING set to: N/A
GPU models and configuration: No CUDA
Nvidia driver version: No CUDA
cuDNN version: No CUDA
HIP runtime version: N/A
MIOpen runtime version: N/A
Is XNNPACK available: True

CPU:
架构：                              x86_64
CPU 运行模式：                      32-bit, 64-bit
Address sizes:                      39 bits physical, 48 bits virtual
字节序：                            Little Endian
CPU:                                16
在线 CPU 列表：                     0-15
厂商 ID：                           GenuineIntel
型号名称：                          Intel(R) Core(TM) i5-14400
CPU 系列：                          6
型号：                              191
每个核的线程数：                    2
每个座的核数：                      10
座：                                1
步进：                              2
CPU 最大 MHz：                      4700.0000
CPU 最小 MHz：                      800.0000
BogoMIPS：                          4992.00
标记：                              fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc art arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf tsc_known_freq pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 sdbg fma cx16 xtpr pdcm sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm 3dnowprefetch cpuid_fault epb ssbd ibrs ibpb stibp ibrs_enhanced tpr_shadow flexpriority ept vpid ept_ad fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms invpcid rdseed adx smap clflushopt clwb intel_pt sha_ni xsaveopt xsavec xgetbv1 xsaves split_lock_detect avx_vnni dtherm ida arat pln pts hwp hwp_notify hwp_act_window hwp_epp hwp_pkg_req hfi vnmi umip pku ospke waitpkg gfni vaes vpclmulqdq rdpid movdiri movdir64b fsrm md_clear serialize arch_lbr ibt flush_l1d arch_capabilities
虚拟化：                            VT-x
L1d 缓存：                          416 KiB (10 instances)
L1i 缓存：                          448 KiB (10 instances)
L2 缓存：                           9.5 MiB (7 instances)
L3 缓存：                           20 MiB (1 instance)
NUMA 节点：                         1
NUMA 节点0 CPU：                    0-15
Vulnerability Gather data sampling: Not affected
Vulnerability Itlb multihit:        Not affected
Vulnerability L1tf:                 Not affected
Vulnerability Mds:                  Not affected
Vulnerability Meltdown:             Not affected
Vulnerability Mmio stale data:      Not affected
Vulnerability Retbleed:             Not affected
Vulnerability Spec rstack overflow: Not affected
Vulnerability Spec store bypass:    Mitigation; Speculative Store Bypass disabled via prctl
Vulnerability Spectre v1:           Mitigation; usercopy/swapgs barriers and __user pointer sanitization
Vulnerability Spectre v2:           Mitigation; Enhanced / Automatic IBRS; IBPB conditional; RSB filling; PBRSB-eIBRS SW sequence; BHI BHI_DIS_S
Vulnerability Srbds:                Not affected
Vulnerability Tsx async abort:      Not affected

Versions of relevant libraries:
[pip3] numpy==1.26.4
[pip3] nvidia-nccl-cu12==2.20.5
[pip3] torch==2.3.0
[pip3] torchvision==0.18.0
[pip3] transformers==4.42.3
[pip3] triton==2.3.0
[conda] numpy                     1.26.4                   pypi_0    pypi
[conda] nvidia-nccl-cu12          2.20.5                   pypi_0    pypi
[conda] torch                     2.3.0                    pypi_0    pypi
[conda] torchvision               0.18.0                   pypi_0    pypi
[conda] transformers              4.42.3                   pypi_0    pypi
[conda] triton                    2.3.0                    pypi_0    pypi
ROCM Version: Could not collect
Neuron SDK Version: N/A
vLLM Version: 0.5.1
vLLM Build Flags:
CUDA Archs: Not Set; ROCm: Disabled; Neuron: Disabled
GPU Topology:
Could not collect

How you are installing vllm
ref the openvino install way from https://docs.vllm.ai/en/latest/getting_started/openvino-installation.html

# step1
conda create -n vllm-openvino python=3.10
conda activate vllm-openvino

wget vllm-0.5.1
tar && cd vllm-0.5.1

# step2
pip install --upgrade pip
pip install -r requirements-build.txt --extra-index-url https://download.pytorch.org/whl/cpu

# step3
PIP_PRE=1 PIP_EXTRA_INDEX_URL="https://download.pytorch.org/whl/cpu https://storage.openvinotoolkit.org/simple/wheels/nightly/" VLLM_TARGET_DEVICE=openvino python -m pip install -v .

(vllm-openvino) yongshuai_wang@intsig.com@HHDT2024060052:~/codes/github/vllm-s/vllm-0.5.1$ PIP_PRE=1 PIP_EXTRA_INDEX_URL="https://download.pytorch.org/whl/cpu https://storage.openvinotoolkit.org/simple/wheels/nightly/" VLLM_TARGET_DEVICE=openvino python -m pip install -v .
Using pip 24.1.2 from<EMAIL_ADDRESS>(python 3.10)
Looking in indexes: https://pypi.org/simple, https://download.pytorch.org/whl/cpu, https://storage.openvinotoolkit.org/simple/wheels/nightly/
Processing<EMAIL_ADDRESS>Running command pip subprocess to install build dependencies
Using pip 24.1.2 from<EMAIL_ADDRESS>(python 3.10)
Looking in indexes: https://pypi.org/simple, https://download.pytorch.org/whl/cpu, https://storage.openvinotoolkit.org/simple/wheels/nightly/, https://download.pytorch.org/whl/cpu, https://storage.openvinotoolkit.org/simple/wheels/nightly/
Collecting cmake>=3.21
Obtaining dependency information for cmake>=3.21 from https://files.pythonhosted.org/packages/f9/2e/4f04db5517547aea3cf7dc59c4fef66b2b0e647792babd913b956aa95ceb/cmake-3.30.0-py3-none-manylinux_2_17_x86_64.manylinux2014_x86_64.whl.metadata
Using cached cmake-3.30.0-py3-none-manylinux_2_17_x86_64.manylinux2014_x86_64.whl.metadata (6.1 kB)
Collecting ninja
Obtaining dependency information for ninja from https://files.pythonhosted.org/packages/6d/92/8d7aebd4430ab5ff65df2bfee6d5745f95c004284db2d8ca76dcbfd9de47/ninja-<IP_ADDRESS>-py2.py3-none-manylinux1_x86_64.manylinux_2_5_x86_64.whl.metadata
Using cached ninja-<IP_ADDRESS>-py2.py3-none-manylinux1_x86_64.manylinux_2_5_x86_64.whl.metadata (5.3 kB)
Collecting packaging
Obtaining dependency information for packaging from https://files.pythonhosted.org/packages/08/aa/cc0199a5f0ad350994d660967a8efb233fe0416e4639146c089643407ce6/packaging-24.1-py3-none-any.whl.metadata
Using cached packaging-24.1-py3-none-any.whl.metadata (3.2 kB)
Collecting setuptools>=49.4.0
Obtaining dependency information for setuptools>=49.4.0 from https://files.pythonhosted.org/packages/42/54/2a8ecfcc9a714a6fbf86559a4b0f50b126a4ac4269ea8134f2c75c3e73de/setuptools-70.2.0-py3-none-any.whl.metadata
Using cached setuptools-70.2.0-py3-none-any.whl.metadata (5.8 kB)
Collecting torch==2.3.0
Using cached https://download.pytorch.org/whl/cpu/torch-2.3.0%2Bcpu-cp310-cp310-linux_x86_64.whl (190.4 MB)
Collecting wheel
Obtaining dependency information for wheel from https://files.pythonhosted.org/packages/7d/cd/d7460c9a869b16c3dd4e1e403cce337df165368c71d6af229a74699622ce/wheel-0.43.0-py3-none-any.whl.metadata
Using cached wheel-0.43.0-py3-none-any.whl.metadata (2.2 kB)
Collecting filelock (from torch==2.3.0)
Obtaining dependency information for filelock from https://files.pythonhosted.org/packages/ae/f0/48285f0262fe47103a4a45972ed2f9b93e4c80b8fd609fa98da78b2a5706/filelock-3.15.4-py3-none-any.whl.metadata
Using cached filelock-3.15.4-py3-none-any.whl.metadata (2.9 kB)
Collecting typing-extensions>=4.8.0 (from torch==2.3.0)
Obtaining dependency information for typing-extensions>=4.8.0 from https://files.pythonhosted.org/packages/26/9f/ad63fc0248c5379346306f8668cda6e2e2e9c95e01216d2b8ffd9ff037d0/typing_extensions-4.12.2-py3-none-any.whl.metadata
Using cached typing_extensions-4.12.2-py3-none-any.whl.metadata (3.0 kB)
Collecting sympy (from torch==2.3.0)
Obtaining dependency information for sympy from https://files.pythonhosted.org/packages/62/74/7e6c65ee89ff43942bffffdbb238634f16967bf327aee3c76efcf6e49587/sympy-1.13.0-py3-none-any.whl.metadata
Using cached sympy-1.13.0-py3-none-any.whl.metadata (12 kB)
Collecting networkx (from torch==2.3.0)
Obtaining dependency information for networkx from https://files.pythonhosted.org/packages/38/e9/5f72929373e1a0e8d142a130f3f97e6ff920070f87f91c4e13e40e0fba5a/networkx-3.3-py3-none-any.whl.metadata
Using cached networkx-3.3-py3-none-any.whl.metadata (5.1 kB)
Collecting jinja2 (from torch==2.3.0)
Obtaining dependency information for jinja2 from https://files.pythonhosted.org/packages/31/80/3a54838c3fb461f6fec263ebf3a3a41771bd05190238de3486aae8540c36/jinja2-3.1.4-py3-none-any.whl.metadata
Using cached jinja2-3.1.4-py3-none-any.whl.metadata (2.6 kB)
Collecting fsspec (from torch==2.3.0)
Obtaining dependency information for fsspec from https://files.pythonhosted.org/packages/5e/44/73bea497ac69bafde2ee4269292fa3b41f1198f4bb7bbaaabde30ad29d4a/fsspec-2024.6.1-py3-none-any.whl.metadata
Using cached fsspec-2024.6.1-py3-none-any.whl.metadata (11 kB)
Collecting MarkupSafe>=2.0 (from jinja2->torch==2.3.0)
Using cached https://download.pytorch.org/whl/MarkupSafe-2.1.5-cp310-cp310-manylinux_2_17_x86_64.manylinux2014_x86_64.whl (25 kB)
Collecting mpmath<1.4,>=1.1.0 (from sympy->torch==2.3.0)
Using cached https://download.pytorch.org/whl/mpmath-1.3.0-py3-none-any.whl (536 kB)
Using cached cmake-3.30.0-py3-none-manylinux_2_17_x86_64.manylinux2014_x86_64.whl (26.9 MB)
Using cached ninja-<IP_ADDRESS>-py2.py3-none-manylinux1_x86_64.manylinux_2_5_x86_64.whl (307 kB)
Using cached packaging-24.1-py3-none-any.whl (53 kB)
Using cached setuptools-70.2.0-py3-none-any.whl (930 kB)
Using cached wheel-0.43.0-py3-none-any.whl (65 kB)
Using cached typing_extensions-4.12.2-py3-none-any.whl (37 kB)
Using cached filelock-3.15.4-py3-none-any.whl (16 kB)
Using cached fsspec-2024.6.1-py3-none-any.whl (177 kB)
Using cached jinja2-3.1.4-py3-none-any.whl (133 kB)
Using cached networkx-3.3-py3-none-any.whl (1.7 MB)
Using cached sympy-1.13.0-py3-none-any.whl (6.2 MB)
Installing collected packages: ninja, mpmath, wheel, typing-extensions, sympy, setuptools, packaging, networkx, MarkupSafe, fsspec, filelock, cmake, jinja2, torch
Creating /tmp/pip-build-env-kq9n1git/overlay/bin
changing mode of /tmp/pip-build-env-kq9n1git/overlay/bin/ninja to 755
changing mode of /tmp/pip-build-env-kq9n1git/overlay/bin/wheel to 755
changing mode of /tmp/pip-build-env-kq9n1git/overlay/bin/isympy to 755
changing mode of /tmp/pip-build-env-kq9n1git/overlay/bin/cmake to 755
changing mode of /tmp/pip-build-env-kq9n1git/overlay/bin/cpack to 755
changing mode of /tmp/pip-build-env-kq9n1git/overlay/bin/ctest to 755
changing mode of /tmp/pip-build-env-kq9n1git/overlay/bin/convert-caffe2-to-onnx to 755
changing mode of /tmp/pip-build-env-kq9n1git/overlay/bin/convert-onnx-to-caffe2 to 755
changing mode of /tmp/pip-build-env-kq9n1git/overlay/bin/torchrun to 755
Successfully installed MarkupSafe-2.1.5 cmake-3.30.0 filelock-3.15.4 fsspec-2024.6.1 jinja2-3.1.4 mpmath-1.3.0 networkx-3.3 ninja-<IP_ADDRESS> packaging-24.1 setuptools-70.2.0 sympy-1.13.0 torch-2.3.0+cpu typing-extensions-4.12.2 wheel-0.43.0
Installing build dependencies ... done
Running command Getting requirements to build wheel
running egg_info
writing vllm.egg-info/PKG-INFO
writing dependency_links to vllm.egg-info/dependency_links.txt
writing requirements to vllm.egg-info/requires.txt
writing top-level names to vllm.egg-info/top_level.txt
reading manifest file 'vllm.egg-info/SOURCES.txt'
reading manifest template 'MANIFEST.in'
adding license file 'LICENSE'
writing manifest file 'vllm.egg-info/SOURCES.txt'
Getting requirements to build wheel ... done
Running command Preparing metadata (pyproject.toml)
running dist_info
creating /tmp/pip-modern-metadata-ghi6pxan/vllm.egg-info
writing /tmp/pip-modern-metadata-ghi6pxan/vllm.egg-info/PKG-INFO
writing dependency_links to /tmp/pip-modern-metadata-ghi6pxan/vllm.egg-info/dependency_links.txt
writing requirements to /tmp/pip-modern-metadata-ghi6pxan/vllm.egg-info/requires.txt
writing top-level names to /tmp/pip-modern-metadata-ghi6pxan/vllm.egg-info/top_level.txt
writing manifest file '/tmp/pip-modern-metadata-ghi6pxan/vllm.egg-info/SOURCES.txt'
reading manifest file '/tmp/pip-modern-metadata-ghi6pxan/vllm.egg-info/SOURCES.txt'
reading manifest template 'MANIFEST.in'
adding license file 'LICENSE'
writing manifest file '/tmp/pip-modern-metadata-ghi6pxan/vllm.egg-info/SOURCES.txt'
creating '/tmp/pip-modern-metadata-ghi6pxan/vllm-0.5.1+openvino.dist-info'
Preparing metadata (pyproject.toml) ... done
Requirement already satisfied: cmake>=3.21 in<EMAIL_ADDRESS>(from vllm==0.5.1+openvino) (3.30.0)
Requirement already satisfied: ninja in<EMAIL_ADDRESS>(from vllm==0.5.1+openvino) (<IP_ADDRESS>)
Collecting psutil (from vllm==0.5.1+openvino)
Obtaining dependency information for psutil from https://files.pythonhosted.org/packages/19/74/f59e7e0d392bc1070e9a70e2f9190d652487ac115bb16e2eff6b22ad1d24/psutil-6.0.0-cp36-abi3-manylinux_2_12_x86_64.manylinux2010_x86_64.manylinux_2_17_x86_64.manylinux2014_x86_64.whl.metadata
Using cached psutil-6.0.0-cp36-abi3-manylinux_2_12_x86_64.manylinux2010_x86_64.manylinux_2_17_x86_64.manylinux2014_x86_64.whl.metadata (21 kB)
Collecting sentencepiece (from vllm==0.5.1+openvino)
Obtaining dependency information for sentencepiece from https://files.pythonhosted.org/packages/a6/27/33019685023221ca8ed98e8ceb7ae5e166032686fa3662c68f1f1edf334e/sentencepiece-0.2.0-cp310-cp310-manylinux_2_17_x86_64.manylinux2014_x86_64.whl.metadata
Using cached sentencepiece-0.2.0-cp310-cp310-manylinux_2_17_x86_64.manylinux2014_x86_64.whl.metadata (7.7 kB)
Collecting numpy<2.0.0 (from vllm==0.5.1+openvino)
Obtaining dependency information for numpy<2.0.0 from https://files.pythonhosted.org/packages/4b/d7/ecf66c1cd12dc28b4040b15ab4d17b773b87fa9d29ca16125de01adb36cd/numpy-1.26.4-cp310-cp310-manylinux_2_17_x86_64.manylinux2014_x86_64.whl.metadata
Using cached numpy-1.26.4-cp310-cp310-manylinux_2_17_x86_64.manylinux2014_x86_64.whl.metadata (61 kB)
Collecting requests (from vllm==0.5.1+openvino)
Obtaining dependency information for requests from https://files.pythonhosted.org/packages/f9/9b/335f9764261e915ed497fcdeb11df5dfd6f7bf257d4a6a2a686d80da4d54/requests-2.32.3-py3-none-any.whl.metadata
Using cached requests-2.32.3-py3-none-any.whl.metadata (4.6 kB)
Collecting tqdm (from vllm==0.5.1+openvino)
Obtaining dependency information for tqdm from https://files.pythonhosted.org/packages/18/eb/fdb7eb9e48b7b02554e1664afd3bd3f117f6b6d6c5881438a0b055554f9b/tqdm-4.66.4-py3-none-any.whl.metadata
Using cached tqdm-4.66.4-py3-none-any.whl.metadata (57 kB)
Collecting py-cpuinfo (from vllm==0.5.1+openvino)
Obtaining dependency information for py-cpuinfo from https://files.pythonhosted.org/packages/e0/a9/023730ba63db1e494a271cb018dcd361bd2c917ba7004c3e49d5daf795a2/py_cpuinfo-9.0.0-py3-none-any.whl.metadata
Using cached py_cpuinfo-9.0.0-py3-none-any.whl.metadata (794 bytes)
Collecting transformers>=4.42.0 (from vllm==0.5.1+openvino)
Obtaining dependency information for transformers>=4.42.0 from https://files.pythonhosted.org/packages/20/5c/244db59e074e80248fdfa60495eeee257e4d97c3df3487df68be30cd60c8/transformers-4.42.3-py3-none-any.whl.metadata
Using cached transformers-4.42.3-py3-none-any.whl.metadata (43 kB)
Collecting tokenizers>=0.19.1 (from vllm==0.5.1+openvino)
Obtaining dependency information for tokenizers>=0.19.1 from https://files.pythonhosted.org/packages/40/4f/eb78de4af3b17b589f43a369cbf0c3a7173f25c3d2cd93068852c07689aa/tokenizers-0.19.1-cp310-cp310-manylinux_2_17_x86_64.manylinux2014_x86_64.whl.metadata
Using cached tokenizers-0.19.1-cp310-cp310-manylinux_2_17_x86_64.manylinux2014_x86_64.whl.metadata (6.7 kB)
Collecting fastapi (from vllm==0.5.1+openvino)
Obtaining dependency information for fastapi from https://files.pythonhosted.org/packages/e6/33/de41e554e5a187d583906e10d53bfae5fd6c07e98cbf4fe5262bd37e739a/fastapi-0.111.0-py3-none-any.whl.metadata
Using cached fastapi-0.111.0-py3-none-any.whl.metadata (25 kB)
Collecting aiohttp (from vllm==0.5.1+openvino)
Obtaining dependency information for aiohttp from https://files.pythonhosted.org/packages/a0/09/e7637f4f0760cad4d67347bbd8311c6ad0259a3fc01f04555af9e84bd378/aiohttp-3.9.5-cp310-cp310-manylinux_2_17_x86_64.manylinux2014_x86_64.whl.metadata
Using cached aiohttp-3.9.5-cp310-cp310-manylinux_2_17_x86_64.manylinux2014_x86_64.whl.metadata (7.5 kB)
Collecting openai (from vllm==0.5.1+openvino)
Obtaining dependency information for openai from https://files.pythonhosted.org/packages/82/60/2ab971a017357bab653035df8ff6e6e625e1d70a8e2e03faed34741750f1/openai-1.35.10-py3-none-any.whl.metadata
Using cached openai-1.35.10-py3-none-any.whl.metadata (21 kB)
Collecting uvicorn[standard] (from vllm==0.5.1+openvino)
Obtaining dependency information for uvicorn[standard] from https://files.pythonhosted.org/packages/b2/f9/e6f30ba6094733e4f9794fd098ca0543a19b07ac1fa3075d595bf0f1fb60/uvicorn-0.30.1-py3-none-any.whl.metadata
Using cached uvicorn-0.30.1-py3-none-any.whl.metadata (6.3 kB)
Collecting pydantic>=2.0 (from vllm==0.5.1+openvino)
Obtaining dependency information for pydantic>=2.0 from https://files.pythonhosted.org/packages/1f/fa/b7f815b8c9ad021c07f88875b601222ef5e70619391ade4a49234d12d278/pydantic-2.8.2-py3-none-any.whl.metadata
Using cached pydantic-2.8.2-py3-none-any.whl.metadata (125 kB)
Collecting pillow (from vllm==0.5.1+openvino)
Obtaining dependency information for pillow from https://files.pythonhosted.org/packages/b5/5b/6651c288b08df3b8c1e2f8c1152201e0b25d240e22ddade0f1e242fc9fa0/pillow-10.4.0-cp310-cp310-manylinux_2_28_x86_64.whl.metadata
Using cached pillow-10.4.0-cp310-cp310-manylinux_2_28_x86_64.whl.metadata (9.2 kB)
Collecting prometheus-client>=0.18.0 (from vllm==0.5.1+openvino)
Obtaining dependency information for prometheus-client>=0.18.0 from https://files.pythonhosted.org/packages/c7/98/745b810d822103adca2df8decd4c0bbe839ba7ad3511af3f0d09692fc0f0/prometheus_client-0.20.0-py3-none-any.whl.metadata
Using cached prometheus_client-0.20.0-py3-none-any.whl.metadata (1.8 kB)
Collecting prometheus-fastapi-instrumentator>=7.0.0 (from vllm==0.5.1+openvino)
Obtaining dependency information for prometheus-fastapi-instrumentator>=7.0.0 from https://files.pythonhosted.org/packages/59/66/2e93a8f56adb51ede41d0ef5f4f0277522acc4adc87937f5457b7b5692a8/prometheus_fastapi_instrumentator-7.0.0-py3-none-any.whl.metadata
Using cached prometheus_fastapi_instrumentator-7.0.0-py3-none-any.whl.metadata (13 kB)
Collecting tiktoken>=0.6.0 (from vllm==0.5.1+openvino)
Obtaining dependency information for tiktoken>=0.6.0 from https://files.pythonhosted.org/packages/e7/8c/7d1007557b343d5cf18349802e94d3a14397121e9105b4661f8cd753f9bf/tiktoken-0.7.0-cp310-cp310-manylinux_2_17_x86_64.manylinux2014_x86_64.whl.metadata
Using cached tiktoken-0.7.0-cp310-cp310-manylinux_2_17_x86_64.manylinux2014_x86_64.whl.metadata (6.6 kB)
Collecting lm-format-enforcer==0.10.1 (from vllm==0.5.1+openvino)
Obtaining dependency information for lm-format-enforcer==0.10.1 from https://files.pythonhosted.org/packages/2d/fd/e21d1f0608da7696746c5d4cdf2f944d714daf63a97def416e0f3c154f98/lm_format_enforcer-0.10.1-py3-none-any.whl.metadata
Using cached lm_format_enforcer-0.10.1-py3-none-any.whl.metadata (16 kB)
Collecting outlines>=0.0.43 (from vllm==0.5.1+openvino)
Obtaining dependency information for outlines>=0.0.43 from https://files.pythonhosted.org/packages/b5/f4/92175c15dc702e5cf099605170c8a4a945682e1e52679fb789cb0894a0b5/outlines-0.1.dev0-py3-none-any.whl.metadata
Using cached outlines-0.1.dev0-py3-none-any.whl.metadata (655 bytes)
Requirement already satisfied: typing-extensions in<EMAIL_ADDRESS>(from vllm==0.5.1+openvino) (4.12.2)
Requirement already satisfied: filelock>=3.10.4 in<EMAIL_ADDRESS>(from vllm==0.5.1+openvino) (3.15.4)
Requirement already satisfied: torch>=2.1.2 in<EMAIL_ADDRESS>(from vllm==0.5.1+openvino) (2.3.0+cpu)
Collecting openvino~=2024.3.0.dev (from vllm==0.5.1+openvino)
Using cached https://storage.openvinotoolkit.org/wheels/nightly/openvino/openvino-2024.3.0.dev20240708-15945-cp310-cp310-manylinux2014_x86_64.whl (40.7 MB)
Collecting optimum-intel>=1.17.2 (from optimum-intel[openvino]>=1.17.2->vllm==0.5.1+openvino)
Obtaining dependency information for optimum-intel>=1.17.2 from https://files.pythonhosted.org/packages/7a/89/62ae5d3a97af94cf5d0e643936413c1a7c6796b9b9a202d8ebb5e70f20cd/optimum_intel-1.18.0-py3-none-any.whl.metadata
Using cached optimum_intel-1.18.0-py3-none-any.whl.metadata (16 kB)
Collecting triton>=2.2.0 (from vllm==0.5.1+openvino)
Using cached https://download.pytorch.org/whl/triton-2.3.1-cp310-cp310-manylinux_2_17_x86_64.manylinux2014_x86_64.whl (168.1 MB)
Collecting interegular>=0.3.2 (from lm-format-enforcer==0.10.1->vllm==0.5.1+openvino)
Obtaining dependency information for interegular>=0.3.2 from https://files.pythonhosted.org/packages/c4/01/72d6472f80651673716d1deda2a5bbb633e563ecf94f4479da5519d69d25/interegular-0.3.3-py37-none-any.whl.metadata
Using cached interegular-0.3.3-py37-none-any.whl.metadata (3.0 kB)
Requirement already satisfied: packaging in<EMAIL_ADDRESS>(from lm-format-enforcer==0.10.1->vllm==0.5.1+openvino) (24.1)
Collecting pyyaml (from lm-format-enforcer==0.10.1->vllm==0.5.1+openvino)
Obtaining dependency information for pyyaml from https://files.pythonhosted.org/packages/e8/08/a33f044060da4c5a3dc0d8f698a7dadb831d36787df3e77a3d0babb3f655/PyYAML-6.0.2rc1-cp310-cp310-manylinux_2_17_x86_64.manylinux2014_x86_64.whl.metadata
Using cached PyYAML-6.0.2rc1-cp310-cp310-manylinux_2_17_x86_64.manylinux2014_x86_64.whl.metadata (2.2 kB)
Collecting openvino-telemetry>=2023.2.1 (from openvino~=2024.3.0.dev->vllm==0.5.1+openvino)
Obtaining dependency information for openvino-telemetry>=2023.2.1 from https://files.pythonhosted.org/packages/2f/6c/89a38fd365446476be13811f565da44d52be4f184d7cb0a0abfc7970c0f5/openvino_telemetry-2024.1.0-py3-none-any.whl.metadata
Using cached openvino_telemetry-2024.1.0-py3-none-any.whl.metadata (2.3 kB)
INFO: pip is looking at multiple versions of optimum-intel to determine which version is compatible with other requirements. This could take a while.
Collecting optimum-intel>=1.17.2 (from optimum-intel[openvino]>=1.17.2->vllm==0.5.1+openvino)
Obtaining dependency information for optimum-intel>=1.17.2 from https://files.pythonhosted.org/packages/c8/e6/3b0e3cd8de323378b751aa8cac109c2b9f6a72cf6dfca2f14a4fbf78a5b4/optimum_intel-1.17.2-py3-none-any.whl.metadata
Using cached optimum_intel-1.17.2-py3-none-any.whl.metadata (16 kB)
ERROR: Cannot install optimum-intel and vllm==0.5.1+openvino because these package versions have conflicting dependencies.
The conflict is caused by:
vllm 0.5.1+openvino depends on transformers>=4.42.0
optimum-intel 1.18.0 depends on transformers<4.42.0 and >=4.36.0
vllm 0.5.1+openvino depends on transformers>=4.42.0
optimum-intel 1.17.2 depends on transformers<4.42.0 and >=4.36.0
To fix this you could try to:

loosen the range of package versions you've specified
remove package versions to allow pip to attempt to solve the dependency conflict

ERROR: ResolutionImpossible: for help visit https://pip.pypa.io/en/latest/topics/dependency-resolution/#dealing-with-dependency-conflicts

Hi @HPUedCSLearner there was a patch release of optimum-intel yesterday that added compatibility with transformers 4.42. That should fix this issue. Could you try again?

thank you very much!!! it work


Content of app/nltk_data not included in slug

With the latest v97, data downloaded as part of slug compilation step (specified via post_compile hook) is not retained in the slug.
This worked fine in v85, and pinning back to v85 this still works.

you need to download the files to the CWD, not to /app.

Thanks; I've pinned to v85 in the meantime. I think it'd be nice to have a warning posted somewhere about this change so to not have a scare and failing builds coming as surprise! :)
The above mentioned post_compile hook is fairly popular way of getting the nltk data.

I just added official nltk support to the buildpack!
Simply add a nltk.txt file with a list of corpora you want installed, and everything should work as expected.

Thank you! It looks like a good solution.
I'd whipped up a buildpack to download the corpora in a multi-buildpack configuration:  prashnts/heroku-buildpack-textblob which seems unnecessary now.

@prashnts nice!


Ship vote for Zowe v1.3.0

The ZLC should vote on approving this release. This would confirm that all testing has been completed (including Security testing) and no problems were found.

Voted to approve


why the read latency for this code is 2+ hours after doing a convolution?

image = img_as_float(im)
gamma_corrected = exposure.adjust_gamma(image, 10)
thresh = threshold_otsu(image)
#Applying threshold
thresholded_image = image > thresh
#Finds contour at certain values
contours = measure.find_contours(thresholded_image, 0.8)
fig, ax = plt.subplots()
ax.imshow(image, cmap=plt.cm.gray)
for n, contour in enumerate(contours):
ax.plot(contour[:, 1], contour[:, 0], linewidth=2)
ax.axis('image')
ax.set_xticks([])
ax.set_yticks([])
plt.show()

For me it runs in under a second.


make profiles() hookable

For extending RockFrontend with other profiles I only needed to make the profiles() method hookable.

cool, thx :)


update shell_plus to not save ipython history when using Jupyter

xref: https://github.com/jupyter/notebook/issues/3001#issuecomment-429760689

Coverage decreased (-71.09%) to 0.0% when pulling 2b7033722851b7dcb8de9c295e5440dc7f382075 on terencehonles:do-not-intermingle-jupyter-and-ipython-history into 75769633c957561d8c6ed7d87c0891705d5165c7 on django-extensions:master.

Thanks !


Persistence Test: Introduce AllRowsEquivalentToJson and ActiveRowsEquivalentToJson

Summary
Adds two new types of TestAssertion: AllRowsEquivalentToJson and ActiveRowsEquivalentToJson (and the corresponding fail statuses), to be used by persistence tests.
Depends on https://github.com/finos/legend-engine/pull/1242
How did you test this change?

[x] Test(s) added
[x] Manual testing (please provide screenshots/recordings)
[ ] No testing (please provide an explanation)

Screenshot 1: test passes case

Screenshot 2: test fails case

Can you some grammar tests in legend-manual-tests and some unit tests in DSL_Persistence_Roundtrip.test.ts

Can you add some grammar tests in legend-manual-tests and some unit tests in DSL_Persistence_Roundtrip.test.ts

Added tests in legend-manual-tests. For DSL_Persistence_Roundtrip.test.ts, I have already included tests, please let me know if they are okay :)


Doesn't recognize shell meta-characters in file path

When passing the CSV path an a string, qsv doesn't seem to recognize the tilde "~" character on Linux (Ubuntu 18.04). Here's the command history to show how to reproduce the bug:
qsv$ node bin/qsv.js -p "~/Desktop/data.csv" -h
{ [Error: ENOENT: no such file or directory, open '~/Desktop/data.csv']
  errno: -2,
  code: 'ENOENT',
  syscall: 'open',
  path: '~/Desktop/data.csv' }
(node:16684) UnhandledPromiseRejectionWarning: TypeError [ERR_INVALID_ARG_TYPE]: The "chunk" argument must be one of type string or Buffer. Received type object
    at validChunk (_stream_writable.js:258:10)
    at WriteStream.Writable.write (_stream_writable.js:292:21)
    at start (/media/common/code/projects/github/qsv/bin/qsv.js:23:20)
(node:16684) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 2)
(node:16684) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
qsv$ node bin/qsv.js -p "/home/ankush/Desktop/data.csv" -h
QSV>

Thanks for the report!
Afaik node.js doesn't expand meta characters automatically see https://github.com/nodejs/node/issues/684
But there is a package linked in the issue that looks promising: untildify

Damn. I saw something interesting in the link you shared: https://github.com/nodejs/node/issues/684#issuecomment-302413878. But then, who knows what other characters we might encounter later!

I just tested the version of #14 with ~ and $ and it seems to work
test=path/to/file.csv

node bin/qsv.js -p ~/$test

I don't know if there are more meta characters of interest.
If we find some it's probably best to open an issue/pr on the untildify repo.
What do you think?


Bold selected item in frost-select and stabilize tests for CI

This project uses semver, please check the scope of this pr:

[x] #patch# - backwards-compatible bug fix
[ ] #minor# - adding functionality in a backwards-compatible manner
[ ] #major# - incompatible API change

CHANGELOG

Fixed selected item(s) in the select dropdown to have a heavier font weight.

👍

Approved

I take it the wait statements didn't help with your CI failures?

Approved

:+1:


For a given board and target confguration, for example px4_fmu-v5_default, what code is scanned by cppcheck & clang-tidy vs modalAI_flightcore-v1_default

For a given board and target confguration, for example px4_fmu-v5_default, what code is scanned by cppcheck & clang-tidy vs modalAI_flightcore-v1_default

This is dependent on (potential) work done on: #17. The answer is only px4_sitl is scanned right now. So there is no difference because neither of these boards are scanned.

The specified configuration options in the *.px4board file ONLY change what code is scanned on a driver / module / app / etc. basis. The whole px4 library which every driver / module / app / etc... depends on is scanned no matter what.
Proper make targets are needed in order to scan whatever firmware you choose.


Fix nil pointer dereference in initSidecarInjector of Pilot

When the Pilot is deployed in a non-K8s environment, the process of initializing the server will cause the program to panic. In order to reproduce this issue, as in the following example, set the service registry of the Pilot to Mock registry,  build and run discovery cmd.
./pilot-discovery discovery --registries=mock --configDir=/tmp

Then, I got the nil pointer dereference error.
panic: runtime error: invalid memory address or nil pointer dereference

I find the reason. When the local injection config is not exist in the path ./var/lib/istio/inject specified in initial serverArgs, the  server will find the remote injection config by accessing ConfigMap with KubeClient. Our Pilot is deployed in a non-K8s environment and the KubeClient will not be created, so we get the nil pointer dereference.
I improve the code of this method initSidecarInjector  to avoid the above issue.
[ ] Configuration Infrastructure
[ ] Docs
[ ] Installation
[ ] Networking
[ ] Performance and Scalability
[ ] Policies and Telemetry
[ ] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure

Hi @SpecialYang. Thanks for your PR.
I'm waiting for a istio member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.
Once the patch is verified, the new status will be reflected by the ok-to-test label.
I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@googlebot I signed it!

/ok-to-test

@SpecialYang: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

release-notes_istio
55f24d47bc404d7a3362e0bd00e0f2078112d3a1
link
/test release-notes_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@SpecialYang: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

release-notes_istio
55f24d47bc404d7a3362e0bd00e0f2078112d3a1
link
/test release-notes_istio

lint_istio
55f24d47bc404d7a3362e0bd00e0f2078112d3a1
link
/test lint_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@SpecialYang: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

release-notes_istio
55f24d47bc404d7a3362e0bd00e0f2078112d3a1
link
/test release-notes_istio

lint_istio
55f24d47bc404d7a3362e0bd00e0f2078112d3a1
link
/test lint_istio

gencheck_istio
55f24d47bc404d7a3362e0bd00e0f2078112d3a1
link
/test gencheck_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/retest

@SpecialYang: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

lint_istio
55f24d47bc404d7a3362e0bd00e0f2078112d3a1
link
/test lint_istio

gencheck_istio
55f24d47bc404d7a3362e0bd00e0f2078112d3a1
link
/test gencheck_istio

release-notes_istio
55f24d47bc404d7a3362e0bd00e0f2078112d3a1
link
/test release-notes_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@SpecialYang: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

lint_istio
55f24d47bc404d7a3362e0bd00e0f2078112d3a1
link
/test lint_istio

release-notes_istio
55f24d47bc404d7a3362e0bd00e0f2078112d3a1
link
/test release-notes_istio

gencheck_istio
55f24d47bc404d7a3362e0bd00e0f2078112d3a1
link
/test gencheck_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@SpecialYang: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

release-notes_istio
55f24d47bc404d7a3362e0bd00e0f2078112d3a1
link
/test release-notes_istio

gencheck_istio
55f24d47bc404d7a3362e0bd00e0f2078112d3a1
link
/test gencheck_istio

lint_istio
55f24d47bc404d7a3362e0bd00e0f2078112d3a1
link
/test lint_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@SpecialYang: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

release-notes_istio
55f24d47bc404d7a3362e0bd00e0f2078112d3a1
link
/test release-notes_istio

gencheck_istio
55f24d47bc404d7a3362e0bd00e0f2078112d3a1
link
/test gencheck_istio

lint_istio
55f24d47bc404d7a3362e0bd00e0f2078112d3a1
link
/test lint_istio

integ-security-multicluster-tests_istio
55f24d47bc404d7a3362e0bd00e0f2078112d3a1
link
/test integ-security-multicluster-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@SpecialYang: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

gencheck_istio
55f24d47bc404d7a3362e0bd00e0f2078112d3a1
link
/test gencheck_istio

lint_istio
55f24d47bc404d7a3362e0bd00e0f2078112d3a1
link
/test lint_istio

integ-security-multicluster-tests_istio
55f24d47bc404d7a3362e0bd00e0f2078112d3a1
link
/test integ-security-multicluster-tests_istio

release-notes_istio
7fe4ac7501f0646e15af8951b0e9889d38fe38ec
link
/test release-notes_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@SpecialYang: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

lint_istio
55f24d47bc404d7a3362e0bd00e0f2078112d3a1
link
/test lint_istio

integ-security-multicluster-tests_istio
55f24d47bc404d7a3362e0bd00e0f2078112d3a1
link
/test integ-security-multicluster-tests_istio

release-notes_istio
7fe4ac7501f0646e15af8951b0e9889d38fe38ec
link
/test release-notes_istio

gencheck_istio
7fe4ac7501f0646e15af8951b0e9889d38fe38ec
link
/test gencheck_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@SpecialYang: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-security-multicluster-tests_istio
55f24d47bc404d7a3362e0bd00e0f2078112d3a1
link
/test integ-security-multicluster-tests_istio

release-notes_istio
7fe4ac7501f0646e15af8951b0e9889d38fe38ec
link
/test release-notes_istio

gencheck_istio
7fe4ac7501f0646e15af8951b0e9889d38fe38ec
link
/test gencheck_istio

lint_istio
7fe4ac7501f0646e15af8951b0e9889d38fe38ec
link
/test lint_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@SpecialYang: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

gencheck_istio
7fe4ac7501f0646e15af8951b0e9889d38fe38ec
link
/test gencheck_istio

lint_istio
7fe4ac7501f0646e15af8951b0e9889d38fe38ec
link
/test lint_istio

release-notes_istio
95f1a38627676b7f8297fdde2b337006796a57c9
link
/test release-notes_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@SpecialYang: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

release-notes_istio
95f1a38627676b7f8297fdde2b337006796a57c9
link
/test release-notes_istio

integ-pilot-multicluster-tests_istio
95f1a38627676b7f8297fdde2b337006796a57c9
link
/test integ-pilot-multicluster-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@SpecialYang: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

release-notes_istio
95f1a38627676b7f8297fdde2b337006796a57c9
link
/test release-notes_istio

integ-pilot-multicluster-tests_istio
95f1a38627676b7f8297fdde2b337006796a57c9
link
/test integ-pilot-multicluster-tests_istio

integ-telemetry-k8s-tests_istio
95f1a38627676b7f8297fdde2b337006796a57c9
link
/test integ-telemetry-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test integ-telemetry-k8s-tests_istio

/test integ-pilot-multicluster-tests_ist

@SpecialYang: The specified target(s) for /test were not found.
The following commands are available to trigger jobs:

/test unit-tests_istio
/test release-test_istio
/test benchmark_istio
/test integ-pilot-k8s-tests_istio
/test integ-security-k8s-tests_istio
/test integ-telemetry-k8s-tests_istio
/test integ-telemetry-mc-k8s-tests_istio
/test integ-multicluster-k8s-tests_istio
/test integ-distroless-k8s-tests_istio
/test integ-ipv6-k8s-tests_istio
/test integ-operator-controller-tests_istio
/test integ-pilot-multicluster-tests_istio
/test integ-external-istiod-mc-tests_istio
/test integ-security-multicluster-tests_istio
/test integ-helm-tests_istio
/test analyze-tests_istio
/test lint_istio
/test gencheck_istio
/test release-notes_istio

Use /test all to run the following jobs:

unit-tests_istio
release-test_istio
integ-pilot-k8s-tests_istio
integ-security-k8s-tests_istio
integ-telemetry-k8s-tests_istio
integ-telemetry-mc-k8s-tests_istio
integ-multicluster-k8s-tests_istio
integ-distroless-k8s-tests_istio
integ-ipv6-k8s-tests_istio
integ-operator-controller-tests_istio
integ-pilot-multicluster-tests_istio
integ-external-istiod-mc-tests_istio
integ-security-multicluster-tests_istio
integ-helm-tests_istio
analyze-tests_istio
lint_istio
gencheck_istio
release-notes_istio

In response to this:

/test integ-pilot-multicluster-tests_ist

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

/test integ-pilot-multicluster-tests_istio

@howardjohn Can you add the label release-notes-none for this pr? Thanks.

/retest


provider names must match in /docs/user-guides/acme-dns-validation.md

Is this a BUG REPORT or FEATURE REQUEST?:

Uncomment only one, leave it on its own line:

/kind bug

/kind feature

What happened:
Certificate could not discover any configured provider.
What you expected to happen:
Flawless provider discovery.
How to reproduce it (as minimally and precisely as possible):
Follow /docs/user-guides/acme-dns-validation.md
Anything else we need to know?:
Fix @ https://github.com/clstb/cert-manager/commit/604ce9e753dbb026130824e2b63e52fa7b2d2200
Environment:

Kubernetes version (use kubectl version):
v1.8.3-gke.0
Cloud provider or hardware configuration**:
gcp
Install tools:
helm
Others:

Thanks for the report (and corresponding patch!). Would you be able to make a PR to fix this upstream?

PR opened and lives here: https://github.com/jetstack/cert-manager/pull/224


Carto V4 Beta - Where?

Appreciate that Carto.Js v3 is no longer being developed, is there a link to carto v4 beta repository available or is this only going to be available through a cdn?

Hello @dbkbali!
It is also available as an npm package https://www.npmjs.com/package/carto.js
You can access the documentation through https://carto.com/documentation/cartojs, I'm not sure if it's documented yet, but if it's not, it will be soon :)

Thanks for your feedback @dbkbali! We'll add a message about this in our readme.

Thanks


Add migration tool, guide and add script to test if migration job from api-server to CRD is working

Description
Changes proposed in this pr:

Add migration tool and guide which allow clients to do easily migration from api-server to CRD approach.
Scenario

pre-upgrade hook

Make API Server read-only
Check if API Server deployment exist. If deployment was not found we skip the migration.
Backup Service Catalog custom resources to files in a Persistent Volume.
Remove OwnerReference fields in all Secrets pointed by any ServiceBinding
Remove all Service Catalog resources

upgrade

remove the api-server
remove the etcd storage
adjust secrets, RBAC etc.
upgrade controller manager
install webhook server

post-upgrade

Scale down the Controller Manager to avoid any resource processing while backuping resources.
Restore all resources. The migration tool sets all necessary fields added in the Service Catalog 0.3.0.
Add proper OwnerReference to all Secrets pointed by ServiceBindings.
Scale up the Controller Manager.

Full documentation with diagrams is added in this PR: https://github.com/kubernetes-sigs/service-catalog/pull/2710/files#diff-c13a535c132e80742d0b5f424960c632

Add script to test if migration job from api-server to CRD is working (will be executed as CI pipeline).
Scenario:
1. Create k8s cluster (kind)
2. Install Service Catalog from latest api-server release
3. Created sample data (sample service broker, service instances etc.)
4. Upgrade Service Catalog to the version built from sources
5. Execute tests to check if data from step 3 are still working
6. Shutdown cluster

Fixes:

https://github.com/kubernetes-sigs/service-catalog/issues/2634
https://github.com/kubernetes-sigs/service-catalog/issues/2660

/retest

I think you actually broke some stuff in pkg/controller...

That’s true, there is sth wrong and I’m still working on it:)

/remove-label  do-not-merge/work-in-progress

/remove-do-not-merge/work-in-progress

@piotrmiskiewicz @jberkhahn PTAL

/test pull-build-all-images-for-s390x

Waiting for your reviews :)
/hold

/lgtm

/lgtm

/test pull-build-all-images-for-ppc64le

/test pull-build-all-images-for-arm

/test pull-service-catalog-test-integration

/test pull-service-catalog-test-integration

@jberkhahn changes applied:)
there is also PR for adding CI for running migration tests: https://github.com/kubernetes/test-infra/pull/14464.
It was executed on our infra: https://storage.googleapis.com/kyma-prow-logs/logs/post-test-sc-upgrade-job/1176903408213299200/build-log.txt. You can also execute it locally:
./contrib/hack/ci/run-migration-tests.sh

/lgtm


Dialog width does not follow the specs.

I don't know if this applies specwise to all dialogs, but at least the simple dialog does not follow the specs.
According to the specs whe width should wrap the content, but in 56dp steps, with a minimum of 5 x 56dp.
I'm mentioning this, because when I use a simple dialog on a Nexus 7 its width is almost as wide as the entire screen (in portrait mode), which is clearly not in accordance with the specs. It's as if margin_left and margin_right are defining the dialog's width, which is wrong.
http://www.google.com/design/spec/components/dialogs.html#dialogs-simple-dialogs
Other than that, it's a really great library.

Well, the only thing that page lists is the width of a simple dialog on a phone. It doesn't say anything about tablets, or regular dialogs, so there's not too much I can unless they add more information to the guidelines.

Voting on this.
Okay, maybe not the guidelines, but I simply CANNOT set dialog with to wrap_content, or to a fixed size. Even when using a custom view.

Yes, even if it isn't explicitly in the spec, and, @afollestad I apologize for pointing out a wrong thing, I think that implementing this feature would be no waste of time, as it should only be a matter of time when the spec includes more info on this.
It looks so wrong on a tablet that I had to move over to a feature-reduced popup menu.

Im not sure if this is material design specifications, but at least for my personal design specifications this looks totally weird. This dialog has a custom view with a framelayout set to wrap_content containing an ImageView set to  wrap_content

This one is wiithout a custom view and has the same too-wide layout.

A nexus 7 has a screen width of 600dp. So according to this where they use 5x56 dp = 280dp, thats  less than half of the screen width.
Im not sure but one of these could be interpreted to have 8*56dp=448dp, which would be about 75%.
Right now we are at... 90%?

@plusCubed have an ideas for this?

@plusCubed @teslacoil have any ideas for this?

Same here. I cannot achieve a dialog's width to be wrapped by a content's width.

I came across with this bug too....when I use a customView work well.

@diogo10 Thanks, I will check this out.
On a note aside, I noticed that on a Nexus 7 in the YouTube app the filter dialog for searches, the one that pops up when pressing the slashed triangle on the top right after entering a search allowing you to refine the search also expands itself to fill the screen, instead of wrapping the content.
So this may be a hint that Google hasn't yet taken enough care on defining the behaviour of the dialogs.
If the customView allows one to wrap the dialog's content as a workaround, then it may be better to wait until Google decides what to do.

@afollestad I am able to modify the dialog width by changing the insetRight and insetLeft attributes of the dialog background, so it is definitely possible to modify the width. Right now, the AppCompat library's background style uses a 16dp inset on all sides of the dialog. The lack of specs for tablet layouts (and details for dialogs on mobile - it looks quite ridiculous with 40dp padding on both sides as specified by the guidelines) makes me want to wait for Google before doing anything though.
As for the wrap_content thing, all layout attributes for the root view of custom views are ignored (I believe). @Ph1b
In the mean time, for anyone who wants to change the width, call getWindow().setLayout(width, height) on the MaterialDialog instance (keep in mind the 16dp inset is still applied). I wouldn't recommend doing this unless you know how to implement ALL the factors (screen width and height, content width and height, etc).

@plusCubed is it possible to see what insets AppCompat uses for different screen sizes, or do they not use insetRight and insetLeft? I agree that it's frustrating that Google offers little-to-no tablet information in the Material spec

@hzsweers We are using AppCompat's backgrounds, and I believe they only have one definition for all screen sizes (which is 16dp inset on all sides).

I see. We might have a couple of contacts at google on the MD team that we can reach out to on this, I'll shake some trees and report back. In the meantime, it would probably be safe to categorize insets for phones, 7" tablets, and 9"+ tablets to keep things simple. What do you think?

@hzsweers Thanks in advance. I don't know what to set for the insets for 7" and 9"+ though - it seems ambiguous to just assume some numbers. There is also a mechanism that I haven't fully investigated yet - if you turn a phone to landscape, something (OS/dialog theme/dialog style..? - IDK) limits the width.

So talked with our contact, and they gave us some guidelines:

We haven't established max widths of dialogs or bottom sheets. Instead, for the sake of flexibility, we simply determine width based on content needs and using increments (either 56dp for small screens, or 64dp for large screens).

For example, this dialog from spec is 5x width, or 280dp.

You can see here, in the metrics and keylines section of the Material Design spec, that we can use increments to determine multiple aspects of a layout, this way the size of various structural components relate to each other.

Regarding items with variable width and can fit to the container of the parent (text, gridviews, etc):

What I would suggest is a combination of the increments described, and an understanding of appropriate line length based on the content.

There is a section in spec under typography that talks about appropriate line length if you scroll down in the section a bit.

I put together this gist of some examples: https://gist.github.com/hzsweers/eb76c43f1a4536173af4
I think ultimately what we should do is just go with the width settings of the system dialogs. Open source, so we should hopefully be able to dig in and find them. Target that size, and allow custom views in the dialog to request a wider view if necessary (layoutparams + results of their onMeasure).
What do you think?

I am able to modify the dialog width by changing the insetRight and insetLeft attributes of the dialog
background, so it is definitely possible to modify the width.

@afollestad: Got more detailed instructions how to do that?

@hzsweers Sorry for getting back to you so late - kinda forgot about this :S I think that's a good idea - I'll get started on that. Perhaps in the future we can do something with the line length.
@freezy If you are willing to fork the repo, what you can do is get a copy of abc_dialog_material_background_light.xml from the appcompat library sources, and modify the insetLeft/insetRight. Then set that as the android:windowBackground attribute of the material-dialog theme. I don't recommend doing this - if you're just looking for a more optimized tablet layout, as I said above, I'll be working on that :)

Thanks for the info. I thought it would somehow be possible without a modified build. I fiddled with MaterialDialog#getView() but couldn't get it to display at a given width.
Future solutions to this problem would be very welcome. Thanks for giving it a thought!

We had a hangout with members of the material team on Tuesday and they're
going to look at improving the guidelines in Themis regard. In the
meantime, we agreed it's probably best to define upper and lower bounds for
width in accordance with the spec for line length, so I think we should
shoot for that.
Proposed rules:

If a custom view and it wraps its content, try to wrap around the view's
intrinsic width (measure first and set the rest of the dialog's dimensions
accordingly)
If custom view and match/fill parent, then fall back to line length
(maybe discourage this though)
If no custom view (I.e. The built-in stuff), all fall back to line length
bounds. Message-only especially can benefit from this.
after calculating desired line length and dialog width, set horizontal
margins accordingly to force this size. Use a density-specific Boolean
resources to resolve screen sizes and choose line lengths accordingly.

Thoughts?
On Thu, Jul 23, 2015 at 7:04 AM freezy<EMAIL_ADDRESS>wrote:

Thanks for the info. I thought it would somehow be possible without a
modified build. I fiddled with MaterialDialog#getView() but couldn't get
it to display at a given width.
Future solutions to this problem would be very welcome. Thanks for giving
it a thought!
—
Reply to this email directly or view it on GitHub
https://github.com/afollestad/material-dialogs/issues/552#issuecomment-124118215
.

We had a hangout with members of the material team on Tuesday and they're
going to look at improving the guidelines in Themis regard. In the
meantime, we agreed it's probably best to define upper and lower bounds for
width in accordance with the spec for line length, so I think we should
shoot for that.
Proposed rules:

If a custom view and it wraps its content, try to wrap around the view's
intrinsic width (measure first and set the rest of the dialog's dimensions
accordingly)
If custom view and match/fill parent, then fall back to line length
(maybe discourage this though)
If no custom view (I.e. The built-in stuff), all fall back to line length
bounds. Message-only especially can benefit from this.
after calculating desired line length and dialog width, set horizontal
margins accordingly to force this size. Use a density-specific Boolean
resources t

@hzsweers That sounds like a good plan. How should the line lengths and specific specs for that be though? Reading the guidelines, there doesn't seem to be a hard, fast spec - there's the 60 characters per line, then the "short lines" guideline (which seems to point at about 30 characters per line).
I think the simplest way to go about this would be to calculate the width for an optimal number of characters vs line length ratio (with lower/upper limits for the dialog width). In other words, the height vs width of a body of text. I have no idea whether that is an approved way under the material guidelines though. The optimal height vs width (# of char vs line length) ratio would also need to be determined.
The other option is to follow the guideline more closely and determine a cutoff for the number of characters for a text to be considered "short" and "normal".
Either way, we would also need to take into account other languages - which makes me think this all needs to be either configurable or highly advanced to be able to calculate the line length correctly for all languages. Although using the first option, the optimal height vs width would probably work for most languages if we calculate the measured height vs width instead of using the # of characters.
What do you think?

I think we can be flexible regarding "short" lines. If it's below a certain number of characters, just assume it's a short message and measure accordingly. Default to the 60 character length though.
I think the character size won't really be a worry across languages though. We can revisit if people bring it up, but otherwise I think we can get probably 95% of what we want with behavior just with the simple approach.
So to be clear, my suggestion is:

Default to 60 char line length + normal horizonal insets as dialog width
If message is less than, say, 45 chars (we can test to see what looks best), then use the narrower line spec.

What about custom layouts? Is it possible to just "wrap content" for them?

if they wrap content, we can just use its given size. Onus is on the user to be intelligent about their custom views. If they say match/fill parent, then just limit it to the upper bound we defined above

Actually, I have a new idea that's much simpler. Notification panel has strict dimens for its sizes on different screen sizes, and it just so happens that this looks like it's about right. Maybe we can just steal them?
Example: https://android.googlesource.com/platform/frameworks/base/+/13522a2/packages/SystemUI/res/values-sw600dp/dimens.xml
See notification_panel_width

Boom: https://github.com/afollestad/material-dialogs/pull/640

https://github.com/afollestad/material-dialogs/releases/tag/v<IP_ADDRESS>

What about the ability to set dialog width to "wrap_content"?

The solution I pull requested covers probably 95% of all use cases for
dialogs. If you really need something that needs dynamic width, then you
probably shouldn't be using dialogs IMO. The main issue here was always
that dialogs took full width on tablets, which this solves. If someone can
come up with a good solution for reliably measuring custom view content
before the dialog is shown, I'm all for it. Until then, I think this is
enough.
On Mon, Aug 3, 2015, 10:22 PM Lev Shock<EMAIL_ADDRESS>wrote:

What about the ability to set dialog width to "wrap_content"?
—
Reply to this email directly or view it on GitHub
https://github.com/afollestad/material-dialogs/issues/552#issuecomment-127482461
.

Man, I can't believe I missed how Android system dialogs did the width. So, in the latest AppCompat 23.1.0, as Chris Banes writes here: https://plus.google.com/+ChrisBanes/posts/TX817XUewtF, the AppCompat dialog width was fixed, so I went to re-investigate. Turns out, there were just different screen width dimension resources in Android lollipop+ for the windowMinWidthMajor and windowMinWidthMinor properties, and they added them into the latest AppCompat.
Anyway, final resolution to this issue in 56b19673fccd84597067ea62aa657f15a397f395, reverting back to using the AppCompat styles for width.

@plusCubed good find!

@plusCubed here's a side by side of Material Dialogs (on the left) and a stock Marshmallow AlertDialog (on the right). Looks like it's working fine now!

But, the heights are slightly different, but it looks like the AppCompat AlertDialog doesn't really follow the guidelines perfectly.


Documentation on Oracle user/schema creation

Improve the documentation on setting up Oracle by mentioning explicit privileges. These improvements were possible with the help of Dubai Municipality.

Needs to be reviewed by the data storage team.

@basdebakker thanks for getting back to me.  As this PR is now merged, you can contact me directly if you require further changes.


some logging added needed for snet assistant

@besSveta , this logging should be enough for now. It doesn't fully solve #22 , but at least some messages about errors should appear. Can you please check if it is the case for the example in #22 and possibly other situations. It seems to work for problems in chromadb, and some other cases (like wrong agent name), but maybe something is missing.

@besSveta , this logging should be enough for now. It doesn't fully solve #22 , but at least some messages about errors should appear. Can you please check if it is the case for the example in #22 and possibly other situations. It seems to work for problems in chromadb, and some other cases (like wrong agent name), but maybe something is missing.

for the case #22 the logs are not written. maybe we should write logs on call of : raise TypeError, raise RuntimeError

They are written to console and I checked #22 example and see the error message, so it is not kept silent. Whether to create a log file or use console is up to the caller.


Support for some currencies

Resolves #1104 , at this moment not tested.

@Syndesi I'm going to close this for now.  Please re-open https://github.com/KaTeX/katex-fonts/issues/18 is resolved.  I'm going to try to add some documentation to https://github.com/KaTeX/katex-fonts to help people add new symbols to the fonts.  I'll let you know when that documentation is ready if you're interested in giving that a try.


Is there any subtle difference between use(*) use(/)

// 1
app.use(fn)

// 2
app.use(`/`, fn)

// 3
app.use(`*`, fn)

// 4
app.use([], fn)

there is no difference because both will prevent the request to go beyond them.

I remember I found their nuances in some project, but I forgot. I will continue to keep an eye on this issue

Hi @wll8 ! So the app.use function takes basically n-paths and then n-middlewares. When no paths are given, the default is '/'. This means that 1, 2, and 4 are all exactly the same in your example. But 3 uses the path *, which is a capture group, so though matches the same URLs, the entire URL is captured in req.params[0] and then the matched part (the entire URL) is trimmed off from req.url, leaving it as just /.
I hope that helps!


Polygon implementation

I've just realized you've added Mesh and Polygon classes which I had already implemented.
Please review what I have done so far and let me know what changes you'd like me to add, if any, so we won't do the same work twice.
BTW, I have some working examples in AndEngineExamples.

Hey,
I'm aware of your branch and it is highly appreciated!
I'm concerned though about the heavy usage of (permament and temporary(->GC)) Vector2 objects (every single object in Java/Android has sth like ... 24 Bytes of overhead!), which is impossible to use for large games like DreamZoo ( https://market.android.com/details?id=com.zynga.dreamzoo ) where you have a shitload of huge VBOs and permanently fear running out of memory. So instead the stuff I'm doing works on float[]s, which can be directly passed into the VBO. I'll try to leverage as much of the stuff that you've done :) !!!
Btw there already is a Triangulation algorithm in the physics extension, but it also works on Vector2d objects, so I'm going to fix that one to work on a float[] too.
Thanks again!

I know what you mean, I've also faced the nasty out of memory exception in one my apps. ;)
I didn't know about the triangulation algorithm in the physics extension, are you planning to move that code to AndEngine ? Otherwise filled Polygons would need to be an extension too.
Your Mesh and my PolygonBase class are pretty much the same (except for the Vector2d stuff and the ability to update the mesh ), so it should be pretty straight forward to update the Ellipse, PolyLine and Line code to use your class.
I can do the port if you're ok.
However, I'll wait to update the Polygon class as it needs the triangulation algorithm.

Yes, I planning to move more stuff from the PhysicsExtension down to AndEngine itself. (Mainly the hull and triangulation algorithms)
Also updating the ShapeCollisionChecker to work on float[]s and vertexOffsetX/vertexOffsetY/vertexStride parameters as we speak.
The stuff I'm doing should be pretty much stable by the end of today. =)

I have just updated Ellipse and PolyLine to use the Mesh class.
I'll update (filled) Polygons as soon as the triangulation algorithm goes into AndEngine.
Have a nice weekend!

I've just updated Polygon class to use your Mesh class. It currently uses EarClippingTriangulator from Box2d, but once you've found a home sweet home for the triangulation algorithm in Andengine, I'll update the import.


Driver not supported

Godot version: 3.2.3

OS/device including version: Microsoft Windows 10 Pro/10.0.19041 Build 19041 (It is graphics-related.)

Issue description: [In Godot] Well, when I hit the play button in the project it said my driver was not supported. [In Unity] But when I play a scene in Unity it works, I am very unhappy with this, please help. [I have an attachment if you need more info.]

Steps to reproduce: Well my driver version is "Intel(R) HD Graphics 3000"
Minimal reproduction project: None
Additional File(s): Godot Driver Proof.docx

You need to change in project settings(Project Settings -> Rendering -> Quality -> Driver Name) GLES 3 to GLES 2, because in Windows Intel HD 3000 doesn't support OpenGL ES 3.0.
I remember than on laptop I had i3-2330m with same video card, and on Linux after change from Windows I got 2x speedup(bunnymark score) and support for GLES 3.

Thanks! I actually forgot to test it in GLES2, Sorry.


no recommended download for my OS

It would be nice if the install page helped guide me to the right triple. I see some other issues about some sort of detect OS functionality, but when I check my network tab, that JS isn't being loaded, and I don't see it in the source HTML either.

@steveklabnik we've merged a few things in today- can you let us know if you still have this issue?
if so, could you take a screen cap for us and also let us know what window.os returns in your console? thanks!!

screenshot

> window.os
'64-windows-pc'

looks like artifacts.js is expecting

ohhh, the idea is that you only really open this page if we can't detect it on the homepage, any idea how we could direct the user here?
We do now load the JS here

the idea is that you only really open this page if we can't detect it on the homepage

The homepage shows me

which just leads to that page, so I'm not sure if it's working on the homepage either.

any idea how we could direct the user here?

https://rustup.rs/ is one example of a possibility; they show only the one relevant to my platform and then have a link to expand to other platforms. This is a product question really, so what you do specifically is more of a call for you all than for me :)

@steveklabnik when you have the homepage open can you run window.os in your browser console and tell us what it says
the home page is trying to detect your OS and is failing for some reason.. e.g. it shows me this (on a mac silicon):

Same as on the other page, '64-windows-pc.

sorry, didn't see under the image. investigating now. thanks for the info!

I believe I have sorted it out.
> getOS();
'64-windows-pc'

this is working properly. The issue:
let hit = Array.from(document.querySelectorAll(".target[data-targets]")).find(
  (a) => a.attributes["data-targets"].value.includes(os)
);

if i check this in my console, hit is undefined. It's trying to find a data-targets with 64-windows-pc, but the actual data-targets in the HTML is x86_64-pc-windows-msvc, so hit is undefined and I get the backup logic.

god, our detection is backwards and we need to switch from pc-windows to windows-pc

Success!


[release-1.16] Fix gateway service dependencies

This is an automated cherry-pick of #42422

@istio-testing: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

unit-tests-arm64_istio_release-1.16
ebfc3ecaa70c1caac5717dc9764c53cf9862a3e6
link
true
/test unit-tests-arm64

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.


Default content-type is json when using post.

@frodelu or @havardpe  PR

Fixes #19840

This should be accompanied by an update to the documentation, which still says you need to specify application/json.