Questions:

Hi there, thanks for interesting tool. Would be possible to answer on following questions?

How it works? Some similar tools force/rebuild windows thumbnail database folder in order to fix issue with missing thumbnails. Preloaded create linked thumbnails and populate them into that folder? Or maybe it create invisible sub file next to original images? I did not noticed change (by single bit) of preloaded folder
What is difference between "preload thumbnails" and "preload thumbnail recursively" ? In what situations we should use those once we build thumbnails with "preload thumbnail recursively" ?
Installation version that provide context menu tab, use multithreading or its something that only works with command line? I was thinking about build-up thumbnails for my whole system, but expect it gonna take hours and want to be sure I perform that as fast as possible

Would be great to see answers for those questions in Faq or something.

Hi, this program works by scanning the selected directory for files with specified file extensions, and then processes the thumbnails by asking windows to generate a thumbnail for each file directly. What this achieves is speeding up the loading of thumbnails on folders which haven't yet had thumbnails generated for them without having to manually navigate to each folder, which would otherwise make the thumbnails of images take a long while to load, especially for folders with large amounts of files.
The difference is shown in this example here, though from the original version which was single-threaded:

The difference between "Preload Thumbnails" and "Preload Thumbnails Recursively" is that using the first option will only preload thumbnails for the specified folder while the second option will preload thumbnails for both the specified folder along with any subfolders the specified folder may contain. The wording choice was from the original author of the program and I may consider changing it to something that's more intuitive to understand.
Using the installer version will add the context menu to folders and drives along with allowing use of the command line without having to specify the path of the program. The V2 version of the program also benefits from this for various features which also includes keeping any folders that are generated such as backed up thumbnail cache and (soon) logs to be in the same folder as the program.
I'll definitely consider adding an FAQ, especially for the V2 version which may need a lot of documentation to fully understand all of its features. Hope you find this program to be useful for you!

@jurandfantom see AppData\Local\Microsoft\Windows\Explorer\thumbcache_xxx.db


Derive some meta attributes.

Ensure that read and write units are passed down to derived classes, as well as streams (although I'm not sure about this logic as I don't use streams).

Hmm.. not sure what it's complaining about, because it certainly hits those lines of code...

Ok, I set the list of attributes that will carry over to derived Meta classes to read_units, write_units and a new table_prefix.  The table_prefix prefixes the table name with it's value.  As this will be carried down to it's derived classes, you can have a base class defined as something like:
class MyBaseClass(BaseModel):
    class Meta:
        abstract = True
        table_prefix = get_config().ENVIRONMENT  # Something like dev or staging
    pass

class MyClass(MyBaseClass):  # tables name will be something like dev-MyClass or staging-MyClass
    pass

As with #92, thanks for taking on this work!  Any inheritance impl will need to make copying Meta attributes easy, so this is a great step towards a solution.
I'm leaving the more general how-does-inheritance-work discussion for #72 and #92, so comments here are just focused on the Meta class inheritance.

I like the idea of table_prefix as a user, but it's a little too specific for bloop to care about; why then not table_suffix or table_pattern?  Instead of whitelisting property names, what about just copying everything down from the base?  That way users' custom values always work (the alternative is they have to hack onto the whitelist themselves).
What are the rules when a base class is bound (possibly injecting a stream arn) and then a class is derived from that?  Does the derived class take the bound stream arn?
The same question applies to table read_units and write_units; in an upcoming change (the next few hours) the default behavior will change (see #88) such that omitting them will no longer default to 1/1, but will take their values from the existing DescribeTable.  In that case, deriving a class after binding the base class will grab the bound read/write units, and not the base class's intent, which was "get these from Dynamo".  Can we preserve that information without polluting the original Meta object or leaking memory by holding on to large custom meta properties?

Thanks for the thoughtful response!
A little background first...  I'm a refugee from the flywheel project, and porting to this library seemed the easiest transition. But there are features that are missing, that I would like to implement.
So, my original intent with this was to add a prefix to table names.  In the flywheel package, you can pass in the "namespace" into the engine on creation.  I use this to prefix all tables with the environment they are deployed too.  For example, develop_user, staging_user, prod_user tables.
So with that in mind, I poked around the table creation code, and noticed that there were a lot of references to the obj.Meta.table_name without any translation methods under the hood.  So I figured the only place to make that prefix was in the metaclass for model creation.
Perhaps there is a better way to do this.  What about having an internal metadata class that holds the information gleaned from the model.Meta classes?  That way, we can have computed properties on that metadata, etc...

For prefixing table names, I'd recommend connecting to the before_create_table signal.  The example suffixes table names with a nonce, but that's an easy transition:
def table_prefix_for(model):
    """
    Maybe this inspects the model name, or model columns to select
    the appropriate namespace.  Or, it always returns the same fixed value.
    """
    return "my-table-"

@before_create_table.connect
def apply_table_prefix(_, model, **__):
    prefix = table_prefix_for(model)
    model.Meta.table_name = prefix + model.Meta.table_name

The integ tests use a configurable nonce suffix so that simultaneous runs don't interact, but still offer a way to set the nonce explicitly.

We can probably close this one then, unless there is something that you want to derive.  I'll add a pattern for people wanting to do environment sharded tables as well.

Closing for now.  I suspect we'll revisit the Meta class as we get further into abstract inheritance and mixins, but I'd like to tackle that when column/index inheritance is working.


Automate releases

Summary of the issue
Releases should:

Be simple and automated
Use GitHub's release mechanism
Include a changelog
Ensure zkg.meta points to that release's version, allowing us to change our main's zkg.meta to indicate main as the version.

Consider backfilling releases for 0.1, 0.2, and 0.3.

@ottobackwards any additional acceptance criteria you'd like to see with automated releases?

@ottobackwards any additional acceptance criteria you'd like to see with automated releases?

Can we define what a release entails?

Can we define what a release entails?

I intended the first comment to have everything.  Are you thinking process as well?

I intended the first comment to have everything.  Are you thinking process as well?

https://github.com/SeisoLLC/zeek-kafka/pull/26


[feedback] /web/tools/chrome-devtools/css/

Page Affected: https://developers.google.com/web/tools/chrome-devtools/css/
What needs to be done?
I found the best postion for Dev Tools for going through the interactive tutorial in this page is to open them on the right with 50% width. The responsive documentation is beautifully fitting this way. For first timers, mentioning this tip would help.

Thanks for the idea. Do you mean like this?


Webcam light still on after cam.release()

Expected behaviour
When releasing webcam, not only the webcam should be released but also the webcam light indicator should be turned off.
Actual behaviour
The webcam light keeps on even though the webcam is, in fact, released.
I am doing:
webcam = cv2.VideoCapture(0)
webcam.release()

After the release command, if I try to read the cam I get: (False, None) but the webcam itself is still <VideoCapture 0EE62DC0>. I don't know if this is the issue, but the light keeps on until I kill all python script or python terminal responsible to turn it on.
I am on a Windows 10, python 3.5, opencv 4.0.1. According to comments on my stackoverflow question (https://stackoverflow.com/questions/51974632/webcam-light-still-on-after-cam-release) other version also shows the issue (python 3.6 and opencv 3.4.2)
It seems that it was introduced in an earlier version because version <IP_ADDRESS> works fine.

Please report OpenCV bugs to the official OpenCV repository: https://github.com/opencv/opencv/issues
This repository is just an unofficial wrapper which generates python bindings automatically from OpenCV sources.

If anyone has the same issue... the issue was open in the official repo (https://github.com/opencv/opencv/issues/12301)

@skvark Hi, very sorry to disturb again... but I am more of an user.
I've opened the issue in the oficial repo, but it was suggested for me to "Attach logs with OPENCV_VIDEOIO_DEBUG=1 environment variable.
Also try OPENCV_VIDEOIO_PRIORITY_MSMF=0 to disable MSMF." since the opencv-python is a wrapper, how can I do this? Could you help me?
Thanks in advance...

I believe that you can just set those environment variables in the command line before you run your Python script. For example:
setx OPENCV_VIDEOIO_DEBUG 1
python yourscript.py


Create a new ByteBuffer for decoding when retrying with CESU-8

Fixes #2546
This fixes a case which wasn't handled in #2299.

When a string can't be decoded with UTF-8, we retry the decoding with CESU-8 (done as part of #2299)
If the bytes that can't be decoded are not at the start of the bytes range to be decoded, then the UTF-8 decoder changes the position of the ByteBuffer and the CESU-8 decoder will start decoding at the new position.
To avoid this, we wrap the  array with a new ByteBuffer and use it with the CESU-8 decoder.

For example, before this change, when trying to decode with UTF-8 the bytes representing the following:
Good morning! 👋 Sun 🌞
The UTF-8 will read from the byte buffer partially and the CESU-8 will decode this:
👋 Sun 🌞

thanks!


lonelypotato.fireeye Install Error

Bug Description
When attempting to install the lonelypotato.fireeye package from Chocolatey, I receive this error: ERROR: The remote file either doesn't exist, is unauthorized, or is forbidden for url 'https://github.com/decoder-it/lonelypotato/archive/1845a19662856abd1e3f84f3ebdb9c029e93ab8d.zip'. Exception calling "GetResponse" with "0" argument(s): "The remote server returned an error: (404) Not Found."
Here is my Chocolatey log relating to this install:
lonelypotato.fireeye Install Log.txt
Steps To Reproduce

Run the following command in an elevated PowerShell prompt:
cinst -y lonelypotato.fireeye

Screenshots

Version

OS: Windows 10 Version 2004 Build 19041.508
$Env:FEVM_PROFILE: Commando_Default

@syth3 this looks like the file may be being blocked by a proxy of sorts. Can you confirm you are not installing this behind a firewall/proxy that may be interfering?

@day1player I am pretty certain I am not installing it behind a firewall/proxy. My current setup is a Windows 10 computer running Commando VM inside of VMWare workstation. The Commando VM is configured to use NAT networking. My Windows 10 host computer is connected directly to my ISP-given router running their default firewall. Because of this, the only firewall/proxy that seem to be of interest are any Windows 10 firewalls running on either the Commando VM or my host machine, or the default firewall on my router. Additionally, I have tested installing this package in a different VM on a different network entirely and face the same issues. When I visit the url listed in the error message in my web browser, I also receive a HTTP 404.

Right on it looks like that was definitely removed then. We will have to update the package. I will let you know when it is done, thank you!

Sure thing. Thanks for the help!

fixed with june update #262


hard coded config file in test scripts

In all test_....py scripts, the config_path is hard coded to '../config.yml' which does not align well with the recently implemented feature that allows the exchange of the config files.

Create a test_config.yml file dedicated exclusively to testing.


Add scenario Klimaatakkoord to presets

Kalavasta made a 2030 scenario according to the "klimaatakkoord" (Scenario Klimaatakkoord).
Let's add this to the presets
Actions:

[x] Add some sentences to introductory text
[x] Ask Kalavasta for permission (for preset and introductory text)
[x] Put settings in preset-format (commit)
[ ] Process feedback Kalavasta / Nebeheer NL

Update 24-09. Rob will check with Netbeheer NL whether it is alright with them if we make this scenario a preset scenario.

https://github.com/quintel/etsource/pull/2129


support search_covering

Thank you for creating such a convenient and useful Rust library! I am doing research about BGP routing, and previously, I implemented an algorithm using the py-radix library in Python, but it had serious efficiency issues (the program needed to process millions of prefixes and ASN data and perform complex calculations), so I rewrote it in Rust. Most of the algorithms could find equivalent replacements in prefix-trie, which is great. However, a method called search_covering from the py-radix library does not have a corresponding implementation in prefix-trie, so I would like to add it. This method would return a vec of all nodes that cover a given prefix.

Thanks for the PR. It looks good. However, I have a couple of suggestions:

Document that prefix itself will also be returned if present, and that all elements will be sorted according to the depth in the tree.
Add the same function also for PrefixSet
Add functions to not only get the values, but also the prefixes (or both).
How about not returning a Vec, but returning an Iterator instead? Allows the user to collect into whatever data structure they like, and abort after prefixes of a specific length, etc...

In other words, let's add the following functions (and names that match with rust's naming convention of maps):

PrefixSet::cover to return Vec<&'a P>
PrefixMap::cover_keys to return Vec<&'a P>
PrefixMap::cover_values to return Vec<&'a T>
PrefixMap::cover to return Vec<(&'a P, &'a T)>

Do you have time to implement those changes? If not, I can also take care of them.

I will close this PR now, as I implemented it myself with my comments above.
Small remark: There was a bug in your implementation that the root node would never be returned.

Thanks, your implementation is more elegant! And I must admit that I am still a Rust newbie 😂


[BUG] Double Spaces after periods

Describe the bug
Two spaces are always added after period and ellipsis, and not for any other punctuation.
To Reproduce
Steps to reproduce the behavior:

Encode a file with a period and a space after it.
Decode it.
See that there are two spaces.

Expected behavior
One space will appear after the period, just like with commas.

No longer applies. See #4.


refactor: normalize Angular and Angular.js sections/resources

What does this PR do?
Add resource(s) | Add info | Improve repo
For resources
Description
Why is this valuable (or not)?
Completes to apply #4940 to all listings
Some usefull resources are been added to prevent single items section hierachy in listings where was mixed. Also sets creators, platforms fileformats... in those sections Angular.js, Typescript>Angular.
How do we know it's really free?
For book lists, is it a book? For course lists, is it a course? etc.
Checklist:

[x] Read our contributing guidelines
[x] Search for duplicates. Completes #4940
[x] Include author(s) and platform where appropriate.
[x] Put lists in alphabetical order, correct spacing.
[x] Add needed indications (PDF, access notes, under construction)

Review Tasks

[x] Move resources. Angular :arrow_forward: Typescript - Angular, AngularJS :arrow_forward: Javascript - AngularJS
[x] Normalize title AngularJS
[ ] Add see also/crosslink notes

Followup

Check the output of Travis-CI for linter errors!

If it's named at the source as "AngularJS" then why "angular.js"
Would it make sense to add "see also" links  between the two angular sections? Will someone looking for an Angular book to learn from know that it's not in the AngularJS section?

If it's named at the source as "AngularJS" then why "angular.js"
Would it make sense to add "see also" links between the two angular sections? Will someone looking for an Angular book to learn from know that it's not in the AngularJS section?

If it's named at the source as "AngularJS" then why "angular.js"

In English listing was typed as is. To be clear... You suggest revert headings and use AngularJS?

Would it make sense to add "see also" links between the two angular sections? Will someone looking for an Angular book to learn from know that it's not in the AngularJS section?

Do you are talking to put a note at TOC entries? or how to abord? I don't know if linter accept it.

I think if the crosslink starts with … it will sort to the end of the list except for CJK …
HORIZONTAL ELLIPSIS
Unicode: U+2026, UTF-8: E2 80 A6
need to experiment

Our general rule for titles, names, etc. is to use the form used by the creator. So based on https://angularjs.org/ , I would say we need to use AngularJS.

so far so good

so far so good

Yep. I'm in progress yet :construction:. It was very weird pass linter this time, so I prefer force-amend instead sync :laughing:
Sorry for actions report spam. Altough, I have enabled the actions enviroment in my fork, I'm trying to have a remark/linter local enviroment with same fpb rules to avoid this kind of issues :wink: If it serve, I can pull it too as another PR. :wink:
Reviewing now about "see also" notes :rocket:

I think if the crosslink starts with … it will sort to the end of the list except for CJK …
HORIZONTAL ELLIPSIS
Unicode: U+2026, UTF-8: E2 80 A6
need to experiment

I bring good news. No problems with linter :rocket; as first draft
I opt with quote syntax placed under section heading, taking care about whitespaces rule 1-0-2. Ellipsis is also used as you suggest.
* [Official Free Online Guide for Apache Wicket framework](http://wicket.apache.org/learn/#guide)

### JavaScript

> :notebook::information_source: See also … [TypeScript](#typescript)

* [Basic JavaScript for the impatient programmer](http://www.2ality.com/2013/06/basic-javascript.html) - Dr. Axel Rauschmayer (HTML)

Check the live preview deployed in my repo (in english books or in spanish books) before continue with other files and push changes:

…

Also let me know where crosslinks should we add (e.g. also in TOCs, in both directions like you can see now...) to have everything well tied :wink:.

the blue "i" is a good idea - 2 icons is overkill

the blue "i" is a good idea - 2 icons is overkill

Maybe :twisted_rightwards_arrows: :twisted_rightwards_arrows: reffers better to crosslinks?

the blue "i" is a good idea - 2 icons is overkill

Maybe :twisted_rightwards_arrows: 🔀 refers better to crosslinks?

the 'i' seems more versatile and easier to understand (for me at least)

As the community may have suggestions/ comments about the form and usage guidelines for crosslinks, I suggest that this PR should only use crosslinks for the Angular situation. Other crosslinks should be moved to a separate PR

Sorry for overscope inconvenient. Check it again

OK, any more changes can go in a new pr.


Use unique featureid

#229

Use cartodb_id as feature id
Set cartodb_id on GeoJSON sources
Request cartodb_id to windshaft sources (Dataset, SQL)
Update interactivity examples: points, lines, polygons
Add unit tests
Add user tests

🍐 ✨


For a 0.16.3 release

#497

Codecov Report

Merging #498 (25aa0f7) into master (d09d53c) will decrease coverage by 4.37%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master     #498      +/-   ##
==========================================
- Coverage   81.88%   77.51%   -4.38%
==========================================
  Files          39       39
  Lines        2932     2468     -464
==========================================
- Hits         2401     1913     -488
- Misses        531      555      +24

Impacted Files
Coverage Δ

src/data/data.jl
94.91% <ø> (+1.89%)
:arrow_up:

src/hyperparam/one_dimensional_range_methods.jl
91.46% <ø> (-0.68%)
:arrow_down:

src/init.jl
100.00% <100.00%> (ø)

src/measures/meta_utilities.jl
30.76% <0.00%> (-67.48%)
:arrow_down:

src/composition/learning_networks/arrows.jl
0.00% <0.00%> (-46.67%)
:arrow_down:

src/measures/loss_functions_interface.jl
68.42% <0.00%> (-28.95%)
:arrow_down:

src/interface/model_api.jl
76.92% <0.00%> (-15.39%)
:arrow_down:

src/composition/models/_wrapped_function.jl
22.22% <0.00%> (-11.12%)
:arrow_down:

src/measures/measures.jl
78.72% <0.00%> (-9.04%)
:arrow_down:

src/interface/data_utils.jl
86.95% <0.00%> (-8.97%)
:arrow_down:

... and 27 more

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 d09d53c...6328ebc. Read the comment docs.


Native Events/Functional Components: Event.stopImmediatePropagation does not cancel event loop.

Version
2.4.1
Reproduction link
https://jsfiddle.net/alexsasharegan/ojymho07/
Steps to reproduce

Create a functional component:

create an event handler that calls Event.stopImmediatePropagation
put the context's event handler in an array with the component's handler, but place the component's handler at the first index. (Allowing the component's handler the first chance to stop propagation)

Using this functional component in a parent component, bind a listener to the same event (e.g. "click")
Execute the event

What is expected?

The functional component's handler should be called first, since it is first in the array
The functional component's handler should execute the stopImmediatePropagation call, and kill the event loop.

What is actually happening?

Execution order is preserved correctly.
The parent component's handler is still being invoked (but additional handlers bound through EventTarget.addEventListener are not).

My use case starts at creating a link component that will respect a disabled property, but continues on to various other components to create a cohesive UI component API.
It would be beneficial to have some way to cancel the Vue event loop. I don't know my way around the source well enough, but I imagine that Vue internally tracks all event handlers for a given node, intercepts the native event first, then invokes all callbacks. This is why natively bound callbacks do not get invoked, but callbacks bound by Vue are invoked.

That's because Vue is wrapping all of those functions in one function so it only has to register 1 instead of n listeners.
https://github.com/vuejs/vue/blob/dev/src/core/vdom/helpers/update-listeners.js#L26
You should simply do the same - wrap it all in your function instead of pushing your own into the array.


describe acceptance criteria

Acceptance criteria are a set of conditions that must be met for a user story or feature to be considered complete. By establishing clear acceptance criteria upfront, teams can ensure they have a shared understanding of project requirements and deliverables. The specific requirements and conditions that must be met for a project deliverable or component to be considered complete, satisfactory, and acceptable by the client or stakeholders involved.

https://medium.com/@alexeusgr/acceptance-criteria-ee21cb72725b


Assets page - Merge discovered an server data

We need to merge both data returned by the server (via the API) and data discovered by the client (endpoints, spans etc.)
The design already indicates how to show client discovered assets with no data.

@kshmidt-digma is the react App support it? if not please open an issue on this one in digma-ui repository and add reference to it in this issue


A question about reference-style links rendering.

So I was working on some custom markdown tags using markdown-it-regex package, and I used another rendering functions to convert the text inside these tags, and it works perfectly.
My question is not about custom tags, or plugins development, but it's about reference-style links.
So since the extra rendering functions converts only the text inside the custom tags, using reference-style will not gonna work since the syntex is not inside the rendered text and its located in another part of the document.
I wanna know more about reference-style links rendering, I know that a links map will be stored somewhere while rendering, so how to get this object for external use?

Those are stored in env, last param of parser call. Please, inspect sources before create such issues.

Hmmm sorry, I opened this issue using mobile, that's why I didn't give more details.
So env will store it, thanks for the info.

@puzrin Excuse me, I think I didn't really understand you.
So after some tries I ended with this:
var ref = window.markdownit('zero').enable('refernece');
console.log(ref.parse(text, {}));

On the output I can only see the the tokens of the rendered text, but nothing about references, I don't really know what I supposed to do since I still trying to understand the renderer system.


Fuse Box

Addition layer of protection

Not implemented on current design due to limited space in junction box.


@notifee/react-native is not working with FCM in ios

getInitialNotification()
onNotificationOpenedApp()
onMessage()
setBackgroundMessageHandler()
all these methods are working fine in android with @notifee/react-native
But in ios these methods are not working as expected with notifee. I  uninstalled  and try  then these methods :-
getInitialNotification()
onNotificationOpenedApp()
onMessage()
setBackgroundMessageHandler()
are working fine.

does yours work with android when app is killed?

i same :(

onForegroundEvent, onBackgroundEvent,.... not working on ios device :(


Scheduled livestreams sections

Issue type
Feature request
Description of the problem

Play SRF: Add sport livestreams and sport replay in Livestreams tab
Play RTR: Add RTR livestreams in Livestreams tab
Play RTS: Add sport livestreams, sport replay and sign languages livestreams in Livestreams tab

Environment information

iOS / tvOS: Both
Device: Any

After review and tests, we separate iOS and tvOS live home sections.
New remote configuration property added.


Merge refs/heads/update-dependencies into alpha

Merge refs/heads/update-dependencies into alpha

This PR has been merged into alpha and tagged as 2.0.0-alpha-202308301518. Thanks for your contribution!


Exclusion of IntegrationRuntimes - InputIsMalformedDetailed

When performing a release to our PROD environment sadly we have (not by my choice) an SHIR that runs for each environment (DEV/UAT/PROD) and then in some cases I've had to install an SHIR on the PROD environment (due to VPN's) and then use a link-shared SHIR back on my dev-adf from the prod-adf.
Deployments are playing havoc, initially it was telling me there was a permissions issue with the 'SHIR' IR and that there were no permissions.
I decided that the best solution then would be to "exclude" the integrationRuntime from the deployment. I have added
-integrationRuntine.*
to my exclusion list and then the error I got on release was:
"InputisMalformedDetail: Input is malformed, Reason: could not get integration runtime details for SHIR-PROD"
Now this is one SHIR that is shared from PROD to DEV, however I don't understand why I'm excluding integrationRuntime that it is even attempting to do anything with the IR's.

note your typo in
-integrationRuntine.*


Add Ability to Provide Custom Logic for Asserting a Match

I have a scenario where I need to take and compare a snapshot of string and non string data (specifically EPUB and PDF). I use pytest-snapshot for the string data and have written additional functions to do the non-string comparisons, but I prefer not to have two snapshot solutions and would also like to be able to take advantage of the --snapshot-update ability.
I took a look at what @otosystems was doing with a custom-comparator in https://github.com/otosystems/pytest-snapshot/tree/custom-comparator, but it didn't fit my needs.
So I took a stab at creating an additional approach. You can find an initial proposal at https://github.com/patbakdev/pytest-snapshot/tree/custom-matcher. Basically, my plan is to allow for an optional func to be base to the assert_match methods. By default it would simply pass on to the existing string comparison function so its backwards compatible. I also wrote a simple filecmp function as a proof of concept/example and for use in tests. Presumably more matching functions could be provided in the future.
I don't think this is the best approach, but it was the least impactful. There is an unfortunate coupling between the plugin and the function needed for the update logic. A better approach might be to separate out the logic into a plug-able architecture with methods for snapshot update, comparison, etc., but that would require substantial changes to existing code and more time. Let me know if you are open to making some kind of change here and if so any thoughts you have on the approach/implementation.
Thanks

Hello, thanks for the suggestion. I guess that the library could also be useful for non-string objects.
We could safely add support for bytes in addition to str without changing the API or much downsides. pytest gives helpful diff messages for bytes, though they wont be as useful as for string data.
We could also add custom comparator logic, something like
@dataclass
class Person:
    name: str
    age: int

def compare(value: Person, expected_value: Person) -> None:
    # This function should raise an exception if the values are different
    assert value.name == expected_value.name and value.age == expected_value.age

def encode(obj: Person) -> bytes:
    # This function should encode the object into bytes, preferably in a human-readable format for good readability.
    return f'Person\n name: {obj.name}\n age: {obj.age}'.encode('utf-8')

def decode(data: bytes) -> Person:
    # This function should reverse the ``encode`` function's operation.
    return ...

snapshot.assert_match(obj, 'my_snapshot.txt', compare=compare, encode=encode, decode=decode)

This would give the users the ability to use pytest-snapshot for almost any type of object.
There is one big downside to this solution. The user might encode data into the snapshot that he doesn't compare. For example, if the above compare function only compared the name and not the age. Anyone that looked at the snapshot file would probably assume that the age is also being tested, when in fact, it is not.
This is the reason that I would rather avoid supporting custom comparison functions.
So what do you think? Would supporting bytes be good enough? Or do you need custom comparator logic? I could add it, and put it at the bottom of the documentation with a warning of its downsides. Do you have any improvements to the API I specified above?

Having a helpful diff is not a big issue in my book. I usually always end up using a proper diff tool. For PDFs I convert and compare each page, but I suppose a byte comparison would work in this case. The most important part is knowing that its different and then I can use DiffPDF or similar tool. EPUB is more difficult since its an archive of text and images. Currently my compare function extracts the files to a temporary directory then compares each one after normalizing one part of the xml that is date based. I like the idea of having the compare function for this, but I also think I could move this logic into the test so that I use pytest-snapshot against each text file (str) and image (byte) individually.
So, if we could get a byte comparison that would be great, a custom comparative would be nice and might be more shareable, but might not be worth changing the API for, has the downside you mentioned, and could be accomplished with more testcase code/logic.
I'm basically just using filecmp for the file compare. The API you have looks good to me (better than what I had). If the only change made is to support bytes, then it would be nice not to have to provide any additional information (auto detect?) or a flag.
Thanks.

I created branch bytes-snapshots which adds support for bytes and lays the groundwork to easily add custom comparators/encoders/decoders.
As you asked, it auto-detects whether the object is str or bytes but this leads to a troubling edge case. pytest-snapshot will not raise an error if the tested value changes from a string into bytes with the "same" value or vice versa: If a snapshot was created from 'hello' and then the value changed to b'hello', the test would not raise an error.
I am not sure what the ideal solution to this is:

Ignore the edge case.
Save the type of the object that created the snapshot file somewhere. I don't want to save it at the start of the snapshot file since the file is probably a valid json file/pdf/etc.
Create extra functions assert_match_bytes and assert_match_dir_bytes.
Some other solution?

I am leaning towards the first solution since:

It keeps the API clean and simple.
The library's goal isn't to be used as a single tool to unit test an object. Users can test the object's type themselves.
Trying to save type information can get problematic if we start supporting snapshots for all objects. (builtins, renamed classes, dynamically created types, ...)

What do you think?

Agreed. First solution seems acceptable.
I switched over my code to use this branch and was able to reduce my comparison code considerably. I still needed to tweak the built outputs to remove EPUB/PDF metadata before doing the comparison, which meant that I had  to extract and compare the individual contents (extract EPUB archive files, convert PDF to individual pages, etc.) and also check for new/missing files, instead of a direct comparison, but I think its reasonable to expect this to be something the user should do.
I think this moves things far enough to be more useful to more people and open up additional scenarios to explore in the future, but allows me to solve for my use case now.
-Thanks.

In regards to epub metadata that changes every build due to the date, that isn't something that this library can solve. (Perhaps freezegun could help you?
In regards to PDF, why do you still need to convert to individual pages? For easier diffing? Instead of checking for new/missing pages yourself, this is just the case to use assert_match_dir.
I'll merge the branch into the library soon.

Actually, I just changed my code to use assert_match_dir and it worked fine. I guess those type hints are really just hints.

I updated the type hint in the branch. Perhaps you were looking at the master branch type hints?

I don't worry about the normalization too much. They are limited in number and I try to drop in placeholders that make it very clear what is going on. That in addition to inspecting the diffs closely. But if I were new to a large project, I could see the potential for some confusion. This is just a problem that is hard to avoid with dates being so prevalent in logs, stdout, etc. (But the tool/fixture you mentioned earlier sounds great for reducing that problem).
As for custom comparitors, I could see the benefit for the cases that I have been working with, in as much as having specific PDF and EPUB comparitors that could be shared with others and between project could make things easier. But as you said many people may want to handle that logic themselves to ensure its not doing the wrong thing.  I'm trying to think of other scenarios, but between bytes and string, I think a user is pretty much unblocked.
The dataclass scenario is also interesting I think, but that might be beyond the scope of this project. I always looked at snapshots as a quick and dirty way to compare output (files or stdout). Anything more than that and I would likely start doing the comparison myself inside the test code. That's not to say having a library available to do that would not be helpful, but there may already be existing solutions for that and/or that may be a level of scope expansion that doesn't fit with simple snapshots.
So, I guess at this point I'd classify the custom comparitor as a nice to have.


Default Wikipedia Bridge partially broken

Describe the bug
The default wikipedia bridge causes the following error when the languages Dutch or German are selected, the others work fine:

Bridge encountered an unexpected situation! (18473)
Today'sfeatured article from de.wikipedia.org was unable to receive or process the remote website's content! Error message:Call to a member function find() on nullQuery string:action=display&bridge=Wikipedia&language=de&subject=tfa&fullarticle=on&format=AtomVersion:dev.2020-02-26`

To Reproduce
Steps to reproduce the behavior:
Select German or Dutch as language.
I found it to be the same on other public instances example
Expected behavior
The same that would happen with the other languages …

Ping @LogMANOriginal

I was looking into this @em92 .
Yes, this issue is still there, so the bridge seems to be broken (at least partially) for at least a year. Still, there was only 1 issue reported, which may indicate the usage of the bridge.
The bridge can do 2 things: "Featured Article" and "Did you know..". The "Featured article" actually has it's own RSS feed from wikipedia, available in all languages that support it:
English:  https://en.wikipedia.org/w/api.php?action=featuredfeed&feed=featured&feedformat=atom
German: https://de.wikipedia.org/w/api.php?action=featuredfeed&feed=featured&feedformat=atom
etc.
The "Did you know.." is tricky. It's not automatically generated content that has the same endpoint in the API or even in wording anywhere. It's a manually produced list (with responsible people for each day and so on... suuuper manual effort) that is updated by a bot and then embedded into the main page. I could not find a non-individual-language-site-scraping mechanism to get this data.
This leaves us with 2 options: Fix the bridge and maintain 10+ individual sites to scrape, only for the "Did you know" entries (as the featured article can be retrieved through the API) or just flat out kill the bridge (which seems to not be used a lot since parts of it are broken for a year and a half :D ).
50% of it is supported natively by wikipedia and the other 50% will need a high level of maintenance and individual code for each language.
Thoughts?

Fixed in https://github.com/RSS-Bridge/rss-bridge/pull/2167


Autofetch user skin from ely.by after player reconnect

Step to reproduce:

Set skin type in config to ely.by
Join server
Leave server
Change skin in ely.by account
Join server

Excepted behavior:
Skin should change on server
Real behavior:
Nothing happens

This is the intended behavior.
Automatic fetching works only if player does not have skin set (e.g. when player joins offline server for the first time or if they reset their skin using /skin reset).
If you want to update your skin you should use command /skin refresh, which will refetch your skin from ely.by. Note that it takes couple of minutes for ely.by to actually update your skin.


Move the role assignment to the ARM template and fix api versions

Move the role assignment to the ARM template.
Fix the api versions for ManagedIdentity and Authorization.
TODO: End to end tests for user assigned identity. With the move to ARM we should be able to get the e2e flow through for the user assigned identity. Add it once the ARM template starts working.

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

[ ] documentation
[ ] unit tests
[ ] tested backward compatibility (ie. deploy with previous version, upgrade with this branch)

Release note:

cc @khenidak

Could you link the doc for the two api versions to the PR? 2015-08-31-PREVIEW for Managed Identity seems pretty old

@kkmsft  Recall the issue we had around system-assigned msi for VMSS. We ended up defaulting a value for UserAssignedID if UseManagedIdentity is enabled by the user. See here: https://github.com/Azure/acs-engine/pull/3769/files#diff-b675d85a0a0ab84d3405eb458423bf67R317
I see the k8sConfig.UserAssignedID assignment has been removed from deploy.go. In this case, this logic needs to be updated:
https://github.com/Azure/acs-engine/blob/master/pkg/acsengine/template_generator.go#L351-L357 such that if we are using VMSS, then we default a value for UserAssignedID if UseManagedIdentity is enabled.

@kkmsft Any updates on this PR?

Its ready for review (pending the merge from the recent changes and the multi master VMA scenario which I have not tried yet). Working on the e2e tests after which I will remove the WIP tag. @tariq1890 - please do let me know if you have any comments from there review.

@kkmsft Thanks for letting me know. I'll remove the WIP tag then :)

@ritazh @tariq1890 : Have updated the review with the templates for e2e and also addressed review comments. PTAL.

@kkmsft There are failing UTs. Could you have a look at that?

@tariq1890 : so the UT which is failing is talking about code coverage. The additions in this are mostly template changes, there is some code rearrangement - from the deploy to default, but otherwise nothing new which is UT able. Is there a way to do UTs for template changes too ? I wonder how the coverage has come down ? Any ideas ?

@kkmsft That is actually just name of the make routine. If you see the logs you will see the test errors.
--- FAIL: TestAssignKubernetesParameters (10.11s)
    params_k8s_test.go:34: Loading file testdata/userassignedidentity/vmas/kubernetes-vmas-multimaster.json got error: missing Properties.MasterProfile.DNSPrefix
    params_k8s_test.go:34: Loading file testdata/userassignedidentity/vmas/kubernetes-vmas.json got error: missing Properties.MasterProfile.DNSPrefix
    params_k8s_test.go:34: Loading file testdata/userassignedidentity/vmss/kubernetes-vmss.json got error: missing Properties.MasterProfile.DNSPrefix

@kkmsft Thanks for the patience. Changes look good . LGTM pending one more comment.


LVGL9 example

Basic instructions for LVGL 9 example. Similar but not identical to LVGL 8.

I have tested this and it works just fine with the lvgl Arduino library version 9.0.0.


how to  convert parameters  dtype from float32 to float64 in gluon?

I need to do this because model produce very small values, and float32 is not suitable in
this case, Does anyone who has any ideas about convert float32 parameter to float64 in gluon?

Cast data to float64, and the corresponding weights in model will be initialized to float64 accordingly once you call net(x)
Or there's per parameter function cast: https://mxnet.incubator.apache.org/api/python/gluon/gluon.html?highlight=parameterd#mxnet.gluon.Parameter.cast

@piiswrong @ry @pluskid

Similar to https://github.com/apache/incubator-mxnet/issues/8799

@zhaoningning Hello, do you still experience this issue? If so, would you please provide some example scripts to reproduce your issue? Thanks!

I could reproduce this error using the following example from #8799. I will work on this issue.
import mxnet as mx
import numpy as np
from mxnet import autograd

def crit_func(a):
    q, l = mx.nd.linalg.gelqf(a)
    # Could as well write _, l = mx.nd.linalg.gelqf(a)
    # This circumvents the issue, but is highly obscure:
    #bogus = mx.nd.BlockGrad(q) * 0.0
    #return mx.nd.sum(l) + bogus
    return mx.nd.sum(l)

ctx = mx.cpu()

dtype = np.float32
a32 = mx.nd.random.normal(shape=(2, 3), ctx=ctx, dtype=dtype)
a32.attach_grad()
with autograd.record():
    crit32 = crit_func(a32)
    print ('crit32 = %f' % crit32.asscalar())
    crit32.backward()
    print ('grad32\n', a32.grad.asnumpy())

dtype = np.float64
a64 = mx.nd.Cast(a32, dtype=dtype)
a64.attach_grad()
with autograd.record():
    crit64 = crit_func(a64)
    print ('crit64 = %f' % crit64.asscalar())
    crit64.backward()
    print ('grad64\n', a64.grad.asnumpy())

@zhaoningning Could you provide a small script of your issue. I would like to verify my fix since your description of the issue is not exactly the same as #8799. Thanks!

@zhaoningning are you able to provide a script reproducing the issue?

@apeforest @lupesko  sorry,I can not reproduce this issue after such a long time...

@zhaoningning Sorry for the delayed response. I believe your issue should have been fixed by #12290 if not already by other PRs. We will be responsive to issues filed in the future. Thank you for your continuing support of MXNet.

@sandeep-krishnamurthy This issue has been fixed. Please close this issue.


Use stdlib functions for file & path operations

I set out to remove these imports and use replacements from stdlib:

java.io.File
java.nio.file.Files
java.nio.file.Paths

I was mostly successful, held back by the detekt-gradle-plugin being on API version 1.4, and a couple of stdlib functions which still require an opt in. I chose not to use the opt in functions until they're stable, hopefully in Kotlin 1.9 if not before.
I recommend reviewing by individual commit as I've broken up the changes into logical chunks.

@Goooler they're already covered?
https://github.com/detekt/detekt/pull/5754/files#diff-1d7a1cd6085118b76e5689c6c2bdd234c831a4bc566dfbb946975b90c1b2585e

You are right, just see it.

Great work!


Social media: google plus share link not working properly

Clicking on the google plus social media link redirects to the google plus post page but yields a brief "That link isn't valid. Please check the link and try again." error message.

Google plus would not be able to get to the QA server.


Update docs links

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.006%) to 95.073%

Totals

Change from base Build<PHONE_NUMBER>:
0.006%

Covered Lines:
849

Relevant Lines:
893

💛  - Coveralls

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.006%) to 95.073%

Totals

Change from base Build<PHONE_NUMBER>:
0.006%

Covered Lines:
849

Relevant Lines:
893

💛  - Coveralls


Re-enable arbitrary LA access on staging

In the long term, we want to use staging purely within our CI pipeline.
However, various parts of the product team rely on having access to
staging for UR and demo purposes at the moment, and until we have found
an alternative solution we need to stop enforcing the LA allowlist on
staging.

Review app deployed to https://teaching-vacancies-review-pr-2953.london.cloudapps.digital


use pip-compile-multi and flit_core instead of pdm

I used this project to test switching to PDM to manage the development environment, lock dependencies, and run commands. However, it wasn't significantly better for our use case over using pip-compile-multi to manage requirements/*.in to *.txt files. Instead of going back to setuptools, I've used flit_core as the build backend, as it's simpler and faster.
This also enables PyPI's trusted publisher authentication.

If you already have a dev env using pdm, you'll want to delete any local .venv and .tox folders, then create a new venv:
$ rm -r .tox .venv
$ python3 -m venv .venv
$ . .venv/bin/activate
$ pip install -r requirements/dev.txt && pip install -e .


Failed to verify bitcode in LocalNotificationsPlugin.framework/LocalNotificationsPlugin:\nerror: Bundle only contains bitcode-marker /var/folders/4d/zcq9x1910f9_7vk9_v8q6xp8jqxkx7/T/IDEDistributionOptionThinning.Jj0/Payload/appmedical.app/Frameworks/LocalNotificationsPlugin.framework/LocalNotificationsPlugin (armv7)

Error description (IDEDistribution.standard.log):
appmedical.app/Frameworks/TNSWidgets.framework/TNSWidgets arm64 ->
2019-05-10 13:38:35 +0000  error: Failed to verify bitcode in LocalNotificationsPlugin.framework/LocalNotificationsPlugin:
error: Bundle only contains bitcode-marker /var/folders/4d/zcq9x1910f9_7vk9_v8q6xp8jqxkx7/T/IDEDistributionOptionThinning.Jj0/Payload/appmedical.app/Frameworks/LocalNotificationsPlugin.framework/LocalNotificationsPlugin (armv7)

and:
2019-05-10 13:38:38 +0000  /Applications/Xcode.app/Contents/Developer/usr/bin/ipatool exited with 1
2019-05-10 13:38:38 +0000  ipatool JSON: {
    alerts =     (
                {
            code = 3299;
            description = "Configuration issue: platform AppleTVSimulator.platform doesn't have any non-simulator SDKs; ignoring it";
            info =             {
            };
            level = WARN;
        },
                {
            code = 3299;
            description = "Configuration issue: platform WatchSimulator.platform doesn't have any non-simulator SDKs; ignoring it";
            info =             {
            };
            level = WARN;
        },
                {
            code = 3299;
            description = "Configuration issue: platform iPhoneSimulator.platform doesn't have any non-simulator SDKs; ignoring it";
            info =             {
            };
            level = WARN;
        },
                {
            code = 0;
            description = "Failed to verify bitcode in LocalNotificationsPlugin.framework/LocalNotificationsPlugin:\nerror: Bundle only contains bitcode-marker /var/folders/4d/zcq9x1910f9_7vk9_v8q6xp8jqxkx7/T/IDEDistributionOptionThinning.Jj0/Payload/appmedical.app/Frameworks/LocalNotificationsPlugin.framework/LocalNotificationsPlugin (armv7)\n\n";
            info =             {
            };
            level = ERROR;
            type = "malformed-payload";
        },
                {
            code = 0;
            description = "Failed to verify bitcode in TNSWidgets.framework/TNSWidgets:\nerror: Bundle only contains bitcode-marker /var/folders/4d/zcq9x1910f9_7vk9_v8q6xp8jqxkx7/T/IDEDistributionOptionThinning.Jj0/Payload/appmedical.app/Frameworks/TNSWidgets.framework/TNSWidgets (armv7)\n\n";
            info =             {
            };
            level = ERROR;
            type = "malformed-payload";
        }
    );
}
2019-05-10 13:41:39 +0000 [MT] Canceled distribution assistant

@AquilesOliveira Did you ever figure this out?


FeatureStore and PropertyStore using REST API client

A use case I have in mind for FF4j is to integrate our Java apps with a single central FF4J server. I don't want to be exposing database, redis, filesystem information to these client apps. Just HTTP. So, my java app should be able to load FF4j ff4j = new FF4j("http://ff4j.example.com");
However, this is currently not possible, the closest would be to load the XML Export file...
URL xmlURL = new URL("http://localhost:8080/ff4j-web-console/api/export");
InputStream exportXML = url.openStream();
ff4j = new FF4j(exportXML);

I have used the Swagger definition from the ff4j-sample-springboot-starter app, and generate a Java client SDK from the swagger online editor. I've then implemented a RESTFeatureStore, and a RESTPropertyStore which uses this client SDK generated code.
With this in place, my client java app can then load FF4j via REST API url.
URL restURL = new URL("http://localhost:8080");
ff4j = new FF4j(restURL);

Since the String param class init was already taken by XML file path for the InMemory store, I pass a URL object.
Current known limitation of this implementation of the REST Store is that the generate SDK code is very ugly, but its simple to generate using a swagger definition, should updates need to occur in the future. Also, at the moment, its hard to properly unit test the REST store, because it depends on a REST API being available. Maybe I should delete the RESTFeatureStoreTest.java, until then. Even though there are 10 sample projects that provide a REST API, I don't know how to quickly stand something up for the test. Also, maybe I should add a layer of caching to the REST store, so that it doesn't make a new GET for every call, but perhaps allow it 10s-5m before calling again.
Thank you.

First of all thank you for all your work. Your use case is indeed a good idea.
To implemented it I created in a FeatureStore and PropertyStore wrapping an HTTP client (for both Jersey1x and 2x 2 ways to expose the API but not for the spring MVC)
https://github.com/clun/ff4j/tree/master/ff4j-webapi-jersey2x/src/main/java/org/ff4j/web/jersey2/store
Based on what you provided I will create a ff4j-store-clienApi module. I will probably use the new client framework like hystrix, feign, okHttp or retrofit.

Many thanks for your response, and for already having created the Jersey rest client. Jersey generated client code is way better than the mess I've auto-generated above. What you've built now, is enough for one to use the use-case I've mentioned, external apps with zero knowledge of backends.
What I've done, add dependencies to client java app pom.xml
<dependency>
    <groupId>org.ff4j</groupId>
    <artifactId>ff4j-core</artifactId>
    <version>1.6.5</version>
</dependency>
<dependency>
    <groupId>org.ff4j</groupId>
    <artifactId>ff4j-webapi-jersey2x</artifactId>
    <version>1.6.5</version>
</dependency>

And then, create a new FF4j, and set the HTTP versions of the Feature and Property stores.
import org.ff4j.FF4j;
import org.ff4j.web.jersey2.store.FeatureStoreHttp;
import org.ff4j.web.jersey2.store.PropertyStoreHttp;

FF4j ff4j = new FF4j();
String ff4jAPI = "http://localhost:8080/api/ff4j";
ff4j.setFeatureStore(new FeatureStoreHttp(ff4jAPI));
ff4j.setPropertiesStore(new PropertyStoreHttp(ff4jAPI));

boolean isEnabled = ff4j.exist("test") && ff4j.check("test");
System.out.println("feature [test] enabled?: " + isEnabled);

I'd say that is fine. Though it would be convenient, and a simpler integration if the next version of FF4j had a convenient constructor for new FF4j() that accepted a URL, and set the HTTP stores.

I agree with your ideas and the constructor. Still it will required extra dependencies storeHttp, will see how to make this optional.
I would also show know that you can secured the API using ApiKey and/or userpassword. Have a look here https://github.com/clun/ff4j/issues/245, I will update the documenation.


Bug: Timeout only active is user presses Toggle Privileges in dock item first, then app

When a user presses the app normally, pop up for reason shows however no timeout is set.
If a user presses Toggle Privileges as user, nothing happens. However on the next button press, countdown is set

After further investigating, these symptoms looked to be caused by the following chain:

Privileges Dock Tile is started by pressing right click -> Toggle Privileges
Privileges isn't able to update because it needs a reason
However an observer was added using<EMAIL_ADDRESS>in the Dock Tile
Thus the next normal run of Privileges now has the observer added

Unfortunately I am not too familiar with Parent to Dock Tile communication, however Apple does provide docs on the matter:

https://developer.apple.com/documentation/appkit/nsdocktile

For a work around we could do the following:

Implement a timeout in the app itself, not just dock tile
Implement a launch daemon that listens for when Privileges is started

When raised to admin, have LD start a count down to lower itself

Will need to investigate further on additional alternatives

After further investigating, we seem to be unable to update dock information due to Privileges using a Helper XPC service to change the user. This means that calling [[NSApplication sharedApplication] dockTile]; will not work as it fails to grab the core app's dock tile.
With this, we'll need to setup a Launch Daemon/Agent (or in the helper itself) that keeps track of time and changes privileges when needed.


add bulkInsert

#27

This PR is now obsolete as bulk inserts are supported by the insert method. Thanks for submitting in any case!


Fixissue5784 by adding checks for circuit size

Summary
Fixes issue #5784
Details and comments
This issue was present in the latex, text and mpl drawers in the visualization library. Primarily added checks for the size of the circuits that were being passed in the drawers. The singleton registers, now, do not contain indices as was mentioned in the original issue.
Here are some screenshots of the expected results -
from qiskit import *
q2 = QuantumCircuit(3,2)
q  = QuantumCircuit(1)
q.h(0)
q.measure_all()
q2.x([0,1])
q2.cx(0,2)
q2.measure(0,1)

q.draw(output='mpl',cregbundle=False,filename = "mpl_circ_1.JPG")
q.draw(output='mpl',filename = 'mpl_circ_2.JPG')
q2.draw(output='mpl',filename = 'mpl_circ_3.JPG')

q2.draw(output='text', filename = "text_circ_3.JPG")
q.draw(output='text',filename = "text_circ_1.JPG")
q.draw(output='text',cregbundle=False,filename = "text_circ_2.JPG")

q.draw(output = 'latex', cregbundle = True)
q.draw(ouput = 'latex', cregbundle = False)
q2.draw(output = 'latex')

@TheGupta2012 Just checking to see if you are still working on this. Thanks.

@TheGupta2012  as we haven't heard from you I will reassign to @enavarro51 as he has asked to pick it up. If you would still like to work on it please reach out to Ed about continuing to work on it together 😄

@TheGupta2012 as we haven't heard from you I will reassign to @enavarro51 as he has asked to pick it up. If you would still like to work on it please reach out to Ed about continuing to work on it together 😄

I am extremely sorry @javabster and @enavarro51, I haven't been able to take out the time for the past three weeks due to my college exams and tests. @enavarro51 you may continue to work on the fix and as soon as I am able to, I shall also contribute to the same.
Again, really sorry for the delay..

@TheGupta2012 Thanks for the reply. No problem. We know everyone is busy with other things. I will start working on this in the next few days. I think I already have the items @TharrmashasthaPV reviewed above taken care of. The big task is fixing all the text drawer tests. There have been some changes merged into main that require some fixing.
I'll just move along with it and if you have some time just let me know. I'll invite you as a collaborator on my repo when you're ready.


Add terraform legacy version as used by tfenv

Add comprehension of the tfenv version file format.

@nikolay Mind taking a look?


HBASE-28921 Skip bundling hbase-webapps folder in jars (#6368)

Backports https://github.com/apache/hbase/pull/6368

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 38s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  0s

codespell was not available.

+0 :ok:
detsecrets
0m  0s

detect-secrets was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

_ branch-3 Compile Tests _

+0 :ok:
mvndep
0m 13s

Maven dependency ordering for branch

+1 :green_heart:
mvninstall
3m 41s

branch-3 passed

+1 :green_heart:
compile
5m  4s

branch-3 passed

+1 :green_heart:
spotless
0m 52s

branch has no errors when running spotless:check.

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 11s

Maven dependency ordering for patch

+1 :green_heart:
mvninstall
3m 34s

the patch passed

+1 :green_heart:
compile
5m 21s

the patch passed

+1 :green_heart:
javac
5m 21s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
xmllint
0m  0s

No new issues.

+1 :green_heart:
hadoopcheck
13m  5s

Patch does not cause any errors with Hadoop 3.3.6 3.4.0.

+1 :green_heart:
spotless
0m 52s

patch has no errors when running spotless:check.

_ Other Tests _

+1 :green_heart:
asflicense
0m 26s

The patch does not generate ASF License warnings.

41m 51s

Subsystem
Report/Notes

Docker
ClientAPI=1.43 ServerAPI=1.43 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6376/1/artifact/yetus-general-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/6376

Optional Tests
dupname asflicense javac codespell detsecrets xmllint hadoopcheck spotless compile

uname
Linux 3fda4c5c922b 5.4.0-1103-aws #111~18.04.1-Ubuntu SMP Tue May 23 20:04:10 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-3 / 3ccb128dac4e02f5d7dccb5f2b5f08fe7fd830d1

Default Java
Eclipse Adoptium-17.0.11+9

Max. process+thread count
84 (vs. ulimit of 30000)

modules
C: hbase-server hbase-thrift hbase-rest U: .

Console output
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6376/1/console

versions
git=2.34.1 maven=3.9.8 xmllint=20913

Powered by
Apache Yetus 0.15.0 https://yetus.apache.org

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 27s

Docker mode activated.

-0 :warning:
yetus
0m  3s

Unprocessed flag(s): --brief-report-file --spotbugs-strict-precheck --author-ignore-list --blanks-eol-ignore-file --blanks-tabs-ignore-file --quick-hadoopcheck

_ Prechecks _

_ branch-3 Compile Tests _

+0 :ok:
mvndep
0m 11s

Maven dependency ordering for branch

+1 :green_heart:
mvninstall
3m  1s

branch-3 passed

+1 :green_heart:
compile
1m 39s

branch-3 passed

+1 :green_heart:
javadoc
1m 13s

branch-3 passed

+1 :green_heart:
shadedjars
5m 36s

branch has no errors when building our shaded downstream artifacts.

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 12s

Maven dependency ordering for patch

+1 :green_heart:
mvninstall
2m 55s

the patch passed

+1 :green_heart:
compile
1m 40s

the patch passed

+1 :green_heart:
javac
1m 40s

the patch passed

+1 :green_heart:
javadoc
1m 13s

the patch passed

+1 :green_heart:
shadedjars
5m 34s

patch has no errors when building our shaded downstream artifacts.

_ Other Tests _

+1 :green_heart:
unit
211m 28s

hbase-server in the patch passed.

+1 :green_heart:
unit
6m 42s

hbase-thrift in the patch passed.

+1 :green_heart:
unit
3m 49s

hbase-rest in the patch passed.

250m 22s

Subsystem
Report/Notes

Docker
ClientAPI=1.43 ServerAPI=1.43 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6376/1/artifact/yetus-jdk17-hadoop3-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/6376

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux 46dd8ab70162 5.4.0-1103-aws #111~18.04.1-Ubuntu SMP Tue May 23 20:04:10 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-3 / 3ccb128dac4e02f5d7dccb5f2b5f08fe7fd830d1

Default Java
Eclipse Adoptium-17.0.11+9

Test Results
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6376/1/testReport/

Max. process+thread count
5098 (vs. ulimit of 30000)

modules
C: hbase-server hbase-thrift hbase-rest U: .

Console output
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6376/1/console

versions
git=2.34.1 maven=3.9.8

Powered by
Apache Yetus 0.15.0 https://yetus.apache.org

This message was automatically generated.

Stale


Color scales: gradient-like interpolation across multiple color stops

Currently we have Color.range() and friends which only interpolates between 2 colors. I just had to write this for a color component I’m writing (<color-slider>), and it was no fun:
colorAt (p) {
	let bands = this.scales?.length;

	if (bands <= 0) {
		return null;
	}

	// FIXME the values outside of [0, 1] should be scaled
	if (p >= 1) {
		return this.scales.at(-1)(p);
	}
	else if (p <= 0) {
		return this.scales[0](p);
	}

	let band = 1 / bands;
	let scaleIndex = Math.max(0, Math.min(Math.floor(p / band), bands - 1));
	let scale = this.scales[scaleIndex];
	let color = scale((p % band) * bands);

	return color;
}

And this is just equally spaced color stops. I dread to think about implementing the general case.
Which is why I think Color.js should provide it 😁
I’m thinking of something like:
/**
  @param {Array<Color | {color: Color, at: number}>} stops
  @param {RangeOptions} [options]
 */
function colorScale(colors: Array<Color>, options): function;

Thoughts?

I think gradients across multiple color stops is a good idea. I know I implemented this behavior in ColorAide, so I definitely think it is useful.

Do you plan on supporting adjusting stop position? It may be something to consider upfront if this is desired for the future.

As soon as we move from linear two-stop interpolation we need to consider how we want to handle smooth curves and curve continuity (regardless of whether we also need to support piecewise linear with bolted-on fix-ups like midpoint position, ease-in ease-out, and the like which are crude approximations to true, easily-animatable multi-point curves).
Ideally, multi-point smooth curves that can be

constrained to lie within an arbitrary polyhedron,
avoid excessive overshoot

As soon as we move from linear two-stop interpolation we need to consider how we want to handle smooth curves and curve continuity (regardless of whether we also need to support piecewise linear with bolted-on fix-ups like midpoint position, ease-in ease-out, and the like which are crude approximations to true, easily-animatable multi-point curves).
Ideally, multi-point smooth curves that can be
constrained to lie within an arbitrary polyhedron,
avoid excessive overshoot

I'll let others define the API to introduce such functionality and I'll speak generally to multi-point smooth curves.
Generally, I like the approach that Culori employed using cubic splines: https://culorijs.org/api/#interpolatorSplineBasis. The one thing I think Culori did not address is what to do with undefined channels when applying these approaches. I will speak to how I decided to handle such things.
Using splines requires us to broaden the definition of what a piece is. While you must handle 2 color and 3 color cases, splines need a bit more context and ideally should take into account 4 colors if available. This will help shape the curve smoothly through the colors.
Personally, I found undefined handling for the current linear interpolation insufficient considering the requirements of 4 colors (if available) for splines. In order to settle on what I found to be a reasonable solution, I needed to adjust undefined channel handling. To do this, undefined channels, for anything other than piecewise linear, are evaluated throughout the entire chain of colors, essentially filling in any gaps and holes before interpolation takes place. This is currently done by using simple linear interpolation to create points between the defined channels. Such gaps are considered and filled before easing functions are applied.

Undefined channels not between two defined channels simply take on the value of the defined channel on either its left or right.

Using this logic as a basis, splines were implemented on top of that. Overshoot is dependant upon the spline approach chosen. I'm not sure any approach perfectly eliminates overshoot, but monotone at least will keep it within the bounds of the data.

Extrapolation beyond the endpoints is handled in a linear fashion, at least in my implementation.
Stops and easing functions are generally handled as they were previously in normal linear, piecewise interpolation. Stops are applied to the current color stops, and easing functions adjust the progress between the two colors currently under evaluation, even if that evaluation is looking past those two colors to shape the curve in the spline.
Hopefully, some of this is helpful for considering what direction Color.js should take.

I think this has a fair amount of overlap with https://github.com/color-js/color.js/issues/18, unless I'm misunderstanding.
I would be very interested in a convenience function (or just a flexible interpolation API) to interpolate over a custom domain (instead of fixed [0-1]) similar to chroma.js. A real world example being mapping colors to temperature, and then being able to easily call colorScale(myTemperature). (see: https://github.com/color-js/color.js/issues/18#issuecomment-1217391633)

I think custom domains would be useful. I think this could easily be done now with a simple external function that you pass your value through before passing it to the interpolation function that coerces a defined domain to 0 - 1. It doesn't have to be implemented directly in Color.js, though I'm sure it would be appreciated if the domain could be specified in range or mix and then just handled automatically.


New issue with Joplin 2.9.17 freezing

Hello. I've noticed that when using the macos theme plugin v1.3.5 with the new version of Joplin 2.9.17, clicking the dropdown arrow next to a folder causes Joplin to freeze/crash. This issue occurs even after reinstalling the plugin and disabling all other plugins, and this issue resolves when I disable the macos theme plugin.

I can confirm that I'm seeing the same behaviour and problem, using an M1 Mac with Ventura, and the same versions of the software and the plugin. I've disabled the plugin for now, but I'd love to be able to enable it again!

That is superweird. I'm on the same platform but can't reproduce the issue with the same version of Joplin. Could it be that a conflict with another plugin is causing the issue, like here is the case?

Same issue for me.
If I navigate in the tree and I randomly select notebooks it'll eventually freeze the UI. I'm still trying to understand on what event it freezes.
Joplin 2.9.17 (prod, darwin)

Client ID: ccb2807a53db48afae96a22577554662
Sync Version: 3
Profile Version: 41
Keychain Supported: Yes

Revision: a84a8e7

Could it be related to the number of sub-notebooks, number of notes, or contents of the notes etc?
I am not able to reproduce this issue either, very strange..
Joplin: 2.9.17
macOS theme: 1.3.9
macOS: 13.1

Good thought, you may be on to something.
I tried opening a notebook with 7 notes and it worked fine, but when I tried the dropdown arrow on my large notebook containing 50+ notes w/ images, the error occurred again.

Had the same problem (sudden freezes, where i had to kill the application) with Joplin 2.9.17 (prod, win32).
This is what I did:

I disabled or removed macOS theme extension
Deleted all Emojis I added to folders
reinstalled macOS theme

Haven't had a freeze for a couple of days so far.
Hope this helps.

Sorry everyone, but I have to close this issue. While the theme may play a role, I think it isn't causing the actual issue at hand, since the theme is doing very little other than injecting CSS. If you find new hints or you think otherwise, feel free to comment or reopen! Thanks for investigating!

The problem is still there with Joplin 2.10.6 (prod, darwin) without any plugins
I tested on

Windows 10 (10.0.19045) and macOS Ventura 13.0.1
Different notebooks configurations

It seems that UI freezes when I expand group of notebooks with emojis


Removed validate-sample workflow

Removed validate-sample.yml due to constant failure. More info: https://github.com/pnp/cli-microsoft365/pull/6027#issuecomment-2232938893

Merged manually, thank you!


arm: stm32: Data cahce (dcache) management update

This patch series fixes problem with enabling at the same time STM32H7's Data cache and CONFIG_NOCACHE_MEMORY option.
On the STM32 it shall be possible to use memory buffers with __nocache attribute with data cache being enabled.
This is not the best possible solution - one could fix cache coherency issues on the DMA driver level, but allows avoiding
performance penalty when data cache is disabled.
This solution has been tested on nucleo_h743zi with littlefs sample program.
west build -p always -b nucleo_h743zi ./zephyr/samples/subsys/fs/littlefs -DCONF_FILE=prj_blk.conf
This patch series comply with point '2.1' of https://github.com/zephyrproject-rtos/zephyr/issues/36471

I don't think we should go with this solution as this is globally the same as #35165 which was already rejected

@erwango The #35165 has been already accepted and pulled - the #ifndef CONFIG_NOCACHE_MEMORY is already present in soc/arm/st_stm32/stm32h7/soc_m7.c.
And the current situation (as it is now in Zephyr repo's - main branch) is IMHO just wrong and reduces system performance considerably. Customers are really concerned about this.
With this patch we are going one small step forward - with having DCache enabled with DMA running with __nocache attribute for crucial buffers, which are really small.
Some STM32 drivers do require defining the  CONFIG_NOCACHE_MEMORY and as a result, now the DCache is disabled for the whole system.
This patch allows developers to use DCache and also check if their __nocache defined DMA buffers also are handled correctly. Until Zephyr gains proper handling of cache coherency, this would reduce the possible performance degradation (as it is now noticeable by some Zephyr users).

@erwango The #35165 has been already accepted and pulled - the #ifndef CONFIG_NOCACHE_MEMORY is already present in soc/arm/st_stm32/stm32h7/soc_m7.c.

Ok, this is not strictly exact, but in the end you're right.
#35165, which was affecting F7 was indeed rejected, but some time after, #37716, targeting H7 and doing the same exact thing was merged.
So, I do agree a change is required to offer possibility to use DCache and nocache memory sections.
But then, I think DCACHE_DISABLE should be default n and enabled only when required by drivers (like uart async api, cf tests/drivers/uart/uart_async_api/boards/nucleo_h723zg.conf)
Also, I'd suggest to extend to other M7 based cores, at least on STM32, ie STM32F7.

@erwango The #35165 has been already accepted and pulled - the #ifndef CONFIG_NOCACHE_MEMORY is already present in soc/arm/st_stm32/stm32h7/soc_m7.c.

Ok, this is not strictly exact, but in the end you're right. #35165, which was affecting F7 was indeed rejected, but some time after, #37716, targeting H7 and doing the same exact thing was merged. So, I do agree a change is required to offer possibility to use DCache and nocache memory sections. But then, I think DCACHE_DISABLE should be default n and enabled only when required by drivers (like uart async api, cf tests/drivers/uart/uart_async_api/boards/nucleo_h723zg.conf) Also, I'd suggest to extend to other M7 based cores, at least on STM32, ie STM32F7.

The problem here is that we already have many systems with DCache disabled when CONFIG_NOCACHE_MEMORY is enabled. This patch series tries to not introduce regressions as much as possible.
It would be the system integrator responsibility to enable the DCACHE explicitly (i.e. CONFIG_DCACHE_DISABLE=n) when he/she is also planning to use nocache memory DMA buffers (as it is with mine nucleo board).
However, I don't mind to follow your guidelines if other developers (i.e. @de-nordic @Laczen @FRASTM @ABOSTM @nvlsianpu ) agree about this approach.

@erwango The #35165 has been already accepted and pulled - the #ifndef CONFIG_NOCACHE_MEMORY is already present in soc/arm/st_stm32/stm32h7/soc_m7.c.

Ok, this is not strictly exact, but in the end you're right. #35165, which was affecting F7 was indeed rejected, but some time after, #37716, targeting H7 and doing the same exact thing was merged. So, I do agree a change is required to offer possibility to use DCache and nocache memory sections. But then, I think DCACHE_DISABLE should be default n and enabled only when required by drivers (like uart async api, cf tests/drivers/uart/uart_async_api/boards/nucleo_h723zg.conf) Also, I'd suggest to extend to other M7 based cores, at least on STM32, ie STM32F7.

The problem here is that we already have many systems with DCache disabled when CONFIG_NOCACHE_MEMORY is enabled. This patch series tries to not introduce regressions as much as possible. It would be the system integrator responsibility to enable the DCACHE explicitly (i.e. CONFIG_DCACHE_DISABLE=n) when he/she is also planning to use nocache memory DMA buffers (as it is with mine nucleo board).
However, I don't mind to follow your guidelines if other developers (i.e. @de-nordic @Laczen @FRASTM @ABOSTM @nvlsianpu ) agree about this approach.

Gentle PING on this patch set ....

However, I don't mind to follow your guidelines if other developers (i.e. @de-nordic @Laczen @FRASTM @ABOSTM @nvlsianpu ) agree about this approach.

I'd go for deactivating it by default and add a note in the release note to inform users.

However, I don't mind to follow your guidelines if other developers (i.e. @de-nordic @Laczen @FRASTM @ABOSTM @nvlsianpu ) agree about this approach.

I'd go for deactivating it by default and add a note in the release note to inform users.

@erwango
So you want to go with DCACHE_DISABLED=n by default?
Shouldn't, also, the option be dependent on CACHE_MANAGEMENT and disable DCACHE_LINE_SIZE_DETECT and DCACHE_LINE_SIZE when DCACHE_DISABLED=n?
Wouldn't we maybe go further add something like 'HAS_HW_DCACHE', that would be selected by platform and that would then show the DCACHE_* options?
Maybe we can, instead of DCACHE_DISABLED=n, have DCACHE=y defined like
config DCACHE
    bool ...
    default y if HAS_HW_DCACHE

And it would be y for platforms that define the HAS_HW_DCACHE (or whatever) and user projects could still override it to n,

However, I don't mind to follow your guidelines if other developers (i.e. @de-nordic @Laczen @FRASTM @ABOSTM @nvlsianpu ) agree about this approach.

I'd go for deactivating it by default and add a note in the release note to inform users.

@erwango So you want to go with DCACHE_DISABLED=n by default?
Shouldn't, also, the option be dependent on CACHE_MANAGEMENT and disable DCACHE_LINE_SIZE_DETECT and DCACHE_LINE_SIZE when DCACHE_DISABLED=n?
Wouldn't we maybe go further add something like 'HAS_HW_DCACHE', that would be selected by platform and that would then show the DCACHE_* options?
Maybe we can, instead of DCACHE_DISABLED=n, have DCACHE=y defined like
config DCACHE
    bool ...
    default y if HAS_HW_DCACHE

And it would be y for platforms that define the HAS_HW_DCACHE (or whatever) and user projects could still override it to n,

@de-nordic Is there any example of HAS_HW_DCACHE usage already present in Zephyr? Personally, I would opt for enabling the DCACHE by default and then, only when integrator finds issues, allow disabling it.
However, such approach could break some existing STM32H7 boards, as they run with DCACHE disabled when drivers with __nocache buffers are used.

However, such approach could break some existing STM32H7 boards, as they run with DCACHE disabled when drivers with __nocache buffers are used.

This is a good example of this non sense situation. This should be fixed. And on these ones, I don't think this should raise issues.
Where I expect issues is on drivers (well, more on applications using these drivers actually) that don't use __nocache buffers, but need some, like uart_async where DMA is used.
For these, in a first step, we can replace in tree current CONFIG_NOCACHE_MEMORY=y by CONFIG_DCACHE=n.
For sure this will have impact on out of tree users for sure, but anyhow current way of handling this on STM32H7 is wrong and should be fixed one day.

However, such approach could break some existing STM32H7 boards, as they run with DCACHE disabled when drivers with __nocache buffers are used.

This is a good example of this non sense situation. This should be fixed. And on these ones, I don't think this should raise issues. Where I expect issues is on drivers (well, more on applications using these drivers actually) that don't use __nocache buffers, but need some, like uart_async where DMA is used. For these, in a first step, we can replace in tree current CONFIG_NOCACHE_MEMORY=y by CONFIG_DCACHE=n. For sure this will have impact on out of tree users for sure, but anyhow current way of handling this on STM32H7 is wrong and should be fixed one day.

Please correct my understanding if it is wrong:

I need to introduce CONFIG_DCACHE for STM32H7 (similar to patches sent with this PR) set by default to y
All instances of CONFIG_NOCACHE_MEMORY=y shall be replaced by CONFIG_DCACHE=n
We do accept out-of-tree boards breakage - boards maintainers' are responsible for checking if those will run with DCACHE enabled.
Support for HAS_HW_DCACHE is for now skipped

Or am I missing something?

Please correct my understanding if it is wrong:

I need to introduce CONFIG_DCACHE for STM32H7 (similar to patches sent with this PR) set by default to y

Yes. Use CONFIG_DCACHE in STM32H7 soc_m7.c to protect code enabling DCache.

All instances of CONFIG_NOCACHE_MEMORY=y shall be replaced by CONFIG_DCACHE=n

Yes, for STM32H7 based boards only.

We do accept out-of-tree boards breakage - boards maintainers' are responsible for checking if those will run with DCACHE enabled.

Unfortunately, I don't see way to generate a smart warning, so I can think of only 2 ways to help out of tree users:

Add note in doc/releases/release-notes-3.1.rst
Send a mail to users/devel (I can do it if required).

Support for HAS_HW_DCACHE is for now skipped

Fine with me. Maybe @de-nordic can comment.

Or am I missing something?

We'll aslo need to get STM32F7 to also use DCACHE, but that's another story.

Please correct my understanding if it is wrong:

I need to introduce CONFIG_DCACHE for STM32H7 (similar to patches sent with this PR) set by default to y

Yes. Use CONFIG_DCACHE in STM32H7 soc_m7.c to protect code enabling DCache.

All instances of CONFIG_NOCACHE_MEMORY=y shall be replaced by CONFIG_DCACHE=n

Yes, for STM32H7 based boards only.

We do accept out-of-tree boards breakage - boards maintainers' are responsible for checking if those will run with DCACHE enabled.

Unfortunately, I don't see way to generate a smart warning, so I can think of only 2 ways to help out of tree users:
* Add note in `doc/releases/release-notes-3.1.rst`

* Send a mail to users/devel (I can do it if required).

Support for HAS_HW_DCACHE is for now skipped

Fine with me. Maybe @de-nordic can comment.

Or am I missing something?

We'll aslo need to get STM32F7 to also use DCACHE, but that's another story.

@de-nordic  Do you have any input or comments to the above plan?

@erwango @de-nordic  Gentle ping on this patch set.

@de-nordic Is that ok to get this in V3.1.0 as this is globally a bug fix for STM32H7 platfom ?

Yes, it is fine by me, but I am not in charge of the release.

@erwango - Is there any easy way to restart the Coding Guidelines / Run coding guidelines checks on patch series (PR) (pull_request) task ? As it looks like the service was not available at the moment when the CI has been started?
And the second question - would it be possible to add this PR to v3.1.0 ?
@FRASTM - Just a side note. In the document that you pointed out:
https://www.st.com/content/ccc/resource/technical/document/application_note/group0/08/dd/25/9c/4d/83/43/12/DM00272913/files/DM00272913.pdf/jcr:content/translations/en.DM00272913.pdf
Mistakes to avoid and tips: (point 4)
"Always better to use non-cacheable regions for DMA buffers. The software can use the MPU to set up a
non-cacheable memory block to use as a shared memory between the CPU and DMA."
It looks like even STM recommends using the __nocache attribute for DMA buffers, without the need to fine management of cache operations.

@erwango - Is there any easy way to restart the Coding Guidelines / Run coding guidelines checks on patch series (PR) (pull_request) task ? As it looks like the service was not available at the moment when the CI has been started?

I've restarted gh task.

And the second question - would it be possible to add this PR to v3.1.0 ?

I'm trying to


repeat error building metadata tools- fatal: reference is not a tree: b765575f51d6eaf3af296bede89a6bafd4d8e93c

is there a problem with the git repository for the metadata creator tool?
i use:
git clone https://github.com/input-output-hk/offchain-metadata-tools.git
and end up with "not a tree" error when running the final  "cabal-build-all.sh" cmd.
We are in a time crunch and building the metadata is literally the only thing holding us up.

i have no quick answer to your question, but you can use the token-metadata-creator binary from within the SPO scripts mainnet directory:
https://github.com/gitmachtl/scripts/tree/master/cardano/mainnet


add sample webapp and resource in the same application

Fixes Azure/azure-sdk-for-java#19816
Related prerequisites PR: Support web app and web api in the same application
Changelog:

Add a new sample to apply web app and web api in the same scenario.
Use the new value on_behalf_of for readme and YAML files.
Add appRoles setting description for client credentials scope.

Hi @chenrujun , please help to review together.

@chenrujun please help review this sample


#614 reorganise model docs

Description
Reorganise model docs to make it clearer which models are used by PyBaMM.
note:

this branch merges into #608  to make use of the options documentation
I think we can now get rid of the example models (reaction diffusion and simple ODE) as they don't add anything beyond the examples in the examples folder. Reaction-diffusion in particular is annoying to maintain (#615)

Fixes #614
Type of change

[x] New feature (non-breaking change which adds functionality)

Key checklist:

[ ] No style issues: $ flake8
[ ] All tests pass: $ python run-tests.py --unit
[ ] The documentation builds: $ cd docs and then $ make clean; make html

You can run all three at once, using $ python run-tests.py --quick.
Further checks:

[ ] Code is commented, particularly in hard-to-understand areas
[ ] Tests added that prove fix is effective or that feature works
[ ] Any dependent changes have been merged and published in downstream modules

will have a proper look tomorrow, but looks good. one comment: should we add refs for the li-ion models (e.g. to Scott's paper) and then in the blurb in the models docs we can say each of the pre-built models contains a ref with the model docstring?

I think the failing tests are because #608 is failing so will leave this until that is merged

isn't this being merged into #608? I'm not sure on how merging into other PRs works - do you have to merge this into 608 and then that into master, or does merging 608 into master take this along with it?

Thought #608 was also failing hence why this was failing, but looks like it's fine now.
Either order works - if we merge this into 608 first then the 608 PR will include these changes, whereas if we merge 608 into master first then (I think) this branch will merge directly into master afterwards. So go ahead and merge 608 if it's ready

@rtimms @Scottmar93 any ideas why there's that error with the DFN example? I haven't changed anything in the code specific to it

looks like #550 is failing on the same thing. this happened once before on master -- the PR was passing all tests, then after merge master was failing this notebook. but then a different PR got merged and everything was passing again, so I presumed whatever bug it was had been inadvertently fixed. weird, as #550 was passing all the tests before, and like you, nothing specific to that example has been changed...


request entity too large

Is there an existing issue for this?

[X] Yes, I have searched the existing issues and none of them match my problem.

Product Variant
Self-Hosted
Current Behavior
Hi, I'm trying to import my cv from json and I get this error:
[Nest] 88  - 11/09/2024, 1:24:34 PM   ERROR [ExceptionsHandler] request entity too large
PayloadTooLargeError: request entity too large
at readStream (/app/node_modules/.pnpm/raw-body@2.5.2/node_modules/raw-body/index.js:163:17)
at getRawBody (/app/node_modules/.pnpm/raw-body@2.5.2/node_modules/raw-body/index.js:116:12)
at read (/app/node_modules/.pnpm/body-parser@1.20.2/node_modules/body-parser/lib/read.js:79:3)
at jsonParser (/app/node_modules/.pnpm/body-parser@1.20.2/node_modules/body-parser/lib/types/json.js:138:5)
at Layer.handle [as handle_request] (/app/node_modules/.pnpm/express@4.19.2/node_modules/express/lib/router/layer.js:95:5)
at trim_prefix (/app/node_modules/.pnpm/express@4.19.2/node_modules/express/lib/router/index.js:328:13)
at /app/node_modules/.pnpm/express@4.19.2/node_modules/express/lib/router/index.js:286:9
at Function.process_params (/app/node_modules/.pnpm/express@4.19.2/node_modules/express/lib/router/index.js:346:12)
at next (/app/node_modules/.pnpm/express@4.19.2/node_modules/express/lib/router/index.js:280:10)
at internalNext (/app/node_modules/.pnpm/helmet@7.1.0/node_modules/helmet/index.cjs:521:6)
Thank you in advance.
Tommaso
Expected Behavior
I expected the json to be loaded.
Steps To Reproduce
No response
What browsers are you seeing the problem on?
No response
What template are you using?
None
Anything else?
I have a working version: https://resume.linuxguru.it/tommaso.bilotta/cv
with the latest version of the CV it doesn't work.

why is every issue assign to @AmruthPillai

When you encounter the error "PayloadTooLargeError: request entity too large," it usually means the JSON file you're trying to import is larger than the server's default limit for request size. To resolve this, you can increase the payload limit in your server's configuration. This adjustment should help you avoid the error.

the error is given to me inside the container logs. if it was the reverse proxy the request to the container I don't think would have arrived. chatgpt told me that I have to put a parameter inside the code (I admit my ignorance with this framework):
import { NestFactory } from @.***/core';
import { AppModule } from './app.module';
import * as bodyParser from 'body-parser';
async function bootstrap() {
const app = await NestFactory.create(AppModule);
// Set a custom size limit for the body
app.use(bodyParser.json({ limit: '50mb' }));
app.use(bodyParser.urlencoded({ limit: '50mb', extended: true }));
await app.listen(3000);
}
bootstrap();
Ottieni BlueMail per Android
Il giorno 11 Nov 2024, 15:55, alle ore 15:55, Abhishek Singh @.***> ha scritto:

When you encounter the error "PayloadTooLargeError: request entity
too large," it usually means the JSON file you're trying to
import is larger than the server's default limit for request size.
To resolve this, you can increase the payload limit in your
server's configuration. This adjustment should help you avoid the
error.
--
Reply to this email directly or view it on GitHub:
https://github.com/AmruthPillai/Reactive-Resume/issues/2097#issuecomment-2468370768
You are receiving this because you authored the thread.
Message ID:
@.***>

The same error is also given on the rxresu.me cloud
Ottieni BlueMail per Android
Il giorno 11 Nov 2024, 18:23, alle ore 18:23, Tommaso Bilotta @.***> ha scritto:

the error is given to me inside the container logs. if it was the
reverse proxy the request to the container I don't think would have
arrived. chatgpt told me that I have to put a parameter inside the code
(I admit my ignorance with this framework):
import { NestFactory } from @.***/core';
import { AppModule } from './app.module';
import * as bodyParser from 'body-parser';
async function bootstrap() {
const app = await NestFactory.create(AppModule);
// Set a custom size limit for the body
app.use(bodyParser.json({ limit: '50mb' }));
app.use(bodyParser.urlencoded({ limit: '50mb', extended: true }));
await app.listen(3000);
}
bootstrap();
Ottieni BlueMail per Android
Il giorno 11 Nov 2024, 15:55, alle ore 15:55, Abhishek Singh
@.***> ha scritto:

When you encounter the error "PayloadTooLargeError: request
entity
too large," it usually means the JSON file you're trying to
import is larger than the server's default limit for request size.
To resolve this, you can increase the payload limit in your
server's configuration. This adjustment should help you avoid the
error.
--
Reply to this email directly or view it on GitHub:
https://github.com/AmruthPillai/Reactive-Resume/issues/2097#issuecomment-2468370768
You are receiving this because you authored the thread.
Message ID:
@.***>

if you want I can send you the json that I try to import. it is about 156KB, to see if it works for you. I have customers who on the same kubernetes upload files of tens of MB on vtiger.
Ottieni BlueMail per Android
Il giorno 11 Nov 2024, 18:23, alle ore 18:23, Tommaso Bilotta @.***> ha scritto:

the error is given to me inside the container logs. if it was the
reverse proxy the request to the container I don't think would have
arrived. chatgpt told me that I have to put a parameter inside the code
(I admit my ignorance with this framework):
import { NestFactory } from @.***/core';
import { AppModule } from './app.module';
import * as bodyParser from 'body-parser';
async function bootstrap() {
const app = await NestFactory.create(AppModule);
// Set a custom size limit for the body
app.use(bodyParser.json({ limit: '50mb' }));
app.use(bodyParser.urlencoded({ limit: '50mb', extended: true }));
await app.listen(3000);
}
bootstrap();
Ottieni BlueMail per Android
Il giorno 11 Nov 2024, 15:55, alle ore 15:55, Abhishek Singh
@.***> ha scritto:

When you encounter the error "PayloadTooLargeError: request
entity
too large," it usually means the JSON file you're trying to
import is larger than the server's default limit for request size.
To resolve this, you can increase the payload limit in your
server's configuration. This adjustment should help you avoid the
error.
--
Reply to this email directly or view it on GitHub:
https://github.com/AmruthPillai/Reactive-Resume/issues/2097#issuecomment-2468370768
You are receiving this because you authored the thread.
Message ID:
@.***>

Yes and Give code in text or structured format
On Fri, 15 Nov 2024, 03:41 TommasoBilotta, @.***> wrote:

if you want I can send you the json that I try to import. it is about
156KB, to see if it works for you. I have customers who on the same
kubernetes upload files of tens of MB on vtiger.
Ottieni BlueMail per Android
Il giorno 11 Nov 2024, 18:23, alle ore 18:23, Tommaso Bilotta @.***>
ha scritto:

the error is given to me inside the container logs. if it was the
reverse proxy the request to the container I don't think would have
arrived. chatgpt told me that I have to put a parameter inside the code
(I admit my ignorance with this framework):
import { NestFactory } from @.***/core';
import { AppModule } from './app.module';
import * as bodyParser from 'body-parser';
async function bootstrap() {
const app = await NestFactory.create(AppModule);
// Set a custom size limit for the body
app.use(bodyParser.json({ limit: '50mb' }));
app.use(bodyParser.urlencoded({ limit: '50mb', extended: true }));
await app.listen(3000);
}
bootstrap();
Ottieni BlueMail per Android
Il giorno 11 Nov 2024, 15:55, alle ore 15:55, Abhishek Singh
@.***> ha scritto:

When you encounter the error "PayloadTooLargeError: request
entity
too large," it usually means the JSON file you're trying to
import is larger than the server's default limit for request size.
To resolve this, you can increase the payload limit in your
server's configuration. This adjustment should help you avoid the
error.
--
Reply to this email directly or view it on GitHub:

https://github.com/AmruthPillai/Reactive-Resume/issues/2097#issuecomment-2468370768

You are receiving this because you authored the thread.
Message ID:
@.***>

—
Reply to this email directly, view it on GitHub
https://github.com/AmruthPillai/Reactive-Resume/issues/2097#issuecomment-2477508219,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A36S7I2YCEXWP6KTQFNL33D2AUNYZAVCNFSM6AAAAABRQTPOW2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINZXGUYDQMRRHE
.
You are receiving this because you commented.Message ID:
@.***>

Hello, sorry for delay.
This is the json. I tryed just now on the  cloud rxresu.me, the validation was fine but after the import phase return me the error. I attached you one photo.
Thank you.
Tommaso
Ottieni BlueMail per Android
Il giorno 16 Nov 2024, 13:21, alle ore 13:21, Abhishek Singh @.***> ha scritto:

Yes and Give code in text or structured format
On Fri, 15 Nov 2024, 03:41 TommasoBilotta, @.***> wrote:

if you want I can send you the json that I try to import. it is about
156KB, to see if it works for you. I have customers who on the same
kubernetes upload files of tens of MB on vtiger.
Ottieni BlueMail per Android
Il giorno 11 Nov 2024, 18:23, alle ore 18:23, Tommaso Bilotta
@.***>
ha scritto:

the error is given to me inside the container logs. if it was the
reverse proxy the request to the container I don't think would have
arrived. chatgpt told me that I have to put a parameter inside the
code
(I admit my ignorance with this framework):
import { NestFactory } from @.***/core';
import { AppModule } from './app.module';
import * as bodyParser from 'body-parser';
async function bootstrap() {
const app = await NestFactory.create(AppModule);
// Set a custom size limit for the body
app.use(bodyParser.json({ limit: '50mb' }));
app.use(bodyParser.urlencoded({ limit: '50mb', extended: true }));
await app.listen(3000);
}
bootstrap();
Ottieni BlueMail per Android
Il giorno 11 Nov 2024, 15:55, alle ore 15:55, Abhishek Singh
@.***> ha scritto:

When you encounter the error "PayloadTooLargeError: request
entity
too large," it usually means the JSON file you're trying
to
import is larger than the server's default limit for request
size.
To resolve this, you can increase the payload limit in your
server's configuration. This adjustment should help you avoid
the
error.
--
Reply to this email directly or view it on GitHub:

https://github.com/AmruthPillai/Reactive-Resume/issues/2097#issuecomment-2468370768

You are receiving this because you authored the thread.
Message ID:
@.***>

—
Reply to this email directly, view it on GitHub

https://github.com/AmruthPillai/Reactive-Resume/issues/2097#issuecomment-2477508219,

or unsubscribe

https://github.com/notifications/unsubscribe-auth/A36S7I2YCEXWP6KTQFNL33D2AUNYZAVCNFSM6AAAAABRQTPOW2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINZXGUYDQMRRHE

.
You are receiving this because you commented.Message ID:
@.***>

--
Reply to this email directly or view it on GitHub:
https://github.com/AmruthPillai/Reactive-Resume/issues/2097#issuecomment-2480542571
You are receiving this because you authored the thread.
Message ID:
@.***>