When will CoreOS be supported ?

Hey, thanks for your interest in Flocker. CoreOS presents a few challenges, insofar as handling mount namespaces for containers from a container is tricky. This is not currently high priority for us, but feedback such as yours is how we make product decisions to prioritize features, so consider the request taken as input.
Out of interest, what is your use-case for Flocker on CoreOS? Which applications or databases would you be interested in running on it?

Thanks @lukemarsden, basically looking at zfs backup of docker container data,
i.e Database, HDFS, Kafka without relying on replication

@charlesa101 Cool - thanks for the feedback. Is there a reason you want to use ZFS specifically?

based on the MongoDB example tutorial, where container + data was migrated, i thought this could be applicable to all other containers withe CoreOS as well.
I want to have a more effective backup strategy for disaster recovery and not have to rely on data replication alone

Yes, Flocker definitely works with any app that writes to a filesystem. Thanks for the feedback - we will work this into our roadmap. If you sign up for updates in the footer of our website at https://clusterhq.com/ you'll get an email when new features such as CoreOS support and backup/restore functionality are announced. Meanwhile, you can try out Flocker for stateful container migration on Ubuntu or CentOS. Thanks!

+1 for prioritizing CoreOS support

Hey folks, we are happy to announce this working  here: https://clusterhq.com/2015/09/01/flocker-runs-on-coreos/
Check it out and please send feedback!
cc @tobiasmcnulty @charlesa101

+1 for CoreOS cloud agnostic support

@rimusz hey!
In principle Flocker supports any of these: https://docs.clusterhq.com/en/1.8.0/introduction/flocker-supports.html and you could use the experimental Flocker containers that we run on CoreOS on any of those infrastructures.
Which other infrastructures are you interested in supporting? We are currently working on adding GCE and Ceph as options.
@wallnerryan and @davidoliverSP2 are working on documenting the experimental containerized Flocker.

@lukemarsden GCE support sounds good to me :+1:
What about bare-metal based CoreOS installs?

@rimusz cool, will bump GCE priority up a notch!
Regarding bare metal:
The problem with the ZFS driver is that it doesn't give you failover, so if you lose a node you wouldn't be able to recover the data that was on it. Would that be a problem for your use case?
Failover/HA use cases on bare metal could be enabled by the Ceph integration we're working on (unfinished project! testing needed! cc @robhaswell). Or there are other commercial "software defined storage" solutions that could work, like ScaleIO, Hedvig or ConvergeIO, just to name a few. I'm not sure if any of these support CoreOS but they do have Flocker drivers. Let me know if you're interested and I can find out from them! (They all wrote Flocker drivers).

@lukemarsden ok, cool regarding GCE :+1:
If bare-metal node gets lost and data was already replicated to others nodes, I do not see it as big problem.
Failover/HA if that is based on the Ceph it is fine as I would prefer to have the open source version.
Commercial versions are more for enterprise companies :)
Have you looked into http://minio.io/ or http://basho.com/products/riak-s2/ for object storage?

Great, thanks for the feedback @rimusz!
You can sign up for our newsletter here to get updates when we release Ceph support in officially supported version of Flocker https://clusterhq.com/newsletter/
Or if you want to test a more experimental version of the Ceph backend then @robhaswell can help out :)

Is there an implementation on coreos for digitalocean?

@mateeyow we havent run it on digital ocean but we do work with installing on coreos via and you can also use try and use our containers to install

@wallnerryan
The only solution at the moment for CoreOS is to use AWS as the persistant data storage?
How about latency with this cloud based storage. IF one would save database for example

@maxa4e you can run coreos and use it with any of our backends. Backends supported include a number of different solutions from SDS, Enterprise Arrays and cloud storage. more details here https://docs.clusterhq.com/en/latest/supported/index.html#supported-infrastructure-storage
Yes, using cloud storage does mean some latency but this is usually defined by the cloud storage provider with different levels of performance and network throughput. In the case for AWS, there are provisioned IOPs, general SSD, provisioned IOPs SSD and magnetic. See more http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/EBSVolumeTypes.html. You can access these through flocker profiles.
If the above specs /performance don't work for you, look to use an on-prem, sds solution.
R

@rimusz


struct to json conversion should not be unsafe

According to the ballerina documentation it says struct to json conversion is always safe, and it should be. (see documentation: https://ballerinalang.org/docs/by-example/json-struct-map-conversion). But it fails to run without multi-return conversion expression. Please go through following example.
import ballerina.lang.system;

struct Strings {
    string[] strings;
}

function main (string[] args) {
    Strings strings = {
                          strings:["String 1", "String 2"]
                      };

    var stringsJson = <json>strings;

    system:println(stringsJson);
}

The output as follows.
Test.bal:12: unsafe conversion from 'Strings' to 'json', use multi-return conversion expression

Structs can contain types that are not supported in JSON such as connectors, 'message' type fields, etc. Hence struct to JSON is an unsafe conversion.
We need to update the doc.

Docs are updated with PR https://github.com/ballerinalang/ballerina/pull/3070.
Hence closing the issue.


Getting this message when running the script register-dids.sh

Hello Folks,
I am getting this message when running this script "register-dids.sh"
Error Message: /usr/bin/which: no gp in (/home/linux/.local/bin:/home/linux/bin:/usr/local/bin:/usr/bin:/usr/local/sbin:/usr/sbin)

@frank-bee  @etschelp
Could you please help.

duplicate of https://github.com/hyperledger-labs/business-partner-agent/issues/857


Syntax highlighting off for /*! comments.

I have a scss file that begins with:
/*!
 *  Theme Name:     Doctor What 2011
 *  Author:         Christian Höltje
 *  Author URI:     http://docwhat.org/
 *  Template:       toolbox
 *  Version:        1.0
 */

But everything past the /*! is not highlighted correctly.
In addition, indent-region acts weird for all code below this.
For example, I can select the SCSS directly below this, then run multiple indent-regions and it'll shift around each time I indent.

Also just regular /* comments, everything past the first line is not highlighted, and when // comments are not the first non-whitespace on the line they are not highlighted.


[question]TRPO can't use LstmPolicy or MlpLstmPolicy?

from stable_baselines.common.policies import *
from stable_baselines import *
from stable_baselines.common.env_checker import check_env
from stable_baselines.common.vec_env.dummy_vec_env import DummyVecEnv
from TradeEnv import TradeEnv
from Util.Util import *
from Util.Callback import CustomCallback

episode = 5000
EP_LEN = 250 * 3
FILE_TAG = "TRPO"
mode = "train"
n_training_envs = 1

def post_processor(state):
    return log10plus1R(state) / 10

def make_env():
    env = TradeEnv(obs_time_size='60 day', obs_delta_frequency='1 day', sim_delta_time='1 day',
                   start_episode=0, episode_len=EP_LEN, stock_code='000938_XSHE',
                   result_path="E:/运行结果/TRPO/" + FILE_TAG + "/" + mode + "/",
                   stock_data_path='E:\PycharmProjects\DPPO\myDPPO\Data/train/',
                   poundage_rate=1.5e-3, reward_verbose=1, post_processor=post_processor,
                   max_episode_days=EP_LEN)
    env.seed(0)
    check_env(env)
    return env

env = DummyVecEnv([make_env for _ in range(n_training_envs)])
callback = CustomCallback()
model = TRPO(MlpLstmPolicy, env, verbose=1, tensorboard_log="./log/", seed=0)
model.learn(total_timesteps=episode * EP_LEN, callback=callback)
model.save("./model")

Describe the bug
the observation of my ENV is
self.observation_space = spaces.Box(
low=np.array([[float('-inf') for _ in range(26)]
for _ in range(self.obs_time // self.obs_delta_frequency)]),
high=np.array([[float('inf') for _ in range(26)]
for _ in range(0, self.obs_time // self.obs_delta_frequency)]))
its shape is like (timestep=60, feature=26)
When I run this code, I got error like this:
ValueError: The initializer passed is not valid. It should be a callable with no arguments and the shape should not be provided or an instance of tf.keras.initializers.*' and shape` should be fully defined.
But if I use PPO2, it runs normal
Code example
see above
Traceback (most recent call last):
Instructions for updating:
Colocations handled automatically by placer.
Traceback (most recent call last):
  File "C:\Users\zkx74\Anaconda3\lib\site-packages\stable_baselines\trpo_mpi\trpo_mpi.py", line 138, in setup_model
    None, reuse=False, **self.policy_kwargs)
  File "C:\Users\zkx74\Anaconda3\lib\site-packages\stable_baselines\common\policies.py", line 681, in __init__
    layer_norm=False, feature_extraction="mlp", **_kwargs)
  File "C:\Users\zkx74\Anaconda3\lib\site-packages\stable_baselines\common\policies.py", line 427, in __init__
    layer_norm=layer_norm)
  File "C:\Users\zkx74\Anaconda3\lib\site-packages\stable_baselines\common\tf_layers.py", line 143, in lstm
    weight_x = tf.get_variable("wx", [n_input, n_hidden * 4], initializer=ortho_init(init_scale))
  File "C:\Users\zkx74\Anaconda3\lib\site-packages\tensorflow\python\ops\variable_scope.py", line 1479, in get_variable
    aggregation=aggregation)
  File "C:\Users\zkx74\Anaconda3\lib\site-packages\tensorflow\python\ops\variable_scope.py", line 1220, in get_variable
    aggregation=aggregation)
  File "C:\Users\zkx74\Anaconda3\lib\site-packages\tensorflow\python\ops\variable_scope.py", line 547, in get_variable
    aggregation=aggregation)
  File "C:\Users\zkx74\Anaconda3\lib\site-packages\tensorflow\python\ops\variable_scope.py", line 499, in _true_getter
    aggregation=aggregation)
  File "C:\Users\zkx74\Anaconda3\lib\site-packages\tensorflow\python\ops\variable_scope.py", line 890, in _get_single_variable
    raise ValueError("The initializer passed is not valid. It should "
ValueError: The initializer passed is not valid. It should be a callable with no arguments and the shape should not be provided or an instance of `tf.keras.initializers.*' and `shape` should be fully defined.

System Info
Describe the characteristic of your environment:

Describe how the library was installed: pip in anaconda env
GPU models and configuration: default tf-gpu
Python version 3.7
Tensorflow version 1.13.2
Versions of any other relevant libraries

Additional context
Add any other context about the problem here.

TRPO does not support recurrent architectures, as shown in the implementation grid.


tag_group level directory filters are allowed but not supported

Describe the bug
Based on the docs, directory filters for tag groups are seemingly only supported for each tag in the tag group. For example:
tag_groups:
  - name: devops
    tags:
      - name: group
        value:
          default: devops
        filters:
          directory: apps/datadog

We would like to be able to use the directory filter on the tag_group level instead of per tag. For example:
tag_groups:
  - name: datadog
    tags:
      - name: group
        value:
          default: devops
      - name: env
        value:
          default: prod
    filters:
      directory: apps/datadog
  - name: jenkins
    tags:
      - name: group
        value:
          default: infra
      - name: env
        value:
          default: dev
    filters:
      directory: apps/jenkins

While yor is able to run with this config the directory filters are not respected at all.
When run with the above config file there there are resources in the same file which have tags from each of the different groups.
For example:
resource "aws_instance" "test" {
  ....
  ....

  tags = {
    group                = "devops"
    env                   = "prod"
  }
}

resource "aws_eip" "test" {
  ....
  ....
  tags = {
    group                = "infra"
    env                   = "dev"
  }
}

Even files that do not correspond to the directory filters are tagged as well (files in the other subdirectories of apps/).
Expected behavior
It isn't clear if this is something that is currently supported. If not, yor shouldn't be able to run with an incorrect config file.
Desktop (please complete the following information):

OS: macOS Catalina 10.15.2
Yor Version 0.1.128

Hey @BorisO, thank you for reporting the issue, a contribution would be welcomed!
In order to enable directory filtering to a whole tag group, the following changes are needed in src/common/tagging/external/tag_group.go:

Add to the Config type a filters section of its own - should be added inside the internal TagGroups []struct array.
Ensure the new tag-group level filters are used in *TagGroup CreateTagsForBlock method. Please note that the code to parse a filters section already exists inside the SatisfyFilters method, so the logic should be reused.


Alternative version for template sensor in Wiki

I couldn't find an edit button for the Wiki lemma, but I wanted to propose an alternative template sensor for the creation of the template sensor:
The variables set in the first 3 lines of the attribute make it more easy for the users to adjust the template for their own source sensor.
I also found it a bit redundant to create the lists for both today and tomorrow in each attribute.
Not a user of the integration myself, but I was asked to help with creating a template sensor to be used with this integration, and thought it might be good to share :)
template:
  - sensor:
      - name: "Epex Spot Transformed"
        unit_of_measurement: "€/kWh"
        unique_id: 1daf4afa-8c54-4ab7-b055-7f85ea65a2c7
        state: "{{ states('sensor.epex_spot_data_net_price') }}"
        availability: "{{ 'sensor.epex_spot_data_net_price' | has_value }}"
        attributes:
            prices_today: >
                {%- set forecast_data = state_attr('sensor.epex_spot_data_net_price', 'data') %}
                {%- set time_key = 'start_time' %}
                {%- set price_key = 'price_ct_per_kwh' %}
                {%- set ns = namespace(data=[]) %}
                {%- for i in forecast_data | default([], true) if as_local(as_datetime(i[time_key])).date() == now().date() %}
                  {%- set ns.data = ns.data + [dict(time= as_local(as_datetime(i[time_key])).isoformat(), price = i[price_key])] %}
                {%- endfor %}
                {{ ns.data }}
            prices_tomorrow: >
                {%- set forecast_data = state_attr('sensor.epex_spot_data_net_price', 'data') %}
                {%- set time_key = 'start_time' %}
                {%- set price_key = 'price_ct_per_kwh' %}
                {%- set ns = namespace(data=[]) %}
                {%- for i in forecast_data | default([], true) if as_local(as_datetime(i[time_key])).date() == (now()+timedelta(days=1)).date() %}
                  {%- set ns.data = ns.data + [dict(time= as_local(as_datetime(i[time_key])).isoformat(), price = i[price_key])] %}
                {%- endfor %}
                {{ ns.data }}

@TheFes was helping me with the template to use the Zonneplan component as source.
This is the working result template, might be nice to add to the Wiki:
template:
  - sensor:
      - name: "zonneplan_template_price_sensor"
        unit_of_measurement: "€/kWh"
        state: >
          {{ states('sensor.zonneplan_current_electricity_tariff') | float }}
        attributes:
          prices_today: >
            {%- set forecast = state_attr('sensor.zonneplan_current_electricity_tariff', 'forecast') %}
            {%- set time_key = 'datetime' %}
            {%- set price_key = 'electricity_price' %}
            {%- set ns = namespace(data=[]) %}
            {%- for i in forecast | default([], true) if as_local(as_datetime(i[time_key])).date() == now().date() %}
              {%- set ns.data = ns.data + [dict(time= as_local(as_datetime(i[time_key])).isoformat(), price = i[price_key] / 10000000 )] %}
            {%- endfor %}
            {{ ns.data }}
          prices_tomorrow: >
            {%- set forecast = state_attr('sensor.zonneplan_current_electricity_tariff', 'forecast') %}
            {%- set time_key = 'datetime' %}
            {%- set price_key = 'electricity_price' %}
            {%- set ns = namespace(data=[]) %}
            {%- for i in forecast | default([], true) if as_local(as_datetime(i[time_key])).date() == (now()+timedelta(days=1)).date() %}
              {%- set ns.data = ns.data + [dict(time= as_local(as_datetime(i[time_key])).isoformat(), price = i[price_key] / 10000000 )] %}
            {%- endfor %}
            {{ ns.data }}

Added unit_of_measurement, unique_id and availability to the YAML

@TheFes, thanks for the alternative version. I have used it to update the EPEX Spot Wiki page. Except for the UUID, which is good for automatically generated IDs, but maybe not as good for manually created IDs.
@hmmbob, I also added the Zonneplan variant to the Wiki page.
Also, when adding unique_id to the template, the properties of the entity changed in such a way that I needed to update the code a bit. So now there is a v1.11.0-dev2 release available.

I have sensor for getting tibber prices based on the template above, but when i try to use it in the integration i get the error that the sensor could not be found.
The sensor is defined as follows:
`template:

sensor:

name: "my_ev_price_tibber_sensor"
unit_of_measurement: "€/kWh"
availability: "{{ 'sensor.tibber_electricity_price' | has_value }}"
state: '{{state_attr("sensor.tibber_electricity_price","current")["total"] | float}}'
attributes:
prices_today: >
{%- set forecast_data = state_attr('sensor.tibber_electricity_price', 'today') %}
{%- set time_key = 'startsAt' %}
{%- set price_key = 'total' %}
{%- set ns = namespace(data=[]) %}
{%- for i in forecast_data | default([], true)%}
{%- set ns.data = ns.data + [dict(time= as_local(as_datetime(i[time_key])).isoformat(), price = i[price_key])] %}
{%- endfor %}
{{ ns.data }}
prices_tomorrow: >
{%- set forecast_data = state_attr('sensor.tibber_electricity_price', 'tomorrow') %}
{%- set time_key = 'startsAt' %}
{%- set price_key = 'total' %}
{%- set ns = namespace(data=[]) %}
{%- for i in forecast_data | default([], true)%}
{%- set ns.data = ns.data + [dict(time= as_local(as_datetime(i[time_key])).isoformat(), price = i[price_key])] %}
{%- endfor %}
{{ ns.data }}
`
The values within the gui look like in the screenshot attached.
I would appreciate your help.

Hi,

I have sensor for getting tibber prices based on the template above, but when i try to use it in the integration i get the error that the sensor could not be found.
The sensor is defined as follows:
template:
  - sensor:
      - name: "my_ev_price_tibber_sensor"
        unit_of_measurement: "€/kWh"
        availability: "{{ 'sensor.tibber_electricity_price' | has_value }}"
        state: '{{state_attr("sensor.tibber_electricity_price","current")["total"] | float}}'
        attributes:
          prices_today: >
            {%- set forecast_data = state_attr('sensor.tibber_electricity_price', 'today') %}
            {%- set time_key = 'startsAt' %}
            {%- set price_key = 'total' %}
            {%- set ns = namespace(data=[]) %}
            {%- for i in forecast_data | default([], true)%}
              {%- set ns.data = ns.data + [dict(time= as_local(as_datetime(i[time_key])).isoformat(), price = i[price_key])] %}
            {%- endfor %}
            {{ ns.data }}
          prices_tomorrow: >
            {%- set forecast_data = state_attr('sensor.tibber_electricity_price', 'tomorrow') %}
            {%- set time_key = 'startsAt' %}
            {%- set price_key = 'total' %}
            {%- set ns = namespace(data=[]) %}
            {%- for i in forecast_data | default([], true)%}
              {%- set ns.data = ns.data + [dict(time= as_local(as_datetime(i[time_key])).isoformat(), price = i[price_key])] %}
            {%- endfor %}
            {{ ns.data }}

The values within the gui look like in the screenshot attached.
I would appreciate your help.

@adegenkolbe, can you double check that there is an entity named sensor.my_ev_price_tibber_sensor? If you look in Settings->Devices & services->Entities
If there is such an entity, can you add unique_id: my_ev_price_tibber_sensor to the template and try again?
Please let me know your observations.

Thanks for the quick response and your hel @jonasbkarlsson
The Entity was present. After I added the unique id i could complete the setup. So it seems to be a mandatory field.

Reply on the content:
state: '{{state_attr("sensor.tibber_electricity_price","current")["total"] | float}}'

The | float has no use, as HA states are always strings. So this is he correct one:
state: '{{state_attr("sensor.tibber_electricity_price","current")["total"] }}'

@adegenkolbe, thanks for the feedback. Can you confirm that it is v1.11.0-dev2 that you are using?

@jonasbkarlsson i was pretty sure that i chose the beta for installation (as you stated in the comments above) but obviously i  made a mistake or something else happend. i was on the latest stable. I updated and now it also worked without a unique id. sorry for the confusion

@adegenkolbe, thanks for checking. A good to hear that you had the "wrong" version. I'm quite sure it should work without unique_id. However, I think it is better to include unique_id  in the template.

Reply on the content:
state: '{{state_attr("sensor.tibber_electricity_price","current")["total"] | float}}'

The | float has no use, as HA states are always strings. So this is he correct one:
state: '{{state_attr("sensor.tibber_electricity_price","current")["total"] }}'

(it doesn't break anything though, it's just getting converted back to string again)

Is that really correct? The documentation of entity says that state can be str | int | float | None. And the documentation of template  even says that " If the sensor is numeric, i.e. it has a state_class or a unit_of_measurement, the state template must render to a number or to none. The state template must not render to a string..."

Whoa. @TheFes ?

It doesn't matter actually.
The result of a template is always a string. The template parser in HA then tries to convert it to a native Python type (float, int, list, dict etc). If it can't, it will use the template result as string.
That's why something like {{ "[ 'a', 'b', 'c']" }} will show as a list in developer tools > templates (as it uses the same template parser).

@TheFes was helping me with the template to use the Zonneplan component as source (Zonneplan is one of the Netherlands energy providers with dynamic/hourly tariffs)
This is the working result template, might be nice to add to the Wiki:
template:
  - sensor:
      - name: "Zonneplan template price sensor"
        unique_id: zonneplan_template_price_sensor
        unit_of_measurement: "€/kWh"
        availability: "{{ 'sensor.zonneplan_current_electricity_tariff' | has_value }}"
        state: "{{ states('sensor.zonneplan_current_electricity_tariff') }}"
        attributes:
          prices_today: >
            {%- set forecast = state_attr('sensor.zonneplan_current_electricity_tariff', 'forecast') %}
            {%- set time_key = 'datetime' %}
            {%- set price_key = 'electricity_price' %}
            {%- set ns = namespace(data=[]) %}
            {%- for i in forecast | default([], true) if as_local(as_datetime(i[time_key])).date() == now().date() %}
              {%- set ns.data = ns.data + [dict(time= as_local(as_datetime(i[time_key])).isoformat(), price = i[price_key] / 10000000 )] %}
            {%- endfor %}
            {{ ns.data }}
          prices_tomorrow: >
            {%- set forecast = state_attr('sensor.zonneplan_current_electricity_tariff', 'forecast') %}
            {%- set time_key = 'datetime' %}
            {%- set price_key = 'electricity_price' %}
            {%- set ns = namespace(data=[]) %}
            {%- for i in forecast | default([], true) if as_local(as_datetime(i[time_key])).date() == (now()+timedelta(days=1)).date() %}
              {%- set ns.data = ns.data + [dict(time= as_local(as_datetime(i[time_key])).isoformat(), price = i[price_key] / 10000000 )] %}
            {%- endfor %}
            {{ ns.data }}

Let me update this one with the trigger we added in #279
template:
  - trigger:
        # This should generare triggers for all changes in the entity, both in it's state and it's attributes.
      - platform: state
        entity_id: sensor.zonneplan_current_electricity_tariff
  - sensor:
      - name: "Zonneplan template price sensor"
        unique_id: zonneplan_template_price_sensor
        unit_of_measurement: "€/kWh"
        state: "{{ states('sensor.zonneplan_current_electricity_tariff') }}"
        availability: "{{ 'sensor.zonneplan_current_electricity_tariff' | has_value }}"
        attributes:
          prices_today: >
            {%- set forecast = state_attr('sensor.zonneplan_current_electricity_tariff', 'forecast') %}
            {%- set time_key = 'datetime' %}
            {%- set price_key = 'electricity_price' %}
            {%- set ns = namespace(data=[]) %}
            {%- for i in forecast | default([], true) if as_local(as_datetime(i[time_key])).date() == now().date() %}
              {%- set ns.data = ns.data + [dict(time= as_local(as_datetime(i[time_key])).isoformat(), price = i[price_key] / 10000000 )] %}
            {%- endfor %}
            {{ ns.data }}
          prices_tomorrow: >
            {%- set forecast = state_attr('sensor.zonneplan_current_electricity_tariff', 'forecast') %}
            {%- set time_key = 'datetime' %}
            {%- set price_key = 'electricity_price' %}
            {%- set ns = namespace(data=[]) %}
            {%- for i in forecast | default([], true) if as_local(as_datetime(i[time_key])).date() == (now()+timedelta(days=1)).date() %}
              {%- set ns.data = ns.data + [dict(time= as_local(as_datetime(i[time_key])).isoformat(), price = i[price_key] / 10000000 )] %}
            {%- endfor %}
            {{ ns.data }}

@hmmbob, thanks for the suggestion of using ```yaml. I have put your first template in the Wiki.
For the second template, should it really be - sensor:? I thought that hyphen will mean that the preceesing trigger is not used. Meaning that it should be sensor: (without a hypen) for the trigger to be applied.

@jonasbkarlsson you are right, it should be without the hyphen

Yeah, that's a typo here. I have it without hypen in my config. Good spot!


remove composer.lock from gitignore

based on getcomposer.org recommendation at https://getcomposer.org/doc/01-basic-usage.md#commit-your-composer-lock-file-to-version-control it is important to have composer.lock within git.

Committing this file to VC is important because it will cause anyone who sets up the project to use the exact same versions of the dependencies that you are using. Your CI server, production machines, other developers in your team, everything and everyone runs on the same dependencies, which mitigates the potential for bugs affecting only some parts of the deployments. Even if you develop alone, in six months when reinstalling the project you can feel confident the dependencies installed are still working even if your dependencies released many new versions since then. (See note below about using the update command.)

I know that there are some debate whether we should have this within frameworks or not, but if am not mistaken Jigsaw is an application not a framework.
More info about why we should have composer.lock within git was mentioned here https://www.engineyard.com/blog/composer-its-all-about-the-lock-file

We will always have a debate weather it is an application or a framework, as for example I cant say that Laravel Mix is a framework, its a tool, the same thing with Jigsaw in my opinion,  it is just a set of tool that any user can use it, remember each one of us can define a different specification for the word end-users.
What can help us is to define who is the end-user for Jigsaw, a designer, a programmer or anyone with few knowledge of markup?

What can help us is to define who is the end-user for Jigsaw, a designer, a programmer or anyone with few knowledge of markup?

The end-user is the user at the end? I.e. the one who visits and uses the website/web application. The programmer or designer just writes it for the end-user.

Based on that the end user has no interest in jigsaw or what files we
include or exclude from it.and they only care about the website they visit
with the mabojambo style and layout
From my mobile, Please excuse any awkward autocorrections or typos.
On Sat, Aug 25, 2018, 5:16 PM Ped<EMAIL_ADDRESS>wrote:

What can help us is to define who is the end-user for Jigsaw, a designer,
a programmer or anyone with few knowledge of markup?
The end-user is the user at the end? I.e. the one who visits and uses the
website/web application. The programmer or designer just writes it for the
end-user.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/tightenco/jigsaw/pull/244#issuecomment-415972252, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AABr6CvXhSiFWTK_9pDlsdvOYF0gdrj_ks5uUVxMgaJpZM4VwknZ
.


fast fine-tuning?

I understand that your code uses the VITS code, right? Would it be possible to add fast fine-tuning, like in this repository: https://github.com/Plachtaa/VITS-fast-fine-tuning? Or is it a completely different repository?
Currently, I have trained three models, but they take quite a long time to train, as it requires around 6 hours of training to achieve a good voice. Also, the models mispronounce some words in the Polish language. I'm not sure if it's due to poor phonemization or the model itself.

My VITS code has diverged quite a bit from the original, so I don't know if that approach will work. Some changes recently in Piper v1 may help your pronunciation issues with Polish (more phonemes added).
I'd also recommend using --resume_from_checkpoint to fine-tune one of the pre-trained models. I have a couple Polish models available there.

There isn't any checkpoint for the Persian (Farsi) language in the pre-trained models. what should I do to fine-tune the Piper model in the Persian language?


Correct formula for decimal

AFAICT, the correct formula should use max(s, 6), not min(s, 6).

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

@GalLalouche Welcome as a first-time contributor. I will be reviewing and updating this request.


Too slow on GPU

I ran the flax example from the examples folder on GPU and CPU.
It runs lightning fast on the CPU taking less than 2s, whereas on GPU it took more than 28s. I observed the same problem in another training code. Infact, that is where I first figured that the optax specific part is slow/bottleneck.
Is there any reason why this is happening and how to fix it?
If it helps to know, I am using jax==0.3.4 installed via pip install jax[cuda] and optax==0.1.0, and cudatoolkit==11.3.1
Thanks,

Hi! Oh, interesting - thanks for raising this! I took a look at the examples and the behaviour you describe could be due to the placement of jax.jit.
The jit is only placed around the loss function and not the optax calls. This means that the optax code will run slowly and not on device. For an example on where to place the jit to get the best performance, see the lookahead example. We should definitely change the flax example to include the optax update and apply in the jit too.
In the haiku example and the quick start there is no jax.jit at all - presumably on purpose, but I think it might be good to add it to demonstrate the best practice of placing the jit around the optax calls too.
Would this explain the performance issue in the other training code you mentioned too?

Would this explain the performance issue in the other training code you mentioned too?

Yes, this explains the issue.

Would you like to file the PR for making the changes to where jit is used? No worries if not, someone else can jump in too or I'm also happy to make the change.

Would this explain the performance issue in the other training code you mentioned too?

Yes, this worked. I am sorry for raising an issue without trying jitting --- I thought optax would do it already for me.

Would you like to file the PR for making the changes to where jit is used? No worries if not, someone else can jump in too or I'm also happy to make the change.

I would be happy to fix this. Did you mean for me to add jit in the examples or all the optimizers?

Hi! Not at all - thanks for raising this! I think the placement of the jit in the flax example isn't the best so I think we should change this.
Regarding optax including the jit around the optimizers: we don't do this for several reasons (it would almost always be the wrong place for the jit, user might want different transformations or different arguments for the jit, and in some cases users might not want the jit at all). In most cases, it is best to place the jit around the outermost jittable function. In the case of neural network training this is usually the function that takes one training step.
I think we should change the flax example to have the jit around an entire training step and not just the loss (similar to how the lookahead example does it).
Thanks a lot!


HIDError: Report size has to be 1025 elements (bytes)

Hi, when I run "pyocd gdbserver" command, I get this error.

0000253:INFO:board:Target type is cortex_m
0000253:WARNING:board:Generic 'cortex_m' target type is selected; is this intentional? You will be able to debug but not program flash. To set the target type use the '--target' argument or 'target_override' option. Use 'pyocd list --targets' to see available targets types.
0000269:CRITICAL:main:uncaught exception: Report size has to be 1025 elements (bytes)
Traceback (most recent call last):
File "build\bdist.win32\egg\pyocd_main_.py", line 338, in run
self.COMMANDSself._args.cmd
File "build\bdist.win32\egg\pyocd_main.py", line 566, in do_gdbserver
with session:
File "build\bdist.win32\egg\pyocd\core\session.py", line 287, in enter
self.open()
File "build\bdist.win32\egg\pyocd\core\session.py", line 363, in open
self._probe.open()
File "build\bdist.win32\egg\pyocd\probe\cmsis_dap_probe.py", line 141, in open
self._link.open()
File "build\bdist.win32\egg\pyocd\probe\pydapaccess\dap_access_cmsis_dap.py", line 552, in open
self._packet_count = self._protocol.dap_info(self.ID.MAX_PACKET_COUNT)
File "build\bdist.win32\egg\pyocd\probe\pydapaccess\cmsis_dap_core.py", line 126, in dap_info
self.interface.write(cmd)
File "build\bdist.win32\egg\pyocd\probe\pydapaccess\interface\pywinusb_backend.py", line 144, in write
self.report.send([0] + data)
File "build\bdist.win-amd64\egg\pywinusb\hid\core.py", line 1475, in send
% self.__raw_report_size)
HIDError: Report size has to be 1025 elements (bytes)

I'm using LPC-LINK 2 board with LPC4370 on-board MCU

This is a known issue with LPC-Link2 and pywinusb. You can try the hidapi USB backend instead, which should work. Just run 'pip install hidapi'. pywinusb is still the default for Windows mostly for historical reasons, but it changing this to hidapi might make sense.


unable to see the user interface of react tide

Hi Team,
Can you check the issue of ReactTide of live website? unable to render the UI.

I believe this project is discontinued, and the website's domain subscription wasn't renewed


Superscript Temporarily Disabled

The Superscript element works, but needs to be disabled until the following conditions are met:

[x] Implement/fix other markup elements that must be parsed before superscript:

[ ] Implement link: element, and capture ^ for blank targeting.
[x] Correctly handle the [cols="<...>"] one-liner that precedes tables.

[x] Re-enable test Tests/quotes/_syntax_test_Superscript.asciidoc.

Superscript was temporarily disabled (commit f7ab8323b) because it was breaking up documents where the caret ^ was used for links with blank target or tables alignments.
If a document contained, e.g.:
link:https://some-url.com[some text^]
                                   ^   i.e. "target_blank" link

or
[cols="3*^"]
|=====================
         ^   i.e. column alignment (center)

the ^ was parsed as an opening subscript delimiter, thus breaking up the whole document until another ^ was encountered.
To fix this, we need to implement the link: element and capture the [cols="<...>"] one-liner that precedes tables, and ensure that these elements always precede subscript in the syntax parsing order, so that the ^ will be properly handled in these contexts.

Fixed!
OK, I've managed to fix the Superscript element now. The link element is also back, which was part of the original syntax, implemented together with the generic macro definition.
In order to prevent document disruption with tables options like [cols="3*^"], I had to introduce a new "dummy element" in order to consume the occurrence of similar table options, without providing any scope to them. In the future I might need to introduce a dedicated element for these table options (what are they called?), but for now the fix will do.
Also, it would be a good idea to create a separate element for handling links, for we could provide better semantics and cover more fine-grain details — e.g. title="" and ^ for target blank, and others — as well as to allow attributes in links (which are not uncommon).
Anyhow, now all tests are back, along with new ones checking for false positive Subscript matches, and they all pass.


feat(Topology/Algebra/Module/WeakDual): prove basic relations between the weak topology and the original topology

(This PR continues #11472)
Prove the following basic facts about the weak topology in a topological vector space (or AddCommMonoid) E.

any set that is open in the weak topology is open in the original topology.
any function in E that converges to a point in the original topology (with respect to some filter) converges also in the weak topology.
if a function in E converges to a point in the original topology, then its composition with a continuous linear functional converges.
any function from E that is continuous in the weak topology is also continuous in the original topology.

Motivation: WeakSpace has some basic properties, analogue of which are proved for WeakDual.
I have some doubts:

in order to avoid typeclass instance problem, I had to add a type ascription continuousLinearMapToWeakSpace : E →L[𝕜] WeakSpace 𝕜 E when needed. Is this fine or is there a canonical way to avoid it? (I tried to add variable (𝕜 E) in before def/thm but it gave type mismatch in many places)
I made two theorems about IsOpen, but not sure about the naming convention.

You get the type-mismatch because you have to now write continuousLinearMapToWeakSpace k E.
The general rule is that if you want reviews you should make sure that CI passes (you get a green checkmark after the commit), see https://leanprover-community.github.io/contribute/index.html#lifecycle-of-a-pr

thanks for your comments, I wrote 𝕜 E where necessary.
In order to avoid lint errors, I deleted toWeakSpace_eq_iff which could be proved by one simp only<EMAIL_ADDRESS>I would like to have a comment on the naming convention of isOpen_of_isOpen_WeakSpace, isOpen_of_isOpen_WeakSpace'

Thanks for your review!
As isOpen_of_isOpen depends on the definitions and isOpenMap_toWeakSpace_symm as well, I moved everything out of namespace. I hope this is fine.

OK, I committed all your suggestions.

Thanks!
bors merge


style: Update Icons for HDH #HDH-76

Harness Developer Pull Request
Thanks for helping us make the Developer Hub better. The PR will be looked at
by the maintainers.
What Type of PR is This?

[ ] Issue
[ ] Feature
[x] Maintenance/Chore

If tied to an Issue, list the Issue(s) here:

Issue(s)

House Keeping
Some items to keep track of. Screen shots of changes are optional but would help the maintainers review quicker.

[x] Tested Locally
[x] Optional Screen Shoot.

Preview environment: https://hdh.pr.harness.io/pr-1115


Add Cost Information for Subscription

I cannot query cost information about my azure subscriptions
Azure's cost portal is not the most flexible, and I would like to be able to query subscription costs.
Solution
I would like to query azure subscription costs, possibly being broken down by resource group.
Describe alternatives you've considered
The alternative is to use steampipe to query resourcegroup to get cost center tags, then assemble data from steampipe and azure portal in excel.
Additional context
I have been tasked with querying costs by resource group and tag by month, steampipe is much more flexible than azure portal, I'd love to see this functionality implemented.

Welcome to Steampipe @dgsauve 👍 and thanks for raising this request.
If anyone would like to attempt to develop this table, the APIs mentioned in<EMAIL_ADDRESS>is an excellent place to start.
Additional links - https://learn.microsoft.com/en-us/rest/api/cost-management/
Please let us know in case there are questions 👍 .

not stale

@dgsauve, my apologies for the lack of communication regarding this issue.
We have identified an API that fulfils your requirements. We are actively investigating and conducting thorough testing of this API using various test cases. You can find all the relevant details and progress updates here. We welcome your feedback and suggestions as we continue working on this. Rest assured; we will keep you informed of any further developments in this matter.
Here is a sample test output which fetches the cost per resource group of a particular subscription -
> select
  display_name as subscription,
  jsonb_pretty(columns) as columns,
  jsonb_pretty(rows) as rows
from
azure_cost_management as m,
azure_subscription as s
where
m.subscription_id = s.subscription_id
+-----------------+----------------------------------+-------------------------------------------+
| subscription    | columns                          | rows                                      |
+-----------------+----------------------------------+-------------------------------------------+
| newwarriors AAA | [                                | [                                         |
|                 |     {                            |     [                                     |
|                 |         "name": "PreTaxCost",    |         0.001344086021505,                |
|                 |         "type": "Number"         |         20230611,                         |
|                 |     },                           |         "demo",                           |
|                 |     {                            |         "USD"                             |
|                 |         "name": "UsageDate",     |     ],                                    |
|                 |         "type": "Number"         |     [                                     |
|                 |     },                           |         0.000003,                         |
|                 |     {                            |         20230611,                         |
|                 |         "name": "ResourceGroup", |         "kp-test-k8-compliance_group",    |
|                 |         "type": "String"         |         "USD"                             |
|                 |     },                           |     ],                                    |
|                 |     {                            |     [                                     |
|                 |         "name": "Currency",      |         0.0000319298,                     |
|                 |         "type": "String"         |         20230611,                         |
|                 |     }                            |         "nist-test_group",                |
|                 | ]                                |         "USD"                             |
|                 |                                  |     ],                                    |
|                 |                                  |     [                                     |
|                 |                                  |         2.001683513643921,                |
|                 |                                  |         20230611,                         |
|                 |                                  |         "turbottest11815",                |
|                 |                                  |         "USD"                             |
|                 |                                  |     ],                                    |
|                 |                                  |     [                                     |
|                 |                                  |         0.000006,                         |
|                 |                                  |         20230611,                         |
|                 |                                  |         "turbottest28408",                |
|                 |                                  |         "USD"                             |
|                 |                                  |     ],                                    |
|                 |                                  |     [                                     |
|                 |                                  |         0.004267008,                      |
|                 |                                  |         20230611,                         |
|                 |                                  |         "turbottest37303",                |
|                 |                                  |         "USD"                             |
|                 |                                  |     ],                                    |

@dgsauve @ledoyen @John-Donalson, we have temporarily postponed the work above due to our current focus on higher-priority tasks. However, we plan to return to it shortly. In the meantime, if you would like, you are more than welcome to use the provided code as a starting point and make any necessary changes. We would appreciate it if you could raise a pull request (PR) with your changes. Feel free to also reach out to us if you need any help with the same.

As per the message above, we're closing this issue as not planned for now, but will re-open once we have time to revisit it (if another user wants to take up the work, please re-open).


Allow empty passwords

Allow empty passwords with the restic flag "--insecure-no-password"

closes https://github.com/emuell/restic-browser/issues/122


MuTect2 should annotate DP in FORMAT  field

Feature request
Tool(s) involved
MuTect2
Description
Right now, MuTect2 only outputs AD. Users would find it helpful to have the filtered depth like DP in HaplotypeCaller output.
This Issue was generated from your [forums]
[forums]: http://gatkforums.broadinstitute.org/gatk/discussion/comment/35778#Comment_35778

@chandrans We suspect that we fixed this somewhere along the line.  @takutosato will check and fix if necessary.

In gatk4 we report both DP and AD.

Great, thanks!


Added docstrings to several undocumented functions

Documented various functions that we found particularly lacking of docstrings.

Sorry, but your description here is super deceiving. You did not document functions you found "particularly lacking of docstrings", you ran some automated tool that generates questionable docstrings to put it favorably.


Face capture should work on web

implement a web component using face-api
use it also for face expression detection
need to return faces object
{ faces: {
faces:[{bounds:{origin:{x,y},size:{width,height}}, leftEyeOpenProbability?, rightEyeOpenProbability?, smilingProbability?, neutralProbability, rollAngle, yawAngle
}}
doesnt provide eyes probability
smilingProbability=happy probability - doesnt return it, should return neutral probability instead
use head pose estimation for roll/yaw/pitch
https://github.com/mjyc/head-pose-estimation-demo

there's an https://docs.expo.io/versions/latest/sdk/camera/ package working on all platform (including web) and supporting face detection.
I'll try to make small demo app using it, if everything will work, we can use it both for web & native instead of RNCamera
@sirpy What you think ?

@sirpy
Unfortunately, we can't use expo-camera for now due to the following reason:

Expo SDK packages aren't compatible with create-react-native-web-app bolierplate we're using (it's based on create-react-native-app but ejected a few versions ago). Now there're no (at least easy) way to use expo-camera.
So, the only way to use camera is to use latest create-react-native-app but
a) we need to transfer all GoodApp (re-create, import existing code, retest everything). It's not our way )
b) Even if supposedly we did a), it's not worth the trouble - expo for web is still in beta, stability is very floating from version to version. On my system expo-camera won't work (on Chrome it doesn't detects web camera, on Safari detects but anyway won't show video frame)

For  now i propose to return to the plan i proposed this morning: HTML5-based camera implemented by some simple (as much as possible) library.
I've already tested react-webcam package - it works with RN Web:
https://www.npmjs.com/package/react-webcam
on Web (as all web support in expo-cli & expo SDK) are sti

ok.
see here for example calling face-api in a loop on a video stream, minimum
video constraint should be 640x360
https://github.com/justadudewhohacks/face-api.js/blob/master/examples/examples-browser/views/videoFaceTracking.html


Add a6c and cN3LO dynamics parameters to ROQ

Pull request to add the EOB dynamics parameters ( TEOBResumS_a6c and TEOBResumS_cN3LO ) to the ROQ generation.

Thanks a lot for this! It looks spotless.


pfio collective_stage_data fails when client root process passes no data AND using multi group server

The collective_stage_data call of the PFIO server has for many years now had the ability to still function if some process do not have data, in that case you just make a local memory reference or array reference with a size 0 array on those processes that do not have any data to stage.
This is used when the grid is too coarse in History and some processes do not have a de. It's also used in the restart writing to write the tile data where it is all gathered to root.
In both those cases the root process does have data to write.
I've been trying to finish another PR I am working to have one file per write. That is all working but I was also trying to get it working with o-server. If I have say 6 writers, then when it is time to write, you make the collective_stage_data call for all 6 files for example. With each request only 1/6th of the processes have a non-zero sized array reference passed. If I use the simple server, (i.e. where there s no separate o-server) it seems to work and I get 6 files with the right data
However, once I turn on the multi group server I've been struggling and have concluded that if the ROOT process of the application does not have a non-zero size array something goes wrong in this case. That's the only logical conclusion I can come to after struggling for over day with this. When I've been prototyping this I can write the file  for writer 1 which has the root process. But if I try to write any other file for the other writers it fails here:
https://github.com/GEOS-ESM/MAPL/blob/main/pfio/MultiGroupServer.F90#L397
Next I attempted to create a reproducer from one of the pfio tests that exercises the multi group server to reproduce this issue. I think I have (kind of).
That can be found here on discover
~bmauer/for_users/for_weiyuan/collective_stage_debugger.F90
Basically I took the pfio test executable and stripped it down.
Here is an example of how to run with 6 client process,  a multgroup server with 3 writers, 3 front end cores (for total of 6 cores for the server, and 12 total). I also added a new -o option:
mpirun -np 12 ./bin/collective_stage_debugger.x -nc 6 -nso 6 -ngo 1 -v T -s multigroup -nw 3 -o 1
In the code the server is told to create a file with xdim=12 and ydim=12 so the file has 144 points total, then which ever process you specify with the new -o options (so value must be <= nc -1) writes to the file, otherwise collective stage is passed an empty array reference.
The process that does pass non-empty data to collective state has it's values (a 12x12 array) set to the rank of that process
So if you set -o 1 the file should be filled with 1's
if you set -o 0, it should be filled with 0's
if you set -o 2, it should be filled with 2's
In other words the file should filled with the rank of the process you said to write on.
But I'm seeing that unless I set -o 0 the file is filled with garbage.
The strange thing is I'm not seeing the same error (that select case with the "yet to implement" fail), in fact I see no error, but the unless the non-empty array is on rank 0, it's clearly not work as it should in that file is not being correctly written, the value of the variable is garbage like it was never written to at all.
Either way I am forced to conclude that when collective_state_data is used with the multi group server, if the root process of the application code (therefore client) does not pass data, something goes wrong.

That root requires non-zero data is an interesting theory.   I cannot immediately think of any underlying design aspect of the server that would require such - it is pretty agnostic about such things as "root" on the client side.  Hopefully @weiyuan-jiang has a good idea on how to dig into that.

at least I was able to reproduce something outside of our checkpoint code (that's where I hit this first) via the reproducer I posted. It does seem to be something  with root having/not having data, I spend a long time and I just can't see that I've made any other mistakes in the checkpoint code where I hit his, it really does seem to be exactly as I've described :(

I am working on it now...

This PR https://github.com/GEOS-ESM/MAPL/pull/2559 seems to have fixed. Thanks @weiyuan-jiang
I will close issue.


Support for Visual Studio 2013

I am wondering how long do we plan to support VS 2013?
In PR https://github.com/Microsoft/ChakraCore/pull/1481 I started using constexpr on some functions to avoid using macros.
Before I reverted those change, I believe it would be worth checking if we planned to drop support soon.

@curtisman @digitalinfinity @dilijev @LouisLaf @MikeHolman Any thoughts on the matter ?

constexpr is a great feature we're missing out on. This isn't the first time it has come up. Since VS 2015 has a community edition that anyone can use for free, I'm seeing less of a compelling reason to keep supporting downlevel products because "people have already paid for those". Possibly you could argue "people are used to the workflow" but I don't think much of the community is depending on a VS 2013 workflow for our project.

Agreed.
I may be mistaken, but I believe VS 2013 is the only non-fully compliant C++ 11 compiler we support.  It would be nice to have the full C++11 feature set available for us to use, by dropping VS 2013.

Use of constexpr came up once before in #309
We thought about using C++11 char16_t and u"..." for xplat strings in #456 but couldn't because VS 2013 doesn't have it

I believe there were one or two other issues that came up where it would have been nice to have full C++11 support.

+1, though I seem to remember there being being issues about downlevel and ARM.

Node still support building with VS2013.

^ And that right there is the only reason we need to keep supporting VS 2013. :P

That is too bad.  Doesn't mean node-chakracore needs to support VS2013, but reasonable to do so.


fix: removed old key_val_input, updated keyval_array, show ds info

Description
This PR deals with :

Removing the old KeyValueInputControl having control type KEY_VAL_INPUT.
Moved form configurations having control type KEY_VAL_INPUT to KEYVALUE_ARRAY
Updated the Array fields for Headers, Query Params etc for datasources to follow UQI based designs
Saved values for datasources are now visible on datasource cards in active pane as well on view mode for individual datasources.

TL;DR
Fixes #14804
Fixes #6181

Type of change

Bug fix (non-breaking change which fixes an issue)

How Has This Been Tested?

Manual
Cypress

Test Plan

Add Testsmith test cases links that relate to this PR

Issues raised during DP testing

Link issues raised during DP testing for better visiblity and tracking (copy link from comments dropped on this PR)

Checklist:
Dev activity

[ ] My code follows the style guidelines of this project
[ ] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes
[ ] PR is being merged under a feature flag

QA activity:

[ ] Test plan has been approved by relevant developers
[ ] Test plan has been peer reviewed by QA
[ ] Cypress test cases have been added and approved by either SDET or manual QA
[ ] Organized project review call with relevant stakeholders after Round 1/2 of QA
[ ] Added Test Plan Approved label after reveiwing all Cypress test

/ok-to-test sha=50c11d7

/ok-to-test sha=a50a358

/ok-to-test sha=1664c8b

/ok-to-test sha=5b48dae

Adding label Test Plan Approved label as specified in https://github.com/appsmithorg/appsmith/issues/14804#issuecomment-1348664134


Title elements.

As a web developer
I want to make sure title elements contain concise and descriptive titles
So that the HTML is easier for developers and browser to read and to meet accessibility standards.

Title element now contains a concise and descriptive title for the webpage.


FileNotFoundException at com.amplitude.core.utilities.EventsFileManager.writeToFile

Encountering numerous crashes in version 1.6.0.
Fatal Exception: java.io.FileNotFoundException: /data/user/0/package_name/app_amplitude-disk-queue/<redacted>-71975.tmp (Permission denied)
       at java.io.FileOutputStream.open0(FileOutputStream.java)
       at java.io.FileOutputStream.open(FileOutputStream.java:287)
       at java.io.FileOutputStream.<init>(FileOutputStream.java:223)
       at com.amplitude.core.utilities.EventsFileManager.writeToFile(EventsFileManager.kt:168)
       at com.amplitude.core.utilities.EventsFileManager.finish(EventsFileManager.kt:145)
       at com.amplitude.core.utilities.EventsFileManager.rollover(EventsFileManager.kt:104)
       at com.amplitude.android.utilities.AndroidStorage.rollover(AndroidStorage.kt:54)
       at com.amplitude.core.platform.EventPipeline$upload$1$1$1.invokeSuspend(EventPipeline.kt:102)
       at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:33)
       at kotlinx.coroutines.DispatchedTask.run(DispatchedTask.kt:106)
       at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1162)
       at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:636)
       at java.lang.Thread.run(Thread.java:764)

Thanks for reporting this @shawn-lin-013. Is this happening to a certain type of devices? Are you able to repro this issue locally?

Hi @shawn-lin-013, we recently pushed some fixes around storage to resolve some crashes. Would you mind upgrading to the latest and see if that helps?

Hi @shawn-lin-013, we recently pushed some fixes around storage to resolve some crashes. Would you mind upgrading to the latest and see if that helps?

Hi @qingzhuozhen, we wonder which version is suggested to upgrade?

Hi @shawn-lin-013 We recently released v1.16.4, maybe try to upgrade to that version and see if that helps. Feel free to let us know if the issue is still not solved and we can dive further,

@shawn-lin-013 closing this issue but please feel free to reopen the issue if you still see problems with the latest version.


CANCELLED Using camelCase route names seems to be broken in 2.0+

I have a route name that's mainMenu. While using that, I get the following error. When I change it to all lowercase, it works fine. I'm using RiverPod 2.0.0-dev.9 but the issue is go_router 3.03. Hence I'm closing this report.
The following assertion was thrown while handling a gesture:
Assertion failed:
file:///L:/development/sdks/flutter/.pub-cache/hosted/pub.dartlang.org/go_router-4.1.0/lib/src/go_route_information_parser.dart:97:12
..\…\src\go_route_information_parser.dart:97
_nameToPath.containsKey(name)
"unknown route name: mainMenu"

Here's other reports on issueHint https://issuehint.com/issue/flutter/flutter/106163

Hello!
What does this have to do with riverpod?
On Sat, 9 Jul 2022, 17:18 jeff9315, @.***> wrote:

I have a route name that's mainMenu. While using that, I get the following
error. When I change it to all lowercase, it works fine. I'm using
2.0.0-dev.9
The following assertion was thrown while handling a gesture:
Assertion failed:
file:///L:/development/sdks/flutter/.pub-cache/hosted/pub.dartlang.org/go_router-4.1.0/lib/src/go_route_information_parser.dart:97:12
..\…\src\go_route_information_parser.dart:97
_nameToPath.containsKey(name)
"unknown route name: mainMenu"
Here's other reports on issueHint
https://issuehint.com/issue/flutter/flutter/106163
—
Reply to this email directly, view it on GitHub
https://github.com/rrousselGit/riverpod/issues/1492, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AEZ3I3LVWA3OO3DQ5AWNONLVTGJ4XANCNFSM53DQSDNQ
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>


VSchema documentation

This is the VSchema user guide. This is mostly a superset of https://github.com/youtube/vitess/blob/master/doc/VTGateV3Features.md, which I plan to delete. I'm even thinking of deleting the Vindex design doc, but there could be arguments to keep it around.

You can view a readable version of the doc here https://github.com/sougou/vitess/blob/doc/doc/VSchema.md.

Review status: all files reviewed at latest revision, 23 unresolved discussions.

doc/VSchema.md, line 132 at r2 (raw file):

lookup_unique | Lookup Unique | Lookup table unique values | If unowned | Yes | 10
numeric | Functional Unique | Identity | Yes | Yes | 0
mumeric_static_map | Functional Unique | A JSON file that maps input values to keyspace IDs | Yes | No | 1

numeric_static_map instead of mumeric_static_map

Comments from Reviewable


Custom Sidebar animation

Howdy,
Is there a way to override thee default animation of the sidebar? (it pulls from left to right)
I only see the following on the documentation:
animate	boolean	true	Animate the opening/closing of the sidebar.
I was wondering, since I'm doing some animations using angular2 api
Thanks,
e. Vazquez 😄

The animations are done using CSS due to limitations of Angular 2's animations API. If you want to override them, just use plain old CSS to have a different transition!
For reference: https://github.com/arkon/ng-sidebar/blob/master/src/sidebar.component.ts#L74

@arkon thanks, I was to set it set it to none or do a custom one with css animations
When you say angular2 animation limitations, what are you referring to ?
For what I've read and learn angular's 2 framework is using the standard Web Animations API, and there is a recommendation to use a polyfill for older browsers support
Regards,
e. Vazquez

I wasn't able to dynamically change the animation state definitions, so I couldn't implement docked mode properly. I was actually using Angular's animation API before, but reverted back to CSS because of that. If they do implement it in the future, I could switch back. We also still saw compatibility issues (#28).


Scrolling bug when selecting new region/state

The results page scrolls to the bottom of the page when states near the end of the alphabet (dropdown menu) are selected.

┆Issue is synchronized with this Trello card by Unito

mmmm I think we fixed this. @bluejayfang can you reproduce it anymore?


chore: use custom PAT for release-plz actions

Custom PATs must be used to allow GitHub to run actions on automated PRs

coverage: 76.094%. remained the same
when pulling 414e12ff035fba525eee669a48f0a96f10b49325 on chore/ci/release-plz-custom-token
into 65c996256aafd947ab2ea7c47616b1fab3b3eb1f on main.


Fix GYB doctests on Windows

These tests fail because we hardcoded unix paths.
Windows:

/dummy.file -> C:/dummy.file

Unix:

/dummy.file -> /dummy.file

This caused two test failures:
**********************************************************************
File "gyb.py", line 1012, in __main__.execute_template
Failed example:
    print(out, end="")
Expected:
    //#sourceLocation(file: "/dummy.file", line: 1)
    Nothing
    //#sourceLocation(file: "/dummy.file", line: 4)
    0
    //#sourceLocation(file: "/dummy.file", line: 4)
    1
    //#sourceLocation(file: "/dummy.file", line: 4)
    2
Got:
    //#sourceLocation(file: "C:\dummy.file", line: 1)
    Nothing
    //#sourceLocation(file: "C:\dummy.file", line: 4)
    0
    //#sourceLocation(file: "C:\dummy.file", line: 4)
    1
    //#sourceLocation(file: "C:\dummy.file", line: 4)
    2
**********************************************************************
File "gyb.py", line 1031, in __main__.execute_template
Failed example:
    print(out, end="")
Expected:
    //#sourceLocation(file: "/dummy.file", line: 1)
    Nothing
    //#sourceLocation(file: "/dummy.file", line: 6)
    [0, 1, 2]
Got:
    //#sourceLocation(file: "C:\dummy.file", line: 1)
    Nothing
    //#sourceLocation(file: "C:\dummy.file", line: 6)
    [0, 1, 2]
**********************************************************************
1 items had failures:
   2 of   6 in __main__.execute_template
***Test Failed*** 2 failures.

@swift-ci please smoke test

@hughbe I'm not certain if this is the best way to address these.  IIRC, Windows tools like VC++ are resilient to the use of unix-style paths, and probably our tools ought to follow suit on Windows.

Will address your comments. Sorry, I thought this was fairly uncontroversial and not worth wasting review time


Invalidating images in the dom diffing

Hi,
I am using Mithril to display a product catalog. In the product list page, I have small blocks that display the product image along with some description. When the page charges for the first time, you see white blocks along with text, then images appear.
When I change the sort order, I display different products. Mithril dom diffing does its job just fine and will reuse existing DOM to display the new data (including IMG tags where it will only change the SRC attribute). Hence, all descriptions will change instantly, but the old images still show until the new one starts to load which may take a while depending on the connection of the user.
This leads to a page where wrong pictures are shown.
I am struggling to find a way to "invalidate" those images when the diffing occurs. I could display a blank image, a spinning wheel, ... anything will do as long as those old images go away.
Of course, I could scan the whole DOM to invalidate those images by hand. I'd rather set an option into mithril to not reuse IMG objects in its diffing if the SRC differs.
I have no idea if that makes sense.

Hi @pieroxy — can I just say thanks for lz-string — it proved invaluable in my last Mithril app! :)
Frankly I'm surprised that the browser would keep displaying the old image while it loads the new src. I would expect it to display nothing as soon as the src changes.
To my mind the simple solution is to force Mithril to create new DOM elements for each individual image. This can be achieved using the key property:
m( 'img', {
  src : imgSrc,
  key : imgSrc
} )

The source is the very thing that uniquely identifies the image, therefore there is no need to create a new reference for this.
This solution would be less desirable when you are expecting the same images to re-appear in the list in different position, since Mithril only recycles keyed elements if they keep a unique parent element between draws. In this case, it may be desirable to associate the key with the list item that contains the image:
m( 'li.item', {
  key : imgSrc
},
  m( 'img', {
    src : imgSrc
  } )
)

This presents its own problems, again depending on the dynamic behaviour of the list: whereas previously list items would be recycled aggressively, now they are destroyed and created depending on identity. So it would work very well for dynamically sorted list, not so well for a dynamically filtered list.
The complicated solution that doesn't force opinionated DOM recycling logic would be to use DOM scripting within the view via the config method:
var loadingSrc = 'data:image/gif;base64,R0lGODlhAQABAIAAAP///wAAACH5BAEAAAAALAAAAAABAAEAAAICRAEAOw=='

m( 'img', {
  src    : imgSrc,
  config : function( element, initialised, state ){
    // If the current state hasn't been recorded
    // (and it won't have the first time we get here)
    if( imgSrc != state.oldSrc ){
      // Load the new source programmatically
      var newImg = new Image( imgSrc )

      // If the source has not loaded synchronously
      if( !newImg.complete ){
        // Then display placeholder image in place
        element.src = loadingSrc

        // And display the desired source when it loads
        newImg.onload = function apply(){
          element.src = imgSrc
        }
      }

      // Record the current source for internal logic
      state.oldSrc = imgSrc
    }
  }
} )

lz-string is also useful to me ;-) You're welcome.
Back on topic, that looks fantastic. I'll test it soon and then close the ticket. Thanks a bunch.

Well, it works great. I guess it's another case of RTFM...
Thanks a bunch anyways :-)


Bad “vendor” folder embedded in .phar throws an error "Class not found"

Hello,
I don't understand how the castor composer command works when transforming the application into PHAR.
I used castor composer require and I have a .castor/vendor folder with my dependencies.

But when I convert the application to PHAR, it is not this folder which is embedded but the vendor which is at the root of the project

Because of this, the compiled application does not work because the dependencies do not exist
What didn't I understand? Is there a problem ?
Thanks 🙏

Hey can you try https://github.com/jolicode/castor/pull/481 ?
It should fix your issue.
In fact we need to include this vendor directory since we need castor and our dependencies to make castor work on your repacked application.
We are not sure about implication of having to include both of those directories so instead we only copy castor.composer.json file

Thanks @joelwurtz .
Sorry, it doesn't work.
composer.json
{
  "require": {
    "jolicode/castor": "dev-main#f4e0e8a25f950b738ff3834592ea61f34bdb6306"
  },
  "config": {
    "allow-plugins": {
      "php-http/discovery": true
    }
  }
}

composer update

repack --app-name=$name --app-version=$version

❌ bad vendor folder

❌ Class not found

Was I wrong?

Should be good with https://github.com/jolicode/castor/pull/485
I reproduce the problem and fix it with that
However i'm wondering if you should use this approach, in this scenario you should use "composer" instead of "castor composer" i don't think it add any value to split the two ?

Indeed, now both files are imported and I no longer have a problem.
Thanks.
I thought that the "castor composer" version allowed me to choose what is useful for my application so as not to include the "vendor" which allows "castor" to work and compile for example.
But if both are encapsulated now, I don't quite understand. Especially since I was doing things differently before and you advised me to change: https://github.com/jolicode/castor/issues/456#issuecomment-2098527406
Do you have an easy way to choose between castor composer and composer ?
Thanks

With our current philosophy it doesn't change much to include castor dep directly in your composer when you repack. As in both case we don't provide the composer command into the repacked application as we think this approach if for people that don't want it to change overtime.
Also it should be safer since you ensure that dependencies are compatible between each others.
We may in the future allow composer in the repacked application and not include files from ".castor" directory, so it would provide a middle step where you allow the dependencies on your castor files to change. But IMO this requirement is niche and don't think we will do that in the near future.

Alright, but I don't quite understand when to use castor composer instead of composer.
Thanks for this fix and this advice 👍


feat(combobox): focusEl logic implemented

This PR fix #744. Added focusEl v-model, if there is some additional questions feel free to ask 🙌
https://github.com/radix-vue/radix-vue/assets/82209198/c9ad99be-8ded-4224-bff6-4cee09d39a14

@zernonia thanks for your great work on this project ❤  When you have some free time can you take a look if this will be ok or maybe something to change? I don't know if we need focusEl prop, or just emit.
Mark this PR as Draft because it needs some more work but seems good for me)

Thanks for the PR @romanhrynevych .. This will be implemented in v2 (as labelled in the issue above) when wrapping Combobox with Listbox component. So I will not be merging this ya 😁


Is there any limitation on Form Select?

Discussed in https://github.com/orchidsoftware/platform/discussions/2422

Originally posted by archlicher November  2, 2022
Hi,
I am facing a problem with Form Select - how can I add more than 50 items to it with package monarobase/country-list?
Thank you

Hi @jigsaw075 Can you please describe what you want to achieve

I would guess he's trying to add more than 50 values to the Select. I have a Select with a lot of values, but it only displays up to...something like 50 values, but if I start typing a value I know is beyond what I see, it will allow me to select it.

sorry, i missed the notification. i'm trying to list all counties with select option but it doesn't show all the values like @Mazena86. here is the code.
               Select::make('country_code')                     ->title("Country")                     ->options(CountryListFacade::getList())                     ->empty('Select...')                     ->required(),

Oh, I can see where it comes from. Tom select official documentation limits amount of displayed items to 50 (maxOptions value)

maxOptions | The max number of options to display in the dropdown. Set maxOptions to null for an unlimited number of options. Default: 50

I think this issue was referring to the same behavior as described here: https://github.com/orchidsoftware/platform/issues/2478


Remove generated symbol tests

Currently the conformance tests include some tests with generated symbol names following the convention partiql-lang-kotlin and the spec use (using _1, _2,...).
The spec states in section 6.3.1 that

SQL and PartiQL do not provide a standard convention

Since there's no mention of the actual generated names, these conformance tests should be removed or moved to the "extended" directory of tests.

Tests not explicitly testing the generated name (example test) should probably add aliases so the generated symbols aren't necessary.


Enable setting configuration options for local testing

Adds ability to set configuration options via dev-config.yml
PS: With modification of CONTRIBUTING.md to update instructions, there are some linter changes included in this PR

Validation:

With an external config file:

@cnagadya please take a look and let me know what you think!

Looks great. Just two small (script vs scripts) typos in scan_pr


[5.6] Fire event when logger is resolved

This will allow to easily attach additional data to logger creating LoggerResolved event listener. For example I often attach request url or artisan command and so on to get more information to track the potential problem.

Is there any use case that that you experience not possible right now?

@crynobone I was not customizing logger in 5.6 yet (did it in previous releases) but for example how can I now add request url to all logger? I'm using stack as default logger and in channels I have set both daily and slack so I would like to have in both of them included request url.

You can already listen to Illuminate\Foundation\Http\Events\RequestHandled or Illuminate\Routing\Events\RouteMatched.

And how does it help adding current request url to logger? In those events I don't have valid loggers instances I believe.

In those events I don't have valid loggers instances I believe.

Logger are resolved at very core of Illuminate\Foundation\Application construction, see https://github.com/laravel/framework/blob/5.6/src/Illuminate/Foundation/Application.php#L188. While creating logger instance entirely depends on when it was first requested on your app which might be before or after request is resolved.


LinkedIn Version 2 API requirements

Description:
LinkedIn has published this update last December:
https://engineering.linkedin.com/blog/2018/12/developer-program-updates
According to the document, the v1 API will cease to function as of March 1, 2019.
Is there any update on this or is this expected to cause problems with this plugin?   Alternatively, is there another WSO2 IS "owned" plugin to support this?
Affected Product Version:
1.0.3

Hello @morganm00
pull request with support new api version
https://github.com/wso2-extensions/identity-outbound-auth-linkedIn/pull/13

Relates to https://github.com/wso2/product-is/issues/5953


add "HasSubtoken"

While coding I noticed you were right. This is still good to have.  This way I just need to check it and not make a delegate for the event and another property.

For what it's worth, after the recent changes, modules will load only after their subtoken has been acquired, so you probably shouldn't have to listen on the event like you mentioned.
This is probably still good to have, though.


Fix bitfields on big-endian machines.

Fixes #1340

Sorry for the lag here, this looks fine but the tests need to be updated. I'll get to it ASAP.

:pushpin: Commit a642894 has been approved by emilio

@bors-servo r+

:hourglass: Testing commit a64289400ccbd58d12341da26dd1f3bebb17f845 with merge c3955ddeac236f4a6b967d5b8ddc8dc21238d152...

:sunny: Test successful - status-travis
Approved by: emilio
Pushing c3955ddeac236f4a6b967d5b8ddc8dc21238d152 to master...


Raspberry Pi Pico W Support?

Hello all, I use this with an ESP-32, but I have a friend that has a whole bunch of Raspberry Pi Pico W's. It would be much appreciated if someone was able to port this project and make it work with the Pi Pico W.

Dupe of #4, sorry I am not interested in it.
@RapierXbox had added something in an MR, maybe you can use that to do something: https://github.com/ckcr4lyf/EvilAppleJuice-ESP32/pull/28/commits/72a769b587268a38be28bfc30c11c13afa21d6dd


Missing checksum in test_file.json caused pytest to fail

pytest failed in the latest 3.7.0
> =========================== short test summary info ============================
> FAILED tests/test_export.py::TestExportColors::test_all_templates - KeyError: 'checksum'
> FAILED tests/test_export.py::TestExportColors::test_css_template - KeyError: 'checksum'

Both tests in test_export.py use export.every(), and the function call chain is as followed:
https://github.com/eylles/pywal16/blob/784d0b9aaec945478342601258626372baae806b/tests/test_export.py#L41
https://github.com/eylles/pywal16/blob/784d0b9aaec945478342601258626372baae806b/pywal/export.py#L120-L122
https://github.com/eylles/pywal16/blob/784d0b9aaec945478342601258626372baae806b/pywal/export.py#L75-L85
#79 added exporting checksum in flatten_colors(), which requires that the imported test file must have a checksum field. Considering that test_file.json is used by other tests, perhaps the easiest way to fix it is to replace the test_file.json used in test_export.py with test_file3.json?
https://github.com/eylles/pywal16/blob/784d0b9aaec945478342601258626372baae806b/tests/test_export.py#L11

yeh, that is certainly a really good idea, overlooked this since i wanted to put out a release as soon as possible, doesn't help that setuptools 75.4 removed the test command and that i decided to leave the update of the test suite and change to a robust test tooling like tox for the next release cycle...
oh well will have to put out 3.7.1 in some minutes...


Update docs to provide clearer instructions on configuration

I couldn't get the github extension to work. After much experimentation I figured there must be something wrong with the configuration, so I started reading through the docs for the other extensions one by one until I found one (pull references) which actually showed how configuration is supposed to work. Ten seconds later, I had a working Github extension.
If all the extensions use the same configuration syntax, you might consider writing up a very short explainer. You could even link it from the individual extension docs.
I'm happy to submit a PR with these changes, but would need you to specify exactly how configuration works and how you'd want to incorporate the information into the docs (put it on the index page? give it its own page? link to it from individual extensions docs pages?) so it might actually be less work for you to just do yourself. Whatever you prefer.

I started configurations using the Roam Attributes, but recently have been transitioning away to just have tree configuration and not require attributes. Because of this, I would rather just improve the pull references and GitHub docs to be a lot clearer


Link Gerrit credentials to IDEA projects instead of applying them globally

I work on dozens of IDEA projects and need Gerrit only for a single one, a forked Eclipse project. Even there, I only need it when contributing one of my bugfixes to the upstream project because Eclipse requires PRs in Gerrit. Nevertheless, the Gerrit plugin always tries to connect to the server when starting the IDE or re-opening unrelated projects. It also shows me notifications about pending reviews completely out of context in projects not using Gerrit. This becomes even more useless when I get curious, opening the Gerrit view, but seeing nothing of course, due to the fact that 99% of my projects do not use Gerrit and my pending reviews etc. are only displayed when I open the right project with the right Git connection.
I think that this is a design flaw. Gerrit server URLs and credentials should be per project, so that the plugin does not do anything when the corresponding project does not use Gerrit but e.g. GitHub or whatever SCM. And what if two different OSS or commercial projects use different Gerrit servers, for example one company server and one OSS one for Eclipse?

I think this is a duplicate of #159. If you do not agree, please let me know.

I agree. I am going to transfer the issue text as a comment to the other issue.


Unclear ExprSort::Cast target type

In the structure of a cast expression we see that target field denotes the type to convert that expression to.
In the document target has type Index, but doesn't mention where to look it up.
Should target be of type TypeIndex or what should this Index reference?

Should target be of type TypeIndex or what should this Index reference?

Yes, this is a typo.  It should be TypeIndex.


Update Posts “markdown-syntax”

Automatically generated by Netlify CMS

👷 Deploy Preview for jchendriks-s5 processing.
🔨 Explore the source changes: 5a0336ed8839296ea7b2507ab41f6b9277642bce
🔍 Inspect the deploy log: https://app.netlify.com/sites/jchendriks-s5/deploys/61c0926020eae900073633f4


Update state.zh.md

Documentation

fix a typo

@sdk2 thanks for your contribution to fix the typo. Currently, the FoldingState has been deleted in FLINK-17376, the documentation about FoldingState has been removed. could you please close this pr.
you can find other open issues here, and here for chinese-documentation-translation-tasks


PEnum use name() instead of toString()

Hi Rob,
using enums in a typequery uses toString() to geht the enum representation. This ist not working if you override the toString() in an enum.
To reproduce:
public enum Type {
        CUSTOMER("Kunde"),
        private final String caption;
        private Type(String caption) {
            this.caption = caption;
        }
        @Override
        public String toString() {
            return caption;
        }
    }

And the Query:
new QCustomer().type.eq(Customer.Type.CUSTOMER).findUnique();
new QCustomer().type.in(Customer.Type.CUSTOMER).findUnique();

Will result in a query where the type="Kunde" and not type="CUSTOMER".

This pull request does not look appropriate.  The actual bind value depends on how the Enum is mapped and that can be by name, ordinal or a mapped value via @EnumValue.  The determination of that bind value happens later (not as part of typequery).
So there will be some other problem but this pull request is not appropriate.

Ok, no problem. Do you have a hint for me, where I have to search for a better solution?

I'll see if there are tests for all 3 forms of enum mapping.
You can try adding:
@Enumerated(EnumType.STRING)
Or explicit mapping via @EnumValue ...
public enum Status {
@EnumValue("N")
NEW,
@EnumValue("A")
APPROVED,
@EnumValue("S")
SHIPPED,
@EnumValue("C")
COMPLETE
}
On 30 September 2015 at 09:00, ossd<EMAIL_ADDRESS>wrote:

Ok, no problem. Do you have a hint for me, where I have to search for a
better solution?
—
Reply to this email directly or view it on GitHub
https://github.com/ebean-orm/avaje-ebeanorm-typequery/pull/10#issuecomment-144172919
.

Ok, but there is an @Enumerated on my field:
    @Enumerated(EnumType.STRING)
    private Type type;

Where is the test case? Is there a test case with @Enumerated(EnumType.STRING) and an overridden toString() in the enum?

This was logged as https://github.com/ebean-orm/avaje-ebeanorm/issues/580 ... will be fixed in 7.1.2

So this merge request is not correct in that the problem was never in the querybean but instead in ebean as per https://github.com/ebean-orm/avaje-ebeanorm/issues/580
Closing.


Check whether there’s anything important there, and delete the old master branch

copied some stuff, removed branch master


Change the API to support filesystem::path if this feature is available

When using unicode path under windows, there are some issues and files couldn't not be retrieved/accessed correctly. The way to fix this is to use filesystem::path to delegate path encoding to std library.

@dimitri-tdg Wow, thanks for doing this work! I think this looks fine as-is with 1 minor comment that I left relating to undefining the defines. I'll need to update the viewer application to account for the breaking change and I'll want to change my .clang-format to use indention for the #defines but I'll check those in afterwards on my own I think.

Oh you're right @jessey-git! I didn't modify the viewer application to support this modification. I focused on unit tests and validation tests only. I can check to integrate this into the same PR but I'm not super comfortable with Windows graphical API :sweat_smile:
Anyway, if you want to pack all modifications (code + utests + viewer application), feel free to modify/reuse my proposal!


Add interface / convenience functionality concerning result file handling needed by SAF

📝 Description of the feature

[ ] To ParametricSystem wrapper class, add interface / convenience functionality to

Obtain path to result OMDB file (resemble functionality of OWS "/omdb" endpoints)
Generate and store a CSV/Json file containing result designs

[ ] To Node wrapper class, add functionality to

Obtain information about node result files:

Path on filesystem
Registered file ID and Comment
Status (exists or not)
File size
Last modified

[ ] To Project wrapper class, add functionality to

Obtain information about project result files:

Path on filesystem
Registered file ID and Comment
Status (exists or not)
File size
Last modified

Time estimation: 1PW
💡 Steps for implementing the feature
No response
🔗 Useful links and references
According tasks in SAF:

https://github.com/Solution-Applications/solution-enablement-product-management/issues/484
https://github.com/Solution-Applications/solution-enablement-product-management/issues/515

@asbfall @iazehaf FYI

@sebastian-wolff FYI

Hi Ronny, could you please clarify, what exactly you mean by result files? Do you mean registered files that I can obtain by basic_project_info query for the project? For nodes I can then use get_actor_info to obtain uids of registered files associated with individual nodes and filter whole list obtained by basic_project_info.
@rfahlberg

@PanekOndrej Yes, exactly. The "result  files" are the centrally registered files, which are set to { "usage": "Output file" }. The global list can be obtained using "basic_project_info". If a registered file is not associated to (use by) a certain node, it should be accessible via pyosl "Project" interface. If a registered file is associated to (use by) a certain node, it should be accessible via pyosl "Node" interface. For nodes you can use get_actor_info to obtain uids of used registered files.

@PanekOndrej looks very good to me. Please go ahead with unit tests and PR.

@iazehaf Please confirm the additions are sufficient for SAF.


Implement Linkedlist Data Structure in C.

This C program implements a singly linked list, a dynamic data structure. It comprises nodes, each holding data and a pointer to the next node. The Node structure is defined to create and initialize nodes. Three insertion methods are provided: at the beginning, end, or a specified position. Deletion is supported based on node value. The program includes a function to print the linked list. User interaction is facilitated through a menu-driven interface. Error handling ensures graceful handling of invalid operations. This implementation offers a versatile tool for efficient dynamic data management, crucial for scenarios with changing data requirements.

@vivek5200 remove credits from code and make more commit at a time


Cannot get input element value

Hi all,
I am beginner in angular 2
I develop web chat app using angular 2.Pls refer this http://imgur.com/dpnLSSv
I need dont display repeated value.Because I will check two variable.
below my html code

{{chat.date | amDateFormat:'LL'}}

    <input #myname type="hidden" value={{chat.date}}>

      {{chat.path_text}}
      {{chat.date | amDateFormat:'hh:mmA'}}

      {{chat.message_text}}
      {{chat.date | amDateFormat:'hh:mmA'}}

So i Bind the chat.date value using input tag.i get input element value using id.below my typescript file.
import { Component, Inject, ViewChild, ElementRef, AfterViewInit } from '@angular/core';

export class ChatPage implements AfterViewInit {
  @ViewChild('myname') input: ElementRef;
  constructor(public modalCtrl: ModalController, public navCtrl: NavController) { }
  ngAfterViewInit() {
    console.log(this.input.nativeElement.value);
  }
}

i am getting this error
Cannot read property 'nativeElement' of undefined
How to fix this issue.or any other way to find slutions.I need same values are does not show.
.I tried to many way.I have no idea.
Kindly Advice me,
Thanks & Regards

This looks like a better fit for the support forums than a GitHub issue.

i have the same problem .  can any one sovle this

Hello! Thanks for opening an issue with us! As this seems like more of a support question i will urge that you ask this question on our forum or on our slack channel. Thanks for using Ionic!


fix bug of implication of 'addDelegate:(id)delegate beforeDelegate:(i…

…d)otherDelegate' and 'addDelegate:(id)delegate afterDelegate:(id)otherDelegate'

I can not understand your changes why the object need be hisself delegate?
If you have these unique needs，you can implemented a different method in a custom class.

I think if the delegate is specified to 'self' in the method,then what is the use of the parameter 'delegate'?


Vue Component Preview doesn't work on Windows if a path has spaces in it

PS C:\Path With Spaces In It> cd c:\Path With Spaces In It\source
Set-Location : A positional parameter cannot be found that accepts argument 'With'.
+ cd c:\Path With Spaces In It ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : InvalidArgument: (:) [Set-Location], ParameterBindingException
    + FullyQualifiedErrorId : PositionalParameterNotFound,Microsoft.PowerShell.Commands.SetLocationCommand

PS C:\Path With Spaces In It> node "c:\\Users\\me\\.vscode\\extensions\\vue.volar-0.40.13-win32-x64\\dist\\preview-bin\\vite.js" --port=3333
node:internal/modules/cjs/loader:936
  throw err;
  ^

Error: Cannot find module 'vite/package.json'
Require stack:
- c:\Users\me\.vscode\extensions\vue.volar-0.40.13-win32-x64\dist\preview-bin\vite.js
    at Function.Module._resolveFilename (node:internal/modules/cjs/loader:933:15)
    at Function.resolve (node:internal/modules/cjs/helpers:108:19)
    at Object.<anonymous> (c:\Users\me\.vscode\extensions\vue.volar-0.40.13-win32-x64\dist\preview-bin\vite.js:7:29)
    at Module._compile (node:internal/modules/cjs/loader:1101:14)
    at Object.Module._extensions..js (node:internal/modules/cjs/loader:1153:10)
    at Module.load (node:internal/modules/cjs/loader:981:32)
    at Function.Module._load (node:internal/modules/cjs/loader:822:12)
    at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:81:12)
    at node:internal/main/run_main_module:17:47 {
  code: 'MODULE_NOT_FOUND',
  requireStack: [
    'c:\\Users\\me\\.vscode\\extensions\\vue.volar-0.40.13-win32-x64\\dist\\preview-bin\\vite.js'
  ]
}

This results in large amounts of terminated terminals.

Is there a way to turn this plugin off?

Is there a way to turn this plugin off?

You can close the component preview tab and reload vscode window.


Update

Exclude tests which fail on OJ9 same way they fail on HS

@ben-walsh - can you please update the link to point to the open #602 issue? (instead of 593?)

@smlambert Done.


[5.2] Changed the Validator::validateUrl method to use the Symfony regex

This is in response to #10149, with this the PR from @franzliedke should pass based on @taylorotwell suggestion to use the Symphony regex for URL validation.
This is my first PR to Laravel, so I'm not sure I did this 100% correctly... apologies if it's wrong.

@scrothers would be useful if you include the "failing" tests from #10149 to ensure that this solve it.

Good point, but I made one change to the tests that didn't make sense.
The url 'http://laravel.com/?' in the original issue, is listed as "invalid" however, that is most definitely a valid url. So I marked that as a valid url.

Did you remove it from the invalid list because it looks like its still in there?

You're looking at 'http://laravel.com?' not 'http://laravel.com/?', notice the last slash in particular.

Ah yeah sorry didn't see there wasn't a slash in it.

I think the idea was to copy the regex, not include the Symfony library, but obviously there are also benefits to that approach. :)

@GrahamCampbell I added it to the other composer.json as well. Should build fine in Travis in a few minutes.

I don't think we should pull in the component. I think we should just lift the regex.

@taylorotwell Done, I removed the inclusion of the Symfony library and also that sprintf by just including the URIs into the regex itself. I considered adding the regex to the class as a constant, like in Symfony, but I felt that was only going to serve to make the code messy, so I included the regex into the method. Open to suggestion there, that decision was made based on code organization only and no technical reason.

Thank you everyone. :)


Connection Refused - pocketbase on linux server

Hello!, I'm have this small cloud server (ubuntu v18 and also try v20), and I can't  connect  to simple /_

Firewall ports TCP/UDP are open 80, 8090, 433 etc...

Oh, It could be a lot of things. There is not enough info to debug this.
My guess is that there is a firewall (could be a separate service from your vps) that blocks the 8090 port or there is some local network configuration that is mising. You could try several things:

start with --http="<IP_ADDRESS>:8090", eg. ./pocketbase serve --htp="<IP_ADDRESS>:8090"
use 80 port eg. ./pocketbase serve --htp="<IP_ADDRESS>:80" and try to access directly the ip of your server
contact your vps provider support

Perfect, thank You very much. I will try this later 👌

I tried this and it worked!

the previous two (with localhost) did not work


Snapshot versions in place then refresh for workflows (WIP)

Needs tests and to verify that this is the expected behavior.
Seems like we may want to add an error when someone tries to mutate a frozen version from the webservice. Also, the "upsert version" endpoints might be a better way of doing this instead of modifying a workflow in place.

Screenshot would be helpful

You can make draft PR for WIP stuff