Automate updates from Weblate

Until now, we have been automatically updating our translations files when updates are made to our text strings. These updates are then automatically pushed to Weblate; the online community driven translation service. However, when new translations are made, we have not been receiving the translations from Weblate.
This PR adds a new job to the update-translations workflow to:

Automatically check for new translations made on Weblate
Pull changes from Weblate to a branch called weblate
Create a pull request to add those changes to Rebel Engine

Oops! This updated the update-translations branch not the main branch. I've resubmitted the Pull Request against the main branch.


macOS ZFS Sandbox

Rebase and squash of the current macOS worker.

Is the GitHub actions failure a bug related to the new implementation of finished for macOS sandboxes?

It was from an earlier Implementation before I moved the code to the sandbox.  This line needed to be removed from the build function:
 Zfs.unmount t ~ds >>= fun () ->


Build directory not on include path after FindTensorflow.cmake

Environment

info
output

os
Ubuntu 18.04

c++ version
7.4.0

TF version
1.14.1

TF is working
works

Issue
Build directory not on include path after FindTensorflow.cmake
Context:
Just trying to include image_ops.h
~/coding/catkin_ws$ ls $TENSORFLOW_BUILD_DIR/includes/tensorflow/cc/ops/
array_ops.h                        control_flow_ops.h           image_ops.h            list_ops.h              manip_ops.h           no_op.h                 remote_fused_graph_ops.h           string_ops.h
array_ops_internal.h               control_flow_ops_internal.h  image_ops_internal.h   list_ops_internal.h     manip_ops_internal.h  no_op_internal.h        remote_fused_graph_ops_internal.h  string_ops_internal.h
audio_ops.h                        data_flow_ops.h              io_ops.h               logging_ops.h           math_ops.h            parsing_ops.h           sparse_ops.h                       training_ops.h
audio_ops_internal.h               data_flow_ops_internal.h     io_ops_internal.h      logging_ops_internal.h  math_ops_internal.h   parsing_ops_internal.h  sparse_ops_internal.h              training_ops_internal.h
candidate_sampling_ops.h           functional_ops.h             linalg_ops.h           lookup_ops.h            nn_ops.h              random_ops.h            state_ops.h                        user_ops.h
candidate_sampling_ops_internal.h  functional_ops_internal.h    linalg_ops_internal.h  lookup_ops_internal.h   nn_ops_internal.h     random_ops_internal.h   state_ops_internal.h               user_ops_internal.h

Reproduce:
I followed the directions to copy the output of bazel-genfiles into ${TENSORFLOW_BUILD_DIR} as described here https://github.com/PatWie/tensorflow-cmake#inference
Output
The example inference file builds fine for me, but when trying to expand it by including image_ops I get the following error
fatal error: tensorflow/cc/ops/image_ops.h: No such file or directory
 #include "tensorflow/cc/ops/image_ops.h"
          ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
compilation terminated.

Expectation
Big beautiful green letters saying compile completed with 0 errors
Investigation
~/coding/catkin_ws$ python -c "import tensorflow as tf; print(tf.__version__); print(tf.__cxx11_abi_flag__); print(tf.sysconfig.get_include()); print(tf.sysconfig.get_lib() + '/libtensorflow_framework.so')"
1.14.1
1
/home/tyler/.local/lib/python2.7/site-packages/tensorflow/include
/home/tyler/.local/lib/python2.7/site-packages/tensorflow/libtensorflow_framework.so

Fixed it by adding
target_include_directories(TensorFlow_DEP SYSTEM INTERFACE ${TensorFlow_BUILD_DIR}/includes/

in FindTensorFlow.cmake.

In 1.14 TF has changed many header files. There was an attempt of supporting this version (https://github.com/PatWie/tensorflow-cmake/tree/1.14.0). But I currently see no pressure to support this version as well.


doubts about tracking

First, thank you for your work. I have some confusion about the tracking part in the paper. The paper presents L tracking, where the weight for the depth part is determined by the standard deviation, and the weight for the color part is controlled by λt. So, how does {R,t} influence L tracking, and why minimizing L tracking can optimize {R,t}? Does this {R,t} refer to the current frame or all sampled frames?

Hi!
Thanks and sorry for my late reply! Thanks for your question.
The {R, t} represents the pose ONLY of the current frame. We optimize the post of the current frame such that it renders a color and depth as close as possible to the sensor depth at the same frame. Does that help?


luci-mod-network: wireless.js: Key input disappears for PSK/PSK2 client modes

Steps to reproduce:

go to: Network → Wireless → Edit on any wireless interface
Interface Configuration -> General Setup: Set Mode to Client or Client (WDS)
Interface Configuration -> Wireless Security: Set Encryption to WPA2-PSK, WPA-PSK (or any non-WPA3 PSK option)
Observe no Key input to define pre-shared key

Actual behavior:
Any non-WPA3 encryption mode using pre-shared key for authentication will hide the Key field. Access point modes work fine with any encryption. Client modes with WPA3-SAE also work.
Expected behavior:
Key field should appear for all pre-shared key modes as it is required
Additional Information:
Bisected LuCI repository and identified 75a2fd233baabf6fa5bafcb13ccc6d7000a4604d as the problem commit. I don't understand exactly how the dependency works, it could be that the Key field inherits the dependencies of the ppsk item, which depends on Access point modes. WPA3 dependencies are added afterwards, which would explain why WPA3-SAE allows Key entry.
DISTRIB_ID='OpenWrt'
DISTRIB_RELEASE='SNAPSHOT'
DISTRIB_REVISION='r25004+2-b463737826'
DISTRIB_TARGET='ath79/generic'
DISTRIB_ARCH='mips_24kc'
DISTRIB_DESCRIPTION='OpenWrt SNAPSHOT r25004+2-b463737826'
DISTRIB_TAINTS='no-all'

@mgiganto any comments?

I had a quick play with the GUI and it seems some weird interplay in that rats-nest of dependencies. Setting a dep to PSK and variants exclusively works fine, but adding ppsk: '0' makes it disappear...

This issue is serious and there's no reaction from the original commit author, please revert this faulty change.

Resolved in 05af14b25bc0fc2262416dcebf3360b11104198b


Disable all validations

Question
Please complete:

OS: Ubuntu 18.04
Python version import sys; print(sys.version):
3.7.3 (default, Apr  3 2019, 19:16:38)
[GCC 8.0.1 20180414 (experimental) [trunk revision 259383]]
Pydantic version import pydantic; print(pydantic.VERSION): 0.32.2

Hello anyone,
It possible to disable all validations of incoming data?
import pydantic

class MyModel(pydantic.BaseModel):
    class Config:
        validation = False

...

I am also very interested in this question, as in many cases in my code I know the values are correct and don't require validation. It would also be nice to have an API for initializing a model instance from known-valid inputs without needing to go through the various alias-lookups etc.
In general though I wouldn't want to disable the validation at the model level, but rather on a per-initialization basis. (So a separate classmethod for initializing from known-valid values would be nice.)
I think this is possible in one way or another; I'll see if I can make any progress.

@prostomarkeloff if you really do want "models" with validation disabled, you might try using vanilla dataclasses?

Okay, yes, I got this working (based on BaseModel.validate):
The following method could be added to your model subclass if you want to do 100% unvalidated assignment:
    @classmethod
    def unvalidated(__pydantic_cls__: "Type[Model]", **data: Any) -> "Model":
        for name, field in __pydantic_cls__.__fields__.items():
            try:
                data[name]
            except KeyError:
                if field.required:
                    raise TypeError(f"Missing required keyword argument {name!r}")
                else:
                    data[name] = field.default
        self = __pydantic_cls__.__new__(__pydantic_cls__)
        object.__setattr__(self, "__dict__", data)
        object.__setattr__(self, "__fields_set__", set(data.keys()))
        return self

I did some performance tests and for data-heavy models, and the performance difference is enormous:

Click to expand the benchmark script
from contextlib import contextmanager
import time
from datetime import datetime
from typing import List, Dict, Iterator

from pydantic import BaseModel

class DoubleNestedModel(BaseModel):
    number: int
    message: str

class SubDoubleNestedModel(DoubleNestedModel):
    timestamps: List[datetime]

class NestedModel(BaseModel):
    number: int
    message: str
    double_nested: DoubleNestedModel

class SubNestedModel(NestedModel):
    timestamps: List[datetime]

class Model(BaseModel):
    nested: List[Dict[str, NestedModel]]

class SubModel(Model):
    other_nested: Dict[str, List[NestedModel]]
    timestamps: List[datetime]

def get_sub_model(timestamp: datetime) -> SubModel:
    timestamps = [timestamp] * 5
    sub_double_nested = SubDoubleNestedModel(number=1, message="a", timestamps=timestamps)
    sub_nested = SubNestedModel(number=2, message="b", double_nested=sub_double_nested, timestamps=timestamps)

    nested = [{letter: sub_nested for letter in 'abcdefg'}]
    other_nested = {letter: [sub_nested] * 5 for letter in 'abcdefg'}
    return SubModel(nested=nested, other_nested=other_nested, timestamps=timestamps)

def get_sub_model_unvalidated(timestamp: datetime) -> SubModel:
    timestamps = [timestamp] * 5
    sub_double_nested = SubDoubleNestedModel.unvalidated(number=1, message="a", timestamps=timestamps)
    sub_nested = SubNestedModel.unvalidated(number=2, message="b", double_nested=sub_double_nested,
                                            timestamps=timestamps)

    nested = [{letter: sub_nested for letter in 'abcdefg'}]
    other_nested = {letter: [sub_nested] * 5 for letter in 'abcdefg'}
    return SubModel.unvalidated(nested=nested, other_nested=other_nested, timestamps=timestamps)

@contextmanager
def basic_profile(label: str) -> Iterator[None]:
    t0 = time.time()
    yield
    t1 = time.time()
    print(f"{label}: {(t1 - t0):,.3f}s")

def run():
    n_warmup_runs = 1000
    n_runs = 10000

    timestamp = datetime.utcnow()
    sub_model = get_sub_model(timestamp)
    unvalidated_sub_model = get_sub_model_unvalidated(timestamp)

    assert sub_model == unvalidated_sub_model

    for _ in range(n_warmup_runs):
        get_sub_model(timestamp)
        get_sub_model_unvalidated(timestamp)

    with basic_profile("validated"):
        for _ in range(n_runs):
            get_sub_model(timestamp)

    with basic_profile("unvalidated"):
        for _ in range(n_runs):
            get_sub_model_unvalidated(timestamp)

run()

The result:
validated: 2.918s
unvalidated: 0.083s

That's a 35x speedup. Not surprising, given that validators are called on each list element / dict value. But I think it may be worth using an API like this if you know it's safe.
Note: in my testing, removing the field checks and default value inference sped things up even further to an ~43x speedup, but I think having the field and default checks are worthwhile.
@samuelcolvin do you think there is any room for a method like this on the BaseModel class? (Maybe with a little more polish in case I'm mishandling some edge cases?) Or do you think this should be left to users to implement at their own risk?

This is what construct is for:
https://github.com/samuelcolvin/pydantic/blob/6cda388c7a1af29d17973f72dfebd98cff626988/pydantic/main.py#L417
It definitely needs documenting but I don't think we need a new method.
If it's signature needs changing to do what you want, we should do that pre v1 if possible.

@samuelcolvin I wasn't aware of that, that's nice.
It seems to me that 1) support for default values, and 2) not needing to manually specify the fields_set would go a long way toward making it more of a drop in replacement for __init__ when the input data is known-valid.
I think it would be easier to justify the refactor efforts if it was literally just a matter of adding .construct for the speed up, as opposed to the more potentially involved refactor currently required.

I would be in favor of a private method like _construct instead of what is currently called construct, and have construct use defaults if missing and set the fields_set based on the keyword arguments provided.
I would also understand if you didn't want to add a breaking API change this far into the 1.0 beta stuff. I would definitely be in favor of adding the above-described functionality though even if it needs to be a different method name or a private call. But I can always just define it on custom base class, so it's not the end of the world.

I am also very interested in this question, as in many cases in my code I know the values are correct and don't require validation. It would also be nice to have an API for initializing a model instance from known-valid inputs without needing to go through the various alias-lookups etc.
In general though I wouldn't want to disable the validation at the model level, but rather on a per-initialization basis. (So a separate classmethod for initializing from known-valid values would be nice.)
I think this is possible in one way or another; I'll see if I can make any progress.
@prostomarkeloff if you really do want "models" with validation completely disabled under all circumstances, you might try using vanilla dataclasses?

Thank you for answer! What about dataclasses? Firstly, i don't want to mix really different libraries in one project, secondly, dataclasses slower than pydantic. Some models in my project need this feature.

Okay, yes, I got this working (based on BaseModel.validate):
The following method could be added to your model subclass if you want to do 100% unvalidated assignment (beyond checking field names and falling back to default values):
    @classmethod
    def unvalidated(__pydantic_cls__: "Type[Model]", **data: Any) -> "Model":
        for name, field in __pydantic_cls__.__fields__.items():
            try:
                data[name]
            except KeyError:
                if field.required:
                    raise TypeError(f"Missing required keyword argument {name!r}")
                if field.default is None:
                    # deepcopy is quite slow on None
                    value = None
                else:
                    value = deepcopy(field.default)
                data[name] = value
        self = __pydantic_cls__.__new__(__pydantic_cls__)
        object.__setattr__(self, "__dict__", data)
        object.__setattr__(self, "__fields_set__", set(data.keys()))
        return self

I did some performance tests and for data-heavy models, and the performance difference is enormous:
Click to expand the benchmark script
The result:
validated: 2.918s
unvalidated: 0.083s

That's a 35x speedup. Not surprising, given that validators are called on each list element / dict value. But given the performance benefits I think it may be worth using an API like this if you know it's safe. Currently it's probably bit risky due to the lack of type checking, but it would be very easy to use a mypy plugin to set the signature in the same way currently done in #722 for the __init__ function. So I think this could be supported in a statically checked way. (Note: this would not call any custom validators or similar.)
Note: in my testing, removing the field checks and default value inference sped things up even further to an ~43x speedup, but I think having the field and default checks are worthwhile.
@samuelcolvin do you think there is any room for a method like this on the BaseModel class in pydantic proper? (Maybe with a little more polish in case I'm mishandling some edge cases?) Or do you think this should be left to users to implement at their own risk?

Awesome! I think it's what i need.

I would also understand if you didn't want to add a breaking API change this far into the 1.0 beta.

Hopefully this wouldn't be much of a breaking change, and it would be to an as-yet undocumented feature.

I would be in favor of a private method like _construct instead of what is currently called construct, and have construct use defaults if missing and set the fields_set based on the keyword arguments provided.

Please have a look at #898 which is my proposal for how to fix this.
If you think that it would be useful, it'll also need documentation of construct adding.

Here is a snipped how I use construct:
def enhance_data(request: Request, data: Data) -> EnhancedData:
    """Enhances data in-place by adding attributes.

    Args:
        request (Request): Request object
        data (Data): Data where attributes will be added to.
    """

    data = data.dict()

    data["request"] = request

    for alert in data["alerts"]:
        specific = set(alert["annotations"]) - set(data["common_annotations"])
        alert["specific_annotations"] = {k: alert["annotations"][k] for k in specific}

        specific = set(alert["labels"]) - set(data["common_labels"])
        alert["specific_labels"] = {k: alert["labels"][k] for k in specific}

    return EnhancedData.construct(**data)

Do give you an idea, @dashsatish

@dashsatish does this help? https://pydantic-docs.helpmanual.io/usage/models/#creating-models-without-validation

try this
from pydantic import fields as pydantic_field
pydantic_fields.ModelField.validate = lambda *args, **kwargs: (args[1], None)

Is there an equivalent to the construct method but for scenarios where you may be using parse_raw_as or parse_obj_as?

how to skip validation in v2.3.0?

How to skip validation in v2.3.0?

We have the SkipValidation (https://docs.pydantic.dev/latest/usage/validators/#special-types).

Hello guys, is there a way to disable validation for the entire BaseModel?
Would be nice to have some flag in ConfigDict that will disable validation by default.

For anyone else searching, I made a quick and dirty hack around this. This is NOT safe for production and is definitely not fully correct.
from pydantic.fields import FieldInfo
from pydantic_core import ArgsKwargs

class NoValidator:
    def validate_python(self, args_kwargs: ArgsKwargs, self_instance):
        model_fields = cast(dict[str, FieldInfo], self_instance.__pydantic_fields__)
        # print(model_fields)
        args = list(args_kwargs.args)
        mapping = dict(args_kwargs.kwargs) if args_kwargs.kwargs else dict()
        for field, info in model_fields.items():
            assert not info.init_var
            if not info.kw_only:
                mapping[field] = args.pop(0)
        for field, value in mapping.items():
            setattr(self_instance, field, value)

YourModel.__pydantic_validator__ = NoValidator()

try this
it will disable all validations and type converting in your project, and parse_obj(), from_orm(), BaseModel#__init__ will loss of ability to convert type, some functions such as fastapi json-deserialize for str to int , make sure you know what you are doing
from pydantic import fields as pydantic_field
pydantic_fields.ModelField.validate = lambda *args, **kwargs: (args[1], None)

Is pydantic_fields a typo (against pydantic_field) ?

If I am not wrong, available solutions in Pydantic are not doing a complete switch-off of validation operations. Something that can help to test things at runtime (think of a CLI program for example where each and every function is validated using Pydantic).

Comment https://github.com/pydantic/pydantic/issues/897#issuecomment-1760587892 means to deactive an existing model, right ?
Comment https://github.com/pydantic/pydantic/issues/897#issuecomment-1695492233 (i.e. using model_construct see: https://docs.pydantic.dev/latest/concepts/models/#creating-models-without-validation) means to do the same in a per-model basis
Comment https://docs.pydantic.dev/latest/api/functional_validators/#pydantic.functional_validators.SkipValidation is useful in Annotations

It would be interesting and useful to be able to just switch off everything that should happen with Pydantic. Is this possible while still not breaking basic functionality like checking field names and setting default values ?


feat(query): New types added

+ LogicalExpression
+ LogicalExpression implements HasSpan
+ LogicalExpression implements Expression
+ LogicalExpression.operator
+ LogicalExpression.left
+ LogicalExpression.right

+ LogicalExpressionAST
+ LogicalExpressionAST implements LogicalExpression
+ LogicalExpressionAST implements ASTNode
+ LogicalExpressionAST implements Expression
+ LogicalExpressionAST implements HasSpan

+ Parameter implements HasSpan

+ UnaryExpression
+ UnaryExpression implements HasSpan
+ UnaryExpression implements Expression
+ UnaryExpression.operator
+ UnaryExpression.value

+ UnaryExpressionAST
+ UnaryExpressionAST implements ASTNode
+ UnaryExpressionAST implements Expression
+ UnaryExpressionAST implements HasSpan
+ UnaryExpressionAST implements UnaryExpression

Codecov Report
Patch and project coverage have no change.

Comparison is base (3110490) 92.20% compared to head (0bbe345) 92.20%.

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #754   +/-   ##
=======================================
  Coverage   92.20%   92.20%
=======================================
  Files         203      203
  Lines       41465    41465
=======================================
  Hits        38233    38233
  Misses       3232     3232

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


missing label with circleMarker

Is Leaflet.label supposed to work with circleMarker and MarkerCluster on a geoJSON layer? When I set noHide=true, I get labels, but lots of markers that have no label. Works fine if I change from L.circleMarker to L.marker.

Could you set up a jsfiddle to demonstrate the issue.

will this do as a sample app
http://projx.integrated-mapping.com/MEG/index-test.html
look in http://projx.integrated-mapping.com/MEG/js/MEGmap-test.js function initMap at line 130
zoom in till the clusters spot up. you'll see many markers with no label. If you use  L.circleMarker instead of L.marker, it works properly with all marks being labelled.

it would be much more helpful to set up a minimal example. The current example has a bunch of other libraries that could be attributed to the issue. I would take the Leaflet.markercluter example and include Leaflet.label in it.


Drop-Down

Please use the form below, leaving the prefilled data to help us. Thank you.
Page link: Drop-Down
Document link: drop-down.md
My Issue/Suggestion
The dropdown button isnt a dropdown.
it just creates a popup that doesnt respect the DOM at all.
either fix the button, or make it clear in the documentation that this is just a popup creator.

Hi @jasonteunissen ,
I spoked with Takuma about your comments at length. Owing partially to your feedback, and the feedback of other users, this widget is going to undergo comprehensive changes in the future. So while the widget and its docs will stay as they are for the moment, they will be changed drastically in the future due (in part) to your feedback.
Thank you for improving Mendix,
Connor


compile(*):  support go 1.22

What problem does this PR solve?

Issue Number: close #10647
What is changed and how it works?
support building CDC using golang version 1.22
Check List
Tests

Unit test
Integration test
Manual test (add detailed scripts or steps below)
No code

Questions
Will it cause performance regression or break compatibility?
Do you need to update user documentation, design documentation or monitoring documentation?
Release note
`None`.

/retest

/retest


Website not matching main repo

Describe the bug
The website https://circuitverse.org/simulator seems to be running on a different version than the main branch on this repo. I'm working on a PR to fix issue #198. I don't know what changes to make since it might lead to merge conflict. When I compared this to the currently running website, it had some changes.
To Reproduce
Steps to reproduce the behavior:

Go to Current Website
Click on Combinational Analysis.
Generate a table.
Now run the main branch of this repo locally.
Go to Combinational Analysis.
Generate table.

Expected behavior
The UI for both, this repo and the current website were expected to be the same, but there were some changes.
Screenshots

Device Information [optional]:

OS: Windows
Browser: Brave
Version: 1.6.101

Are you working on this issue? (Yes/No)
Yes.

Closing this because I accidentally submitted twice. Oops.


Fix to the new pull request button

Fixing an issue where the new pull request button was pointing to an incorrect repository.
To reproduce:

Create a fresh new gitea
Register as a new user, admin or otherwise.
Create a new organization.
Go to the organizations dashboard,
Create a repository under that organization and initilize it
Return to the organization dashboard and select the newly created repository
Click the green new pull request icon

Expected Result:
You are taken to a branch-to-branch merge with the repository
Actual result:
You are taken to a non-existent fork that assumes to exist that leads to a 404

Removed.

Diff still shows a newline added, you might want to remove it :)

please squash the commits and give it an appropriate comment


Rename file and block provisioner pod with proper yaml extension.

Signed-off-by: Humble Chirammal<EMAIL_ADDRESS>

@childsb Can you please merge this pr? Thanks!

/lgtm


DM-33247: Build and push to Google Artifact Registry.

The project id must be in the image name for the Jenkins docker push to work correctly, so it seems that we have to build the image twice.

Unfortunately in this case it's not the tag portion (after the :) that we need multiple versions of; we already do that, and the plugin handles that fine.  It's the image name (before the :) that needs an additional /-separated component specific to one registry.  (And that's because the plugin appears to assume that the registry URL cannot contain that component but can only have a hostname.)


Alexa AWS Cloudfllare timeout

The problem
Hello together,
I have Alexa configured via AWS & have been using the Cloudflared addon for some time now. But since a few days (round about after updating to HA 2023.3 & Cloudflared 5.1.5) the AWS Calls to my HA instance time out 90%  of the time.
When using Cloudflare DNS in proxy-mode I also get the timeout error. It seems like AWS & Cloudflare have some trouble working together currently.
The problem seems not be repeatable for everybody using the same setup, sine I found this post: https://community.simon42.com/t/probleme-mit-alexa-geraete-nur-teilweise-ansprechbar/20672
here also, a thread in the HA forum: https://community.home-assistant.io/t/alexa-aws-cloudfllare-timeout/701837
As a workaround, I now configured nginx & Cloudflare without proxy to get everything back up & running.
What version of Cloudflared has the issue?
5.1.5
What was the last working version of Cloudflared?
No response
What type of installation are you running?
Home Assistant OS
Add-on YAML Configuration
No response
Anything in the logs that might be useful for us?
No response
Steps to reproduce the issue
n/n
Additional information
No response

Unfortunately I have the same problem. When I restart the Cloudflare addon, access via Alexa works for a few seconds. As soon as I go into the Alexa app, I can only switch one device and then nothing works. The Lambda function spits out a positive debug at the beginning, as soon as I send a voice command via Alexa or via the app, the devices no longer respond... then the Lambda function spits out a failed log.😞
What version of Cloudflared has the issue?
5.1.5
What was the last working version of Cloudflared?
No response
What type of installation are you running?
Home Assistant Supervised Installed (2024.3)
Add-on YAML Configuration
No response
Anything in the logs that might be useful for us?
No response
Steps to reproduce the issue
n/n
Additional information
No response

I don't use Alexa, so I can only share a few ideas, but unfortunately I can't really help.
Also, it should be said that it is less a problem with the add-on and more with AWS and/or Cloudflare (or the Cloudflare tunnel).
In the past, I had also played around with the Alexa integration via AWS/Lambda.
What you can try to narrow down the error:

Cloudflare part: Check the firewall log in the Cloudflare dashboard (open your Domain configuration, search the left menu for Security > Events, if I remember right I had to tweak with the security settings to get it working in the first place)
Cloudflared tunnel part: Add "--loglevel=debug" as additional run_parameters to check the cloudflared tunnel log for errors related to Alexa (see run_parameters documentation)
AWS part: I am not sure but maybe it is possible to get more connection logs to dig deeper into it on AWS side?
Home Assistant part: The error message from the screenshot indicates an authentication error, I am no longer sure how this is integrated with HA but maybe there is something in the log here too. However, the fact that the command is executed correctly according to your statement speaks against this.

But as I said, I'm just poking around in the dark, sorry!


elan trackpad can't use?

i'm korean sorry for my bad english.
i'm elan trackpad user.
why elan trackpad cannot be used absolute pointing.
is that hardware problem? or else?
Cannot fix it if it's hardware problem?

AbsoluteTouch uses the Synaptics API to read the touchpad input. As far as I know Elan does not have an API, so this program won't work on Elan touchpads. Sorry.

i'm a student in korea.
i start to learn programming from 2017.3
i'm planning to program absolutetouch on elan trackpad.
is that impossible to develop?
api or hardware problem?

It's definitely possible, but you would need to write a driver for it that runs in the kernel. You can take a look at the Linux driver for Elan touchpads, but getting it to work on Windows will be a difficult task.

Thank you for comment!
You are genius!
thanks for my study.

I read events from /dev/input/eventX in Linux and successfully got the absolute position.I am wondering if there is any universal method to read events from Win32 API since Windows10 support multi-touch gestures for both Syn and Elan.

Not sure, I'm not familiar with the Windows kernel. I think https://msdn.microsoft.com/en-us/library/windows/desktop/ms645543(v=vs.85).aspx would be the closest thing? Don't know if it you can get raw touchpad input from it though.

Thanks.It helps.


PM Sundry APIs detects "com.topjohnwu.magisk" after V3.0.4 Updates

When i installed V2.3.2 and Magisk module, it couldn't detects anything. but I deleted the module, and installed V3.0.6 -> Some apps started detecting something, and PM Sundry APIs is showing me "com.topjohnwu.magisk" is Found...
Applist Detector image

LSPosed Log
12-12 22:17:34.705  1199  1614 W BroadcastQueue: Background execution not allowed: receiving Intent { act=android.intent.action.PACKAGE_REPLACED dat=package:com.samsung.android.mdx.kit flg=0x4000010 (has extras) } to com.topjohnwu.magisk/.core.Receiver

Title is wrong -> I installed "V3.0.6"


Make scikit-mdr a Python package on PyPi

Added setup.py
Still need to finish up setup.py and upload the package to PyPi.


ci: add tags to AWS instances

The new terraform runners support an extended lists of tags to get a greater precision on the stats we can extract from AWS cost center.

(rebased)


CH06 acorr_ljungbox

When using the same code as the book for this test:
from statsmodels.stats.diagnostic import acorr_ljungbox
lbvalue, pvalue = acorr_ljungbox(residuals, np.arange(1, 11, 1))
print(pvalue)
This is what is returned (a string with no values):
lb_pvalue
Instead of a tuple, statsmodels acorr_ljungbox returns a dataframe now instead. The lbvalue is in one column while the pvalues on the other (on statsmodels 0.14.0).

I was going to report the same issue but see this has already been done. For those without much familiarity with pandas who have run into the same error, here's what works:
pvalue = acorr_ljungbox(residuals, np.arange(1, 11, 1))['lb_pvalue']

The Ljung-Box test statistics themselves are not used so there is no real need for any sort of unpacking.

Another solution is
lb_df= acorr_ljungbox(residuals, np.arange(1, 11, 1))


Display #downloads for each package

We should harvest the number of downloads per package + display it on the app.

API information from the NPM Registry for download counts can be found here: https://github.com/npm/registry/blob/master/docs/download-counts.md
Important notes:

The bulk query feature does not support scoped packages (these must be queried one-by-one)
The data is per-package, not per-package-version (the UI should be clear about that)

Open questions:

Show download counts over what period? A month? A week? Multiple (graph)?
Should this be displayed in search results (see note above about bulk query ability), or only in detail page?

@RomainMuller We do want to display this in both search & the detail page, so this will need to be on the catalog.json as well as metadata.json
For the time period, I imagine supporting all three (day, week, month) would be useful, and we could support sorts for all three. I'll check in with UXD folks to see how we can support multiple download periods on the UI

Answers:

#downloads per week/month (whatever is easier to implement)
Should  be displayed in search results + package page

Since there might be a difference in the #downloads we display and the #downloads on npm registry, we should save the date in which we harvested this number and display it. For example: '#downloads/w: 2000 (updated on: Sep 12, 2021)'
It also means we should think of how to keep harvesting this information on a weekly/monthly basis, regardless if a new version was published or not.

An update from our latest UX sessions. It seems like we will not display the exact date on which the number of downloads were updated. Instead we will display a generic tooltip for all packages which will explain that the number of downloads is harvested from npm registry from time to time (means it's not necessarily the up to date).
BTW, post GA, we may start harvesting these numbers from additional repositories as well (Think about Maven, PyPI etc.) and perhaps aggregate it to one number.


Add product pages to home page navigation

📝 Changed routes:

/authentication
/

(view full size)
(view full size)

Commit 08c40779c7b62d4c5fb6a78b3ded4bba4cbe18f8 (https://thirdweb-d38jg49vg-thirdweb.vercel.app).


 However, it's not realistic diff, as it excludes the staged changes. Does anyone know of a way to get the diff of the "zero-eth" commit?
TODOs:

[ ] need to improve diff display (either hide it or learn to include staged
changes) - google it!
[ ] we also need to test for all the flags we allow to supply to commit w/ amend
[x] the failing test passes now :)

Hi @asfaltboy!
You should be optimistic here. Like nobody amends its first commit. So try with what we usually do and fallback and repair only if the git command fails.
The parent of the inital commit is 4b825dc642cb6eb9a060e54bf8d69288fbee4904. So you can use
git diff 4b825dc642cb6eb9a060e54bf8d69288fbee4904

for include unstaged and
git diff 4b825dc642cb6eb9a060e54bf8d69288fbee4904  --cached

otherwise if iirc the options we have here.

@kaste how do you get the parent of an initial commit? How is that even possible, is there a way to get that 0-state commit?

I have it from GitGUI source: https://github.com/git/git/blob/master/git-gui/git-gui.sh#L1423-L1434
This sha is currently a constant. It is though safer to do what gitGUI does. In the console
>>> git = GitCommand()
>>> git.view = view
>>> git.git('mktree', stdin='')
'4b825dc642cb6eb9a060e54bf8d69288fbee4904\n'

Look at the empty check -> https://github.com/git/git/blob/master/git-gui/git-gui.sh#L1431

Basically, a factoring like this would be dope
try:
	diff = self.do_diff(..., parent='HEAD^')
except ...:
	parent = self.git('mktree', stdin='').strip()
	diff = self.do_diff(..., parent=parent)

That is awesome! I was missing that an empty tree is a hash constant, cool stuff!
Refs:

https://f-o.org.uk/2017/empty-trees-in-git.html
https://stackoverflow.com/a/9766506/484127

I will try to play with this in the weekend


Redrafts of section on Tasking Manager

Proposed redrafts of the section of Tasking Manager.

Hi @geomantic , sorry about the delay. Just catching up with things now. I've merged your changes into this staging site, but I've changed it from a draft so that the changes are visible here on the site - http://nick-tallguy.github.io/en/coordination/tasking-manager-project-admin/
I've just quickly looked it over, and there are still a couple of formatting errors that need altering.
It's unlikely that I will have time to work on this for a while - there are translations sitting on Transifex for me to work on as well. If you're able to do more commits, I will add them in as quickly as I can.
Thanks for our work on this
Nick

Hi @Nick-Tallguy , thanks for the feedback. I'll work on it as time permits. Best,
Steven

Hi @geomantic and @Nick-Tallguy,
I just saw the thread about this document, had a look at it and fixed the formatting issues Nick mentioned: headings look as they should be, the note at the beginning appears as a note and I redesigned the link to the OSM wiki so that it does no longer extend beyond the column on smaller screen sizes.
Best Regards
Michael


suggestion:  dynamic RTL

this plugin for obsidian is a good example of my suggestion for dynamic  RTL in logseq.

There's a custom.js wrapper that enables dynamic RTL, would be nice to have it included by default.
https://github.com/hkgnp/logseq-rtlblocks-plugin

Must say that I highly object to the notion of dynamic RTL.
The only reason I chose to use this plug in is becase it does not have dynamic RTL.
I write a lot of technical notes, and many times I need to start a sentence with a technical term in English.
I can't do that with dynamic RTL, since this flips the block to be an LTR block.
The direction of a text cannot be recognized only from the first letter of a sentence, and doing that puts an unreasonable constraint on writing.


Echoing theme mods

When echoing theme mods (get_theme_mod( $name, $default )), I get

Expected next thing to be an escaping function (see Codex for 'Data Validation'), not 'get_theme_mod'

Now, this is kinda odd, since all themes must pass the Theme Check, and if you don't specify the sanitization callback (sanitize_callback) when setting up a theme mod, you won't pass the check (from the plugin).
So if we are already sanitizing the select/input, or whatever modification we stored to the database, isn't it assumed that the output of that same theme mod should be safe to echo even without escaping it?

Sanitization and escaping serve different purposes. You sanitize input and escape output according to the context where it is echoed. A string may very well be sanitized but when used in the context of an HTML attribute it may also very well be unsafe if not escaped. Best to never assume a value will be safe and escape every time you echo any data.

Ok, thanks for the explanation :)


Dynamic port node

Thanks for awesome node editor, Dmitry! I played with him a few evenings and delighted with the architect and opportunities for decor it.
I added the signals for add and remove ports. Maybe you want to add this to your repository. Video: https://youtu.be/KUt4qlTLrW0
There is a problem when removing connections. I didn't know how correct remove connections from the FlowScene.

Could you please rebase onto the latest master and squash your commits?

Did this, Dmitry.
I seem to make a mistake with the rebase and squash branches. I do not how to fix it in this PR, sorry.

@paceholder ,  if @signmotion will refuse to fulfill your requirements, please find my pull request with his work squashed and rebased.

Hi, great feature, I've been using it in my fork.
I noticed that my application would crash when loading scenes with dynamic port nodes with an out-of-range exception on the input/output connection vectors in the nodestates.
I created a new PR with fix https://github.com/paceholder/nodeeditor/pull/268 for anyone who might need this feature (since the original PR has not been accepted yet)

I played a bit with this branch and the @willys0 fix. The main point is Node::onPortAdded() and Node::onPortRemoved() just resize the underlying connection vector, so they kinda works when the last port is added or removed, but if I have 5 ports connected and remove connection at index 2 the layout breaks. So I guess at least signal portRemoved() e and onPortRemoved should have the index of the connection port removed to correctly remove the right port.

Thanks for your contribution. I've implemented the feature in the latest master.
The current code correctly handles the changed connection order is using somehow similar approach to data modifications as in Qt's QAbstractItemModel class used for trees and tables.


[Bug] Color hints may display twice at view edges with line wrap

With `"editor.wordWrap": "on"`, the color hints (inline color decorators) may be double-displayed near the wrapped view edges.
----
Version: 1.75.1
Commit: 441438abd1ac652551dbe4d408dfcec8a499b8bf
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:109.0) Gecko/20100101 Firefox/111.0
Embedder: github.dev

Can you share a screenshot?

https://github.com/MasterInQuestion/Markup/raw/0ac01f2d24d886977fb55da27a719813835a3961/Verbose.htm

This bug has been fixed in the latest release of VS Code Insiders!
@MasterInQuestion, you can help us out by commenting /verified if things are now working as expected.
If things still don't seem right, please ensure you're on version 822ad2de026bf4cf858d17237937a3ca743d1b22 of Insiders (today's or later - you can use Help: About in the command palette to check), and leave a comment letting us know what isn't working as expected.
Happy Coding!

/verified

    Basically alright.
    But the early wrapping may be optimized. (see near line 6 "#bf3989", "#ff7b72")


Implement a database backed State.

This pull requests implements an optimized state backed by an LMDB database.
There are currently a couple of major limitations:

The code relies on the python gc to close databases. This leaks file descriptors under pypy, causing the test suite to fail.
Various performance optimisations are needed.

I'm planning to remove the original optimized state soon rather than continuing to maintain it.
Cute Animal Picture

Codecov Report

Merging #360 (cafa42d) into master (8bf3a41) will decrease coverage by 0.00%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master     #360      +/-   ##
==========================================
- Coverage   95.49%   95.49%   -0.01%
==========================================
  Files          46       46
  Lines        2422     2419       -3
==========================================
- Hits         2313     2310       -3
  Misses        109      109

Flag
Coverage Δ

unittests
95.49% <100.00%> (-0.01%)
:arrow_down:

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

Impacted Files
Coverage Δ

src/ethereum/frontier/rlp.py
100.00% <100.00%> (ø)

src/ethereum/frontier/trie.py
97.63% <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 8bf3a41...cafa42d. Read the comment docs.


Servlet json

Implement json functionality with hard-coded comments.

Not sure if I mentioned this before. It's usually good to attach a screenshot for UI change


Open with and Open file when set as default application

The ability to open files via document type, set as default application and context menu "Open with" in Windows and Mac.

Hi @dakotalightning !
Sorry for the delayed answer ¯_(ツ)_/¯
Yes it's a good idea, I don't know how to do this for now, I'll see, but it's definitely planned ! :)
Thank you for contributing !


#import <React/RCTEventEmitter.h> not found

Hey @maystrenkoYurii , I am facing the same issue. Are you able to resolve this issue?

What is your RN version? 61? Does your Podfile conform to required?

same issues in RN 0.59.9

same issue using expo 35.0.0

use --> cd ios --> pod install

Same issue with RN 0.59.10
i tried pod install with no success

pod install so it works in react-native 0.60+, sorry

pod install so it works in react-native 0.60+, sorry

Yep, it probably work for RN 0.60+, but the major issues related here are for RN 0.59.x

Same issue after upgrading RN 0.61.3

RN0.61.4 same issue!!!

I m solved it!

Libraries→PushNotificationIOS.xcodeproj→build setting→Search Paths→Header Search Paths:
$(SRCROOT)/../../../../ios/Pods/Hearders/Public

menu(Product)→Scheme→Edit Scheme:
[+]→Pods→React

clean→build

Typo in your path for "Headers" but it worked for me. Thanks.


repository: version_suffix doesn't exist, so don't check it

File "/mnt/media/code/Urcheon/Urcheon/Repository.py", line 391, in getPakFile
elif version_suffix:
^^^^^^^^^^^^^^
UnboundLocalError: cannot access local variable 'version_suffix' where it is not associated with a value
Fixes this runtime error

version_suffix exists in some situations but with a missing fallback, see:

https://github.com/DaemonEngine/Urcheon/pull/65


ChatScript

Topics, Implementation, Integration.

Topics: [TO DISCUSS]

Lecture Schedule
Stuff information and roles in department
Contact info (telephone, email, address)
Basic technical issues (password reset, VPN)
Applications
Study
Information for candidates
Basic information about Wroclaw
Other topics from yebood FAQ


Liquibase website is unavailable

Search first

[X] I searched and no similar issues were found

Description
As of this morning UK time, the liquibase.org website is unavailable.
Over HTTPS, I get a certificate mismatch error (the cert is for *.wpengine.com, wpengine.com). Over HTTP, I get a "Site is not available" message from WP Engine.
This is unfortunately now blocking our database migrations, as the XML parser is trying to download the XSD from liquibase.org.
Steps To Reproduce
Visit liquibase.org in a web browser.
Expected/Desired Behavior
The liquibase.org website loads successfully, with a valid TLS certificate, and database migrations are able to be executed successfully.
Liquibase Version
No response
Database Vendor & Version
No response
Liquibase Integration
No response
Liquibase Extensions
No response
OS and/or Infrastructure Type/Provider
No response
Additional Context
No response
Are you willing to submit a PR?

[ ] I'm willing to submit a PR (Thank you!)

Same here 👀

Just remove s from https.

😭😭😭

same thing, that needs to be fixed

panic do fix

my production is down thx

Same here 👀

I tried to contact wpengine via chat and mail. They only respond to the website owner if contacted via their portal.

@nvoxland or @wwillard7800  Can you please help, our production deployments are failing due to XSD dns paths is no longer valid:
http://www.liquibase.org/xml/ns/dbchangelog/dbchangelog-3.9.xsd

Same here :eyes:

Same here Is there any workaround ? How can we contact the support ?

Same here ^_^

You can upgrade your dependency version (i have upgraded upto 4.16.0). it help me. There are schemas in artifact

de your dependency version (i have upgraded upto 4.16.0). it help me. There are schemas in artifact
Hey can you tell me how you have used it cause when i upgrade my version it couldn't find my property file . It was able to find the path earlier of my property file can you tell me the plugin configuration in pom.xml

You can upgrade your dependency version (i have upgraded upto 4.16.0). it help me. There are schemas in artifact

Hey can you tell me how you have used it cause when i upgrade my version it couldn't find my property file . It was able to find the path earlier of my property file can you tell me the plugin configuration in pom.xml

@jonasvoelcker
Hey how can i change the schemalocation to local directory ?

The liquibase.org site is back up and the XSDs should be available again. Could you let us know if things are working for you again?

It doesn't work :/

I can confirm that it works. Use a browser with private or incognito mode or a browser that you have not opened the website today.

The liquibase.org site is back up and the XSDs should be available. Could you let us know if things are working for you again?

Still getting an error for http://www.liquibase.org/xml/ns/dbchangelog/dbchangelog-latest.xsd because of the 301 return code - should switch to https it seems :smiling_face_with_tear:

The liquibase.org site is back up and the XSDs should be available. Could you let us know if things are working for you again?

I can curl the XSD from the command line but our web application is returning a 403 error when attempting to fetch the XSD. I believe this might be due to the cert change and our previously signed cert in the java keystore not aligning with the new certificate issued to the site.

Yes - you will need to use https instead of http.

Issue continues to be perceived with 301 redirect errors:

It looks like the website is now up and accessible, but there seems to now be a redirect in place from HTTP to HTTPS, which breaks older versions of Liquibase. Can the redirect be reverted? We have old versions in the wild that we can't (easily) update, and they're now broken.
liquibase.exception.ChangeLogParseException: liquibase.exception.SetupException: Error parsing line 2 column 35 of liquibase-boomi-bus.xml: s4s-elt-character: Non-whitespace characters are not allowed in schema elements other than 'xs:appinfo' and 'xs:documentation'. Saw '301 Moved Permanently'.
        at liquibase.parser.core.xml.AbstractChangeLogParser.parse(AbstractChangeLogParser.java:25)
        at liquibase.Liquibase.getDatabaseChangeLog(Liquibase.java:216)
        at liquibase.Liquibase.update(Liquibase.java:189)
        at liquibase.Liquibase.update(Liquibase.java:178)
        at liquibase.integration.commandline.Main.doMigration(Main.java:1639)
        at liquibase.integration.commandline.Main.run(Main.java:303)
        at liquibase.integration.commandline.Main.main(Main.java:159)

Fun fact: Even with HTTPS enabled I'm getting an error - it sounds like the XSD itself has changed? :thinking:
liquibase.exception.ChangeLogParseException: Error parsing line 3 column 137 of META-INF/changelog.xml: cvc-elt.1.a: Cannot find the declaration of element 'databaseChangeLog'

I'll investigate further - maybe my fault

Fun fact: Even with HTTPS enabled I'm getting an error - it sounds like the XSD itself has changed? 🤔
liquibase.exception.ChangeLogParseException: Error parsing line 3 column 137 of META-INF/changelog.xml: cvc-elt.1.a: Cannot find the declaration of element 'databaseChangeLog'
at org.liquibase//liquibase.parser.core.xml.XMLChangeLogSAXParser.parseToNode(XMLChangeLogSAXParser.java:113)
	at org.liquibase//liquibase.parser.core.xml.AbstractChangeLogParser.parse(AbstractChangeLogParser.java:15)
	at org.liquibase//liquibase.Liquibase.getDatabaseChangeLog(Liquibase.java:369)
	at org.liquibase//liquibase.Liquibase$16.run(Liquibase.java:1982)
	at org.liquibase//liquibase.Scope.lambda$child$0(Scope.java:180)
	at org.liquibase//liquibase.Scope.child(Scope.java:189)
	at org.liquibase//liquibase.Scope.child(Scope.java:179)
	at org.liquibase//liquibase.Scope.child(Scope.java:158)
	at org.liquibase//liquibase.Liquibase.runInScope(Liquibase.java:2405)
	at org.liquibase//liquibase.Liquibase.listUnrunChangeSets(Liquibase.java:1978)

I'll investigate further - maybe my fault
edit: ℹ Using liquibase-core 4.8.0

Hi, have you added https only to this link? :  https://www.liquibase.org/xml/ns/dbchangelog/dbchangelog-latest.xsd
I say this because I got your error if I add https to the xmlns properties urls of the databasechangelog element.
Only this url : https://www.liquibase.org/xml/ns/dbchangelog/dbchangelog-latest.xsd, others with http its okey for me.
regards!

We're looking into the http to https redirect with the goal of removing the redirect. I'll share an update with you when I hear back.

@kevin-atx We are getting 403 errors either with http / https as well
Caused by: java.io.IOException: Server returned HTTP response code: 403 for URL: https://www.liquibase.org/xml/ns/dbchangelog/dbchangelog-3.4.xsd
at sun.net.www.protocol.http.HttpURLConnection.getInputStream0 (HttpURLConnection.java:1902)
at sun.net.www.protocol.http.HttpURLConnection.getInputStream (HttpURLConnection.java:1500)
at sun.net.www.protocol.https.HttpsURLConnectionImpl.getInputStream (HttpsURLConnectionImpl.java:268)
at com.sun.org.apache.xerces.internal.impl.XMLEntityManager.setupCurrentEntity (XMLEntityManager.java:648)
at com.sun.org.apache.xerces.internal.impl.XMLVersionDetector.determineDocVersion (XMLVersionDetector.java:148)
at com.sun.org.apache.xerces.internal.impl.xs.opti.SchemaParsingConfig.parse (SchemaParsingConfig.java:582)

Thank you @dvt-blip-ui :pray:
Only updating the link to the changeog xsd seems to be the solution:
<databaseChangeLog xmlns="http://www.liquibase.org/xml/ns/dbchangelog" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
  xsi:schemaLocation="http://www.liquibase.org/xml/ns/dbchangelog
                      https://www.liquibase.org/xml/ns/dbchangelog/dbchangelog-latest.xsd">

(line breaks for readability)

I just heard from the team that the automatic XSD redirect from http to https has been removed. Caching might still be an issue for people (clearing the cache or time should address that). Please let me know if this change helps the situation for those that still have trouble accessing the XSDs.

another way to avoid this problem also in future is to switch to a YAML definition

Hi everyone! Does anyone know if we have any ETA for resolving this issue?

Hi All,  this issue has been resolved, but you may need to clear your browser cache.  To confirm, do the following:

Open a private browsing window
Open developer tools -> network
Navigate to your desired XSD using http
You should see a 200 OK instead of a 301 Redirect

Example: http://www.liquibase.org/xml/ns/dbchangelog/dbchangelog-latest.xsd

I can retrieve XSD files with the browser, but builds in my CI pipeline using the liquibase-maven-plugin are failing on a year old changeset - the error still occurs:
Failed to read schema document 'http://www.liquibase.org/xml/ns/dbchangelog/dbchangelog-latest.xsd', because 1) could not find the document; 2) the document could not be read; 3) the root element of the document is not <xsd:schema>.: Server returned HTTP response code: 403 for URL: http://www.liquibase.org/xml/ns/dbchangelog/dbchangelog-latest.xsd -> [Help 1]

@jnewton03  You can use this https://github.com/ojas-krishnaprasad/Liquibase, mvn liquibase:update

For us this worked:
<databaseChangeLog xmlns="http://www.liquibase.org/xml/ns/dbchangelog"
                   xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
                   xsi:schemaLocation="http://www.liquibase.org/xml/ns/dbchangelog https://www.liquibase.org/xml/ns/dbchangelog/dbchangelog-latest.xsd">

@ojas-krishnaprasad  thank you SO MUCH.  Very helpful.  I worked with support at our hosting provider and tweaked the redirects to not require HTTPS for anything after www.liquibase.org/xml/
We were able to successfully run your project now.  We also tried updating the maven-compiler-plugin and liquibase-maven-plugin to the latest available versions and that was also successful.
Can you all try your projects again and let me know if it's still failing?

Still failing, a 403 error on the URL  https://www.liquibase.org/xml/ns/dbchangelog/dbchangelog-3.5.xsd

Still failing, a 403 error on the URL https://www.liquibase.org/xml/ns/dbchangelog/dbchangelog-3.5.xsd

Hi!  I updated the changelog in the sample project @ojas-krishnaprasad provided and it was successful:
<databaseChangeLog
        xmlns="http://www.liquibase.org/xml/ns/dbchangelog"
        xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
        xsi:schemaLocation="http://www.liquibase.org/xml/ns/dbchangelog https://www.liquibase.org/xml/ns/dbchangelog/dbchangelog-3.5.xsd">

Would you mind sharing a sample changelog that fails for you?

Still failing, a 403 error on the URL https://www.liquibase.org/xml/ns/dbchangelog/dbchangelog-3.5.xsd

@azfdgdasfgdagf what Liquibase version are you using?

This is with liquibase 3.4.1, the header in a changelog that fails seems identical to yours.  It's maven building a jar.

<include file="indexing_schema_1.0.xml" relativeToChangelogFile="true"/>

full error is
[ERROR] Failed to execute goal org.liquibase:liquibase-maven-plugin:3.4.1:updateSQL (Generate SQL Server Schema) on project ovitas-indexing: Error setting up or running Liquibase: Error parsing line 4 column 133 of C:/(path removed)/master.changelog.xml: schema_reference.4: Failed to read schema document 'https://www.liquibase.org/xml/ns/dbchangelog/dbchangelog-3.5.xsd', because 1) could not find the document; 2) the document could not be read; 3) the root element of the document is not xsd:schema.: Server returned HTTP response code: 403 for URL: https://www.liquibase.org/xml/ns/dbchangelog/dbchangelog-3.5.xsd -> [Help 1]

Thanks, @azfdgdasfgdagf . Since you are on 3.4.x, you'll need to keep your XSD version as 3.4.xsd or lower.
We'll see about what is causing 3.4.1 to get the 403 error, but the reason it's going out to the network in the first place is becuase 3.5 is not packaged in your version of liquibase (because it didn't exist when 3.4.1 was released). So even when we do fix the network issue, it's still setting you up for problems where the XSD is suggesting that some XML attributes are valid when they were not actually valid in 3.4.1.
By going to the 3.4.xsd, Liquibase will find it packaged in the application and use that without having to go out to the network and hit the 403 error.

I'm still seeing the same error using liquibase-maven-plugin v. 3.4.1. Changing to https still results in the same error. Heres the changelog:
<databaseChangeLog
        xmlns="http://www.liquibase.org/xml/ns/dbchangelog"
        xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
        xmlns:ext="http://www.liquibase.org/xml/ns/dbchangelog-ext"
        xmlns:pro="http://www.liquibase.org/xml/ns/pro"
        xsi:schemaLocation="
          http://www.liquibase.org/xml/ns/dbchangelog http://www.liquibase.org/xml/ns/dbchangelog/dbchangelog-latest.xsd
          http://www.liquibase.org/xml/ns/dbchangelog-ext http://www.liquibase.org/xml/ns/dbchangelog/dbchangelog-ext.xsd
          http://www.liquibase.org/xml/ns/pro http://www.liquibase.org/xml/ns/pro/liquibase-pro-latest.xsd">

[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time:  8.018 s
[INFO] Finished at: 2023-06-06T20:53:45-04:00
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.liquibase:liquibase-maven-plugin:3.4.1:update (default) on project end-user-sync-db: Error setting up or running Liquibase: liquibase.exception.SetupException: Error parsing line 11 column 70 of db/changelogs/my_changelog.xml: schema_reference.4: Failed to read schema document 'https://www.liquibase.org/xml/ns/dbchangelog/dbchangelog-latest.xsd', because 1) could not find the document; 2) the document could not be read; 3) the root element of the document is not <xsd:schema>.: Server returned HTTP response code: 403 for URL: https://www.liquibase.org/xml/ns/dbchangelog/dbchangelog-latest.xsd -> [Help 1]

What changes you made it to work. Still i am facing same issue

@ojas-krishnaprasad thank you SO MUCH. Very helpful. I worked with support at our hosting provider and tweaked the redirects to not require HTTPS for anything after www.liquibase.org/xml/
We were able to successfully run your project now. We also tried updating the maven-compiler-plugin and liquibase-maven-plugin to the latest available versions and that was also successful.
Can you all try your projects again and let me know if it's still failing?

What changes you made it to work. Still i am facing same issue

@kjthorpe18 If you are on 3.4.1, the -latest.xsd won't work for you. The overall logic liquibase should be doing is:

If the referenced xsd can be found bundled with the liquibase build, use that
If not, try to download it (this is normally not what you want anyway, and later versions of liquibase disable this from even being tried by default)

Step 2 is having a problem on our server we're looking into, but you should be able to stop it at step 1 by only referencing xsd filese that are bundled in your version of Liquibase. So for 3.4.1, that will be dbchangelog-3.4.xsd or earlier. The dbchangelog-latest.xsd file was only introduced around 4.12, so if you are on any versions before 4.12 then requesting dbchangelog-latest.xsd will still be trying to go out to the network.
If you change your reference to http://www.liquibase.org/xml/ns/dbchangelog/dbchangelog-3.4.xsd does it work?
Also: if you are have a reference to a liquibase-pro xsd file with 3.4.1 you'll also be hitting the "fall back to the network" step, since there was no support for any pro functionality in 3.4.1. Removing that xsd reference will help too.

Found on another forum and was able to reproduce the issue in Postman.

Create a GET request to https://www.liquibase.org/xml/ns/dbchangelog/dbchangelog-3.1.xsd and execute. We content of XSD is returned and status is 200.
Add User-Agent: Java/1.8.0_251 request header. Now the response is 403 and I can see an error message:

Error 1010
Ray ID: 7d36b3e76dca9555 • 2023-06-07 06:05:19 UTC
Access denied
What happened?
The owner of this website (www.liquibase.org) has banned your access based on your browser's signature (7d36b3e76dca9555-ua21).

same here, how getting the following exception:
Caused by: java.io.IOException: Server returned HTTP response code: 403 for URL: https://liquibase.org/xml/ns/dbchangelog/dbchangelog-3.8.xsd
	at sun.net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:1902)
	at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1500)
	at sun.net.www.protocol.https.HttpsURLConnectionImpl.getInputStream(HttpsURLConnectionImpl.java:268)
	at com.sun.org.apache.xerces.internal.impl.XMLEntityManager.setupCurrentEntity(XMLEntityManager.java:648)
	at com.sun.org.apache.xerces.internal.impl.XMLVersionDetector.determineDocVersion(XMLVersionDetector.java:148)
	at com.sun.org.apache.xerces.internal.impl.xs.opti.SchemaParsingConfig.parse(SchemaParsingConfig.java:582)
	...

same here getting 403 when we use liquibase in a maven build.  Last time this happened back in 2022 it wass due to something rejecting the java in the user-agent (we can access via the browser fine).  Guessing when everything has came back up certain settings (user-agent permissions) have not been re-applied.

We're using liquibase v 3.* and the solution was to switch from https to http. This will use XSD files bundled in liquibase library.
https://github.com/liquibase/liquibase/blob/3.3.x/liquibase-core/src/main/java/liquibase/parser/core/xml/StandardNamespaceDetails.java

Hey, same error here using Azure App Services to run my application:
Caused by: java.io.IOException: Server returned HTTP response code: 403 for URL: https://www.liquibase.org/xml/ns/dbchangelog/dbchangelog-latest.xsd
	at sun.net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:1902) ~[?:1.8.0_345]
	at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1500) ~[?:1.8.0_345]
	at sun.net.www.protocol.https.HttpsURLConnectionImpl.getInputStream(HttpsURLConnectionImpl.java:268) ~[?:1.8.0_345]
	at org.apache.xerces.impl.XMLEntityManager.setupCurrentEntity(Unknown Source) ~[xercesImpl-2.12.0.jar:2.12.0]
	at org.apache.xerces.impl.XMLVersionDetector.determineDocVersion(Unknown Source) ~[xercesImpl-2.12.0.jar:2.12.0]
	at org.apache.xerces.impl.xs.opti.SchemaParsingConfig.parse(Unknown Source) ~[xercesImpl-2.12.0.jar:?]
	at org.apache.xerces.impl.xs.opti.SchemaParsingConfig.parse(Unknown Source) ~[xercesImpl-2.12.0.jar:?]
	at org.apache.xerces.impl.xs.opti.SchemaDOMParser.parse(Unknown Source) ~[xercesImpl-2.12.0.jar:?]

On my local environment I can download the xsd

Hi, same error here.
<databaseChangeLog     xmlns="http://www.liquibase.org/xml/ns/dbchangelog"     xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"     xsi:schemaLocation="http://www.liquibase.org/xml/ns/dbchangelog http://www.liquibase.org/xml/ns/dbchangelog/dbchangelog-3.4.xsd"> ....
Error Log:
{"log":":: JHipster    :: Running Spring Boot 1.4.1.RELEASE ::\n","stream":"stdout","time":"2023-06-07T08:30:03.746367277Z"} ... {"log":"2023-06-07 10:30:17.330  WARN 7 --- [           main] liquibase                                : schema_reference.4: lettura del documento di schema \"http://www.liquibase.org/xml/ns/dbchangelog/dbchangelog-3.5.xsd\" non riuscita perché 1) non è stato possibile trovare il documento; 2) non è stato possibile leggere il documento; 3) l'elemento radice del documento non è \u003cxsd:schema\u003e.\n","stream":"stdout","time":"2023-06-07T08:30:17.330899683Z"}

I think the error is that Cloudflare restrict access with e.g. User-Agent: Java/1.8.0_251

https://forum.liquibase.org/t/tomcat-not-starting-getting-403-error-from-liquibase/8311
Here is the ungoing discussion on forum.liquibase.org

Thanks all.  Great find.  Working with WPEngine support right now and will post an update shortly.

Flow that wasn't working for me previously is now successful. Thank you!

It is fixed for me also

Changing the xsd to a version specific (dbchangelog-3.4.xsd) one worked for me, thanks!

Now everything works! Thank you!!

OK, so now everything should be back up and running.  Here's what happened:

liquibase.org is hosted on WPEngine on their legacy network.
Yesterday (6/6) there was an outage with our site
The solution from WPEngine was to update our DNS to use their Advanced Network Offering
This brought the site back online, but broke HTTP redirects for XSDs and enabled CloudFlare security which blocks Java agents < version 10.
Today we reverted the DNS change back to the legacy network.  I've tested access to the XSDs via browser, curl, and liqubase-maven-plugin and all seem to be working.

Thank you all for being patient with us.  Apologies for the outage.  We are looking at ways to mitigate this type of thing in the future.

Closing this issue, but feel free to re-open if ya'll see more problems.

Hi team,
It appears the issue reported in this thread has resurfaced. As of today, we are still encountering errors related to certificate mismatches and unavailable XSD schemas, which are blocking our database migrations. The issue persists despite clearing cache, switching browsers, and upgrading Liquibase versions.
Could this issue be reopened for further investigation?
Thanks for your attention to this matter.

Same here...

You guys can try https://github.com/liquibase/liquibase/issues/6364#issuecomment-2376625135, worked for me.

@sheik61 @ptpu @thangnq1001 This was, indeed, a DNS issue.  It has since been resolved.  Please reply if you are still having issues.


profile.d script failing on rebuild

Rebuilding sprint boot app with sample java build pack results in this error -
/buildpacks/sh.packs.samples.buildpack.java/0.0.1/bin/build: line 35: /launch/sh.packs.samples.buildpack.java/jdk/profile.d/jdk.sh: No such file or directory

We tracked this isssue down to a bug in the sample jdk buildpack.
The jdk buildpack was only creating the jdk layer directory if it would be different to the previous build's layer. However, it was always sourcing a profile script from that same directory.
We are submitting a PR to fix this issue in the sample jdk buildpack


Add Budgie as an option for Pop!_OS and other Distros

I am thinking I might break this off into a separate project called Deacon - so that for users that JUST want to install a global menu into a Gnome based distros or possibly other DEs can have that and the choice of either running xfce4-panel or the Budgie-panel. I suspect the budgie-panel will largely be limited to Gnome DE from hardcoded menu options to logout, restart or turn off the system. Xfce4-panel always has the option to change those out based on the underlying system.
Do you have any thoughts @RedBearAK? I am thinking about Deacon being a system tray app that Sorun could install in a similar manner as to Kinto, that would give users the option to switch btwn the default DE, xfce4-panel or the budgie-panel.

Also I have no idea why the default ubuntubudgie backports repo pulled in that logo.. I will be removing that and using my bishop logo in place of it.

@rbreaves
That actually sounds very interesting. Just make sure there is a robust and simple mechanism to help the user get back to the default panel if something goes wrong. There will be many of us who want to play with that who won't have even the slightest idea how to reverse the changes, and that's very scary. My preference would be to have a simple command that can be run in terminal (must be installed in a standard path location like /usr/bin, obviously) that can be used to either switch between the bars or revert to the default for the DE, or restore everything and uninstall the switcher.
A tray icon to access this can be a real convenience, but we would be talking about situations where one version of the bar (like GNOME's default top bar) might not even have tray icons enabled, or something might be going wrong and the bar disappears, etc. So by all means have a tray icon, but it must be backed up by a memorable and easy to understand shell command that does all the same things, so the user can feel very comfortable messing with such a fundamental part of the UI of their DE.
I've been encountering remarkable instability with the GNOME shell lately, it seems to crash every time I unlock the system and it usually takes Firefox down with it, and I haven't been able to track down exactly what extension might be causing the instability. It's not a big deal unless I happen to be composing something in Firefox when it crashes, since the tab manager will just reload everything each time and the shell just restarts itself with little fuss, but it got me thinking that if there were a way to just try out the global menu and xfce4-panel portion of Sorun without messing with other parts of the Sorun script, that would be pretty neat to try. As long as I can be really comfortable that it would reliably revert things to the original state.
I'd still have to find replacements for some of the tools I have in the GNOME top bar with extensions, but if it gave me a more stable menu bar with global menu that could be easily replicated in other DEs, that might be a very worthwhile tradeoff.
I say go for it. Just focus on making it safe to use (for normal people, not just gurus who know how to troubleshoot) and robust to recover from the changes at every stage.

That is a good point about system tray crowding and yea, Deacon would need a full on GUI app kinda like Kinto, although I wouldn't be displaying a terminal in the case of Deacon just the actions a user might want to perform and maybe some fields that would allow them to tweak certain aspects of spacing, font style, etc that would effect the global menu's look. Editing the gtk.css is a bit much imo. I find myself wasting a lot of time having to google who to do X, Y or Z in terms of tweaking the global menu's look.
Of course I can document a lot on how to theme it properly, but again needs to have a GUI imo. I may very well consider task tray merging of Deacon and Kinto. I don't want to be expanding the scope of Kinto though, so it'll be interesting to redesign the Kinto system tray to pull in another python script into itself as I assume that would be how I would do it. It would probably be best to make Deacon an optional install of both Sorun and Kinto really. I can see users wanting Deacon but may only have an interest in Kinto or Sorun and not both.

... so it'll be interesting to redesign the Kinto system tray to pull in another python script into itself as I assume that would be how I would do it.

Yeah that's what I was thinking.
What I was thinking is that, while the Kinto icon is brilliant, you should consider a more generic symbolic icon capable of representing both projects, and possibly others. Then it won't matter whether the user installs Kinto, Deacon, or both. The tray icon will just detect whatever happens to be installed and present the relevant options.
Rather than injecting new submenu options it may make more sense to just have a single option for each installed project to open a dialog to change settings of the separate projects. Different preferences dialogs for each, that just open GUIs that are also accessible via the main system menu, like how the Kinto GUI app is listed as an application.
Think about doing it in the simplest possible way that makes it easier for you to develop and maintain the code. The current code for the tray app is actually quite cumbersome, and extremely redundant with the Kinto GUI app. Ideally the tray app should just be issuing commands to the GUI app through command-line options, and all the actual code for what to do should just be in the GUI app. That would make the tray app a lot simpler to maintain and adapt to incorporate an additional package like Deacon. And then Deacon would just come with its own GUI app that also understands commands passed to it from the tray app.
This turned out to meander between a couple of different paradigms as I was thinking, but hopefully some of it made sense.
Side note: The Kinto GUI app is one of a few apps I've encountered that Plank won't let me add permanently to the dock. That needs to be fixed at some point. But I don't know exactly what causes that issue. Maybe there's some specific attribute that the application needs to have in order for Plank to insert it permanently in the dock.

I wasn't aware of that plank icon issue but I will try to remember to take a look at that. And yea.. the Kinto tray probably makes more sense than one for deacon - and there's probably not much reason to see it all the time - assuming it is highly stable. Would be a bit easier too to just have a single menu option that links to the Deacon settings as you suggest vs creating/injecting additional cascading menu options.
I'm also remembering why I didn't do Budgie first in Pop!_OS - Budgie can only show for 1 monitor.. whereas xfce4-panel can appear for however many monitors you actually have. All in all when I implement a Budgie-panel option for Gnome via Deacon I should be mindful of that and actually detect multiple monitor setups and have an option of running both Budgie-panel and xfce4-panel to fill the void. The system tray icons will likely be tied to Budgie-panel only though as I don't think I can have them on both panels at once.
This is actually what I am running on a physical desktop right now, Ubuntu Budgie 21.04 w/ xfce4-panel & the vala-appmenu on it too and it works without issue so far. I really do and prefer Pop!_OS's default font though and think it is likely the best support Ubuntu based distro today. I think I will likely start gearing more of my efforts and resources towards it and Manjaro Budgie/XFCE/Gnome. I like Ubuntu Budgie, but I am not really seeing it having the developer or creator user base that I feel like my applications/scripts would attract the most.
Also detecting DPI would be a very good thing too and suggesting xrandr parameters that would a user quickly resize their desktop to a size appropriate for them - if under x11. Finding a way to simplify the scaling of individual applications would be very good too.. off the top of my head I am imagine an app shortcut on the dock and when launched it is just a window with a big box in it for you to drag and drop an app on to so it can resize it for you, regardless of the type of app it is it could add in the right env variables to it.
Another open would be a shortcut that when pressed could detect your current app, close it, apply the env variables such as GDK SCALING to the .desktop file and re-launch the app.

I get the impression now that I've used it a bit that Pop!_OS support is mainly focused on making sure newer hardware works well, with less focus on maintaining compatibility with older hardware. Possibly because the company behind it created Pop to use on their own Linux computer products that they sell.
I've had many issues trying to run Pop on older MacBook/MacBook Pros (kernel panics booting the installer). I didn't experience these issues running Ubuntu, elementary, Fedora or OpenSUSE on the same hardware. So at this point I am far less excited about Pop!_OS than I was hoping to be. The worst thing I've found is that the functionality of GNOME's Mac-style application-centric task switching (the "Switch applications" keyboard shortcut) is broken on Pop, just like Budgie, and I don't expect it to be fixed. It's been broken since at least Pop!_OS 20.04 LTS.
It's super frustrating since the same feature works perfectly on the version of Ubuntu those distros are based on, and on Fedora (GNOME). I also expect it to work on Manjaro GNOME, but haven't tested yet.
But Pop!_OS is certainly popular and getting more popular, so... makes sense to give it some attention.
I've actually had an excellent experience using Fedora 34 on the same old MacBook Pro where I get the Pop!_OS kernel panic. Fedora even puts a proper icon and name on the Option-key boot picker screen instead of showing the generic "EFI Boot" displayed by most Linux installs. Not sure if Ubuntu does that, but Pop certainly doesn't (I filed a bug report / feature request about that). In general the amount of user-friendliness and professional UI polish in Fedora has surprised me.
I haven't had much experience yet with High DPI displays, but that utility sounds like something a lot of people would find useful, for all the apps that still don't properly support scaling.

Hmmm.. well installing Pop!_OS baremetal is not something I have done on any Apple products, but that is useful to know. Tbh though I have little interest in running Linux on my macbook baremetal, but I am triple booting macOS, Windows and Ubuntu Budgie atm. I spend most of my time in Windows 10 though as my laptop actually seems to run best under Windows 10 - has the least amount of heat and fan noise despite all of the configuring I have ever done under linux to perfect the fan control stuff under it, although Ubuntu Budgie is not as bad as KDE Neon in that regard.
But yea.. Pop!_OS is likely best ran on actual Pop! hardware, not too unlike the macOS experience being best on Apple hardware. I am not sure what the most stable distro and OS experience may be for general hardware. Would be interesting to try and measure that but I am not sure where one would begin.
I do need to spend more time with Fedora - I know that Kinto could install better on it and avoid needing to disabling SELinux.

On Fedora I've been using the branch from Kinto PR #446 with the solution provided by @prosac, it works fine and bypasses the SELinux issue. I've been meaning to try and splice his changes into a PR that doesn't have conflicts with the current master installer file. It's fairly simple, just a few lines, I just haven't gotten around to it.
 Didn't work quite as well on the 2008 MacBookPro4,1 though. Wouldn't be surprised if the NVidia card on the MBP is at the root of that issue.

Hmmmm well that is interesting, that Fedora seems to support MBP's better. Think better than stock Ubuntu as well?

I wonder if PR 446 is the one that veered off into installer changes

You're thinking of Kinto PR #455. 446 is super simple. Much simpler than what I came up with to try and fix the Fedora install.
https://github.com/rbreaves/kinto/pull/446/files
Frankly that would be one of the best PRs to take the time to merge. Most of the other open PRs on the list are just sort of fluff or nice additions to kinto.py, but 446 would actually fix installing on Fedora. That would serve a lot of users.

Hmmmm well that is interesting, that Fedora seems to support MBP's better. Think better than stock Ubuntu as well?

Tested Ubuntu 21.04 and Fedora 34, just for sleep functionality, to see what would happen:
Ubuntu on MacBook3,1: Sleeps and wakes when using "Suspend" from the menu, but fails to come back when putting it to sleep by closing the lid. Screen stays black, system seems completely non-responsive. When closing the lid the backlight stays on for a while and then finally goes out and the light on front starts to pulse.
Fedora on MacBook3,1: Sleeps and wakes fine from either the menu item or by closing the lid. When closing the lid the backlight goes off immediately and the light on front starts pulsing, just like if it was running macOS. Opening the lid wakes it back up.
Both distros on the MacBookPro4,1 fail to resume.
The main distros that have given me problems with the Macs (two MBPs, one white MB, two 2007 iMacs) that I have available are Manjaro (tends to boot immediately to a black screen with no further activity) and Pop!_OS, which has had kernel panics on multiple releases on multiple Macs.
Fedora certainly seems to have slightly better default support than Ubuntu for at least the white 2007 MacBook. But I think they are about even in general, with Pop!_OS really being the odd man out and the least compatible with the Mac hardware I've tried to run it on.
I should get out one of the old iMacs and try Fedora. The other distros like elementary OS and Solus that I've tried on those worked great but came back from suspend with a nasty graphics corruption issue that required a reboot. It was a strange one, like the screen still worked but every other column of pixels was color-inverted. Would be interesting to see if Fedora has better compatibility with resuming that old ATI(?) graphics hardware.

@rbreaves
I've learned a couple of things since this discussion, about the WhiteSur GTK theme. It's actually better than I even realized at the time.
I had always been installing it from gnome-look.org with ocs-url, but turns out it has a very robust install script with many different options. It's only there if you download the latest version from the GitHub. I started an issue over there regarding a couple of spots where I was encountering fonts that were too small (top bar and system prompts), and the dev showed me a new "-HD" option that fixed it.
It also has options for some different looks for Nautilus. So now what I would suggest if you're wanting to try out WhiteSur is this:

Get it directly from the GitHub page, and download the ZIP from the green Code button because the latest "release" is already old and doesn't yet have the "-HD" install option.

https://github.com/vinceliuice/WhiteSur-gtk-theme

If you have a 1080p or higher resolution display, I'd suggest running installing with this command:

./install.sh -HD -N mojave

The installer will install both the dark and light versions, with transparent and solid variants. The "mojave" option changes the header bar in Nautilus to look quite a bit better.
There are also a number of handy options in the separate tweaks.sh script for connecting the theme to Flatpaks and Snaps, and a Firefox theme (although with the Firefox 89 UI update I am finding that it doesn't really need a special theme installed to blend in much better than it used to).
And WhiteSur is also available for KDE. I wonder if it would be possible to integrate it into Sorun as an option that would allow KDE applications to look a little better on GTK desktops.

To my displeasure pop!_os does not properly support btrfs. Hard for me to take it seriously now imo.

And on that note, I just went ahead and wiped Neon off my secondary drive and replaced it with Fedora 34. If you go with the automatic partitioning option the default FS since v33 is btrfs.
Looking forward to something like Deacon being available to test on distros like Fedora and Ubuntu, or any other distro that hasn’t managed to break GNOME task switching. I haven’t tested yet but I’m assuming that Arch/Manjaro and OpenSUSE have no reason to break GNOME the way Budgie and Pop!_OS do.

To my displeasure pop!_os does not properly support btrfs. Hard for me to take it seriously now imo.

Is this due to pop!_os not using btfs in the default install and requiring some workarounds to set up encryption if you want to partition manually, or something else? for both Luks-under-LVM and btrfs, creating sub-volumes seems to be a satisfactory workaround to get Pop behaving properly.


Property 'hex' does not exist on type 'ColorValue'.

Version
typescript: 4.1.2
mui-color: 2.0.0-beta.2
@mui/material: 5.0.4
react: 17.0.2
@emotion/react: 11.5.0
@emotion/styled: 11.3.0
Issue
When trying to access to the hex value of a ColorValue inside of ColorPicker onChange event handler, typescript throw Property 'hex' does not exist on type 'ColorValue'.
Same issue for all the properties of ColorValue object.
Screenshot

Workaround
<ColorPicker
    onChange={(e) => {
        const color = e as ColorObject;
        console.log(color.hex);
    }}
/>

Should the onChange handler argument type be ColorObject instead of ColorValue ?

I don't think this is a bug. You can also enter text in the color picker to get a color. The argument type used to be Color though instead of ColorValue

Ok, I think I got it. And yes, it would be better to have an argument of type Color, instead of ColorValue. In this way we should be able to get the color as any format.


we have added a calculator project script

Group A members that's Karim , Michael , Damilola , Leslie and Derrick

Good work.
Your project is simple but functional and efficient.
Also the code is concise and clear. Your use of comments to explain blocks of the code is commendable.
Nice work overall.

However for future projects, do not compress all your code into one giant commit. Your commits should be small and incremental.


Proposal: adding eslint to the project

Hi, I was wondering how you feel about using eslint in this project?
I realize that this request may not be wanted, and would of course be perfectly fine with a rejection in case of different plans/preferences.
I'm under the impression, however, that a linter is an improvement for most projects and would like to suggest the settings coming with this PR for this project as a starting point.
To sum up the changes that would come from this PR:

Add lint as a script to package.json, so that by running yarn lint the source code can be linted.
Add eslint and plugins to the devDependencies.
Make some used dependencies explicit: react, react-helmet and typography are imported, but not mentioned directly as dependencies.
Add a missing import of toggleInfoScreen to layouts/index.js.
Replace usages of Object.assign with the ... operator.
Use the Airbnb settings for eslint

On a personal note:
Thanks for this nice starter in any case!

Deploy preview ready!
Built with commit 7be4bd2ba2ce8a6e2417decdea5e5e9a4c22eace
https://deploy-preview-7--jovial-mclean-88c629.netlify.com

Hi Jakob,
I cherry-picked your second commit,
https://github.com/greglobinski/gatsby-styled-blog-starter/commits/master
but the first one I have to reject. It harms the style of the starter's typography.  https://deploy-preview-7--jovial-mclean-88c629.netlify.com/
About the dependencies: react is a dependency of gatsby so I do not have to list it explicitly, the same with react-helmet which is a dependency of gatsby-plugin-react-helmet. Regarding Typography, the starter does not use it. Firstly I had thought that I will  but then I changed the mind. Yes, I have to clean the code.
The ESlint? It's on the todo list. I will add it, but rather stay with double quotes.

Hi Greg,
thanks for the swift reply and action on this!
Glad to hear at least some of the changes appeared to be useful.


Reviced api.py for non-air broadening parameter

Added in Mdbhitran class;

Definition of extra-params so that one can select whether or not to include broadening parameters(e.g. h2, he...) when downloading from Hitran
Definition of each broadening parameter when it exists in downloaded hitran database

Thanks! @KoHosokawa

Currently, extra_params is None or "all". So, False or True is adequate? Or do you plan some extension in future for instance, "all", "H2O", "CO" etc?

I have the following error. Can you check it?

>>> import numpy as np
>>> from exojax.utils.grids import wavenumber_grid
>>> from exojax.spec import api
>>> nus,wav,res=wavenumber_grid(6910,6990,100000,unit='cm-1',xsmode="premodit")
xsmode =  premodit
xsmode assumes ESLOG in wavenumber space: mode=premodit
>>> mdb = api.MdbHitran("CO",nus,extra_params="all")
Using /home/kawahara/exojax/downloads__can_be_deleted/CO

Data is fetched from http://hitran.org

BEGIN DOWNLOAD: CO_1
  65536 bytes written to /home/kawahara/exojax/downloads__can_be_deleted/CO/CO_1.data
  65536 bytes written to /home/kawahara/exojax/downloads__can_be_deleted/CO/CO_1.data
  65536 bytes written to /home/kawahara/exojax/downloads__can_be_deleted/CO/CO_1.data
  65536 bytes written to /home/kawahara/exojax/downloads__can_be_deleted/CO/CO_1.data
  65536 bytes written to /home/kawahara/exojax/downloads__can_be_deleted/CO/CO_1.data
  65536 bytes written to /home/kawahara/exojax/downloads__can_be_deleted/CO/CO_1.data
  65536 bytes written to /home/kawahara/exojax/downloads__can_be_deleted/CO/CO_1.data
  65536 bytes written to /home/kawahara/exojax/downloads__can_be_deleted/CO/CO_1.data
  65536 bytes written to /home/kawahara/exojax/downloads__can_be_deleted/CO/CO_1.data
Header written to /home/kawahara/exojax/downloads__can_be_deleted/CO/CO_1.header
END DOWNLOAD
                     Lines parsed: 1344
PROCESSED

Data is fetched from http://hitran.org

BEGIN DOWNLOAD: CO_2
  65536 bytes written to /home/kawahara/exojax/downloads__can_be_deleted/CO/CO_2.data
  65536 bytes written to /home/kawahara/exojax/downloads__can_be_deleted/CO/CO_2.data
  65536 bytes written to /home/kawahara/exojax/downloads__can_be_deleted/CO/CO_2.data
  65536 bytes written to /home/kawahara/exojax/downloads__can_be_deleted/CO/CO_2.data
  65536 bytes written to /home/kawahara/exojax/downloads__can_be_deleted/CO/CO_2.data
  65536 bytes written to /home/kawahara/exojax/downloads__can_be_deleted/CO/CO_2.data
  65536 bytes written to /home/kawahara/exojax/downloads__can_be_deleted/CO/CO_2.data
Header written to /home/kawahara/exojax/downloads__can_be_deleted/CO/CO_2.header
END DOWNLOAD
                     Lines parsed: 1042
PROCESSED

Data is fetched from http://hitran.org

BEGIN DOWNLOAD: CO_3
  65536 bytes written to /home/kawahara/exojax/downloads__can_be_deleted/CO/CO_3.data
  65536 bytes written to /home/kawahara/exojax/downloads__can_be_deleted/CO/CO_3.data
  65536 bytes written to /home/kawahara/exojax/downloads__can_be_deleted/CO/CO_3.data
  65536 bytes written to /home/kawahara/exojax/downloads__can_be_deleted/CO/CO_3.data
  65536 bytes written to /home/kawahara/exojax/downloads__can_be_deleted/CO/CO_3.data
  65536 bytes written to /home/kawahara/exojax/downloads__can_be_deleted/CO/CO_3.data
Header written to /home/kawahara/exojax/downloads__can_be_deleted/CO/CO_3.header
END DOWNLOAD
                     Lines parsed: 920
PROCESSED

Data is fetched from http://hitran.org

BEGIN DOWNLOAD: CO_4
  65536 bytes written to /home/kawahara/exojax/downloads__can_be_deleted/CO/CO_4.data
  65536 bytes written to /home/kawahara/exojax/downloads__can_be_deleted/CO/CO_4.data
  65536 bytes written to /home/kawahara/exojax/downloads__can_be_deleted/CO/CO_4.data
  65536 bytes written to /home/kawahara/exojax/downloads__can_be_deleted/CO/CO_4.data
  65536 bytes written to /home/kawahara/exojax/downloads__can_be_deleted/CO/CO_4.data
Header written to /home/kawahara/exojax/downloads__can_be_deleted/CO/CO_4.header
END DOWNLOAD
                     Lines parsed: 800
PROCESSED

Data is fetched from http://hitran.org

BEGIN DOWNLOAD: CO_5
  65536 bytes written to /home/kawahara/exojax/downloads__can_be_deleted/CO/CO_5.data
  65536 bytes written to /home/kawahara/exojax/downloads__can_be_deleted/CO/CO_5.data
  65536 bytes written to /home/kawahara/exojax/downloads__can_be_deleted/CO/CO_5.data
  65536 bytes written to /home/kawahara/exojax/downloads__can_be_deleted/CO/CO_5.data
  65536 bytes written to /home/kawahara/exojax/downloads__can_be_deleted/CO/CO_5.data
Header written to /home/kawahara/exojax/downloads__can_be_deleted/CO/CO_5.header
END DOWNLOAD
                     Lines parsed: 674
PROCESSED

Data is fetched from http://hitran.org

BEGIN DOWNLOAD: CO_6
  65536 bytes written to /home/kawahara/exojax/downloads__can_be_deleted/CO/CO_6.data
  65536 bytes written to /home/kawahara/exojax/downloads__can_be_deleted/CO/CO_6.data
  65536 bytes written to /home/kawahara/exojax/downloads__can_be_deleted/CO/CO_6.data
  65536 bytes written to /home/kawahara/exojax/downloads__can_be_deleted/CO/CO_6.data
Header written to /home/kawahara/exojax/downloads__can_be_deleted/CO/CO_6.header
END DOWNLOAD
                     Lines parsed: 601
PROCESSED
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/home/kawahara/exojax/src/exojax/spec/api.py", line 762, in __init__
    self.activate(df)
  File "/home/kawahara/exojax/src/exojax/spec/api.py", line 806, in activate
    self.gQT, self.T_gQT = hitranapi.make_partition_function_grid_hitran(
  File "/home/kawahara/exojax/src/exojax/spec/hitranapi.py", line 56, in make_partition_function_grid_hitran
    len_max = np.max(len_idx)
  File "<__array_function__ internals>", line 5, in amax
  File "/home/kawahara/anaconda3/lib/python3.8/site-packages/numpy/core/fromnumeric.py", line 2733, in amax
    return _wrapreduction(a, np.maximum, 'max', axis, None, out,
  File "/home/kawahara/anaconda3/lib/python3.8/site-packages/numpy/core/fromnumeric.py", line 87, in _wrapreduction
    return ufunc.reduce(obj, axis, dtype, out, **passkwargs)
ValueError: zero-size array to reduction operation maximum which has no identity
>>>

This was the error when there is no line in the wavelength range. Thanks!

I'll note it about 1st question as a log, just in case
I wrote so because the radis/hitranapi/download_and_parse command which mdbhitran refers uses "extra_params" to switch whether to include the non-air broadening parameter for downloading data or not.
I thought it would be fewer codes to add that to not change the parameter name. so we can define other parameter name and rename them.
And since the above radis script defines "all" or "none", we need to revise radis/hitranapi to define other situations or use the HAPI command directly.
Thanks for reviewing & merging it!

Thank you! I am sorry for the delay in reviewing. I have confirmed that with the current develop branch, I can get non-air broadening parameters for HITRAN/CO, CO2, and H2S.


Rename extras/init.py to be correct.

extras/__init__.py was named extras/__init.py__. This was preventing the bin_parser_extras module from being found!
This prevented compare_yaml and make_skeleton from working and, as a result, it also stopped extras/test.sh from running.
Reference: openjournals/joss-reviews#766.

I was apparently not entirely awake when I committed this. Thank you for spotting it.


how can I set a service binding via this action?

what it says on the tin.

In the UI: https://dash.cloudflare.com/?to=/:account/pages/view/:pages-project/settings/functions


cURL Error "Option 20056"

Hello !
I have an error using this library. I want to sign in my users with their Google account. I'm using JavaScript client-side to get an id_token, and then check his validity with PHP. Here's the PHP code where I'm using the google-api-php-client:
<?php
	$client = new Google_Client();
	$client->setAuthConfig('google-oauth-credentials.json');

	$accessToken = $client->fetchAccessTokenWithAuthCode($id_token);
	$client->setAccessToken($accessToken);
?>

I'm using the latest version of the Google App Engine Launcher, and the google-api-php-client is installed with composer.
The error is "Option 20056 is not supported by this curl implementation."
And option 20056 is CURLOPT_PROGRESSFUNCTION.
The directive google_app_engine.enable_curl_lite is set to "1" in php.ini
Do you have any idea how I can solve this?
Thank you.

I solved it by changing the directive google_app_engine.enable_curl_lite to "0" in php.ini.
But now I've got an other error "No system CA bundle could be found in any of the the common system locations."
I tried to add the line
$client->setHttpClient(
	new GuzzleHttp\Client([ 'verify' => false ])
);

but that would be too easy, and I got a 400 Bad Request from the Google API.
I'll try to get one of these "CA bundle", should solve my problem.
But it looks like this problem isn't related to the google-api-php-client anymore, so, bye.


Issue/20 mvp national

Pull Request
Description
Make National Forecast, by adding up all the GSP forecasts
Fixes #20
How Has This Been Tested?
Add unittests

[ ] Yes

If your changes affect data processing, have you plotted any changes? i.e. have you done a quick sanity check?

[ ] Yes

Checklist:

[ ] My code follows OCF's coding style guidelines
[ ] I have performed a self-review of my own code
[ ] I have made corresponding changes to the documentation
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] I have checked my code and corrected any misspellings

Codecov Report

Merging #21 (7d76c23) into main (ddfeeef) will decrease coverage by 0.34%.
The diff coverage is 90.69%.

@@            Coverage Diff             @@
##             main      #21      +/-   ##
==========================================
- Coverage   94.46%   94.11%   -0.35%
==========================================
  Files          11       13       +2
  Lines         325      357      +32
==========================================
+ Hits          307      336      +29
- Misses         18       21       +3

Impacted Files
Coverage Δ

nowcasting_forecast/database/national.py
88.00% <88.00%> (ø)

nowcasting_forecast/models/nwp_solar_simple.py
94.73% <93.75%> (+0.61%)
:arrow_up:

nowcasting_forecast/__init__.py
100.00% <100.00%> (ø)

nowcasting_forecast/app.py
88.88% <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 ba01bfd...7d76c23. Read the comment docs.