Java JCE Installation Error

Ohai!  I would normally submit a PR for this kind of thing but did not know the best way to handle it.  Long story short, when I go to install the JCE policy files for Java 8, Java 8 is installed /usr/lib/jvm/java and the JCE policy files are installed /usr/lib/jvm/java/jre/lib/security with symlinks to the JCE policy files being installed in their default location at /opt/java_jce/8/  The issue is that the JCE files are installed at node['java']['oracle']['jce']['home'].  The Chef resource appropriate creates the directory recursively but only sets the permissions of the directory at the lowest level leaf (https://github.com/agileorbit-cookbooks/java/blob/v1.37.0/recipes/oracle_jce.rb#L36-L39) on the /opt/java_jce/8 directory but the /opt/java_jce directory that is created does not have world readable permissions.  On my system, the permissions are created for 740.  What this means is that a service running as non-root cannot resolve the symlinks to the JCE policy files because parts of the file path are not traversable by the world.
What would be the best way to handle this so that all directories that are created recursively get the proper permissions to handle the symlink?
Hopefully this makes sense and I can clarify if needed!
Thanks Chefs!

On my system, the permissions are created for 740.
The permissions in the cookbook recipe you linked to show mode '0755', right?
In testing it seems to correctly be 0755 on Ubuntu.
Which operating system do you have?  What are the permissions on just /opt?
If you launch brand new instances with test kitchen can you re-confirm the results?

I was testing using CentOS 6/7 and I can confirm I am still having the issue.  Using test-kitchen opt is getting 755 permissions.  I think this is a umask problem per OS and probably has to explicitly be stated in the cookbook to ensure non-root users can get access to this directory.

"On my system, the permissions are created for 740."   740 could be a problem.   However, here are the permissions I see on test-kitchen CentOS7 (which you could also run).   Everything is at least globally readable.   There is not a 0 permission.     Maybe your proprietary cookbook is doing something to alter permissions.    This test is only with the java cookbook.  Observe:
kitchen converge oracle-8-centos-71
cd java_jce/
[root@oracle-8-centos-71 java_jce]# ls -al
total 0
drwxr-xr-x. 3 root root 14 Feb  9 19:49 .
drwxr-xr-x. 6 root root 95 Feb  9 19:49 ..
drwxr-xr-x. 2 root root 56 Feb  9 19:49 8
[root@oracle-8-centos-71 java_jce]# cd 8/
[root@oracle-8-centos-71 8]# ls -al
total 8
drwxr-xr-x. 2 root root   56 Feb  9 19:49 .
drwxr-xr-x. 3 root root   14 Feb  9 19:49 ..
-rw-rw-r--. 1 root root 3035 Dec 20  2013 local_policy.jar
-rw-rw-r--. 1 root root 3023 Dec 20  2013 US_export_policy.jar
ls -al /usr/lib/jvm/jdk1.8.0_65/jre/lib/security/
total 152
drwxr-xr-x.  2 root root  4096 Feb  9 19:49 .
drwxr-xr-x. 15 root root  4096 Oct  7 00:29 ..
...
lrwxrwxrwx.  1 root root    32 Feb  9 19:49 local_policy.jar -> /opt/java_jce/8/local_policy.jar
lrwxrwxrwx.  1 root root    36 Feb  9 19:49 US_export_policy.jar -> /opt/java_jce/8/US_export_policy.jar

@sdarwin is correct, if you have a custom umask, you'll have to address that in a wrapper cookbook, thanks!


integrations.md looks bad

As reported by @LeifW:

Things like :white_check_mark: look nice on the GitHub markdown, but they're not rendered on the actual site:
https://http4s.org/v1.0/integrations/

Subjective, I reckon it looks pretty good now.
https://http4s.org/v0.23/docs/integrations.html


Fix install and probe bugs

Description
This fixes a nil pointer issue when Helm evaluates the deployment template before the secrets template creates trino-gateway-configuration. It also fixes an issue with the liveness and readiness probe templates.

Additional context and related issues
The nil pointer issue may result in an error message like
Error: template: trino-gateway/templates/deployment.yaml:20:71: executing "trino-gateway/templates/deployment.yaml" at <"trino-gateway-configuration">: nil pointer evaluating interface {}.resourceVersion

The templating issue results in a livenessProbe like:
livenessProbe:
            httpGet:
                path: /
                port: 9082
            initialDelaySeconds: .Values.livenessProbe.initialDelaySeconds
            periodSeconds: .Values.livenessProbe.periodSeconds
            failureThreshold: .Values.livenessProbe.failureThreshold
            timeoutSeconds: .Values.livenessProbe.timeoutSeconds

Release notes
( ) This is not user-visible or is docs only, and no release notes are required.
( ) Release notes are required. Please propose a release note for me.
(x) Release notes are required, with the following suggested text:
* Fix issue with Helm deployment when configuration secret not create
* Pass template values through to readiness and liveness probes

@willmostly Please use Rebase and merge when merging the PR.

Or if you need to use squash and merge  - make sure to reword message properly and remove the PR number in the title - see https://trino.io/development/process#maintainer-processes
also cc @vishalya and @Chaho12


Removed ResourceInteractiveLoader, add built-in threaded loading.

ResourceInteractiveLoader was an old vestige of the past, when Godot was aimed mainly at devices that only had one processor, like mobile, low end desktops and some consoles.
Godot has supported loading of resources on threads since a long time, so this old method of loading was obsolete.
In exchange, a new set of functions were added:
Error ResourceLoader.load_threaded_request(path: String, type_hint: String = "", use_sub_threads: bool = false)
ThreadLoadStatus ResourceLoader.load_threaded_get_status(path: String, r_progress: Array = [  ] )
Resource ResourceLoader.load_threaded_get(path: String)

First, a thread loading process is requested. It can be a single thread or multiple threads. If you want to focus on loadig times (load as fast as possible), then multiple threads can be specified. If you wan to focus on not affecting the game performance (just background load), then single threaded mode can be specified.
	ResourceLoader.load_threaded_request("res://myresource.tscn","",true)

Status can be requested at any time by calling:
	var status = ResourceLoader.load_threaded_get_status("res://myresource.tscn")

Optionally, progress can be retrieved from the status, too:

	var progress= []
	var status = ResourceLoader.load_threaded_get_status("res://myresource.tscn",progress)
	print("Progress: ",int(progress[0]*100),"%")

Finally, when status is complete (ResourceLoader.THREAD_LOAD_LOADED), the resource can be obtained:
	var res = ResourceLoader.load_threaded_get("res://myresource.tscn")

Calling the above function before thread is done loading will just result in blocking the current thread until the resource has finished loading.
This is a very useful feature because it allows the common pattern of start loading something (like, the first level while on the intro and title screen), and the block until completion, severely reducing load times in games.
It is important to not block the main game thread during this process, else the engine will deadlock.  If you want your loading to happen entirely on the main thread, use the old ResourceLoader.load() funciton, don't use these.
Using threaded loading in my tests resulted in an improvement of 4x to 6x times faster loading.

If you want to focus on loadig times (load as fast as possible), then multiple threads can be specified. If you wan to focus on not affecting the game performance (just background load), then single threaded mode can be specified.

What if I want to load as fast as possible without affecting the game performance?

Will that allow for something like 'level-streaming' in background functionality?
Or more than that - swapping/unloading assets while playing?

Will that allow for something like 'level-streaming' in background functionality?
Or more than that - swapping/unloading assets while playing?

This is what load_threaded_request() should allow if you don't use subthreads (which is the default). Only one thread will be used to load the resource, which ensures some CPU resources remain available for the main thread.

What about multi-threaded resource loading in editor?
Does this PR implements it?

@KoBeWi The problem is that there is no real metric for this. You can control how much it may affect game performance by the number of threads used, but this is entirely different on each hardware, so in the end the only "safe" value is to just use threads or don't use them.

@qarmin could eventually happen i suppose. Once this is well tested, it can be enabled.

@KoBeWi The problem is that there is no real metric for this. You can control how much it may affect game performance by the number of threads used, but this is entirely different on each hardware, so in the end the only "safe" value is to just use threads or don't use them.

What about multi threading and lower priority than the main game threads? Would be then the one fits all solution. Probably a mess when trying to implement that cross platform, though. Just thinking loudly. Looks really awesome!

@jejay I really prefer to not have to play with thread priorities nowadays. It just opens a different can of worms. Generally the high amount of cores and schedulers make sure everything more or less works ok,and in most operating systems the main UI or rendering thread already is given more priority so for now I would prefer to not get into that stuff.

Thanks!

I didn't see that any documentation was added with the addition of these 3 methods. Any plans on making that happen? @reduz

Really grea improvement, but

It is important to not block the main game thread during this process, else the engine will deadlock.

Makes me a bit suspicious. Is it a real deadlock? It is very bad and A runtime error, or at least warning would be way better - if not better get rid of that behavior.

@reduz, with your proposed implementation, the user would have to continuously poll the progress of the loading process before they're safely able to get the resource.
Since Godot is heavily focused on Signals, would it not be better to implement a Signal for the resource loader, which the user can hook their get function into?

@aspenforest A signal may be a bit complex, but with the new callable API, maybe you can just specify a function to get called when it's done. The only downside to this is that it will be called on the main thread. May be enough, though.

load_threaded_request
Isn't this feature currently available?
API documentation already exists this function.
but:When using this feature in 3.2.1, it prompts me that this function cannot be found.

This is a Godot 4.0 feature.

Could we cherry pick this one in?

How does this work with OpenGL contexts that may only be active in a single thread at a time? As far as I can tell, calls like glTexImage will fail in a separate thread without additional preparation. And the ideal solution would be to fully load resources in a separate thread, i.e. GPU stuff should be available for use on the GPU.
This would require special synchronization calls both in OpenGL and Vulkan and I don't see such things here, so I wonder how this works. From what I see these calls are not even directly available in GLES2, but Android and iOS provide their own ways to resolve this (Android via EGL, Apple via extensions that mimic GLES3). All in all, it seems there still a lot of work to do before actual multithreaded resource loading is there.
At the sime time, the "interactive loader" was already removed, and it was the main means of loading a scene in chunks, providing more granular feedback of the loading progress to the user.

This is cool. But the API is very weird. Why not use an Object named AsyncLoadResult, which is returned when the request is made. It’s properties could store the path to the resource and wrap the other 2 functions, namely progress, status and a get_result function. Additionally it could have a completed signal. This would work great with the new GDScript async. Also the use of Array like this is very inconsistent. Many other functions expect a non empty array while some (like this one) just replace the passes Array.

@PranavSK Please open a proposal on the Godot proposals repository to request improvements.

Any chance of this making it over to 3.x? :D  I keep running into bizarre issues using multithreading with loading in gdscript.  Now I'm having to do scary things like add a 1 second delay to avoid errors and crashes, but I don't feel good about it.

Any chance of this making it over to 3.x? :D I keep running into bizarre issues using multithreading with loading in gdscript. Now I'm having to do scary things like add a 1 second delay to avoid errors and crashes, but I don't feel good about it.

This relies on core refactoring (and breaks compatibility with existing projects), so it can't be backported to 3.x.


Feature: Pm custom separator

Summary
Hi folks, I'm opening this issue in order to extend the conversation about providing a custom separator for the @pm operator.
It is an open feature request from such a long time inside the Modsecurity repo (see https://github.com/SpiderLabs/ModSecurity/issues/682) and Wasm is yet another player that would take advantage of such a feature.
Basic example
I made a first PoC under ModSec repo: https://github.com/SpiderLabs/ModSecurity/pull/2786.
This first proposal takes advantage of a fixed string at the beginning of the rule (PmCustomSeparator:) in order to provide and figure out that we are going to use a custom separator.
An overall example of rule syntax is the following:
SecRule REQUEST_BODY "@Pm PmCustomSeparator:| single_word|<this> <is> <a> <string>|trailing_space " "id:999,phase:2,t:lowercase,deny"

Motivation

Make the @pm operator more flexible and able to handle some cases that currently can only be managed by PmFromFile.
Wasm environment that is lacking file system support would benefit from it.
Depending on the design agreed, it may lead also to looking for piped payloads (currently, to the best of my knowledge, it is not possible to match the pipe | character and do not interpret it as Suricata syntax)

Extra details

Even a different operator may be a way to go in order to avoid tweaking a known one and not messing with its default design.
If we agree on the usefulness of that feature and on a proper design, I would be happy to implement it on Coraza.

Thanks for any feedback!
cc: @jcchavezs

Hey @M4tteoP, thank you for your interest in Coraza. CRS has solved this problem by using text wrappers like |, but what you are talking about WASM is right, and it should concern us.
I have been thinking about a different solution for a while, creating seclang datasets like:
datasets.conf
SecDataset malicious_browsers `
hacker_browser
# this is a comment
hacker_browser_2

rules.conf
include datasets.conf
SecRule REQUEST_HEADERS:user-agent "@pmfromdict malicious_browsers" "..."

This would be consistent with the idea of helpers and code snippets.

Hi @jptosso, thanks a lot for the prompt reply!
I feel that SecDataset solution mimics in a great way the PmFromFile logic. Thinking about supporting as many characters as possible I would prefer your first example:
SecDataset malicious_browsers `
hacker_browser
# this is a comment
hacker_browser_2
`

As far as I can see, it could permit to look also for % and " characters.
Summarizing:
SecDataset solution would be:

harder to implement, maybe a bit less intuitive (but something like PmFromDataset should easily remind a similar behaviour to PmFromFile)
a bit more complex. A simple match like "a b c" would still require writing both the SecDataset and the rule.
With more characters supported.
Working fine in a Wasm env just like PmCustomSeparator.

A couple of questions:

What about The Snort-Suricata syntax, would you just mimic PmFromFile leaving that syntax only for the @pm directive?
What about the implementation? Do you feel that it could have to deal with big problems in Coraza?

As a side note, I'm dreaming about an implementation that may also land on ModSecurity, but there it may be way more tricky...

Snort-Suricata is not supported, but we haven't received any request or issue. I have monitored this repo in case we want to implement Suricata syntax, and we should be completely open to implementing it as long as it is compatible with WASM. Feel free to create an issue if you want.
The only major change for the seclang processor would be the ``` wrappers, as we haven't touched the lex processor in more than a year, but we can handle it.

I will open this discussion for the August Monthly Meeting

Just a note that may add another element to the discussion: the same concept may be applied to ipMatch/ipMatchFromFile operators, having something like SecDataset with the list of IPs and an ipMatchFromDict operator. Here I can see that it would just be about readability instead of relying on a long list of inlined IPs.

Could we mark this as solved with the new SecDataset operator?

@M4tteoP ☝ ?

Sorry to have kept you waiting, but https://github.com/corazawaf/coraza/pull/393 gave me pause wondering about overlaps in functionalities with SecDataset. In the end, I still see value in SecDataset (e.g. easy way to inline PmFromFile-like rules avoiding the need to recompile the Wasm plugin with the new rules embedded.)
I close it, thank you!


Clean up the grammar specification

The grammar can be cleaned up to make it more clearer / more understandable.
Some examples:

The number rule is only used in the value rule
INTEGER and FLOAT could be moved into the value rule

Same case for the parameter rule, it could be moved up to the call input rule

Changes like these, would make the grammar and the parser code smaller -> More clearer

This issue will be closed, as the above mentioned changes do not increase the readability and some rules are already being changed for other issues.


Websocket Encryption

A producer is sending a messages using encryption while the consumer should be able to consume the encrypted message using the websocket
wanted an help
If no is there a way
we can configure to
start websocket proxy with option to avoid decryption, and let it pass same payload to web-socket client
the configuration settings or the steps required to change
or any other option where we can resolve the issue

@kjaggann I think this will help: https://github.com/apache/pulsar/pull/10026

Is this change is in pulsar 2.7.1 version.
however we have upgraded the websocket version in our websocket proxies but still the user is unable to connect the when the encryption is enabled

The recent change to the pulsar websocket allows the encrypted payload to be passed thru to the client.
However,  it does not appear that the (aes) encrypted data key is included with the message that we get.
How does a websocket client get this key?

websocket just pass through message payload with key to client without modifying anything.

Can someone please tell me if the above mentioned "key" ("Original routing key set by producer") is actually the '(aes) encrypted data key' ?

https://github.com/apache/pulsar/issues/11197

it is not, the key mentioned here is used to determine which partition a message will be sent to: https://pulsar.apache.org/docs/en/admin-api-topics/#publish-to-partitioned-topics


Support SparseReduceSum on GPU

System information

TensorFlow version (you are using): 1.12.0
Are you willing to contribute it (Yes/No): Yes

Describe the feature and the current behavior/state.
From a generated trace I see that tensorflow performs SparseReduceSum on CPU while the rest of computation on GPU. I'm using tf.sparse.reduce_sum
Will this change the current api? How?
No
Who will benefit with this feature?
Everyone, reduction on CPU kills performance completely.
Any Other info.
Could you point to data structures and/or algorithms that you are going to use, if any?

this is particularly a problem if loading a graph with this op onto GPU.

@sh1ng,
Sorry for the delayed response. Can you please let us know if tf.raw_ops.SparseReduceSum in the latest Tensorflow Version (2.5) runs on GPU? Thanks!

tf.sparse.reduce_sum has been supported on GPU? @sjtusmartboy


DOC: minor tweaks

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
2 unchanged lines in 2 files lost coverage.
Overall coverage decreased (-0.001%) to 91.635%

Files with Coverage Reduction
New Missed Lines
%

.nox/test-3-10/Lib/site-packages/cogent3/core/alignment.py
1
94.42%

.nox/test-3-9/lib/python3.9/site-packages/cogent3/core/alignment.py
1
94.38%

Totals

Change from base Build<PHONE_NUMBER>:
-0.001%

Covered Lines:
236180

Relevant Lines:
257740

💛  - Coveralls


Change extension from .nc to .vdc

In some cases I left the ability to use .nc extensions for usability. For example, in the Open Dataset dialog on OSX where disabling it would force users to rename their files. The sphinx documentation needs to be re-generated to include the changes but that can be done at the next release.
Fix #2248

@StasJ this PR changes the help messages issued such that the extension ".nc" is replaced by ".vdc", but that is all it does. I guess I was expecting the conversion utilities to automatically append a ".vdc", if none was present, when generating a .vdc file. What do @sgpearse and @shaomeng think?

I don't have a rigid stance on this.  In my experience, other command-line file editing tools like NCO let users name generated files whatever they want.
I can't think of a reason why all .vdc files must always have only one extension, but maybe you guys can.  Conversly, enforcing .vdc adds more code to maintain.

@clyne this PR keeps the same behavior that we've had with the .nc extension. The functionality you suggested can be added but was not mentioned previously.

@clyne this PR keeps the same behavior that we've had with the .nc extension. The functionality you suggested can be added but was not mentioned previously.

The issue that you opened, #2248, states "possibly forcing them to use .vdc output files". I guess possibly is the operative word here. I would think that if we don't do something like automatically changing the output file to include the extension we probably won't accomplish much.

@clyne Fair point. I was referring to the fact that I didn't realize that was a requirement/expectation for this PR but I have no problem adding it.
There are 2 options:

We automatically append a .vdc extension if the file does not have one, i.e. if a user specifies out.nc, we output out.nc.vdc. This behavior mimics the system file save dialog.
We abort with an error code if the extension is not .vdc

1 seems more convenient to me however the advantage of 2 is that if a user has a script, this will clearly let them know we have started enforcing this file extension whereas option 1 may cause their script to silently fail and they have to debug it.

@StasJ per our discussion this afternoon let's just add a warning message if the .vdc extension is not used.

vapor doesn't seem to recognize the .vdc extension when the file is specified on the command line. The application starts, but the data set isn't loaded.

That was never actually a feature that vapor supported. I just threw in some basic support for this for my own convenience when testing so I did not bother updating it here. I can clean up that code a bit and update it if we want to make it a feature.

I find it to be a highly useful feature. Please make it work.

Done

@clyne That came across wrong. I was just explaining why I didn't update it initially. I put that there when I was developing a feature a long time ago. Since I had already been using .vdc for a while it didn't work for me and I considered it old development code. It now works for vdc, netcdf, and wrf files.


normalize line endings

Minor, but nice to have!

Yep, got VS complaining about them yesterday. :D


Clean up python package build dependency structure

Currently, all files are included via glob making it hard to add further internal dependencies between files...
Clean this adding separate BUILD files in each directory

Where is this the case?


Update xaml-templated-controls-cppwinrt-winui-3.md

2 typos.

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

The typo fixes look good; thanks.


selectionLimit = 1 and checkboxes

if you set selectionLimit to 1 and checkedStyle to 'checkboxes' you still can select multiple checkboxes even though the model gets only one value assigned. It's probably not what one want. I got  around this by adding another option to the checkedStyle entry:
checkedStyle?: 'checkboxes' | 'glyphicon' | 'radio';

and in the template
                    <input *ngIf="settings.checkedStyle == 'radio'" name="radioitem" type="radio" [checked]="isSelected(option)" />

and in setSelected
        if (this.settings.checkedStyle == 'radio') {
            this.model = [option.id];
        }

I've proposed an "auto unselect" option which would allow for single selections, and for multiple selections constrained to the selection limit by automatically unchecking the oldest selections #27
Keen on some feedback, I think it might go nicely with an alternate checkedStyle, as I suppose semantically checkboxes don't make sense for single selections.

Merged pull request and created new release.


Release v.0.0.3

Feature changes:

TBD

Major code hygiene changes:

MongoDB Cloud verification done using a graph traversal model of tests instead of a massive validation function. This should encapsulate and abstract this, even if it makes it a bit less readable (although a massive function will get unwieldy too).

Let's do it.

Let's do it.


Missing wordHighlightForeground

VSCode Version: 1.12.1
OS Version: OSX 10.11.6

Steps to Reproduce:

In my case, open a *.cs (csharp) file
Place cursor on word that is repeated
I think tmTheme sets a value for this, in my case I'm not sure its implemented, hard to tell what keys to change if possible. Open settings and set wordHighlightBackground to white for example.  My default font colour is white so now it doesn't show up, is there a way to select wordHighlightForeground, I don't see this option available

We don't currently allow to selections and highlights to set the text foreground colors.
It's because of an architectural choice in the editor implementation: The implementation keeps selections and highlights in a separate layer than the text in order to avoid relayouting text on selection changes.
As this is unlikely going to be changed soon, I'm closing the issue as won't fix.
You have to pick selection colors that go well with the token colors.


Document how to install Gardener using just .gardener.cloud/.sapcloud.io CRDs and kubectl

What would you like to be added:
I would love to see documentation which details how one can install Gardener (ie, the "garden" cluster) and seed/shoot clusters via a process which

First installs CRDs for all .gardener.cloud/*.sapcloud.io API server extensions (via kubectl)
Then installs garden/seed/shoots clusters, cloudprofiles/machines, and plants etc using pure k8s yaml and kubectl apply

Why is this needed:
The current Gardener installation process is incredibly confusing.  For example, do we really have to use sow, gardenctl, etc to set up Gardener?  Or can we not simply boil down the installation steps into 1) bootstrapping CRDs on some type of bootstrap cluster and then 2) using kubectl and standard Kubernetes GitOps tooling (think ArgoCD, WeaveFlux etc) to create and manage clusters?

As there is no activity on this issue I will close it for now.
@n-boshnakov please can you review it if something more can be added
/close


Compatibility with IE11

Hello,
The lib looks awesome, but I've one question given that the library uses CSS Variables : is the library compatible with IE 11 ?
Thanks

Just like regular CSS, this library works with IE11 but certain features may not work. Unfortunately, this means all dynamic theming features are unavailable.

@markdalgleish
What if IE11 is fine with just the default theme, without any dynamic css changes?


Recur without completing task, cancel or any other status the old task

⚠ Please check that this feature request hasn't been suggested before.

[X] I searched previous Ideas in Discussions didn't find any similar feature requests.
[X] I searched previous Issues didn't find any similar feature requests.

🔖 Feature description
A recurring task that would add CANCELLED or other status when not done by due date, but it would still recur according to original schedule.
✔ Solution
A situation: I have a pill I need to take everyday. When I click the task done, I know I took it that day. When I don't do it that day, I still have track of the day I did not take it.
Another case: I have a weekly thing that only happens on wednesdays. I'd like it only to appear on wednesdays as that is the due date, but I would love to keep track of those that I did not mark done.
Another: I have a tasks-filter that shows me all past due dates for recurring tasks, those that "are left undone". Some of these I would like to automatically skip if I did not do it that day.
❓ Alternatives
For some use cases I see no other alternative, such as the last one described. I need a way to automatically skip some tasks if they were undone, plus also keep track if it was not done.
📝 Additional Context
I love to use tasks to keep track on when I have done recurring tasks and this feature is a much needed addition to that. If it already is completely doable with the current tools, then I apologize!

For the pill case, what if 2 days (or more) were skipped? There shall be a cancelled task created for each of the missed recurrences, I imagine?
This seems like a nice functionality, but if this is implemented I'd like to suggest it as an option somewhere (probably in the recurrence keywords) and not the default behaviour.
For instance, I have a thing to do each Monday, but if it is not done on Monday, I still need to it on Tuesday. And don't need a cancelled recurrence for Monday.

@ronny3 If you haven't done so, could you have a look at the existing 'when done' facility...
https://publish.obsidian.md/tasks/Getting+Started/Recurring+Tasks#Repeating+a+Task+Based+on+the+Original+Due+Date+or+the+Completion+Date
I use it to keep track of when I did the tasks, for example in this block, each line ends with a done date that shows when I actually did the task.
- [X] Exercises - walk one mile or exercise class #context/town ⏫ 🔁 every 2 days when done 📅 2023-04-15 ✅ 2023-04-17
- [X] Exercises - walk one mile or exercise class #context/town ⏫ 🔁 every day when done 📅 2023-04-12 ✅ 2023-04-12
- [X] Exercises - walk one mile or exercise class #context/town ⏫ 🔁 every day when done 📅 2023-04-08 ✅ 2023-04-11
- [X] Exercises - walk one mile or exercise class #context/town ⏫ 🔁 every day when done 📅 2023-04-01 ✅ 2023-04-07
- [X] Exercises - walk one mile or exercise class #context/town ⏫ 🔁 every day when done 📅 2023-03-18 ✅ 2023-03-25
- [X] Exercises - walk one mile or exercise class #context/town ⏫ 🔁 every day when done 📅 2023-03-17 ✅ 2023-03-17
- [X] Exercises - walk one mile or exercise class #context/town ⏫ 🔁 every day when done 📅 2023-03-16 ✅ 2023-03-16
- [X] Exercises - walk one mile or exercise class #context/town ⏫ 🔁 every day when done 📅 2023-03-15 ✅ 2023-03-15
- [X] Exercises - walk one mile or exercise class #context/town ⏫ 🔁 every day when done 📅 2023-03-14 ✅ 2023-03-14
- [X] Exercises - walk one mile or exercise class #context/town ⏫ 🔁 every day when done 📅 2023-03-13 ✅ 2023-03-13
- [x] Exercises - walk one mile or exercise class #context/town ⏫ 🔁 every day when done 📅 2023-03-03 ✅ 2023-03-12
- [x] Exercises - walk one mile or exercise class #context/town ⏫ 🔁 every day when done 📅 2023-02-26 ✅ 2023-03-02
- [x] Exercises - walk one mile or exercise class #context/town ⏫ 🔁 every day when done 📅 2023-02-23 ✅ 2023-02-25
- [x] Exercises - walk one mile or exercise class #context/town ⏫ 🔁 every day when done 📅 2023-02-22 ✅ 2023-02-22
- [x] Exercises - walk one mile or exercise class #context/town ⏫ 🔁 every day when done 📅 2023-02-19 ✅ 2023-02-21

Does that achieve what you are after?
If it doesn't, please could you explain how you want the following to work?

A recurring task that would add CANCELLED or other status when not done by due date, but it would still recur according to original schedule.

Could you talk through the series of steps that you are asking for, so that it is clear how and when you want the cancelled task to be created?
Many thanks.

@ilandikov I agree, it should not be the default behavior, as it's more a special case.
@claremacrae indeed I very much love the "when done" behavior. However, I would like tasks to automatically add CANCELLED, if the task was not done on the scheduled/due date.
- [ ] Walk 500 miles 🔁 every saturday with cancel twist 📅 2023-06-17
- [-] Walk 500 miles 🔁 every saturday with cancel twist 📅 2023-06-10 ❌ 2023-06-10
- [X] Walk 500 miles 🔁 every saturday with cancel twist 📅 2023-06-03 ✅ 2023-06-03

The thing that this adds as completely new is that it updates the task to a new date even if I do no interaction for it. For example imagine this:
- [ ] Take the pill 🔁 every saturday when done 📅 2023-03-18
- [X] Take the pill 🔁 every saturday when done 📅 2023-03-11 ✅ 2023-03-11
- [X] Take the pill 🔁 every saturday when done 📅 2023-03-04 ✅ 2023-03-04

This would be an undone task that is way past its due date, but the past due date is irrelevant. What is relevant is that it should be still going on for every upcoming saturday, if we have a query that for example shows everything we need to do for the date.
not done
due today

The above query would not show the "take the pill" task, as it's due in the past. If it kept updating, it would show up. The cancelled is not necessary, as I just realized these are 2 different features, but I would find it useful as well.
The other option of not using the "when done" operator would not be ideal either, as you would get bloat of tasks that you'd need to cancel manually (as clicking means done, but this would be false if I never did the deed).

@ilandikov I agree, it should not be the default behavior, as it's more a special case.
@claremacrae indeed I very much love the "when done" behavior. However, I would like tasks to automatically add CANCELLED, if the task was not done on the scheduled/due date.

Hi @ronny3, thanks for the reply.
So can I just check that I understand.
Currently, Tasks only edits any checkbox/task line when the user explicitly interacts with it.
I think that you are requesting a whole different way of Tasks interacting with the user's vault, which is some kind of batch processing:

At some pre-determined interval or scheduled ...
... should search the entire vault ....
... and every overdue recurring task that it finds with some newly agreed text to indicate 'cancel if overdue ' ....
... should be given

a 'date cancelled' emoji
and cancelled status

and a new instance should be created... (but see below, becomes sometimes multiple new instances should be created)

Complications/factors to be considered when thinking about implementing this:

The user may not have run Tasks for several days, and so it would need to handle the case where multiple new cancelled instances would need to be created
It should run soon after Obsidian startup, so that if the user has loaded a 'tasks due today' search, very soon after start-up that search would show the updated tasks
Tasks already does have a scheduled action that reloads open searches just after midnight

But that doesn't always work due to a Chrome bug - #1289

Recur without completing task, cancel or any other status the old task

I don't think I understand that summary... could you please clarify what "cancel or any other status the old task" means?

Another complication:

The user may have more than one CANCELLED status
OR they may have none of their statuses toggling to CANCELLED

So it will need to something like:

Take the Task's current status ...
... and toggle through its nextStatus, nextNextStatus etc until ....

a status of type CANCELLED is reached ...
or the original status is reached again - in which case just used the default CANCELLED status [-]
or an unknown status is reached - in which case just used the default CANCELLED status [-]

Another complication:

What will happen if the user was editing an overdue task when the scheduler came along and skipped its recurrence?

I do understand the appeal of this. I know which of my tasks I would apply it to straight away.
However, just to set user (and developer) expectations, this is one of those features that initially sounds quite simple but actually has a lot of corner cases - and as the first automated editing of a user's vault, it would need a lot of careful manual and automated testing.

@claremacrae yes I see how it's a feature that breaks many typical barriers of how tasks operates on normal day-to-day basis. I am happy that you picked up on it as a good feature. Maybe an "easy" experimental version is to do it all only at startup. I think many users are also fine with having "experimental" options in settings, accepting that they may still not be fully functional.
With "cancel or any other status the old task" I was referring to marking the task as [-] or any other custom such as [<] etc.
Thanks!

@claremacrae yes I see how it's a feature that breaks many typical barriers of how tasks operates on normal day-to-day basis.

That's actually a nice summary.

Maybe an "easy" experimental version is to do it all only at startup.

Whoah... that would be really dangerous. The user would get totally different behaviour on any given day, depending on whether they Quit Obsidian when the finished the day before.
And on iPhone and iPad Obsidian generally doesn't restart unless you force-quit.

I think many users are also fine with having "experimental" options in settings, accepting that they may still not be fully functional.

Sorry but I have higher standards for Tasks than that.

With "cancel or any other status the old task" I was referring to marking the task as [-] or any other custom such as [<] etc. (excuse my weird sentence structures)

OK... So how would Tasks (or rather, the volunteer programmer working on Tasks) know whether to use [-] or [<] - please can you add more detail/be more specific?


FAST: compilation warnings on GCC 5.1

gcc version 5.1.1 20150422 (Red Hat 5.1.1-1) (GCC)

In file included from lib/proto/fast_book.c:2:0:
lib/proto/fast_book.c: In function ‘apply_increment.constprop’:
/home/denis/devel/arbcap/libtrading/include/libtrading/proto/fast_book.h:134:17: warning: array subscript is above array bounds [-Warray-bounds]
   if (set->books[i].secid == secid)
                 ^
lib/proto/fast_book.c: In function ‘fast_books_join’:
/home/denis/devel/arbcap/libtrading/include/libtrading/proto/fast_book.h:134:17: warning: array subscript is above array bounds [-Warray-bounds]
   if (set->books[i].secid == secid)
                 ^
/home/denis/devel/arbcap/libtrading/include/libtrading/proto/fast_book.h:134:17: warning: array subscript is above array bounds [-Warray-bounds]
   if (set->books[i].secid == secid)
                 ^

@mstanichenko Can you please take a look? Perhaps GCC 5.1.1 optimizes the inline functions more aggressively and discovers an off-by-one somewhere? Or then it's just a false positive.

Hello guys! I was already thinking of the problem. Need to reproduce it as don't know what it could be.
I just compile gcc locally but don't see these warnings. @divaykin, could you please tell what source I can use to get release you were building against? Thanks!
xgcc (GCC) 5.1.0
Copyright (C) 2015 Free Software Foundation, Inc.

@mstanichenko just master branch. we've not modified fast_book.c/.h lately. if can't be reproduced easily I don't think it make sense to bother much

@divaykin, I'm sorry for confusion. I meant GCC release. Is it available here? You must be also using additional optimization flags that might trigger that issue.

It's Fedora 22 beta's GCC. Nope, optimization flags are standard i.e.
unmodified Makefile.
Maybe just too bleeding edge compiler.
Best
D
On Wednesday, May 13, 2015, Marat Stanichenko<EMAIL_ADDRESS>wrote:

@divaykin https://github.com/divaykin, I'm sorry for confusion. I meant
GCC release. Is it available here https://gcc.gnu.org/releases.html?
You must be also using additional optimization flags that might trigger
that issue.
—
Reply to this email directly or view it on GitHub
https://github.com/libtrading/libtrading/issues/74#issuecomment-101446343
.

I was advised that there is a temporary workaround here. Do not use -O3 optimization. Use -O2 for example for the time being.

I am unable to reproduce with the GCC version from Fedora 23:
gcc version 5.3.1 20160406 (Red Hat 5.3.1-6) (GCC)

Closing.


expose API for listing all currently detected mesos masters, not just the leader

/cc @kozyraki

Just curious, what's the reason for exposing all masters?

christos mentioned that the HDFS framework wanted IP addresses, registered in mesos-dns, for all mesos masters. The detection API already listened for changes to the mesos-master list, it just didn't provide a hook for those interested.

to further clarify, there are two parts to the problem this is attempting to solve:

there exist frameworks that want to dynamically obtain the list of all ZK nodes in the cluster, under the assumption that every mesos master node also runs ZK. older versions of zookeeper don't allow dynamic discovery, so this is really a workaround for that based on an assumption.
mesos-dns, which uses this zookeeper detection helper, could provide DNS entries for all mesos master nodes if it could detect them through the APIs presented here. clients of mesos-dns could then query the server for a list of all mesos masters. they could then assume that all of those masters are running ZK.

xref https://github.com/mesosphere/mesos-dns/issues/166

@tnachen the nginx in DCOS proxies to master.mesos. When designing it like that the assumption was that master.mesos would contain all the masters. We only later found out that that's only the case for when the masters are hard coded in the mesos-dns config. When running via zookeeper it only returns the current leader at which point it's essentially the same as leader.mesos.
This currently breaks HA for the DCOS UI. E.g. if marathon on the current leader becomes unresponsive then nginx will still proxy requests to it because it doesn't know about the other master nodes.
So having master.mesos always return the masters would be extremely helpful to us. I'd also argue that from a user point of view it's what I would expect to happen when I query that record.


First branch

Did some test, only to understand how the create pull request feature works.

Succesfuly merged.


feature/TECH 507 argo cd support

Resolves #181

[x] Introduce plain k8s manifests as deploy result. These can be deployed with kubectly apply -f, or feed into argocd.
[x] Replace brittle dictionary fiddling
[x] Move type definitions local to their respective domains
[x] Clearly describe the 4 different targets of a k8s deploy in documentation

⚠ mpyl_config.yml will need to have the imagePullSecrets defined like such:
    kubernetes:
      imagePullSecrets:
        - name: 'acme-registry'

📕 TECH-507 Integrate MPyL with ArgoCD
181
🏗 Build 5 ✅ Successful, started by Sam Theisens
🚀 cloudfront-service, job, kong-sync, nodeservice, sbtservice, sparkJob

Looks nice, just some minor comments & questions!
I do think it would have been easier for us to review if all the type(casting) changes would have been its own pr. Then it would also be clearer which changes are actually required for argo for us 'noobs' ;-)

Yeah, maybe I should have done that. Although it is a relevant refactoring now that we have 4 different deploy artifacts.
More PRs also means a bigger testing burden.
I'm happy to make more PRs, let me know what you prefer.

Another weird thing I noticed: I corrected the config so now that part is fine, and in the build plan everything seems fine:
+ pipenv run run
🏗 Building
🏗 tradingMockServiceApi
📋 tradingMockServiceApi
🚀 tradingMockServiceApi

but after the test step it seems like deploy step was skipped completely! I checked in kubernetes and indeed the service was not deployed. In the logs I don't see the usual helm upgrade output either.
I attached the full logs
Uploading console.txt…

Another weird thing I noticed: I corrected the config so now that part is fine, and in the build plan everything seems fine:
+ pipenv run run
🏗 Building
🏗 tradingMockServiceApi
📋 tradingMockServiceApi
🚀 tradingMockServiceApi

but after the test step it seems like deploy step was skipped completely! I checked in kubernetes and indeed the service was not deployed. In the logs I don't see the usual helm upgrade output either.
I attached the full logs console.txt
this was the run: https://jenkins.k8s-serv-backend.vdbinfra.nl/job/MPyL Pipeline/job/PR-11303/11/console

Ah, that doesn't sound good. I'll have a look tomorrow.

It looks like there was/is an issue with the logging. It seems as if log level is set to too high. Only the straight to stdout output is shown.
I ran another build and things seem to work as they should. I hope it's not an intermittent problem. I've added a console print with the log level. So next time this occurs at least we know if there's something wrong with that.
Could you maybe try another run?

Same goes for me concerning the smaller PRs, other than that looks good! :)

Another weird thing I noticed: I corrected the config so now that part is fine, and in the build plan everything seems fine:
+ pipenv run run
🏗 Building
🏗 tradingMockServiceApi
📋 tradingMockServiceApi
🚀 tradingMockServiceApi

but after the test step it seems like deploy step was skipped completely! I checked in kubernetes and indeed the service was not deployed. In the logs I don't see the usual helm upgrade output either.
I attached the full logs console.txt
this was the run: https://jenkins.k8s-serv-backend.vdbinfra.nl/job/MPyL Pipeline/job/PR-11303/11/console

Ah, that doesn't sound good. I'll have a look tomorrow.

It looks like there was/is an issue with the logging. It seems as if log level is set to too high. Only the straight to stdout output is shown.
I ran another build and things seem to work as they should. I hope it's not an intermittent problem. I've added a console print with the log level. So next time this occurs at least we know if there's something wrong with that. Could you maybe try another run?

I checked again with version 185.2368 and same is printed for me (nothing for deployment). Also I checked in kubernetes and the pod of my service was deployed yesterday the last time, so I don't think it's just the logging that's acting up

Another weird thing I noticed: I corrected the config so now that part is fine, and in the build plan everything seems fine:
+ pipenv run run
🏗 Building
🏗 tradingMockServiceApi
📋 tradingMockServiceApi
🚀 tradingMockServiceApi

but after the test step it seems like deploy step was skipped completely! I checked in kubernetes and indeed the service was not deployed. In the logs I don't see the usual helm upgrade output either.
I attached the full logs console.txt
this was the run: https://jenkins.k8s-serv-backend.vdbinfra.nl/job/MPyL Pipeline/job/PR-11303/11/console

Ah, that doesn't sound good. I'll have a look tomorrow.

It looks like there was/is an issue with the logging. It seems as if log level is set to too high. Only the straight to stdout output is shown.
I ran another build and things seem to work as they should. I hope it's not an intermittent problem. I've added a console print with the log level. So next time this occurs at least we know if there's something wrong with that. Could you maybe try another run?

I checked again with version 185.2368 and same is printed for me (nothing for deployment). Also I checked in kubernetes and the pod of my service was deployed yesterday the last time, so I don't think it's just the logging that's acting up.
This is the run: https://jenkins.k8s-serv-backend.vdbinfra.nl/job/MPyL Pipeline/job/PR-11303/13/console Console: console.txt

There's definitely something wrong with the logging. In the logs you shared none of the mpyl logging is visible.
It does say:
MPyL log level is set to INFO

So an incorrect log level is probably not causing it.
I don't have access to Jenkins, so I could only capture logs from the CLI:
argocd-support-logs.txt
This explains why the services weren't deployed to the cluster:
INFO     mpyl.KubernetesDeploy  Service sbtservice reachable at: https://sbtservice-185.test.nl
INFO     mpyl  Execution of Kubernetes Deploy succeeded for 'sbtservice' with outcome 'Wrote kubectl manifest to tests/projects/sbt-service/target/kubernetes'

What is the action configured here https://github.com/Vandebron/mpyl/blob/2e179fcc4db22dac3b2563a2804bcbfaa68c1a0e/mpyl_config.example.yml#L70 in the config repo?

Reapplied changes in https://github.com/Vandebron/mpyl/pull/185 to merge with main

Reapplied changes in https://github.com/Vandebron/mpyl/pull/185 to merge with main


fix(netns): avoid double-close persistent file

Resolves: #80

The fix seems quite simple. The remove method of DefaultEnv will always remove_file the path of the persistent file created by NetNs::new. It won't remove the file created by NetNs::current. However, the file owned by NetNs::current will be auto-closed in the drop function. There might be no need to explicitly close the persistent file before we let env remove that netns. See if @minhuw has some words on this.


Add --no-pager option to avoid long line issue in smaller terminal windows

In base_sys_setup, line 233, change to:
sudo systemctl start ufw && sudo systemctl status ufw --no-pager
This will ignore the long lines of output so it doesn't pause the script.  Basically you can test this pretty easily in putty simply by making your terminal window small and running
sudo systemctl status ufw
and then again with the --no-pager option
sudo systemctl status ufw --no-pager
I didn't actually try running the script in full with this option, so it might be needed elsewhere.  And perhaps it would be good to add to line 275 as well just in case.

will implement in dev and verify the effects before pushing to main

tested in ufw-pager branch ok. have not been able to replicate the issue encountered by some so inconclusive from my perspective.

further testing with extremely minimal terminal window has replicated the issue.  --no-pager has had no impact.  user input of 'q' + 'enter' is required to bypass


Issue with many charts one page

Hello! I have a new problem. I use jQuery EasyUI for create many tabs. I dynamically create charts in tabs. (This example contents 3 tabs with charts, but in my project I create very many tabs)
All tabs contents serial Amchart. I use autoOffsetAxis, but tool works not correct. Last chart in third tab correctly positione offset, but first and second not work :(
http://codepen.io/shumakosik/pen/qrovgL
ValueAxes starts works fine when you click at legend for "off/on" graph after initialization chart.
May you help me?
Thanks.

Hi there.
It must be some sort of timing issue.
We just released an update. (1.4)
It adds a public method to chart object updateOffsets().
I'm not familiar with EasyUI, but I bet it should have some sort of event model which you can use to call the above method on your chart objects. You might need to experiment a bit which event to use. It could be when tab is created, selected or when all tabs are created.
You need to call this method on all chart objects once.
I.e.:
AmCharts.charts[0].updateOffsets();

I hope this helps.

Thanks for answer!
I fix this problem with updateOffsets() and setTimeout function.


The programmer does not work in any of the three modes: UPDI, HV, PCHV!

I put together your diagram.
The programmer does not work in any of the three modes: UPDI, HV, PCHV!
I have an Attiny412 controller
Why did you power the tinyAVR controller from your Arduino Nano ADC?
The ADC pins only work for the input, right?!

Pins A0-A5 are setup as digital outputs. Since they originate from the same port and are driven at the same time, they are used as a target power source that can be power-cycled when needed. Pin A6 is an input that is used to sense an overload condition on A0-A5. Pin A7 is an input that senses the Mode.
From the documentation here, there's a small table showing the jumper positions and resulting Mode.
Just below that, there's another small table showing recommended connections for each Mode. The Nano's 6-pin connector can be used for 5V (steady power) and GND and this might be needed under some conditions ... refer to the last table showing test results (ATtiny412) and suggestions.


f7 router events

Hi. I have to make redirect when authorized user going to the login page. How can I use f7 router events?

Same as framework7-Vue. You can check from http://framework7.io/vue/navigation-router.html

yes, yes. Thank you.


Extend settings component

#124 Introduced information.qml which is a mutation of Setting.qml but introduces an additional two loaders and respective properties to handle the scenarios where a setting doesn't use an option switch and needs to instead display a link, display an image, or take input.
The issue, despite large amounts of duplicate code is that, following this design pattern, we will be introducing a new mutation of Settings.qml everytime we have a scenario when there should be something aside from an option switch.
Instead of endless mutations, Settings.qml can just be made extensible by simply introducing a loader which gives it an actionItem. an actionItem is the interact-able element of this setting; that could be an option switch, a url, a text input box, or something completely new.
An example of something new, see the current simplification of the AboutOptions.qml developer settings button:
-    RowLayout {
-        Header {
-            Layout.fillWidth: true
-            center: false
-            header: qsTr("Developer options")
-            headerSize: 18
-            description: qsTr("Only use these if you have development experience")
-            descriptionSize: 15
-            descriptionMargin: 10
-            wrap: false
-            }
-        Loader {
-            Layout.fillWidth: true
-            Layout.preferredWidth: 0
-            Layout.alignment: Qt.AlignRight
-            Layout.rightMargin: 5
-            active: true
-            visible: active
-            sourceComponent: TextButton {
-                text: ">"
-                bold: false
-                rightalign: true
-                onClicked: {
-                    introductions.incrementCurrentIndex()
-                    swipeView.inSubPage = true
-                }
+    Setting {
+        Layout.fillWidth: true
+        header: qsTr("Developer options")
+        description: qsTr("Only use these if you have development experience")
+        actionItem: TextButton {
+            text: ">"
+            bold: false
+            rightalign: true
+            onClicked: {
+                introductions.incrementCurrentIndex()
+                swipeView.inSubPage = true
             }

There is currently an issue with the layout and long links, would appreciate review feedback that addresses this small layout issue.
based on #141 and #142
Links for Windows and macOS build artifacts. Replace  with the assigned pull request number.

updated from ac4dbd2 to 0935349 (PR143.01 -> PR143.02, diff)
changes:

rebase over changes on #141
update one temporary setting with no importance from an ExternalLink to ValueInput to prevent a warning in the terminal when running the gui

updated from 0935349 to 3b53ae6 (pr143.02 -> pr143.03, diff)
changes: rebased over changes in #141

updated from 3b53ae6 to 69d0778 (pr143.03 -> pr143.04, diff)
changes: rebased over changes in #141

@jarolrod

changes: rebased over changes in #141

One more rebase?

updated from d4db4d1 to ee82e9c Compare
changes: rebase over changes on master


Update antlr4-runtime to version 4.10 or higher

Latest versions of spring-boot-starter-data-jpa use antlr4-runtime with version 4.10.1. Breaking changes were made in version 4.10 (that require regeneration all of lexers and parsers) so it makes this library unusable with spring-boot-starter-data-jpa.

Thanks @Nickkreker for reporting
Could you open a PR as well? For this type of change we also want to bumb the package version


HIVE-27604 : Backport of HIVE-21167 to branch-3

JIRA link - https://issues.apache.org/jira/browse/HIVE-27604

@vihangk1 @sankarh Can you please approve and merge this


Training Data Format

Can you show the training data format which is used to train llama. If possible, I would like you to show me a example training data so that we can build our own training data set.

Thank you for your interest! We provide some data examples at https://github.com/microsoft/ToRA/tree/main/data/tora/.


Json parameter now works in config file

Thanks @mew1033 for your contribution! I've updated the base branch to develop.


[Snyk] Upgrade html-snapshots from 3.7.1 to 3.8.0

This PR was automatically created by Snyk using the credentials of a real user.Snyk has created this PR to upgrade html-snapshots from 3.7.1 to 3.8.0.
:information_source: Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

The recommended version is 1 version ahead of your current version.
The recommended version was released 2 days ago, on 2024-05-09.

Release notes

Package name: html-snapshots

3.8.0 -<EMAIL_ADDRESS>

3.7.1 -<EMAIL_ADDRESS>

    from html-snapshots GitHub release notes

Commit messages

Package name: html-snapshots

509cfd5 Merge pull request #714 from localnerve/rc-3.8.0
da29a14 @ 3.8.0 -<EMAIL_ADDRESS>devdeps
e96954d Merge pull request #712 from localnerve/snyk-upgrade-0f1c701c8969082b7d02603a55615692
b60b6fc fix: upgrade html-snapshots from 3.6.3 to 3.7.1
94c543f Merge pull request #711 from localnerve/snyk-upgrade-8ad5f10bbc2cd8cb2ff4c1e6cc72ce7a
87df049 fix: upgrade html-snapshots from 3.7.0 to 3.7.1
55a6575 Merge pull request #710 from localnerve/snyk-upgrade-834e12a87f9efdc4241a78c0c8b34c47
0b82070 fix: upgrade html-snapshots from 3.6.3 to 3.7.1
c055841 Merge pull request #709 from localnerve/snyk-upgrade-ac6ea021d5ff3e5ee43777c22f4413c6
546e8fb fix: upgrade html-snapshots from 3.6.3 to 3.7.1
8348bf7 Merge pull request #708 from localnerve/snyk-upgrade-dc0b2f0e78fd64896a5124838ee38720
e54dc53 fix: upgrade html-snapshots from 3.7.0 to 3.7.1
f348e07 Merge pull request #707 from localnerve/snyk-upgrade-bc1db0ed0c5c950abd352c225b782a3d
aa1743f fix: upgrade html-snapshots from 3.6.3 to 3.7.1
718febe Merge pull request #706 from localnerve/snyk-upgrade-d092705e00570c6ef4ce8d4728ab628e
2a61530 fix: upgrade html-snapshots from 3.6.3 to 3.7.1
50cb41a Merge pull request #705 from localnerve/snyk-upgrade-93a075e19e307f2099103a262b955c53
632d8be fix: upgrade html-snapshots from 3.6.3 to 3.7.0

Compare

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.
For more information:
🧐 View latest project report
🛠 Adjust upgrade PR settings
🔕 Ignore this dependency or unsubscribe from future upgrade PRs

coverage: 99.245%. remained the same
when pulling f39f7bc60ffb6d5a53bd633078eb1ac6ea23c473 on snyk-upgrade-89c0448b20552203ac10bb05f5ad55c1
into cc6d833a6da13936bd1950bc649ec1aaea22a6bb on master.