METRON-941 fix PaloAltoParser

Contributor Comments
Fixed comma related issue by using Guava Splitter instead of split (reproduce: send log message with comma in payload, such as url or user-agent)
introduced consistent field naming according to https://www.paloaltonetworks.com/documentation/70/pan-os/pan-os/monitoring/syslog-field-descriptions
introduced v7.0 log format support
adding missing fields (that even existed prior to 7.0)
This is build and run tested with real-life logs.
Pull Request Checklist
Thank you for submitting a contribution to Apache Metron.
Please refer to our Development Guidelines for the complete guide to follow for contributions.
Please refer also to our Build Verification Guidelines for complete smoke testing guides.
In order to streamline the review of the contribution we ask you follow these guidelines and ask you to double check the following:
For all changes:

[x] Is there a JIRA ticket associated with this PR? If not one needs to be created at Metron Jira.
[x] Does your PR title start with METRON-XXXX where XXXX is the JIRA number you are trying to resolve? Pay particular attention to the hyphen "-" character.
[x] Has your PR been rebased against the latest commit within the target branch (typically master)?

For code changes:

[x] Have you included steps to reproduce the behavior or problem that is being changed or addressed?

[ ] Have you included steps or a guide to how the change may be verified and tested manually?

[ ] Have you ensured that the full suite of tests and checks have been executed in the root incubating-metron folder via:
mvn -q clean integration-test install && build_utils/verify_licenses.sh

[ ] Have you written or updated unit tests and or integration tests to verify your changes?

[ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?

[x] Have you verified the basic functionality of the build by building and running locally with Vagrant full-dev environment or the equivalent?

For documentation related changes:

[ ] Have you ensured that format looks appropriate for the output in which it is rendered by building and verifying the site-book? If not then run the following commands and the verify changes via site-book/target/site/index.html:
cd site-book
mvn site

Note:
Please ensure that once the PR is submitted, you check travis-ci for build issues and submit an update to your PR as soon as possible.
It is also recommended that travis-ci is set up for your personal repository such that your branches are built there before submitting a pull request.

A number of the field name changes seem to depart from Metron conventions. Is there a reason to change these from matching the metron ip_src_addr style pattern?

Do you have any examples? The previous concept was to use arbitrary (at least I couldn't find any reference) field names (i.e. source_address or destination_address) and then further down these were renamed to "standard" Metron style (i.e. outputMessage.put("ip_src_addr", outputMessage.remove("source_address"));). I started to use the "official" field names (as per vendor documentation), but I still rename the defined field names to Metron style... did I miss any?

Yes, that makes sense, but does have some performance implications of course. A single mapping would have much faster response, so I would question the original approach (on which you are quite correct). I'm sure others will chime in if there are benefits to the re-write the name approach that I'm missing. Right now we only formally define a small number of the fields - ip_(src|dest)_(addr|port) etc to have the metron format, but I would argue things like nat_source_addr in this parser should follow the spirit of the convention.

I agree to both of your points, defining it with the final name from the beginning would be more efficient and we should come up with a more normalized and standardized field naming convention in general.
However, the second part is something for all parsers, not just this one, so it's a little bit out of scope for this PR. In fact, this PR doesn't change the concept of the previous code, it just makes the "intermediate" field names more consistent by following the vendor documentation.
My suggestion would be to either merge this PR as-is or with one-time-definition of already defined Metron field names. To follow-up on the other topic we create a new Jira to define a normalized message format for all parsers (and enrichments), with subtasks to adapt each of the parsers (including this one).

I updated the mapping to use the Metron name right away and added some more handling for different versions of the log format. Any other feedback?

Thanks for the contribution! Would you mind having a look at the unit tests for this parser and updating them?
From a quick glance, the unit test appears to be defunct. It's using AbstractConfigTest to read in test data from a file that doesn't exist anyone.

@ctramnitz says (in email): "I didn’t touch unit tests because it was already broken before.
We agreed to put this into a separate ticket (METRON-962) as it applies to other parsers as well.
For now, METRON-941 fixes an actual bug (parsing is broken with the current code)."
@ottobackwards and @justinleet (principles on METRON-962), do you agree we should go ahead and commit this without a viable PaloAltoParser unit test?  Or wait for METRON-962?
@kylerichardson , what is your opinion on the issue?
Thanks.

Also, @ctramnitz , could you please describe in more detail the manual testing you did, which might make us feel better about a commit without unit test?  Thanks.

I'm running this myself and actively parsing PaloAlto logs with this change for about 3 weeks. You can also see that the changes are fairly trivial and that structure and naming follows the vendors specifications.
I understand your concerns about the missing unit tests, but, as mentioned before, unit testing was completely non functional before, I didn't even remotely touch it. You basically have the choice of not merging this, resulting in having no unit test and a broken parser, or merging it with still no unit test but having a working parser. As I already discussed for METRON-962 I can provide sample logs for unit testing.

Given these unit tests have been broken for quite some time and @ctramnitz has thoroughly tested in his environment and that this is a relatively minor change, I'm okay to move it forward especially with a JIRA in to address these broken 'AbstractConfigTest' tests holistically in METRON-962.
+1 from me but would prefer a second to commit without tests.
@ctramnitz as discussed please upload public safe sample logs to the JIRA to assist with test development.
-Kyle

On Jun 5, 2017, at 5:40 PM, Matt Foley<EMAIL_ADDRESS>wrote:
@ctramnitz says (in email): "I didn’t touch unit tests because it was already broken before.
We agreed to put this into a separate ticket (METRON-962) as it applies to other parsers as well.
For now, METRON-941 fixes an actual bug (parsing is broken with the current code)."
@ottobackwards and @justinleet (principles on METRON-962), do you agree we should go ahead and commit this without a viable PaloAltoParser unit test? Or wait for METRON-962?
@kylerichardson , what is your opinion on the issue?
Thanks.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

I just kicked up https://github.com/apache/metron/pull/612, which theoretically fixes the unit tests (and simplifies them a lot).  Straight replacing the logs would work, but we might want versioned tests (which could either be done here, or as a follow on).
A proper review obviously has to be done there (and I still owe a bit on it myself), but if reasonably possible I'd prefer to get that done to enable unit testing here.

@ctramnitz Can you merge/rebase master into this PR? I'd like to make a PR against your branch, but it depends on METRON-962 being in.  Basically I just pulled out the log files it loaded, and made it actually check the JSON field-by field (instead of just checking if results are not null) for the two test logs we already had (Traffic and threat on 60).
At that point, you should have a pretty good basis for adding unit tests with the logs that you have.

Actually, I'll just open a separate ticket/PR.  You'll still want to merge it in.

I lied, it's a bit circular.  It depends on your PR's fixes, so let's go back to the original strategy of making a PR against your branch.  I'm more than happy to give up credit, since this is just moving where the test data lives and actually checking against it.

https://github.com/ctramnitz/metron/pull/1 opened, if anyone cares.  As noted, https://github.com/ctramnitz/metron/commit/bf8ce62cb5ed3846f288e4a7a606410ebbaf9d30 is the relevant commit.

First, a note to @ctramnitz : Christian, please be patient with the long cycle on this.  It is not a reflection on your work, but rather a desire to make sure that work gets appropriate consideration.  Your work is very much appreciated.  We really do have a very strong bias in Apache toward test-driven development, and so we tend to ask that new work provide unit tests, even if those tests were lamentably lacking before the new work :-)
Anyway, thanks to fast work by @justinleet , METRON-962 is now in, and the PaloAlto parser can be unit tested.  Please rebase so it can be done.  Since the one file you changed has not been touched by recent commits, the rebase should be painless.  If you're not familiar with git rebase, ping me offline.
If my understanding of Justin's PR is correct, you can then just layer on his bf8ce62 patch, and have a good start on testability.  @justinleet is that correct?  Was it your intent that this patch will fully provide the unit testing capability, or is it just the start?  Thanks.

Just the start.  I got the previously existing test cases in a better shape, and @ctramnitz should be able to add on pretty easily.
I do want to echo what @mattf-horton said about the quality of work and the length of the cycle. We definitely appreciate getting fixes like this, and I wanted to make sure we got tests in, not just for the quality of your work, but so that we avoid regressions in the future.

@ctramnitz Any update?  I know you brought it up on the release discussion thread awhile ago, since it is good stuff.  I'm happy to help out any way I can on getting testing up and running for this.

Hi we would like to get this into the next release.  @ctramnitz we'll be happy to help you fix it

@ctramnitz is there any update on this PR?  Is there something we can do to help?

Rebasing to master to see where we are. If this comes back clean please don't merge yet, I want to add 8.0 log format first.

@ctramnitz thank you!  Let us know where you are at and if we can help

I think https://github.com/apache/metron/pull/579/commits/ccd99dda3c8a72408ae13eeaca078af1e345a36c#diff-e0385f97ebea64bab3a83bceef70bb4aR67
expected.put(BasicPaloAltoFirewallParser.PaloAltoDomain, "<11>Jan  5 05:38:59 PAN1.exampleCustomer.com 1");
should be
expected.put(BasicPaloAltoFirewallParser.PaloAltoDomain, "1");
The rest is the syslog header, not the PA domain.
I'd suggest to strip the syslog header off the test data and assume it will also be stripped off on ingestion until we have a syslog-preparsing capability (i.e. https://issues.apache.org/jira/browse/METRON-1453).
I'm already doing this using rsyslog:
module(load="imudp")
module(load="omkafka")

template(name="msgonly" type="string"
         string="%msg:::drop-last-lf%"
        )

ruleset(name="udp514"){
  if (<some-condition>) then {
    action(
      broker=["<kafka_host>:6667"]
      confparam=["client.id=rsyslog", "compression.codec=snappy", "socket.keepalive.enable=true"]
      type="omkafka"
      topic="paloalto"
      template="msgonly"
      errorfile="/var/log/rsyslog_kafka_failures.log"
    )
  }
}
input(type="imudp" port="514" ruleset="udp514")

from @ctramnitz on the PR I made against his branch.

However, I'm not sure the result for is really as expected.
It shouldn't be "<11>Jan 5 05:38:59 PAN1.exampleCustomer.com 1", but just "1". The rest is the Syslog header.
Is the PaloParser called against the entire syslog line or after the header has been stripped out?

Keeping in mind, that I'm definitely not an expert on this, here's what I've dug up.  If anybody has more expertise / insight, I'd be happy for the contribution.
Looking over it, the full log line. Check out metron-platform/metron-integration-test/src/main/sample/data/SampleInput/PaloaltoOutput
Looking at https://www.paloaltonetworks.com/content/dam/pan/en_US/assets/pdf/framemaker/60/pan-os/pan-os.pdf for the 6.0 fields, they are
FUTURE_USE
Receive Time
Serial Number
Type
Subtype
FUTURE_USE
Generated Time
Source IP
Destination IP
NAT Source IP
NAT Destination IP
Rule Name
Source User
Destination User
Application
Virtual System
Source Zone
Destination Zone
Ingress Interface
Egress Interface
LogForwarding Profile
FUTURE_USE
Session ID
Repeat Count
Source Port
Destination Port
NAT SourcePort
NAT Destination Port
Flags
Protocol
Action
Miscellaneous
Threat ID
Category
Severity
Direction
Sequence Number
Action Flags
Source Location
Destination Location
FUTURE_USE
Content Type
PCAP_id*
Filedigest*
Cloud*

The field we pull out as palo_alto_domain appears to be a FUTURE_USE field.  There also doesn't appear to something that would obviously correspond to the PaloAltoDomain field (unless I can't read, which has happened before).
The field we call time_logged also appears to be FUTURE_USE. There's also another FUTURE_USE, but I think I misread something because it didn't line up like I expected (and the specifics aren't actually super important).
It makes me question how reliable anything labelled FUTURE_USE is (although that doesn't stop us from looking at it and labelling it).

For the syslog header vs message parser this future_use is not really important. This has other implications than just carrying arbitrary data in a field that is labeled to do something else.

8.0 log format is also working now
In the latest two commits I included the changed tests from @justinleet but changed the expected input from full syslog messages including syslog header into just the syslog message aka payload.
It is not safe to assume that the previously used syslog header (in old RFC3164 format) will be used by anyone. Until we have something generic to (pre-)parse syslog before it reaches the message parser I assumed the messages will be stripped off the syslog header for now.
This works nicely with the rsyslog config snippet above.
The PR should be ready for prime-time now. Please let me know if anything else needs to be changed.

Im +1 on this.  I would like to get comment from @simonellistonball et al on the change for syslog

Any further comments? The old parser was plain broken. So even if there is room for improvement here, I would really like to see this merged.
Thanks!

I'm +1, this is definitely a major improvement and I agree, getting it merged would be great. @simonellistonball Any comment as @ottobackwards asked, or are we good to pull this in?

I don't believe I have any further things to add. I'm +1 and keen to see this get in.

@ctramnitz one thing, since this is a regression, technically, we need to update the release notes / upgrade guide.
Can you add a note to the Upgrading.md about the removal of the Syslog -ness?

after that I'll merge

@ctramnitz Just noticed this, but could you change the name of the PR to match the Jira?
i.e.

METRON-941 native PaloAlto parser corrupts message when having a comma in the payload

@ottobackwards Where is the regression? If a user used the parser previously with a full syslog header it will continue to work the same way. The result will be the same odd domain field ", 1" instead of "1". The parser hasn't changed, only the test which expects just the message now. And since the test was non-functional before (it was never invoked), this cannot be regression either.
The only thing that has changed is some field names, but since this was utterly broken before, i.e.
BasicPaloAltoFirewallParser.java line 84++

-  public static final String Bytes = "content_type";
-  public static final String BytesSent = "content_type";
-  public static final String BytesReceived = "content_type";
-  public static final String Packets = "content_type";
-  public static final String StartTime = "content_type";
-  public static final String ElapsedTimeInSec = "content_type";
-  public static final String Padding = "content_type";

I wouldn't call this a regression, it may be worth a note though.

maybe regression isn't the right word  -
"Until we have something generic to (pre-)parse syslog before it reaches the message parser I assumed the messages will be stripped off the syslog header for now." is this not a new requirement or behavior?

No it's not a requirement. The parser will continue to work the same way as it did before if you feed it a full syslog line including header. (Which wouldn't produce a valid domain field, but thats exactly the same behavior as before)

+1 one.  Thank you @ctramnitz.  I know how it can be to have a long review process.  This is really good work and I look forward to seeing what you do next ;)

I'm still +1.  This is really great, and everyone definitely appreciates how much work went into improving this so much.


KHR_materials_transmission - Make roughness affect thin surface refraction again

Would be great to not use branch with if when the value comes out from texture ?

@sebavan Indeed. I realized that at lunch today. I'll change it when I get a chance to work on this again. There is at least one more thing I need to do.

Okay, so this is fixed now.
However, I’m wondering if we need the volume ior VS surface ior logic at all. We can just use the thickness check to see if the material is volumetric or not.
Originally, I think I separated the two IOR's so that we could have IOR affect the reflections and refractions independently but I don't think that's really necessary.
This might change existing scenes that use refraction with a thickness of 0 though?

I would prefer to avoid breaking changes but let s see what @Popov72 and @bghgary think ?

I told @MiiBond to check with you, haha. From a glTF perspective, there is no change.

I think this one can be merged?


Add Sreelakshmi393's file

First created a branch then created a file and made commit and finally opened a pull request

Done the process


[conf] Add annotations for documenting function worker configuration settings

Motivation
This change is adding annotations to function worker configuration for generating function worker configuration file.


Add test for string type time columns

Fix a bug in pmdarima/training.py
Add test for string type time column in training and inference for pmdarima and prophet.

Codecov Report

Merging #49 (62f5442) into main (7751d29) will not change coverage.
The diff coverage is 100.00%.

:exclamation: Current head 62f5442 differs from pull request most recent head 13eb2ea. Consider uploading reports for the commit 13eb2ea to get more accurate results

@@           Coverage Diff           @@
##             main      #49   +/-   ##
=======================================
  Coverage   99.48%   99.48%
=======================================
  Files          18       18
  Lines         584      584
=======================================
  Hits          581      581
  Misses          3        3

Flag
Coverage Δ

unittests
99.48% <100.00%> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

...ricks/automl_runtime/forecast/pmdarima/training.py
98.48% <100.00%> (ø)

Continue to review full report at Codecov.

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

By default, prophet is using pd. to_datetime  in prophet call: https://github.com/facebook/prophet/blob/b7d5ec448177b7ac2abf25cc3259cb55e4c44069/python/prophet/forecaster.py#L267

By default, prophet is using pd. to_datetime  in prophet call: https://github.com/facebook/prophet/blob/b7d5ec448177b7ac2abf25cc3259cb55e4c44069/python/prophet/forecaster.py#L267

Thanks for the pointer! I have the impression as well, but what I mean is we should guarantee this ourselves instead of relying on the implementation details of other projects. This could make the expected behavior against string column clearer as well as avoid breaking changes introduced by external project. wdyt?

Sure. Let me also add the type conversion in prophet function too to make sure we will have the same one for all models.


Fix missing characters in file name sanitizer

Fixes #15

looks good, thanks for catching & fixing that


Add more idaklu solver options (number 2)

Description
Adds more user-configurable options to the IDA solver following the list in the IDA guide.
Some code cleanup to enforce early returns.
Type of change
Please add a line in the relevant section of CHANGELOG.md to document the change (include PR #) - note reverse order of PR #s. If necessary, also add to the list of breaking changes.

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

Key checklist:

[x] No style issues: $ pre-commit run (or $ nox -s pre-commit) (see CONTRIBUTING.md for how to set this up to run automatically when committing locally, in just two lines of code)
[x] All tests pass: $ python run-tests.py --all (or $ nox -s tests)
[x] The documentation builds: $ python run-tests.py --doctest (or $ nox -s doctests)

You can run integration tests, unit tests, and doctests together at once, using $ python run-tests.py --quick (or $ nox -s quick).
Further checks:

[x] Code is commented, particularly in hard-to-understand areas
[x] Tests added that prove fix is effective or that feature works

Replacement for #4249, review was partially done there

I changed IDAKLUSolver's default rtol from 1e-6 to 1e-4. This is more closely in line with other ODE/DAE solvers, such as MATLAB and Julia's DifferentialEquations of 1e-3. I've found that 1e-4 is more appropriate for solving battery systems of equations.


[ENHANCEMENT] Finish All Communities-Related Things

[ ] Finish implementing the Community Bio's
[ ] Finish implementing the Request's tab (and make it functional)
[ ] Make Community slug the URL of the Community

UPDATE: Make it so that the owner(s) of the community can delete any thread posted as the community.

UPDATE:

[ ] Make a edit form for the Community


App uses non certified ad SDK

I used Sentry in an app that's designed for kids, and Google is telling me that Sentry is a non-certified ad SDK and has been constantly rejecting my app. Is there any plan in the future to make this SDK compliant? I don't even know this SDK has ads feature...

@hongfeiyang this SDK isn't an ad SDK, also, we don't run ads at all, we are a crash reporting and we'll be scaling this, thanks for reporting.

@hongfeiyang a quick update, our legal team is already in contact with Google trying to figure this out

@marandaneto I know this is not an ad SDK, I am just shocked by the fact that google treats this as an ad SDK. Thanks for the update, please reply in this thread once this is approved by Google. My Flutter app's future depends on this 🙏

I am also on the project with @hongfeiyang .. very frustrating; but it is hard to argue with the google play app review on behalf of Sentry.io; so I hope Sentry.io can self certify via this form:
https://support.google.com/googleplay/android-developer/?p=adnet
For the record, here is the email from Google Play Developer Support:
`
Status: App not available on Google Play
I’ve reviewed your appeal request and found that your app still violates Google Play Policy. I’ve included details below about the specific issue with your app and what you can do to get your app back on Google Play.
Step 1: Fix the policy violation with your app, XXX app (xxx.xxx.xxx)
We have detected that your app includes non-certified ad SDKs and/or SDKs that are not approved for use in child-directed services. Any SDKs used in the app must be appropriate for use in child-directed services. Additionally, apps that solely target children must not contain any SDKs that are not approved for use in child-directed services, including ads SDKs. Apps in the Designed for Families program must only use ad SDKs that have certified their compliance with the Families Ads Program[1].
We have detected the use of Sentry SDK, which is not allowed in apps that are in the Families program. An ad SDK is not allowed if it has not self-certified its compliance with Play’s Families Ads Program (certified ad SDKs), or it is non-COPPA compliant per its own public documentation. Please note, the status of SDKs often changes and it is your responsibility to review documentation of all SDKs used in your app to ensure compliance with Families policies.
Please update your app to fix this issue. Before resubmitting your app for further review, please make sure to DEACTIVATE the non-compliant APK and increment the version number of the APK. Kindly note that all active APK versions need to be compliant.
`
REF:
[1] https://support.google.com/googleplay/android-developer/answer/9283445

@derek-meeco as I said, we are already in contact with Google, unfortunately, we don't know what sort of trigger they have to detect this as an ad SDK.
We can't certify the SDK for a feature that we don't have, our SDKs are open-source, you are free to help us to figure out what's going on.

@marandaneto self certifying a none existent feature is the easiest thing ever; you answer "no" to everything :) - sometimes you just gotta work in the system ;)

Is there any news? I use "@sentry/react-native" in my app and got rejection too:

"We have detected the use of Sentry SDK, which is not allowed in apps that are in the Families program"

no afaik, @mitsuhiko is in contact with Google, he will update us once there's news from their side.

we have an update, Apps that have been rejected due to the Sentry SDK are now free to submit again, thanks for the patience.
We're going to work on docs to be more specific about PII on our SDKs

https://docs.sentry.io/product/security/mobile-privacy/


bluebird typings are still referenced

According to yarn the bluebird are still referenced.
yarn add sequelize-typescript
yarn add v1.22.4
[1/5] 🔍  Validating package.json...
[2/5] 🔍  Resolving packages...
[3/5] 🚚  Fetching packages...
[4/5] 🔗  Linking dependencies...
warning " ><EMAIL_ADDRESS>has unmet peer dependency "@types/bluebird@*".
[5/5] 🔨  Building fresh packages...
success Saved lockfile.
success Saved 1 new dependency.
info Direct dependencies
└─<EMAIL_ADDRESS>info All dependencies
└─<EMAIL_ADDRESS>
See here https://github.com/RobinBuschmann/sequelize-typescript/blob/master/package.json#L75

Hey @ShaharHD, this is because the latest sequelize version (Version 5.21.11) still requires bluebird.

But the warning regarding this comes only from sequelize-typescript.
latest version of sequelize (if it was new project, as with yarn install sequelize sequelize-typescript) will not install bluebird typings, or am I mistaken?


Account overview page - partials

Creates separate partial files to arrange the content of the three tabs:

my appointments
my beehive
my achievements

That's a great idea! No it's much easier to read :+1:


pandoc: apply patch removing the usage of polyfill.io in the templates

Description of changes
If you output HTML with MathJax content Pandoc might uses a JS library provided by cdn.polyfill.io which is now considered to be a bad actor.
https://sansec.io/research/polyfill-supply-chain-attack
Pandoc does not use this domain in recent versions but upgrading it seems more complex right now (and it will be done in the Haskell package set upgrade) especially if we consider backports to the stable releases.
To reproduce the issue:

Create a file math.text with the following content $a^2 + b^2 = c^2$
Call pandoc with pandoc math.text -s --mathjax -o ex.html
Look at the injected scripts in ex.html

Things done

Built on platform(s)

[x] x86_64-linux
[x] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
24.11 Release Notes (or backporting 23.11 and 24.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Thank you! Let’s merge this quickly!
Did actually build something with the patched pandoc and confirmed that mathjax still works?

Yes, I added a minimal repro in the description :)

I have validated that this fix works, thanks for the reproducer! Seeing that this is a security issue and that the patch is an already applied and released change from upstream this is a no brainer.
However this override belongs in configuration-common.nix instead of configuration-nix.nix and there is a handy appendPatch helper which can be used instead of overrideCabal.

I will quickly fix that myself.

Couldn’t force push to your branch so I opened a new PR.
Thank you for bringing this to attention!


Feature Request: Insufficient Resource message

Both dcos package install or dcos marathon app add make a request to POST /v2/apps.  If the app requests more resources than currently available on mesos, the POST still succeeds.  This might be expected if the user wants the app to deploy as soon as their are available offers, but often, the user wants to know immediately that their app will not deploy.
I propose we add an e.g. failFast option to POST /v2/apps that rejects the request if mesos doesn't have enough resources.  We can query state.json for the resource allocation data.
I realize there are resource race conditions, and that even sufficient available resources doesn't guarantee deployment, but the option will help us alert users as soon as possible that we know with high likelihood that their app will not deploy.

Hi @mgummelt, I do like the idea and I agree that this is user-friendly.
However, that's not how Marathon works and it would be very difficult to implement. Currently, Marathon does not keep information about current Mesos resources in its own state.
An alternative would be to block the POST call for a limited time and return status if starting failed. This would also require serious changes that will not happen any time soon.
I will keep thinking about it, maybe we can have a simple solution for that.

Did you read my proposal for using state.json.  That doesn't require saving state.

Yes. I think waiting for a limited time if the deployment succeeds is better:

it is easy to support constraints
maybe if I am wrong but reading the state.json will still require some sort of interpretation by us:

how likely is it that Mesos offers the required resources to us etc
we have to apply the resource matching algorithm to fragments from the state.json
if we incorrectly interprete the state.json, we might incorrectly reject an application that is deployable.

reading state.json is fairly resource intensive on the Mesos side and blocks one of their main actors.
how do we deal with the race conditions?

There have been some attempts to mitigate that -- the history service, a state.json summary etc... But it will probably involve some work to make that robust and we have so many things that need attention.

I'm not sure if it satisfies the original feature request, but would it be possible to set a threshold of deployment attempts and/or resource offers?  I think it'd be a step in the right direction to automatically stop a deploy or roll back an upgrade if it's unable to succeed after N deployment attempts or M declined resource offers.  Alternatively, it seems like either one of those could be time-based.  It would be helpful if the insufficient resources message could be shown in the debug tab of the app.  It wouldn't be an immediate response to the POST, but it would be pretty quick feedback.

I believe this is covered by rejected offers.


Add armc6 build in TFLM CI using Github-actions

We have identified bugs when building TFLM using the armc6 compiler. Thus, we would like to add a way to regression test TFLM using armc6. It is possible to run the relevant tests on our virtual hardware using AWS. By providing Github secrets and a Github actions workflow, the verification can be incorporated into the regular CI. This will guarantee correctness of execution on relevant Cortex-M platforms, and identify performance deviations during validation. A PR will be opened and tagged here.

See more at the VHT-AMI repository

Hi, this is a duplicate of #1021 and since that's been merged, we may close this PR. Thanks Matthias!


[RDBMS] BREAKING CHANGE: az mysql/postgres flexible-server create/update: Deprecate Enabled for --high-availability argument

Related command
az mysql/postgres flexible-server create/update
Description
Enabled value for --high-availability argument in commands az mysql/postgres flexible-server create/update will be deprecated. The possible values for that argument will be only ZoneRedundant, SameZone and Disabled, the value Enabled was the same as ZoneRedundant.

This checklist is used to make sure that common guidelines for a pull request are followed.

[ ] The PR title and description has followed the guideline in Submitting Pull Requests.

[ ] I adhere to the Command Guidelines.

[ ] I adhere to the Error Handling Guidelines.

RDBMS

Hi @DaeunYim, Let me know your decision to merge this now or keep it until next breaking change window after your internal discussion. Our next breaking change window would be half a year later....

Hi @DaeunYim, Let me know your decision to merge this now or keep it until next breaking change window after your internal discussion. Our next breaking change window would be half a year later....

Sure let me get back to you on that


Please render a fully usable css file with classes from the svg filenames

Do you want to request a feature, report a bug or ask a question?
Feature
What is the current behavior?
It only generates a sprite.svg file.
What is the expected behavior?
It would be nice to have a sprite.css file too, where this code is inside:
.svg-asm {
    background: url("svg/sprite.css-a740267f.svg") 74.19354838709677% 44.44444444444444% no-repeat;
}

.svg-asm-dims {
    width: 32px;
    height: 32px;
}

.svg-bat {
    background: url("svg/sprite.css-a740267f.svg") 0 0 no-repeat;
}

.svg-bat-dims {
    width: 88px;
    height: 88px;
}

.svg-c {
    background: url("svg/sprite.css-a740267f.svg") 35.483870967741936% 14.814814814814815% no-repeat;
}

.svg-c-dims {
    width: 32px;
    height: 32px;
}

.svg-clojure {
    background: url("svg/sprite.css-a740267f.svg") 0 40.74074074074074% no-repeat;
}

This is the output from the svg-sprite npm package, which is very handy. Here are the options for this:
svg-sprite --css --css-render-css --css-example --css-example will create a html where you see all your svg files on a page which is cool too.
Regards
Chris

I have a comment regarding this issue and the library itself:
If we do load an SVG library using this loader, symbols provided by this load are available all accross the HTML context (that's all correct) but what about the CSS context?
I mean, if I use some css depending on that sprite.svg like:
.patternBackground {
background: url("svg/sprite.svg#pattern") no-repeat;
}
That will result in loading the sprite.svg again! (tested using the chrome network panel)
Obviously, loading the sprite.svg file twice should be avoided at all costs ...
Am I wrong? Cause I have tested this in a very isolated example.
Thanks in advance.

You're right, but it's two different approaches: when SVGs used as JS object (in React for instance) and when it used in CSS. I expect developer should use one of them. What is use case for mixing them?

The use-case is:
My app has a single assets library/sprite SVG. I want the APP to do a single network request for that library and the symbols of that library should be available all accross de application: HTML and CSS.
I mean, it's a clear and basic use case for me. I'm not asking for heaven :)
Thanks in advance.

Ah I see now, you talking about 1 single sprite which used as source of any kind of symbols on the page. Partially it can be done just using external sprite everywhere, check extract mode examples for CSS and for JS. In each case you have single external sprite.

check extract mode examples for CSS and for JS. In each case you have single external sprite

@aalbericio is this approach worked for you?


Fix esbuild module resolve and missing parameter passing

Steps to reproduce the bug:
cd create-www/simple-crm
echo {} > package.json
npm install --dev esbuild
node $(which nue)
# ok
node $(which nue) build --production
# error: Bundler not found. Please use Bun or install esbuild

1. Fixed esbuild module resolve and missing parameter passing

introduced import-meta-resolve, because import.meta.resolve doesn't work for me
manually tested linking and nue build --production --esbuild under both node and bun

2. Added Testing and Linking guide to Contributing docs
I found I can only link by bun link or npm link to develop and test nuekit locally.
If you guys can do it via pnpm link, pls let me know :)
pnpm link+node $(which nue) (as documented in official docs) is not working:

# /Users/fritx/Library/pnpm/nue
#!/bin/sh
basedir=$(dirname "$(echo "$0" | sed -e 's,\\,/,g')")

case `uname` in
    *CYGWIN*) basedir=`cygpath -w "$basedir"`;;
esac

if [ -z "$NODE_PATH" ]; then
  export NODE_PATH="/Users/fritx/g/nue/packages/nuekit/src/node_modules:/Users/fritx/g/nue/packages/nuekit/node_modules:/Users/fritx/g/nue/packages/node_modules:/Users/fritx/g/nue/node_modules:/Users/fritx/g/node_modules:/Users/fritx/node_modules:/Users/node_modules:/node_modules:/Users/fritx/Library/pnpm/global/5/.pnpm/node_modules"
else
  export NODE_PATH="/Users/fritx/g/nue/packages/nuekit/src/node_modules:/Users/fritx/g/nue/packages/nuekit/node_modules:/Users/fritx/g/nue/packages/node_modules:/Users/fritx/g/nue/node_modules:/Users/fritx/g/node_modules:/Users/fritx/node_modules:/Users/node_modules:/node_modules:/Users/fritx/Library/pnpm/global/5/.pnpm/node_modules:$NODE_PATH"
fi
if [ -x "$basedir/bun" ]; then
  exec "$basedir/bun"  "$basedir/global/5/node_modules/nuekit/src/cli.js" "$@"
else
  exec bun  "$basedir/global/5/node_modules/nuekit/src/cli.js" "$@"
fi

Awesome/important fix again! Thanks so much.
Wonder if the import-meta-resolve module should be used on the findModule function as well. I use it to check for existence of lightningcss and stylus modules. Nuekit should start using lightningcss after calling bun add lightningcss on the project directory and when editing a CSS file. You should see a lightning icon on the console.
btw: would you like to have access rights to this repository for merging pull requests?

Thanks, I'd love to help. But I'm just learning nuejs progressively.  😄
Although I have submitted some contributions, I actually have not yet understood the entire code base.
Its minimalism is awesome and open for anyone to learn and get in touch with.

Wonder if the import-meta-resolve module should be used on the findModule function as well

Sorry, I was missing there was already a findModule. Now I've tested under both Bun and Node.
Finding that the simple implementation of findModule is also working, while the path='lib/main.js' is required in Node.
(Looks like there are still a bit of environment differences between Bun and Node...)
try {
    if (!is_esbuild) return Bun
    // working
    // const esbuild_entry = await resolve('esbuild', `file://${process.cwd()}/`)
    // return await import(esbuild_entry)
    // also working
    const esbuild = await findModule('esbuild', 'lib/main.js') // required in Node
    if (!esbuild) throw new Error('Cannot find esbuild')
    return esbuild
  } catch (err) {
    throw 'Bundler not found. Please use Bun or install esbuild'
  }


Relative strength index gridline widths are inconsistent

The top gridlines of the RSI chart contain 2x the number of light grey pixels.

Does not always seem to happen, but if you add a MACD chart underneath it, you can see that the middle line is different to the upper/lower gridlines.

Looks like it's probably happening because it'll be dealing with fractions of pixels.
This will probably give use a quick win, without having to round everything:
shape-rendering: crispEdges;

They are also being rendered on top of the actual chart lines. Image one shows this really clearly.

Opened a new issue for @jackarnstein's comment
#610

They are also being rendered on top of the actual chart lines. Image one shows this really clearly.

Good spot - this is coming directly from a d3fc component so I've raised an issue against d3fc too.


Investigate daily why daily runs do not have 24 images.

This is strange, running it manually on lambda works correctly (1 image per hour) but when it runs scheduled, it does not (6 image per hour).

Found the bug, it has to do with what time lambda daily cron decides to run the job. In manual testing, it always had a sample event which had a minute=0, so it worked but lambda might run it when minute=18 and that would cause the weather.gc.ca site to fail. Overriding the minute fixes the problem.

Working correctly.


Statically link libgcc and libstdc++ while using Clang

Clang also supports -static-{libstdc++, libgcc}.

Thanks! Merging...


Odd fire effect under certain conditions

I'm sorry if this is the wrong place to report this, but I couldn't find a repository for general CSGO/CS2 issues. This issue is present on both windows and linux, but the fact that it hasn't been reported and that there doesn't seem to be much info about it online likely mean it's hardware dependent. But I did find this reddit post showing the same issue https://www.reddit.com/r/counterstrike/comments/18ixyni/players_feet_caught_fire_when_holding_molotov/
Issue
A fire effect can appear between others feet. Others I've asked have said they see nothing, so I don't think this is intended.
![cs2 incendiary grenades](https://github.com/ValveSoftware/csgo-demoinfo/assets/70454800/a3136dc9-3376-45b7-9cf9-adb17a0e16f7)
How to reproduce
When someone holds an incendiary grenade/molotov, a small fire effect will appear at their feet. Having the grenade equipped isn't enough, it needs to be held, and the fire effect disappears when it gets thrown. The effect appears with bots as well as players. The effect isn't visible in grenade cam when aiming at yourself, or when looking down at your own model's feet, you need someone else to holdit.
![Y0130_221419](https://github.com/ValveSoftware/csgo-demoinfo/assets/70454800/93939be1-1200-44d3-a830-b13451606bb9)
Setup
I have a RX6600, on linux I used radv, on windows I used DX11, both display the same effect.

I mixed by github tabs, meant to post this on https://github.com/ValveSoftware/csgo-osx-linux


Table columns sizing is not working with col-*

I have a table like this:

                Name
                Login
                Role

                Juliano
                juliano
                Supervisor

However the columns are not respecting the sizes I've set on each 	. The first column is taking almost all of the available space and the others are using just the space necessary for its content. Why?

This is very much a Bootstrap 4 question. It is related to Bootstrap 4 using flexbox for column widths now. To make it work I have to add d-inline-block in addition to the col-1 to each  and also to each . Hope that helps.


Can't create new VHD on non-ReFS file systems

The 'RemoveIntegrityStream' method throws an InvalidOperationException when creating a VHD on a non-ReFS file system. The error message states 'Incorrect Function' which I think means the function isn't supported.

Can you please send the crash report directly from application?
I will take a look at it in meantime.

There is no crash. After creating a new VHD, I get an error saying unable
to open the vhd file. The file is created on disk, but 0 bytes.
[image: Inline image 1]
Thanks for looking at it.
On Fri, Nov 20, 2015 at 3:28 PM, Josip Medved<EMAIL_ADDRESS>wrote:

Can you please send the crash report directly from application?
I will take a look at it in meantime.
—
Reply to this email directly or view it on GitHub
https://github.com/medo64/VhdAttach/issues/1#issuecomment-158432138.

Fixed in commit 8c737f6.
Please check the latest release.

Yup, that release fixes the problem for me. Thanks very much ... and really useful utility.


Data race error

Summary of Bug
Almost test-race test is failed after #495.
I think this data race problem is occurred by goleveldb used in Ostracon.
for example:
https://github.com/line/lbm-sdk/runs/6127657380?check_suite_focus=true
Version

after #495
Steps to Reproduce

For Admin Use

[ ] Not duplicate issue
[ ] Appropriate labels applied
[ ] Appropriate contributors tagged
[ ] Contributor assigned/self-assigned

This bug was not fixed.
I merged #516 into #513. And this similar bug was occurred again.
https://github.com/line/lbm-sdk/runs/6209018884?check_suite_focus=true
WARNING: DATA RACE
[153](https://github.com/line/lbm-sdk/runs/6209018884?check_suite_focus=true#step:6:153)
Write at 0x00c0030d7690 by goroutine 120:
[154](https://github.com/line/lbm-sdk/runs/6209018884?check_suite_focus=true#step:6:154)
  github.com/line/lbm-sdk/baseapp.(*BaseApp).BeginBlock()
[155](https://github.com/line/lbm-sdk/runs/6209018884?check_suite_focus=true#step:6:155)
      /home/runner/work/lbm-sdk/lbm-sdk/baseapp/abci.go:195 +0xf9e
[156](https://github.com/line/lbm-sdk/runs/6209018884?check_suite_focus=true#step:6:156)
  github.com/line/lbm-sdk/simapp.(*SimApp).BeginBlock()
[157](https://github.com/line/lbm-sdk/runs/6209018884?check_suite_focus=true#step:6:157)
      <autogenerated>:1 +0xf7
[158](https://github.com/line/lbm-sdk/runs/6209018884?check_suite_focus=true#step:6:158)
  github.com/line/ostracon/abci/client.(*localClient).BeginBlockSync()
[159](https://github.com/line/lbm-sdk/runs/6209018884?check_suite_focus=true#step:6:159)
      /home/runner/go/pkg/mod/github.com/line/ostracon@v1.0.4/abci/client/local_client.go:295 +0x1b4
[160](https://github.com/line/lbm-sdk/runs/6209018884?check_suite_focus=true#step:6:160)
  github.com/line/ostracon/proxy.(*appConnConsensus).BeginBlockSync()
[161](https://github.com/line/lbm-sdk/runs/6209018884?check_suite_focus=true#step:6:161)
      /home/runner/go/pkg/mod/github.com/line/ostracon@v1.0.4/proxy/app_conn.go:85 +0xd4
[162](https://github.com/line/lbm-sdk/runs/6209018884?check_suite_focus=true#step:6:162)
  github.com/line/ostracon/state.execBlockOnProxyApp()
[163](https://github.com/line/lbm-sdk/runs/6209018884?check_suite_focus=true#step:6:163)
      /home/runner/go/pkg/mod/github.com/line/ostracon@v1.0.4/state/execution.go:383 +0x734
[164](https://github.com/line/lbm-sdk/runs/6209018884?check_suite_focus=true#step:6:164)
  github.com/line/ostracon/state.(*BlockExecutor).ApplyBlock()
[165](https://github.com/line/lbm-sdk/runs/6209018884?check_suite_focus=true#step:6:165)
      /home/runner/go/pkg/mod/github.com/line/ostracon@v1.0.4/state/execution.go:169 +0x252
[166](https://github.com/line/lbm-sdk/runs/6209018884?check_suite_focus=true#step:6:166)
  github.com/line/ostracon/consensus.(*State).finalizeCommit()
[167](https://github.com/line/lbm-sdk/runs/6209018884?check_suite_focus=true#step:6:167)
      /home/runner/go/pkg/mod/github.com/line/ostracon@v1.0.4/consensus/state.go:1699 +0x1056
[168](https://github.com/line/lbm-sdk/runs/6209018884?check_suite_focus=true#step:6:168)
  github.com/line/ostracon/consensus.(*State).tryFinalizeCommit()
[169](https://github.com/line/lbm-sdk/runs/6209018884?check_suite_focus=true#step:6:169)
      /home/runner/go/pkg/mod/github.com/line/ostracon@v1.0.4/consensus/state.go:1610 +0x5c7
[170](https://github.com/line/lbm-sdk/runs/6209018884?check_suite_focus=true#step:6:170)
  github.com/line/ostracon/consensus.(*State).enterCommit.func1()
[171](https://github.com/line/lbm-sdk/runs/6209018884?check_suite_focus=true#step:6:171)
      /home/runner/go/pkg/mod/github.com/line/ostracon@v1.0.4/consensus/state.go:1545 +0x146
[172](https://github.com/line/lbm-sdk/runs/6209018884?check_suite_focus=true#step:6:172)
  github.com/line/ostracon/consensus.(*State).enterCommit()
[173](https://github.com/line/lbm-sdk/runs/6209018884?check_suite_focus=true#step:6:173)
      /home/runner/go/pkg/mod/github.com/line/ostracon@v1.0.4/consensus/state.go:1583 +0x94c
[174](https://github.com/line/lbm-sdk/runs/6209018884?check_suite_focus=true#step:6:174)
  github.com/line/ostracon/consensus.(*State).addVote()
[175](https://github.com/line/lbm-sdk/runs/6209018884?check_suite_focus=true#step:6:175)
      /home/runner/go/pkg/mod/github.com/line/ostracon@v1.0.4/consensus/state.go:2251 +0x152e
[176](https://github.com/line/lbm-sdk/runs/6209018884?check_suite_focus=true#step:6:176)
  github.com/line/ostracon/consensus.(*State).tryAddVote()
[177](https://github.com/line/lbm-sdk/runs/6209018884?check_suite_focus=true#step:6:177)
      /home/runner/go/pkg/mod/github.com/line/ostracon@v1.0.4/consensus/state.go:2048 +0x7c
[178](https://github.com/line/lbm-sdk/runs/6209018884?check_suite_focus=true#step:6:178)
  github.com/line/ostracon/consensus.(*State).handleMsg()
[179](https://github.com/line/lbm-sdk/runs/6209018884?check_suite_focus=true#step:6:179)
      /home/runner/go/pkg/mod/github.com/line/ostracon@v1.0.4/consensus/state.go:888 +0xe56
[180](https://github.com/line/lbm-sdk/runs/6209018884?check_suite_focus=true#step:6:180)
  github.com/line/ostracon/consensus.(*State).receiveRoutine()
[181](https://github.com/line/lbm-sdk/runs/6209018884?check_suite_focus=true#step:6:181)
      /home/runner/go/pkg/mod/github.com/line/ostracon@v1.0.4/consensus/state.go:832 +0x8a4
...


[BUG] (Android) Commissioning fails - getting "Device not found" error

Reproduction steps
Reproduction steps:
I have an ESP32 kit with a lighting app. When I try to commission it using the Android Chiptool sample app, I get a "Device not found" error after entering wifi credentials.  But the same kit I am able to commission using the Google Matter sample app.

Select Provision chip device with Wi-Fi
scan the Qr code
Enter Wifi SSID and password

Bug prevalence
Every time I try to commission the device
Platform
Android

Logs:
java.lang.IllegalArgumentException: Receiver not registered: android.view.OplusScrollToTopManager$2@d6a6004
IllegalArgumentException:java.lang.IllegalArgumentException: Unknown URL content://com.oplus.statistics.provider/track_event
java.lang.IllegalArgumentException: Receiver not registered: android.view.OplusScrollToTopManager$2@af3ef7d
java.lang.IllegalArgumentException: Receiver not registered: android.view.OplusScrollToTopManager$2@a34e5c5
java.lang.IllegalArgumentException: Receiver not registered: android.view.OplusScrollToTopManager$2@8584828
SettingNotFoundException, fall through to G.downloadBytesOverMobileMaximum
SettingNotFoundException, fall through to G.downloadBytesOverMobileRecommended
java.lang.IllegalArgumentException: Receiver not registered: android.view.OplusScrollToTopManager$2@5ed048d
java.lang.IllegalArgumentException: Receiver not registered: android.view.OplusScrollToTopManager$2@6c56cab
E  ARP read failure: android.system.ErrnoException: read failed: EAGAIN (Try again)
E  java.lang.NullPointerException: Attempt to invoke virtual method 'java.lang.Object android.os.Bundle.get(java.lang.String)' on a null object reference
java.lang.NullPointerException: Attempt to invoke virtual method 'java.lang.Object android.os.Bundle.get(java.lang.String)' on a null object reference
Bug prevalence
Every time I try to commission the device
GitHub hash of the SDK that was being used
https://github.com/project-chip/connectedhomeip/commit/de0dfcfbc42fe574774dc440a0e89a8884b28573
Platform
android, esp32
Platform Version(s)
No response
Type
Core SDK Crash
Anything else?
No response

locally try it, and cannot reproduce it, would close it now. I guess you esp may not be beaconing in ble?  let me know whether it is still problem in your side, feel free to create new ticket with more logging on accessory and controller. thanks


Added/fixed countries from the stripe modal.

Kosovo & South Sudan don't actually work, I think it's because we're
using the 2011 version of the API? They show up in the NetSuite
interface. I have a manual workaround for those two elsewhere.

🚢

:chihuahua:


[CP][beta channel] Fail early when running dart migrate with too-high min SDK constraint

commit(s) to merge: da029c6ef365b18c3dabeded33b344f4a0b2c4d3 , 83cf6d67dc36152abe68ef529e8c2d1575ed9610 in that order
merge instructions: clean merge onto 2.12.0-29.0.dev +https://github.com/dart-lang/sdk/issues/44182 + https://github.com/dart-lang/sdk/issues/44183 + https://github.com/dart-lang/sdk/issues/44184
What is the issue: Fail early when running dart migrate with too-high min SDK constraint
What is the fix: https://dart-review.googlesource.com/c/sdk/+/171624, https://dart-review.googlesource.com/c/sdk/+/171643
Link to original  issue(s): https://github.com/dart-lang/sdk/issues/44144
/cc @kevmoo @mit-mit @whesse @athomas @vsmenon @franklinyow @pcsosinski @stereotype441

As we have already discussed this as necessary for beta release, mark as approved

Merged to beta in 6fee8e27b8206acd82cd7ed6204941916a2568e5  (2.12.0-29.7.beta).


Assertion failure in Optimizer

This program:
actor SomeActor
  let env : Env

  new create(e : Env) =>
    env = e

  be op(p1 : Bool, p2 : Bool) =>
    env.out.print("op( p1: " + p1.string() + ", p2: " + p2.string() + " )")

actor Main
  let someActor : SomeActor

  new create(env: Env) =>
    someActor = SomeActor.create(env)
    someActor.op(false, false)

when compiled results in this error message:
Building builtin -> /usr/local/lib/pony/0.2.1-250-g8aea627/packages/builtin
Building . -> /Users/hutch/Projects/nymi/DEV/tip/api/bug2/app
Generating
Optimising
Assertion failed: (DL.getTypeStoreSize(ExtractedTy) + Offset <= DL.getTypeStoreSize(IntTy) && "Element extends past full value"), function CreateExtractInteger, file /tmp/llvm20151219-57946-1560ky3/llvm-3.6.2.src/include/llvm/IR/IRBuilder.h, line 1562.
Stack dump:
0.	Running pass 'CallGraph Pass Manager' on module 'app'.
1.	Running pass 'BasicBlock Pass Manager' on function '@"SomeActor_$dispatch"'
2.	Running pass 'LoadCombine' on basic block '%handler'
Illegal instruction: 4

There is no error if ponyc --debug is used.

I see it as well with homebrew llvm 3.6.2, OS X 10.11.2, ponyc 0.2.1-261-g632d836

OK, I reproduce this on OS X, but not on Linux or Windows.
It occurs when the first 2 parameters are Bool and both are referenced. If either one is any type other than Bool (I've tried U32, U8, I8 and String) or is not referenced then the crash doesn't occur.
Later parameters don't seem to have any affect, whether or not they are Bool and referenced.
It also only happens with behaviours, not functions.
The simplest case I have found is:
actor Main
  new create(env: Env) =>
    op(true, true)

  be op(a: Bool, b: Bool) =>
    if a and b then
      @printf[I32]("Oops\n".cstring())
    end

(I used @printf to avoid having to save env to a field.)
Handing over to @sylvanc, because I know he'll love this one :)

Fixed. The LLVM LoadCombine pass appears to be buggy on OSX. More cases fail with LLVM 3.7 than with LLVM 3.6. I've disabled LoadCombine when building on OSX.

Can me make this PONY_LLVM dependent please.
I'd rather use 3.6 and LoadCombine then.
In gencontrol.c we already check for the bad 3.7.0 version.

BTW: I've also detected crazy darwin-only gcc bugs with long double, SSE in static struct inits recently in my compiler (wrong offset). Need to find out the offender later. Workaround was to init some member fields at run-time again. My trust in the darwin compiler folks is wading...

The problem is present in 3.6 as well. The example code at the top provokes it. I had thought it was a ponyc bug, and that I'd simply been unable to track it down, but sadly that doesn't seem to be the case.
I'm hoping 3.8 addresses this. We'll need to rewrite all of the code to emit debug info in order to support 3.8 (which is both good and bad: the old LLVM debug info API was not ideal, and the new one appears better, but it will delay 3.8 adoption).


Error: Modifier is already applied on this attribute!

I turned my friend into creative, then a minute later I turned myself into creative - that's when I got the error the first time.

If relevant, we weren't near each other (probably about 10 chunks away from each other).
Crash report:
https://pastebin.com/bsfPYAk5
ReachFix-1.12.2-1.0.1
This occurred with a custom mod pack.

Fixed in v1.12.2-1.0.2


Same exit node all the time?

Perhaps I'm reading this wrong but doing lsof -a -p <pid> shows me a bunch of TCP filedescriptors my node program uses, while routing through rotating-proxy. These all read as follows:
TCP <IP_ADDRESS>:<var>->sandiego.ar01.host28.scalematrix.net:http (ESTABLISHED)
Shouldn't sandiego.ar01.host28.scalematrix.net always be changing, or isn't this the exit node?

solved


Contribution Proposal

Name
Vivek Srikrishnan
Email
<EMAIL_ADDRESS>Institution
Cornell University
Referral
I'm a coauthor!
Topic Area
Uncertainty Quantification
Description
Tutorial notebook on Markov Chain Monte Carlo for uncertainty quantification with an application to calibrating HYMOD.
Additional Information
!

Hi @vsrikrish, your proposal is approved! Please submit a PR with your contribution when you are ready.


✨ Centered everything in the heading

What type of PR is this? (check all applicable)

[ ] 🚀 Added Name
[ ] ✨ Feature
[ ] 🐛 Grammatical Error
[x] 📝 Documentation Update
[ ] 🚩 Other

Description

Centered the heading styles
Ported Markdown to HTML for headings and badges
Introduced dwyl hits instead of glitch visitor badge, but it is disabled because it does not line up with the styles of other badges

from:

to:

Let me know if you want me to change something in my PR.

Reopening it


added Zomato scraper

Description

The changes made in this pull request should be briefly described.

I have added a Zomato scraper that scrapes zomato page and provides name, cuisine, area, rating, offers, etc to the user.
Resolves: #515
Checklist

Before submitting this pull request, kindly verify that the ensuing checkpoints have been reached.

[x] Have you adhered to the repository's defined coding convention rules?
[x] Have you updated the 'documentation.md' file with the method/function documentation?
[x] Have you sent a message along with the result or response?
[x] Have you used the try-catch technique?
[x] Has the method/class been added to the documentation (md file)?

Screenshots

Uploading a screenshot illustrating the approach you developed for validation is required.

Additional Notes/Comments

Any additional remarks or suggestions concerning this pull request are welcome.

I certify that I have carried out the relevant checks and provided the requisite screenshot for validation by submitting this pull request.
I appreciate your contribution.

Please review

Great work @Swapnil-Singh-99 !!
Do not forget to

Share your contribution on socials(twitter mainly), tag us and Clueless 🫂
Give this repository a star ✨
Follow Clueless Community on GitHub ✅


Website/updatefooter

Pull Request Test Coverage Report for Build 99ff2acb756ce20dc3fdd81b7df2422666e55eb5-PR-1569

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 70.683%

Totals

Change from base Build 8ec2b8d136298f165a9b8e5956158d1ec6156d72:
0.0%

Covered Lines:
1965

Relevant Lines:
2780

💛  - Coveralls


build a mobile side app with peatio

hi guys,
I'm working on the mobile app, and looking for members who are also interested in it.
The Peatio's backend is still ok, but frontend seems too old. The UI/UX cannot satisfy our clients anymore. People are leaving us and moving to some other exchanges. Therefore, we need a mobile app to make Peatio better, and the best (finally... I'm not sure about that.)
I'm going to build the mobile app with ionic/react or other solutions that make it run on both iOS and Android, and desktop maybe.
Please come and join us.
The things we already done

an exchange site with eth and erc20 coins implemented.
multiple coins trading

The things we are about to do
build a hybrid mobile app which can handle mulitple coins on market

deposit
withdraw
trading
information

team communication
no wechat, no whatsapp, no skype. Slack maybe or maybe not.
Basically we programmers communicate on github/bitbucket.
licence
The app will be half open-source and half closed for members only. You will get paid, maybe not very nice at very first, but you will.
why we don't open whole source?

because we have some unique specifications which will be unnecessary for all the users.
also, because we bought some codes as lib, which are not open source license.

skill-set
mobile app and front-end experience is welcome, including but not limited to

angular/react/vue
understanding the backend of Peatio, (especially, the api/v2.)

Let's do it.

@shouton kindly get in touch with us - Skype: martin_princeberk and we will see if we can be of help to your project. BTW we already have a working mobile app which you might take a look at

You can contact us to for mobile app and other services skype : physivert

@scatterp, @mxo2
Cool!
but let me ask some questions.

is your mobile app based on  peatio-api-v2?
how much can you share you code with us 100% open or it is just a private project?

I know I'm a little late to the conversation, however if you make this as a PWA with the exisiting API calls and registration aspects as the existing peatio you can make this easily with BuildFire.

Let our team of experts assist you & build your own mobile side app with peatio with features such as – admin backend panel, API integration, margin trading, mobile application and payment gateway integration.
For more details visit :
Website : https://antiersolutions.com/cryptocurrency-exchange-development-company.html
Email us<EMAIL_ADDRESS>Skype id<EMAIL_ADDRESS>

hi, @HysMagus
yes, finally, we do it as PWA. 'Cuz app store will not accept the app even if we build one.
rewrite all UIs, is painful. coffeejs...


MSVD-QA and MSRVTT-QA evaluation

for the results in the few shot table which file did you use test_qa or val_qa for MSVD-QA and MSRVTT-QA evaluation

Hi @KerolosAtef ,
Thank you for your interest in our work and apologies for the late response. We use the validation set for MSVD and MSRVTT and the test set for TGIF. A copy of the annotation files have been attached in the links.
Thank you


Feature/collapse downstream

What? and Why?

What does this pull request change/fix? Why was it necessary?

Remove cora logic and publish all submissions to same queue. Necessary in order to have one downstream service.
Checklist

[x] CHANGELOG.md updated? (if required)

Codecov Report

Merging #206 into master will decrease coverage by 0.01%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master     #206      +/-   ##
==========================================
- Coverage   99.18%   99.17%   -0.02%
==========================================
  Files           8        8
  Lines         488      482       -6
==========================================
- Hits          484      478       -6
  Misses          4        4

Impacted Files
Coverage Δ

tests/test_response_processor.py
100% <100%> (ø)
:arrow_up:

app/settings.py
96.55% <100%> (-0.12%)
:arrow_down:

app/response_processor.py
100% <100%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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

 (5) Collapse sdx-downstream into a single service


Support custom types

Systems and tools that want to adopt CDEvents may already have a set of events or webhooks defined, which needs to be mapped to CDEvents. It may happen that not all existing events may map to a CDEvent, which raises the question of what to do in those cases.
If the tool supports multiple event formats, it may retain its original messages and add CDEvents as an alternative format, with only a subset of the events supported. Consumers that want to benefit from CDEvents, as well as the extra tool messages, may need to listen to two different channels for both kinds of events.
An alternative solution would be to let CDEvents encapsulate this non-standard data, so that consumers may only listen to one channel to receive the event and use a single SDK to at least extract the event payload and context.
CDEvents allows today for customData to be added to the event's payload. This unfortunately is not enough to fully solve the problem described above. There are two alternative options that could help:

either allow tools to define their own custom CDEvents types, optionally with their own schemas, and let CDEvents SDK marshal and unmarshal such events
or introduce a CDEvent generic/encapsulating event, and let tools send and consume any non-standard event through it. This second option means that no unexpected event type needs to be accepted by the SDKs, and the details about the type and optionally schema would have to be hosted in the customData, making it impossible for the CDEvents SDK to validate the payload

While custom types or generic events may be counterproductive in terms of standardisation, they may be very beneficial during the initial adoption phases of CDEvents.

Fixed by #184 and #185


Update erc.yml after metadata update

When a user changes the main file or display file after uploading, then the erc.yml must be updated.

https://github.com/o2r-project/o2r-muncher/pull/95


Airdrop works?

Hello! I saw the project, my question is if that card could work with continuity and airdrop on hackintosh. Thank you.

@KikeVR1996
Airdrop doesn't work in any way.
With itlwm.kext you don’t have any Handoff or Continuity feature.
AirportItlwm.kext provides minimal Continuity features (Handoff and Universal Clipboard, not always available).


Code helper process high cpu usage

Type: Bug
I noticed my vs code is slow recently, and in acitiviy monitor, code helper process take about 100% cpu, I troubleshooted the problem, turns out there are around 8k+ history files which "code helper" keeps on stats on them. After delete all of those, "Code helper"'s cpu usage back to normal.
VS Code version: Code 1.73.1 (Universal)<PHONE_NUMBER>f055b99068d3688932416f2346dd3b, 2022-11-09T02:08:38.961Z)
OS version: Darwin arm64 22.1.0
Modes:
Sandboxed: No

System Info

Item
Value

CPUs
Apple M1 Pro (8 x 24)

GPU Status
2d_canvas: enabledcanvas_oop_rasterization: disabled_offdirect_rendering_display_compositor: disabled_off_okgpu_compositing: enabledmetal: disabled_offmultiple_raster_threads: enabled_onopengl: enabled_onrasterization: enabledraw_draw: disabled_off_okskia_renderer: enabled_onvideo_decode: enabledvideo_encode: enabledvulkan: disabled_offwebgl: enabledwebgl2: enabledwebgpu: disabled_off

Load (avg)
6, 5, 5

Memory (System)
16.00GB (0.16GB free)

Process Argv
--crash-reporter-id e375ec04-becc-43fb-9a2b-9523089c1b92

Screen Reader
no

VM
0%

Extensions (8)

Extension
Author (truncated)
Version

intellij-idea-keybindings
k--
1.5.4

remote-ssh
ms-
0.92.0

remote-ssh-edit
ms-
0.84.0

remote-explorer
ms-
0.0.2

rust-analyzer
rus
0.4.1294

crates
ser
0.5.10

code-settings-sync
Sha
3.4.3

vim
vsc
1.24.3

A/B Experiments
vsliv368cf:30146710
vsreu685:30147344
python383cf:30185419
vspor879:30202332
vspor708:30202333
vspor363:30204092
vslsvsres303:30308271
pythonvspyl392:30443607
vserr242:30382549
pythontb:30283811
vsjup518:30340749
pythonptprofiler:30281270
vshan820:30294714
vstes263cf:30335440
pythondataviewer:30285071
vscod805:30301674
binariesv615:30325510
bridge0708:30335490
bridge0723:30353136
cmake_vspar411:30581797
vsaa593cf:30376535
pythonvs932:30410667
cppdebug:30492333
vsclangdf:30486550
c4g48928:30535728
dsvsc012cf:30540253
azure-dev_surveyone:30548225
pyindex848cf:30577861
nodejswelcome1cf:30587006
3biah626:30602489
gswce1:30612156
iaj6b796:30613358
dbltrim-noruby:30604474
89544117:30613380

Problem:

Dtruss:

wc -l

Use this command to clear local history

Can you follow this wiki and post the results back here to understand more about why performance is so bad for you: https://github.com/Microsoft/vscode/wiki/Performance-Issues
Thanks!

@bpasero
Can you try this on your machine
 cd ~/Library/Application\ Support/Code/User/History && touch {{a..z},{A..Z},{0..99}}.txt

Yeah I wonder what process is causing the stat to begin with. I am not aware of code in VS Code that would constantly stat all history entries. It is expected though that the history can grow very large because it contains up to 50 entries for files you make edits to.

I see. Let me see what I can do.

Yep, it is an extension called setting sync. https://marketplace.visualstudio.com/items?itemName=Shan.code-settings-sync.

@bpasero from the project's github, seems the plugin both not maintained and with high cpu issue, is there any way to add an alert or something on the extension market?

@shuoli84 oh great you figured that out!
@isidorn @alexdima fyi I think there was a recent issue where you also figured out that the extension causes issues.

This is configurable via settings, so I suggest you look there to reduce the number of entries. I am hesitant to change the defaults though as it does not seem to cause issues otherwise.

Got it. I think neither "Max File Entries" nor "Max File size" useful for projects with many small files. I close this for now, "too many files created" is a different issue anyway. Thanks for your time~

Tracked at #147707


myst  formatting directive with only 1 parameter

Context
```{exercise-start}
:label: ex1
```

is formatted as
```{exercise-start}
---
label: ex1
---
```

Proposal
I think it is too verbose for this case, especially when we have several directives like that in a file.
When there is only 1 parameter, it should be kept with the syntax :label: ex1.
Tasks and updates
No response

Another case for which really I wish to have the shorter format
```{math}
:label: rayleigh_eq
\varphi'' - k^2 \varphi - \frac{U''}{U-c} \varphi = 0
```

instead of
```{math}
---
label: rayleigh_eq
---
\varphi'' - k^2 \varphi - \frac{U''}{U-c} \varphi = 0
```

I have files with several equations like that. Two more lines per equation make the whole file much longer and less readable.


updated v6.4.0

Checklist

[x] Used a personal fork of the feedstock to propose changes
[x] Bumped the build number (if the version is unchanged)
[x] Reset the build number to 0 (if the version changed)
[x] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[x] Ensured the license file is being packaged.

Closes https://github.com/conda-forge/octave-feedstock/pull/57

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

@conda-forge-admin please rerender

hmmm

where exactly do we give it sundials?
checking for SUNDenseLinearSolver... no
checking whether SUNDIALS API provides the necessary functions... yes
checking whether SUNDIALS IDA is configured with double precision realtype... yes
checking sunlinsol/sunlinsol_dense.h usability... ye

where exactly do we give it sundials?
checking for SUNDenseLinearSolver... no
checking whether SUNDIALS API provides the necessary functions... yes
checking whether SUNDIALS IDA is configured with double precision realtype... yes
checking sunlinsol/sunlinsol_dense.h usability... ye

https://github.com/izahn/octave-feedstock/blob/50d6cbeb3588919bb3d98c308c4e251d0a07f9b2/recipe/meta.yaml#L53

where exactly do we give it sundials?
checking for SUNDenseLinearSolver... no
checking whether SUNDIALS API provides the necessary functions... yes
checking whether SUNDIALS IDA is configured with double precision realtype... yes
checking sunlinsol/sunlinsol_dense.h usability... ye

https://github.com/izahn/octave-feedstock/blob/50d6cbeb3588919bb3d98c308c4e251d0a07f9b2/recipe/meta.yaml#L53

Okay, testing locally. Please lower sundials. Goes much farther than this.

I cannot recommend changes... but as a first swipe, please go for <6 both runtime and host

I sorta believe this is it. I am kinda confused why sundials isn't pinned globally though...

Okay, got this error for sundials 5.7.x on osx
      void std::__1::vector<Magick::ColorRGB, std::__1::allocator<Magick::ColorRGB> >::__push_back_slow_path<Magick::ColorRGB>(Magick::ColorRGB&&) in libcorefcn.a(libcorefcn_la-__magick_read__.o)
  NOTE: a missing vtable usually means the first non-inline virtual member function has no definition.
ld: symbol(s) not found for architecture x86_64

waiting for linux run to go through with 5.8.x
should we use the new qt feedstock btw?

As an alternative to sticking with sundials 5.x we could adopt the Arch Linux patch at https://github.com/archlinux/svntogit-community/blob/packages/octave/trunk/PKGBUILD .  That would be my preference.

That would be my preference

my preference, too. Please go ahead. Or do you want to give me push access to your fork?

archlinux patches, to the rescue, yet again! 🥳

OK great! The direct link to the patch is https://github.com/archlinux/svntogit-community/blob/packages/octave/trunk/octave-sundials-6.0.patch
I invited you to my fork, feel free to push there!

Octave successfully built.  Now choose from the following:

   ./run-octave    - to run in place to test before installing
   make check      - to run the tests
   make install    - to install (PREFIX=$PREFIX)

   HG ID for this build is "8d7671609955"

TODO:

[ ] add libtool

@izahn
Mamba failed to solve:
 - octave 6.4.0.* h8594d46_0
 - _openmp_mutex >=4.5
 - alsa-lib >=1.2.3,<<IP_ADDRESS>a0
 - arpack >=3.7.0,<<IP_ADDRESS>a0
 - bzip2 >=1.0.8,<2.0a0
 - curl >=7.80.0,<8.0a0
 - fftw >=3.3.10,<4.0a0
 - fltk >=1.3.8,<1.4.0a0
 - fontconfig >=2.13.1,<3.0a0
 - fonts-conda-ecosystem
 - freetype >=2.10.4,<3.0a0
 - ghostscript
 - gl2ps >=1.4.2,<<IP_ADDRESS>a0
 - glib
 - glpk >=4.65,<4.66.0a0
 - gnuplot
 - graphicsmagick >=1.3.37,<2.0a0
 - hdf5 >=1.12.1,<<IP_ADDRESS>a0
 - icu >=68.2,<69.0a0
 - libblas >=3.8.0,<4.0a0
 - libcblas >=3.8.0,<4.0a0
 - libcurl >=7.80.0,<8.0a0
 - libgcc-ng >=9.4.0
 - libgfortran-ng
 - libgfortran5 >=9.4.0
 - libglib >=2.70.2,<3.0a0
 - libglu
 - libiconv >=1.16,<1.17.0a0
 - liblapack >=3.8.0,<4.0a0
 - liblapacke >=3.8.0,<4.0a0
 - libpng >=1.6.37,<1.7.0a0
 - libsndfile >=1.0.31,<1.1.0a0
 - libstdcxx-ng >=9.4.0
 - libxml2 >=2.9.12,<2.10.0a0
 - libzlib >=1.2.11,<1.3.0a0
 - ncurses >=6.2,<6.3.0a0
 - openssl >=1.1.1l,<1.1.2a
 - pcre >=8.45,<9.0a0
 - portaudio >=19.6.0,<20.0a0
 - qhull >=2020.2,<2020.3.0a0
 - qscintilla2 >=2.11.2,<2.12.0a0
 - qt >=5.12.9,<5.13.0a0
 - readline >=8.1,<9.0a0
 - suitesparse >=5.10.1,<5.11.0a0
 - suitesparse >=5.10.1,<6.0a0
 - sundials >=6.0.0,<6.1.0a0
 - texinfo
 - xz >=5.2.5,<5.3.0a0
 - zlib >=1.2.11,<1.3.0a0
 - coreutils

with channels:

The reported errors are:
- Encountered problems while solving:
-   - package octave-6.4.0-h8594d46_0 requires sundials >=5.8.0,<5.9.0a0, but none of the providers can be installed
-

We may need  to pin to 5.8...

@conda-forge-admin, please rerender

@conda-forge/octave (@ocefpaf @isuruf): all green as of 3f22ad8 + added libtool two new maintainers. Please merge/automerge when ready, thanks.
Up next (future PR): try qt-main and build for osx-arm64 + address issues

It looks good to me!

This one is ready for review @conda-forge/octave


REF: Companion PR to ophyd StatusBase API change

Changes to run_engine.py are minimal. Most of this is cleaning up old "done" logic in examples.py, some of which predates status objects.

Both of these PRs need a rebase.

😢


flutter_view_ios__start_up devicelab test failures

A couple commits showed failures for the flutter_view_ios__start_up test:
85f09f6 (xster)
b0eb163 (xster)
CC: @aam @a-siva @xster
The failure seems to be related to a sync/async option in the Dart VM:
......
2018-07-16T19:40:08.032494: stdout: [  +33 ms] Application launched on the device. Waiting for observatory port.
2018-07-16T19:40:08.400210: stdout: [ +367 ms] [VERBOSE-3:dart_vm.cc(422)] Error while initializing the Dart VM: Snapshot not compatible with the current VM configuration: the snapshot requires 'release no-type_checks no-asserts no-error_on_bad_type no-error_on_bad_override no-sync_async reify_generic_functions arm64' but the VM has 'release no-type_checks no-asserts no-error_on_bad_type no-error_on_bad_override sync_async reify_generic_functions arm64'
2018-07-16T19:43:49.083340: Task failed: TimeoutException after 0:05:00.000000: Future not completed2018-07-16T19:43:49.083441:

Stack trace:
2018-07-16T19:43:49.123649: package:flutter_devicelab/tasks/perf_tests.dart 131:7      StartupTest.run.
===== asynchronous gap ===========================
dart:async                                                 _AsyncAwaitCompleter.completeError
package:flutter_devicelab/tasks/perf_tests.dart            StartupTest.run.
===== asynchronous gap ===========================
dart:async                                                 _asyncErrorWrapperHelper
package:flutter_devicelab/tasks/perf_tests.dart            StartupTest.run.
package:flutter_devicelab/framework/utils.dart 369:24      inDirectory
===== asynchronous gap ===========================
dart:async                                                 _asyncThenWrapperHelper
bin/tasks/platform_view_ios__start_up.dart                 main.
package:flutter_devicelab/framework/framework.dart 125:32  _TaskRunner._performTask.

2018-07-16T19:43:50.161705: Force quitting process:
command : /Users/flutter/.cocoon/flutter/dev/devicelab/../../bin/flutter run --verbose --profile --trace-startup -d e7184ae5fe05c2ea2ad4654ac70b4ba19c92f2c6
  started : 2018-07-16 19:38:49.066724
  pid     : 18606
2018-07-16T19:43:50.165690: exitcode: -15
2018-07-16T19:43:51.175549: Task execution finished

Task failed with the following reason:
Timeout waiting for task process to exit: Future not completed

Is this still an issue?  I know I encountered this problem internally, but it was fixed.

I don't think so we have been running with this flag turned on for more than a month now.


Add apple_rules_lint at 0.2.0

The test module I added does not contain any actual tests, it verifies everything at build time.


Images always come out as JPEGs internally

Thank you for creating this wonderful app.
:+1:
There is one problem I’ve found:

I take a screenshot.
I choose PNG as the format.
I share it with my computer using Bluetooth.
I open it with an image viewer.
The image viewer says that the file is not a valid PNG.
I open the image with a hex editor.
The first letters in the file are: JFIF (indicating the file is actually a JPEG), when the first letters should be: PNG.

I did the same thing but chose WEBP as the format, but the file still started with: JFIF, instead of something like: RIFFr WEBPVP8.
I also redid both of the aforementioned actions, but shared the file using Phone Saver (version 5.2.1), but the same thing happened.
It seems that the file always comes out as a JPEG on the inside, and only the file extension (.jpeg, .png, .webp) changes.
(Note: Most programs (like the web browsers) are coded the silently ignore a disparity between file extension and contents, which might have masked this issue.)
I am using F-Droid Screenshot Assistant (version 2.0.1), with Android 9.
If you need more diagnostics information, just ask.
:slightly_smiling_face:

What an insanely good catch! Already found the problematic code section. I am currently wrinting my master's thesis though, so its really hard to find the time.
It may take me some time to squeeze this in. I am however always open to good pull requests :P


Unable to connect to PostgreSQL server: FATAL: password authentication failed for user "smartloy_user"

Unable to login from adminer (note: I'm just starting with postgres, i have not tried to login from anything else at this point) while username and password are correct (I have checked many times)
docker-compose.yml
version: '3.8'
services:
  postgres_db_smartloy:
    image: postgres
    container_name: smartloydb
    restart: always
    volumes:
      - ./data/db:/var/lib/postgres/data
    ports:
      - '5432:5432'
    environment:
      - POSTGRES_DB=smartloy
      - POSTGRES_USER=smartloy_user
      - POSTGRES_PASSWORD=smartloy_353##$$
    networks:
      - smartloy

  adminer:
    image: adminer
    container_name: adminer
    restart: always
    ports:
      - '8080:8080'
    networks:
      - smartloy

networks:
  smartloy:

Device:
Distributor ID:	Debian
Description:	Debian GNU/Linux 12 (bookworm)
Release:	12
Codename:	bookworm

Docker:
Client:
 Version:           20.10.24+dfsg1
 API version:       1.41
 Go version:        go1.19.8
 Git commit:        297e128
 Built:             Thu May 18 08:38:34 2023
 OS/Arch:           linux/amd64
 Context:           default
 Experimental:      true

Server:
 Engine:
  Version:          20.10.24+dfsg1
  API version:      1.41 (minimum version 1.12)
  Go version:       go1.19.8
  Git commit:       5d6db84
  Built:            Thu May 18 08:38:34 2023
  OS/Arch:          linux/amd64
  Experimental:     false
 containerd:
  Version:          1.6.20~ds1
  GitCommit:        1.6.20~ds1-1+b1
 runc:
  Version:          1.1.5+ds1
  GitCommit:        1.1.5+ds1-1+deb12u1
 docker-init:
  Version:          0.19.0
  GitCommit:

docker-compose version 1.29.2, build unknown
docker-py version: 5.0.3
CPython version: 3.11.2
OpenSSL version: OpenSSL 3.0.11 19 Sep 2023

Starts working after changing password in docker-compose.yml file (not sure why but it's working now)

idk why but for me nothing is working....

@felipeit I'm also unable to detect the issue, but changing password to simple text like "user_pass" worked for me previously it was like "user_pass@#@$@$2".
Are you getting the same error  "password authentication failed for user 'user'" ?

The hash sign # creates a comment in yaml. You should put double character around your password if it contains special characters

Yeah @abkarim

this is something with SCRAM authentication.
docker-compose.yml

i have set POSTGRES_HOST_AUTH_METHOD like md5 but dont have effect...


Setting for "prefer IPv4" or "disable IPv6"

Verification

[X] This issue's title and/or description do not reference a single formula e.g. brew install wget. If they do, open an issue at https://github.com/Homebrew/homebrew-core/issues/new/choose instead.

Provide a detailed description of the proposed feature
Add a global setting and/or command-line argument to

Prefer IPv4
Prefer IPv6
Disable IPv4
Disable IPv6

What is the motivation for the feature?
My home internet is provided by TekSavvy. In my area, they use the infrastructure of Vidéotron.
While Vidéotron does provide IPv6 to its direct customers, it does not provide IPv6 for clients of resellers, such as TekSavvy. This is to encourage people to pay the higher price that they charge and to enforce their monopoly on my region.
Politics aside, I am using an accessibility service, Hurricane Electric Free IPv6 Tunnel Broker, at the router level to provide my home network with access to IPv6. However, download speeds with the tunnel brokers are atrocious, which is to be expected.
Being able to restrict Homebrew from downloading (not requesting package versions) via IPv6 would speed up the download process by a lot.
How will the feature be relevant to at least 90% of Homebrew users?
People who live in Canada, have a monopoly enforced by the government for internet access in their region or otherwise use a tunnel broker or VPN might need such a config for Homebrew's downloads.
Admittedly, it might not be 90%+ of users.
What alternatives to the feature have been considered?
Being able to offload the download process from Homebrew to another download manager like aria2c would also solve this issue, since other download managers are probably able to be configured for this kind of scenario.

There is a curl option to choose IPv4 only (--ipv4) you can add it to your .curlrc and set HOMEBREW_CURLRC=1.
For anything more advanced than that, you're probably looking at something on system or DNS level. Basic rule of thumb is if it's impossible to do with curl alone, there's nothing much we can do ourselves.

Thanks, that's exactly what I was looking for


Unable to share a preview link

Issue Summary
Unable to share a preview link with other admin users.
Steps to Reproduce

On an existing project e.g Pull the latest wagtail bakery.
Open admin in one browser e.g. Chrome (simulating one user)
Login and edit a page. Copy the Preview link from the 'Preview in a new tab button'
e.g. http://localhost:8000/admin/pages/60/edit/preview/?mode=
Open another browser e.g. Safari (simulating second user) and go to the copied link
The user will not be logged in and will be taken to the login screen with a redirect url e.g.
http://localhost:8000/admin/login/?next=/admin/pages/60/edit/preview/%3Fmode%3D
Login with credentials
An Error shows on the route e.g. http://localhost:8000/admin/pages/60/edit/preview/?mode=
Preview not available
Preview cannot display due to validation errors.
Click save to highlight the relevant fields.

This can be a useful feature that some of our content loaders use to share working status changes of pages internally. This used to be something that worked in older versions of Wagtail. Sorry I am unable to provide a version of Wagtail where it broke. Maybe we just need to be better at using the Moderators workflows.
I consider this a bug. I would expect the latest draft revision for that page to render when the second user visits the page after logging in.

I have confirmed that this issue can be reproduced as described on a fresh Wagtail project: Yes

Technical details
As tested with the latest Wagtail Bakery

Python version: 3.12.5
Django version: 5.0.8
Wagtail version: Version: 6.2.1
Browser version: Chrome: 128.0.6613.86, Safari 17.5

Working on this

Anyone can contribute to this. View our contributing guidelines, add a comment to the issue once you’re ready to start.

This is expected, that preview link is specific to your current editing session and not meant to be viewed when you're not editing, because the data comes from the form that has not been saved into a revision.
To share a preview of a saved draft revision, you can go to the history view and click on the three-dot menu and click Preview. That link can be shared to other admin users who have permissions to edit the page.

Thank you for reviewing @laymonage. It's nice to find things like the ability to share a preview of a saved draft revision! Thanks for sharing. I figured that there must be something specific to the users editing session, appreciate you confirming.


⚠ Bofrost.es has degraded performance

In 6cc1c94, Bofrost.es (https://www.bofrost.es) experienced degraded performance:

HTTP code: 200
Response time: 1505 ms

Resolved: Bofrost.es performance has improved in 319789c after 6 minutes.