Cannot be used with PostgreSQL

Describe the bug
Hi, when using TypesenseBundle with a PostgreSQL database, it is impossible to use the query method from CollectionFinderInterface, that is supposed to return hydrated Doctrine Entities.
The bundle uses the ORDER BY FIELD directive, which is specific to MySQL.
To Reproduce
Steps to reproduce the behavior:

Start a Symfony 6.3 project, with a PostgreSQL database, and TypesenseBundle enabled
Configure the bundle properly to persist an entity (like a topic with an author and a content)
Persist at least one entity
Use the query method

Expected behavior
Should return the hydrated objects instead of crashing (from the SQL server).
Screenshots

Desktop (please complete the following information):

OS: Ubuntu 22.04 LTS
Docker

Additional context

PostgreSQL version: postgres:14.2 (postgres:14.2-alpine docker image)
Typesense version: 0.25.0 (typesense/typesense:0.25.0 docker image)

I suggest to add a configuration key 'database', which accepts either 'mysql' or 'postgresql' (or gets it from the Doctrine configuration automatically), to then customize the request according to which engine is used.

Also, could you not use Doctrine to query the database? It would be much simpler!

Hello @EdouardCourty thank you for reporting this issue.
This is indeed a problem, I will have a look at it this week.

Quick update on this subject
As you can see if you read the code, the hydrate() function load entities from the database, based on the results given by Typesense.
In order to be sure that the hydrated collection is in the same order than the given result by typesense (eg : ids (3,1,6)), we add a SORT instruction with FIELD in our request.
We use it in a native SQL request. it could be done using the beberlei/DoctrineExtensions, to use Doctrine Query Builder, but after some research it appears that FIELD instruction is not available in PostGreSQL.
So, I don't see how to get a sorted collection with PostGreSQL that respects the Typesense order.
I think we should refactor the code in order to sort the entities in PHP.

Hi, thanks for your reply :)
For now I'm using the RawQuery method and I deserialize the documents myself.
I also noticed that searching on boolean fields is not possible, is it a limitation from the Typesense server or from the implementation?
I would be more than happy to contribute to the project!


This ranking rewards popularity over commits, even if they're unrelated.

The way of building the ranking is incorrect. Followers should be set to one, and list size could be reduced by account lifetime.
It's also good to note that seniority and code quality is opposite to popularity.

Unfortunately sorting by contributions is not possible in the GitHub API. And yes, this is simply a list sorted by number of contributions, nothing more.

Actually, this is first a rank of followers, then sorted by contributions. Plus, you could open an issue for the github api requesting implementation of the obviously missing feature, then close this issue once you get a definitive answer. But it's your public project so it's ok if this is how you handle the issues.


refactor functions to minimise use of global variables

This build script was inherited from a 3rd party. Now that I have a fuller understanding of InvokeBuild, the script should be re-written to avoid the use of bad practices, like the unnecessary use of global/script variables which is having a detrimental effect of the maintenance of the script.

There's no point fixing this as I've made the decision to cmpletely re-write the build script, because it is currentl unmaintainable. The original author (I forgot where I got this from), made too much use of global variables which is prooving to be a total menace.

Alread7 addressed by issue #22


Unable to launch browser

I get this error when I try to launch debug from vscode with the new support for one-step debugging for Blazor #1885
Unable to launch browser: "Could not open wss://localhost:5001/_framework/debug/ws-proxy?browser=ws%3A%2F%2F<IP_ADDRESS>%3A53267%2Fdevtools%2Fbrowser%2F53f91446-8e68-4407-95d8-d9c70558ff11": timeout after 30000ms
If I delete everything from .vscode folder I get the same error. I have the the latest Nightly JavaScript Debugger and the latest C# Extension.
Environment information
VSCode version: 1.46.0-insider
C# Extension: 1.22.0
JavaScript Debugger (Nightly): v2020.5.2917
Dotnet Information
.NET SDK (reflecting any global.json):
 Version:   5.0.100-preview.4.20258.7
 Commit:    65f0fc2cad
Runtime Environment:
OS Name:     Mac OS X
OS Version:  10.15
OS Platform: Darwin
RID:         osx.10.15-x64
Base Path:   /usr/local/share/dotnet/sdk/5.0.100-preview.4.20258.7/
Host (useful for support):
Version: 5.0.0-preview.4.20251.6
Commit:  47ec733ba7
.NET SDKs installed:
5.0.100-preview.4.20258.7 [/usr/local/share/dotnet/sdk]
.NET runtimes installed:
Microsoft.AspNetCore.App 5.0.0-preview.4.20257.10 [/usr/local/share/dotnet/shared/Microsoft.AspNetCore.App]
Microsoft.NETCore.App 5.0.0-preview.4.20251.6 [/usr/local/share/dotnet/shared/Microsoft.NETCore.App]

CC @captainsafia

Let's see if we can figure this out, @ofrades.
Typically, the error that you received occurs if the Blazor dev server has not started by the time the browser is launched. This can occur for a few reasons:

A build error in your application prevents it from running correctly
The application you are debugging is a hosted app but your config is associated with a standalone app
Your application has a complicated build setup and takes longer than 30 seconds to build and run

To help debug this, can you check if:

dotnet run works on your application without failing
What the contents of your launch.json are?

Thank for the reply @captainsafia.
dotnet run works without errors.
I have tried several launch.json configuration. If I run F5 without one, select the Blazor WebAssembly Debug, vscode creates this one for me:
{
	// Use IntelliSense to learn about possible attributes.
	// Hover to view descriptions of existing attributes.
	// For more information, visit: https://go.microsoft.com/fwlink/?linkid=830387
	"version": "0.2.0",
	"configurations": [
		{
			"type": "blazorwasm",
			"name": "Launch and Debug Blazor WebAssembly Application",
			"request": "launch"
		}
	]
}

Another thing I just noticed is that if I am running the app with dotnet run and run the debug (which makes no sense) I get one error that might be useful:
It was not possible to find any compatible framework version
The framework 'Microsoft.AspNetCore.App', version '3.1.0' was not found.
  - The following frameworks were found:
      5.0.0-preview.4.20257.10 at [/usr/local/share/dotnet/shared/Microsoft.AspNetCore.App]

You can resolve the problem by installing the specified framework and/or SDK.

I am using Blazor 3.2.0 by the way and the only sdk I have is 5.0.100-preview.4.20258.7

I am using Blazor 3.2.0 by the way and the only sdk I have is 5.0.100-preview.4.20258.7

The 3.1.3 SDK is required in order to run Blazor WASM applications. This is likely what is causing the failure in this case. Blazor WASM isn't bundled with 5-preview4.

Yes, that's it! Thanks.

In my case, it was one package missing :Microsoft.AspNetCore.Components.WebAssembly.DevServer
Happy coding.


Testing delegation active/next

Issue Number
#1342
Overview

d30ce0dddf76fc222122f388d9bb7cb221b93e2f
I have reorganized a bit integration tests for "stake pool active/next" groupping them into 5 scenarios:

STAKE_POOL_NEXT_01 - Can join/re-join another/quit stake pool
STAKE_POOL_NEXT_02 - Join 2 sp in the same epoch => delegating to the
last one in the end
STAKE_POOL_NEXT_02 - Join and quit in the same epoch =>
not_delegating in the end
STAKE_POOL_NEXT_03 - Join 2 in two subsequent epochs => delegating to
1st in epoch X + 2 and 2nd in epoch X + 3
STAKE_POOL_NEXT_03 - Join and quit in two subsequent epochs =>
delegating in epoch X + 2, not_delegating in epoch X + 3

2d9e46ee6de1f0f0ea06e0643a909ddea100c343
Adjust quitStakePool/joinStakePool to not allow joining/quitting only when last pending interferes

Comments

I let myself adding also:
44d97a0
Forbid quitting SP when not_delegating is already a target in the delegation next

bors r+

bors r+

bors r+

So, yeah, buildkite times out:
Timed out after 30 minutes.

Cause newly added tests add ~9 minutes to execution, which make integration tests to run for slightly more than 30 mins now.

Cause newly added tests add ~9 minutes to execution

Awe... Should we consider maybe moving these cases at a unit level? I mean, we aren't much testing the integration at this point, but simply different scenarios of delegation given different starting point.
We could very much have this at the unit level if we move the conditions for delegating / retiring to separate pure functions (e.g. "canDelegate" "canRetire")

Awe... Should we consider maybe moving these cases at a unit level?

If that's possible then why not :)

OK, as discussed leaving in this PR:
d30ce0d
I have reorganized a bit integration tests for "stake pool active/next" groupping them into 5 scenarios... (so basically the same tests as before but re-organized)
2d9e46e
Adjust quitStakePool/joinStakePool to not allow joining/quitting only when last pending interferes
And will open another PR with further integration tests with the intention to move them into unit tests next week...
bors r+

Buildkite still times out, so leaving only:
36d3dcd - Adjust quitStakePool/joinStakePool to not allow joining/quitting only when last pending interferes
Tests in another pr.
bors r+

Interesting, how does it work locally ?

Hm, Actually exec time is ok but 3 integration tests failed for me (however not related with the change I think):
Failures:

  test/integration/Test/Integration/Jormungandr/Scenario/CLI/Server.hs:96:9:
  1) CLI Specifications, DaedalusIPC [SERIAL], Should reply with the port --random
       uncaught exception: IOException of type NoSuchThing
       node: createProcess: runInteractiveProcess: exec: does not exist (No such file or directory)

  To rerun use: --match "/CLI Specifications/DaedalusIPC [SERIAL]/Should reply with the port --random/"

  test/integration/Test/Integration/Jormungandr/Scenario/CLI/Server.hs:102:9:
  2) CLI Specifications, DaedalusIPC [SERIAL], Should reply with the port --port
       uncaught exception: IOException of type NoSuchThing
       node: createProcess: runInteractiveProcess: exec: does not exist (No such file or directory)

  To rerun use: --match "/CLI Specifications/DaedalusIPC [SERIAL]/Should reply with the port --port/"

  test/integration/Test/Integration/Jormungandr/Scenario/CLI/Server.hs:109:9:
  3) CLI Specifications, DaedalusIPC [SERIAL], Regression test for #1036
       uncaught exception: IOException of type NoSuchThing
       node: createProcess: runInteractiveProcess: exec: does not exist (No such file or directory)

  To rerun use: --match "/CLI Specifications/DaedalusIPC [SERIAL]/Regression test for #1036/"

Randomized with seed<PHONE_NUMBER>

Finished in 1193.6961 seconds
1149 examples, 3 failures, 1 pending

The same tests fail for me locally on master, so I don't know... maybe related to Ubuntu 19.10, to which I just switched...
bors r+

@piotr-iohk you need to have Node.js installed and available in your $PATH to run these tests. So, it's probably normal if you don't.

bors r+

@KtorZ any update on when this PR could be merged? This is currently blocking us from releasing next Daedalus version...
Or is there another PR which excludes tests and is perhaps already merged?

now this integration test fails -> NETWORK_BYRON, which I cannot reproduce locally... (issued: https://github.com/input-output-hk/cardano-wallet/issues/1368)
bors r+

bors r+

bors try

NETWORK_BYRON failing tests appears to be fixed in d87907c870947a4def285d68efd8bb172b2a9b6e.
bors r+


java solution for Find the Running Median(updated README.md aswell)

Please provide issue number in description.


Update README.md

I attempted to improve the readability of README

Nice! thanks for all the contributions 👍🏼


Sometimes RVerify.js does not hide after solving

Dear support.
Thank you for this wonderful project.
Today while am testing RVerify.js, I have this case when I solved the RVerify correctly, but it does not hide the RVerify.js modal. and I can not close it anymore even though the close button is disabled the slider, everything is disabled.
Please Advice.
Is there an API to call so I can assure the RVerify closed!

you can use RVerify.action() to solve. According to the different return values, handling the action when the modal closed. You can also provide a demo in codepen.io to reproduce the problem you encountered~


Missing summit location when run macs2 with --broad option

Hi, tommy
Thanks for your post about MACS, it helps me a lot!
Actually I usually use Homer to call histone modification peaks. Recently, I need to use macs to "validate" my previous results. When I run
macs2 callpeak -t test_rep1.bam -n test --broad -p 0.01 --nomodel --extsize 147 -g 1.4e9

The output files don't have NAME_summits.bed and there is no column of "absolute peak summit position" in NAME_peaks.xls. Did I miss some specific options?
Or do you happen to know how can I quickly identify the summit location in a bed file(The most enriched signal location in a region)? I am new to bioinformatics, I write a small script to calculate the 100bp bin region FPKM then screen the max value...but it is very slow(of course)..
Thanks for your help in advance!

it seems if you specify --broad, no summit will be reported by macs2. The only way to do is get a single base pair pipleup say by bedtools genomcov and then for each broad peak identified by macs2 check with base has the highest value.
I also see you asked the question on the pybigwig page. as you see, there is no direct way you can get it easily...

Thanks for your reply! Kind of desperate...I also asked the questions on biostar, macs, Homer 😅 New to bioinformatics, just intuitively thought it was a simple question but I could not find more elegant solution. (￣o￣)
Thanks again, your series of ChIP-seq blog really help me a lot.

glad it helps! I was new too, that's why I wrote down the notes.


Structure of Tetramers Configuration

Hi all,
Do we have to know the structure of tetramer configurations and search for the position of Na and Cl ion to be used for optimization. For different structure, what is the difference that we have to do to implement the code. Paper shows that the binding energy per ions for given configurations are different, so how we approach to get that value?

Yeah, you are right. Also, the main difference is the position of the ions.


Adds description for all methods within server and client c files wit…

Added descriptions to methods for lwm2mserver and lwm2mclient c files

@NihadF7 @marcoraddatz  This is approved, we can merge it. I would also advise that we include a new ticket during code implementation which will include additional creation of the documentation for data types,function and use cases in a .md format, as mentioned in resolved comments. This can be done during code implementation as a acceptance criteria.

I agree with @ssalkic proposal. PR merged. Closing as done.


GrpcTransportOptions uses internal grpc APIs

GrpcTransportOptions references io.grpc.internal.SharedResourceHolder. As it is in the internal package, it has an unstable API that may change at any time.
https://github.com/googleapis/google-cloud-java/blob/6b567115e98271632bdaa04833fdd9e217bd9c3e/google-cloud-clients/google-cloud-core-grpc/src/main/java/com/google/cloud/grpc/GrpcTransportOptions.java#L35-L36

It's only used in an internal api of java-core. So, it should be safe in case it has to change. Please re-open, if needed.

Please re-open.
No, this isn't about whether the API is exposed to your users. Libraries must not use unstable APIs in other libraries as libraries cannot dictate which version of libraries are being used.

@chingor13 You had a PR open to fix it, but you closed it. Why?


ENH - Improve Docs consistency

This PR aims to

Unify docs with our style guide (WIP in #64 )
Add TODO comments for links that need updating for visibility
Move rename disclaimer from warning to an announcement bar
Minor wording improvements in md. - removing emojis, changing “we” for “you", ensuring we use admonitions consistenly
styling - fix annoying code styles, use reusable patterns for style settings, change hyperlinks
navigation  - update links in navbar (there were too many and this was making it really unusable on smaller screens)

What does this implement/fix?
Put an x in the boxes that apply

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds a feature)
[ ] Breaking change (fix or feature that would cause existing features to not work as expected)
[x] Documentation Update
[ ] Code style update (formatting, renaming)
[ ] Refactoring (no functional changes, no API changes)
[ ] Build related changes
[ ] Other (please describe):

Testing

[x] Did you test the pull request locally?
[ ] Did you add new tests?

Documentation

Access-centered content checklist
Text styling

[x] The content is written with plain language (where relevant).
[x] If there are headers, they use the proper header tags (with only one level-one header: H1 or # in markdown).
[x] All links describe where they link to (for example, check the Nebari website).
[x] This content adheres to the Nebari style guides.

Non-text content

[x] All content is represented as text (for example, images need alt text, and videos need captions or descriptive transcripts).
[x] If there are emojis, there are not more than three in a row.
[x] Don't use flashing GIFs or videos.
[x] If the content were to be read as plain text, it still makes sense, and no information is missing.

Any other comments?

@kcpevey please not I changed the navbar links. - there were too many items and the navbar was getting al kinds of wonky on smaller screens/widths
Anyway I think it makes sense to keep only a few links since the sidebar should have the full list of docs

Note I could not find how to fix the sidebar pre rendering (see image) - but I think this is a limitation within Docusaurus. Will dig deeper later on

I could not find how to fix the sidebar pre rendering

Thats fine, if we can't get syntax highlighting, do we want to keep the back ticks? We could remove them and then no one would really notice that we didn't get the syntax highlighting.

Ok removed this from the description - unless there are more comments I will merge this today


qemu: query migrate status

This makes saveSandbox wait for migration completion, then we can remove the arbitrary sleep waiting for migration completion when creating a tempalte vm.
The govmm patch will be revendored once it is merged.

Blocked on https://github.com/intel/govmm/pull/51.

lgtm

Because of Golint error, I think I should first give a small "looks good to me" :-)
virtcontainers/factory/template/template_test.go:23:2:warning: unused variable or constant undeclared name: templateWaitForMigration (varcheck)
virtcontainers/factory/template/template_test.go:23:2:warning: unused struct field undeclared name: templateWaitForMigration (structcheck)
virtcontainers/factory/template/template_test.go:23:2:warning: undeclared name: templateWaitForMigration (unused)
virtcontainers/factory/template/template_test.go:23:2:warning: undeclared name: templateWaitForMigration (staticcheck)

@WeiZhang555 Yes I noticed that. I was waiting for the govmm pr to be merged and then I'll update this one here. Just do not want to waste another round of CI resources ;)

@bergwolf Do you work on katacontainers migration?

@clarecch yes

@bergwolf Wow, I think it would be a hard work. Do you have any plan for that？

@clarecch We did some work on migration for customer feature requirements. I'm posting this out first since it also helps vm templating. I'll post more later when we have new progress.

Kicked the density CI (timed out).

Still blocked on https://github.com/intel/govmm/pull/51.

updated. PTAL.

/test

@bergwolf Can you rebase and push?

/test

@jodh-intel I am seeing these errors in the CI for ubuntu 16.04 and fedora 27:
ERROR: kata-log-parser: no log records to process
Any idea?

Just to note - those are not what broke the builds ;-) I agree, it would be nice to know if that is a real problem with the log parser - but generally that is just a tail end issue when trying to clean up a broken build. If you look further up the F27 one for instance you will find:
runtime pid=13652 source=runtime
open /sys/module/kvm_intel/parameters/unrestricted_guest: no such file or directory
Build step 'Execute shell' marked build as failure
Performing Post build task...

Yeah, if we can make the tail end in a fail case a bit cleaner, then folks will skip back up more to find the real error(s).

Missing kvm-intel kernel module?

@amshinde, @grahamwhaley - If you ask the log parser to run and it doesn't find any log records across all the log files it's been give, that's an error (by design). You can get a hint of that if you look at all the "ignoring empty file ..." lines above the error. But as @grahamwhaley says, that's just "fallout" from the real error.
@mnaser, @chavafg - no VT-x over here too :(

There is no wip but pullapprove always thinks there is... Pending — Work in progress - do not merge

This can be fixed by adding and removing DNM label again...

@caoruidong Nice! Thx!

lgtm

@bergwolf seems approved. Ping (from your Kata herder)

/retest

jenkins-ci-ubuntu-16-04-initrd failed on network issue. re-triggered.

CI green (finally;)


Shadow jackson and bump dependencies versions

Fixes #65

Error: com.oracle.graal.pointsto.constraints.UnresolvedElementException: Discovered unresolved type during parsing: com.mifmif.common.regex.Generex. To diagnose the issue you can use the --allow-incomplete-classpath option. The missing type is then reported at run time when it is accessed the first time.
Detailed message:
Trace:
        at parsing io.github.serpro69.kfaker.provider.Bank.ibanDetails(Bank.kt:29)
Call path from entry point to io.github.serpro69.kfaker.provider.Bank.ibanDetails(String):
        at io.github.serpro69.kfaker.provider.Bank.ibanDetails(Bank.kt)
        at com.oracle.svm.reflect.Bank_ibanDetails_010f0cf2035e2f5169d343f907d75e3523b55170_398.invoke(Unknown Source)
        at java.lang.reflect.Method.invoke(Method.java:498)
        at picocli.CommandLine$Model$UsageMessageSpec$1.run(CommandLine.java:7673)
        at java.lang.Thread.run(Thread.java:748)
        at com.oracle.svm.core.thread.JavaThreads.threadStartRoutine(JavaThreads.java:519)
        at com.oracle.svm.core.posix.thread.PosixJavaThreads.pthreadStartRoutine(PosixJavaThreads.java:192)
        at com.oracle.svm.core.code.IsolateEnterStub.PosixJavaThreads_pthreadStartRoutine_e1f4a8c0039f8337338252cd8734f63a79b5e3df(generated:0)

Error: Use -H:+ReportExceptionStackTraces to print stacktrace of underlying exception
Error: Image build request failed with exit status 1

> Task :cli-bot:nativeImage FAILED


Rename organisers section in cofounders and core-team

TODO

Add Emmy as a core team member

Give Emmy all the core members rights (email, slack etc.)
Do a blog post release? (ask Emmy if that would be desirable)

Extend co-founders with the legal title of executive directors

It would be fixed with #412


support inherited @Api annotations

uses Springs annotation utils to search for the @Api annotation on superclasses (and interfaces), not just the RestController

Closing, as unit tests are needed.  Please re-open with unit tests if you're still interested.


etckeeper: Add push subcommand

This will make it more convenient to update the state in git-infra when changes are pulled from master (i.e. add a call to etckeeper push in Ansible if new changes were received).

I see a reference to 99push but where is the code for it?

@lrvick It's a symlink, as /etc/etckeeper/commit.d/99push already exists.

+1


Comment about the information I talked about on the Blog?

testing this comment system

testing this comment system

this is a test

test


bootstrap web fonticons not working properly

I have problem bootstrap 4 or 5 some svg web font icons not working
for example :

Probably wrong repo, you should report such issues upstream in bootstrap-icons.

Probably wrong repo, you should report such issues upstream in bootstrap-icons.

Probably wrong repo, you should report such issues upstream in bootstrap-icons.

Yes, you are right and I did the same


New function for adaptive authentication to retrieve claims of associated user

Description
When a user is authenticated using a federated authentication flow and mapped to a local user account by user account association through adaptive authentication, we can't get the associated user claims as identity server is not expecting that there is an association at this point since the association is handled through post auth handlers.
Therefore to get the associate user claim values, a custom adaptive authentication function needs to be implemented. Since this is a valid requirement, it would be better if we can introduce a new JS function for adaptive authentication to retrieve the associate user claims.

This issue is being closed due to extended inactivity. Please feel free to reopen it if further attention is needed. Thank you for helping us keep the issue list relevant and focused!


I have the paid key but I don't want to fetch perfectcanvas because it takes quite a while, what should I do?

there is no alternative unless  you're very experienced with this framework


showNegative reflected in customOutput

fix for #115

cool, it would be nice to have test cases that catch this kind of bug

added @FrancescoBorzi 🎉


Added new category for competitive programming

I've added a new category for competitive programming, some of the channels are very rare (although I've only added the ones by top competitive programmers)

Wow this great! Thanks @jayvasantjv


Make it so Rosetta construction routes don't need archive URI/connection/pool

Refactors the Rosetta server code so the archive URI is optional and only used to instantiate a DB connection/pool when a request is made to a top-level route that may need it (i.e., any route other than construction/*).
To test I ran Rosetta's test suite and saw it still passes with the existing parameters; then started Rosetta without the archive-uri parameter set (along with Mina running without archive-address set) and made sure construction/* routes worked but others failed gracefully.
TODO:

This means the first non-construction/* call to any Rosetta server will be slower than normal since it needs to instantiate the DB connection. Is this okay?
We previously were just returning Deferred.unit when failing to connect to the DB (when an archive URI was passed); this now returns a SQL error instead. Is this okay?

Checklist:

[x] Document code purpose, how to use it

Mention expected invariants, implicit constraints

[x] Tests were added for the new behavior

Document test purpose, significance of failures
Test names should reflect their purpose

[ ] All tests pass (CI will check this if you didn't)
[x] Serialized types are in stable-versioned modules
[x] Does this close issues? List them:

Closes #7690

!ci-build-me

!approved-for-mainnet


Add basic input components

[x] text (https://formkit.com/inputs/text)
[ ] select (https://formkit.com/inputs/select)
[ ] checkbox (https://formkit.com/inputs/checkbox)
[ ] radio button (https://formkit.com/inputs/radio)
[ ] text area (https://formkit.com/inputs/textarea)
[x] number field (https://formkit.com/inputs/number)

Obsolete as former is now headless


Deprecated features usage query does not work.

Deprecated features usage query does not work for named instances. Needs to be corrected. Also the actual object_name in the DMV has a bunch of spaces appended. Only something like below would work.
SELECT * FROM sys.dm_os_performance_counters
WHERE object_name like '%:Deprecated Features%';

Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

ID: 350a39df-f728-83b5-fd69-45c1050f389f
Version Independent ID: 350a39df-f728-83b5-fd69-45c1050f389f
Content: Deprecated database engine features in SQL Server 2022 - SQL Server 2022
Content Source: docs/database-engine/deprecated-database-engine-features-in-sql-server-2022.md
Product: sql
Technology: release-landing
GitHub Login: @MikeRayMSFT
Microsoft Alias: mikeray

@ajithkr-ms -- Ajith, thank you for your suggestions.
@MikeRayMSFT -- Mike, please look into this issue.

Thanks for the feedback, @ajithkr-ms - an update is in process.


feat(box): support min version checks, expose vardiac options

What this PR does / why we need it: This PR adds support for min spec version checks and varidic options for EnsureBox

JIRA ID: DTSS-775

Notes for your reviewer: Big thanks to @malept for discovering the bug that required this.
Related PR: https://github.com/getoutreach/box/pull/4

:tada: This PR is included in version 1.17.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Check for correct ponyc version

Would it make sense to have our Makefiles check that the correct version of ponyc is installed before compiling so that users don't get compiler errors that really (unbeknownst to them) indicate that they have the wrong version of ponyc?
@dipinhora

This sounds... yes. This sounds reasonable.

@jtfmumm @SeanTAllen What should happen if it's not the "correct version of ponyc"? Should an error be printed telling folks to install the correct version?
How should we handle the case of someone intentionally using a "non-correct version of ponyc" (i.e. someone wanting to use master as part of upgrading the wallaroo code for compatibility)?

@dipinhora i was imagining something along the lines of how the ponyc make process errors out if you don't have a supported LLVM version.

@SeanTAllen Understood regarding the error/exit when the "incorrect version of ponyc" is installed. We'd also need to define/maintain a list of "correct versions of ponyc" that I'm assuming at a minimum would include the release being built without the .git directory existing and with it (i.e. 0.24.0 and 0.24.0-79af8a0 in the case of version 0.24.0).
I'm still not entirely clear on whether we want to support folks being able to use an "incorrect version of ponyc" intentionally or not. Only allowing for the specific versions would make things easier for end users but possibly harder for development (i.e. we regularly use custom ponyc versions when testing bug fixes and upgrades to new versions of ponyc; usually prior to or in-between releases).

I don't think we want to support "incorrect version of ponyc". But it should be "painless" for someone going through the upgrade cycle for Wallaroo. Like perhaps changing a clause in the Makefile.


Add Gateway for Integration with Paypal Express for Digital Goods

I needed to adjust ActiveMerchant to support PayPal's Express Checkout for Digital Goods (EC4DG).
This type of integration with PayPal allows a more integrated approach, where instead of bouncing the user to  PayPal in the same window, then bouncing the user back, it allows the user to add JavaScript to their site to do the redirection inside an iframe/lightbox.  This integration method has certain limitations, and differences;
CHANGES:
-different redirection url
-build_setup_request => calling this method in the DG integration requires additional parameters (need to include itemized options with category of all the items 'Digital').
-i had to tweak the PayPal Express base class to support additional fields when setting up a request.  These fields are allowed in any request, but required for a DG integration
-Digital Goods Integration is only supported at 65+ Version.  Upped the version to 72 since that is the latest
-changed the redirect_urls from being cattr_accessor (using the same class variable) to class_inheritable_accessor (plays nicer with inheritence)
-added test cases for this new gateway.
If there are any changes I need to make to this in order to get this integrated let me know.

Is there a reason this hasn't been merged yet? I need this functionality too!

Closing in favor of #224.


Updated CONTRIBUTING.md

Changed the contribution guidelines to be more consistent with the style that wlroots has evolved into, partially mentioned in #93.
This is my current interpretation of what the style is actually supposed to be. Correct me if I'm wrong.
I've removed some of the things which was duplicating information from the kernel style, and am mainly highlighting the differences from it. We just defer to the kernel style in cases not mentioned here.
I removed the code example, as it had references to very sway specific things, and it didn't actually follow the style being talked about. Not to mention that I think the code was probably a bit too complicated for an example.
I looked around the wlroots codebase for a replacement, but I couldn't find a reasonably self-contained example that showcased the style and not have some other problem with it.
We can add the example back when the code gets cleaned up a little bit.

bump

Updated.

Thanks!


Automated Package Upgrade

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Can I use plotsr to visualize multiple human genomes with known SVs?

Hi,
We have some cell lines where we made SVs using CRISPR editing. We would like to use plotsr to visualize these SVs, but I am struggling a bit to figure out how to do it. Unlike the example, I have bam files for 3 samples, but only a single reference .fa (the standard hg38.fa). I have plotsr installed and can get the example image, but not sure how to proceed with our data. Do I need to make genome assemblies from each sample (Illumina 150 bp WGS 30X) in order to run SiRY? It appears our HPC has SOAPdenovo installed, but it isn't clear to me that this outputs a .fa file...sorry, I am used to running packages that use Fastq or bam, definitely not used to using genome assemblies outside of the standard hg38 reference. Thanks in advance for any help!
Take care,
Jeff
PS - We have confirmed the SVs by both PCR and WGS with SV calling using Manta and lumpy.

Hey Jeff I'm not part of the plotsr group (love the software btw) but I've had experience with validating SVs.
I think you might want a different package to plot your SVs.
I've used samplot (Belyeu et al., 2021) to plot the read coverage and identification of discordant mapping short reads.
This will help you avoid assembling your new genomes (i doubt your 30X illumina would be good enough for that)
Hope that helps

Hi Ben,
Thanks for the suggestion to try samplot, I'll give it a try! I've been trying (so far unsuccessfully) to get either svviz or svviz2 up and running, lets hope installation of samplot is a bit more straight-forward. Thanks again!
Take care,
Jeff

Hi Jeff, I would agree with Ben that in your setting, other packages might be more useful. Samplot is indeed cool and works very well. Also, sometimes, simple IGV screentshots are the best option.
I have a feeling that you are working with smaller SVs (10s to 100s bp long). Plotsr focus more at the chromosome level variations, so these SVs might not be visualised by it.

Hi Manish,
Our SVs are actually quite large (10+ kb) and probably would look quite nice with the plotsr visualization, but trying to do de novo assembly from our 30X Illumina genomes seems to be more effort than it is worth. Even if we can't use it for this, I did want to let you know that plotsr is a very nice package, congrats on it!
Take care,
Jeff


Cargo xbuild failed when linking to high address

I'm trying to build and link my kernel to higher address but cargo xuild emits alots of errors.
rust-lld: error: core.dn6za2s3-cgu.4:(function core::fmt::num::imp::_$LT$impl$u20$core..fmt..Display$u20$for$u20$usize$GT$::fmt::h5a6ad2655a4131f3: .text._ZN4core3fmt3num3imp54_$LT$impl$u20$core..fmt..Display$u20$for$u20$usize$GT$3fmt17h5a6ad2655a4131f3E+0xFB): relocation R_X86_64_32 out of range:<PHONE_NUMBER>6221277272 is not in [0,<PHONE_NUMBER>]
          rust-lld: error: core.dn6za2s3-cgu.4:(function core::fmt::num::imp::_$LT$impl$u20$core..fmt..Display$u20$for$u20$u32$GT$::fmt::hb74b0354b9128009: .text._ZN4core3fmt3num3imp52_$LT$impl$u20$core..fmt..Display$u20$for$u20$u32$GT$3fmt17hb74b0354b9128009E+0xFB): relocation R_X86_64_32 out of range:<PHONE_NUMBER>6221277272 is not in [0,<PHONE_NUMBER>]

cargo xbuild --version
cargo-xbuild 0.5.31 (eede1a1 2020-05-13)

link.ld:
PHDRS
{
	load PT_LOAD;
}

SECTIONS
{
    . = 0xffff800000000000;

	.text : { *(.text) }
	.data : { *(.data) *(.rodata) }
	.bss : { *(.bss) }

    /DISCARD/ : { *(.eh_frame) *(.comment) }
}

rust-toolchain:
nightly-2020-02-24

.cargo/config:
[build]
rustflags = ["-Clink-arg=--script=link.ld"]

I don't think that this error is related to cargo-xbuild, given that it comes directly from the linker.
From a first guess, I think that this might be related to the code model in your target specification. Try setting it to large or kernel. See https://github.com/phil-opp/blog_os/issues/801 for more information.

I tried that too but still error.
x86_64-unknown-none.json:
{
  "llvm-target": "x86_64-unknown-none",
  "data-layout": "e-m:e-i64:64-f80:128-n8:16:32:64-S128",
  "arch": "x86_64",
  "target-endian": "little",
  "target-pointer-width": "64",
  "target-c-int-width": "32",
  "os": "none",
  "executables": true,
  "relocation-models": "static",
  "code-model": "large",
  "linker-flavor": "ld.lld",
  "linker": "rust-lld",
  "panic-strategy": "abort",
  "disable-redzone": true,
  "features": "-mmx,-sse,+soft-float"
}

Try cargo clean before building it to ensure that everything is compiled with the new code model. Also, try removing the "relocation-models": "static" key (I don't think that it applies anyway because it has to be "relocation-model" (singular) as far as I know).

Ah, my bad. i tried with both "relocation-model": "static" (signular) and delete that key, with cargo clean before caro xbuild --target x86_64-unknown-none, but still no hope :(

Hmm, I'm out of ideas then. Unfortunately, I don't have the time to help debugging this at the moment.

I look into the error messages and it seem that all the error is in the core crate itself, which could mean the core crate is not compiled with code-model large in mind. Maybe this can help somehow.

We build core and other sysroot libraries for the same target as the kernel, so if your target JSON file sets the code-model to large, it should also apply to core. Still, it might make sense to try compiling with cargo's own -Zbuild-std=core,alloc flag instead of cargo-xbuild, maybe there is something we're doing wrong. See https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#build-std for more information about the -Zbuild-std flag.

Could you please explain more? I don't quite know how to cross-compile core crate (that why i use cargo xbuild to do the work for me) and link it with my kernel.

As I run cargo build -Zbuild-std=core,alloc --target x86_64-unknown-none, it finish with error: Could not find specification for target "x86_64-unknown-none", the same for cargo xbuild -Zbuild-std=core,alloc --target x86_64-unknown-none

it greet me with this error: error: undefined symbol: memcpy

This is expected since -Zbuild-std currently builds the compiler_builtins crate without its mem feature. You can work around that error by adding the rlibc crate as dependency. Note that you also need to specify extern crate rlibc in your main.rs (even on the 2018 edition) to enforce that it is linked.

I tried again and it somehow process, but this time, a new error: ```  = note: the x86_64-unknown-none-3339195998372785209 target may not be installed

I tried again and it somehow process, but this time, a new error:
error[E0463]: can't find crate for `std`
  = note: the x86_64-unknown-none-3339195998372785209 target may not be installed

Are you sure that your binary/library is no_std? This error means that your crate or one of your dependencies tries to include the standard library, which is not available on bare metal.

Are you sure that your binary/library is no_std? This error means that your crate or one of your dependencies tries to include the standard library, which is not available on bare metal.

Yes, i'm very sure since i have '#![no_std]' line in my main.rs.
That error only appear when i have extern crate rlib; in my main.rs
Currently, I have extern crate rlib; in my main.rs and rlib = "0.0.1" in my Cargo.toml

By the way, I found my backup and have sysroot folder that build and link everything ok. That sysroot folder i built using cargo-xbuild, with rustc nightly-2020-03-24.
But I can't re-build that sysroot folder anymore, even i'm still using rustc nightly-2020-03-24 and cargo-build, with exactly same code and 86_64-unknown-none.json. It throw out a lots of relocation R_X86_64_32S out of range linking errors.
I can send you that sysroot folder if you whan a closer look.

Currently, I have extern crate rlib; in my main.rs and rlib = "0.0.1" in my Cargo.toml

You need to include the rlibc crate, not the (empty) rlib crate. The latter is not no_std, so that's likely where the issue is coming from.

Ah, my bad again, sorry about that :(
This time: main.rs extern crate rlibc; Cargo.toml: rlibc = ""
My command: cargo build -Zbuild-std=core,alloc --target x86_64-unknown-none.json
Good news: It's worked! So I think there is some problems with cargo-xbuild

Ok, could you try to create a minimal example project that works with -Zbuild-std but not cargo-xbuild? This would make debugging this issue much easier.

Here you are:
main.rs
#![no_std]									// don't link the Rust standard library
#![no_main]									// disable all Rust-level entry points

use core::panic::PanicInfo;
static TEST: usize = 1;

#[no_mangle]
pub extern "C" fn _start () -> ! {
	let a = &TEST as *const usize as u128;
	let b = a*128;
	loop {}
}

#[panic_handler]
pub fn my_panic_handler (_panic_info: &PanicInfo) -> ! {
	loop {}
}

rust-toolchain: nightly-2020-03-24
x86_64-unknown-none.json
{
  "llvm-target": "x86_64-unknown-none",
  "data-layout": "e-m:e-i64:64-f80:128-n8:16:32:64-S128",
  "arch": "x86_64",
  "target-endian": "little",
  "target-pointer-width": "64",
  "target-c-int-width": "32",
  "os": "none",
  "executables": true,
  "relocation-model": "static",
  "code-model": "large",
  "linker-flavor": "ld.lld",
  "linker": "rust-lld",
  "panic-strategy": "abort",
  "disable-redzone": true,
  "features": "-mmx,-sse,+soft-float"
}

link.ld
PHDRS
{
	load PT_LOAD;
}

SECTIONS
{
    . = 0xffff800000000000;

	.text : { *(.text) }
	.data : { *(.data) *(.rodata) }
	.bss : { *(.bss) }

    /DISCARD/ : { *(.eh_frame) *(.comment) }
}

.cargo/config
rustflags = ["-Clink-arg=--script=link.ld", "-Ccode-model=large", "-Crelocation-model=static"]

build command: cargo xbuild --target x86_64-unknown-none.json
Errors:
rust-lld: error: core.es9ltvmc-cgu.5:(function core::panicking::panic_fmt::he67cfa247b17aacf: .text._ZN4core9panicking9panic_fmt17he67cfa247b17aacfE+0x9): relocation R_X86_64_32S out of range: -140737488355240 is not in [-2147483648,<PHONE_NUMBER>]
          rust-lld: error: core.es9ltvmc-cgu.5:(function core::panicking::panic::h9ffef647d76b21f3: .text._ZN4core9panicking5panic17h9ffef647d76b21f3E+0x2F): relocation R_X86_64_32S out of range: -140737488355240 is not in [-2147483648,<PHONE_NUMBER>]
          rust-lld: error: core.es9ltvmc-cgu.5:(function core::panicking::panic_fmt::he67cfa247b17aacf: .text._ZN4core9panicking9panic_fmt17he67cfa247b17aacfE+0x12): relocation R_X86_64_32S out of range: -140737488355240 is not in [-2147483648,<PHONE_NUMBER>]

For this to build with cargo build, you just add extern crate rlibc; to main.rs and rlibc = "" to Cargo.toml

I tried it with both the current nightly, nightly 2020-03-24, and nightly 2020-03-23, and it always seems to work for me. It builds without any error.

It's weird then. Have you build it with config file at .cargo/config? I use that file to force cargo link to high address, the problem only appear when linking to high address.

FWIW, I am able to run the snippet provided with "code-model": "large". To run with "code-model": "kernel", I had to remove "relocation-model": "static"

By run, do you mean that it compile without error? Do the binary link correctly to address 0xffff800000000000? Do the init code of variable 'a' not stripped? Can you post the binary here?

I was able to link to a high address and run a quick test to verify.
https://github.com/vinaychandra/MoonDustKernel/tree/master
You can see that I'm actually using code model as kernel. Call make run will build and run qemu.

I see that your kernel can link and run just ok. Now i'm really out of ideal.


fix: SOF-1404 controlling ATEM's USK above 1

Fixes how timeline objects controlling Upstream Keyers are generated
(The indexes in the upstreamKeyers array are used by TSR instead of the upstreamKeyerId, so we need to fill the array with blank objects when controlling only the higher USKs)

Closing in favor of a TSR fix https://github.com/tv2/tv-automation-state-timeline-resolver/pull/53


Cannot verify MD5 hash when file name contains spaces when using egnyte.com

FTP Server: egnyte.com service
When a file name contains spaces, the egnyte.com service puts quotation marks around the [FilePath] in the "251" response even if there were no quotes in the "MD5" command.  This confuses the response parsing in the "GetMD5()" method in "FtpClient_Hash.cs", which checks "if (response.StartsWith(path))".
The spec on http://tools.ietf.org/html/draft-twine-ftpmd5-00#section-3.1 does not seem to be very clear about when quotes should be used.  But regardless, it would be good for FluentFTP to work with egnyte.com.
Logs :
Command:  MD5 /shared/import/file 1.xlsx
Response: 251 "/shared/import/file 1.xlsx" 48317576D6CA6C93641CCB06487AF457
File Verification: FAIL

Fixed by @Nimelo. Go thank him!


WFLY 17645 component upgrade for transactions

https://issues.redhat.com/browse/WFLY-17645

Hello, mmusgrov. I'm waiting for one of the admins to verify this patch with /ok-to-test in a comment.

Thanks @mmusgrov and @jbliznak


Request unsafe for browser client domain: dialogflow.googleapis.com"

Hi, I'm using nodejs to make a gateway so client can post api to get results from dialogflow. But recently, this message is displayed instead of dialogflow information.
"3 INVALID_ARGUMENT: Request unsafe for browser client domain: dialogflow.googleapis.com"

I'm getting the same issue. Our production app is failing because of this.

I'm getting the exact same error.
I'm setting up a DialogFlow wrapper and I'm using the DialogFlow JavaScript SDK. But, I'm getting the following error:
Error: Request unsafe for browser client domain: dialogflow.googleapis.com
This was working before, but I'm not sure why it suddenly stopped working.
I've tried reverting all code to a version that worked. I'm sure it's a DialogFlow error.
const intentDetectResponse = await sessionClient.detectIntent(request)

The complete error log is as follows:
{ Error: Request unsafe for browser client domain: dialogflow.googleapis.com
    at Http2CallStream.call.on (/Users/NewProject/node_modules/@grpc/grpc-js/build/src/client.js:101:45)
    at Http2CallStream.emit (events.js:194:15)
    at process.nextTick (/Users/NewProject/node_modules/@grpc/grpc-js/build/src/call-stream.js:71:22)
    at process.internalTickCallback (internal/process/next_tick.js:70:11)
  code: 3,
  details:
   'Request unsafe for browser client domain: dialogflow.googleapis.com',
  metadata:
   Metadata {
     options: undefined,
     internalRepr: Map { 'grpc-server-stats-bin' => [Array] } } }

Facing the same issue on production for the last couple of hours all of a sudden.

Facing this error
Error: 3 INVALID_ARGUMENT: Request unsafe for browser client domain: dialogflow.googleapis.com

I'm getting the same issue. I used v0.9.0 and upgraded to the latest version v0.10.3 also face the same error log:
INVALID_ARGUMENT: Request unsafe for browser client domain: dialogflow.googleapis.com
    at Object.exports.createStatusError (/app/node_modules/dialogflow/node_modules/grpc/src/common.js:91:15)
    at Object.onReceiveStatus (/app/node_modules/dialogflow/node_modules/grpc/src/client_interceptors.js:1204:28)
    at InterceptingListener._callNext (/app/node_modules/dialogflow/node_modules/grpc/src/client_interceptors.js:568:42)
    at InterceptingListener.onReceiveStatus (/app/node_modules/dialogflow/node_modules/grpc/src/client_interceptors.js:618:8)
    at callback (/app/node_modules/dialogflow/node_modules/grpc/src/client_interceptors.js:845:24)
extra info: { Error: 3 INVALID_ARGUMENT: Request unsafe for browser client domain: dialogflow.googleapis.com
    at Object.exports.createStatusError (/app/node_modules/dialogflow/node_modules/grpc/src/common.js:91:15)
    at Object.onReceiveStatus (/app/node_modules/dialogflow/node_modules/grpc/src/client_interceptors.js:1204:28)
    at InterceptingListener._callNext (/app/node_modules/dialogflow/node_modules/grpc/src/client_interceptors.js:568:42)
    at InterceptingListener.onReceiveStatus (/app/node_modules/dialogflow/node_modules/grpc/src/client_interceptors.js:618:8)
    at callback (/app/node_modules/dialogflow/node_modules/grpc/src/client_interceptors.js:845:24)
  code: 3,
  metadata: Metadata { _internal_repr: { 'grpc-server-stats-bin': [Array] } },
  details: 'Request unsafe for browser client domain: dialogflow.googleapis.com' }

{ Error: 3 INVALID_ARGUMENT: Request unsafe for browser client domain: dialogflow.googleapis.com     at Object.exports.createStatusError (/home/jitendra/chatservices/node_modules/grpc/src/common.js:91:15)     at Object.onReceiveStatus (/home/jitendra/chatservices/node_modules/grpc/src/client_interceptors.js:1204:28)     at InterceptingListener._callNext (/home/jitendra/chatservices/node_modules/grpc/src/client_interceptors.js:568:42)     at InterceptingListener.onReceiveStatus (/home/jitendra/chatservices/node_modules/grpc/src/client_interceptors.js:618:8)     at callback (/home/jitendra/chatservices/node_modules/grpc/src/client_interceptors.js:845:24)   code: 3,   metadata: Metadata { _internal_repr: { 'grpc-server-stats-bin': [Array] } },   details: 'Request unsafe for browser client domain: dialogflow.googleapis.com' }

My detectIntent request successes now


Development Branch: NUM_ASTERIX breaking in key_to_map implementation

BLE Keyboard Repo (forked by me):
const uint8_t KEY_NUM_ASTERISK = 0xDD;
const uint8_t NUM_ASTERIX = 0xDD; // kept for bc

However the code in TFAction.cpp is as follows:
#define KEY_TO_MAP(k)         \
    {                         \
        QUOTE(k), { KEY_##k } \
    }

KEY_TO_MAP(NUM_ASTERIX)

This will turn NUM_ASTERIX into KEY_NUM_ASTERIX and break the build (Not defined in scope error). I'd recommend moving to KEY_TO_MAP(NUM_ASTERISK)
Suggested fix: Use the correct name for the Asterisk in the fork of the BLE repo :) Furthermore, the code is now compatible with the original of the BLE Keyboard Library, so I suggest to remove the reference to the fork, and encourage users to install the original library.

https://github.com/DustinWatts/FreeTouchDeck/commit/264aa48c597dc07a494c1786b9e8c162a7d39ec8


Using ng-model-options="{ updateOn: 'blur' }" with FCSA doesn't update model

When using FCSA and ng-model-options="{ updateOn: 'blur' }" the model is not updated.  I believe it is related to this SO Post as well.

Hey! I have that issue too. How can I fix it?


Pagespeed rating drops after a couple of hours? Why?

Pagespeed rating drops after a couple of hours? Why?
I did some analysis on https://developers.google.com/speed/pagespeed/insights and after a few runs the rating was at maximum of 68%m - 94%d.
15:03 68%m - 94%d
After 2 hours and 27 minutes I run 3 more analysis.
First analysis shows a significant drop in rating which finally increases to the previous level on the 3rd run. Here are the redults:

RATING: 45%m - 71%d with the following messages:

[Thu, 09 May 2019 15:03:20 GMT] [Info] [5477] Shutting down PageSpeed child
[Thu, 09 May 2019 17:29:28 GMT] [Info] [5514] Need to check cache size against target<PHONE_NUMBER>
[Thu, 09 May 2019 17:29:29 GMT] [Info] [5514] Cannot combine http://<IP_ADDRESS>/journal-cache/_4a4cb49ef93ac16b2313bb452ac35f17.css: resource not combinable, reason: CSS parse error
[Thu, 09 May 2019 17:29:29 GMT] [Info] [5514] Need to check cache size against target<PHONE_NUMBER>
[Thu, 09 May 2019 17:29:29 GMT] [Info] [5514] Cannot combine http://<IP_ADDRESS>/journal-cache/_118ac6eae4ff651d333b1193002a3dda.js: resource not combinable, reason: File seems to look for its URL
[Thu, 09 May 2019 17:29:29 GMT] [Info] [5514] Need to check cache size against target<PHONE_NUMBER>
[Thu, 09 May 2019 17:29:29 GMT] [Info] [5514] Need to check cache size against target<PHONE_NUMBER>
[Thu, 09 May 2019 17:29:29 GMT] [Info] [5483] Cannot combine http://<IP_ADDRESS>/journal-cache/_8f4eff1d0f916f37b5f61c1add6219eb.js: resource not combinable, reason: File seems to look for its URL
[Thu, 09 May 2019 17:29:29 GMT] [Info] [5483] Need to check cache size against target<PHONE_NUMBER>
[Thu, 09 May 2019 17:29:29 GMT] [Warning] [5514] CSS parsing error in http://<IP_ADDRESS>/journal-cache/_4a4cb49ef93ac16b2313bb452ac35f17.css
[Thu, 09 May 2019 17:29:29 GMT] [Info] [5514] Cache entry is expired: http://<IP_ADDRESS>/catalog/view/javascript/bootstrap/fonts/glyphicons-halflings-regular.eot?#iefix (fragment=<IP_ADDRESS>)
[Thu, 09 May 2019 17:29:29 GMT] [Info] [5514] Cache entry is expired: http://<IP_ADDRESS>/catalog/view/javascript/bootstrap/fonts/glyphicons-halflings-regular.svg#glyphicons_halflingsregular (fragment=<IP_ADDRESS>)
[Thu, 09 May 2019 17:29:29 GMT] [Info] [5514] Cache entry is expired: http://<IP_ADDRESS>/catalog/view/javascript/font-awesome/fonts/fontawesome-webfont.eot?#iefix&v=4.4.0 (fragment=<IP_ADDRESS>)
[Thu, 09 May 2019 17:29:29 GMT] [Info] [5514] Cache entry is expired: http://<IP_ADDRESS>/catalog/view/javascript/font-awesome/fonts/fontawesome-webfont.svg?v=4.4.0#fontawesomeregular (fragment=<IP_ADDRESS>)
[Thu, 09 May 2019 17:29:29 GMT] [Error] [5514] PageSpeed Serf fetch failure rate extremely high; only 0 of 50 recent fetches fully successful; is fetching working?
[Thu, 09 May 2019 17:29:29 GMT] [Info] [5514] Cache entry is expired: http://<IP_ADDRESS>/catalog/view/theme/journal2/css/icons/fonts/journal-icons.eot?#iefix (fragment=<IP_ADDRESS>)
[Thu, 09 May 2019 17:29:29 GMT] [Info] [5514] Cache entry is expired: http://<IP_ADDRESS>/catalog/view/theme/journal2/css/icons/fonts/journal-icons.svg#journal-icons (fragment=<IP_ADDRESS>)
[Thu, 09 May 2019 17:29:29 GMT] [Info] [5514] Cache entry is expired: http://<IP_ADDRESS>/catalog/view/theme/journal2/lib/lightgallery/fonts/lg.eot?#iefixn1z373 (fragment=<IP_ADDRESS>)
[Thu, 09 May 2019 17:29:29 GMT] [Info] [5514] Need to check cache size against target<PHONE_NUMBER>
[Thu, 09 May 2019 17:29:29 GMT] [Info] [5514] Checking cache size against target<PHONE_NUMBER> and inode count against target 500000
[Thu, 09 May 2019 17:29:29 GMT] [Info] [5514] Cache entry is expired: http://<IP_ADDRESS>/catalog/view/theme/journal2/lib/lightgallery/fonts/lg.svg?n1z373#lg (fragment=<IP_ADDRESS>)
[Thu, 09 May 2019 17:29:29 GMT] [Info] [5514] Cache entry is expired: http://<IP_ADDRESS>/catalog/view/theme/journal2/lib/rs-plugin/font/revicons.eot?5510888#iefix (fragment=<IP_ADDRESS>)
[Thu, 09 May 2019 17:29:29 GMT] [Info] [5514] Cache entry is expired: http://<IP_ADDRESS>/catalog/view/theme/journal2/lib/rs-plugin/font/revicons.svg?5510888#revicons (fragment=<IP_ADDRESS>)
[Thu, 09 May 2019 17:29:29 GMT] [Info] [5514] HTTPCache key=http://<IP_ADDRESS>/catalog/view/javascript/bootstrap/fonts/glyphicons-halflings-regular.eot?#iefix fragment=<IP_ADDRESS>: remembering recent failure for 299 seconds.
[Thu, 09 May 2019 17:29:29 GMT] [Info] [5514] HTTPCache key=http://<IP_ADDRESS>/catalog/view/javascript/bootstrap/fonts/glyphicons-halflings-regular.svg#glyphicons_halflingsregular fragment=<IP_ADDRESS>: remembering recent failure for 299 seconds.
[Thu, 09 May 2019 17:29:29 GMT] [Info] [5514] HTTPCache key=http://<IP_ADDRESS>/catalog/view/javascript/font-awesome/fonts/fontawesome-webfont.eot?#iefix&v=4.4.0 fragment=<IP_ADDRESS>: remembering recent failure for 299 seconds.
[Thu, 09 May 2019 17:29:29 GMT] [Info] [5514] HTTPCache key=http://<IP_ADDRESS>/catalog/view/javascript/font-awesome/fonts/fontawesome-webfont.svg?v=4.4.0#fontawesomeregular fragment=<IP_ADDRESS>: remembering recent failure for 299 seconds.
[Thu, 09 May 2019 17:29:29 GMT] [Info] [5514] HTTPCache key=http://<IP_ADDRESS>/catalog/view/theme/journal2/css/icons/fonts/journal-icons.eot?#iefix fragment=<IP_ADDRESS>: remembering recent failure for 299 seconds.
[Thu, 09 May 2019 17:29:29 GMT] [Info] [5514] HTTPCache key=http://<IP_ADDRESS>/catalog/view/theme/journal2/css/icons/fonts/journal-icons.svg#journal-icons fragment=<IP_ADDRESS>: remembering recent failure for 299 seconds.
[Thu, 09 May 2019 17:29:29 GMT] [Info] [5514] HTTPCache key=http://<IP_ADDRESS>/catalog/view/theme/journal2/lib/lightgallery/fonts/lg.eot?#iefixn1z373 fragment=<IP_ADDRESS>: remembering recent failure for 299 seconds.
[Thu, 09 May 2019 17:29:29 GMT] [Info] [5514] HTTPCache key=http://<IP_ADDRESS>/catalog/view/theme/journal2/lib/lightgallery/fonts/lg.svg?n1z373#lg fragment=<IP_ADDRESS>: remembering recent failure for 299 seconds.
[Thu, 09 May 2019 17:29:29 GMT] [Info] [5514] HTTPCache key=http://<IP_ADDRESS>/catalog/view/theme/journal2/lib/rs-plugin/font/revicons.eot?5510888#iefix fragment=<IP_ADDRESS>: remembering recent failure for 299 seconds.
[Thu, 09 May 2019 17:29:29 GMT] [Info] [5514] HTTPCache key=http://<IP_ADDRESS>/catalog/view/theme/journal2/lib/rs-plugin/font/revicons.svg?5510888#revicons fragment=<IP_ADDRESS>: remembering recent failure for 299 seconds.
[Thu, 09 May 2019 17:29:29 GMT] [Warning] [5483] CSS parsing error in http://<IP_ADDRESS>/journal-cache/_4a4cb49ef93ac16b2313bb452ac35f17.css
[Thu, 09 May 2019 17:29:29 GMT] [Info] [5514] File cache size is 138891264 and contains 3923 inodes; no cleanup needed.
[Thu, 09 May 2019 17:29:29 GMT] [Info] [5483] HTTPCache key=http://<IP_ADDRESS>/catalog/view/javascript/bootstrap/fonts/glyphicons-halflings-regular.eot?#iefix fragment=<IP_ADDRESS>: remembering recent failure for 299 seconds.
[Thu, 09 May 2019 17:29:29 GMT] [Info] [5483] HTTPCache key=http://<IP_ADDRESS>/catalog/view/javascript/bootstrap/fonts/glyphicons-halflings-regular.svg#glyphicons_halflingsregular fragment=<IP_ADDRESS>: remembering recent failure for 299 seconds.
[Thu, 09 May 2019 17:29:29 GMT] [Info] [5483] HTTPCache key=http://<IP_ADDRESS>/catalog/view/javascript/font-awesome/fonts/fontawesome-webfont.eot?#iefix&v=4.4.0 fragment=<IP_ADDRESS>: remembering recent failure for 299 seconds.
[Thu, 09 May 2019 17:29:29 GMT] [Info] [5483] HTTPCache key=http://<IP_ADDRESS>/catalog/view/javascript/font-awesome/fonts/fontawesome-webfont.svg?v=4.4.0#fontawesomeregular fragment=<IP_ADDRESS>: remembering recent failure for 299 seconds.
[Thu, 09 May 2019 17:29:29 GMT] [Info] [5483] HTTPCache key=http://<IP_ADDRESS>/catalog/view/theme/journal2/css/icons/fonts/journal-icons.eot?#iefix fragment=<IP_ADDRESS>: remembering recent failure for 299 seconds.
[Thu, 09 May 2019 17:29:29 GMT] [Info] [5483] HTTPCache key=http://<IP_ADDRESS>/catalog/view/theme/journal2/css/icons/fonts/journal-icons.svg#journal-icons fragment=<IP_ADDRESS>: remembering recent failure for 299 seconds.
[Thu, 09 May 2019 17:29:29 GMT] [Info] [5483] HTTPCache key=http://<IP_ADDRESS>/catalog/view/theme/journal2/lib/lightgallery/fonts/lg.eot?#iefixn1z373 fragment=<IP_ADDRESS>: remembering recent failure for 299 seconds.
[Thu, 09 May 2019 17:29:29 GMT] [Info] [5483] HTTPCache key=http://<IP_ADDRESS>/catalog/view/theme/journal2/lib/lightgallery/fonts/lg.svg?n1z373#lg fragment=<IP_ADDRESS>: remembering recent failure for 299 seconds.
[Thu, 09 May 2019 17:29:29 GMT] [Info] [5483] HTTPCache key=http://<IP_ADDRESS>/catalog/view/theme/journal2/lib/rs-plugin/font/revicons.eot?5510888#iefix fragment=<IP_ADDRESS>: remembering recent failure for 299 seconds.
[Thu, 09 May 2019 17:29:29 GMT] [Info] [5483] HTTPCache key=http://<IP_ADDRESS>/catalog/view/theme/journal2/lib/rs-plugin/font/revicons.svg?5510888#revicons fragment=<IP_ADDRESS>: remembering recent failure for 299 seconds.
[Thu, 09 May 2019 17:29:29 GMT] [Warning] [5514] CSS parsing error in http://<IP_ADDRESS>/journal-cache/_4a4cb49ef93ac16b2313bb452ac35f17.css
[Thu, 09 May 2019 17:29:29 GMT] [Info] [5514] HTTPCache key=http://<IP_ADDRESS>/catalog/view/javascript/bootstrap/fonts/glyphicons-halflings-regular.eot?#iefix fragment=<IP_ADDRESS>: remembering recent failure for 299 seconds.
[Thu, 09 May 2019 17:29:29 GMT] [Info] [5514] HTTPCache key=http://<IP_ADDRESS>/catalog/view/javascript/bootstrap/fonts/glyphicons-halflings-regular.svg#glyphicons_halflingsregular fragment=<IP_ADDRESS>: remembering recent failure for 299 seconds.
[Thu, 09 May 2019 17:29:29 GMT] [Info] [5514] HTTPCache key=http://<IP_ADDRESS>/catalog/view/javascript/font-awesome/fonts/fontawesome-webfont.eot?#iefix&v=4.4.0 fragment=<IP_ADDRESS>: remembering recent failure for 299 seconds.
[Thu, 09 May 2019 17:29:29 GMT] [Info] [5514] HTTPCache key=http://<IP_ADDRESS>/catalog/view/javascript/font-awesome/fonts/fontawesome-webfont.svg?v=4.4.0#fontawesomeregular fragment=<IP_ADDRESS>: remembering recent failure for 299 seconds.
[Thu, 09 May 2019 17:29:29 GMT] [Info] [5514] HTTPCache key=http://<IP_ADDRESS>/catalog/view/theme/journal2/css/icons/fonts/journal-icons.eot?#iefix fragment=<IP_ADDRESS>: remembering recent failure for 299 seconds.
[Thu, 09 May 2019 17:29:29 GMT] [Info] [5514] HTTPCache key=http://<IP_ADDRESS>/catalog/view/theme/journal2/css/icons/fonts/journal-icons.svg#journal-icons fragment=<IP_ADDRESS>: remembering recent failure for 299 seconds.
[Thu, 09 May 2019 17:29:29 GMT] [Info] [5514] HTTPCache key=http://<IP_ADDRESS>/catalog/view/theme/journal2/lib/lightgallery/fonts/lg.eot?#iefixn1z373 fragment=<IP_ADDRESS>: remembering recent failure for 299 seconds.
[Thu, 09 May 2019 17:29:29 GMT] [Info] [5514] HTTPCache key=http://<IP_ADDRESS>/catalog/view/theme/journal2/lib/lightgallery/fonts/lg.svg?n1z373#lg fragment=<IP_ADDRESS>: remembering recent failure for 299 seconds.
[Thu, 09 May 2019 17:29:29 GMT] [Info] [5514] HTTPCache key=http://<IP_ADDRESS>/catalog/view/theme/journal2/lib/rs-plugin/font/revicons.eot?5510888#iefix fragment=<IP_ADDRESS>: remembering recent failure for 299 seconds.
[Thu, 09 May 2019 17:29:29 GMT] [Info] [5514] HTTPCache key=http://<IP_ADDRESS>/catalog/view/theme/journal2/lib/rs-plugin/font/revicons.svg?5510888#revicons fragment=<IP_ADDRESS>: remembering recent failure for 299 seconds.
[Thu, 09 May 2019 17:29:29 GMT] [Info] [10759] Reusing shared memory for path: /var/cache/mod_pagespeed/ purge .
[Thu, 09 May 2019 17:29:30 GMT] [Info] [10760] Reusing shared memory for path: /var/cache/mod_pagespeed/ purge .
[Thu, 09 May 2019 17:29:30 GMT] [Info] [10761] Reusing shared memory for path: /var/cache/mod_pagespeed/ purge .
[Thu, 09 May 2019 17:29:31 GMT] [Info] [10762] Reusing shared memory for path: /var/cache/mod_pagespeed/ purge .
[Thu, 09 May 2019 17:29:31 GMT] [Info] [10764] Reusing shared memory for path: /var/cache/mod_pagespeed/ purge .
[Thu, 09 May 2019 17:29:31 GMT] [Info] [10765] Reusing shared memory for path: /var/cache/mod_pagespeed/ purge .
[Thu, 09 May 2019 17:29:31 GMT] [Info] [10763] Reusing shared memory for path: /var/cache/mod_pagespeed/ purge .
[Thu, 09 May 2019 17:29:32 GMT] [Info] [10767] Reusing shared memory for path: /var/cache/mod_pagespeed/ purge .
[Thu, 09 May 2019 17:29:32 GMT] [Info] [10769] Reusing shared memory for path: /var/cache/mod_pagespeed/ purge .
[Thu, 09 May 2019 17:29:32 GMT] [Info] [10772] Reusing shared memory for path: /var/cache/mod_pagespeed/ purge .
[Thu, 09 May 2019 17:29:32 GMT] [Info] [10771] Reusing shared memory for path: /var/cache/mod_pagespeed/ purge .
[Thu, 09 May 2019 17:29:32 GMT] [Info] [10770] Reusing shared memory for path: /var/cache/mod_pagespeed/ purge .
[Thu, 09 May 2019 17:29:32 GMT] [Info] [10773] Reusing shared memory for path: /var/cache/mod_pagespeed/ purge .
[Thu, 09 May 2019 17:29:32 GMT] [Info] [10768] Reusing shared memory for path: /var/cache/mod_pagespeed/ purge .
[Thu, 09 May 2019 17:29:32 GMT] [Info] [10774] Reusing shared memory for path: /var/cache/mod_pagespeed/ purge .
[Thu, 09 May 2019 17:29:35 GMT] [Warning] [5785] CSS parsing error in http://<IP_ADDRESS>/journal-cache/_4a4cb49ef93ac16b2313bb452ac35f17.css
[Thu, 09 May 2019 17:29:35 GMT] [Info] [5785] HTTPCache key=http://<IP_ADDRESS>/catalog/view/javascript/bootstrap/fonts/glyphicons-halflings-regular.eot?#iefix fragment=<IP_ADDRESS>: remembering recent failure for 293 seconds.
[Thu, 09 May 2019 17:29:35 GMT] [Info] [5785] HTTPCache key=http://<IP_ADDRESS>/catalog/view/javascript/bootstrap/fonts/glyphicons-halflings-regular.svg#glyphicons_halflingsregular fragment=<IP_ADDRESS>: remembering recent failure for 293 seconds.
[Thu, 09 May 2019 17:29:35 GMT] [Info] [5785] HTTPCache key=http://<IP_ADDRESS>/catalog/view/javascript/font-awesome/fonts/fontawesome-webfont.eot?#iefix&v=4.4.0 fragment=<IP_ADDRESS>: remembering recent failure for 293 seconds.
[Thu, 09 May 2019 17:29:35 GMT] [Info] [5785] HTTPCache key=http://<IP_ADDRESS>/catalog/view/javascript/font-awesome/fonts/fontawesome-webfont.svg?v=4.4.0#fontawesomeregular fragment=<IP_ADDRESS>: remembering recent failure for 293 seconds.
[Thu, 09 May 2019 17:29:35 GMT] [Info] [5785] HTTPCache key=http://<IP_ADDRESS>/catalog/view/theme/journal2/css/icons/fonts/journal-icons.eot?#iefix fragment=<IP_ADDRESS>: remembering recent failure for 293 seconds.
[Thu, 09 May 2019 17:29:35 GMT] [Info] [5785] HTTPCache key=http://<IP_ADDRESS>/catalog/view/theme/journal2/css/icons/fonts/journal-icons.svg#journal-icons fragment=<IP_ADDRESS>: remembering recent failure for 293 seconds.
[Thu, 09 May 2019 17:29:35 GMT] [Info] [5785] HTTPCache key=http://<IP_ADDRESS>/catalog/view/theme/journal2/lib/lightgallery/fonts/lg.eot?#iefixn1z373 fragment=<IP_ADDRESS>: remembering recent failure for 293 seconds.
[Thu, 09 May 2019 17:29:35 GMT] [Info] [5785] HTTPCache key=http://<IP_ADDRESS>/catalog/view/theme/journal2/lib/lightgallery/fonts/lg.svg?n1z373#lg fragment=<IP_ADDRESS>: remembering recent failure for 293 seconds.
[Thu, 09 May 2019 17:29:35 GMT] [Info] [5785] HTTPCache key=http://<IP_ADDRESS>/catalog/view/theme/journal2/lib/rs-plugin/font/revicons.eot?5510888#iefix fragment=<IP_ADDRESS>: remembering recent failure for 293 seconds.
[Thu, 09 May 2019 17:29:35 GMT] [Info] [5785] HTTPCache key=http://<IP_ADDRESS>/catalog/view/theme/journal2/lib/rs-plugin/font/revicons.svg?5510888#revicons fragment=<IP_ADDRESS>: remembering recent failure for 293 seconds.
[Thu, 09 May 2019 17:29:36 GMT] [Info] [10769] Shutting down PageSpeed child
[Thu, 09 May 2019 17:29:37 GMT] [Info] [10771] Shutting down PageSpeed child
[Thu, 09 May 2019 17:29:38 GMT] [Info] [10773] Shutting down PageSpeed child
[Thu, 09 May 2019 17:29:39 GMT] [Info] [10768] Shutting down PageSpeed child
[Thu, 09 May 2019 17:29:40 GMT] [Info] [10770] Shutting down PageSpeed child
[Thu, 09 May 2019 17:29:41 GMT] [Info] [10772] Shutting down PageSpeed child
[Thu, 09 May 2019 17:29:42 GMT] [Info] [5427] Shutting down PageSpeed child
[Thu, 09 May 2019 17:29:43 GMT] [Info] [5467] Shutting down PageSpeed child
[Thu, 09 May 2019 17:29:44 GMT] [Info] [10761] Shutting down PageSpeed child
[Thu, 09 May 2019 17:29:45 GMT] [Info] [10762] Shutting down PageSpeed child
[Thu, 09 May 2019 17:29:46 GMT] [Info] [10765] Shutting down PageSpeed child
[Thu, 09 May 2019 17:29:47 GMT] [Info] [10763] Shutting down PageSpeed child
[Thu, 09 May 2019 17:29:48 GMT] [Info] [10767] Shutting down PageSpeed child
[Thu, 09 May 2019 17:29:49 GMT] [Info] [10760] Shutting down PageSpeed child
[Thu, 09 May 2019 17:29:55 GMT] [Info] [5793] Shutting down PageSpeed child

RATING: 42%m - 75%d

[Thu, 09 May 2019 17:33:18 GMT] [Info] [10889] Reusing shared memory for path: /var/cache/mod_pagespeed/ purge .
[Thu, 09 May 2019 17:33:19 GMT] [Info] [10893] Reusing shared memory for path: /var/cache/mod_pagespeed/ purge .
[Thu, 09 May 2019 17:33:19 GMT] [Info] [10894] Reusing shared memory for path: /var/cache/mod_pagespeed/ purge .
[Thu, 09 May 2019 17:33:20 GMT] [Info] [10895] Reusing shared memory for path: /var/cache/mod_pagespeed/ purge .
[Thu, 09 May 2019 17:33:20 GMT] [Info] [10898] Reusing shared memory for path: /var/cache/mod_pagespeed/ purge .
[Thu, 09 May 2019 17:33:20 GMT] [Info] [10897] Reusing shared memory for path: /var/cache/mod_pagespeed/ purge .
[Thu, 09 May 2019 17:33:20 GMT] [Info] [10896] Reusing shared memory for path: /var/cache/mod_pagespeed/ purge .
[Thu, 09 May 2019 17:33:21 GMT] [Info] [10899] Reusing shared memory for path: /var/cache/mod_pagespeed/ purge .
[Thu, 09 May 2019 17:33:21 GMT] [Info] [10902] Reusing shared memory for path: /var/cache/mod_pagespeed/ purge .
[Thu, 09 May 2019 17:33:21 GMT] [Info] [10903] Reusing shared memory for path: /var/cache/mod_pagespeed/ purge .
[Thu, 09 May 2019 17:33:21 GMT] [Info] [10904] Reusing shared memory for path: /var/cache/mod_pagespeed/ purge .
[Thu, 09 May 2019 17:33:21 GMT] [Info] [10901] Reusing shared memory for path: /var/cache/mod_pagespeed/ purge .
[Thu, 09 May 2019 17:33:21 GMT] [Info] [10900] Reusing shared memory for path: /var/cache/mod_pagespeed/ purge .
[Thu, 09 May 2019 17:33:21 GMT] [Info] [10905] Reusing shared memory for path: /var/cache/mod_pagespeed/ purge .
[Thu, 09 May 2019 17:33:21 GMT] [Info] [10906] Reusing shared memory for path: /var/cache/mod_pagespeed/ purge .
[Thu, 09 May 2019 17:33:25 GMT] [Info] [10905] Shutting down PageSpeed child
[Thu, 09 May 2019 17:33:26 GMT] [Info] [10903] Shutting down PageSpeed child
[Thu, 09 May 2019 17:33:27 GMT] [Info] [10900] Shutting down PageSpeed child
[Thu, 09 May 2019 17:33:28 GMT] [Info] [10901] Shutting down PageSpeed child
[Thu, 09 May 2019 17:33:29 GMT] [Info] [5425] Shutting down PageSpeed child
[Thu, 09 May 2019 17:33:30 GMT] [Info] [10894] Shutting down PageSpeed child
[Thu, 09 May 2019 17:33:31 GMT] [Info] [10893] Shutting down PageSpeed child
[Thu, 09 May 2019 17:33:32 GMT] [Info] [10895] Shutting down PageSpeed child
[Thu, 09 May 2019 17:33:33 GMT] [Info] [10896] Shutting down PageSpeed child
[Thu, 09 May 2019 17:33:34 GMT] [Info] [10897] Shutting down PageSpeed child
[Thu, 09 May 2019 17:33:35 GMT] [Info] [10898] Shutting down PageSpeed child
[Thu, 09 May 2019 17:33:36 GMT] [Info] [10889] Shutting down PageSpeed child
[Thu, 09 May 2019 17:33:37 GMT] [Info] [10904] Shutting down PageSpeed child
[Thu, 09 May 2019 17:33:38 GMT] [Info] [5514] Shutting down PageSpeed child
[Thu, 09 May 2019 17:33:39 GMT] [Info] [5782] Shutting down PageSpeed child

RATING: 70%m - 94%d

[Thu, 09 May 2019 17:35:05 GMT] [Info] [10759] Cannot combine http://<IP_ADDRESS>/journal-cache/_4a4cb49ef93ac16b2313bb452ac35f17.css: resource not combinable, reason: CSS parse error
[Thu, 09 May 2019 17:35:05 GMT] [Info] [10759] Cannot combine http://<IP_ADDRESS>/journal-cache/_118ac6eae4ff651d333b1193002a3dda.js: resource not combinable, reason: File seems to look for its URL
[Thu, 09 May 2019 17:35:05 GMT] [Info] [10774] Cannot combine http://<IP_ADDRESS>/journal-cache/_8f4eff1d0f916f37b5f61c1add6219eb.js: resource not combinable, reason: File seems to look for its URL
[Thu, 09 May 2019 17:35:05 GMT] [Warning] [10759] CSS parsing error in http://<IP_ADDRESS>/journal-cache/_4a4cb49ef93ac16b2313bb452ac35f17.css
[Thu, 09 May 2019 17:35:05 GMT] [Info] [10759] Cache entry is expired: http://<IP_ADDRESS>/catalog/view/javascript/bootstrap/fonts/glyphicons-halflings-regular.eot?#iefix (fragment=<IP_ADDRESS>)
[Thu, 09 May 2019 17:35:05 GMT] [Info] [10759] Cache entry is expired: http://<IP_ADDRESS>/catalog/view/javascript/bootstrap/fonts/glyphicons-halflings-regular.svg#glyphicons_halflingsregular (fragment=<IP_ADDRESS>)
[Thu, 09 May 2019 17:35:05 GMT] [Info] [10759] Cache entry is expired: http://<IP_ADDRESS>/catalog/view/javascript/font-awesome/fonts/fontawesome-webfont.eot?#iefix&v=4.4.0 (fragment=<IP_ADDRESS>)
[Thu, 09 May 2019 17:35:05 GMT] [Info] [10759] Cache entry is expired: http://<IP_ADDRESS>/catalog/view/javascript/font-awesome/fonts/fontawesome-webfont.svg?v=4.4.0#fontawesomeregular (fragment=<IP_ADDRESS>)
[Thu, 09 May 2019 17:35:05 GMT] [Info] [10759] Cache entry is expired: http://<IP_ADDRESS>/catalog/view/theme/journal2/css/icons/fonts/journal-icons.eot?#iefix (fragment=<IP_ADDRESS>)
[Thu, 09 May 2019 17:35:05 GMT] [Info] [10759] Cache entry is expired: http://<IP_ADDRESS>/catalog/view/theme/journal2/css/icons/fonts/journal-icons.svg#journal-icons (fragment=<IP_ADDRESS>)
[Thu, 09 May 2019 17:35:05 GMT] [Info] [10759] Cache entry is expired: http://<IP_ADDRESS>/catalog/view/theme/journal2/lib/lightgallery/fonts/lg.eot?#iefixn1z373 (fragment=<IP_ADDRESS>)
[Thu, 09 May 2019 17:35:05 GMT] [Info] [10759] Cache entry is expired: http://<IP_ADDRESS>/catalog/view/theme/journal2/lib/lightgallery/fonts/lg.svg?n1z373#lg (fragment=<IP_ADDRESS>)
[Thu, 09 May 2019 17:35:05 GMT] [Info] [10759] Cache entry is expired: http://<IP_ADDRESS>/catalog/view/theme/journal2/lib/rs-plugin/font/revicons.eot?5510888#iefix (fragment=<IP_ADDRESS>)
[Thu, 09 May 2019 17:35:05 GMT] [Info] [10759] Cache entry is expired: http://<IP_ADDRESS>/catalog/view/theme/journal2/lib/rs-plugin/font/revicons.svg?5510888#revicons (fragment=<IP_ADDRESS>)
[Thu, 09 May 2019 17:35:05 GMT] [Info] [10759] HTTPCache key=http://<IP_ADDRESS>/catalog/view/javascript/bootstrap/fonts/glyphicons-halflings-regular.eot?#iefix fragment=<IP_ADDRESS>: remembering recent failure for 299 seconds.
[Thu, 09 May 2019 17:35:05 GMT] [Info] [10759] HTTPCache key=http://<IP_ADDRESS>/catalog/view/javascript/bootstrap/fonts/glyphicons-halflings-regular.svg#glyphicons_halflingsregular fragment=<IP_ADDRESS>: remembering recent failure for 299 seconds.
[Thu, 09 May 2019 17:35:05 GMT] [Info] [10759] HTTPCache key=http://<IP_ADDRESS>/catalog/view/javascript/font-awesome/fonts/fontawesome-webfont.eot?#iefix&v=4.4.0 fragment=<IP_ADDRESS>: remembering recent failure for 299 seconds.
[Thu, 09 May 2019 17:35:05 GMT] [Info] [10759] HTTPCache key=http://<IP_ADDRESS>/catalog/view/javascript/font-awesome/fonts/fontawesome-webfont.svg?v=4.4.0#fontawesomeregular fragment=<IP_ADDRESS>: remembering recent failure for 299 seconds.
[Thu, 09 May 2019 17:35:05 GMT] [Info] [10759] HTTPCache key=http://<IP_ADDRESS>/catalog/view/theme/journal2/css/icons/fonts/journal-icons.eot?#iefix fragment=<IP_ADDRESS>: remembering recent failure for 299 seconds.
[Thu, 09 May 2019 17:35:05 GMT] [Info] [10759] HTTPCache key=http://<IP_ADDRESS>/catalog/view/theme/journal2/css/icons/fonts/journal-icons.svg#journal-icons fragment=<IP_ADDRESS>: remembering recent failure for 299 seconds.
[Thu, 09 May 2019 17:35:05 GMT] [Info] [10759] HTTPCache key=http://<IP_ADDRESS>/catalog/view/theme/journal2/lib/lightgallery/fonts/lg.eot?#iefixn1z373 fragment=<IP_ADDRESS>: remembering recent failure for 299 seconds.
[Thu, 09 May 2019 17:35:05 GMT] [Info] [10759] HTTPCache key=http://<IP_ADDRESS>/catalog/view/theme/journal2/lib/lightgallery/fonts/lg.svg?n1z373#lg fragment=<IP_ADDRESS>: remembering recent failure for 299 seconds.
[Thu, 09 May 2019 17:35:05 GMT] [Info] [10759] HTTPCache key=http://<IP_ADDRESS>/catalog/view/theme/journal2/lib/rs-plugin/font/revicons.eot?5510888#iefix fragment=<IP_ADDRESS>: remembering recent failure for 299 seconds.
[Thu, 09 May 2019 17:35:05 GMT] [Info] [10759] HTTPCache key=http://<IP_ADDRESS>/catalog/view/theme/journal2/lib/rs-plugin/font/revicons.svg?5510888#revicons fragment=<IP_ADDRESS>: remembering recent failure for 299 seconds.
[Thu, 09 May 2019 17:35:05 GMT] [Warning] [10774] CSS parsing error in http://<IP_ADDRESS>/journal-cache/_4a4cb49ef93ac16b2313bb452ac35f17.css
[Thu, 09 May 2019 17:35:05 GMT] [Info] [10774] HTTPCache key=http://<IP_ADDRESS>/catalog/view/javascript/bootstrap/fonts/glyphicons-halflings-regular.eot?#iefix fragment=<IP_ADDRESS>: remembering recent failure for 299 seconds.
[Thu, 09 May 2019 17:35:05 GMT] [Info] [10774] HTTPCache key=http://<IP_ADDRESS>/catalog/view/javascript/bootstrap/fonts/glyphicons-halflings-regular.svg#glyphicons_halflingsregular fragment=<IP_ADDRESS>: remembering recent failure for 299 seconds.
[Thu, 09 May 2019 17:35:05 GMT] [Info] [10774] HTTPCache key=http://<IP_ADDRESS>/catalog/view/javascript/font-awesome/fonts/fontawesome-webfont.eot?#iefix&v=4.4.0 fragment=<IP_ADDRESS>: remembering recent failure for 299 seconds.
[Thu, 09 May 2019 17:35:05 GMT] [Info] [10774] HTTPCache key=http://<IP_ADDRESS>/catalog/view/javascript/font-awesome/fonts/fontawesome-webfont.svg?v=4.4.0#fontawesomeregular fragment=<IP_ADDRESS>: remembering recent failure for 299 seconds.
[Thu, 09 May 2019 17:35:05 GMT] [Info] [10774] HTTPCache key=http://<IP_ADDRESS>/catalog/view/theme/journal2/css/icons/fonts/journal-icons.eot?#iefix fragment=<IP_ADDRESS>: remembering recent failure for 299 seconds.
[Thu, 09 May 2019 17:35:05 GMT] [Info] [10774] HTTPCache key=http://<IP_ADDRESS>/catalog/view/theme/journal2/css/icons/fonts/journal-icons.svg#journal-icons fragment=<IP_ADDRESS>: remembering recent failure for 299 seconds.
[Thu, 09 May 2019 17:35:05 GMT] [Info] [10774] HTTPCache key=http://<IP_ADDRESS>/catalog/view/theme/journal2/lib/lightgallery/fonts/lg.eot?#iefixn1z373 fragment=<IP_ADDRESS>: remembering recent failure for 299 seconds.
[Thu, 09 May 2019 17:35:05 GMT] [Info] [10774] HTTPCache key=http://<IP_ADDRESS>/catalog/view/theme/journal2/lib/lightgallery/fonts/lg.svg?n1z373#lg fragment=<IP_ADDRESS>: remembering recent failure for 299 seconds.
[Thu, 09 May 2019 17:35:05 GMT] [Info] [10774] HTTPCache key=http://<IP_ADDRESS>/catalog/view/theme/journal2/lib/rs-plugin/font/revicons.eot?5510888#iefix fragment=<IP_ADDRESS>: remembering recent failure for 299 seconds.
[Thu, 09 May 2019 17:35:05 GMT] [Info] [10774] HTTPCache key=http://<IP_ADDRESS>/catalog/view/theme/journal2/lib/rs-plugin/font/revicons.svg?5510888#revicons fragment=<IP_ADDRESS>: remembering recent failure for 299 seconds.
[Thu, 09 May 2019 17:35:05 GMT] [Warning] [5785] CSS parsing error in http://<IP_ADDRESS>/journal-cache/_4a4cb49ef93ac16b2313bb452ac35f17.css
[Thu, 09 May 2019 17:35:05 GMT] [Info] [5785] HTTPCache key=http://<IP_ADDRESS>/catalog/view/javascript/bootstrap/fonts/glyphicons-halflings-regular.eot?#iefix fragment=<IP_ADDRESS>: remembering recent failure for 299 seconds.
[Thu, 09 May 2019 17:35:05 GMT] [Info] [5785] HTTPCache key=http://<IP_ADDRESS>/catalog/view/javascript/bootstrap/fonts/glyphicons-halflings-regular.svg#glyphicons_halflingsregular fragment=<IP_ADDRESS>: remembering recent failure for 299 seconds.
[Thu, 09 May 2019 17:35:05 GMT] [Info] [5785] HTTPCache key=http://<IP_ADDRESS>/catalog/view/javascript/font-awesome/fonts/fontawesome-webfont.eot?#iefix&v=4.4.0 fragment=<IP_ADDRESS>: remembering recent failure for 299 seconds.
[Thu, 09 May 2019 17:35:05 GMT] [Info] [5785] HTTPCache key=http://<IP_ADDRESS>/catalog/view/javascript/font-awesome/fonts/fontawesome-webfont.svg?v=4.4.0#fontawesomeregular fragment=<IP_ADDRESS>: remembering recent failure for 299 seconds.
[Thu, 09 May 2019 17:35:05 GMT] [Info] [5785] HTTPCache key=http://<IP_ADDRESS>/catalog/view/theme/journal2/css/icons/fonts/journal-icons.eot?#iefix fragment=<IP_ADDRESS>: remembering recent failure for 299 seconds.
[Thu, 09 May 2019 17:35:05 GMT] [Info] [5785] HTTPCache key=http://<IP_ADDRESS>/catalog/view/theme/journal2/css/icons/fonts/journal-icons.svg#journal-icons fragment=<IP_ADDRESS>: remembering recent failure for 299 seconds.
[Thu, 09 May 2019 17:35:05 GMT] [Info] [5785] HTTPCache key=http://<IP_ADDRESS>/catalog/view/theme/journal2/lib/lightgallery/fonts/lg.eot?#iefixn1z373 fragment=<IP_ADDRESS>: remembering recent failure for 299 seconds.
[Thu, 09 May 2019 17:35:05 GMT] [Info] [5785] HTTPCache key=http://<IP_ADDRESS>/catalog/view/theme/journal2/lib/lightgallery/fonts/lg.svg?n1z373#lg fragment=<IP_ADDRESS>: remembering recent failure for 299 seconds.
[Thu, 09 May 2019 17:35:05 GMT] [Info] [5785] HTTPCache key=http://<IP_ADDRESS>/catalog/view/theme/journal2/lib/rs-plugin/font/revicons.eot?5510888#iefix fragment=<IP_ADDRESS>: remembering recent failure for 299 seconds.
[Thu, 09 May 2019 17:35:05 GMT] [Info] [5785] HTTPCache key=http://<IP_ADDRESS>/catalog/view/theme/journal2/lib/rs-plugin/font/revicons.svg?5510888#revicons fragment=<IP_ADDRESS>: remembering recent failure for 299 seconds.
[Thu, 09 May 2019 17:35:06 GMT] [Info] [11038] Reusing shared memory for path: /var/cache/mod_pagespeed/ purge .
[Thu, 09 May 2019 17:35:07 GMT] [Info] [11039] Reusing shared memory for path: /var/cache/mod_pagespeed/ purge .
[Thu, 09 May 2019 17:35:07 GMT] [Info] [11040] Reusing shared memory for path: /var/cache/mod_pagespeed/ purge .
[Thu, 09 May 2019 17:35:08 GMT] [Info] [11043] Reusing shared memory for path: /var/cache/mod_pagespeed/ purge .
[Thu, 09 May 2019 17:35:08 GMT] [Info] [11045] Reusing shared memory for path: /var/cache/mod_pagespeed/ purge .
[Thu, 09 May 2019 17:35:08 GMT] [Info] [11044] Reusing shared memory for path: /var/cache/mod_pagespeed/ purge .
[Thu, 09 May 2019 17:35:08 GMT] [Info] [11046] Reusing shared memory for path: /var/cache/mod_pagespeed/ purge .
[Thu, 09 May 2019 17:35:09 GMT] [Info] [11048] Reusing shared memory for path: /var/cache/mod_pagespeed/ purge .
[Thu, 09 May 2019 17:35:09 GMT] [Info] [11047] Reusing shared memory for path: /var/cache/mod_pagespeed/ purge .
[Thu, 09 May 2019 17:35:09 GMT] [Info] [11054] Reusing shared memory for path: /var/cache/mod_pagespeed/ purge .
[Thu, 09 May 2019 17:35:09 GMT] [Info] [11050] Reusing shared memory for path: /var/cache/mod_pagespeed/ purge .
[Thu, 09 May 2019 17:35:09 GMT] [Info] [11053] Reusing shared memory for path: /var/cache/mod_pagespeed/ purge .
[Thu, 09 May 2019 17:35:09 GMT] [Info] [11051] Reusing shared memory for path: /var/cache/mod_pagespeed/ purge .
[Thu, 09 May 2019 17:35:09 GMT] [Info] [11052] Reusing shared memory for path: /var/cache/mod_pagespeed/ purge .
[Thu, 09 May 2019 17:35:09 GMT] [Info] [11049] Reusing shared memory for path: /var/cache/mod_pagespeed/ purge .
[Thu, 09 May 2019 17:35:12 GMT] [Warning] [10902] CSS parsing error in http://<IP_ADDRESS>/journal-cache/_4a4cb49ef93ac16b2313bb452ac35f17.css
[Thu, 09 May 2019 17:35:12 GMT] [Info] [10902] HTTPCache key=http://<IP_ADDRESS>/catalog/view/javascript/bootstrap/fonts/glyphicons-halflings-regular.eot?#iefix fragment=<IP_ADDRESS>: remembering recent failure for 292 seconds.
[Thu, 09 May 2019 17:35:12 GMT] [Info] [10902] HTTPCache key=http://<IP_ADDRESS>/catalog/view/javascript/bootstrap/fonts/glyphicons-halflings-regular.svg#glyphicons_halflingsregular fragment=<IP_ADDRESS>: remembering recent failure for 292 seconds.
[Thu, 09 May 2019 17:35:12 GMT] [Info] [10902] HTTPCache key=http://<IP_ADDRESS>/catalog/view/javascript/font-awesome/fonts/fontawesome-webfont.eot?#iefix&v=4.4.0 fragment=<IP_ADDRESS>: remembering recent failure for 292 seconds.
[Thu, 09 May 2019 17:35:12 GMT] [Info] [10902] HTTPCache key=http://<IP_ADDRESS>/catalog/view/javascript/font-awesome/fonts/fontawesome-webfont.svg?v=4.4.0#fontawesomeregular fragment=<IP_ADDRESS>: remembering recent failure for 292 seconds.
[Thu, 09 May 2019 17:35:12 GMT] [Info] [10902] HTTPCache key=http://<IP_ADDRESS>/catalog/view/theme/journal2/css/icons/fonts/journal-icons.eot?#iefix fragment=<IP_ADDRESS>: remembering recent failure for 292 seconds.
[Thu, 09 May 2019 17:35:12 GMT] [Info] [10902] HTTPCache key=http://<IP_ADDRESS>/catalog/view/theme/journal2/css/icons/fonts/journal-icons.svg#journal-icons fragment=<IP_ADDRESS>: remembering recent failure for 292 seconds.
[Thu, 09 May 2019 17:35:12 GMT] [Info] [10902] HTTPCache key=http://<IP_ADDRESS>/catalog/view/theme/journal2/lib/lightgallery/fonts/lg.eot?#iefixn1z373 fragment=<IP_ADDRESS>: remembering recent failure for 292 seconds.
[Thu, 09 May 2019 17:35:12 GMT] [Info] [10902] HTTPCache key=http://<IP_ADDRESS>/catalog/view/theme/journal2/lib/lightgallery/fonts/lg.svg?n1z373#lg fragment=<IP_ADDRESS>: remembering recent failure for 292 seconds.
[Thu, 09 May 2019 17:35:12 GMT] [Info] [10902] HTTPCache key=http://<IP_ADDRESS>/catalog/view/theme/journal2/lib/rs-plugin/font/revicons.eot?5510888#iefix fragment=<IP_ADDRESS>: remembering recent failure for 292 seconds.
[Thu, 09 May 2019 17:35:12 GMT] [Info] [10902] HTTPCache key=http://<IP_ADDRESS>/catalog/view/theme/journal2/lib/rs-plugin/font/revicons.svg?5510888#revicons fragment=<IP_ADDRESS>: remembering recent failure for 292 seconds.
[Thu, 09 May 2019 17:35:13 GMT] [Info] [11053] Shutting down PageSpeed child
[Thu, 09 May 2019 17:35:14 GMT] [Info] [11054] Shutting down PageSpeed child
[Thu, 09 May 2019 17:35:15 GMT] [Info] [11049] Shutting down PageSpeed child
[Thu, 09 May 2019 17:35:16 GMT] [Info] [11050] Shutting down PageSpeed child
[Thu, 09 May 2019 17:35:17 GMT] [Info] [11051] Shutting down PageSpeed child
[Thu, 09 May 2019 17:35:18 GMT] [Info] [11052] Shutting down PageSpeed child
[Thu, 09 May 2019 17:35:19 GMT] [Info] [11046] Shutting down PageSpeed child
[Thu, 09 May 2019 17:35:20 GMT] [Info] [11040] Shutting down PageSpeed child
[Thu, 09 May 2019 17:35:21 GMT] [Info] [11043] Shutting down PageSpeed child
[Thu, 09 May 2019 17:35:22 GMT] [Info] [11044] Shutting down PageSpeed child
[Thu, 09 May 2019 17:35:23 GMT] [Info] [11045] Shutting down PageSpeed child
[Thu, 09 May 2019 17:35:24 GMT] [Info] [11039] Shutting down PageSpeed child
[Thu, 09 May 2019 17:35:25 GMT] [Info] [10899] Shutting down PageSpeed child
[Thu, 09 May 2019 17:35:26 GMT] [Info] [11048] Shutting down PageSpeed child
[Thu, 09 May 2019 17:35:27 GMT] [Info] [5777] Shutting down PageSpeed child

After the 3rd analysis by https://developers.google.com/speed/pagespeed/insights the rating stays around the same high levels.
Can someone explain to me why this is and how to overcome this?

See https://www.modpagespeed.com/doc/faq#varying-results

Thanks for replying: I have read that page when setting things up.
My test site is http://<IP_ADDRESS>/ (no domain, no SSL, no traffic)
This is why I chose to my setup as follows:
ModPagespeed on
AddOutputFilterByType MOD_PAGESPEED_OUTPUT_FILTER text/html
ModPagespeedFileCachePath            "/var/cache/mod_pagespeed/"
ModPagespeedLogDir "/var/log/pagespeed"
ModPagespeedSslCertDirectory "/etc/ssl/certs"
ModPagespeedStatisticsLogging on
ModPagespeedEnableCachePurge on
ModPagespeedPurgeMethod PURGE
ModPagespeedFileCacheSizeKb 2048000
ModPagespeedFileCacheCleanIntervalMs 3600000
ModPagespeedFileCacheInodeLimit 500000
ModPagespeedDefaultSharedMemoryCacheKB 50000
ModPagespeedImageMaxRewritesAtOnce -1
ModPagespeedLoadFromFileCacheTtlMs<PHONE_NUMBER>0
ModPagespeedLoadFromFileMatch "^https?://<IP_ADDRESS>/" "/home/hallonpower/public_html/"
ModPagespeedLoadFromFileRuleMatch disallow .*
ModPagespeedLoadFromFileRuleMatch allow .css$
ModPagespeedLoadFromFileRuleMatch allow .jpe?g$
ModPagespeedLoadFromFileRuleMatch allow .png$
ModPagespeedLoadFromFileRuleMatch allow .gif$
ModPagespeedLoadFromFileRuleMatch allow .js$
ModPagespeedLoadFromFileRuleMatch allow .svg$
ModPagespeedDisallow "/admin/"
ModPagespeedFetchHttps enable

ModPagespeedRewriteLevel CoreFilters
ModPagespeedEnableFilters remove_comments,collapse_whitespace,elide_attributes,trim_urls
ModPagespeedDomain http://fonts.googleapis.com
ModPagespeedGoogleFontCssInlineMaxBytes 20000
ModPagespeedEnableFilters inline_google_font_css
ModPagespeedEnableFilters lazyload_images
ModPagespeedEnableFilters responsive_images
ModPagespeedEnableFilters responsive_images_zoom
ModPagespeedEnableFilters insert_image_dimensions
https://www.modpagespeed.com/doc/faq#varying-results states:
There are two (relatively) common situations that may lead up to a fluctuating level of optimization in the output:
1.
Low traffic (TRUE FOR THIS TEST SITE - test was without traffic for 2 hours)
short http expiry times for image, css and javascript (increase the http expiry or set up LoadFromFile)
ModPagespeedFileCacheCleanIntervalMs 3600000
ModPagespeedLoadFromFileMatch "^https?://<IP_ADDRESS>/" "/home/hallonpower/public_html/"
ModPagespeedLoadFromFileCacheTtlMs<PHONE_NUMBER>0

High cache churn rates:
caches are sized too small, (Size the cache to 3 to 4 times the size of the original assets)
ModPagespeedFileCacheSizeKb 2048000
ModPagespeedFileCacheInodeLimit 500000
ModPagespeedDefaultSharedMemoryCacheKB 50000

If the above did not help, the admin pages offer various tools that may assist in diagnosing what happens.

Question:

ModPagespeedFileCacheCleanIntervalMs 3600000 = 1 hour
If I increase this to 86400000 (24 hours) this should stop early expiry?

ModPagespeedDefaultSharedMemoryCacheKB 50000
How do I know if this is enough or not?

Anything else you see that I may be doing wrong? Been playing with pagespeed for only a week.

Well, referencing resources in css that respond with 404 can cause unsteady results (because pagespeed will remember that 404 for 5 minutes and then try again).
And then there's beacon expiry as well:
https://www.modpagespeed.com/doc/config_filters.html#FinderPropertiesCacheExpirationTimeMs
Bumping the file cache clean interval may mask an undersized cache; is would be better to size it properly I think. Ideally, ballpark it should be able to hold 3-4X the sum of the size of the original resources.
Otto

Thanks for the tips.
ModPagespeedFileCacheSizeKb 2048000 is 3-4 times my assets.
ModPagespeedLoadFromFileCacheTtlMs<PHONE_NUMBER>0 I see this number on most assets in console
But for this? Do you think this may be small?  ModPagespeedDefaultSharedMemoryCacheKB 50000
Isn't it strange that in my first post in all message sections, there is no place  where pagespeed mentions that some particular asset  has expired?

For checking general module (and cache) health, it's may be helpful to set up the admin pages:
https://www.modpagespeed.com/doc/admin
The logs won't warn about beacon expiry. There are other warnings in there though for the combiners.
It looks like enabling rewriting of introspective javascript is worth giving a shot, as well as fallback rewriting css that can't be parsed.

I will try that thanks.
But for this? Do you think this may be small? ModPagespeedDefaultSharedMemoryCacheKB 50000


Create .Buf/.Blob coercers on Cool

This would create a Buf/Blob of the Int of the given value, for the correct size, big endian.

OK, but which problem is this going to resolve?

What @AlexDaniel said: we should start with the problem. I speculate the problem is:

It's tiresome to write my Buf $x .= new; $x.write-int32(42); to get a Buf containing the encoding of that integer value
There's no ideal way to get a Blob rather than a Buf if wanting to have it as an immutable value

Those are probably fair problems, thought the solution proposed here doesn't seem ideal to me, since:

Things like Str are also Cool, and having that be numified in response to .Buf or .Blob feels a bit odd. Folks would quite possibly expect it to do something like .encode does.
There is no "correct size" for the integer 1. Depending on the needs of the binary format being produced, it could be represented in 1 byte, 2 bytes, 4 bytes, or 8 bytes.

I'd be more in favor of factory methods on Blob/Buf, so you could do Blob.from-int32(-1) and it'd produce a 4-byte Blob holding the representation of -1; endianness can optionally be provided as it is in write-int32.

That'd work for me too  :-)

While you're at it, how about taking an array (Iterable) as input as well?

@CurtTilmes Perhaps, but we have to be a bit careful, in that arrays in numeric contexts typically numify. It'd not be unreasonable for somebody to write my $chunk-count = Blob.from-int32(@chunks) and expect to have a Blob with the number of elements in the array encoded. It's a natural generalization for anyone happily doing if @stuff == 1 { } and similar.
Maybe a plural version of the methods: Blob.from-int32s(@values)?

Sounds good.  I like this because it makes a few things easier.
Native types, shaped arrays, Blob-ifying numbers, etc. are on their way to competing with NumPy and PDL, but I still don't understand how it all fits together.


Adding new device manually

Feature request:
I would like to add my espHome devices manually by IP or by mDNS name.
Currently I saw that users can add a new device only if it found the device on the network.

when you click "pencil" you can add manual host

Thanks, I didn't see that as the Node-RED phone ui is not the best.


Bump the terraform version in the all-in-one image

Please bump the TF version to https://github.com/ppc64le-cloud/test-infra/blob/master/images/all-in-one/Dockerfile#L7
TF version can be bumped to the latest release

/kind feature
/assign @RagniGarg97

fix: https://github.com/ppc64le-cloud/test-infra/pull/172

/assign @Rajalakshmi-Girish

This is already fixed.


PCAP Compressions

[ ] Design file format (probably 64k blocks that are compressed)
[ ] Figure out how to encode? we have file, block position in file, packet position in uncompress/unencrypted block
[ ] Change viewer support reader plugins
[ ] Code writer
[ ] Code reader

i remember somebody laughing at me when i suggested this

It used to be part of #484 but I moved out since I finished encryption.
We can probably save 10-20%, although a better way to save space is just to drop tls traffic after so many packets.  https://github.com/aol/moloch/wiki/RulesFormat

My thoughts on this were as follows:

A compressed pcap file contains:
A gzip header
A number of individually compressed deflate blocks not exceeding 64k bytes in size (or 1MB of uncompressed PCAP data -- whichever comes first

A packetPos is then (offsetOfBlockStart << 20) + (offsetOfPacketStartInUncompressedData)
If this value is kept to the range  0 .. 2^53 - 1, then it can be exactly represented in Javascript. This gives a max compressed file size of around 8GB (2^33 bytes).
The raw compressed file can be decompressed by gzip for other tools to analyze and can also be read by seeking to a block start and then inflating 64k of data.


"editor.gotoLocation.many": "reveal"`: reveals second entry

Testing #71087
Version: 1.33.0-insider
Commit: b9bcca2b9830df592892d63201704026c18dcbe5
Date: 2019-03-26T08:08:33.302Z
Electron: 3.1.6
Chrome: 66.0.3359.181
Node.js: 10.2.0
V8: 6.6.346.32
OS: Linux x64 4.15.0-45-generic
The description of  "editor.gotoLocation.many": "reveal" says that this would reveal the first entry. It looks like it is the second.

set "editor.gotoLocation.many": "peek"

in the vscode repo, open workbenchThemeService.ts, set cursor at line 95, IExtensionService.

Use Goto Definition from context menu
export const IExtensionService = createDecorator<IExtensionService>('extensionService'); is first entry

set "editor.gotoLocation.many": "reveal"

Use Goto Definition from context menu

reveals export interface IExtensionService

Well, export const IExtensionService = createDecorator<IExtensionService>('extensionService'); is the first entry but not the selected one... The logic is that the 'nearest' definition is selected and that's what we pick when reveal is used.
However, the nearest-logic seems flawed when changing files and there were also discussions about not doing this when having definitions that we should just use the provider sorting...

Behaviour is fine for me. Just fix the description to e.g.  'Reveal the primary result and ignore others


chore(deps): bump https://github.com/jenkins-x/jx-cli to 3.0.314

Update jenkins-x/jx-cli to 3.0.314
Command run was ./promote/main

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To complete the pull request process, please assign jstrachan
You can assign the PR to them by writing /assign @jstrachan in a comment when ready.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@jenkins-x-bot-test: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

gke
e96c9989533fa2ed1a9b291da61e4af862ab865e
link
/test gke

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


Brevented apps still running and showing notifications.

I Brevented Lazada app but still, it still running and show notifications. I even set it on aggressive mode.

There are some roms (mainly in china), allow apps to notify without running, and show the icon of the apps instead of notify app.


Added new three detection events

Add WindowsThreat event for windows sysmon events.
Add NetworkThreat event for network events.
Add ExtraThreat event for misc events.

The EventKind enum has been modified to add new variants and remove some existing ones. This breaks the compatibility with the previous versions of the library, so we need to increment the minor version number according to the semantic versioning rules.
The EventMessage struct, which contains an EventKind field, is serialized and stored in the database. To avoid data loss and corruption, we need to implement a migration function that will update the existing records in the database to match the new EventKind definition.
Please also kindly include the reason why Log is removed and replaced with ExtraThreat for record keeping.

@minshao
1.I will fix this.


ionicAnimation removed?

in beta 11, ionicAnimation removed from ionic.bundle.js?

@mhartington Its been over a year. Any updates on this?

2years pasted.Still nothing new updated.

What about this? Collide.io is in offline.


Adjusts on steps and fix this issue #1472

When locastyle.steps.init run twice, it add the class ls-active and ls-actived.

:+1: