MetaDrive env: "AttributeError: 'NoneType' object has no attribute 'reset'"

Hello,
I am trying to run an algorithm on a MetaDrive environment as follows:
python marl/main.py --algo_config=mappo --env_config=metadrive with env_args.map_name=Roundabout

I have installed the MetaDrive environment as per the documentation:
pip install metadrive-simulator==0.2.3

But I get the following error after training for some time:
2023-01-31 09:56:28,733 ERROR trial_runner.py:924 -- Trial MAPPOTrainer_metadrive_Roundabout_45631_00000: Error processing event.
Traceback (most recent call last):
  File "/home/oscar/anaconda3/envs/marllib/lib/python3.8/site-packages/ray/tune/trial_runner.py", line 890, in _process_trial
    results = self.trial_executor.fetch_result(trial)
  File "/home/oscar/anaconda3/envs/marllib/lib/python3.8/site-packages/ray/tune/ray_trial_executor.py", line 788, in fetch_result
    result = ray.get(trial_future[0], timeout=DEFAULT_GET_TIMEOUT)
  File "/home/oscar/anaconda3/envs/marllib/lib/python3.8/site-packages/ray/_private/client_mode_hook.py", line 105, in wrapper
    return func(*args, **kwargs)
  File "/home/oscar/anaconda3/envs/marllib/lib/python3.8/site-packages/ray/worker.py", line 1625, in get
    raise value.as_instanceof_cause()
ray.exceptions.RayTaskError(AttributeError): ray::MAPPOTrainer.train_buffered() (pid=20470, ip=<IP_ADDRESS>, repr=MAPPOTrainer)
  File "/home/oscar/anaconda3/envs/marllib/lib/python3.8/site-packages/ray/tune/trainable.py", line 224, in train_buffered
    result = self.train()
  File "/home/oscar/anaconda3/envs/marllib/lib/python3.8/site-packages/ray/rllib/agents/trainer.py", line 682, in train
    raise e
  File "/home/oscar/anaconda3/envs/marllib/lib/python3.8/site-packages/ray/rllib/agents/trainer.py", line 668, in train
    result = Trainable.train(self)
  File "/home/oscar/anaconda3/envs/marllib/lib/python3.8/site-packages/ray/tune/trainable.py", line 283, in train
    result = self.step()
  File "/home/oscar/anaconda3/envs/marllib/lib/python3.8/site-packages/ray/rllib/agents/trainer_template.py", line 240, in step
    evaluation_metrics = self.evaluate()
  File "/home/oscar/anaconda3/envs/marllib/lib/python3.8/site-packages/ray/rllib/agents/trainer.py", line 958, in evaluate
    self.evaluation_workers.local_worker().sample()
  File "/home/oscar/anaconda3/envs/marllib/lib/python3.8/site-packages/ray/rllib/evaluation/rollout_worker.py", line 753, in sample
    batches = [self.input_reader.next()]
  File "/home/oscar/anaconda3/envs/marllib/lib/python3.8/site-packages/ray/rllib/evaluation/sampler.py", line 103, in next
    batches = [self.get_data()]
  File "/home/oscar/anaconda3/envs/marllib/lib/python3.8/site-packages/ray/rllib/evaluation/sampler.py", line 233, in get_data
    item = next(self._env_runner)
  File "/home/oscar/anaconda3/envs/marllib/lib/python3.8/site-packages/ray/rllib/evaluation/sampler.py", line 586, in _env_runner
    base_env.poll()
  File "/home/oscar/anaconda3/envs/marllib/lib/python3.8/site-packages/ray/rllib/env/base_env.py", line 422, in poll
    obs[i], rewards[i], dones[i], infos[i] = env_state.poll()
  File "/home/oscar/anaconda3/envs/marllib/lib/python3.8/site-packages/ray/rllib/env/base_env.py", line 478, in poll
    self.reset()
  File "/home/oscar/anaconda3/envs/marllib/lib/python3.8/site-packages/ray/rllib/env/base_env.py", line 528, in reset
    self.last_obs = self.env.reset()
  File "/home/oscar/msc/MARLlib/envs/base_env/metadrive.py", line 69, in reset
    original_obs = self.env.reset()
  File "/home/oscar/anaconda3/envs/marllib/lib/python3.8/site-packages/metadrive/envs/base_env.py", line 291, in reset
    self.engine.reset()
AttributeError: 'NoneType' object has no attribute 'reset'

Any guidance would be appreciated,
Thanks.

This is not a bug. We don't support MAPPO in Metadrive. Only independent learning algorithms (e.g. IPPO) are available.
Main reason: the agent number is not fixed in metadrive (e.g. crashed cars are wiped out before the end of the game). Thus the input dimension of centralized critic function is always changing. This is unacceptable.
There may exist solutions such as mean field-based MAPPO. While it goes far beyond MARLlib's original intention on building algorithms which is not too task specific.
You can try --algo_config=ppo to test if the metadrive installation is ok.
Any further concern is welcome.

This is not a bug. We don't support MAPPO in Metadrive. Only independent learning algorithms (e.g. IPPO) are available.
Main reason: the agent number is not fixed in metadrive (e.g. crashed cars are wiped out before the end of the game). Thus the input dimension of centralized critic function is always changing. This is unacceptable.
There may exist solutions such as mean field-based MAPPO. While it goes far beyond MARLlib's original intention on building algorithms which is not too task specific.
You can try --algo_config=ppo to test if the metadrive installation is ok.
Any further concern is welcome.

I see, thank you for the clarification on algorithms supported in MetaDrive.
As suggested I tried the IPPO algorithm, but I get the same error.
Failure # 1 (occurred at 2023-02-03_09-35-27)
Traceback (most recent call last):
  File "/home/oscar/anaconda3/envs/marllib/lib/python3.8/site-packages/ray/tune/trial_runner.py", line 890, in _process_trial
    results = self.trial_executor.fetch_result(trial)
  File "/home/oscar/anaconda3/envs/marllib/lib/python3.8/site-packages/ray/tune/ray_trial_executor.py", line 788, in fetch_result
    result = ray.get(trial_future[0], timeout=DEFAULT_GET_TIMEOUT)
  File "/home/oscar/anaconda3/envs/marllib/lib/python3.8/site-packages/ray/_private/client_mode_hook.py", line 105, in wrapper
    return func(*args, **kwargs)
  File "/home/oscar/anaconda3/envs/marllib/lib/python3.8/site-packages/ray/worker.py", line 1625, in get
    raise value.as_instanceof_cause()
ray.exceptions.RayTaskError(AttributeError): ray::IPPOTrainer.train_buffered() (pid=39673, ip=<IP_ADDRESS>, repr=IPPOTrainer)
  File "/home/oscar/anaconda3/envs/marllib/lib/python3.8/site-packages/ray/tune/trainable.py", line 224, in train_buffered
    result = self.train()
  File "/home/oscar/anaconda3/envs/marllib/lib/python3.8/site-packages/ray/rllib/agents/trainer.py", line 682, in train
    raise e
  File "/home/oscar/anaconda3/envs/marllib/lib/python3.8/site-packages/ray/rllib/agents/trainer.py", line 668, in train
    result = Trainable.train(self)
  File "/home/oscar/anaconda3/envs/marllib/lib/python3.8/site-packages/ray/tune/trainable.py", line 283, in train
    result = self.step()
  File "/home/oscar/anaconda3/envs/marllib/lib/python3.8/site-packages/ray/rllib/agents/trainer_template.py", line 240, in step
    evaluation_metrics = self.evaluate()
  File "/home/oscar/anaconda3/envs/marllib/lib/python3.8/site-packages/ray/rllib/agents/trainer.py", line 958, in evaluate
    self.evaluation_workers.local_worker().sample()
  File "/home/oscar/anaconda3/envs/marllib/lib/python3.8/site-packages/ray/rllib/evaluation/rollout_worker.py", line 753, in sample
    batches = [self.input_reader.next()]
  File "/home/oscar/anaconda3/envs/marllib/lib/python3.8/site-packages/ray/rllib/evaluation/sampler.py", line 103, in next
    batches = [self.get_data()]
  File "/home/oscar/anaconda3/envs/marllib/lib/python3.8/site-packages/ray/rllib/evaluation/sampler.py", line 233, in get_data
    item = next(self._env_runner)
  File "/home/oscar/anaconda3/envs/marllib/lib/python3.8/site-packages/ray/rllib/evaluation/sampler.py", line 586, in _env_runner
    base_env.poll()
  File "/home/oscar/anaconda3/envs/marllib/lib/python3.8/site-packages/ray/rllib/env/base_env.py", line 422, in poll
    obs[i], rewards[i], dones[i], infos[i] = env_state.poll()
  File "/home/oscar/anaconda3/envs/marllib/lib/python3.8/site-packages/ray/rllib/env/base_env.py", line 478, in poll
    self.reset()
  File "/home/oscar/anaconda3/envs/marllib/lib/python3.8/site-packages/ray/rllib/env/base_env.py", line 528, in reset
    self.last_obs = self.env.reset()
  File "/home/oscar/msc/MARLlib/envs/base_env/metadrive.py", line 69, in reset
    original_obs = self.env.reset()
  File "/home/oscar/anaconda3/envs/marllib/lib/python3.8/site-packages/metadrive/envs/base_env.py", line 291, in reset
    self.engine.reset()
AttributeError: 'NoneType' object has no attribute 'reset'

Note that the initial check for the environment installation seems OK.
Successfully registered the following environments: ['MetaDrive-test-v0', 'MetaDrive-validation-v0', 'MetaDrive-v0', 'MetaDrive-10envs-v0', 'MetaDrive-1000envs-v0', 'MetaDrive-training0-v0', 'MetaDrive-training1-v0', 'MetaDrive-training2-v0'].
+------------+----------------+-------------------------------------+-------------------------------------+----------------------------+
| Env_Name   | Check_Status   | Error_Log                           | Config_File_Location                | Env_File_Location          |
+============+================+=====================================+=====================================+============================+
| mpe        | Error          | No module named 'numpy.typing'      | envs/base_env/config/mpe.yaml       | envs/base_env/mpe.py       |
+------------+----------------+-------------------------------------+-------------------------------------+----------------------------+
| mamujoco   | Error          | No module named 'multiagent_mujoco' | envs/base_env/config/mamujoco.yaml  | envs/base_env/mamujoco.py  |
+------------+----------------+-------------------------------------+-------------------------------------+----------------------------+
| smac       | Error          | No module named 'smac'              | envs/base_env/config/smac.yaml      | envs/base_env/smac.py      |
+------------+----------------+-------------------------------------+-------------------------------------+----------------------------+
| football   | Error          | No module named 'gfootball'         | envs/base_env/config/football.yaml  | envs/base_env/football.py  |
+------------+----------------+-------------------------------------+-------------------------------------+----------------------------+
| magent     | Error          | No module named 'numpy.typing'      | envs/base_env/config/magent.yaml    | envs/base_env/magent.py    |
+------------+----------------+-------------------------------------+-------------------------------------+----------------------------+
| rware      | Error          | No module named 'rware'             | envs/base_env/config/rware.yaml     | envs/base_env/rware.py     |
+------------+----------------+-------------------------------------+-------------------------------------+----------------------------+
| lbf        | Error          | No module named 'lbforaging'        | envs/base_env/config/lbf.yaml       | envs/base_env/lbf.py       |
+------------+----------------+-------------------------------------+-------------------------------------+----------------------------+
| pommerman  | Error          | No module named 'pommerman'         | envs/base_env/config/pommerman.yaml | envs/base_env/pommerman.py |
+------------+----------------+-------------------------------------+-------------------------------------+----------------------------+
| hanabi     | Error          | No module named 'cffi'              | envs/base_env/config/hanabi.yaml    | envs/base_env/hanabi.py    |
+------------+----------------+-------------------------------------+-------------------------------------+----------------------------+
| metadrive  | Ready          | Null                                | envs/base_env/config/metadrive.yaml | envs/base_env/metadrive.py |

Could you pls share your params.json file for us to check?
By the way, does this bug appear after some training iterations or just early stop before the training starts?

Could you pls share your params.json file and list of packages you installed for us to check? By the way, does this bug appear after some training iterations or just early stop before the training starts?

Thanks for the reply. Sure, here's the params.json
{
  "batch_mode": "complete_episodes",
  "clip_param": 0.3,
  "entropy_coeff": 0.01,
  "env": "metadrive_Roundabout",
  "evaluation_interval": 10,
  "framework": "torch",
  "kl_coeff": 0.2,
  "lambda": 1.0,
  "lr": 0.0005,
  "model": {
    "custom_model": "Base_Model",
    "custom_model_config": {
      "algo_args": {
        "batch_episode": 10,
        "batch_mode": "complete_episodes",
        "clip_param": 0.3,
        "entropy_coeff": 0.01,
        "kl_coeff": 0.2,
        "lambda": 1.0,
        "lr": 0.0005,
        "num_sgd_iter": 5,
        "use_gae": true,
        "vf_clip_param": 10.0,
        "vf_loss_coeff": 1.0
      },
      "algorithm": "ppo",
      "env": "metadrive",
      "env_args": {
        "crash_done": true,
        "map_name": "Roundabout",
        "num_agents": 5,
        "start_seed": 0
      },
      "episode_limit": 200,
      "evaluation_interval": 10,
      "framework": "torch",
      "global_state_flag": false,
      "local_mode": false,
      "mask_flag": false,
      "model_arch_args": {
        "core_arch": "gru",
        "fc_layer": 1,
        "hidden_state_size": 256,
        "out_dim_fc_0": 128
      },
      "num_agents": 5,
      "num_cpus_per_worker": 1,
      "num_gpus": 1,
      "num_gpus_per_worker": 0,
      "num_workers": 0,
      "opp_action_in_cc": false,
      "policy_mapping_info": {
        "all_scenario": {
          "all_agents_one_policy": true,
          "description": "metadrive all scenarios",
          "one_agent_one_policy": true,
          "team_prefix": [
            "agent_"
          ]
        }
      },
      "seed": 123,
      "share_policy": "group",
      "space_act": "Box([-1. -1.], [1. 1.], (2,), float32)",
      "space_obs": "Dict(obs:Box([-0. -0. -0. -0. -0. -0. -0. -0. -0. -0. -0. -0. -0. -0. -0. -0. -0. -0.\n -0. -0. -0. -0. -0. -0. -0. -0. -0. -0. -0. -0. -0. -0. -0. -0. -0. -0.\n -0. -0. -0. -0. -0. -0. -0. -0. -0. -0. -0. -0. -0. -0. -0. -0. -0. -0.\n -0. -0. -0. -0. -0. -0. -0. -0. -0. -0. -0. -0. -0. -0. -0. -0. -0. -0.\n -0. -0. -0. -0. -0. -0. -0. -0. -0. -0. -0. -0. -0. -0. -0. -0. -0. -0.\n -0.], [1. 1. 1. 1. 1. 1. 1. 1. 1. 1. 1. 1. 1. 1. 1. 1. 1. 1. 1. 1. 1. 1. 1. 1.\n 1. 1. 1. 1. 1. 1. 1. 1. 1. 1. 1. 1. 1. 1. 1. 1. 1. 1. 1. 1. 1. 1. 1. 1.\n 1. 1. 1. 1. 1. 1. 1. 1. 1. 1. 1. 1. 1. 1. 1. 1. 1. 1. 1. 1. 1. 1. 1. 1.\n 1. 1. 1. 1. 1. 1. 1. 1. 1. 1. 1. 1. 1. 1. 1. 1. 1. 1. 1.], (91,), float32))",
      "stop_iters": 9999999,
      "stop_reward": 999999,
      "stop_timesteps": 2000000
    },
    "max_seq_len": 200
  },
  "multiagent": {
    "policies": "{'shared_policy'}",
    "policy_mapping_fn": "<function run_il.<locals>.<lambda> at 0x7fb5303e6550>"
  },
  "num_gpus": 1,
  "num_gpus_per_worker": 0,
  "num_sgd_iter": 5,
  "num_workers": 0,
  "sgd_minibatch_size": 2000,
  "simple_optimizer": false,
  "train_batch_size": 2000,
  "use_gae": true,
  "vf_clip_param": 10.0,
  "vf_loss_coeff": 1.0
}

The list of packages via pip freeze
asttokens==2.2.1
async-timeout==4.0.2
attrs==22.2.0
certifi @ file:///croot/certifi_1671487769961/work/certifi
charset-normalizer==3.0.1
click==8.1.3
cloudpickle==1.6.0
colorama==0.4.6
contourpy==1.0.7
cycler==0.11.0
Cython==0.29.6
dm-tree==0.1.8
exceptiongroup==1.1.0
executing==1.2.0
filelock==3.9.0
fonttools==4.38.0
grpcio==1.51.1
gym==0.19.0
gym-notices==0.0.8
gymnasium==0.27.1
gymnasium-notices==0.0.1
icecream==2.1.3
idna==3.4
imageio==2.25.0
importlib-metadata==4.13.0
importlib-resources==5.10.2
iniconfig==2.0.0
jax-jumpy==0.2.0
jsonschema==4.17.3
kiwisolver==1.4.4
lxml==4.9.2
lz4==4.3.2
-e git+https://github.com/Replicable-MARL/MARLlib.git@e1ddcef519b5d6736f140bcf8ad75689de62bff7#egg=marllib
matplotlib==3.6.3
metadrive-simulator==0.2.3
msgpack==1.0.4
networkx==3.0
numpy==1.19.3
opencv-python-headless==<IP_ADDRESS>
packaging==23.0
Panda3D==1.10.8
panda3d-gltf==0.13
panda3d-simplepbr==0.10
pandas==1.4.4
Pillow==9.4.0
pkgutil_resolve_name==1.3.10
pluggy==1.0.0
protobuf==3.20.1
pygame==2.1.2
Pygments==2.14.0
pyparsing==3.0.9
pyrsistent==0.19.3
pytest==7.2.1
python-dateutil==2.8.2
pytz==2022.7.1
PyWavelets==1.4.1
PyYAML==6.0
ray==1.8.0
redis==4.4.2
requests==2.28.2
scikit-image==0.19.3
scipy==1.10.0
seaborn==0.12.2
six==1.16.0
SuperSuit==3.7.1
tabulate==0.9.0
tensorboardX==2.5.1
tifffile==2<IP_ADDRESS>
tomli==2.0.1
torch==1.9.1
tqdm==4.64.1
typing_extensions==4.4.0
urllib3==1.26.14
yapf==0.30.0
zipp==3.12.0

The bug appears after some training iterations. It seems to occur after the 9th training iteration and given "evaluation_interval": 10 from params.json, it seems to be an issue with the evaluation process.

same error

Change num_workers in ray.yaml to >2,e.g. 5 to see if the bug still there.
Metadrive requires additional workers (at least 1) to do the evaluation.

Change num_workers in ray.yaml to >2,e.g. 5 to see if the bug still there. Metadrive requires additional workers (at least 1) to do the evaluation.

Hi, I tried with num_workers: 5 and training ran for the set number of timesteps.


Docker image should accept optional flags as ENV variables

With the current docker image there is no way to pass additional command line flags such as -web.external-url. Instead of invoking prometheus directly the image should invoke a shell script, optionally passing command line variables if they're specified in the environment.

you are correct.


"Explicitly Managed Resource" as an object field

Is this use case thought out? Is there a syntax like { using propKey: propValue } or { propKey: using propValue } ?
As far as I understand, the only way to put a disposable resource into an object is to declare a using variable outside the object, and then create an object field with that variable:
using myResource = new MyResource();
const resources = {
    myResource
};

However, I think that for this case too, syntax should be provided. For example:
const buffers = {
    myResource: using new myResource();
};

Also: If an object is deleted, are the "Explicitly Managed Resources" fields deleted correctly?

What semantics are you looking for exactly?

the only way to put a disposable resource into an object is to declare a using variable outside the object, and then create an object field with that variable

That will likely not do what you expect. When the scope reaches the end, your resource will be disposed, and your object will simply hold onto a disposed resource. You likely want to "move" the disposal responsibility onto the owner object.

Also: If an object is deleted, are the "Explicitly Managed Resources" fields deleted correctly?

There is no such thing a "an object is deleted" in JavaScript.  This proposal is about explicit resource management, whereas garbage collection is not explicit. A collected object does not (and cannot) trigger any explicit disposal logic. A good summary of such discussions can be found at https://github.com/tc39/proposal-explicit-resource-management/issues/213#issuecomment-1909158242
Taking the explicit nature of the proposal into consideration, semantics for using field that could make sense would be to automatically make the object a disposable itself. To rewrite your example above:
function makeBuffers() {
  return {
      using myResource: new myResource();
  }; // object literal implicitly has a `[Symbol.dispose]` property
}

using buffers = makeBuffers();

However beyond this simple use case, you'll quickly notice that you may want to do some work between when you obtain your resource in the maker, and when you return the object. At that point, you should be using a disposable stack to manage your resources:
function makeBuffers() {
  using stack = new DisposableStack();
  const myResource = stack.use(new myResource());

  doSomeInit(myResource);

  const disposer = stack.move();
  return {
    myResource,
    [Symbol.dispose]() {
      disposer.dispose()
    }
  };
}

using buffers = makeBuffers();

Admittedly "moving" the disposable stack to the object's dispose is a little clunky, but I'm not sure there is a much better approach here. Also since you don't want to expose the internal disposer, I don't see how any "per field" syntax could help here. What we may need is a userland helper that moves the stack onto the object:
function moveToDisposeFunction(stack) {
  const disposer = stack.move();
  return disposer.dispose.bind(disposer);
}

function makeBuffers() {
  using stack = new DisposableStack();
  const myResource = stack.use(new myResource());

  doSomeInit(myResource);

  return {
    myResource,
    [Symbol.dispose]: moveToDisposeFunction(stack),
  };
}

using buffers = makeBuffers();

What we may need is a userland helper that moves the stack onto the object:

I originally had that capability with DisposableStack.prototype.dispose being a getter for a bound method, but that approach was rejected by some on the committee.

I originally had that capability with DisposableStack.prototype.dispose being a getter for a bound method, but that approach was rejected by some on the committee.

Yeah I thought I remembered something along those lines. Wondering if it may be worth revisiting.


Remove unnecessary modifier of variables inside of Project.java

Just removed public static final since Project.java is interface.

Any of the checked boxes below indicate that I took action:

[x] Reviewed the Contribution Guidelines.
[x] Signed the Gradle CLA.
[x] Ensured that basic checks pass: ./gradlew quickCheck

🙇

Thanks @hotchemi for this PR. Unfortunately, one of our engineers already addressed that independently of your PR. I will close it however, I'm looking forward to your next PR.

I'm sorry I haven't noticed this PR. I was working on that file and the unnecessary modifiers bothered me as well.

@lacasseio @bamboo No problem! Thx for the review 😃


PARQUET-1532: [C++] Fix build error with MinGW

Error message:
In file included from C:/msys64/mingw64/include/thrift/TApplicationException.h:23,
                 from C:/Users/kou/work/arrow/arrow.kou/cpp/src/parquet/thrift.h:35,
                 from C:/Users/kou/work/arrow/arrow.kou/cpp/src/parquet/column_reader.cc:36:
C:/msys64/mingw64/include/thrift/Thrift.h:32:10: fatal error: netinet/in.h: No such file or directory
 #include <netinet/in.h>
          ^~~~~~~~~~~~~~

@kou I'm not allowed to edit PARQUET project on jira, so I cannot change the fix version. Could You please grant me permissions?

Ah, I don't have permission for PARQUET project.
(I could close this issue because I'm the reporter.)
@wesm @xhochy What should we do for PARQUET issues? @kszucs and I can merge changes to this repository but can't change PARQUET issues. Should we wait @wesm, @xhochy or someone for PARQUET issues?

@kou I'll make you a contributor on PARQUET

Thanks!

I added @kszucs as a Contributor so he should be able to edit fix versions now


build: cronjob to run tests against mdc snapshot builds

Sets up a new cronjob that runs tests against the material-components-web
repository HEAD. This allows us to validate that our MDC components work
properly with upcoming MDC releases.

LGTM, but it might be good if @jelbourn takes a look, I don't really know what I'm looking at :sweat_smile:


[Error: socket hang up] code: 'ECONNRESET' when running tests asynchronously

I am pretty consistently getting an error: [Error: socket hang up] code: 'ECONNRESET' when I try to queue apex classes. I would say this happens about 75% of the time I try to do this. Any thoughts on how this can be resolved? I am not running my script behind a proxy as suggested in other solutions. Here is an example of the piece of code that is causing me problems...basically I get a list of all the class IDs I need and then split them into chunks to be run asynchronously.
                chunk = testClassId.slice(counter, chunkSize);

                    conn.tooling.runTestsAsynchronous(chunk, function(err, results){
                        if (err) {
                            return console.error(err);
                        }

                        testResultId = results;
                        console.log(testResultId);

                    });

@TheWallOfDucks Were you able to solve this problem?  If so, could you explain how please?


Fix stack overflow issue due to recursive getter method call

Purpose
$title
Approach
n/a
Samples
n/a
Remarks
n/a
Check List

[x] Read the Contributing Guide
[ ] Updated Change Log
[ ] Checked Tooling Support (#)
[ ] Added necessary tests

[ ] Unit Tests
[ ] Spec Conformance Tests
[ ] Integration Tests
[ ] Ballerina By Example Tests

[ ] Increased Test Coverage
[ ] Added necessary documentation

[ ] API documentation
[ ] Module documentation in Module.md files
[ ] Ballerina By Examples

Tracked in https://github.com/ballerina-platform/ballerina-lang/pull/24298 ...


fixed typo

One other thing @juanpedromoreno - i noticed that the home title says "A sbt plugin" when it should be "An sbt plugin" - im not sure where to adjust that one.

Thanks @MaureenElsberry , this was already solved. Closing this PR.


On Mac OS 10.9, gets Can't open ftdi device: FT_DEVICE_NOT_OPENED error, but doesn't on Win7

I googled for this issue, found probably because of ftdi_sio (from official Q&A), but the fact is this lib is not installed on my Mac.
What can I do for this?
Thanks.

FYI.
Same issue encountered with Mac OS 10.9 and FT245RL.
Same fix worked like a charm.


[warning] proposal: do_not_check_equality_to_self

do_not_check_equality_to_self
Description
Checking equality to self will always return true and is likely a typo.
Details
Although good code tries to avoid it, sometimes two different variables or fields have similar names and types. It is then possible to mistakenly use one symbol where the programmer meant the other. This lint tries to prevent one such error, where a condition is in the form a == a or a != a.
Kind
This guards against hard-to-spot errors.
Bad Examples
class A {
  int _current = 0;

  void update(int current) {
    if (current != current) {
      // Do some work...
    }
  }
}

Good Examples
class A {
  int _current = 0;

  void update(int current) {
    if (current != _current) {
      // Do some work...
    }
  }
}

Discussion
Just found this exact bug in my code, and only after seeing it happen in the step debugger. This wasn't flagged in any way. I'm using package:flutter_lints/flutter.yaml.
I feel this is the kind of bug that linters were invented for. Stupid, hard to see as a human, easily detectable by the machine, and potentially infuriating ("why the hell doesn't this code run?").
I realize equality might be overridden for user types but even then, I think checking for a == a is probably a typo.
Discussion checklist

[ ] List any existing rules this proposal modifies, complements, overlaps or conflicts with.
[ ] List any relevant issues (reported here, the SDK Tracker, or elsewhere).
[ ] If there's any prior art (e.g., in other linters), please add references here.
[ ] If this proposal corresponds to Effective Dart or Flutter Style Guide advice, please call it out. (If there isn't any corresponding advice, should there be?)
[x] If this proposal is motivated by real-world examples, please provide as many details as you can.  Demonstrating potential impact is especially valuable.

@filiph: I went ahead and moved this to the SDK so consider your request transferred!


DBC Feeder uses TLS for connection to kuksa.val Server by default

The README of the dbc2val feeder suggests that the feeder will not use TLS for connecting to kuksa.val Server/Databroker.
However, ServerClientWrapper actually seems to default to using TLS.
We should either adapt the documentation or the implementation accordingly.

The default configuration is False: https://github.com/eclipse/kuksa.val.feeders/blob/3a72e0b7230927205507e5fd96c5162cc26af56a/dbc2val/config/dbc_feeder.ini#L33

Not if I provide my own config file that doesn't contain the tls option, or am I mistaken?

Ah that may be true, not sure without checking code. @erikbosch might know the answer immediately. He should be back really soon.
I agree, with the original issue: It should of course be consistent  between code and docs

Let me check this for you ;-)
https://github.com/eclipse/kuksa.val.feeders/blob/3a72e0b7230927205507e5fd96c5162cc26af56a/dbc2val/dbcfeeder.py#L483

In my opinion it is good that "the default is TLS unless you set it to false in config or cmd line", wile the default configfile could still be "false", as realistically that is what most people will use.
It should just be reflected in the docs.

Fair enough, then I guess we should change https://github.com/eclipse/kuksa.val.feeders/blob/3a72e0b7230927205507e5fd96c5162cc26af56a/dbc2val/dbcfeederlib/databrokerclientwrapper.py#L49
and the README accordingly ...

I have taken another look at the supported command line switches and their defaults.
It seems strange to me that not all of the config properties can be configured using command line arguments and some of the implementation relies on default values set in a default config file included in the code tree instead of assuming reasonable defaults in the implementation itself.
For example, it seems to be impossible to disable usage of TLS on the command line, neither by means of a command line switch nor by means of an environment variable. Is that intended and follows a particular pattern (which I am not able to see) or is this simply a case of not implemented yet?

We have an issue at https://github.com/eclipse/kuksa.val/issues/589 on the fact that we are not that consistent in config options and the fact that we maybe should not support all config settings as command line arguments. There has also now and then been concerns that we should not change existing (default) behavior as that may cause regressions for downstream projects, I guess that is one of the reasons why broker and server had different default behavior. I will look more in detail and create a PR to better align behavior when time permits

We have migrated CAN Provider (dbcfeeder) to a new repo. Long term my intention is to close all dbc/can-related issues in this repository. If we see the issue as still interesting or relevant we could create a new issue in the new repo, possibly referencing the old issue in the repository.
Suggested way forward:

I will migrate selected issues early 2024
If this issue has not been migrated but you want it to remain open please comment.
Remaining issues no one seems to be interested in will be closed around 2024-03-31


How change height for title

Its possible change height for title(section)?
I try use autolayout, but always get same height. I try use override tableView(_ tableView: UITableView, heightForRowAt indexPath: IndexPath), but not work, section and row get same height.

Thanks

Im resolved by checking if  row == 0... thanks


Added additional sensor categories + substance and position properties

Noted an issue with enums in ADT Explorer: they apparently cannot be unset, once set, and the ADT Explorer GUI defaults to showing an enum field as filled with one (the first?) value in the enum schema. I.e., it's really easy in the GUI to mess up enum-using twins and not be able to undo one's changes. So, for those cases where we use enums: should we provide a safe "unset" option in the enum?

Noted an issue with enums in ADT Explorer: they apparently cannot be unset, once set, and the ADT Explorer GUI defaults to showing an enum field as filled with one (the first?) value in the enum schema. I.e., it's really easy in the GUI to mess up enum-using twins and not be able to undo one's changes. So, for those cases where we use enums: should we provide a safe "unset" option in the enum?

As a matter of fact, ADT Explorer does not seem to play nice with enums GUI-wise even with a solution such as the one proposed above. Perhaps best to update it to do so, rather than implement workarounds in the models.

@hammar ,
For ADT-Explorer I agree with this " As a matter of fact, ADT Explorer does not seem to play nice with enums GUI-wise even with a solution such as the one proposed above. Perhaps best to update it to do so, rather than implement workarounds in the models."
@cschormann, could you please make sure you address ADT Explorer issues with enums? See above.
Thanks

@hammar @alinamstanciu
I have just merged a bunch of changes into Willow Ontology to align with the spreadsheet I prepared on this Capability topic:
https://github.com/WillowInc/opendigitaltwins-building/tree/main/Ontology/Willow/Capability
There are a few differences from what I see here and I've fully populated the Capability enums for position, phenomenon, etc.

@hammar ,
For ADT-Explorer I agree with this " As a matter of fact, ADT Explorer does not seem to play nice with enums GUI-wise even with a solution such as the one proposed above. Perhaps best to update it to do so, rather than implement workarounds in the models."
Could you please show repro steps, not sure I understand correctly.
@cschormann, could you please make sure you address ADT Explorer issues with enums? See above.
Thanks

I'm uploading five pictures illustrating different parts of the process/problem:

The enum schema
Twin that uses this schema. Note that "substance" and "position" fields are seemingly prepopulated with the first enum value for the respective property, in spite of these properties not actually being set on the twin yet.
Result of saving the twin with that default value prepopulated from the schema. Note the lack of patch.
Saving a value that does not exist in the enum definition. Note that this actually saves the default (first listed value), rather than throw an error as expected.
Saving another value that is consistent with the enum schema definition. In this case I manually typed in "Steam", an allowed value, and saved. Note that this actually saves the default (first listed value) rather than the one I entered.

@hammar @alinamstanciu
I have just merged a bunch of changes into Willow Ontology to align with the spreadsheet I prepared on this Capability topic:
https://github.com/WillowInc/opendigitaltwins-building/tree/main/Ontology/Willow/Capability
There are a few differences from what I see here and I've fully populated the Capability enums for position, phenomenon, etc.

Posting in the same response here as I did to Alina's other comment (as I'm not sure if you're pinged on that):

I based this list on the Optio3 list, which I took to be the target list for the first iteration -- but changing to the list provided by Rick is not a problem and I will do so shortly (in an hour or so) and update this PR. I'll also rename substance to phenomenon.

The phenomena and position lists are now updated, I hope this is more in line with expectations.
Note that since RDF, JSON, and JSON-LD do not care about key ordering, enums can sometimes be serialized in a semi-random order when the models are generated. This is obviously less than ideal and I will try to dig into the relevant libraries to see if I can mitigate the effect.

@hammar ,
For ADT-Explorer I agree with this " As a matter of fact, ADT Explorer does not seem to play nice with enums GUI-wise even with a solution such as the one proposed above. Perhaps best to update it to do so, rather than implement workarounds in the models."
Could you please show repro steps, not sure I understand correctly.
@cschormann, could you please make sure you address ADT Explorer issues with enums? See above.
Thanks

I'm uploading five pictures illustrating different parts of the process/problem:

The enum schema
Twin that uses this schema. Note that "substance" and "position" fields are seemingly prepopulated with the first enum value for the respective property, in spite of these properties not actually being set on the twin yet.
Result of saving the twin with that default value prepopulated from the schema. Note the lack of patch.
Saving a value that does not exist in the enum definition. Note that this actually saves the default (first listed value), rather than throw an error as expected.
Saving another value that is consistent with the enum schema definition. In this case I manually typed in "Steam", an allowed value, and saved. Note that this actually saves the default (first listed value) rather than the one I entered.

Thanks Karl!!!!

@hammar @alinamstanciu
I have just merged a bunch of changes into Willow Ontology to align with the spreadsheet I prepared on this Capability topic:
https://github.com/WillowInc/opendigitaltwins-building/tree/main/Ontology/Willow/Capability
There are a few differences from what I see here and I've fully populated the Capability enums for position, phenomenon, etc.

Posting in the same response here as I did to Alina's other comment (as I'm not sure if you're pinged on that):

I based this list on the Optio3 list, which I took to be the target list for the first iteration -- but changing to the list provided by Rick is not a problem and I will do so shortly (in an hour or so) and update this PR. I'll also rename substance to phenomenon.

@hammar , are we eventually going the way Rick did it ? https://github.com/WillowInc/opendigitaltwins-building/tree/main/Ontology/Willow/Capability/Sensor
Thanks

Hi all,
I just completed another large push within Willow Capabilities as I've iterated on the ideas posted above by @hammar around clustering, etc. Here's a link to Willow Capability:
https://github.com/WillowInc/opendigitaltwins-building/tree/main/Ontology/Willow/Capability
Key updates:

Introduced subclasses to Sensor/Setpoint to cluster on the following: Quantity, Detection, Status (still needs work)
The above allows us to move the lastValue to the grouping since they all have the same schema (double, boolean) below
I chose to use these terms over the even more generic Numeric/Double/Boolean because I think they are more intuitive and we don't need to introduce an intermediate clustering of different Boolean sensors (i.e. Detection and Status) at this time
Unlike Sensor/Setpoint clustering, I do think it makes sense to cluster State/Actuator on the terms Binary(Boolean?), Multi-State, and PercentUnity given the nature of how these clusters come together.
The Willow ontology is representative of my current thinking. If/once the concepts are taken up by this ontology, we will remove duplicate properties (i.e. lastValue) and just extend this ontology.

@rszcodronski that looks very promising. I'm a bit under-the-weather at the moment (hopefully just a cold..) and not operating at full capacity; so a more thorough analysis from me may take a day or two more. In the interim I've asked @erikoskarwallin to check this design versus the Idun platform and needs, and see if we can get the REC consortium on board. Personally I think (again, subject to actually looking a little deeper, once my head is working properly) that I'm on board.
Cheers,
Karl

Note that this contains the REC view on quantitysensors, including semantic typing where applicable, etc. I put together this list with the goal to fulfil the Optio3 requirements, but it is not a 1:1-mapping of every exact concept against Optio3 and it is shorter and structured somewhat differently (I'd argue more concise/usable, but I recognize that opinions may diverge on this) than the Willow list.
Anyone else who has input on this, or should we merge and proceed?


docs: open api version / content type in readme

What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
Docs update, fixes #118.

I hope this commit will help others avoid the same issues I had.

Thanks


Gallina turuleca

Song Name
Quesito
Artist Name
BZ fabri
Source
Youtube
Youtube Link
https://youtu.be/1R2LOU7TSbM?si=XEVgyeUdlqA75Zmg
Direct File Link
No response
Song ID
945695
Start Offset [ms]
1
Extra
Created from Auto Nong.
Created for level: 19759411

La gallina turuleca está loca de verdad🤑

Ptos
El mié., 4 de septiembre de 2024 21:28, github-actions[bot] <
@.***> escribió:

Closed #2848 https://github.com/FlafyDev/auto-nong-indexes/issues/2848
as completed.
—
Reply to this email directly, view it on GitHub
https://github.com/FlafyDev/auto-nong-indexes/issues/2848#event-14139729824,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BKRKWV4ASZPNBXSXAFY4RD3ZU66V7AVCNFSM6AAAAABMRD3MMGVHI2DSMVQWIX3LMV45UABCJFZXG5LFIV3GK3TUJZXXI2LGNFRWC5DJN5XDWMJUGEZTSNZSHE4DENA
.
You are receiving this because you authored the thread.Message ID:
@.***>


mutate example does not work

From here:
https://humphrey.whenderson.dev/json/untyped-values.html#manipulating-json-values
use humphrey_json::Value;

fn main() {
   let data = r#"
   {"age": 43, "name": "John Doe"}
   "#;
   let value: Value = humphrey_json::from_str(data).unwrap();
   // expected enum `Value`, found `&str`
   value["name"] = "Humphrey";
   dbg!(value);
}

This was simply a mistake on my part - the new value to set must be a Value. I've fixed this and the documentation should update shortly.

OK cool - thank you!

confirmed fixed, thanks!


#1434 Fix bug when removing comments.

Hi Juan, thank you for this pull request. I've reviewed your code and it looks solid.
This said, we are completely removing commenting from our Camper News since it is an underutilized feature. So I will close this pull request.
I'm sorry about the lack of communication on this - we literally made this decision in the last few hours after you'd already submitted this. Please do not let this discourage you from contributing in the future.

I did not understand you mean you are no longer removing comments? what is
Camper News?
On Sat, Aug 1, 2015 at 12:50 PM, Quincy Larson<EMAIL_ADDRESS>wrote:

Closed #1435 https://github.com/FreeCodeCamp/freecodecamp/pull/1435.
—
Reply to this email directly or view it on GitHub
https://github.com/FreeCodeCamp/freecodecamp/pull/1435#event-371201967.


Feature request: add Redis Channel

Original issue: knative/eventing-contrib#570

/remove-lifecycle stale

/remove-lifecycle stale

/kind feature-request

/kind proposal

@juliafriedman8 what we were talking about yesterday for Redis..

/remove-lifecycle stale

/reopen


Update ticktick extension

Description
When creating a new task, the extension will guess which project the task belongs to. For non-pro users it just acts as before.
Screencast

Checklist

[x] I read the extension guidelines
[x] I read the documentation about publishing
[x] I ran npm run build and tested this distribution build in Raycast
[x] I checked that files in the assets folder are used by the extension itself
[x] I checked that assets used by the README are placed outside of the metadata folder

Seems to work pretty good @Alireza29675, well done! 🔥
@viduycheung do you mind checking this?

@pernielsentikaer Settings have been added and are disabled by default 🙌
Should we enable it by default or wait until we add more features like auto-filling for date and time?

@Alireza29675 I think we can add an action to manually parse, and keep the auto-parsing feature disabled by default.

@viduycheung Sounds like a plan for a start 🙂

Could be cool to have an action to Guess Project, something like:
{environment.canAccess(AI) && (
  <Action
    onAction={() => guessProjectByTitle}
    icon={Icon.Wand}
    title="Guess Project"
    shortcut={{ modifiers: ["cmd"], key: "g" }}
  />
)}

Do you think we could add that

@viduycheung @pernielsentikaer I added an action called "Fill the Form with AI" with the hotkey "Command+F". I'm okay with other options; just change the title or hotkey if you feel like it 🙌


Add support for #[deny(missing_docs)]?

For our CI, it is common to deny commits based on unresolved clippy warnings.  For more mature projects, we will add #[warn(missing_docs)] to the top of the module.  If I use Setters to derive setters for a struct, this produces a documentation warning that I cannot easily address.

From a related issue on the bytemuck crate discussed on URLO, one recommendation given was:

You could open an issue on the bytemuck repo asking the derive macro to include #[allow(missing_docs)] on the generated struct too.

Perhaps setters are generalizable such that inserting a relatively generic "Sets the value of [x] field to [arg]" as a doc comment would work as well.
Thank you,
Erik

Experimenting a bit more, I note that if I document the private fields being accessed by the setter, it clears the warning, but this is not a total win, because it duplicates the doc comment describing the field in the setter method:

I can imagine writing a good doc comment for one method, or the other, but not as easily for both at once.  Am I using this as intended?

I'll think about this use case. derive_getters and derive_new are by other authors, and I had not expected that this would be a possible issue when I first wrote this.

Thank you, Rimi.
I checked out the changes this morning, and this seems to work like a charm for our use case.
Much appreciated.
Erik
[cid:2812831a-aed7-48cf-96a9-f77fdafe8e77]

From: Rimi Kanokawa @.>
Sent: Monday, August 5, 2024 8:07 PM
To: Lymia/derive_setters @.>
Cc: GIS @.>; Author @.>
Subject: Re: [Lymia/derive_setters] Add support for #[deny(missing_docs)]? (Issue #10)
[NOTICE:  This message originated outside the City of Grants Pass -- DO NOT CLICK on links or open attachments unless you are sure the content is safe.]
Closed #10https://github.com/Lymia/derive_setters/issues/10 as completed via 553387bhttps://github.com/Lymia/derive_setters/commit/553387b7895eb62d4ce0a16fa9f103cd92b26662.
—
Reply to this email directly, view it on GitHubhttps://github.com/Lymia/derive_setters/issues/10#event-13772051774, or unsubscribehttps://github.com/notifications/unsubscribe-auth/A23N6Q66MNZTMX2TWFO4TJDZQA4W7AVCNFSM6AAAAABMA6S32SVHI2DSMVQWIX3LMV45UABCJFZXG5LFIV3GK3TUJZXXI2LGNFRWC5DJN5XDWMJTG43TEMBVGE3TONA.
You are receiving this because you authored the thread.Message ID: @.***>
*** DISCLOSURE: Messages to and from this E-mail address may be subject to Oregon Public Records Law. ***


Update change-the-perpetual-valuation-method.md

updating steps

@theley502, Hi Terry, this PR is ready for your final review. Feel free to let me know if it's OK to merge. Thanks!

Looks great, thanks publish
From: Lucy Zou @.>
Sent: Tuesday, January 17, 2023 12:48 AM
To: MicrosoftDocs/SupportArticles-docs @.>
Cc: Terry Heley @.>; Mention @.>
Subject: Re: [MicrosoftDocs/SupportArticles-docs] Update change-the-perpetual-valuation-method.md (PR #852)
@theley502https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Ftheley502&data=05|01|theley%40microsoft.com|d10f89353ed443812b9708daf856cdc3|72f988bf86f141af91ab2d7cd011db47|1|0|638095348958546763|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=mBYzzcBk0AnlgBxcFYh6qGeej%2FH%2FXYAo98cTy920VB8%3D&reserved=0, Hi Terry, this PR is ready for your final review. Feel free to let me know if it's OK to merge. Thanks!

Reply to this email directly, view it on GitHubhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2FSupportArticles-docs%2Fpull%2F852%23issuecomment-1384908833&data=05|01|theley%40microsoft.com|d10f89353ed443812b9708daf856cdc3|72f988bf86f141af91ab2d7cd011db47|1|0|638095348958546763|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=xpIlrf42Bparj49A2zTropeSvVsvE7j3fGm9W%2BuDg0M%3D&reserved=0, or unsubscribehttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAKJ5MK6E7KFIFPGAYC6VEDLWSY6CZANCNFSM6AAAAAATZSGCIE&data=05|01|theley%40microsoft.com|d10f89353ed443812b9708daf856cdc3|72f988bf86f141af91ab2d7cd011db47|1|0|638095348958546763|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=CC5TmBHcDvNduQGBkp0RGPbco1Xvrhm8PPu6Tg1tGZI%3D&reserved=0.
You are receiving this because you were mentioned.Message ID<EMAIL_ADDRESS>

@theley502, Hi Terry, thanks for reviewing the draft. The article is live:  https://learn.microsoft.com/en-us/troubleshoot/dynamics/gp/change-the-perpetual-valuation-method


Add hard tanh activation

Implement a "hard" hyperbolic tangent activation function, that gives a segment-wise linear approximation of tanh.
hardTanh.ts has to be manually compiled to hardTanh.js through tsc to be usable. Only hardTanh.ts should be edited, hardTanh.js should be recompiled.

LGTM.


"yyyy-MM" for dateFormat is not running

First,thanks for your plugin!
I am sorry about my english！
There is a problem when set value "yyyy-MM" for dateFormat,
and I found these values of "dd-MM-yyyy" 、 "MM-dd-yyyy" 、 "yyyy-MM-dd" 、"MM yyyy" 、 "MMM yyyy" 、 "MMMM yyyy" to be correct。
by the way，We are eager to hope to set a custom format for datetime。thanks

Hi @DarkRake, I have added "yyyy-MM" date format. Please use latest version.


Authentication using service account (without using file)

Hello,
I'm currently migrate API from v1 to v2, one of the big changes is the authentication flow. In v1 I using a secret key, passed through Authorization header during POST request. Value is encrypted with a strong encryption system (AWS KMS) and decrypted before being used.
Now, if I understand well, I need to use a JSON file.. I'm in a stateless environment so I haven't access to file system (and I don't want to save it to disk without encryption for obvious security reasons).
There is a method to pass credentials in a different way? Respect using an environment variable (GOOGLE_APPLICATION_CREDENTIALS) to point to a file on disk, for example a secret/access keys pair. An option in class constructor would be preferable instead of forcing to use an environment variable, maybe I can't even use them for example in Lambda@Edge ecosystem.
Being that file a simple JSON file it should not be so complicated to accept that values as javascript object, something like this:
const sessionClient = new dialogflow.SessionsClient({
  "type": "service_account",
  "project_id": "xxxxxxxxxx
  "private_key_id": "xxxxxxxxxx",
  "private_key": "-----BEGIN PRIVATE KEY-----\n....\n-----END PRIVATE KEY-----\n",
  "client_email"<EMAIL_ADDRESS>  "client_id": "xxxxxxxxxxxxxxxxxxxxxxx",
});

this will let developer to choice how to store values (environment variable/hashicorp vault/aws secret manager..etc..etc..) and most importantly, encrypted.
PS: using files to store configurations is an anti-pattern for 12 factor applications, this require to include that file under-version control (terrible) or creating it during build pipeline (this generate an non-agnostic artifact and is a bad practice IMHO) and cannot be tested locally.

You should be able to pass the contents of the .json file to the SessionsClient constructor on the credentials property like so:
const sessionClient = new dialogflow.SessionsClient({ credentials: { /* the json */ } })

For reference, this is the documentation for the constructor of the SessionsClient:
    /**
     * Construct an instance of SessionsClient.
     *
     * @param {object} [options] - The configuration object. See the subsequent
     *   parameters for more details.
     * @param {object} [options.credentials] - Credentials object.
     * @param {string} [options.credentials.client_email]
     * @param {string} [options.credentials.private_key]
     * @param {string} [options.email] - Account email address. Required when
     *     using a .pem or .p12 keyFilename.
     * @param {string} [options.keyFilename] - Full path to the a .json, .pem, or
     *     .p12 key downloaded from the Google Developers Console. If you provide
     *     a path to a JSON file, the projectId option below is not necessary.
     *     NOTE: .pem and .p12 require you to specify options.email as well.
     * @param {number} [options.port] - The port on which to connect to
     *     the remote host.
     * @param {string} [options.projectId] - The project ID from the Google
     *     Developer's Console, e.g. 'grape-spaceship-123'. We will also check
     *     the environment variable GCLOUD_PROJECT for your project ID. If your
     *     app is running in an environment which supports
     *     {@link https://developers.google.com/identity/protocols/application-default-credentials Application Default Credentials},
     *     your project ID will be detected automatically.
     * @param {function} [options.promise] - Custom promise module to use instead
     *     of native Promises.
     * @param {string} [options.apiEndpoint] - The domain name of the
     *     API remote host.
     */
    constructor(opts?: ClientOptions);

Hi @OlenDavis,
I try to retrieve the encrypted file content and passing to credentials parameters:
// retrieve file content from AWS Secret Manager
const secretResponse = await secretsManager.getSecretValue({
    SecretId: event.SecretId
}).promise()
// parse response
const parameters = {
    credentials: JSON.parse(secretResponse.SecretString)
}
// log for debug purpose (just to show you the correct parsed file)
console.log(parameters)
// set credentials parameters
const sessionClient = new dialogflow.SessionsClient(parameters)

file content is correctly formatted as the console.log show:
{ credentials:
   { type: 'service_account',
     project_id: 'myproject-xxxx,
     private_key_id: 'xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx',
     private_key:
      '-----BEGIN PRIVATE KEY-----\n
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
\n-----END PRIVATE KEY-----\n',
     client_email<EMAIL_ADDRESS>     client_id: 'xxxxxxxxxxxxxxxxxxxxxxxxxxx',
     auth_uri: 'https://accounts.google.com/o/oauth2/auth',
     token_uri: 'https://oauth2.googleapis.com/token',
     auth_provider_x509_cert_url: 'https://www.googleapis.com/oauth2/v1/certs',
     client_x509_cert_url:
      'https://www.googleapis.com/robot/v1/metadata/x509/myproject-xxxxxxxxxx.iam.gserviceaccount.com' } }

but client raise an error:
{
    "errorType": "Error",
    "errorMessage": "Could not load the default credentials. Browse to https://cloud.google.com/docs/authentication/getting-started for more information.",
    "stack": [
        "Error: Could not load the default credentials. Browse to https://cloud.google.com/docs/authentication/getting-started for more information.",
        "    at GoogleAuth.getApplicationDefaultAsync (/var/task/node_modules/google-auth-library/build/src/auth/googleauth.js:160:19)",
        "    at process._tickCallback (internal/process/next_tick.js:68:7)"
    ]
}

seems credentials are not correctly loaded.

Using dialogflow with this version:
$ npm list | grep "dialogflow"
├─┬<EMAIL_ADDRESS>
on Node 10.x

This issue might no longer be relevant due to its age. Feel free to re-open.


fix(router-link): Navigation works when the tag value is rendered as …

Navigation works when the tag value is rendered as a custom component

If you want a custom component to apply the click listener, rebind it inside the component or use the v-slot api


[feature] #3153: make serde_client_cli output machine-readable

Description of the Change
Adds --json flag to client_cli for usage in scripts.
Issue
#3153
Benefits
Allows for automated testing
Possible Drawbacks
None that I can think of
Usage Examples or Tests
$ ./iroha_client_cli --json asset list all | jq '.[1].id'
"rose##alice@wonderland"

Coverage is failing again (though intermittently)

RE: coverage, probably not your fault. Our tests are quite unstable since we moved to the new sumeragi.


Make it possible to specify delimiter

CSV files can use different column delimiter. They should be a way to specify it, something like -d ';'.
This can be easily done with https://docs.rs/csv/latest/csv/struct.ReaderBuilder.html#method.delimiter
Thanks.

This is added in master.


[Feature Request] add managed worker support for quick deployment as microservices

If the current client application for ASTRA is an HTTP server, it would be ideal to encapsulate the worker management process. Turning it into a microservice or a process pool would simplify the ASTRA client application code and improve quality.

Just a worker manager or use microservice framework? I'd like to using Kratos. Because I just did RTM2 integration for Kratos Transport, it's helpful.

Are there any other options on the market we can consider? Having only one framework choice seems too opinionated, which might not be healthy for maintaining an OSS framework.

On second thought, this topic is worth converting into discussion as well.


review wiki for http links when SSL https is added

Should just be a find/replace for http://total-briecall.herokuapp.com.

we're also planning to use a DNS name, so it'll change to total-briecall.com

wiki reviewed and updated


Zoom to Feature zooms in too close to feature

I need to zoom to a feature at 1:72,224 scale.  how can I update my code to make this happen.  i see two locations where code could be altered.  i do not need to change the size of the buffer graphic.
postCreate: function () {
this.inherited(arguments);
        if (!this.spatialReference) {
            this.spatialReference = this.map.spatialReference.wkid;
        }
        if (!this.pointExtentSize) {
            if (this.spatialReference === 4326) { // special case for geographic lat/lng
                this.pointExtentSize = 0.0001;
            } else {
                this.pointExtentSize = 250; // could be feet or meters
            }
        }

zoomToExtent: function (extent) {
this.map.setExtent(extent.expand(1.5));
console.log(extent);
},

@cmccullough2 Assuming your basemap uses the Web Mercator spatial reference, you can simply set the map's zoom level to 13 which has a scale of 72,224
zoomToExtent: function (extent) {
    this.map.setExtent(extent.expand(1.5));
    this.map.setZoom(13);
},

the first line will center the map on the feature before zooming the map in/out to level 13;

Beautiful! worked like a charm.  Thanks


Does -((a+bi)/c) need brackets around the whole fraction when displayed in TeX?

We had an expression -(125+i)/3, which was rendered in TeX as -\frac{ 125 + i }{ 3 }. I think that brackets around the fraction would make it clearer that the negation applies to the whole thing.
I'm not sure whether - a/b should always have brackets around the fraction, or just when there's an addition or subtraction on the top, or what.

As far as I can tell, $-\frac{ 125 + i }{ 3 }$ is fine and is the usual thing to write. I would definitively prefer not to have parentheses in this case.
First example in a printed text I found (from the Princeton Companion to Mathematics):

Thanks, @ugoertz

OK, no extra parentheses.


Feature/expose callonce karate api

Description
Thanks for contributing this Pull Request. Make sure that you submit this Pull Request against the develop branch of this repository, add a brief description, and tag the relevant issue(s) and PR(s) below.

Relevant Issues : https://github.com/intuit/karate/issues/1373#issuecomment-744122768
Relevant PRs : (optional)
Type of change :

[x] New feature
[ ] Bug fix for existing feature
[ ] Code quality improvement
[ ] Addition or Improvement of tests
[ ] Addition or Improvement of documentation

Don't merge yet please - still doing some tests as I have failures and want to ensure it's not related with these changes

Don't merge yet please - still doing some tests as I have failures and want to ensure it's not related with these changes

Reverted my changes and my other issues continue so they're not related to this PR. Should be good to merge.

@joelpramos here's my edit: https://github.com/intuit/karate/commit/b5861294c620e0d9730b80a641739342fb32cf8b
I flipped the order / boolean arg for sharedScope as the first, to be consistent with call() - not the best designed api but hey. also added a unit-test, feel free to extend it if you want to check some edge cases with 2 scenarios etc


infra: upgrade Docusaurus to v2.0

Link: https://docusaurus.io/blog/2022/08/01/announcing-docusaurus-2.0

TBD:

upgrade plugin versions
relocate docusaurus components
reimplement deleted or refactored docusaurus components
reimplement hijacked theme components
reimplement custom plugins
...


mrkdwn_in support in attachments?

Hello,
First of all, thanks for the library!
Would it be possible to add a support mrkdwn_in in the library? It'd help to post e.g. stack traces
Best,
Rafal

@rafaljanicki Thank you for the feature request. Would you be able to send in a PR? I would be happy to review and merge them. I'm currently short of time to work on this repo :(

Fixed via #13


dbeaver doesn't show parent partitioned table in pg-10

Hi, thanks for the great product!
New PostgreSQL 10 has got declarative partitioning. Dbeaver's objects browser shows child tables but their master table is not visible. Everything is ok with old-style trigger partitioned tables.
testcase:
# CREATE TABLE measurements (logdate date not null, peaktemp int default 1, unitsales int) PARTITION BY RANGE (logdate);
# CREATE TABLE measurements_2017_07 PARTITION OF measurements FOR VALUES FROM ('2017-07-01') TO ('2017-08-01');
# CREATE TABLE measurements_2017_08 PARTITION OF measurements FOR VALUES FROM ('2017-08-01') TO ('2017-09-01');

Already implemented


Validate antichess knight-versus-knight opposition draw

In antichess knight-versus-knight endgames the player having the opposition cannot lose (and there is no way to lose the opposition).
Getting visibility to situation.color required refactoring InsufficientMatingMaterial(Board, Color) into InsufficientMatingMaterial(Situation), which works well since consumers only care whether the player not on move has sufficient material to win!

Sorry, I think I missed something: We still need to be able to check both sides to immediately end the game when both sides have insufficient material.

No worries!  Please let me know if I need to change either of the methods which test such a condition:
https://github.com/ornicar/scalachess/blob/d2bebc3107b528daba4eb418c1151e5a52832e1e/src/main/scala/Board.scala#L158
https://github.com/ornicar/scalachess/blob/d2bebc3107b528daba4eb418c1151e5a52832e1e/src/main/scala/Situation.scala#L32
I think another challenging aspect of this PR is that it changes the public interface of InsufficientMatingMaterial consumed by lila:
https://github.com/ornicar/lila/blob/8dcddaa1048c347cde6d0a6773515764ee71877e/modules/round/src/main/Finisher.scala#L39-L40

Now in conflict with master due to the arguably more important #164. If you want to reroll this, it might be best to seperate the antichess change from the refactoring (contrary to what I originally suggested).

Oops... yes, I agree on all counts.  I'll eventually get around to both parts of this.


Make a YAML FileConfigurationProvider that ships with AspNetCore

YAML is gaining popularity especially outside the .Net ecosystem. Currently for .Net to use the YAML format, there are 2 options; Write your own YAML provider or to take a 3rd party dependency.
Parsing YAML yourself may be an overkill, so that leaves us with taking 3rd party dependency, not a big issue but there are potential downsides, such as maintenance and much more at risk of obsolescence compared to an officially supported provider.
Since AspNetCore already provides support for some of the most popular formats e.g JSON, XML, INI, in my opinion, it would make sense to also support YAML out of the box.

Parsing YAML yourself may be an overkill, so that leaves us with taking 3rd party dependency, not a big issue but there are potential downsides, such as maintenance and much more at risk of obsolescence compared to an officially supported provider.

That the case for all 3rd party things. Fortunately we care alot about a thriving ecosystem and don't want to be the single software provider for extensible things. There are several yaml configuration providers on nuget.

See also https://github.com/aspnet/Extensions/issues/1904 (and the there linked issues).

That the case for all 3rd party things. Fortunately we care alot about a thriving ecosystem and don't want to be the single software provider for extensible things. There are several yaml configuration providers on nuget that I would recommend you look at before deciding it needs to be in the box.

I somewhat agree but on the other hand what is different about JSON that it got adopted OOTB but not YAML? IMHO, .Net was very late to the game to adopt JSON OOTB, hopefully we don't have to wait as long for YAML support

I recently used AspNetCore and used the yaml format as a profile file. I looked through the documentation and found that the built-in yaml configuration provider was not available until 3.1.
I think it is necessary to provide a built-in yaml configuration parser now in yaml widely used. I'm glad to see this issue in the milestone.
I would like to know whether this repo accept the contribution code and whether a third-party library can be added, or if the yaml parser must be included in the submitted code.
@davidfowl

We don't plan to support YAML in the box right now. This is something we'd really want to encourage the third-party community to work towards. A built-in YAML provider would also require a built-in YAML parser (from dotnet/runtime) which is also very costly to build (and there are already great parsers out there). We also just don't have the resources to prioritize this work over the other things on our backlog when there's a clear extensibility point for the community here.
This is a prime opportunity for the open-source ecosystem, and we want to encourage that approach for this.


Assign codes to errors

Problem
We want there to be nice error reporting toward users (#654).
An issue is that the connection between the problem and possible solutions is not always obvious.
This is because the component generating the error is not aware of its role in the bigger configuration.

Example
For example, if run CSS behind a proxy but forget to set up the Forwarded header, then requests to the server will be made with the wrong hostname and/or protocol. This results in the error:
InternalServerError: http://wrong.host/ is not supported
    at SingleRootIdentifierStrategy.getParentContainer (/Users/ruben/Documents/UGent/Solid/solid-community-server/dist/util/identifiers/BaseIdentifierStrategy.js:14:19)
    at WebAclAuthorizer.getAclRecursive (/Users/ruben/Documents/UGent/Solid/solid-community-server/dist/authorization/WebAclAuthorizer.js:186:48)
    at processTicksAndRejections (internal/process/task_queues.js:93:5)
    at async WebAclAuthorizer.handle (/Users/ruben/Documents/UGent/Solid/solid-community-server/dist/authorization/WebAclAuthorizer.js:41:23)
    at async AuthenticatedLdpHandler.runHandlers (/Users/ruben/Documents/UGent/Solid/solid-community-server/dist/ldp/AuthenticatedLdpHandler.js:75:35)
    at async AuthenticatedLdpHandler.handle (/Users/ruben/Documents/UGent/Solid/solid-community-server/dist/ldp/AuthenticatedLdpHandler.js:46:61)
    at async SequenceHandler.handle (/Users/ruben/Documents/UGent/Solid/solid-community-server/dist/util/handlers/SequenceHandler.js:27:26)
    at async Server.<anonymous> (/Users/ruben/Documents/UGent/Solid/solid-community-server/dist/server/BaseHttpServerFactory.js:25:17)

For SingleRootIdentifierStrategy, it is impossible to know what the actual issue is, and WebAclAuthorizer does not have any clue either.
What we want (after #654), is an error page such as:

Requests to http://wrong.host/ are not supported
The Community Solid Server received a request for http://wrong.host/, which is not configured.
Here are some things you can try to fix this:

Have you started the server with the right hostname?
If you are running the server behind a reverse proxy, did you set up the Forwarded header correctly?

Proposal
Errors should be assigned codes, something like E1234, such that we can easily recognize them later on.
We could do things like:

have a file with a list of constants (enum?) that are error codes

something like export const ERROR_UNSUPPORTED_IDENTIFIER = createErrorType('E1234');
or ErrorCodes.UnsupportedIdentifier (perhaps simlar to the namespaces code we have)

have a specific Error subtype that takes such an error code in its constructor
or even have a custom error class for every error we emit; the class definition then has the error code

something like export const UnsupportedIdentifierError = createErrorType('E1234');

Any reason why the code should be something like E1234 and not just UNSUPPORTED_IDENTIFIER?
This issue feels similar to the problem we initially had on how to link status codes to errors, which we solved by going for the custom error classes for every status code. In case we go for solution 1-2 here, there's something to be said to also determine status code based on those constants so we don't have 2 different solutions internally for the same problem.

Any reason why the code should be something like E1234 and not just UNSUPPORTED_IDENTIFIER?

I was just following TypeScript errors etc. there; to not put too much meaning into the identifier.

there's something to be said to also determine status code based on those constants so we don't have 2 different solutions internally for the same problem.

Absolutely.

The solution here depends on bit on what we exactly want and need. The example error above is a good example of an error where more information should be provided to client, but how many such errors do we have compared to the total amount of different errors that are being thrown?
In case we only have a few errors for which we want to provide more context and information we could create new error classes specifying that. We could have a BadIdentifierError that extends the InternalServerError and has a more extensive description internally. This could be a specific type of DescriptiveError which has more fields than a normal error. We would then also update the error handlers and converter to make sure those fields are supported. But most of the errors we have would stay as they are now, this is assuming only a few would need this.
Another solution is similar to the above but instead of storing the extra fields in the error object we store them somewhere externally (like JSON) and the error handler would then check that resource every time it sees such a special error. We would also need a way to handle variables, so some sort of template might be needed.
The most drastic solution would be similar to the above, but apply it to all errors that we throw. In that case I would suggest only having 1 error class anymore, because otherwise we would almost need a new class for every error that we throw. All error messages/status codes/extra descriptions would then be stored in a single JSON document (or multiple, to allow extension). I think something similar was also suggested initially when talking about how to do errors (and is bullet point 2 in the top message).
Some disadvantages of the last solution are that we lose typing, unless we store information in a typescript file instead of an external JSON. It might also make it more difficult for external packages that want to throw a new type of error. Would depend on how we handle configuration for this. It would make localization easier should that ever be necessary.
I did a count and we currently throw errors on 180 different places. Besides the 404 errors I'm assuming that all those errors have unique error messages. So in case we want to replace all of them that would be a lot of entries. I'm also afraid that keeping the error descriptions in sync with what errors are needed might be an issue.

Resolution after discussion:

Let's ensure that all errors take two parameters; the first being a (short) description string, the second an optional hash that can take a cause parameter. Let's also allow an optional errorCode field in there.
Let's keep the existing error classes as they are otherwise.

A separate JSON document can, for some error codes, provide an extended (paragraph-size) description of how to fix it in the context of the entire server (whereas a local component would only know the local cause). Or they could even be Markdown documents ERR1234.md or even templates so we can render the above example.
Over time, that separate JSON document could also per error code contain the HTTP status codes, thereby fully decoupling those as well.


Tests: add XCTest manifest for non-SPM based builds

This allows for testing without SPM on non-Darwin targets.  We
explicitly exclude the manifest in SPM based builds because we would
like to use the automatic test discovery functionality from SPM.

@swift-ci please test

@swift-ci please test

CC: @lorentey


fix: remove unused authProvider field in cosign verifier

Description
What this PR does / why we need it:

Removes the auth provider field in cosign
This field was never used and a new change to the name in the struct caused a type mismatch when deserializing.

Which issue(s) this PR fixes (optional, using fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when the PR gets merged):
Fixes #655
Type of change
Please delete options that are not relevant.

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Please also list any relevant details for your test configuration

All Azure tests pass on local fork

Checklist:

[ ] Does the affected code have corresponding tests?
[ ] Are the changes documented, not just with inline documentation, but also with conceptual documentation such as an overview of a new feature, or task-based documentation like a tutorial? Consider if this change should be announced on your project blog.
[ ] Does this introduce breaking changes that would require an announcement or bumping the major version?
[ ] Do all new files have appropriate license header?

cc: @binbin-li if you could review when you have a chance. Thanks for finding the issue!


Guidance on starting a new project(my first)

So, currently I am just familiar with basic languages Java, Python and C++ but rather than just keeping on reading more and more basic problems and practice, I decided to work on my skills through projects and came across your repo. Very helpful, have to say. What my query is, I do not know how to go ahead now as I do not know any front end tech. I would like to work on it but if anyone could guide a bit on how to proceed would be very nice of you. I want to do these projects but my main aim is back end rather than full stack. Might sound like a neophyte but well, that is my query. Can you recommend what & how tech stack(language + framework) should I start leaning now to do these projects like JS, React, Angular, etc.
Thanks!

If you like backend stuff other than frontend you can make nice projects with backend, like creating a nice api service and you can monetize.
If you want to go into frontend then I would suggest  you learning Javascript or Typescript, I would suggest learning Typescript and you could learn any frontend framework from the following React or Vue, Then you can go on creating projects. You will start learning more when you start creating projects.
Just find what fits you the most backend, frontend or fullstack.

Thanks @rishikesh2003 I have decided to go with Full Stack now viz. HTML, CSS, JS, Python, APIs, Django and stuff around that.


Fix script help text in the test network document

Signed-off-by: Sol Kang<EMAIL_ADDRESS>Type of change

Documentation update

Description
In the latest version of fabric-samples, the results are as shown this code.
Additional details
The CA version may need to change in the near future.
Related Commit: 49f1ade6f4b68c72f8860ae0f01534a23403d1ba
Related issues
None.

@Mergifyio backport release-2.1


Issue with pages icon

I want to change the UI of the pages icon.The links at the bottom which allows navigation between pages.

Hey @Aanisha, Screenshots would help us understand how/what you are solving.

I want to work on this issue . Assign me this issue

Hey @Aanisha
Thanks for raising this issue :smile:
Please follow the issue template and always add whether you are working on this issue or not.
This will help others to know whether the issue is taken or not

@Aanisha could you please explain the issue in a bit more detail

The page icons and the UI can be improved.I'll like to work on it.
On Wed, 6 Mar 2019, 21:25 Arushit Mudgal<EMAIL_ADDRESS>wrote:

Hey @Aanisha https://github.com/Aanisha, Screenshots would help us
understand how/what you are solving.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/CircuitVerse/CircuitVerse/issues/196#issuecomment-470161815,
or mute the thread
https://github.com/notifications/unsubscribe-auth/Ap5hpJ15i-sECis7qR5t9D2c0GtITFJVks5vT-TngaJpZM4bekDl
.

@Aanisha, Please send a PR(don't forget to include screenshots) for the changes your propose

I have changed the UI of the page icons.I'll be very glad if you try it out.
I have attached the working version of the page buttons,the text code,and
the images
On Wed, 6 Mar 2019 at 22:39, Arushit Mudgal<EMAIL_ADDRESS>wrote:

@Aanisha https://github.com/Aanisha, Please send a PR(don't forget to
include screenshots) for the changes your propose
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/CircuitVerse/CircuitVerse/issues/196#issuecomment-470405400,
or mute the thread
https://github.com/notifications/unsubscribe-auth/Ap5hpKPj1py6y9o6juNgoGG48WWecn4Oks5vULQxgaJpZM4bekDl
.

    <title>Page Title</title>

     <link href='https://fonts.googleapis.com/css?family=Quantico' rel='stylesheet'>

        1

        2

        3

        4

        5

        6

        7

        8

        9

        10

@Aanisha, the code doesn't help us much as we cannot see the output. Images will help.

These are the output images.
On Sun, 17 Mar 2019, 19:32 Satvik Ramaprasad<EMAIL_ADDRESS>wrote:

@Aanisha https://github.com/Aanisha, the code doesn't help us much as
we cannot see the output. Images will help.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/CircuitVerse/CircuitVerse/issues/196#issuecomment-473668665,
or mute the thread
https://github.com/notifications/unsubscribe-auth/Ap5hpIb8sC6cueLBM_yJLdT8EPN7Vyyaks5vXkrcgaJpZM4bekDl
.

@Aanisha Hey there, we can't see the images. It looks like you are responding through email and it would be great if you could come on github and comment. Also you need to make a Pull Request for all the changes you make

can i work on this issue?

@mahmodHammad Hi, yeah you can go forward as this is taking a lot of time. Thanks

Sir but I already submitted a PR regarding this issue.
On Sat, 30 Mar 2019, 15:24 Arushit Mudgal<EMAIL_ADDRESS>wrote:

@mahmodHammad https://github.com/mahmodHammad Hi, yeah you can go
forward as this is taking a lot of time. Thanks
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/CircuitVerse/CircuitVerse/issues/196#issuecomment-478228669,
or mute the thread
https://github.com/notifications/unsubscribe-auth/Ap5hpO7SVZtb9QzLvitHsuH9Wd7bFXzzks5vbzRBgaJpZM4bekDl
.

Sir do I have to improve my PR regardind this issue?
On Sat, 30 Mar 2019 at 03:32, Aanisha Bhattacharyya <
<EMAIL_ADDRESS>wrote:

Sir but I already submitted a PR regarding this issue.
On Sat, 30 Mar 2019, 15:24 Arushit Mudgal<EMAIL_ADDRESS>wrote:

@mahmodHammad https://github.com/mahmodHammad Hi, yeah you can go
forward as this is taking a lot of time. Thanks
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/CircuitVerse/CircuitVerse/issues/196#issuecomment-478228669,
or mute the thread
https://github.com/notifications/unsubscribe-auth/Ap5hpO7SVZtb9QzLvitHsuH9Wd7bFXzzks5vbzRBgaJpZM4bekDl
.

Can I take this issue?


signing password

can i save keypass or storepass in asconfig.json?
when build air app,  i must input password everytime,  is bother.

VSCode does not provide a good way to do something like that, but I was able to come up with this workaround:
https://github.com/BowlerHatLLC/vscode-as3mxml/blob/v0.22.0/distribution/src/assembly/CHANGELOG.md#tips--tricks-1

thanks for your reply


Send adequate information to Hub

I don't know what we're sending to the Hub but we should make sure it is the right information to be able to diagnose problems. If we're sending insufficient or improper information this is a huge waste. So I'd like to know what we are collecting and sending. Plus we need to associate this installation information with the peer once it is registered. We also need to let the users know what we are collecting and why. So let's do this part right. It will help us make for a better experience over the long haul.

@crioto You and I discussed this and you said we needed to do a bit more to get this right and have information we can actually analyze.


Warning WEBGL_debug_renderer_info is deprecated in Firefox and will be removed. Please use RENDERER.

got this warning

Thanks for the message. I'm already aware of this and it can be safely ignored for now.


Don't install laravel 5.5.14

Hi, the composer fails:
C:\xampp\htdocs\api\cruscotto>composer require --dev "xethron/migrations-generator:~1.3.0"
./composer.json has been updated
Loading composer repositories with package information
Updating dependencies (including require-dev)
Your requirements could not be resolved to an installable set of packages.
Problem 1
- Installation request for xethron/migrations-generator ~1.3.0 -> satisfiable by xethron/migrations-generator[v1.3.0].
- Conclusion: remove laravel/framework v5.5.14
- Conclusion: don't install laravel/framework v5.5.14
- xethron/migrations-generator v1.3.0 requires illuminate/support ~4.1 -> satisfiable by illuminate/support[v4.1.0, v4.1.1, v4.1.10, v4.1.11, v4.1.12, v4.1.13, v4.1.14, v4.1.15, v4.1.16, v4.1.17, v4.1.18, v4.1.19, v4.1.2, v4.1.20, v4.1.21, v4.1.22, v4.1.23,
v4.1.24, v4.1.25, v4.1.26, v4.1.27, v4.1.28, v4.1.29, v4.1.3, v4.1.30, v4.1.4, v4.1.5, v4.1.6, v4.1.7, v4.1.8, v4.1.9, v4.2.1, v4.2.12, v4.2.16, v4.2.17, v4.2.2, v4.2.3, v4.2.4, v4.2.5, v4.2.6, v4.2.7, v4.2.8, v4.2.9].
- don't install illuminate/support v4.1.0|don't install laravel/framework v5.5.14
- don't install illuminate/support v4.1.1|don't install laravel/framework v5.5.14
- don't install illuminate/support v4.1.10|don't install laravel/framework v5.5.14
- don't install illuminate/support v4.1.11|don't install laravel/framework v5.5.14
- don't install illuminate/support v4.1.12|don't install laravel/framework v5.5.14
- don't install illuminate/support v4.1.13|don't install laravel/framework v5.5.14
- don't install illuminate/support v4.1.14|don't install laravel/framework v5.5.14
- don't install illuminate/support v4.1.15|don't install laravel/framework v5.5.14
- don't install illuminate/support v4.1.16|don't install laravel/framework v5.5.14
- don't install illuminate/support v4.1.17|don't install laravel/framework v5.5.14
- don't install illuminate/support v4.1.18|don't install laravel/framework v5.5.14
- don't install illuminate/support v4.1.19|don't install laravel/framework v5.5.14
- don't install illuminate/support v4.1.2|don't install laravel/framework v5.5.14
- don't install illuminate/support v4.1.20|don't install laravel/framework v5.5.14
- don't install illuminate/support v4.1.21|don't install laravel/framework v5.5.14
- don't install illuminate/support v4.1.22|don't install laravel/framework v5.5.14
- don't install illuminate/support v4.1.23|don't install laravel/framework v5.5.14
- don't install illuminate/support v4.1.24|don't install laravel/framework v5.5.14
- don't install illuminate/support v4.1.25|don't install laravel/framework v5.5.14
- don't install illuminate/support v4.1.26|don't install laravel/framework v5.5.14
- don't install illuminate/support v4.1.27|don't install laravel/framework v5.5.14
- don't install illuminate/support v4.1.28|don't install laravel/framework v5.5.14
- don't install illuminate/support v4.1.29|don't install laravel/framework v5.5.14
- don't install illuminate/support v4.1.3|don't install laravel/framework v5.5.14
- don't install illuminate/support v4.1.30|don't install laravel/framework v5.5.14
- don't install illuminate/support v4.1.4|don't install laravel/framework v5.5.14
- don't install illuminate/support v4.1.5|don't install laravel/framework v5.5.14
- don't install illuminate/support v4.1.6|don't install laravel/framework v5.5.14
- don't install illuminate/support v4.1.7|don't install laravel/framework v5.5.14
- don't install illuminate/support v4.1.8|don't install laravel/framework v5.5.14
- don't install illuminate/support v4.1.9|don't install laravel/framework v5.5.14
- don't install illuminate/support v4.2.1|don't install laravel/framework v5.5.14
- don't install illuminate/support v4.2.12|don't install laravel/framework v5.5.14
- don't install illuminate/support v4.2.16|don't install laravel/framework v5.5.14
- don't install illuminate/support v4.2.17|don't install laravel/framework v5.5.14
- don't install illuminate/support v4.2.2|don't install laravel/framework v5.5.14
- don't install illuminate/support v4.2.3|don't install laravel/framework v5.5.14
- don't install illuminate/support v4.2.4|don't install laravel/framework v5.5.14
- don't install illuminate/support v4.2.5|don't install laravel/framework v5.5.14
- don't install illuminate/support v4.2.6|don't install laravel/framework v5.5.14
- don't install illuminate/support v4.2.7|don't install laravel/framework v5.5.14
- don't install illuminate/support v4.2.8|don't install laravel/framework v5.5.14
- don't install illuminate/support v4.2.9|don't install laravel/framework v5.5.14
- Installation request for laravel/framework (locked at v5.5.14, required as 5.5.*) -> satisfiable by laravel/framework[v5.5.14].
How cai i fix this?
Thanks

Hello.
Version 1 isn't compatible with Laravel 5. When adding new dependencies with composer, it is recommended that you leave out the version number so that you can get the latest version available.
Try running: composer require --dev "xethron/migrations-generator"


Crash on inspecting a node connected to the output of 'Path from mask'

Description
As title says.
https://github.com/Ttanasart-pt/Pixel-Composer/assets/44508673/fe60b73d-6d01-4a58-9c9d-6db549f2c02e
I've also been able to experience similar issues with other nodes that "Trim Path" (used in this example)
Error message:
==========  Crash log [PXC <IP_ADDRESS>] [Windows] ==========

ERROR in
action number 1
of Draw Event
for object o_main:

index out of bounds request 39 maximum size is 39

========== Stack trace ==========

gml_Script_getPointDistance@anon@1168@Node_Path_From_Mask@node_path_from_mask (line 59)
gml_Script_getPointRatio@anon@2067@Node_Path_From_Mask@node_path_from_mask (line 69)
gml_Script_getPointRatio@anon@1990@Node_Path_Trim@node_path_trim (line 77)
gml_Script_drawOverlay@anon@553@Node_Path_Trim@node_path_trim (line 29)
gml_Script_drawNodeTools@Panel_Preview@panel_preview (line 1256)
gml_Script_drawContent@Panel_Preview@panel_preview (line 1742)
gml_Script_draw@anon@25943@PanelContent@panel_data (line 943)
gml_Script_drawPanel@Panel@panel_data (line 678)
gml_Script_draw@anon@10822@Panel@panel_data (line 411)
gml_Script_draw@anon@10822@Panel@panel_data (line 430)
gml_Script_draw@anon@10822@Panel@panel_data (line 430)
gml_Script_draw@anon@10822@Panel@panel_data (line 430)
gml_Script_draw@anon@10822@Panel@panel_data (line 430)
gml_Object_o_main_Draw_64 (line 43)

========= Crash log end =========

To reproduce

download minimal_reproductible.zip, extract it and open minimal_reproductible.pxc
Connect the node "Path from Mask" to the node "Trim Path" (using the input/output "Path")
Click on the "Trim Path" node

Expected
The inspection panels of the node opens.
Result
The UI disappears and a crash warning is created each frame.
Information
Pixel Composer <IP_ADDRESS>
Steam AND Itch.io version (tested on both)
Windows 11 23H2
AMD Ryzen 7 7840HS w/ Radeon 780M Graphics
NVIDIA GeForce RTX 4070 Laptop

Thank you for reporting. This bug should be fixed in the 1.17.2 beta, I'd recommend testing it there.

Tested with 1.17.rc5 and 1.17.3, can confirm it works perfectly.
I should have read the 1.17.2 Beta devlog, didn't know it was already fixed, sorry for the inconvenience.


add nomad_client_iface option

Sets network_interface in client config. That allows to choose interface on which nomad client will allocate tasks

Thank you!


Add parameter validation for ARIA modules

Summary: Based on #1643, this PR adds parameter validation for the ARIA module.
Work left: Allocate free error code for MBEDTLS_ERR_ARIA_BAD_INPUT_DATA. Slightly annoying because there are already two similar error codes MBEDTLS_ERR_ARIA_INVALID_KEY_LENGTH and MBEDTLS_ERR_ARIA_INVALID_INPUT_LENGTH, and we're running out of low level error codes.

Thanks @AndrzejKurek for your comments. I have fixed the issues you found and some further minor improvements.
The error code handling is still pending, but could you already check if you're ok with the rest? Thanks!

@sbutcher-arm Thanks for your review, I think I have addressed your comments. Specifically, apart from wording and style changes, I added a test for mbedtls_aes_free() to the new parameter validation test. I didn't change the selftest because I think that's out of scope of parameter validation.

Jenkins CI is failing on the BSD timing test. Good enough for a pass.

Jenkins CI is failing only on FreeBSD timing test which is as good as pass. Therefore ready to merge!


FileUpload Field Issue within Tabs?

Seems there is an issue with using tabs and the FileUpload field. Causes runaway network calls (see network console screenshot).
To reproduce
Steps to reproduce the behavior:
Define the follow schema:
    public static function form(Form $form)
    {
        return $form
            ->schema([
                Components\Tabs::make('Page')
                    ->tabs([
                        Components\Tab::make(
                            'Content',
                            [
                                Components\TextInput::make('record.title')
                                    ->autofocus()
                                    ->required(),
                                Components\Select::make('record.layout')
                                    ->dependable()
                                    ->placeholder('Choose the layout for this page.')
                                    ->options([
                                        'page' => 'page',
                                        'home' => 'home',
                                        'about' => 'about',
                                    ])
                                    ->only(Pages\CreatePage::class),
                                Components\Grid::make([
                                    \Filament\Resources\Forms\Components\BelongsToSelect::make('parent_id')
                                        ->relationship('parent', 'title'),
                                    Components\TextInput::make('record.slug')
                                        ->required()
                                        ->unique('pages', 'slug', true),
                                    Components\TextInput::make('record.order')
                                        ->type('number')
                                        ->numeric(),
                                ])->columns(3)->only(Pages\EditPage::class),
                                Components\group::make(config('fields.home', []))->when(fn ($record) => $record->layout === 'home'),
                                Components\group::make(config('fields.about', []))->when(fn ($record) => $record->layout === 'about'),
                                Components\group::make(config('fields.page', []))->when(fn ($record) => $record->layout === 'page'),
                            ]
                        ),
                        Components\Tab::make(
                            'SEO',
                            [
                                Components\TextInput::make('record.seo_title')
                                    ->maxLength(70)
                                    ->hint('May be used to override the page title.')
                                    ->helpMessage('The recommended length of an SEO title is somewhere between 65 to 70 characters including spaces.'),
                                Components\Textarea::make('record.seo_description')
                                    ->rows(3)
                                    ->maxLength(160)
                                    ->helpMessage('The suggested length of an SEO meta description is somewhere between 150 to 160 characters including spaces.'),
                                // This is the culprit! <------------------------------------------------------
                                Components\FileUpload::make('record.seo_image')
                                    ->image()
                                    ->maxSize(5000)

                            ]
                        ),
                    ]),
            ]);
    }

Watch the console.... it will be calling the Livewire page resource causing your fan to go wild!
Context

Package version: develop
Browser: All
Server OS: [e.g. Mac BigSur 11.2.3]
PHP version: [e.g. 7.4]
Database: [e.g. MySQL 8.0]

Additional details
Add any other details about the problem here.

@ryanscherler I'm going to try and reproduce this one now so we can get a patch out for it.

Closed by #179.


Merge to publish.

Docs Build status updates of commit d36ee37:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/microsoft-365-developer-program-faq.yml
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


"About" Page

Epic
#48
Description
### As a: potential employee or customer
I want to: learn more about FlowForge
So that: I can understand the type of company that FlowForge is, what they stand for, and understand their underlying principles and philosophies.
Acceptance Criteria

[ ] Layout Design
[ ] Visual Design - Hero Pictogram (#)
[ ] #53
[ ] #55
[ ] #52
[ ] #54

First iteration idea: Link the handbook about company page. While not ideal, the handbook is most up-to-date.

Do have this operational so far, if we can agree on text, I'd argue this was a much better first iteration to aim for:
https://user-images.githubusercontent.com/99246719/159886758-8eec6664-eba6-4607-b4a2-a4fccf0298e5.mov

:shipit: Agreed


MacOS: i386 is no longer supported

Due to this line:
https://github.com/munificent/wren/blob/master/util/build_libuv.py#L29
This error shows:
note: Using new build system
note: Planning build
note: Constructing build description
Build system information
error: The i386 architecture is deprecated. You should update your ARCHS build setting to remove the i386 architecture. (in target 'libuv')

** BUILD FAILED **

make[1]: *** [build/libuv.a] Error 65
make: *** [release] Error 2

Maybe it would be a better idea to use something like this to detect the architecture? I am not a Python guy so... this is a rather mashed-together thing...
<EMAIL_ADDRESS>/p/tmp $ cat test.py
import platform;

print("ARCHS=" + platform.architecture()[0])

<EMAIL_ADDRESS>/p/tmp $ python test.py
ARCHS=64bit

As long as you are not cross-compiling, it should be fine taking the current OS' architecture off platform.

Yeah, I can see that. Well, I just monkey-patched that script on my end to make it work properly. But this should get fixed, at some point, imho. :)


Documentation: Default useRelativeOutDir

It looks to me like the default value for useRelativeOutDir is actually true, not false. Not sure if you want to fix this in code or documentation but they definitely should match.

Thanks for noticing. I checked the other default values as well, now everything should be correct


feat: add feedback conversation support

This PR adds simple conversation support for the feedback() utility function with a new ..messages argument sink.
The purpose is to handle feedback that may not be resolvable with only one answer and that instead require back-and-forths. This may also prove useful if there are several people reviewing the thesis that may want to add comments to an existing piece of feedback.
Here is how the proposed implementation looks like:

This PR does not break any previous usage of feedback() but simply adds a ..messages argument sink that takes arrays of messages like so:
#feedback(
  ("Reviewer A", "This section needs more clarity.", "2023-10-30"),
  (
    "Author",
    "I've added more examples to make it clearer.",
    "2023-10-31, 10:00AM",
  ),
  (
    "Reviewer B",
    "Could you please add figures?",
    "2023-10-31, 2:00PM",
  ),
  (
    "Author",
    "I'll add some in the next revision.",
    "2023-11-01, 9:00AM",
  ),
)

Where pos0 is author name, pos1 is message content and pos2 is date.
This also means that one can theoretically add a list of messages after the feedback and response arguments (even though I see little use in that).
If the idea seems good, we could think about specific improvements, e.g. define a unique for every author name to make it easier to read when there are several people commenting, among other things.

Thanks for the PR. @otytlandsvik and I had a little discussion about this feature and came to the conclusion that it is currently out of scope for the project and would be better suited as a separate package.


Create splitAndJoinString.py

Python program to Split a string based on a delimiter and join the string using another delimiter


Update quoted true, false in configmap

The non-quoted true, false variable assignment in the argocd-image-updater-config ConfigMap is causing failures. Quoted them now.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.