Add a search service to address REST requests on indexer only nodes.

We add a search service to address REST requests in the UI of index-only
nodes as quickfix for #1482.
It will only address the root part of the requests.
That search service is not mounted as a gRPC service and hence will not address
leaf requests.
We also return an explicit error if there are no search nodes in the cluster.
(before we were panicking).
Closes #1482

@fmassot i opened a separate ticket for th unit test #1494. It might be trickier than the PR itself.


Print debug information for failed testcase.

What's the new look of the submit result message? My last commit has a test case fail, working on it.

On failed testcase, the toast message is like this:

The test case input or output or stdout data sometimes will be so big that the toast is not able to hold. If it can, I think we need a better format or even a better container to display the whole information rather than just simply put them into the toast.

Just consolidated some old commits.
I agree. Sometimes those text can be large. What format do you suggest?

I suggest a well structured urwid view, each section has a fixed size and for oversized contends user can scroll to view the whole content. The view could be a overlay view or we can just append the result view to the bottom of the detail view just like leetcode webpage does.

As a newbie to urwid, this is as far as I can get. The right way is probably to use Pile to stack the detail and result view, but I can not figure out how to assign the height of the detail view.

Somehow the test is failing. and upstream/master is failing on my environment as well. Is there a requirements.txt file that helps testing and debuging? Also, does Python version matter? I tried both 2.7.6 (ubuntu 14.04 default) and 2.7.13 (latest), both setup has test fails.

Sorry for delay, I was out for a meeting this whole week. Test depends on two mock library, mock and requests-mock, both for python 2.7. I haven't tried 2.7.6 but my python version is 2.7.13. Please use pip to install these two packages. You could run test by command 'make test', you could refer to Makefile for information of the command.

Closing since it seems you have a better solution.


fix one more Bug-1485134 from Bugzilla reported. Add WELS_B_MB_REC_VE…

…RIFY to verify if ref picture is lost

It still reports other error like:
codec/decoder/core/src/deblocking.cpp:759:5: runtime error: index 14 out of bounds for type 'const int8_t [4]'
please check again.

Sure, I'll fix it and I am  currently tied with other work right now but will try to fix as soon as I can.

@huili2 Do you have Bugzilla bug number for the error: in codec/decoder/core/src/deblocking.cpp:759:5?

exactly the same one as 1485134.

That's strange and I don't see the run time error codec/decoder/core/src/deblocking.cpp:759:5 anymore after my latest PR #3014.

I mean I don't see the run time error anymore with the attached sample stream in Bug1485134.

Since you are not able to reproduce it (maybe my environment is different), let's bypass it and go on.


nerdctl: use fuse-overlayfs only when kernel < 5.13

The real overlayfs can be safely used on kernel >= 5.13.
Instances created with older releases of Lima will continue to use fuse-overlayfs.
Fix #383

#383 mentions 3 conditions:

fuse-overlayfs shouldn't be needed when (kernel >= 5.13) || (kernel >= 5.11 && !selinux) || (kernel is ubuntu's variant)

This PR seems to only implement the first one: kernel >= 5.13

#383 mentions 3 conditions:

fuse-overlayfs shouldn't be needed when (kernel >= 5.13) || (kernel >= 5.11 && !selinux) || (kernel is ubuntu's variant)

This PR seems to only implement the first one: kernel >= 5.13

Yes, for simplicity


Mapping ICollections gives NotSupported exception

Hi
We are evaluating TinyMapper to replace ValueInjecter in our project. We would like to map entities to their same type to implement a kind of change tracking. Lets say we have this class:
public class Customer
{
    public string Name { get; set; }
    public virtual ICollection<Invoice> Invoices { get; set; }
}

In the setup of the application, we do TinyMapper.Bind<Customer, Customer>(). Then, when loading the Customer from a webservice, we make a copy of it using Map<T>() and save it as Original.
Original = TinyMapper.Map<Invoice>(invoice);

This line throws an exception:

System.NotSupportedException: 'Not suppoerted From ICollection´1 To ICollection´1'

If the Invoices property is null, everything works, but if it is set to contain invoices, we get above mentioned error.
The behavior that we would like is, that the ICollection (lets say it's a List) would be copied, but with references to the same Invoice instances. Is this possible?
(We tried to do TinyMapper.Bind<ICollection<Invoice>, List<Invoice>>(); but as expected this doesn't really work and gives the same error).
luetm

I got same error, I guess it is a bug and needs to be fixed.
Before having the bug fixed, I passed this error with Ignore action and tradational assign.
TinyMapper.Bind<Customer, CustomerVm>(config =>
{
config.Ignore(x => x.Invoices);
});
var customerVm = TinyMapper.Map(customer);
customerVm.Invoices = customer.Invoices;


Implement entrypoint run function

Because otheriwse we run into
AttributeError: module 'wyoming_satellite.__main__' has no attribute 'run'

Thanks!


Could be deployed to Heroku

Heroku returns the next message, when attempting the deploy:
Item could not be created:
We couldn't deploy your app because the source code violates the Salesforce Acceptable Use and External-Facing Services Policy.

Please check this discussion here - https://github.com/thelovekesh/ghost-v4-on-heroku/issues/51 and be sure to explore closed issues before opening a new ticket based on the same topic.


I would love to copy in an ISO time and convert

2023-08-01T17:27:00.000Z

Finally got to this one https://github.com/joecohens/epoch/pull/39


fixes #7757: in oci schema fix query results row keys case

fixes #7757: in oci schema fix query results row keys case when PDO::ATTR_CASE is set to PDO::CASE_LOWER

What if case is neutral?

Then the results contains keys as specified in the query, so uppercase.
I admin I have not run this. I'll try to install Oracle at home because I'm getting more interested in it.

Great.

I forgot to add - PDO::CASE_NATURAL is the default value for PDO::ATTR_CASE.

Ohh and it's a good idea to add a unit test for this. It could also check other databases.

Agree.

Added oci tests, but the whole oci schema implementation is a total mess. Column types are not detected properly. I'm going to fix that before adding case tests.

I feel like the tests I wrote here are some schema fixes should be moved to another PR. Can anybody take a look?

Another PR could be useful but this one isn't too big to be reviewed.

I think I'm going to quote all column names in oci.sql to allow reusing more tests.

I've added more tests and implemented some features like batchInsert along the way.
OracleActiveRecordTest still doesn't pass, this is the last one.
If anybody wants to run this, here's my pdo_oci8 driver.

I'm done here

Thinking about it, AR tests should include loading metadata when PDO:ATTR_CASE is set to PDO::CASE_UPPER.

There's at least one test failing now: https://travis-ci.org/yiisoft/yii2/jobs/56241236#L245

@samdark I fixed one test condition. I think there was parenthesis missing, can you take a look? Now Travis fails with Cubrid setup, is it normal?

Cubrid fail is about travis setup. It is, of course, very annoying because of fail to see real errors.

Ok I've added a test that actually tests what this issue was about and detected and fixed invalid behavior for mysql.
I can't test mssql or cubrid.

Cubrid fail is about travis setup. It is, of course, very annoying because of fail to see real errors.

This is an issue with travis, not sure what is happening as there is no error output, working for me locally. I have tried to make it more robust and not kill the whole test suite on failures:
https://github.com/yiisoft/yii2/commit/fd99fe1efabb22c0c7e019ace03152f0958a5411
If you rebase on master you should be able to see real test results.

@cebe I did and tests still fail. Anyhow, I'm done here with work except fixes if requested, moving on to gii issues.

Yeah but now you see it is only cubrid failing, before it was the whole test suite. Your tests seem fine. The cubrid failure is unrelated and cause by an error in the setup which I have not figured out yet.

@nineinchnick please add changelog and I'll merge PR.

@samdark done.

Thanks!

@nineinchnick great job!


IA-630 feat Add ImportGeoPkgDialog

Changes

create ImportGeoPkgDialog
add API request+hook
add messages and translations
update bluesquare-components to get new IconButton icon
remove intl error in config.js
light code cleanup

Important

The API will complain if the version is null. This should be changed backend side: a null version number should entail the creation of a new version (as discussed with @olethanh )

No front-end tests were written, so please test thoroughly try to break the feature

https://user-images.githubusercontent.com/38907762/123463673-166a5e80-d5ec-11eb-939f-5f777e9ff68e.mov

Only one thing, maybe disable the "use default version"  option if no default version on this data source

Update

Disable "use default option" when no default option exists
Fix bug with default option not being properly passed to Dialog
Updated dep to bluesquare-components
Backend changes will be moved to a separate issue

https://user-images.githubusercontent.com/38907762/123605176-d7125c80-d7fb-11eb-8bcf-c51483586d66.mov


Make more PPLib constructors/methods public

Making these class variables private prevents wiring functions that iterate over a trajectory. For instance, if you want to write a function that transforms a trajectory in the same way that transformStateForAlliance does, but with a different translation that does not require a coordinate system change.
https://github.com/mjansen4857/pathplanner/blob/c6ee3221c1b6e61522e5da74a8cad03e4b45668c/pathplannerlib/src/main/java/com/pathplanner/lib/PathPlannerTrajectory.java#L536-L537
and don't make this method protected:
https://github.com/mjansen4857/pathplanner/blob/c6ee3221c1b6e61522e5da74a8cad03e4b45668c/pathplannerlib/src/main/java/com/pathplanner/lib/PathPlannerTrajectory.java#L29-L42

I found this reference on CD where you say those two State values are "ornamental" but there's still the problem of the constructor being protected.
https://www.chiefdelphi.com/t/pathplanner-2023-beta/416548/206

Going to change this issue to encompass some other things that need to be made public

Adding the add events to a on the fly generated path use case to this issue.


show some difference in the popover's interface after using obsidian's pin command

The popover can be pinned to prevent it from auto closing, but it doesn't mean the popover is fixed, if I need to fix it, I have to use obsidian's pin command. The problem is sometimes I can't tell if the the popover is fixed or not, because even if I have used obsidian's pin command to fix it, there's no change in the popover's interface. So please show some change, like changing pin icon's color, to let user know the popover pane is fixed or not. Thanks.

@pjeby What I said "fix" doesn't mean fix the popover's position, it means if I open backlinks in the popover, it can be opened in another pane, not in the popover pane. Is it possible?
Thanks for your great plugin.

Unfortunately this is not a trivial thing; current versions of Obsidian have removed the code that used to show a pin icon on the view header, and Obsidian does not provide any style basis for knowing whether a pane is pinned.  So we'd have to duplicate the application logic for this sort of thing and figure out how to add it.  It's not likely to be something I'll have time for in the immediate future.
In the meantime, what I would recommend doing is that if you want things to open in a particular place, the easiest way to guarantee the location is to drag the link instead of clicking it.  If you want it to open in the current pane, drag it to the tab or view header, otherwise drag it to a different tab or view header, and it will open there.  This doesn't require you to pin or unpin anything.

Dragging the tink(like links in linked mentions) can open it, but it's only opened at the top of the linked file, not at the position of the link.
Fortunately, someone has just solved this issue. Maybe it can inspire you and add this new feature to next version.
https://forum-zh.obsidian.md/t/topic/38725/11?u=epe

const activeLeaf = app.workspace.activeLeaf;
const isPinned = activeLeaf?.getViewState()?.pinned;
if(!isPinned) {
    activeLeaf.setPinned(true);
    const hoverPinStyle = activeLeaf.containerEl.closest(".hover-popover")?.querySelector(".mod-pin-popover > svg")?.style;
     if(hoverPinStyle) hoverPinStyle.color = 'red';
} else {
    activeLeaf.setPinned(false);
    const hoverPinStyle = activeLeaf.containerEl.closest(".hover-popover")?.querySelector(".mod-pin-popover > svg")?.style;
     if(hoverPinStyle) hoverPinStyle.color = '';
}


stop octree decomposition by node size?

Hi,
I would like to find an octree representation with color coding of the octnodes (white outside of domain boundary, black is inside and grey is on the boundary). I think I will take the advice you gave on another thread and use trimesh to find whether an octnode not located on the boundary (i.e. numPolys==0) is inside or outside the mesh.
I would also like to stop the octree decomposition based on min octnode size instead of the number of Polys/triangles it contains (200 by default). I suppose I could modify line 463 in COctree.cpp :
if (node.branches[i].numPolys() < node.MAX_OCTNODE_OBJECTS)
and replace it by smthg like :
if (node.size[i] < node.MAX_SIZE) ?
But if MAX_SIZE changes from one run to the next, can i just change it in the code and run it or do I have to reinstall/recompile smthg (im not familiar with the Cython way) ?
Thanks!

Nevermind I figured this out!


HTTP status code 500

Sorry to be making a new issue here but, there seems to be a problem!

Alright try again, this time issue should reeealy be fixed.

Seems all good now.
Thanks for the help!


Implement STRING commands

getset
mget
strlen
setrange

Hi @yampml please resolve conflict and add documents for the implemented commands (just like in #52)

@yampml Please move logics from command class to db class, handle lock properly


gold per-file requirements hurt sustainability and deter contributors, why "MUST"?

Having boilerplate/frontmatter in every file is an annoyance to contributors. It's an additional CI check that needs to be run, it's additional friction for people creating new files (but especially newcomers), and it does nothing to increase the security of the project itself. It certainly would make auditing easier for folks who depend on projects that have copy-pasted files from my project - but that's not related to my project's security.
At the very least, I think these should be downgraded to "SHOULD" - but my personal preference would be to invert them and say that one should actively NOT do this. Duplicating information that's already available in the right place at the root of the repo is just noise.

I believe you mean the gold criteria [copyright_per_file] and [license_per_file].
This is a proposed change (reduction) in requirements, so we need to hear from others. If anyone has comments for or against this proposed change, please say so in this issue!
For simplicity, here is more information about each criterion.
Criterion copyright_per_file:

Requirement: The project MUST include a copyright statement in each source file, identifying the copyright holder (e.g., the [project name] contributors). {Met justification} [copyright_per_file]
Details: This MAY be done by including the following inside a comment near the beginning of each file: "Copyright the [project name] contributors.". See "Copyright Notices in Open Source Software Projects" by Steve Winslow.
Rationale: This isn't legally required in most jurisdictions, per the Berne Convention. For example, copyright notices have not been required in the US since 1979. On the other hand, this is not hard to add. Ben Balter's "Copyright notices for open source projects" provides some good arguments for why it should be included: "First, someone may want to use your work in ways not allowed by your license; notices help them determine who to ask for permission. Explicit notices can help you prove that you and your collaborators really are the copyright holders. They can serve to put a potential infringer on notice by providing an informal sniff test to counter the 'Oh yeah, well I didn’t know it was copyrighted' defense. For some users the copyright notice may suggest higher quality, as they expect that good software will include a notice... Git can track these things, but people may receive software outside of git or where the git history has not been retained." In addition, we have been informed by the Linux Foundation's SPDX community that having this information is extremely valuable for relicensing and for checking to determine if a copyrighted work is derived from another. While version control systems do track versioning within a project, when files are copied between projects this information is often lost. Having the copyright notice information helps those researching sources, e.g., if they wish to try to relicense something.

Criterion license_per_file:

Requirement: The project MUST include a license statement in each source file. This MAY be done by including the following inside a comment near the beginning of each file: SPDX-License-Identifier: [SPDX license expression for project]. {Met justification} [license_per_file]
Details:  This MAY also be done by including a statement in natural language identifying the license. The project MAY also include a stable URL pointing to the license text, or the full license text. Note that the criterion license_location requires the project license be in a standard location. See this SPDX tutorial for more information about SPDX license expressions. Note the relationship with copyright_per_file, whose content would typically precede the license information.
Rationale: Files are sometimes individually copied from one project into another. Per-file license information increases the likelihood that the original license will be honored. SPDX provides a simple standard way to identify common licenses, without having to embed the full license text in each file; since this makes the criterion easier to do, we specifically mention it. Technically, the text after "SPDX-License-Identifier" is a SPDX license expression, not an identifier, but the tag "SPDX-License-Identifier" is what is used for backwards-compatibility.

I would be in favor of changing this from MUST to SHOULD, but perhaps we could compromise somewhat and leave it as 'MUST' if a particular source file was "sourced" from another project as you mention in the rationale (or add an appropriate one if not present for that file). I think that would especially be important  when the license type of that particular "borrowed" source file is different than the license type that you are releasing your project under. For instance, a project releasing under LGPL 2.1 license but pulling in a Java class that was licensed under (say) Apache 2 license. During all the code reviews that I've done in the past 10 years, I certainly have seen teams "borrow" something like the source code for org.apache.commons.lang3.StringUtils and pull that directly into their repo rather than including a dependency for Apache Commons Lang 3.
The disadvantage of copyrighting every source file is when you need to change it because the company or organization name changes, it becomes tedious to update it everywhere. I'm somewhat facing that now, because for OWASP ESAPI, most (if not all) of our Java source files have a copyright notice for "Open Web Application Security Project" and then OWASP had to go and change their name to "Open Worldwide Application Security Project".  More of an annoyance, but it still illustrates the point.

That makes total sense for vendored code, it's just exceedingly rare to ever do that in the ecosystems I participate in.

I always thought of this requirement as a way to prove to everyone that the provinance is in order. We know the copyright and license status for every individual file. And I think a gold project should live up to that.
But complying with REUSE does allow for also providing the same info out of file when necessary and as long as that info exists, I think it's fine. That is how we in curl comply with this.

I've seen too many files copied piecemeal from one project to another. IMHO, NOT having the info there is asking for trouble.
I'd even go so far as to suggest making it a SHOULD for SILVER, but leaving it a MUST for GOLD.

Trouble for who? The point of this program is to make the project itself more secure.

If we're going to require Copyright notice on every source file, can we at least make an exclusion for configuration files? That gets confusing because they often get heavily edited by library users.

@kwwall - The requirements are only for "source files". Usually configuration files aren't source files, so typical configuration files are already excluded from this requirement.

With multiple files being copied from project to project as a common development pattern,  the license information is key to retain to ease analysis.   And if there are problems with a license for a file contents being included with other files, only the copyright holder can change the license, so keeping this original metadata with the file, helps de-risk issues with using the software.
As vulnerabilities occur at the file level, having this information handy, helps with notification to the copyright holder, who may have used the contents of this file, in other locations as well.
Agree with David that configuration files and other generated evidence, do not typically have copyright asserted on the contents.

In which ecosystems is this a common and "non-discouraged" pattern?

Agree with David that configuration files and other generated evidence, do not typically have copyright asserted on the contents.

A minor nit: The gold badge currently only requires per-file license statements for source files. Configuration files are often not generated evidence, but since they also aren't normally source files, there's no gold requirement for per-file license statements in typical configuration files (unless they're also source files). I am NOT a lawyer, but my understanding is that it's often pointless to try to claim copyright on configuration files. Copyright law only covers expression. This makes claiming copyright over configuration files often dubious (depending on the circumstance). See this discussion: https://groups.drupal.org/node/17555. No one here is suggesting that license statements be required in every configuration file, but I thought it'd be worth clarifying that there are good reasons for that. You can do it if you want to of course :-).

Configuration file vs source file can get a bit fuzzy at times when it concerns the whole "infrastructure as code" paradigm, but as long as the gold badge standard doesn't get too draconian and leave those choices to the development teams, I think it will work out fine.


Improve error reporting for classloading issues

We noticed that the community build was failing for some projects due to
some class loading issues. My initial approach for detecting the errors
didn't always work because the test framework might wrap the underlying
exception. To fix that, I add the causes to the list of throwables to
scan for class loading related exceptions. I also added
ClassNotFoundException to the list of types to check for. I additionally
added more context to the error message so that it is more clear to the
user what specifically went wrong. The error message is intended to
provide examples that the user can actually paste into the console.
There is also a lot of manual line wrapping that could be improved by
defining paragraphs and then splitting on the jline terminal width. That
could be a useful internal helper function to improve our log messages
in general.
The underlying issue could be addressed by allowing the user to specify
libraries that get excluded from the dependency classpath for layering
purposes. I'm not sure the best way to do that yet and adding that
feature wouldn't fix any existing builds so I think that would be better
handled in 1.4.0.

[x] I've read the CONTRIBUTING guidelines

I tested the circe build with this and got the following result
ethanatkins@Ethans-MacBook-ProZ:~/work/oss/sbt/community/circe$ java -jar ~/work/bin/sbt-launch.jar -Dsbt.supershell=never -Dsbt.version=1.3.0-meta-21 "scodecJVM/testOnly io.circe.scodec.ScodecSuite"
Getting org.scala-sbt sbt 1.3.0-meta-21 ...
:: retrieving :: org.scala-sbt#boot-app
        confs: [default]
        80 artifacts copied, 0 already retrieved (29707kB/240ms)
[info] Loading settings for project global-plugins from idea.sbt,global.sbt ...
[info] Loading global plugins from /Users/ethanatkins/.sbt/1.0/plugins
[info] Loading settings for project circe-build-build from plugins.sbt ...
[info] Loading project definition from /Users/ethanatkins/work/oss/sbt/community/circe/project/project
[info] Loading settings for project circe-build from plugins.sbt ...
[info] Loading project definition from /Users/ethanatkins/work/oss/sbt/community/circe/project
[info] Compiling 1 Scala source to /Users/ethanatkins/work/oss/sbt/community/circe/project/target/scala-2.12/sbt-1.0/classes ...
[info] Done compiling.
WARNING: An illegal reflective access operation has occurred
WARNING: Illegal reflective access by com.google.protobuf.UnsafeUtil (file:/Users/ethanatkins/.sbt/boot/scala-2.12.8/org.scala-sbt/sbt/1.3.0-meta-21/protobuf-java-3.3.1.jar) to field java.nio.Buffer.address
WARNING: Please consider reporting this to the maintainers of com.google.protobuf.UnsafeUtil
WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations
WARNING: All illegal access operations will be denied in a future release
[info] Loading settings for project circe from version.sbt,build.sbt ...
[info] Resolving key references (27404 settings) ...
[info] Set current project to circe (in build file:/Users/ethanatkins/work/oss/sbt/community/circe/)
[info] ScodecSuite:
[info] Codec[BitVector]
[info] - should obey codec.consistency with accumulating
[info] - should obey codec.decoder serializability *** FAILED ***
[info]   ClassNotFoundException was thrown during property evaluation.
[info]     Message: io.circe.Decoder$$anon$15
[info]     Occurred when passed generated values (
[info]
[info]     )
[info] - should obey codec.encoder serializability *** FAILED ***
[info]   ClassNotFoundException was thrown during property evaluation.
[info]     Message: io.circe.ObjectEncoder$$anon$3
[info]     Occurred when passed generated values (
[info]
[info]     )
[info] - should obey codec.roundTrip
[info] Codec[ByteVector]
[info] - should obey codec.consistency with accumulating
[info] - should obey codec.decoder serializability *** FAILED ***
[info]   ClassNotFoundException was thrown during property evaluation.
[info]     Message: io.circe.Decoder$$anon$12
[info]     Occurred when passed generated values (
[info]
[info]     )
[info] - should obey codec.encoder serializability *** FAILED ***
[info]   ClassNotFoundException was thrown during property evaluation.
[info]     Message: io.circe.Encoder$$anon$3
[info]     Occurred when passed generated values (
[info]
[info]     )
[info] - should obey codec.roundTrip
[info] Codec[ByteVector]
[info] - should return failure for Json String
[info] Codec[ByteVector]
[info] - should return failure in case input is an incomplete object
[info] Codec[ByteVector]
[info] - should return empty BitVector in case contains only non-zero header
[error] Test suite io.circe.scodec.ScodecSuite failed with java.lang.ClassNotFoundException: io.circe.Decoder$$anon$15.
[error] This may be due to the ClassLoaderLayeringStrategy (TestDependencies) used by your task.
[error] To improve performance and reduce memory, sbt attempts to cache the class loaders used to load the project dependencies.
[error] The project class files are loaded in a separate class loader that is created for each test run.
[error] The test class loader accesses the project dependency classes using the cached project dependency classloader.
[error] With this approach, class loading may fail under the following conditions:
[error]
[error]  * Dependencies use reflection to access classes in your project's classpath.
[error]    Java serialization/deserialization may cause this.
[error]  * An open package is accessed across layers. If the project's classes access or extend
[error]    jvm package private classes defined in a project dependency, it may cause an IllegalAccessError
[error]    because the jvm enforces package private at the classloader level.
[error]
[error] These issues, along with others that were not enumerated above, may be resolved by changing the class loader layering strategy.
[error] The Flat and ScalaInstance strategies bundle the full project classpath in the same class loader.
[error] To use one of these strategies, set the  ClassLoaderLayeringStrategy key
[error] in your configuration, for example:
[error]
[error] set scodecJVM / Test / classLoaderLayeringStrategy := ClassLoaderLayeringStrategy.ScalaInstance
[error] set scodecJVM / Test / classLoaderLayeringStrategy := ClassLoaderLayeringStrategy.Flat
[error]
[error] See ClassLoaderLayeringStrategy.scala for the full list of options.
[info] ScalaTest
[info] Run completed in 1 second, 829 milliseconds.
[info] Total number of tests run: 11
[info] Suites: completed 1, aborted 0
[info] Tests: succeeded 7, failed 4, canceled 0, ignored 0, pending 0
[info] *** 4 TESTS FAILED ***
[error] Failed: Total 11, Failed 4, Errors 0, Passed 7
[error] Failed tests:
[error]         io.circe.scodec.ScodecSuite
[error] (scodecJVM / Test / testOnly) sbt.TestsFailedException: Tests unsuccessful
[error] Total time: 7 s, completed Apr 3, 2019, 11:01:36 AM


How to reach controller from outside network

Hey man, it's me again.
This is not related to your repo directly - I just can't find the answer anywhere else:
What IP do I call to reach the controller from outside the LAN? For example, if my hotspot script is on Amazon AWS and the controller is behind an Edge Router, how would I determine the right IP to call to authorize the device on the controller?
You're my only hope!

Use the public IP address of the ER. If the IP address is dynamic I suggest you set up some dynamic dns service such as http://dyn.com/dns/, then refer to public domain name.

This does assume that port forwarding rules are in place to request to port 8443 to the internal IP address of the controller.

Excellent, thanks man! Was having connection problems in many locations and I wanted to make sure that the controller would be accessible at all in theory - and that I wasn't trying something impossible.

You're welcome.


O1 models not supported !

Which API Provider are you using?
OpenAI
Which Model are you using?
o1-preview and o1-mini
What happened?

O1 models don't accept system prompts. This should be a very easy fix. Also they don't accept streaming either.
Steps to reproduce
1 - Choose any o1 model.
2 - Send anything using that mode.
Relevant API REQUEST output
No response
Additional context
No response

Fixed in v2.0.8, thank you for reporting

No it still does not work. At least not when using OpenAi as the API provider.


Webserviceexport

add a webservices export (REST) function for fhir resource exporter

Thank you for the pull request, but it is being closed due to conflicts and inactivity.


Anomaly in Quetiapine Measure

The text says the CCG is prescribing better than the median - if you look on graph though it is prescribing worse than the median.

The measure is here
I think the anomaly is being driven by high proportion of branded generics.

It could be due to the disparity in price between when the measure was created and now, due to the huge NCSO hike of standard-release and the slow reduction since.
We have a choice in what to do with this measure:

Withdraw/retire it (based on the fact that the cost savings are no longer there), and possibly resurrect if it becomes cheap again
Make it a non-cost saving measure

My view would be to retire it for now - there's no real clinical benefit to giving more tablets a day, but when the price difference was 50 fold, it did make sense.  Thoughts @brianmackenna ?

As discussed - agree withdraw.
We should keep it on hand to resurrect, as the price seems to be correcting
Our mental health dashboard will only have two measures, will need to keep a look out for good measures.

Measure retired


那位大神弄个iOS 版Kcptun & 出搬瓦工vps 联通免流教程？？？

Before firing issue, make sure you figured out the following common questions.
PLEASE DO SEARCH FIRST.

Check your -key xxx for at least 3 times, MAKE SURE both sides share the same secret.
-nocomp, -datashard, -parityshard,  -key, -crypt must be the same on both side.
Did you correctly set the -target on the server side?
MAKE SURE telnet target port on your server successful(don't ask me why couldn't).
Does your firewall allows UDP communications? (including your ISP Cable-Modem)
Are you using the same version for both client & server
Are you using the latest release?
Which OS do you use?
Which end for this issue related to, client or server?

无iOS

期待ios版本


Users controller

Coverage remained the same at 100.0% when pulling 365886cfb015c4b0ed1210e05fed5d52082b3b6d on users-controller into a2bb3bcedbeb7c4ad96b9aaa32bd5951cd550cfc on rails.


Add seeds

Added seeds for different users (all people working on the project), and two battles, the first of which is won.

While far from being a requirement, I'd be interested in seeing a more "complete" battle, with a few nesting comment threads - it can help demonstrate the intended functionality when the app is first spun up, as well as give us uniform data to work around while styling the front-end.  Don't feel obligated to tackle that unless it sounds fun to you - thanks for knocking this out in any case!
Will gladly merge after we revisit the email addresses in seeds.rb :beers:


button text in develop branch currently being cut off

this button component:
                        {
                          "style": {
                            "align": "left",
                            "color": "#ffffff",
                            "corner_radius": "2",
                            "background": "#3f51b5",
                            "font": "HelveticaNeue",
                            "height": "45",
                            "padding": "20",
                            "size": "22"
                          },
                          "type": "button",
                          "text": "  Listen [English]  "
                        }
                      ]
                    },

produces the following:

That's because the height is fixed at 45, and since the padding is 20, which means you're left with 45-20-20 = 5, so the label gets cut off.
This was an intended change to make the text button be more consistent with image buttons. It used to be unclear what "height" meant for image buttons in the previous versions. It could be the image size, or it could be the size of the clickable region. With the recent update, it's been fixed to "clickable region" http://docs.jasonette.com/components/#button and as a result it was much simpler to go this way (padding is inside the height region) instead of the CSS model (where padding is outside of the "height" area by default but can also be inside the height region if you use border-sizing: border-box)
Sorry about the confusion. I will try to document these things more in the future.
Anyway, to make sure this doesn't break, try either setting a lower padding or setting a smaller font size. You could also increase the height. Hope this makes sense.

makes sense, thanks.


Outdated cask: tg-pro

Outdated cask: tg-pro.
Info:

version: 2.9.5.
appcast url: https://www.tunabellysoftware.com/resources/sparkle/tgpro/profileInfo.php.

Full appcast:
<?xml version="1.0" encoding="utf-8"?>
<rss xmlns:sparkle="http://www.andymatuschak.org/xml-namespaces/sparkle" xmlns:dc="http://purl.org/dc/elements/1.1/" version="2.0">
   <channel>
  <title>TG Pro 2.9.6</title>
  <link>http://tunabelly.com/resources/sparkle/tgpro.xml</link>
  <description>Update to 2.9.6</description>
  <language>en</language>
     <item>
        <title>Version 2.9.6</title>
			 <description><![CDATA[

Version 2.9.6 Changes:

[New] Added feature to override the system to lower fan speeds. This new feature can be turned on/off per fan.

[New] Added feature to easily copy all Auto Boost settings from one power source to the other.

[New] Improved overall reliability of fan control.

[New] Improved CPU usage.

[New] Improved sensor naming for some Macs.

[Fixed] Issue where the previous manual fan control setting wouldn't be restored on app startup.

[Fixed] Issue with menu bar icon overlapping the text.

[Fixed] Issue where Auto Boost might not come on when expected.

[Fixed] Issue where some of the menu bar preference checkboxes were slow to update when clicked.

Version 2.9.5 Changes:

[Fixed] Auto Boost not working.

Version 2.9.4 Changes:

[Fixed] Issue with manual fan control settings not persisting across app re-launches.

[Fixed] Issue where switching from manual to Auto Boost would sometimes keep the manual setting.

[Fixed] Issue with text including separators not appearing in the menu bar in dark mode.

[New] Improved app stability (translation: less crashes).

[New] Improved CPU usage (translation: less CPU usage).

Version 2.9.3 Changes:

[Fixed] Issue with fan control sometimes not working after updating.

[Fixed] Issue with menu bar text not displaying properly.

Version 2.9.2 Changes:

[Fixed] Issue with menu bar text not displaying properly in dark mode.

[Fixed] Improved sesnor naming for Early 2011 MacBookPro models.

Version 2.9.1 Changes:

[Fixed] Launching app on systems with less than OS X 10.10.

Version 2.9 Changes:

[New] Fan control is now simpler. There are three options - System, Manual and Auto Boost.

[New] Added option to use colors for the menu bar temperatures.

[New] Added ability to increase specific fans (instead of all) in Auto Boost rules.

[New] Added Highest and Highest CPU temperature options for use in both the menu bar & Auto Boost rules.

[New] Added tooltip for the menu bar icon with descriptions of what's being shown.

[New] Improved sensor naming for some Mac models.

[Fixed] Issue where nothing would update after registering.

[Fixed] Issue where "Invalid Fan" would show in the menu bar.

[Fixed] Issue where it was possible that some Auto Boost rules would not work correctly.

[Fixed] Issue where drive temperatures were not available in Auto Boost rules.

[Fixed] Issue where only one Auto Boost notification would ever appear.

[Fixed] Potential crash on app launch.

[Fixed] Potential crash when checking drive temperatures.

			]]>
			 </description>
        <pubDate>Thurs, 28 January 2016 21:00:00 -0500</pubDate>
			<enclosure url="https://tunabellysoftware.com/resources/TGPro_2_9_5.zip" sparkle:version="2.9.5" sparkle:dsaSignature="MCwCFFF4N93xWlQmp23uTfof673KnWovAhRlk2yrdniEblYWD+fytl7qQbZHLg==" length="5529778" type="application/octet-stream"/>
     </item>
   </channel>
</rss>

Closing in favour of #17823.


How to get user/groups imageUrl on the All Chat part?

If you want to access group's public data such as name, photo and ... you should use the public field on each topic.
As you see in the example, I'm printing the name of the group here using item.public['fn']:
print('Subscription[' + item.topic.toString() + ']: ' + item.public['fn'] + ' - Unread Messages:' + item.unread.toString());

This does not mean that the name of the group / chat is always going to be saved in that field.
The public field is  user defined and the structure of data is going to be defined by application. You might want to have an interface for that.
In the sandbox or web version, application is using fn key to store full name and photo to store the picture. Picture is stored as a string in public object (base64)


Fixed custom op test failing

Fixes #163. It looks like a module changed name in the new TensorFlow version or something. The documentation hasn't been updated yet either.
I don't think this ever broke anything in the regular code, since it's just regarding the gradient checks. However, this change may break the test in TensorFlow v0.9, though I didn't downgrade again to check this. Is this acceptable? Given the speed of development, I think it's reasonable to expect GPflow users to keep their TensorFlow version updated.

Current coverage is 99.27% (diff: 100%)

Merging #165 into master will not change coverage

@@             master       #165   diff @@
==========================================
  Files            20         20
  Lines          1524       1524
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
  Hits           1513       1513
  Misses           11         11
  Partials          0          0

Powered by Codecov. Last update 1076e47...ceb38be

@jameshensman what do you think of @markvdw 's question on backwards compatibility? I'm personally happy to break backwards compatibility with TensorFlow but we should probably change the version and setup.py .

Yep I have no problem requiring the latest and greatest tensorflow release.
We'll need to change

setup.py (to require 0.10.0)
RELEASE.md
_version.py
codeship

perhaps tag a new release on github also? I just tagged 0.2.1.
This should make it easier for people building on our stuff to upgrade at their own pace.

@jameshensman did you want the new version to be 0.3.0 or 0.2.2?

Perhaps, given the tri2vec ops, we should call this 0.3.0

@jameshensman version number incremented. It looks like someone has already changed the tf version on codeship.

I've already updated the codeship build rules, so I reckon this is ready to go once the tests pass.

Perhaps I could get my 'sphinx' branch in before 0.3.0? Minor changes only, but significant;y improved documentation. It also has a commit on there to improve setup.py, so that includes @markvdw 's binary block in an install.

@jameshensman: What does the adding the .so as an install improve?
Related: One thing that's bothering me, is that I think that if TensorFlow is updated, setup.py needs to be run again to recompile the extra ops. Is there a way to do this automatically? Not a huge issue, but it may confuse someone that GPflow stops working after an update of TensorFlow!

If you do python setup.py install right now on a clean install, it will compile the .so files, but won't copy them over with the python source, i.e. install will fail. My fixes will make sure python bundles the .sos with the .pys.
Yep, you're going to have to run python setup.py develop after updating tensorflow. I thin kthis is pretty normal for a project tracking a fast-paced project.

@jameshensman I think the sphinx branch now needs this one as it is failing. To break the circular dependency I suggest we merge this one with the necessary two lines from setup.py that you allude to. I've committed them just now.
I personally think that it might be best for sphinx to wait for the next version now. If not this branch will have to wait for me to review the sphinx branch. I'm not particularly fussed about waiting except we currently have #163 which is a bug that needs fixing.


Support Multiplatform

Most of the library code is common, exceptions are IO parts and Jupyter integration. We may support KMP (at least K/JS) for this library

There's probably too much JVM reflection going on for this to be easy, let alone viable :/

Any Updates ?

@icecreamparlor Nope. While it would be cool, there are just so many JVM dependencies in the project right now, so while in theory, it should be possible, it would be a huge undertaking.
If performance would be the reason to go multiplatform, I think we still have a lot to gain when the Vector API hits the JVM eventually, plus we have plans to convert our Lists to primitive arrays eventually https://github.com/Kotlin/dataframe/issues/30.
If, aside from performance, there are other needs for multiplatform support, I would be interested in seeing a proof of concept of (part of) the API, so we can then properly decide whether it would be worth the effort or not.

to support multiplatform, needed to switch to kotlinx.serialization - #312
It would be nice if the part with the parser was separated into a separate module

also appeared kotlinx-io - https://github.com/Kotlin/kotlinx-io

Doubts arose about multiplatform support in dataframe, because the library uses a lot of reflections.
I've looked into this a bit, most of the reflection we use is in common. Therefore, if there are problems, then in isolated cases
https://kotlinlang.org/api/latest/jvm/stdlib/kotlin.reflect/

If you look at implementation files like this:
https://github.com/Kotlin/dataframe/blob/master/core/src/main/kotlin/org/jetbrains/kotlinx/dataframe/impl/TypeUtils.kt you can see we use jvmErasure a lot all over the place. I'm not sure if there's a common alternative for that. This needs to be checked.

In fact, this is the only thing I noticed that is strongly tied to the platform.
In this case, for jvm everything will be the same, for native it will be possible to come up with a workaround, with wasmJs I’m not sure if it’s worth supporting at all

I took a closer look at multiplatform support and conducted some experiments with it. Initially, I made some erroneous conclusions.
Here are the issues I discovered:

Support for generated code and proper source configuration
DataFrame plugin - there is support for different targets in ksp.
Plugins working with code or kdoc - such as korro and docProcessor. In the case of korro, it theoretically will work, as it simply finds a function and processes the function body, in the case of common code there should be no problems. With docProcessor, I don't know, as the structure will change, surely changes will be needed for it too.
Jupyter - it's necessary to separate the logic related to notebooks and Jupyter and move it to the jvm part
kotlinpoet - it's multiplatform, but only supports the jvm target
Java types - the code uses java.time, BigDecimal, java.io, java.util, serializable. Some of this is solvable, for example, with support for kotlinx-datetime, kotlinx-io or okio. BigDecimal and its handling need to be moved to a jvm module. The rest needs further exploration.
csv, tsv, json - all our reading is jvm dependent
jdbv)
concurrent - using atomic should solve the problem
There were problems with calculating the types of receivers
Java reflection — there's a small amount of Java reflection. Perhaps it can be replaced by kotlin.reflect.jvm, which is also tied to the jvm)
Kotlin reflection — the code uses JVM reflection in many places. For example:

isAbstract
KVisibility
kotlin.reflect.jvm

jvmErasure
isAccessible
javaField

kotlin.reflect.full

isSubclassOf
isSubtypeOf
isSuperclassOf
withNullability
findAnnotation
hasAnnotation
memberProperties
Superclasses
allSuperclasses
createType
Superclasses
primaryConstructor

This is used in methods, for example: convert, update, join, aggregate, and others. But it's also used in TypeUtils, and methods from there are called when creating new columns, that is, practically with any operation. There's no simple replacement or implementation through expect/actual for the same jvmErasure in Kotlin/Native, so a full refactoring of this logic is required. In some cases, I assume the use of reflection is excessive, and in the case of type erasure, I see the following. The simplest way is to go through the data in Kotlin/Native and calculate the type, but this carries very large overheads. Another option is to calculate the type when the data comes from outside, that is, when creating a dataframe, keep it all the time and reuse it constantly, as it does not always happen now. When calculating a new type during operations with the dataframe, a resolver is necessary, and this will require implementing quite complex logic. Also, I assume that some problems with reflection will be solved with the help of a compiler plugin.
As a result, I do not see multiplatform support with Kotlin/Native (ios) as feasible in the near future, as it requires a lot of effort, which presumably could be solved by Kotlin itself in the future.
Multiplatform support only for JVM and Android seems like a more realistic task but will require:

project configuration
code refactoring, to separate logic. So that in the common module there would ideally be very limited but isolated code
support for tasks such as #312, #587 , support kotlinx-io

Reflekt can do a tiny piece of JVM reflection: finding classes/interfaces in the project, using IR. So finding which supertypes exist etc. should in theory be possible.


Use correct default prefix

When deploying the Azure Monitor Agent, it creates DCR (Data collection rule) and DCE (Data collection endpoint) objects in your Log Analytic workspace's resource group. Instead of "sql-bpa-" the correct default prefix naming is "sqlbpa-" for these objects.

@nhebbar2011
Can you review the proposed changes?
When the changes are ready for publication, add a #sign-off comment to signal that the PR is ready for the review team to merge.
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

#sign-off

Due to the upcoming Ignite conference, all merging and publishing is on hold until the morning of 11/15.
This PR is ready for merge on 11/15.
#label: "event-triaged-to-10AM"
#label: "missed-content-complete"


Create our own modulefile?

Right now, we are using . ./mfc.sh load to set the environment on a specific computer, though it strikes me that modulefiles are made to do exactly this. Does it somehow make more sense to have our own set of maintained module files that we can load in via module use MFC/toolchain/modulefiles/<computer name>, which will provide module load MFC as a viable command, auto-loading the correct modules, and setting environment variables and paths.
It is unclear to me that, if implemented, this would be any better or easier than what we currently have (other than being less "MFC idiosyncratic," but perhaps also less flexible since we are beholden to the capability of lmod). Wondering what you all think... @henryleberre?
Some codes have these built into the system config., e.g.:
[I]br011: /opt/packages $ module show openfoam
----------------------------------------------------------------------------------------------------
   /opt/modulefiles/production/openfoam/6.0:
----------------------------------------------------------------------------------------------------
whatis("openfoam/6.0.0 ")
conflict("openfoam")
setenv("FOAM_VERSION","6.0.0")
setenv("FOAM_DIR","OpenFOAM-6")
setenv("FOAM_INST_DIR","/opt/packages/openfoam/6.0.0/OpenFOAM-6")
help([[OpenFOAM 6.0.0
------------------------

Load the following module first
	openmpi/3.1.6-gcc8.3.1

]])

I wrote a small thesis and then realized that I misunderstood what you trying to achieve.. To summarize, if we wanted to module load mfc and enable users execute things like mfc run case.py -n 4, we would:
mfc() { cd "/path/to/system/mfc/clone" && ./mfc.sh $@ }

To actually address this issue, you make a very good point. We would expect users to:
module use  toolchain/modulefiles/<computer name>/
module load mfc/<cpu or gpu>

where toolchain/modulefiles/<computer name>/ is a directory. I see very little downside to moving to this.

I guess the downside is that the system would have to keep up with current MFC builds -- or we would have to not put MFC in the system's root path but the user's local dir.

closed due to inactivity


Provide documentation for String http_unescape() method

As title states. I found a bug ( #30409 ) while documenting this.

It would be good to group related changes in the same PR / commit (namely #30410), so that they can be reviewed and merged together.

Grouping with your comments from http_encode


Custom 404 pages do not work on the dev server

Describe the bug
Our custom 404 pages are not working on the dev server but they do seem to work if you build the app. This only happened after the upgrade to nextjs 13.5.4
To Reproduce
Steps to reproduce the behavior:

Run the bloom-frontend with yarn dev.
go to localhost:3000/123
See default Next js 404 page.
Exit dev server
Run yarn build
Run yarn start
go to localhost:3000/123
See Custom 404 page which is src/pages/404.tsx

Expected behavior
On the dev server, we should be able to see the custom 404 page.
Screenshots
Nextjs Default

Custom 404

Desktop (please complete the following information):

Macbook Pro 2021, Mac Os Monterey 12.2
Browser Chrome
Version 117.0.5938.132

is this issue still open?

I think this ticket was fixed in a recent upgrade so i am going to close. THanks for your interest @sriabhinay556 !


VSCode jupyter extension (on Insider) appears to take a long time to get saved after being used for a while. How to mitigate?

Discussed in https://github.com/microsoft/vscode-jupyter/discussions/15365

Originally posted by @shandou March 14, 2024:
In the past 1-2 months or so, I start to observe that jupyter notebooks in VSCode could run normally for a while, and then start to take a very long time to run a cell or get saved. This can be resolved by running "reload window", but notebook would also lose all the states. Has anyone run into similar problems and are there better ways to mitigate? Thank you!
The screen capture below is an example where this status box would display "saving..." for an unusually long time.

Also, I have observed that when I install jupyter extensions on GCP's vertex AI workbench instance (connected via remote ssh), it always seems to cause the instance to fail to start again once it was stopped, with health status reporting unhealthy JupyterLab API.
I have only observed this with VScode Insider. Currently don't yet know if stable release would behave differently. Thank you.


entropy and variance

should be new "reductions" on E[…]

still need entropy

(entropy needs to be a separate syntax node type that only takes a choice name as input!)


Added support for loading configurations from URLs

Added support for loading configurations from URLs along with necessary tests.

Current coverage is 93.76% (diff: 75.00%)

Merging #38 into v1.2 will decrease coverage by 0.01%

@@               v1.2        #38   diff @@
==========================================
  Files            63         63
  Lines          3713       3721     +8
  Methods           0          0
  Messages          0          0
  Branches        672        673     +1
==========================================
+ Hits           3482       3489     +7
- Misses          140        141     +1
  Partials         91         91

Powered by Codecov. Last update dd54b4b...93428c4

I like it! Thanks for the documented and tested code.

Always happy to contribute.
Do you have a date in mind for 1.2 release?

I will release 1.2 RC1 in November. The first release candidate, for which no bugs will be reported, will be published as final version 1.2.  So, I guess the final version 1.2 will be published in December or January.

Brilliant. Can't wait to update my project and make use of new features.


Ratify support OCI spec 1.1

What would you like to be added?
OCI spec 1.1 was released recently. This issue is for discussion Ratify supports of OCI spec 1.1, as a result, work items and release plan can be created.
Anything else you would like to add?
No response
Are you willing to submit PRs to contribute to this feature?

[ ] Yes, I am willing to implement it.

I have double checked that Ratify is using the correct oras-go function here. This function will perform a check to see if the target registry is referrers API enabled. If not, it will fallback to the tag schema.
Once oras-go 2.5.0 is released, dependabot will automatically send a PR for ratify to upgrade.


Part 1 of unified mux: subscription states

Split out subscription state out of xDS mux unification PR (https://github.com/envoyproxy/envoy/pull/15473). Made base subscription state class a template. Updated existing delta state tests to work with both legacy and new implementations.
Commit Message: xDS unified mux: subscription states
Additional Description:
Risk Level: low, the code is not being used atm
Testing: updated existing tests, added new ones
Docs Changes:
Release Notes:
Platform Specific Features:
[Optional Runtime guard:]
[Optional Fixes #Issue]
[Optional Deprecated:]
[Optional API Considerations:]

Ping @adisuissa. I followed your suggestion re: how to split the original PR (https://github.com/envoyproxy/envoy/pull/15473).

/assign @adisuissa

/cc @htuch
I think the PR looks good.

responded to feedback

*increased test coverage

Not sure why the coverage for source/common/config/unified_mux is reported so low; I have it at 96.5% locally.

If you check https://github.com/envoyproxy/envoy/blob/main/source/docs/coverage.md it should show you what's missing
there are some quirks to coverage you may be hitting?

Yan: can you cover code reviews until @htuch gets back?

@adisuissa: discovered an issue with how I was handling ttl resources in SotW; fixed now. Also expanded test coverage.

ping @yanavlasov

@htuch: any chance you could take a look?

merged changes from main
responded to feedback


Bump dependencies and improve test

Added test containers to spin up rabbitmq when running tests

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

closes https://github.com/zio/zio-amqp/pull/312

done in https://github.com/zio/zio-amqp/pull/362


List Widget with single child object displays "List[map]........" string in CMS UI

- Do you want to request a feature or report a bug?
Bug
- What is the current behavior?
List widget with a single object as its array element outputs "List[map]........"  string in the ui like shown here https://nupic.co/image/6T638
- If the current behavior is a bug, please provide the steps to reproduce.
Please use this configuration to reproduce the bug
- name: "footer"
  label: "Footer Links"
  file: "_data/footer.yml"
  fields:
   - name: "footer"
     label: "Footer Links"
     widget: list
     disableAdd: true
     fields:
      - name: "links-col-1"
        label: "Footer Links Column 1"
        widget: list
        fields:
         - {label: "Title", name: "name", widget: "string" }
         - {label: "URL", name: "href", widget: "string" }
      - name: "links-col-2"
        label: "Footer Links Column 2"
        widget: list
        fields:
         - {label: "Title", name: "name", widget: "string" }
         - {label: "URL", name: "href", widget: "string" }

Here is the data structure that gets created from the above code
{   "footer": [     {       "links-col-1": [         {           "href": "/activeico.html",           "name": "Active ICO"         },         {           "href": "/upcomingico.html",           "name": "Upcoming ICO"         },         {           "href": "/endedico.html",           "name": "Ended ICO"         }       ],       "links-col-2": [         {           "href": "/whitelist.html",           "name": "Whitelist"         },         {           "href": "/preico.html",           "name": "Pre ICO"         },         {           "href": "Advertising",           "name": "/publishico.html"         }       ]     }   ] }
- What is the expected behavior?

- Please mention your versions where applicable.

Netlify CMS version: 1.5
Browser version:

Node.JS version:
Operating System:
- Please link or paste your config.yml below if applicable.

The core issue here is that we need a smarter approach to providing display titles for list widget items. We currently look for fields with a handful names, or else fallback to stringifying the first field, which results in the above. At a minimum, we should provide a generic fallback, perhaps based on the list widget label itself, if none of the list widget fields are strings.

Any updates on this issue?

For anyone looking into this: see @alberto56's advice, or use the summary on the field. Closing as not planned.


Allowing localstorage on a per model basis

Hi Jerome.
I needed one model to be synced to localStorage and the rest to be via REST.
Overriding Backbone.sync globally prevents this. Changing the name of the function and then choosing how you want to sync seems to be a better approach.
Eg. For one model:
MyModel.sync = Backbone.localSync
or for all models:
Backbone.sync = Backbone.localSync
Stef

@jeromegn giving this a bump. What if you added an option "cache" that if set to true used localstorage, and if set to false used regular Backbone.sync?
So, for example, you could first try fetch({cache:True}), and if that yields no results, do a plain fetch().

I've got the same implementation problems as above. I need to update via a REST api, but need to cache locally in case the device is offline.


provisioning failed because vizier with specified UID is already active

Describe the bug
An aborted install attempt has left installation impossible.
A clear and concise description of what the bug is.
To Reproduce
Clean up as best as I can
px delete
kubectl delete crd catalogsources.operators.coreos.com clusterserviceversions.operators.coreos.com installplans.operators.coreos.com operatorconditions.operators.coreos.com operatorgroups.operators.coreos.com operators.operators.coreos.com subscriptions.operators.coreos.com viziers.px.dev
k delete ns olm

Reinstall
➜ px deploy
Pixie CLI

Running Cluster Checks:
 ✔    Kernel version > 4.14.0
 ✔    Cluster type is supported
 ✔    K8s version > 1.16.0
 ✔    Kubectl > 1.10.0 is present
 ✔    User can create namespace
 ✕    Cluster type is in list of known supported types  ERR: Cluster type is not in list of known supported cluster types. Please see: https://docs.px.dev/installing-pixie/requirements/
Some cluster checks failed. Pixie may not work properly on your cluster. Continue with deploy? (y/n) [y] :
Installing Vizier version: 0.12.2
Generating YAMLs for Pixie
Deploying Pixie to the following cluster: tpkube
Is the cluster correct? (y/n) [y] :
Found 36 nodes
 ✔    Installing OLM CRDs
 ✔    Deploying OLM
 ✔    Deploying Pixie OLM Namespace
 ✔    Installing Vizier CRD
 ✔    Deploying OLM Catalog
 ✔    Deploying OLM Subscription
 ✔    Creating namespace
 ✔    Deploying Vizier
 ⠸    Waiting for Cloud Connector to come online
FATA[0396] Timed out waiting for cluster ID assignment

It took the operator a long time to get ready. Eventually, the pods were all running in px-operator. When the operator is ready it tries to initialize pixie in the pl namespace. This fails. The pod status is
➜ k get po
NAME                                      READY   STATUS             RESTARTS        AGE
kelvin-699b4c9b9b-blkdd                   0/1     Init:0/2           0               4m19s
pl-nats-0                                 1/1     Running            0               4m34s
vizier-cloud-connector-6f9fc774d4-mvxgc   0/1     CrashLoopBackOff   5 (30s ago)     4m19s
vizier-metadata-0                         1/1     Running            2 (3m46s ago)   4m19s
vizier-pem-26gz9                          0/1     Init:0/1           0               4m24s
vizier-pem-2ncsl                          0/1     Init:0/1           0               4m24s
vizier-pem-4s2mw                          0/1     Init:0/1           0               4m24s
...
vizier-pem-wfq2h                          0/1     Init:0/1           0               4m24s
vizier-pem-wmmwb                          0/1     Pending            0               4m24s
vizier-pem-zx8vh                          0/1     Init:0/1           0               4m24s
vizier-query-broker-55967b7dc4-q674f      0/1     Init:0/2           0               4m19s

The last log line before vizier-cloud-connector restarts is
➜ k logs -p vizier-cloud-connector-6f9fc774d4-mvxgc|tail -n1
time="2022-09-13T21:21:45Z" level=fatal msg="Failed to register vizier deployment. If deploying via Helm or Manifest, please check your deployment key. Otherwise, ensure you have deployed with an authorized account." error="rpc error: code = ResourceExhausted desc = provisioning failed because vizier with specified UID is already active"

Expected behavior
I expect px deploy to complete successfully.
Logs
Please attach the logs by running the following command:
❯ px collect-logs
Pixie CLI
WARN[0001] Failed to log pod: kelvin-699b4c9b9b-blkdd    error="container \"app\" in pod \"kelvin-699b4c9b9b-blkdd\" is waiting to start: PodInitializing"
WARN[0001] Failed to log pod: vizier-pem-26gz9           error="container \"pem\" in pod \"vizier-pem-26gz9\" is waiting to start: PodInitializing"
WARN[0001] Failed to log pod: vizier-pem-2ncsl           error="container \"pem\" in pod \"vizier-pem-2ncsl\" is waiting to start: PodInitializing"
WARN[0001] Failed to log pod: vizier-pem-4s2mw           error="container \"pem\" in pod \"vizier-pem-4s2mw\" is waiting to start: PodInitializing"
WARN[0002] Failed to log pod: vizier-pem-59hss           error="container \"pem\" in pod \"vizier-pem-59hss\" is waiting to start: PodInitializing"
WARN[0002] Failed to log pod: vizier-pem-5hwrm           error="container \"pem\" in pod \"vizier-pem-5hwrm\" is waiting to start: PodInitializing"
WARN[0003] Failed to log pod: vizier-pem-622vz           error="container \"pem\" in pod \"vizier-pem-622vz\" is waiting to start: PodInitializing"
WARN[0003] Failed to log pod: vizier-pem-6vjc6           error="container \"pem\" in pod \"vizier-pem-6vjc6\" is waiting to start: PodInitializing"
WARN[0003] Failed to log pod: vizier-pem-6xgqn           error="container \"pem\" in pod \"vizier-pem-6xgqn\" is waiting to start: PodInitializing"
WARN[0004] Failed to log pod: vizier-pem-74k54           error="container \"pem\" in pod \"vizier-pem-74k54\" is waiting to start: PodInitializing"
WARN[0004] Failed to log pod: vizier-pem-7fb7m           error="container \"pem\" in pod \"vizier-pem-7fb7m\" is waiting to start: PodInitializing"
WARN[0005] Failed to log pod: vizier-pem-7vq85           error="container \"pem\" in pod \"vizier-pem-7vq85\" is waiting to start: PodInitializing"
WARN[0005] Failed to log pod: vizier-pem-7xnsh           error="container \"pem\" in pod \"vizier-pem-7xnsh\" is waiting to start: PodInitializing"
WARN[0005] Failed to log pod: vizier-pem-8mfjk           error="container \"pem\" in pod \"vizier-pem-8mfjk\" is waiting to start: PodInitializing"
WARN[0006] Failed to log pod: vizier-pem-9596k           error="container \"pem\" in pod \"vizier-pem-9596k\" is waiting to start: PodInitializing"
WARN[0006] Failed to log pod: vizier-pem-9rzd6           error="container \"pem\" in pod \"vizier-pem-9rzd6\" is waiting to start: PodInitializing"
WARN[0007] Failed to log pod: vizier-pem-c2wwz           error="container \"pem\" in pod \"vizier-pem-c2wwz\" is waiting to start: PodInitializing"
WARN[0007] Failed to log pod: vizier-pem-dlt95           error="container \"pem\" in pod \"vizier-pem-dlt95\" is waiting to start: PodInitializing"
WARN[0007] Failed to log pod: vizier-pem-f247b           error="container \"pem\" in pod \"vizier-pem-f247b\" is waiting to start: PodInitializing"
WARN[0008] Failed to log pod: vizier-pem-fcfhd           error="container \"pem\" in pod \"vizier-pem-fcfhd\" is waiting to start: PodInitializing"
WARN[0008] Failed to log pod: vizier-pem-fchg8           error="container \"pem\" in pod \"vizier-pem-fchg8\" is waiting to start: PodInitializing"
WARN[0009] Failed to log pod: vizier-pem-gw52n           error="container \"pem\" in pod \"vizier-pem-gw52n\" is waiting to start: PodInitializing"
WARN[0009] Failed to log pod: vizier-pem-h6hbd           error="container \"pem\" in pod \"vizier-pem-h6hbd\" is waiting to start: PodInitializing"
WARN[0009] Failed to log pod: vizier-pem-hk982           error="container \"pem\" in pod \"vizier-pem-hk982\" is waiting to start: PodInitializing"
WARN[0010] Failed to log pod: vizier-pem-kvn9l           error="container \"pem\" in pod \"vizier-pem-kvn9l\" is waiting to start: PodInitializing"
WARN[0010] Failed to log pod: vizier-pem-m54fw           error="container \"pem\" in pod \"vizier-pem-m54fw\" is waiting to start: PodInitializing"
WARN[0011] Failed to log pod: vizier-pem-mbtdd           error="container \"pem\" in pod \"vizier-pem-mbtdd\" is waiting to start: PodInitializing"
WARN[0011] Failed to log pod: vizier-pem-mfh89           error="container \"pem\" in pod \"vizier-pem-mfh89\" is waiting to start: PodInitializing"
WARN[0011] Failed to log pod: vizier-pem-mng6b           error="container \"pem\" in pod \"vizier-pem-mng6b\" is waiting to start: PodInitializing"
WARN[0012] Failed to log pod: vizier-pem-nvmfz           error="container \"pem\" in pod \"vizier-pem-nvmfz\" is waiting to start: PodInitializing"
WARN[0012] Failed to log pod: vizier-pem-qgflt           error="container \"pem\" in pod \"vizier-pem-qgflt\" is waiting to start: PodInitializing"
WARN[0013] Failed to log pod: vizier-pem-qqq6w           error="container \"pem\" in pod \"vizier-pem-qqq6w\" is waiting to start: PodInitializing"
WARN[0013] Failed to log pod: vizier-pem-rqrl6           error="container \"pem\" in pod \"vizier-pem-rqrl6\" is waiting to start: PodInitializing"
WARN[0013] Failed to log pod: vizier-pem-rvlfh           error="container \"pem\" in pod \"vizier-pem-rvlfh\" is waiting to start: PodInitializing"
WARN[0014] Failed to log pod: vizier-pem-s4xtr           error="container \"pem\" in pod \"vizier-pem-s4xtr\" is waiting to start: PodInitializing"
WARN[0014] Failed to log pod: vizier-pem-sps4m           error="container \"pem\" in pod \"vizier-pem-sps4m\" is waiting to start: PodInitializing"
WARN[0015] Failed to log pod: vizier-pem-t4c9x           error="container \"pem\" in pod \"vizier-pem-t4c9x\" is waiting to start: PodInitializing"
WARN[0015] Failed to log pod: vizier-pem-t642c           error="container \"pem\" in pod \"vizier-pem-t642c\" is waiting to start: PodInitializing"
WARN[0015] Failed to log pod: vizier-pem-thrh5           error="container \"pem\" in pod \"vizier-pem-thrh5\" is waiting to start: PodInitializing"
WARN[0016] Failed to log pod: vizier-pem-vdpsb           error="container \"pem\" in pod \"vizier-pem-vdpsb\" is waiting to start: PodInitializing"
WARN[0016] Failed to log pod: vizier-pem-wfq2h           error="container \"pem\" in pod \"vizier-pem-wfq2h\" is waiting to start: PodInitializing"
WARN[0017] Failed to log pod: vizier-pem-wmmwb           error="container \"pem\" in pod \"vizier-pem-wmmwb\" is waiting to start: PodInitializing"
WARN[0017] Failed to log pod: vizier-pem-zx8vh           error="container \"pem\" in pod \"vizier-pem-zx8vh\" is waiting to start: PodInitializing"
WARN[0017] Failed to log pod: vizier-query-broker-55967b7dc4-q674f  error="container \"app\" in pod \"vizier-query-broker-55967b7dc4-q674f\" is waiting to start: PodInitializing"
Logs written to pixie_logs_20220913152349.zip

pixie_logs_20220913152349.zip
App information (please complete the following information):

Pixie version - 0.7.17+Distribution.1f8cdfb.20220815151559.3.jenkins
K8s cluster version - v1.23.10
Node Kernel version - 5.15.0-46-generic
Browser version - NA

I deleted the auth as suggested in slack.
vizier-query-broker is in a crash loop. Logs attached.
pixie_logs_20220922160414.zip

@benmathews , we can't reproduce this on our end. Can you please reopen if you see this issue again or have steps to repro.


Can't save Arrays of Resources

Right now, when you try to save an array of Resources, it won't work because the code only makes it so that it parses Resources as Dictionaries when the saved object's type is a Resource. However, even if code detected an Array element is a Resource, loading it at startup and assigning it to a Resource would crash because Resources are actually saved as Dictionaries.
The latter issue can be resolved by creating the inverse of _resource_to_dict, something like _dict_to_resource but if the plugin has the objective of supporting actual Resource save-load, we would need a flag in each saved Dictionary to see whether it is actually a Dictionary, or just a Resource. We also need to be aware of recursion in this instance.
Sample code to reproduce (assuming the project has the plugin downloaded):
extends Node2D
var items = Array()
# Called when the node enters the scene tree for the first time.
func _ready():
  var item = TestResource.new()
  items.append(item)
  $Label.text = "Press Load"

func _on_save_button_pressed():
  SaveSystem.set_var("items",items)
  SaveSystem.save()
  $Label.text = str(items)

Spotted & submitted by https://twitter.com/gferrari

Temporary solution for loading data directly into a Resource as of the latest update:
	var loadedItems = SaveSystem.get_var("items")
	if(loadedItems != null):
		for i in range(loadedItems.size()):
			loadedItems[i] = _dict_to_resource(loadedItems[i], TestResource.new())
	print(loadedItems)

	var savedItems := []
	if(loadedItems != null):
		for item in loadedItems:
			savedItems.append(_resource_to_dict(item))

	savedItems.append(_resource_to_dict(TestResource.new()))
	SaveSystem.set_var("items", savedItems)
	SaveSystem.save()

Hi!:) I'm facing the same problem; rn i'm building a sanbox building game where i want to have different save slot's and a bunch of different types of data stored, and to do this i'm thinking of using Resources with Resources. Like a SaveSlot resource, containing an array of different resources. One could might be a BuiltObjects resource, which in turn would contain an array of BuiltObject resource.
Does the temporary solution work for that? And how do i use it?
Thank you for the amazing plug-in btw!:) It has saved me so much time not having to build an entire save system from scratch 🙏

Hello! Unfortunately the temporary solution doesn't fix this issue, however, once I approve your PR and get around to it, I will implement a method that allows Resource arrays :)

^^

A workaround just came to mind -
You can index the save values' keys, rather than using one key entry to store the entire array. For example:
# Saves an array of resources at save keys "item0", "item1" and so on...
for i in range(savedItems.size()):
  SaveSystem.set_var("item" + str(i), savedItems[i])

Recent commit solves this issue. :)

Eeey! Great work!^^

Thanks mate! I finally got around to it haha
Fortunately it was not a lengthy process, sorry for the wait. :)

Of course! And no worries;it's tricky to find time some times haha

Trueee
Moving onwards to what I imagine as AudioMadeEasy :D I really wish there was a convenient audio management plugin easy enough to use, similar to Godot 3's SoundManager, but even that crashed many of our projects randomly so I had to end up using parts of it to simplify it.

Ooh! That sounds nice goal! I've not done to much work with sound in godot yet, but if there's no simple way to work with it in Godot, a plugin like that sounds great:)

It is actually quite simple, but surprisingly, no plugins deal with it - the easy and manageable way -, as far as I'm aware. It can get really complicated though, but I assume most games are okay with basic functionalities such as volume setting, looping and binding sounds to a certain bus.

Ah, that's fair!:)


Is https://datatracker.ietf.org/doc/html/rfc6243 supported in netopeer2?

Hi,
Is this RFC supported? If not are there any future plans to support it?
br,
//mikael

Yes, with-defaults is supported almost from the beginning of this project.

Great!
//mike


support params in sql panel that cannot be JSON encoded by default JSONEncoder

If sql params are values that cannot be encoded by the built-in json.JSONEncoder, then the sql panel doesn't get the params and subsequently can't perform the query or EXPLAIN the query.
In my case, I often have params that are instance of datetime.datetime.
I currently use the following patch: https://github.com/zt-initech/django-debug-toolbar/commit/47e766434a81622d94432069257f7f4bc79e5dde
It is not very nice. I don't like using both JSON and pickle, and there are probably other problems.
How do you think this problem should be fixed?
For example, should params always be pickled?
Can you help me fix this patch to get it merged upstream?

This issue is probably related: https://github.com/jazzband/django-debug-toolbar/issues/747


+[PpVStream@TV] *AEW All Out 2024 LIVE Broadcast Free ON Tv Channel 07. 09. 2024

5 minutes ago —2024 AEW All Out predictions, card, matches, start time, PPV preview, date, location, match card, wrestlers
🅻🅸🆅🅴🔴▶ CLICK HERE TO WATCH LIVE ONLINE
🆆🅰🆃🅲🅷🔴▶ CLICK HERE TO LIVE STREAM
AEW returns to pay-per-view three weeks after their big All In show
All Elite Wrestling is going All Out three weeks removed from All In. AEW stars performed for tens of thousands at Wembley Stadium in London earlier this month and now make the trip to Illinois for All Out, one of their "big four" pay-per -views, on Saturday.
After finally earning the AEW world title in England, Bryan Danielson is right back to work. Danielson is set to defend his title against TNT champion Jack Perry, who attacked him on AEW Dynamite after his title win. Meanwhile, the man who Danielson won the title from, Swerve Strickland, is also right back in the fire as he is set to take on "Hangman" Adam Page in an unsanctioned Lights Out steel cage match. The two have had a bitter and bloody feud over the last year and Saturday is sure to be the next chapter in an evolving storyline.
Two more title matches of note are set for Saturday night in Chicago. AEW TBS champion Mercedes Mone will defend her crown against Hikaru Shida after a brutal match with Britt Baker at All In. Plus, AEW International champion Will Ospreay puts his recently earned title on the line when he faces Pac.
Along with the title matches are some more intriguing matchups that should keep the audience on their feet throughout the night. Polarizing star MJF is back in action when he takes on Daniel Garcia. A "Chicago Street Fight" is set between a pair of top women when Willow Nightingale takes on Kris Statlander. And the AEW tag team titles are also on the line when the Young Bucks defend their crown against Blackpool Combat Club with the team of Claudio Castagnoli and Wheeler Yuta.
It all begins at 8 pm ET on PPV. Let's take a look at who the CBS Sports experts are picking to win in each match on Saturday's card.
 While it would be fine to have Page get some measure of satisfaction on those fronts after returning to action so recently, AEW has a lot of belief in Strickland as a star. It's rare that someone a promotion believes in that much loses a pair of massive matches back-to-back in a two-week stretch. Strickland lost the world title two weeks ago, he probably should get the win on Saturday. Pick: Swerve Strickland wins -- Brent Brookhouse
Strickland opened a lot of eyes with his phenomenal performance opposite Danielson at All In. A win over "Hangman" would put him right back on track; however, it would really be a disservice to AEW's resident cowboy. Page has repeatedly fallen short against Strickland. Their on-and-off feud remains one of AEW's more interesting storylines. "Hangman" winning breathes more life into it. Pick: "Hangman" Adam Page wins -- Shakiel Mahjouri
AEW World Championship -- Bryan Danielson (c) vs. Jack Perry: There's no chance Danielson is dropping the belt two weeks after winning it in London, especially given that he has said his time as a full-time wrestler will come to an end when he loses the belt. Perry is an interesting and solid first challenger for Danielson's reign but it would make less than no sense for him to end the new champion's time with the belt. Pick: Bryan Danielson retains the title -- Brookhouse (also Mahjouri)
AEW TBS Championship -- Mercedes Mone (c) vs. Hikaru Shida: From the moment Mone debuted at the "Big Business" episode of AEW Dynamite, you knew she'd be a leading woman in the promotion. The Shida match will deliver in the ring but there's not enough juice to justify a title change. If Brit Baker couldn't dethrone Mone, Shida certainly won't. Pick: Mercedes Mone retains the title -- Mahjouri (also Brookhouse)
AEW International Championship -- Will Ospreay (c) vs. Pac: You can basically copy/paste my thoughts on the Danielson match here. Ospreay just won the belt at All In, why would he be dropping it already? This will be a fantastic match and could well steal the show given the talent involved. But all that action will be building to an Ospreay victory. Pick: Will Ospreay retains the title -- Brookhouse (also Mahjouri)
MJF vs. Daniel Garcia: MJF cannot lose two major matches just weeks apart. MJF has been pegged an industry-wide star in the making for years. That luster has slightly diminished but he remains one of AEW's biggest assets. MJF is arguably AEW's most adept talker with the ability to deliver in big matches. It also seems this feud will continue beyond All Out so it's not imperative MJF gets his comeuppance yet. Pick: MJF wins -- Mahjouri (also Brookhouse)
Willow Nightingale vs. Kris Statlander (Chicago Street Fight): This feels like a blow off match the fan-favorite should win. It's a shame to see Statlander take losses at consecutive PPVs but Nightingale's success is a higher priority. Nightingale a magnetic personality that's been well-booked in AEW. A win could set her up nicely for a future feud with AEW women's champ Mariah May. Pick: Willow Nightingale wins -- Mahjouri (also Brookhouse)
🅻🅸🆅🅴🔴▶ CLICK HERE TO WATCH LIVE ONLINE
🆆🅰🆃🅲🅷🔴▶ CLICK HERE TO LIVE STREAM
AEW World Tag Team Championship -- The Young Bucks (Matthew Jackson & Nicholas Jackson) (c) vs. Blackpool Combat Club (Claudio Castagnoli & Wheeler Yuta): There may not be much gas left in the tank for the Bucks as far as fan interest or even the ability (or possibly the willingness) to put on the great matches that made them stars, but this is yet another match where they likely retain the titles. Castagnoli and Yuta seems like the only two members of the BCC who care that the group still exists. There's not enough momentum to switch the belts even if AEW is a promotion that deserves a top tag team that people care about.


Add pytest tests

Issue #23

Some tests have been merged in from #34 so it may be worthwhile merging master back into your branch if you want to continue implementing test @za.

Closing as inactive.


Include Account as a dimension

I have an importer which can return transactions for multiple accounts
e.g.
Assets:Foo:EUR
Assets:Foo:CHF
Assets:Foo:USD
so I can't filter the learning data for the specific account. The predictions should now take the account as an input dimension as it's unlikely that the same transaction that happens for Assets:Foo:EUR would also happen for Assets:Foo:CHF

looks good. two questions:

have you tried if this works with small vocabulary sizes, i.e., when there is only one account?
some thoughts on account names should be vectorized? the code currently says CountVectorizer(ngram_range=(1, 3). I expect that this will split each account name into its components, calculate 1-grams, 2-grams and 3-grams from the components, and count their occurrences. Sounds alright to me.

1 I haven't tried yet, probably should solve this generically for all dimensions
2 I didn't do this intentionally, I just copied the payee dimension.     Not sure if this shouldn't be the full account as you quite often have very similar account names with total different meaning.

Not sure if this shouldn't be the full account as you quite often have very similar account names with total different meaning.

On the other hand, if a new account name comes along, then machine learning would at least have some knowledge for making its suggestions or predictions.

Ok, going to keep it like I created it and then see how it goes


⚠ Bofrost.fr has degraded performance

In eaa49d5, Bofrost.fr (https://www.bofrost.fr) experienced degraded performance:

HTTP code: 200
Response time: 1160 ms

Resolved: Bofrost.fr performance has improved in b6d564e after 9 minutes.


iOS simulator is not working . Also not working for emulator.

Expected ios/Runner.xcodeproj but this file is missing.

@Akshay2941
Can you provide flutter doctor -v ? Is that the new flutter project you created ? or an existing one ?
Does Runner folder has Info.plist ?
If you run flutter create ., does the said file get created ?
Can you also provide pubspec.yaml and .metadata  file ?
Also, cd to the project that's missing the Xcode project, and attach flutter create -v.

it's new flutter project.
in the beginning it was working but I think I might have deleted that .xcodeproj file

Yes, Runner folder has Info.plist file

NO, the said file is not creating.

Pubspec.yaml

Also, cd to the project that's missing the Xcode project,
about this I am not sure how to do this.

also , the .gitignore sign is disable.

and for Android

The Android emulator error is install_failed_insufficient_storage meaning there's no free space in the emulator you are using, so free up some space by deleting unused apps and then try, which should resolve Android emulator error.
Regarding iOS, please don't post screenshots of the details requested. Provide the same in text format so that we can use it properly.
I see that you are on Xcode 14, did you upgrade Xcode recently ? If so, did it work before upgrading ?

it was resolved.


mapView can now be used in mixed layouts, such as GridLayout, BoxLayout etc.

when using the mapview I noticed that when placed in layouts when the mapview position is other than y:0, the markers will be misplaced. There are other quick solutions on the web saying use FloatLayout but that is not my desired way of fixing things, because FloatLayout will still bring the mapView to y=0.
fix and properly tested on my own app.

Good spot, thanks you!


react-digraph does not compile with TypeScript in VueJS

Hello, I'm trying to make react-digraph work in VueJS. I was able to set it up with Javascript, but still receiving errors after bringing in Typescript. The purpose of this exercise is to create a prototype which my team can re-use in another VueJS application which is set up with VueCLI.
Here is my repo: https://github.com/algouser2/react-digraph-vuejs
I don't have too much experience with UI development, especially with React, so I've gathered different ideas together from both repos: react-digraph and veaury.
The current errors I'm receiving right now are related to the ReactGraph.tsx file which was basically taken from here and adapted to Typescript: https://github.com/uber/react-digraph/blob/master/src/examples/graph.js

I'd appreciate if you can provide me with the right direction or a proposed solution

@algouser2
This is because the typescript of vue and react conflict.
https://github.com/devilwjp/veaury#typescript-jsx-types-conflict-caused-by-vue-and-react-at-the-same-time

@algouser2
You can try issue (#39)

@algouser2
This error is at runtime, indicating that the typescript error has been resolved. This runtime error clearly indicates that you passed a VNode into a property that requires ReactNode.
In this case, the parsing method of JSX is generally wrong, and React's JSX parsing should be used instead of Vue's JSX

@algouser2
I think it may be that the version of your dependency package is installed incorrectly, and there are two different versions of react, resulting in multiple cases.

@algouser2
The alias configuration of the vue.config.js of this project is completely wrong, delete the part marked in red and it will work normally


Chore/prepare 5 3 0

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Initial PR for RAT License Check

Description
Goal of this PR -

To get the .rat-excludes file into the 1.2 Release so that RAT check can be run locally during src code validation (voting process)
Get the .rat-excludes file reviewed by everyone before it is merged.

Please let me know if you see any file/directory or file format that should not be included in this list or if there are any regex errors. I have been adding incrementally to this list and a redundant line may have creeped in.
refer this link for further details - https://cwiki.apache.org/confluence/display/MXNET/MXNet+Source+Licenses
Checklist
Essentials
Please feel free to remove inapplicable items for your PR.

[ ] The PR title starts with [MXNET-$JIRA_ID], where $JIRA_ID refers to the relevant JIRA issue created (except PRs with tiny changes)
[ ] Changes are complete (i.e. I finished coding on this PR)
[ ] All changes have test coverage:
Unit tests are added for small changes to verify correctness (e.g. adding a new operator)
Nightly tests are added for complicated/long-running ones (e.g. changing distributed kvstore)
Build tests will be added for build configuration changes (e.g. adding a new build option with NCCL)
[ ] Code is well-documented:
For user-facing API changes, API doc string has been updated.
For new C++ functions in header files, their functionalities and arguments are documented.
For new examples, README.md is added to explain the what the example does, the source of the dataset, expected performance on test set and reference to the original paper if applicable
Check the API doc at http://mxnet-ci-doc.s3-accelerate.dualstack.amazonaws.com/PR-$PR_ID/$BUILD_ID/index.html
[ ] To the my best knowledge, examples are either not affected by this change, or have been fixed to be compatible with this change

Changes

[x] Added a directory for rat check nightly test (script coming soon but may be included after 1.2)
[x] Added a README.md for rat check
[x] Added a .rat-excludes file

Comments
@gautamkmr @eric-haibin-lin @bhavinthaker
Please Review

@mbaijal any updates ?

I think this PR can be merged as is. The list of directories included in the .rat-excludes file has been discussed in the previous release and reasons for most decisions are documented here - https://cwiki.apache.org/confluence/display/MXNET/MXNet+Source+Licenses
In most cases, either the file should have no license or I am unsure about the correct license.
As we move forward, where ever possible the community can add the correct licenses and clean this list further.

I'm going to merge this for now.
@sergeykolychev please update the perl license when you get time. I appreciate it.
@mbaijal thanks for adding the rat-check.


Request to implement a feature about betweenness_centrality

Hello, easygraph developers
I found that the betweenness_centrality function does not implement the feature of sampling k nodes to calculate the node betweenness centrality. But networkx has implemented it. This is to reduce the calculation time of obtaining the node betweenness centrality when the graph is very large. By the way, networkx does not consider how to choose k to balance the calculation time and the node betweenness centrality close to the true value. I hope you can consider this.
Thank you very much.

Thank you for your valuable suggestion!
We appreciate your insights regarding the betweenness_centrality function and the potential benefits of incorporating sampling for k nodes.
We will consider this feature for future versions to enhance performance and accuracy.


Allow passing a list to Bundle constructor

Fix #26

Codecov Report

Merging #27 into master will increase coverage by 0.7%.
The diff coverage is 100%.

@@            Coverage Diff            @@
##           master      #27     +/-   ##
=========================================
+ Coverage   90.94%   91.65%   +0.7%
=========================================
  Files          40       40
  Lines        2541     2731    +190
=========================================
+ Hits         2311     2503    +192
+ Misses        230      228      -2

Impacted Files
Coverage Δ

stix2/test/test_bundle.py
100% <100%> (ø)
:arrow_up:

stix2/bundle.py
100% <100%> (ø)
:arrow_up:

stix2/utils.py
100% <0%> (ø)
:arrow_up:

stix2/test/test_utils.py
100% <0%> (ø)
:arrow_up:

stix2/test/test_indicator.py
100% <0%> (ø)
:arrow_up:

stix2/test/conftest.py
100% <0%> (ø)
:arrow_up:

stix2/test/test_fixtures.py
100% <0%> (ø)
:arrow_up:

stix2/properties.py
97.43% <0%> (+1.8%)
:arrow_up:

Continue to review full report at Codecov.

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

I was a little unsure about the order that objects are put into the list (originally the objects kwarg came first), but your test cases confirmed for me that your order makes the most sense. 👍

@gtback The test cases are what led me to change the order. :)


Bootstrap data-attributes

Encountered an error with bootstrap with Data attributes. It tells me that the attributes 'src' 'href' and 'data' must have a value, it has it and it does not detect it.
'src', 'href', and 'data' attributes of must have a value (007:tag/src-empty)
This is the error line:
<button class="btn btn-info px-4" data-toggle="modal" data-target="#exampleModal">Add task</button>

@Kevindm14 that case is a good one, it should be fixed once this PR gets merged. https://github.com/wawandco/milo/pull/61


Game-breaking artifacts with some old DX9 games when running Wayland session

Description:
When some old games are launched with Wine or Proton (the issues doesn't seem to be version-specific) using DXVK, the image is corrupted with cubic black artifacts, akin to those one might expect to see when their GPU's memory is failing.
This was my immediate go-to thought, but after trying different configurations I've narrowed it down to DX9 applications and Wayland session. When launching the same games using X11 session (or with different API options), this issue is not present.
The other factor at play might be the resolution. I've first noticed that when FNV defaulted to low screen resolution after a crash (sub 720p). When I forced my display's native resolution via FNV's config file, the issue was no longer reproducible. The same went for the L.A. Noire which by default launches in 720p if the launcher is bypassed - artifacts were gone once the res was set to native.
This is how those artifacts appear to the user:

(my apologies for the straight-up photo of the screen, but these artifacts are not visible on the screenshots or screen capture)
Software information

Fallout New Vegas with NVSE and 4G+ patch (Steam version)
Fully vanilla L.A. Noire (Steam version)

System information

Arch Linux (fully updated, no outrageous tweaks, custom kernels or anything like that)
GPU: Radeon RX 7900 XTX
Driver: Mesa 24.2.7
Wine version: various (Proton 9.0-5, GE-Proton9-20, Wine-GE-Proton8-26, custom Wine builds using TKG scripts)
DXVK version: various (2.4, 2.5, 2.5.1)

Apitrace file(s)
https://mega.nz/file/hs9wXBAC#qI1eZ5HZtBStbQUR81kq5fD55v8GaL9yji31t3YZoIc (.7z archive, ~440 megabytes, FalloutNV, GE-Proton9-5 and whatever's version of DXVK is inside of it)
When I was force-enabling WineD3D via Proton's feature flag, I was unable to reproduce the issue. So the .7z archive at the link above contains a number of traces: with WineD3D enabled and DXVK disabled and vice versa, plus separate trace files which were created due to the fact that the game uses a separate launcher which then spawns the main executable.
I was unable to force L.A. Noire to play nice with the apitrace toolkit, so I'm unable to provide any traces for it right now. I'll look into it though once I'll have some time.
Log files
steam-22490-d3d-disabled-dxvk-enabled.log
steam-22490-d3d-enabled-dxvk-disabled.log

This looks a driver bug and is fixed by https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/32115 on Mesa git. You can also work around it with RADV_DEBUG=nodcc.

Multiple bug reports on the mesa gitlab:
https://gitlab.freedesktop.org/mesa/mesa/-/issues/9890
https://gitlab.freedesktop.org/mesa/mesa/-/issues/8705
https://gitlab.freedesktop.org/mesa/mesa/-/issues/11789
https://gitlab.freedesktop.org/mesa/mesa/-/issues/11600
https://gitlab.freedesktop.org/mesa/mesa/-/issues/11547

You can close this, it's not a dxvk bug.