Nuki lock improvements

Description:
Nuki lock component improvements:

Bride port: The port parameter was not forwarded on bridge component initialization.
timeout configuration parameter (optional): The user can establish the timeout in the component configuration. Default is 5s
lock_reachable attribute: New boolean attribute to check if the communication HA <-> brigde and bridge <-> lock is fine.
Check connection service: If, by any reason, the connection between the bridge and the lock was lost, there was no way to detect it. There is now a new service to force the communication between the bridge and the lock, instead of retrieving the last know state. If that communication fails, the attribute lock_reachable will become true.
unlatch_to_unlock configuration parameter (optional): If set to true, when calling the service unlock, the lock will unlatch. Default is false.

Example entry for configuration.yaml (if applicable):
lock:
  - platform: nuki
    host: <IP_ADDRESS>
    port: 8080
    token: [token]
    timeout: 25
    unlatch_to_unlock: true

Checklist:

[x] The code change is tested and works locally.
[x] Local tests pass with tox. Your PR cannot be merged unless tests pass
[x] There is no commented out code in this PR.

If user exposed functionality or configuration variables are added/changed:

[x] Documentation added/updated in home-assistant.io

If the code communicates with devices, web services, or third-party tools:

[x] New dependencies have been added to the REQUIREMENTS variable (example).
[x] New dependencies are only imported inside functions that use them (example).
[x] New or updated dependencies have been added to requirements_all.txt by running script/gen_requirements_all.py.

Hi @franfos,
It seems you haven't yet signed a CLA. Please do so here.
Once you do that we will be able to review and accept this pull request.
Thanks!

Second. Remove the unlatch option and implement the open function: https://github.com/home-assistant/home-assistant/blob/dev/homeassistant/components/homematic/lock.py

Regarding the timeout, I made it configurable because the Nuki lockstate command takes aorund that time to answer. That was in my case, with a android phone acting as a bridge.
The check_connection service uses that lockstate command, and I though this service could act as a watchdog to test if the connection is fine (1 per hour e.g.).
The problem is that if the bridge turns off, the update service will try to connect with that timeout.
But the default value is 5s, so only should be changed in case of necessity.

Second. Remove the unlatch option and implement the open function: https://github.com/home-assistant/home-assistant/blob/dev/homeassistant/components/homematic/lock.py

Will it use the lock the open function by default in the case it is defined?
I use the lock with homekit, and when I trigger "Siri, open the door" it just unlocks.
I had to made a template lock to use lock to lock, and unlatch to unlock.

So, what's next?
I've made a new version removing the nuki_unlatch service and implementing the open service.
I've tried this, and the default command to open still it is unlock. So, even with the open service, the Siri command "Open lock" just unlocks, it doesn't unlatch.
So I think it's still necessary the config parameter unlatch_to_unlock (I even suggest it should be a default parameter for all the lock components).
The timeout parameter, in my case, is necessary. By default, it acts as now, 5s.
Do I made a new PR with this version?


99 add guards

fixes #99

@rultor merge

@rultor merge

@kerelape OK, I'll try to merge now. You can check the progress of the merge here

@rultor merge

@kerelape Done! FYI, the full log is here (took me 1min)


tests/integration/test_flight_level.py::test_flight_level FAILED

tests/integration/test_flight_level.py::test_flight_level FAILED
The above test currently fails.  If the string
            # isn't utf-8, we fall back to iso-8859-1 for all other
            # encodings. (See PR #3538)
            try:
                reason = self.reason.decode('utf-8')
            except UnicodeDecodeError:
                reason = self.reason.decode('iso-8859-1')
        else:
            reason = self.reason

        if 400 <= self.status_code < 500:
            http_error_msg = u'%s Client Error: %s for url: %s' % (self.status_code, reason, self.url)

        elif 500 <= self.status_code < 600:
            http_error_msg = u'%s Server Error: %s for url: %s' % (self.status_code, reason, self.url)

        if http_error_msg:
>           raise HTTPError(http_error_msg, response=self)
E           requests.exceptions.HTTPError: 405 Client Error: METHOD NOT ALLOWED for url: http://localhost:5001/api/v1/alt?acid=SCN1001

This is resolved by upgrading dependency of Bluebird to v1.3.0
Tested locally with release/1.3.0 branch of bluebird and v1.2.1 of bluesky
This can be closed upon successful merge of https://github.com/alan-turing-institute/bluebird/pull/68 and subsequent docker image build with the corresponding tag

Closing with the merge of https://github.com/alan-turing-institute/bluebird/pull/68 and checks confirmed with https://travis-ci.com/alan-turing-institute/simurgh/jobs/239319990


Support for LISTEN/NOTIFY ?

Are there any plans to support PostgreSQL LISTEN/NOTIFY ?

Should be mostly implemented. Please test and let me know if anything is missing.

WOW, thanks a lot!
I have a few ideas to make the API a bit more useful:

add the handler functor to the listen member functions (e.g. conn.listen("channel", [](const char* channelName, const char* payload){///...});
optionally add a poor man's event loop to handle external notifications? I.e. create another thread which will monitor socket and will process the notifications.

For 1. you could write your own dispatcher easily:
void handle_foo( const char* payload )
{
   // ...
}

struct
{
   std::map< std::string, std::function< void( const char* payload ) >, std::less<> > dispatcher;

   void operator()( const tao::pq::notification& n )
   {
      const auto it = dispatcher.find( n.channel_name() );
      if( it != dispatcher.end() ) {
         it->second( n.payload() );
      }
   }

} handle_notification;

// later, do this:

connection->set_notification_handler( std::ref( handle_notification ) );
handle_notification.dispatcher[ "FOO" ] = &handle_foo;

Of course, there are other options to implement that. The handler-class should have set/reset-methods for the channels, etc.
But you could also have a list of handlers per channel, not just a single handler. But then how do you delete the handlers for a channel, etc. I'm not sure what a generic solution should look like. Thoughts?

But then how do you delete the handlers for a channel, etc. I'm not sure what a generic solution should look like. Thoughts?

You already added reset_notification_handler it just needs a channel parameter :)
Another idea is to pass an empty functor to set listener e.g. conn.listen("channel",{});.
But as you said it, people can implement their own dispatchers.

But then how do you delete the handlers for a channel, etc. I'm not sure what a generic solution should look like. Thoughts?

You already added reset_notification_handler it just needs a channel parameter :)

The sentence you quoted was preceded by "But you could also have a list of handlers per channel, not just a single handler." In that context it's not just a channel name to identify the handler to delete.

But as you said it, people can implement their own dispatchers.

I'm not against a more convenient interface, I just need to balance it properly. I am still considering your ideas, I just don't want to rush it.


There is a vulnerability in kramdown:1.17.0,upgrade recommended

https://github.com/facebook/flow/blob/7dbc03f12d7388dc9dc4e1e9084a70668d51e95f/website/Gemfile.lock#L94
CVE-2020-14001
Recommended upgrade version：2.0.0.beta2

No longer a dep


Instance arguments should not automatically be class constraints

I was trying to compile the following code, where I wanted to use instance arguments to ease the proof search a bit:
open import Haskell.Prim
open import Agda.Builtin.Nat

data _≤_ : Nat → Nat → Set where
  instance
    zero-≤ : ∀ {n} → zero ≤ n
    suc-≤ : ∀ {m n} → {{m ≤ n}} → suc m ≤ suc n

data Tree {l u : Nat} : Set where
  Leaf  : {{l ≤ u}} → Tree {l} {u}
  Node  : (x : Nat) → Tree {l} {x} → Tree {x} {u} → Tree {l} {u}
{-# COMPILE AGDA2HS Tree #-}

However, this is currently rejected by Agda2Hs:
Not supported: constructors with class constraints

I see two possible solutions:

We could make the compilation of instance arguments smarter, only translating them to a class constraint if there is actually a class with that name.
We could have a different way to let the user indicate which instance arguments should or should not be compiled. The natural thing to do would be to use the runtime irrelevance annotation @0.

Option 2 has now been implemented, and upon reflection I don't think we should make the backend smarter than necessary, so I'm closing this.

Actually the error is still there even with @0


Bad performance for running this project

Hi, I am trying to run the tritonserver and flask proxy in the same container and found that the performance is bad.
<IP_ADDRESS> - - [10/Sep/2022 08:46:43] "POST /v1/engines/codegen/completions HTTP/1.1" 200 -
Returned completion in 6501.662492752075 ms
<IP_ADDRESS> - - [10/Sep/2022 08:46:45] "POST /v1/engines/codegen/completions HTTP/1.1" 200 -
Returned completion in 6626.265287399292 ms
<IP_ADDRESS> - - [10/Sep/2022 08:46:45] "POST /v1/engines/codegen/completions HTTP/1.1" 200 -
Returned completion in 6687.429904937744 ms
<IP_ADDRESS> - - [10/Sep/2022 08:46:46] "POST /v1/engines/codegen/completions HTTP/1.1" 200 -
Returned completion in 6587.698698043823 ms
<IP_ADDRESS> - - [10/Sep/2022 08:46:46] "POST /v1/engines/codegen/completions HTTP/1.1" 200 -
Returned completion in 5684.9658489227295 ms
<IP_ADDRESS> - - [10/Sep/2022 08:46:46] "POST /v1/engines/codegen/completions HTTP/1.1" 200 -
Returned completion in 5248.137474060059 ms
<IP_ADDRESS> - - [10/Sep/2022 08:46:46] "POST /v1/engines/codegen/completions HTTP/1.1" 200 -
Returned completion in 4866.7027950286865 ms
<IP_ADDRESS> - - [10/Sep/2022 08:46:46] "POST /v1/engines/codegen/completions HTTP/1.1" 200 -
Returned completion in 4606.655836105347 ms
<IP_ADDRESS> - - [10/Sep/2022 08:46:46] "POST /v1/engines/codegen/completions HTTP/1.1" 200 -

Every request need 4 or more seconds. This is not acceptable...But I am usng a V100 gpu which I think is good enough. Hope someone can help me figure out the reason.
This is the config.env:
MODEL=codegen-350M-multi
NUM_GPUS=1
MODEL_DIR=...

This is the nvidia-smi info:
+-----------------------------------------------------------------------------+
| NVIDIA-SMI 470.86       Driver Version: 470.86       CUDA Version: 11.7     |
|-------------------------------+----------------------+----------------------+
| GPU  Name        Persistence-M| Bus-Id        Disp.A | Volatile Uncorr. ECC |
| Fan  Temp  Perf  Pwr:Usage/Cap|         Memory-Usage | GPU-Util  Compute M. |
|                               |                      |               MIG M. |
|===============================+======================+======================|
|   0  Tesla V100-PCIE...  Off  | 00000000:06:00.0 Off |                    0 |
| N/A   32C    P0    36W / 250W |   1649MiB / 32510MiB |      0%      Default |
|                               |                      |                  N/A |
+-------------------------------+----------------------+----------------------+

+-----------------------------------------------------------------------------+
| Processes:                                                                  |
|  GPU   GI   CI        PID   Type   Process name                  GPU Memory |
|        ID   ID                                                   Usage      |
|=============================================================================|
+-----------------------------------------------------------------------------+

And here is the log when start the tritonserver:
I0910 08:43:31.338765 258862 pinned_memory_manager.cc:240] Pinned memory pool is created at '0x7f5498000000' with size 268435456
I0910 08:43:31.339558 258862 cuda_memory_manager.cc:105] CUDA memory pool is created on device 0 with size 67108864
I0910 08:43:31.346725 258862 model_repository_manager.cc:1191] loading: fastertransformer:1
I0910 08:43:31.567535 258862 libfastertransformer.cc:1226] TRITONBACKEND_Initialize: fastertransformer
I0910 08:43:31.567573 258862 libfastertransformer.cc:1236] Triton TRITONBACKEND API version: 1.10
I0910 08:43:31.567581 258862 libfastertransformer.cc:1242] 'fastertransformer' TRITONBACKEND API version: 1.10
I0910 08:43:31.567638 258862 libfastertransformer.cc:1274] TRITONBACKEND_ModelInitialize: fastertransformer (version 1)
W0910 08:43:31.569452 258862 libfastertransformer.cc:149] model configuration:
{
    "name": "fastertransformer",
    "platform": "",
    "backend": "fastertransformer",
    "version_policy": {
        "latest": {
            "num_versions": 1
        }
    },
    "max_batch_size": 1024,
    "input": [
        {
            "name": "input_ids",
            "data_type": "TYPE_UINT32",
            "format": "FORMAT_NONE",
            "dims": [
                -1
            ],
            "is_shape_tensor": false,
            "allow_ragged_batch": false,
            "optional": false
        },
        {
            "name": "start_id",
            "data_type": "TYPE_UINT32",
            "format": "FORMAT_NONE",
            "dims": [
                1
            ],
            "reshape": {
                "shape": []
            },
            "is_shape_tensor": false,
            "allow_ragged_batch": false,
            "optional": true
        },
        {
            "name": "end_id",
            "data_type": "TYPE_UINT32",
            "format": "FORMAT_NONE",
            "dims": [
                1
            ],
            "reshape": {
                "shape": []
            },
            "is_shape_tensor": false,
            "allow_ragged_batch": false,
            "optional": true
        },
        {
            "name": "input_lengths",
            "data_type": "TYPE_UINT32",
            "format": "FORMAT_NONE",
            "dims": [
                1
            ],
            "reshape": {
                "shape": []
            },
            "is_shape_tensor": false,
            "allow_ragged_batch": false,
            "optional": false
        },
        {
            "name": "request_output_len",
            "data_type": "TYPE_UINT32",
            "format": "FORMAT_NONE",
            "dims": [
                -1
            ],
            "is_shape_tensor": false,
            "allow_ragged_batch": false,
            "optional": false
        },
        {
            "name": "runtime_top_k",
            "data_type": "TYPE_UINT32",
            "format": "FORMAT_NONE",
            "dims": [
                1
            ],
            "reshape": {
                "shape": []
            },
            "is_shape_tensor": false,
            "allow_ragged_batch": false,
            "optional": true
        },
        {
            "name": "runtime_top_p",
            "data_type": "TYPE_FP32",
            "format": "FORMAT_NONE",
            "dims": [
                1
            ],
            "reshape": {
                "shape": []
            },
            "is_shape_tensor": false,
            "allow_ragged_batch": false,
            "optional": true
        },
        {
            "name": "beam_search_diversity_rate",
            "data_type": "TYPE_FP32",
            "format": "FORMAT_NONE",
            "dims": [
                1
            ],
            "reshape": {
                "shape": []
            },
            "is_shape_tensor": false,
            "allow_ragged_batch": false,
            "optional": true
        },
        {
            "name": "temperature",
            "data_type": "TYPE_FP32",
            "format": "FORMAT_NONE",
            "dims": [
                1
            ],
            "reshape": {
                "shape": []
            },
            "is_shape_tensor": false,
            "allow_ragged_batch": false,
            "optional": true
        },
        {
            "name": "len_penalty",
            "data_type": "TYPE_FP32",
            "format": "FORMAT_NONE",
            "dims": [
                1
            ],
            "reshape": {
                "shape": []
            },
            "is_shape_tensor": false,
            "allow_ragged_batch": false,
            "optional": true
        },
        {
            "name": "repetition_penalty",
            "data_type": "TYPE_FP32",
            "format": "FORMAT_NONE",
            "dims": [
                1
            ],
            "reshape": {
                "shape": []
            },
            "is_shape_tensor": false,
            "allow_ragged_batch": false,
            "optional": true
        },
        {
            "name": "random_seed",
            "data_type": "TYPE_INT32",
            "format": "FORMAT_NONE",
            "dims": [
                1
            ],
            "reshape": {
                "shape": []
            },
            "is_shape_tensor": false,
            "allow_ragged_batch": false,
            "optional": true
        },
        {
            "name": "is_return_log_probs",
            "data_type": "TYPE_BOOL",
            "format": "FORMAT_NONE",
            "dims": [
                1
            ],
            "reshape": {
                "shape": []
            },
            "is_shape_tensor": false,
            "allow_ragged_batch": false,
            "optional": true
        },
        {
            "name": "beam_width",
            "data_type": "TYPE_UINT32",
            "format": "FORMAT_NONE",
            "dims": [
                1
            ],
            "reshape": {
                "shape": []
            },
            "is_shape_tensor": false,
            "allow_ragged_batch": false,
            "optional": true
        },
        {
            "name": "bad_words_list",
            "data_type": "TYPE_INT32",
            "format": "FORMAT_NONE",
            "dims": [
                2,
                -1
            ],
            "is_shape_tensor": false,
            "allow_ragged_batch": false,
            "optional": true
        },
        {
            "name": "stop_words_list",
            "data_type": "TYPE_INT32",
            "format": "FORMAT_NONE",
            "dims": [
                2,
                -1
            ],
            "is_shape_tensor": false,
            "allow_ragged_batch": false,
            "optional": true
        }
    ],
    "output": [
        {
            "name": "output_ids",
            "data_type": "TYPE_UINT32",
            "dims": [
                -1,
                -1
            ],
            "label_filename": "",
            "is_shape_tensor": false
        },
        {
            "name": "sequence_length",
            "data_type": "TYPE_UINT32",
            "dims": [
                -1
            ],
            "label_filename": "",
            "is_shape_tensor": false
        },
        {
            "name": "cum_log_probs",
            "data_type": "TYPE_FP32",
            "dims": [
                -1
            ],
            "label_filename": "",
            "is_shape_tensor": false
        },
        {
            "name": "output_log_probs",
            "data_type": "TYPE_FP32",
            "dims": [
                -1,
                -1
            ],
            "label_filename": "",
            "is_shape_tensor": false
        }
    ],
    "batch_input": [],
    "batch_output": [],
    "optimization": {
        "priority": "PRIORITY_DEFAULT",
        "input_pinned_memory": {
            "enable": true
        },
        "output_pinned_memory": {
            "enable": true
        },
        "gather_kernel_buffer_threshold": 0,
        "eager_batching": false
    },
    "instance_group": [
        {
            "name": "fastertransformer_0",
            "kind": "KIND_CPU",
            "count": 1,
            "gpus": [],
            "secondary_devices": [],
            "profile": [],
            "passive": false,
            "host_policy": ""
        }
    ],
    "default_model_filename": "codegen-350M-multi",
    "cc_model_filenames": {},
    "metric_tags": {},
    "parameters": {
        "start_id": {
            "string_value": "50256"
        },
        "model_name": {
            "string_value": "codegen-350M-multi"
        },
        "is_half": {
            "string_value": "1"
        },
        "enable_custom_all_reduce": {
            "string_value": "0"
        },
        "vocab_size": {
            "string_value": "51200"
        },
        "tensor_para_size": {
            "string_value": "1"
        },
        "decoder_layers": {
            "string_value": "20"
        },
        "size_per_head": {
            "string_value": "64"
        },
        "max_seq_len": {
            "string_value": "2048"
        },
        "end_id": {
            "string_value": "50256"
        },
        "inter_size": {
            "string_value": "4096"
        },
        "head_num": {
            "string_value": "16"
        },
        "model_type": {
            "string_value": "GPT-J"
        },
        "model_checkpoint_path": {
            "string_value": "/model/fastertransformer/1/1-gpu"
        },
        "rotary_embedding": {
            "string_value": "32"
        },
        "pipeline_para_size": {
            "string_value": "1"
        }
    },
    "model_warmup": []
}
I0910 08:43:31.569890 258862 libfastertransformer.cc:1320] TRITONBACKEND_ModelInstanceInitialize: fastertransformer_0 (device 0)
W0910 08:43:31.569915 258862 libfastertransformer.cc:453] Faster transformer model instance is created at GPU '0'
W0910 08:43:31.569922 258862 libfastertransformer.cc:459] Model name codegen-350M-multi
W0910 08:43:31.569940 258862 libfastertransformer.cc:578] Get input name: input_ids, type: TYPE_UINT32, shape: [-1]
W0910 08:43:31.569948 258862 libfastertransformer.cc:578] Get input name: start_id, type: TYPE_UINT32, shape: [1]
W0910 08:43:31.569954 258862 libfastertransformer.cc:578] Get input name: end_id, type: TYPE_UINT32, shape: [1]
W0910 08:43:31.569960 258862 libfastertransformer.cc:578] Get input name: input_lengths, type: TYPE_UINT32, shape: [1]
W0910 08:43:31.569966 258862 libfastertransformer.cc:578] Get input name: request_output_len, type: TYPE_UINT32, shape: [-1]
W0910 08:43:31.569972 258862 libfastertransformer.cc:578] Get input name: runtime_top_k, type: TYPE_UINT32, shape: [1]
W0910 08:43:31.569978 258862 libfastertransformer.cc:578] Get input name: runtime_top_p, type: TYPE_FP32, shape: [1]
W0910 08:43:31.569984 258862 libfastertransformer.cc:578] Get input name: beam_search_diversity_rate, type: TYPE_FP32, shape: [1]
W0910 08:43:31.569990 258862 libfastertransformer.cc:578] Get input name: temperature, type: TYPE_FP32, shape: [1]
W0910 08:43:31.569995 258862 libfastertransformer.cc:578] Get input name: len_penalty, type: TYPE_FP32, shape: [1]
W0910 08:43:31.570001 258862 libfastertransformer.cc:578] Get input name: repetition_penalty, type: TYPE_FP32, shape: [1]
W0910 08:43:31.570006 258862 libfastertransformer.cc:578] Get input name: random_seed, type: TYPE_INT32, shape: [1]
W0910 08:43:31.570012 258862 libfastertransformer.cc:578] Get input name: is_return_log_probs, type: TYPE_BOOL, shape: [1]
W0910 08:43:31.570018 258862 libfastertransformer.cc:578] Get input name: beam_width, type: TYPE_UINT32, shape: [1]
W0910 08:43:31.570024 258862 libfastertransformer.cc:578] Get input name: bad_words_list, type: TYPE_INT32, shape: [2, -1]
W0910 08:43:31.570034 258862 libfastertransformer.cc:578] Get input name: stop_words_list, type: TYPE_INT32, shape: [2, -1]
W0910 08:43:31.570046 258862 libfastertransformer.cc:620] Get output name: output_ids, type: TYPE_UINT32, shape: [-1, -1]
W0910 08:43:31.570053 258862 libfastertransformer.cc:620] Get output name: sequence_length, type: TYPE_UINT32, shape: [-1]
W0910 08:43:31.570059 258862 libfastertransformer.cc:620] Get output name: cum_log_probs, type: TYPE_FP32, shape: [-1]
W0910 08:43:31.570065 258862 libfastertransformer.cc:620] Get output name: output_log_probs, type: TYPE_FP32, shape: [-1, -1]
[FT][WARNING] Custom All Reduce only supports 8 Ranks currently. Using NCCL as Comm.
I0910 08:43:31.853587 258862 libfastertransformer.cc:307] Before Loading Model:
after allocation, free 31.19 GB total 31.75 GB
[WARNING] gemm_config.in is not found; using default GEMM algo
I0910 08:43:34.250280 258862 libfastertransformer.cc:321] After Loading Model:
after allocation, free 30.33 GB total 31.75 GB
I0910 08:43:34.251457 258862 libfastertransformer.cc:537] Model instance is created on GPU Tesla V100-PCIE-32GB
I0910 08:43:34.252189 258862 model_repository_manager.cc:1345] successfully loaded 'fastertransformer' version 1
I0910 08:43:34.252418 258862 server.cc:556]
+------------------+------+
| Repository Agent | Path |
+------------------+------+
+------------------+------+

I0910 08:43:34.252533 258862 server.cc:583]
+-------------------+--------------------------------------------+--------------------------------------------+
| Backend           | Path                                       | Config                                     |
+-------------------+--------------------------------------------+--------------------------------------------+
| fastertransformer | /opt/tritonserver/backends/fastertransform | {"cmdline":{"auto-complete-config":"false" |
|                   | er/libtriton_fastertransformer.so          | ,"min-compute-capability":"6.000000","back |
|                   |                                            | end-directory":"/opt/tritonserver/backends |
|                   |                                            | ","default-max-batch-size":"4"}}           |
|                   |                                            |                                            |
+-------------------+--------------------------------------------+--------------------------------------------+

I0910 08:43:34.252618 258862 server.cc:626]
+-------------------+---------+--------+
| Model             | Version | Status |
+-------------------+---------+--------+
| fastertransformer | 1       | READY  |
+-------------------+---------+--------+

I0910 08:43:34.298144 258862 metrics.cc:650] Collecting metrics for GPU 0: Tesla V100-PCIE-32GB
I0910 08:43:34.298580 258862 tritonserver.cc:2159]
+----------------------------------+----------------------------------------------------------------------------+
| Option                           | Value                                                                      |
+----------------------------------+----------------------------------------------------------------------------+
| server_id                        | triton                                                                     |
| server_version                   | 2.23.0                                                                     |
| server_extensions                | classification sequence model_repository model_repository(unload_dependent |
|                                  | s) schedule_policy model_configuration system_shared_memory cuda_shared_me |
|                                  | mory binary_tensor_data statistics trace                                   |
| model_repository_path[0]         | /openbayes/home/fauxpilot/models/codegen-350M-multi-1gpu                   |
| model_control_mode               | MODE_NONE                                                                  |
| strict_model_config              | 1                                                                          |
| rate_limit                       | OFF                                                                        |
| pinned_memory_pool_byte_size     | 268435456                                                                  |
| cuda_memory_pool_byte_size{0}    | 67108864                                                                   |
| response_cache_byte_size         | 0                                                                          |
| min_supported_compute_capability | 6.0                                                                        |
| strict_readiness                 | 1                                                                          |
| exit_timeout                     | 30                                                                         |
+----------------------------------+----------------------------------------------------------------------------+

I0910 08:43:34.329038 258862 grpc_server.cc:4587] Started GRPCInferenceService at <IP_ADDRESS>:8001
I0910 08:43:34.329462 258862 http_server.cc:3303] Started HTTPService at <IP_ADDRESS>:8000
I0910 08:43:34.370706 258862 http_server.cc:178] Started Metrics Service at <IP_ADDRESS>:8002

Did you set an excessive `max_token' value?  If the value is too large it may take a huge amount of time to calculate, for instant response I recommend setting it to 32 or less.

I would also add that you should use stop tokens to stop generation when you've generated enough. This is one of the biggest "tricks" Copilot uses; all of their requests are 512 tokens but due to stop tokens they almost never actually generate that many.

Thanks for the replies. These are really helpful. And if I am using the copilot plugin where should I put these configs?

Here is a request generated from vs code, it seems that the stop is already added. But the speed is still very slow.

My 3090 GPU is going to be crazy when I set max_tokens to 100, and it would take minutes to get suggestions appear. Just curious about the capability of your GPU.

My 3090 GPU is going to be crazy when I set max_tokens to 100, and it would take minutes to get suggestions appear. Just curious about the capability of your GPU.

You can see my configs in the issue and with the default config of max_tokens = 500 and the codegen-350M-multi model, it may take more than 3 - 4 seconds to get results...But the response time is kind of random... sometimes the result returns fast.
BTW, how can I change the max_tokens in VS Code copilot plugin?

If you go to Advanced -> Edit in settings.json in the Copilot VSCode settings, you should be able to see what extra settings are available. I think the one you want is length:


start testing across multiple browsers and OSs

let's test on iOS that's always a massive shit
also, lets check it on an ipad pro

I don't happen to have either :P

I'll do it tomorrow in the office then
On Tue, 15 Dec 2015 at 14:14 Alex Lee<EMAIL_ADDRESS>wrote:

I don't happen to have either :P
—
Reply to this email directly or view it on GitHub
https://github.com/bvn-architecture/styleguide/issues/47#issuecomment-164631900
.


What is the exact version of Python? Is it 3.8.0?

What is the exact version of Python? Is it 3.8.0? I encounter numerous errors when I execute pip install -r requirements.txt after running conda create -n gs python=3.8 and conda activate gs.

Hi. I just confirmed that the version of Python is 3.8.13, and I hope it can be of help to you.

What is the exact version of Python? Is it 3.8.0? I encounter numerous errors when I execute pip install -r requirements.txt after running conda create -n gs python=3.8 and conda activate gs.


Add collect supportconfig to Ardana

Add collect supportconfig to Ardana

@jennywei8 , do you still need this PR ? If not, could you close it please in favor of #3648 ?

code now, it is related to 3648


Add Linting

Description
We need to add eslint and stylelint to the project to add consistency to components.

Closed by #9


Change an F to an R as a typo fix [JIRA: CLIENTS-1038]

Context
FiakFutureListener isn't a thing, but RiakFutureListener is.
Expected Behavior
A user should read 'RiakFutureListener' in the javadoc
Actual Behavior
A user reads 'FiakFutureListener' in the javadoc, and is subsequently so confused that they decide to give up writing code and become a 'scrum master'.
Possible Fix
Someone else makes the change from an F to an R
Steps to Reproduce

Look at the docs

Context
I chuckled, and then opened this issue/PR. Then, after all of this typing for a one letter change, I also questioned my ability to properly manage time.
Your Environment

[ 2.0.7] Riak Java Client version
[8 ] Java version
[ ] Riak version
[ ] Operating System / Distribution & Version
[ ] Riak's error.log file, if applicable
[ ] What methods were being executed during the error
[ ] What you expected to have happen
[ ] Sample data, if applicable

Fixed, or closed via GitHub issues.
[posted via JIRA by Alexander Moore]


Link in github issue template 404s

The above appears at the top of the github issue template when creating a new issue in this repository:
<!--
If you suspect your issue is a bug, please attach the output of the info page, see
https://help.datadoghq.com/hc/en-us/articles/203764635-Agent-Status-and-Information

-->

The link 404s and the 404 page has no link to any updated documentation for this particular topic.

Thanks for reporting this @nicbarker! Fixed with https://github.com/DataDog/datadog-agent/pull/2179

Thanks @olivielpeau for the quick fix!


Errback api

What do you think of this, as an idea?
I'm not sure about the "_create_future()" API, and perhaps an interface would be nice for "the thing we give to errbacks" (i.e. Failure or AsyncioFailure).
I'm hopeful there's a better way to get asyncio to do an event-loop iteration, or call all completed Futures or whatever. But for now at least all the error-case tests can run in both asyncio and Twisted.

@meejah Thanks for splitting this out into a separate PR! I have been thinking about this. Please be prepared for more discussions;) You might wonder why I'm so reluctant and not merge such a relatively straight-forward PR right away .. I will try to explain why.
What we do actually do here is come up with a mixin that allows one to write idiomatic code that runs on both Twisted and asyncio: source code compatibility.
The uniform handling of failures (and hence the need for a asyncio analog to Twisted's Failure) is just one aspect. Regarding this specific latter aspect, I am wondering what the asyncio guys think about on the mailing list (python-tulip).
Further, the current classes in AutobahnPython are somewhat misplaced/misdesigned for the general task above anyway:
https://github.com/tavendo/AutobahnPython/issues/242
https://github.com/tavendo/AutobahnPython/issues/243
For these reasons, I think it would be great if we took the chance and come up with a solution that actually solves #242 and #243 too.
As this could be of use not only in AutobahnPython, I have created: https://github.com/tavendo/txaio
AutobahnPython currently only depends on six. With above, the 2nd dependency would be txaio.
So the task would be: write txaio and adjust the AutobahnPython code to using that. What do you think? Makes sense?

No worries, I understand why you want to get this right.
In the end, for Twisted, it provides really nice default logging if we can call log.err(failure, informative_message). To do anything remotely similar with asyncio we need the three args from sys.exc_info() (from what I understand) so that we could make up log messages with a stack-trace (if desired).
I'll have to look into tulip/asyncio some more to get a better handle how this sort of thing is "normally" done in callbacks.
The other piece (that I basically just hacked in "something" in this PR) is the testing aspect. I can't find any information about the/"a" recommended way to "wait" for your Future in a test (i.e. like returning a Defered to trial or pytest-twisted). In the tests I wrote, all the Futures/Deferreds are for sure immediately available, but you still need to get asyncio to "wait" once.
What might be worthwhile -- perhaps as part of txaio -- would be a pytest plugin or similar (just a utility method?) that makes test-writing a little easier with less if statements ;)

p.s. in the meantime, do you think it's worth making a (somewhat smaller) PR that at least fixes the things that definitely won't work in protocol.py + asyncio? I think there's only two:

https://github.com/tavendo/AutobahnPython/blob/master/autobahn/wamp/protocol.py#L573
https://github.com/tavendo/AutobahnPython/blob/master/autobahn/wamp/protocol.py#L810

...but I guess also, onUserError will "fail" for the cases where it's called from an errback (traceback.print_exc() will be sad if there's no current exception). Not fatal, but it won't print anything.

Additionally, instead of a mixin-style class (requiring inheritence, even though they're all static methods), what about just having txaio provide the API methods? Then at import-time txaio determines whether to use the Twisted or asyncio (or Trollius) "real" methods.
So client code (e.g. in Autobahn) would end up looking something like:
   import txaio

   d = txaio.create_future()
   ...
   txaio.resolve_future(d, "yay")

   class Something(object):
       def do_a_thing(self):
            return txaio.create_future_success("it worked")

...etc. This would allow users of txaio decide whether they wanted to use inheritence or composition or bare methods or whatever to accomplish their task. What do you think?

@meejah Ah, I like it. Only exposing simple functions in txaio, and let users choose.
I think users should be able to actively select Twisted vs asyncio, even when both are available.
from txaio import tx as txaio

vs
from txaio import aio as txaio

or something like it.
We still would use these functions then in AutobahnPython to create a (private) mixin class?
Since the reason the current code looks like it does is because I was looking for a solution with the following.
Consider
https://github.com/tavendo/AutobahnPython/blob/master/autobahn/wamp/protocol.py#L1004
Essentially, the code there should run on both Twisted and asyncio. The concrete classes for ApplicationSession for Twisted and asyncio then mix in the respective FutureMixin, which provides
https://github.com/tavendo/AutobahnPython/blob/master/autobahn/twisted/wamp.py#L62
https://github.com/tavendo/AutobahnPython/blob/master/autobahn/asyncio/wamp.py#L59
The user then imports the concrete class
from autobahn.wamp.twisted import ApplicationSession
from autobahn.wamp.asyncio import ApplicationSession

Or is there a different solution?

We could use txaio` via mixins like currently (that call-through to txaio) , but I was thinking along the lines that any code like self._create_future()would simply becometxaio.create_future()`` and there'd be no need for mixins. Users would "select" asyncio/trollius/twisted by installing them. As in: if you have Twisted, you use it; else try asyncio; else try trollius; else fail.
That is, import txaio would basically just try to import things until something works. If "user selects what they want, even though they have asyncio AND Twisted around" is a use-case I'll think a little more on it :) but that could be as simple as your "import ... as" examples above.
So far the only hard part is trying to support the nice options Twisted has for "DeferredList"  and gather. I might split this API so its simpler code, and more-explicit/easier to understand from the user level.

There's a case where Twisted and asyncio will be available - if you have Twisted installed on py3, the majority of core is ported. So, you'd need to be explicit in which one to choose.

Here are the requirements that come to mind:

User must be able to chose between Twisted and asyncio when both are installed.
As far as Autobahn is concerned, for compability reasons, this has to be done by importing the respective classes in user code, like

from autobahn.wamp.twisted import ApplicationSession

within Autobahn itself, we want as much code as possible written in a language agnostic way

I currently don't see how we can achieve above without mixin classes - but I am open to other ideas.
If we do not find another solution (other than mixins), those event loop mixin classes should reside in txaio not Autobahn, since txaio is supposed to help exactly in the general situation where one wants to write code once that runs on both on Twisted and asyncio.
In other words, the USP of txaio is: "A helper library for writing code that runs on both Twisted and asyncio." With this USP, I guess it would make sense to gather feedback early on with devs on tulip/twisted mailing lists.

I think it should be possible to let the entry point into Autobahn (ApplicationRunner if I recall correctly) to choose the underlying framework based on the passed reactor/eventloop (if its a reacton -> twisted, if its an eventloop -> asyncio). Classes which then need framework-independent functionality could be implemented by using dependency injection (which the entry point sets up). As Autobahn already is heavily build around IoC, dependency injection would fit pretty well into it IMHO.
We could realize dependency injection by utilizing constructors or by directly modifying the object instance (session.futureHelper = foo) or by providing a dedicated interface (session.inject("futureHelper", foo). Probably there also are already a bunch of python libraries available for dependency injection.

The only non-mixin solution I can think of would be this:
autobahn.wamp.twisted or autobahn.wamp.asyncio are the only spots where anything is imported from txaio. The respective ApplicationSession classes do something like:
    from txaio import tx as _txaio
    class ApplicationSession(...):
         txaio = _txaio

...and then protocol.py code looks like self.txaio.create_future() etc. In the end, it might cover more use cases to simply put mixins in txaio (so you can do txaio.create_future() or do a mixin-style thing like Autobahn). Then the code would look basically like it does now:
    from txaio.tx import LoopMixin
    class ApplicationSession(LoopMixin, ...):

I have a "working" PoC in my fork of txaio. I still need to add some docs and clean up the asyncio testing/waiting and probably some other things. gather_futures is kind of a horror-show, and I took a stab at supporting an inlineCallbacks/coroutine equivalent decorator (txaio.future_generator) but I'm not sure I got that right -- plus it needs PY3-only code (yield from). On the upside, the tests I do have pass on py2.7 + py3.3 on both asyncio and twisted...
There's one change from what I copied out of Autobahn: we weren't supporting callback return-value mutations (like Twisted does) in asyncio. I don't believe Autobahn depended on this behavior, but I changed the asyncio implementation to support this but it uses one asyncio internal, setting future._result if a callback returns a new value. Twisted also supports jumping to the callback chain from the errback chain (and vice-versa) and that isn't at all supported. I'm not sure of a really "good" solution here: either you get inconsistent behavior depending on the backend you select, or I keep code to make either asyncio or Twisted conform to one way or the other. Probably this is one for "feedback from twisted/tulip mailing lists" :)

Here's how the above looks, as an idea.
All the tests pass (but there are still a few uncovered lines).
https://github.com/tavendo/AutobahnPython/compare/master...meejah:use-txaio?expand=1

https://github.com/tavendo/AutobahnPython/compare/master...meejah:use-txaio?expand=1
is now based off the simplified txaio, just using import txaio. There are at least some tests of creating and cancelling timed-calls (but certainly not all).


[suggestion]Wish the new feature "RAML support"

Restangular is simple and formally with RESTful.
I thought is there any method to generate .raml file or generate a Restangular's .js file from .raml.
After that:

Front-End: We don't need to code .js for formally RESTful API, instead to run a generator(maybe a gulp or grunt plugin)
Back-End: We could also generate Back-End Service via RAML's multiple generator(php, golang, JAX-RS, etc.)

Above all, Restangular will be more friendly with lazy programmer like me. :)

Admiring RESTful, we could have more time to focus on Business Logic Layer rather than Data Model.

That's funny when I notice that RESTangular don't need to support any Description Language. Because It's perfect that we don't need ugly Service, such as $http/$resource.


Menu builder get error in production

When i try to do anything in menu builder(add ,update,delete), it all get me this error
In localhost everything working fine
This happen only on Server

I use laravel 7 & voyager 1.4

I use laravel 7 & voyager 1.4


FPS Drop when many enemies active

sometimes dude. Relax. I'll take care

days passed and never happenned again. Not gonna complain


[BUG] Quick Capture not working when fired through a command

Describe the bug
My "Capture" action is working fine when I fire it from the commander, i.e pressing Ctrl+P, going to QuickAdd, then navigating to the action and running it.
However, my Capture action is nested within a Multi and this multi has a Command (hotkey) toggled on. If I open the multi through that hotkey (instead of through the regular commander and "Open Quickadd"), the capture will fail with this error message :

To Reproduce
Steps to reproduce the behavior:

Create capture action
Add it to a Multi
Add a command (hotkey) to the multi
Try to trigger the capture by using the hotkey and navigating to it

Desktop (please complete the following information):

OS: Windows

After more investigating, it seems that triggering quick capture from a templater script causes the issue so it's not related to quick add ! I'll raise that on templater side :)


when will the code be released

Hi, I am very interested in your work and it is a awsome work. Could you released your code?

Thank you for your continued attention. We have been busy recently but are actively organizing the code and plan to release the source code soon.


Add PeriodicJobBuilder

PeriodicJobBuilder essentially creates cron jobs in Jenkins.

cron syntax: H/15 * * * * runs every 15 minutes
optional repo to clone if you need to run a script from a repo

While I appreciate the work here, I really struggle with the value this adds. Basically, this simplifies adding a cron schedule, but I don't think merits a whole new builder.
here's what I believe about Builders, in principle:

Prefer sticking with job-dsl vs new abstractions; the bar should be pretty high for adding new builders
we should not provide simple abstractions over top of already simple abstractions, and job-dsl is often quite simple.

The question I have is: does it really add value to add a simple wrapper around adding a cron schedule? I'd much rather that people using job-dsl know how to do that without relying on a builder abstraction.
I know this is fuzzy and the guidelines on when should we add a builder vs. not aren't clear, and it's definitely up for debate.
Here are a few things to consider to guide decisions?

Does the builder abstract a gnarly configure block (such as sitemonitor builder)? If so... probably worth it

Does the builder create a custom "job" type, such as the BuildFlowBuilder? If so... probably worth it

Does the builder represent a job that is used so consistently within the org that further modification of that job is not likely (such as the checkmarx builder)? If so, probably worth it.

Does the builder simply add a wrapper around non-custom / non-configure-block job-dsl bits? If so, probably not worth it

Does the builder expose something that saves a line or two of code, but makes it annoying to provide further customization (often the case with scm{} blocks)? If so, probably not worth it

Bottom line: I'd bias toward using job-dsl as much as possible, even if it means more code, over additional abstractions.
When to break this rule? I'd say on a per-project basis, when you look at existing jobs and realize that many of them are highly consistent except for 1 or 2 things that differ, such as the Qu "task" jobs. In that case, it's appropriate to create a custom builder inside that project and use that

I understand your concern about adding a bunch of negligibly incremental builders to the builder stack, and I'm more than happy to do all the logic in my project's groovy code.  I was just trying to follow the workflow that I had observed with our existing stack (i.e. the SiteMonitorBuilder).
Having said that, we have a lot of jobs that run on a schedule, whether it's H/15 * * * * or @hourly or @daily.  At a quick glance it appears that at least 8 Qu jobs have a schedule.  Does this Builder save a ton of time over using BaseJobBuilder with a cron blerb? Not really, but it is something we'd have to do over and over again for many if not all of our projects.
If we expect a high bar for entry as a JobBuilder, maybe we should detail our expectations (basically, what you said above) somewhere in the readme or the documentation, I can't find anything on this topic.

@m3brown These are all excellent comments
I heartily agree about documenting this guidance. I'll add a Jira issue for it.
Re: lots of qu jobs, I think this is likely where it gets into that grayer area, which we can document guidance on to the best of our ability. With Qu, not only did those jobs have cron schedules, but they also had damn-near-identical shell blocks, log-parser-publisher blocks, and mask-password-parameter blocks. Those several things combined led me to create a QuTaskBuilder for use with those task-ish jobs (https://omg-private-url/marcesher/qu-jenkins-automation/blob/master/src/main/groovy/QuTaskBuilder.groovy)

@marcesher @m3brown I am with Marc. The rule of a thumb for a builder- it should produce a viable job. I doubt we have jobs that have a schedule, but do nothing else. We can add it as an optional parameter.


Compiler gives ambiguous type error for valid XML unions

Description:
$title
Steps to reproduce:
xml<xml:Text>|xml<xml:Comment>|xml x13 = xml text1;

Can't seem to reproduce this on 2201.0.1.

FIxed in Ballerina 2201.3.0. Therefore closing the issue.


[Candidate 1v1 Echo ZH v1] Oil Refineries and Artillery Platforms have custom rotations that make their flag less visible

Issue Description
Oil Refineries and Artillery Platforms have custom rotations that make their flag less visible.
Expected behavior
Oil Refineries and Artillery Platforms preferably have default rotation or a rotation that makes their flag highly visible.
Screenshots

Oils and artillery are on full purpose turned. For artillery its important where the gun is facing in the first place.
I change for the oils however.

Uploading [RANK] Echo ZH v1.zip…

[RANK] Echo ZH v1.zip

[RANK] Echo ZH v1.zip

Not found.


Lower-case Aurora table names cause type mismatch.

Describe the bug
If you create an API with an aurora datasource in the Amplify CLI using a table having all lower-case letters in its name, resolvers are created with casing that doesn't match the GraphQL schema.
To Reproduce
Steps to reproduce the behavior:

Create an aurora instance, using table names with all lower-case letters.
Generate and push an API, with that aurora instance as its datasource (all added in Amplify CLI)
Try to call a mutator, and notice that it doesn't work since the casing is mismatched.

Expected behavior
I would expect that a new API with an aurora datasource would CRUD out of the box.
Desktop (please complete the following information):

OS: macOS Mojave, using zsh

Additional context
AWS support case<PHONE_NUMBER>

I was able to reproduce this, it is a bug in the RDS schema transformer. We will work on a fix for it.


Fixed broken links and renamed ES to ALZ

Brought to my attention by @stalejohnsen that these links were broken and at some point the page was renamed to include alertsdetails.md
@jfaurskov can you take a look at the links i have fixed (i'm aware the links are working just wondered if we need to update this section given there are more initiatives we have introduced

@stalejohnsen all merged, thanks again


Swagger connector api updates

Fixes #943 - 'Add State field to Semantic Action in Schema'
Description
This pull request contains updates for the Connector API, based on changes in the swagger spec since Nov 2018:
https://github.com/microsoft/botframework-sdk/blob/master/specs/botframework-protocol/botframework-channel.json
Specific Changes
'localTimestamp' - update description
'localTimezone - update description
botbuilder-js\libraries\botframework-schema\src\index.ts
botbuilder-js\libraries\botframework-schema\src\activityInterfaces.ts
SemanticActions / SemanticActionStates - add 'state' field:
botbuilder-js\libraries\botframework-schema\src\index.ts
botbuilder-js\libraries\botframework-connector\src\connectorApi\models\mappers.ts
ConversationParameters / add 'tenantId' field
botbuilder-js\libraries\botframework-schema\src\index.ts (ALREADY EXISTS - NO CHANGE)
botbuilder-js\libraries\botframework-connector\src\connectorApi\models\mappers.ts
ConversationAccount / add 'tenantId' field
botbuilder-js\libraries\botframework-schema\src\index.ts (ALREADY EXISTS - NO CHANGE)
botbuilder-js\libraries\botframework-connector\src\connectorApi\models\mappers.ts
TokenResponse / add 'channelId' field
botbuilder-js\libraries\botframework-connector\src\tokenApi\models\index.ts (ALREADY EXISTS - NO CHANGE)
botbuilder-js\libraries\botframework-connector\src\tokenApi\models\mappers.ts (ALREADY EXISTS - NO CHANGE)
botbuilder-js\libraries\botframework-schema\src\index.ts
botbuilder-js\libraries\botframework-connector\src\connectorApi\models\mappers.ts
AttachmentView viewId / size descriptions
botbuilder-js\libraries\botframework-schema\src\index.ts
Activity / add 'callerId' field
botbuilder-js\libraries\botframework-schema\src\index.ts
botbuilder-js\libraries\botframework-connector\src\connectorApi\models\mappers.ts
Testing

Manual testing with local bots
botbuilder-js\libraries\botbuilder\tests\botFrameworkAdapter.test.js
Additional tests could be added to 'connector.test.js', once that test suite is refactored and back i a working state (in progress - see https://github.com/microsoft/botbuilder-js/pull/908).

Merging in latest from master


Implement a new parallel iterator scheme that supports flat-map

This commit history is kind of rambly but I don't have time to clean it up. The big bit of work here is support for flat-map, which required a lot of redesign. See the par_iter/README.md file for an overview.
I think there is still tweaking to be done on these traits. For example, I'd like to reduce the unsafety, and maybe add some lifetimes to allow passing references for the shared state in the producer. But this will do for now.
cc @cuviper @bjz

Holy rewrite, Batman!  The description in the readme is helpful, and though the concepts are more challenging now, it sounds pretty reasonable.
I don't have time to dig through this in detail right now, but I did notice a few nits, commented inline.
And FWIW, a program I have using range got about 10% faster, so that's nice. :)

@cuviper

And FWIW, a program I have using range got about 10% faster, so that's nice. :)

Hey, score! :)
I had some thoughts on the subway ride home about how to simplify things a bit (remove some lifetimes etc). I'll try to experiment it with it next chance I get.

OK, so, I thought that I could remove the Shared assoc type from Consumer and instead just thread the shared state with an & reference embedded in the Consumer itself. This would have avoided the need for the 'consume, I think, and also just simplified the fn signatures and so forth. But this idea, sadly, does not work because of the reduce method, which combines two items after a split -- at that point, you no longer have a Consumer to use, so you need to have the shared state separated out.

OK, I'm going to merge this. I have some more edits I'll maybe open in another PR, but this is a good point to get locked down. :)

:+1:


GraphQL-Ruby 1.11+ Broadcasting feature support.

Fixes #13
Documentation: https://graphql-ruby.org/subscriptions/broadcast
Current implementation mimics grapqhl-ruby actioncable implementation from https://github.com/rmosolgo/graphql-ruby/pull/2959 a lot: in actioncable nested hashes are being used to lookup events by topic first and fingerprint then. So I implemented a similar two-step lookup of subscriptions by topic and fingerprint. AnyCable clients are still subscribed to their own subscriptions and we re-evaluate query once but still ~broadcast~ transmit updates individually.
However, it seems possible to avoid two-step search of subscriptions and store them using event fingerprint as a subscription identifier, without storing exactly duplicated queries in redis (see code comments). But I'm not sure that it is safe to do.

it seems possible to avoid two-step search of subscriptions and store them using event fingerprint as a subscription identifier, without storing exactly duplicated queries in redis (see code comments). But I'm not sure that it is safe to do.

That's exactly what I was thinking about. Should work. Will take a closer look on Monday.

Hello,
We're waiting for this feature to be released too :) Is this branch production-ready to use or it's still better to wait for final release?

Hello,
We're waiting for this feature to be released too :) Is this branch production-ready to use or it's still better to wait for final release?

No, it is still untested. I hope that I will be able to get back to it some day this month.

No, it is still untested. I hope that I will be able to get back to it some day this month.

Polished things a bit, added cleanup of new keys on unsubscribe, ensured backward-compatibility with old structure for seamless migration (by default disabled, enable it with setting if you're upgrading). Briefly tested it on one of real applications locally. Seems to work. Will add some docs on the next week and it is probably good to go.

I didn't further develop the idea of direct usage of event fingerprints for streaming. It is totally possible, but just feels too counter-intuitive without these subscription_ids.

Finally I also got rid from unicast of results to every client and replaced it with fingerprint-based multicast. So now we're not only re-execute GraphQL query once, but also send results once (and for all clients).
I can't quickly test it on some live application right now, so would be very grateful if someone will give it a try!

April's fool day is a good day to release new version, I think :wink:


TST: Potentially Skip 8bit bnb regression test if compute capability is too low

The 8bit bnb LoRA regression test results are dependent on the underlying compute capability. The logits are slightly different depending on the version (up to 0.5 abs diff). Therefore, we now check the compute capability for this test and skip it if it's too low. This check may require updating if the hardware of the CI worker is updated.
Note that I have already invalidated the old regression artifacts and created a new one.

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint. The docs are available until 30 days after the last update.


ARROW-12138: [Go][IPC] Update flatbuffers definitions

Updating the generated flatbuffer code so that newer features like compression in IPC can get implemented. Doing the updating of the flatbuffer generated code first as a separate change.
@sbinet @emkornfield

All that was done for this change was to run go run ./gen-flatbuffers.go followed by updating the couple of files in the ipc module which had to switch direct references to byte or int16 to the exported types from the flatbuffers files. So the only files in this change that contain anything that wasn't generated by flatc are ipc/file_writer.go, ipc/message.go and ipc/metadata.go. Everything else just contains the generated flatbuffer code.

@sbinet @emkornfield @wesm once this is merged, i have a PR ready for adding compression handling to the go IPC implementation, I'm just waiting for this to get merged before filing it for ease of review


Hot Reload stopped working with version 1.4.0

Describe the bug
I'm using nested beamers the following way.
There is a root BeamerDelegate that looks like this:
BeamerDelegate(
 ...
  locationBuilder: RoutesLocationBuilder(
    routes: {
       '/baseA/*': (context, state, data) => BaseAMainPage(),
       '/baseB/*' : (context, state, data) => BaseBMainPage(),
     }
  )
 ...
)

Both BaseAMainPage and BaseBMainPage use another Beamer as shown in your examples.
This also works fine, as long as you don't hot reload. Hot-reload does also work for the level-1 pages (/baseA/page1, /baseA/page2). But for pages with higher levels (/baseA/page1/subpage1, /baseA/page1/subpage2) the root BeamerDelegate emits a NotFound page.
This issue only appeared when updating the version from 1.3.0 to 1.4.0+1. (I downgraded, and then it's working again).

Hey @stefangaller :wave:
Thanks for creating an issue.
Sounds like an interesting issue :thinking:
I will look into this as soon as possible and update you here with what I've found.

@slovnicki  I created a small repo containing an app the shows the problem: https://github.com/stefangaller/beamer_1.4.0_hot-reload.
Hot-reload on the ShopPage works, but it will lead to a NotFound on the ShopDetailPage.
Hope that helps.

same happens if you hit back button on a browser, the shared code by @stefangaller works fine with 1.3.0 but breaks in 1.4.0

I am having the same issue but it is also occurring on v1.3.0, whenever I save a file a reload happens and "Not found" page is shown. My app has a bottom nav bar with each section being a nested beamer.

I am having the same issue but it is also occurring on v1.3.0, whenever I save a file a reload happens and "Not found" page is shown. My app has a bottom nav bar with each section being a nested beamer.

probably here is your fix https://github.com/slovnicki/beamer/issues/193

I am actually defining it already as final in external file, but thanks ;) will keep playing around and see what I can do
class GoalaRouterDelegate {
  static final mainRouterDelegate = BeamerDelegate(
    initialPath: MainNavigatorRoutes.splash,
    locationBuilder: BeamerLocationBuilder(
      beamLocations: [MainLocation()],
    ),
  );

  static final exploreRouterDelegate = BeamerDelegate(
    initialPath: ExploreNavigatorRoutes.explore,
    locationBuilder: BeamerLocationBuilder(
      beamLocations: [ExploreLocation()],
    ),
  );

  static final profileRouterDelegate = BeamerDelegate(
    initialPath: ProfileNavigatorRoutes.profile,
    locationBuilder: BeamerLocationBuilder(
      beamLocations: [ProfileLocation()],
    ),
  );
}

@stefangaller
I now realize this was fixed in v1.4.1. The specific PR was #502
(btw, it was not related to hot-reload, but "deep load" in general - that's why it was also happening with browser buttons)
@czaku you can create a new issue if you're still facing some reload problems


Admin should be able to edit settings of all repositories

Global administrators should be able to modify repository and user settings directly through the administration interface i.e. make a public repository private, transfer ownership, edit ssh keys etc.

:+1:
By the looks of it, admins can't delete repositories of other users.

I think an Administrator should be able to create, read, update and delete everything including creating repositories for users, renaming repositories, editing description, organizations, teams and memberships.

@rojaro thanks for the details.

+1

+1

+1

You can now test this on develop branch.

@Unknwon have tested it and it works great.

@stonerl thanks your confirmation!


random edit

Description of changes

Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

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

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

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

[ ] Fits CONTRIBUTING.md.

hans?

@Lassulus hello

xxx

bar

@nixpkgs-merge-bot merge
<!-- hello>

@nixpkgs-merge-bot merge

@nixpkgs-merge-bot merge

@nix-merge-bot merge

@nixpkgs-merge-bot merge

@nixpkgs-merge-bot merge


Aborted

I haven't been able to reproduce this. Is this something you can easily reproduce?

@SeanTAllen
has been in the press f5 to refresh the browser will appear

what platform are you running on? if on linux, which distro?
what version of pony?
what version of llvm?

linuxmint18
0.2.1-946-ge992d20
llvm-3.6

Remove logger no longer crashes

Where you using VirtualBox?
Can you try again using the latest ponyc from masteR?

linuxmint18
siege -c 100 -r 100 http://<IP_ADDRESS>:50000/
localhost - - [08/Jul/2016:00:52:10 +0000] "GET / HTTP/1.1" 200 15 "" "Mozilla/5.0 (pc-x86_64-linux-gnu) Siege/3.0.8" localhost - - [08/Jul/2016:00:52:10 +0000] "GET / HTTP/1.1" 200 15 "" "Mozilla/5.0 (pc-x86_64-linux-gnu) Siege/3.0.8" localhost - - [08/Jul/2016:00:52:10 +0000] "GET / HTTP/1.1" 200 15 "" "Mozilla/5.0 (pc-x86_64-linux-gnu) Siege/3.0.8" localhost - - [08/Jul/2016:00:52:10 +0000] "GET / HTTP/1.1" 200 15 "" "Mozilla/5.0 (pc-x86_64-linux-gnu) Siege/3.0.8" localhost - - [08/Jul/2016:00:52:10 +0000] "GET / HTTP/1.1" 200 15 "" "Mozilla/5.0 (pc-x86_64-linux-gnu) Siege/3.0.8" localhost - - [08/Jul/2016:00:52:10 +0000] "GET / HTTP/1.1" 200 15 "" "Mozilla/5.0 (pc-x86_64-linux-gnu) Siege/3.0.8" localhost - - [08/Jul/2016:00:52:10 +0000] "GET / HTTP/1.1" 200 15 "" "Mozilla/5.0 (pc-x86_64-linux-gnu) Siege/3.0.8" localhost - - [08/Jul/2016:00:52:10 +0000] "GET / HTTP/1.1" 200 15 "" "Mozilla/5.0 (pc-x86_64-linux-gnu) Siege/3.0.8" localhost - - [08/Jul/2016:00:52:10 +0000] "GET / HTTP/1.1" 200 15 "" "Mozilla/5.0 (pc-x86_64-linux-gnu) Siege/3.0.8" localhost - - [08/Jul/2016:00:52:10 +0000] "GET / HTTP/1.1" 200 15 "" "Mozilla/5.0 (pc-x86_64-linux-gnu) Siege/3.0.8" localhost - - [08/Jul/2016:00:52:10 +0000] "GET / HTTP/1.1" 200 15 "" "Mozilla/5.0 (pc-x86_64-linux-gnu) Siege/3.0.8" localhost - - [08/Jul/2016:00:52:10 +0000] "GET / HTTP/1.1" 200 15 "" "Mozilla/5.0 (pc-x86_64-linux-gnu) Siege/3.0.8" localhost - - [08/Jul/2016:00:52:10 +0000] "GET / HTTP/1.1" 200 15 "" "Mozilla/5.0 (pc-x86_64-linux-gnu) Siege/3.0.8" Segmentation fault

I can confirm the Segmentation fault result on Linux Mint 18 with the latest version of ponyc (1e96984) and llvm 3.8.0

Running lldb gives this result:
Process 8925 stopped
* thread #6: tid = 8931, 0x0000000000428f43 httpserver`pony_traceunknown + 3, name = 'httpserver', stop reason = signal SIGSEGV: invalid address (fault address: 0x0)
    frame #0: 0x0000000000428f43 httpserver`pony_traceunknown + 3
httpserver`pony_traceunknown:
->  0x428f43 <+3>:  cmpq   $0x0, 0x40(%rax)
    0x428f48 <+8>:  je     0x428f50                  ; <+16>
    0x428f4a <+10>: jmpq   *0x18(%rdi)
    0x428f4d <+13>: nopl   (%rax)

out of curiousity. @Theodus could you apply
https://github.com/Sendence/ponyc/commit/4ead6e06bd3f1e0fa24cb2df29ebb984307a8169
and run this again and see if the bug still exists. I assume it does, but... I'm wondering if it might fix. Mostly shot in the dark.

@SeanTAllen, it made no difference. Worth a shot though.

I get the same behavior, and using DiscardLog or removing logging altogether from the HTTP package makes no difference.
I'm on LinuxMint 17.3 with LLVM 3.6.
I did some digging, and was able to eliminate the seg fault by screwing around with the code in the received() method in _request_builder.pony. My edits wouldn't be correct code, but the nature of what does and does not eliminate the seg fault was interesting.
It's a little long to describe, so I put it into a gist. Hope it helps.

./httpserver
Listening on <IP_ADDRESS>:50000
fume.fritz.box - - [08/Sep/2016:19:16:15 +0000] "GET /xxx HTTP/1.1" 200 18 "" "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/53.0.2785.92 Safari/537.36"
fume.fritz.box - - [08/Sep/2016:19:16:16 +0000] "GET /favicon.ico HTTP/1.1" 200 26 "" "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/53.0.2785.92 Safari/537.36"
fume.fritz.box - - [08/Sep/2016:19:16:22 +0000] "GET /xxx HTTP/1.1" 200 18 "" "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/53.0.2785.92 Safari/537.36"
fish: './httpserver' terminated by signal SIGSEGV (Adressbereichsfehler)
It happens consistently on the 3. get, on a 32 bit Linux machine
Distributor ID:	ManjaroLinux
Release:	16.08
Codename:	Ellada
ponyc --version
0.3.0 [release]
llvm-config --version
3.8.1

Looking at this, I'm pretty sure this is the same bug as #1118. I can't imagine we have two bugs that result in crashes in trackunknown. @sylvanc would you agree?

@Theodus can you verify you still get this with the latest master and using llvm 3.8.1?

@SeanTAllen I get the same segfault.
0.5.0-8011ddf [release] (llvm 3.8.1) (cc (Ubuntu 5.4.0-6ubuntu1~16.04.2) 5.4.0 20160609)

Thanks. Just wanted to verify @Theodus.

We are assuming this is the same issue as #1118 and once that is fixed, will test this again to verify.

I have not been able to reproduce this with recent versions of Pony.

interesting

Could it have been fixed by #1321 or #1405?

@jemc That's very unlikely for #1321 and definitely not #1405.

Commit f9591b2ed4ee95b5db181574c030da22531a13ad seems to be the first commit that doesn't segfault.

@Perelandric That's interesting. I guess there is a bug somewhere in the code generation for GC tracing. I'll look into it.

I'm closing this because I think its fixed based on the above comments.


Docs on how to use Camera2D

Adds a description of the most typical use case (for new users).

CC @godotengine/documentation

Let's leave this to the docs experts for sometime. I know how to use Camera2D (and I didn't learn it from the current docs).

Not sure what you meant with your comment but you seem upset. Anyone's welcome to contribute, you just have to edit your PR to get it to merge because:

If everyone writes in a different style (that was the case with Godot 2.x's reference) it makes the ref harder to browse and read
Empty lines produce empty paragraphs, thus big gaps in the editor
This is the code reference. It'd be great to have a good camera tutorial, or a page dedicated to the camera, but this goes in the manual

Everyone goes through review, me included, and there are often typos or things to improve before you get merged.


Product Managers' Merged PR Leaderboard in October 2024

Thank you to all those who have successfully merged PRs in Nov. The following list is sorted in an alphabetical order.

[ ] Adityayxt

#5703
#5702

[ ] jzhupup

#5700
#5718
#5800
#5815
#5849
#5859

[ ] justedennnnn

#5698
#5697
#5640
#5726
#5860
#5861

[ ] lemontrees123

#5705
#5690
#5838
#5840
#5842

[ ] samzong

#5704
#5767
#5777
#5793
#5794
#5805
#5820
#5823
#5824
#5825
#5826
#5843

[ ] Ye-Ting
[ ] wlp1153468871

#5699
#5765
#5787

[ ] zhiyingfang2022

[ ] #5782

[ ] Zhuzhenghao

https://github.com/d-run/drun-docs/pull/139

Notes:

Check all merged PRs in September
Check more contribution details from OSS Insight website
Check the real name from a GitHub ID to know who is who

Thanks you all.


Check whether the task finishes before deferring the task for BigQueryGetDataOperatorAsync

Like the SnowflakeOperatorAsync, we try to verify if the submitted job has already completed before deferring it to prevent unnecessary deferring. This way, we can skip deferring the task if it has already been finished.


Image references always default to root directory, do not work in subdirectories

This popped up in my own MD files, but I also noticed it in the docs folder as well.
https://github.com/arnaudsm/raito/blob/f549621d5159ad52bdfef7060df1f17c5e426a23/docs/README.md?plain=1#L128-L130
The web request to the server is wrong though:
GET http://<ip-addr>/logo.svg 404 (Not Found)

This does work though:

Output ⬇

![logo](docs/logo.svg)

After researching further, this only happened with browserRouter: false.


django 1.8 compatibility

Hi guys,
I tried to use the plugin with django 1.8. I get the following exception. When using django 1.7.7 everything works fine:
AttributeError: 'RegexURLResolver' object has no attribute '_resolve_special'
Exception
Stacktrace (most recent call last):
File "maintenancemode/middleware.py", line 44, in process_request
callback, param_dict = resolver._resolve_special('503')
Best,
Ron

_resolve_special has been removed in django1.8
You can change line 44 in middleware.py with this code:
callback, param_dict = resolver.resolve_error_handler('503')

Without guarantee. Works for me. Django==1.8.1

Thanks! But will someone update the package or do I need to fix it manually?

I can confirm it's the right fix.

Hey, bugfix release will be ready either tomorrow or after tomorrow

Cool!


Fix ant speed and 0th challenge completions in c13

Please check this before my #119, it includes my quickfix, making mine unnecessary if approved.


Logo design proposal

Hi, my name is Valeria. I'm a graphic designer and I'd like to collaborate on your open source project and propose free logo/icon design for your app. If it's something you're interested in, please, let me know!
Best,
Valeria

Thank you Valeria for reaching out. Right now we are focused on bringing project up from the ground. We will discuss with the team about your proposal and let you know as soon as we can.

Thank you Valeria for reaching out. Right now we are focused on getting project off the ground. We will discuss with the team about your proposal and let you know as soon as we can.

Ok, I'm sure that your project will do great! Let me know about your decision.


[python3-edl] Add new RPM spec

for the Emergency Download client for managing Qualcomm Arm SoCs.

This is a required tool for setting up Linux on Qualcomm SoCs.


Add waggledance.ai to #Agents

waggledance.ai is intended to be a general goal solver. Goals can include things like research, workflow automation, synthesis of live data, etc.-- things that ChatGPT can do with plugins, considerable chatting and effort.
The general concept is that it takes your data, allows you to configure tools (aka skills), and then runs a plan-validate-solve system of agents.There are some example goals in the UI. Agents are throw-away, i.e., there isn't a "code agent" or "Einstein agent", however there are three distinct agent types. Plan, execute, and critique.
Most of the effort so far has been spent trying to optimize the time-to-first-byte and think about different ways agents may be interacted with. I also have been optimizing parallel execution of tasks to reduce the total amount of time to finish goals.

Thanks @jondwillis for the add. Please use the github link instead of the website.

@sbusso done


Allow user customisation before and after Docker daemon startup

Signed-off-by: Sven Dowideit<EMAIL_ADDRESS>replacement for #759

@tianon

LGTM


Mikado backend

How easy would it be to integrate mikado js as backend. It's really fast, has no synthetic events, and uses plain html5 templates. It's only limitation is that it expects all text to be wrapped in a separate element (no children of element and text)

It can definitely be done, however I'm unlikely to find time to take it up myself right now. I'll leave this open for a while in case someone else wants to take a look.

Closing this in favor of the umbrella issue.


Core extraction fidelity setting

Alloy has a "fast, medium, slow" menu for core extraction. This is distinct from core granularity.
I believe this controls which strategy is used (HybridStrategy, RCEStrategy, etc.)
It's unclear which we're using right now -- probably the fast version.

This was fixed by adding the core_minimization option, allowing RCE, Hybrid, etc.


Proper way to remove unused images in swarm?

Since docker system prune is 'unsafe' to use in swam context: an unused image can be used by a service in another swarm node, and thus needed if swarm decides to start the service on that node
What's a proper way to eliminate old unused docker images in Swarm?

docker image prune -a

@jony4 that's not safe in a multi-node swarm cluster, because it prune local images, but local images might be unused but necessary for the swarm orchestrator

maybe do it one by one, simple 🤣

@jony4 I don't think you understand the problem, swarm images are deployed on every swarm node, but they're not necessarly used on each node, pruning the image on node where it's not currently used will prevent a swarm service to run on that node


Provide a way of getting schema information given a node

@WilliamJamieson With the recent developments can this be closed now?


Actions, Services not bridging on Turtlebot4 w/ Humble

I'm working in a slightly odd setup with a Turtlebot 4 and the domain_bridge node running inside a docker container.  I can see the topics from my Create3 platform (running on domain ID 3) being bridged into my Raspberry Pi (running on domain ID 0).  However, the robot's actions & services are not visible when running ros2 service list or ros2 action list.
If I open a shell in my container I can see the actions & services on domain 3 inside the container. But they don't appear to be bridged into domain 0 properly.

If I add the hidden _action topics to the topics configuration I do see the actions with ros2 action list, but sending a goal hangs on waiting for the action server to become available.  Services remain unbridged in this setup.
Am I doing something wrong with the configuration? Or do I need to build the package from source rather than installing the debian package?  (If that's the case, will the recent changes be bloomed sometime soon?)
Docker configuration
Dockerfile
FROM ros:humble

# install ros package
RUN apt-get update && apt-get install -y \
      ros-${ROS_DISTRO}-irobot-create-msgs \
      ros-${ROS_DISTRO}-domain-bridge && \
    rm -rf /var/lib/apt/lists/*

docker-compose.yml
services:
  create3-bridge:
    image: create3-bridge:latest
    restart: always
    env_file:
      - config/create3.env
    command: ros2 run domain_bridge domain_bridge /opt/config/create3_bridge.yaml
    profiles:
      - create3
    volumes:
      - ./config/:/opt/config
    network_mode: host

config/create3.env
ROS_DOMAIN_ID=3
FASTRTPS_DEFAULT_PROFILES_FILE=/opt/config/fastrtps-profile.xml

config/fastrtps-profile.xml
<?xml version="1.0" encoding="UTF-8" ?>
<profiles xmlns="http://www.eprosima.com/XMLSchemas/fastRTPS_Profiles" >
    <transport_descriptors>
        <transport_descriptor>
            <transport_id>CustomUdpTransport</transport_id>
            <type>UDPv4</type>
        </transport_descriptor>
    </transport_descriptors>

    <participant profile_name="participant_profile" is_default_profile="true">
        <rtps>
            <userTransports>
                <transport_id>CustomUdpTransport</transport_id>
            </userTransports>

            <useBuiltinTransports>false</useBuiltinTransports>
        </rtps>
    </participant>
</profiles>

(This was done to work around the shared memory issues described here: https://answers.ros.org/question/370595/ros2-foxy-nodes-cant-communicate-through-docker-container-border/)

Hi @civerachb-cpr, just wondering if you found any solutions for your problem? I also can't seem to get actions or services to come up but topics work.
In addition, I see that your "true" statements are different than the ones in the example configuration that use "True". Maybe that causes a difference?

I have unfortunately not found the root cause of these problems yet. Completely wiping & rebuilding the containers seems to have fixed it for now, but I'm not sure if it'll spontaneously come back again.

Interesting; I am not using a docker so I am unsure how I would go about fixing the problem as it is present on 2 of my computers. Are there any specific steps you took to make the services appear? For example, I know for topics you have to start publishing first before the new domain id can see the topic as the QOS has to be inherited if not specified.
Sorry to ask so many questions from you, I am just a bit unsure how to proceed and am hoping I just missed something simple!

As of now, the ros bridge doesn't support the bridging of services or actions via the config. you can build a custom executable for services, however, actions are not supported at all.
I opened up a PR (#82) that adds support for services and actions via config using code generation if you want to have a look


Using local user password?

Hi
What is the reason that the simple authentication method doesn't use local Linux user password? Is it because of plain password transmission or something? I want offer the same way that users login when rstudio is installed directly on to host machine: they can login with local linux user and password.
Logging in with AD user may be more complicated, but we will come to that later.

Sorry, I let this project languish. I'd be happy to review any code you may have to get this to work.


Meteor 1.6.1 GenericAdPlugin: Invalid action passed: createBannerView

Hey,
so im using this plugin in meteor 1.6.1. On Client startup, Admob is initialized and events are registered. By clicking a button, i'm calling: window.plugins.AdMob.createBannerView();
This Results in the following console output:
W/GenericAdPlugin: Invalid action passed: createBannerView
Same happens for functions like showAd() etc. Same happens by calling the commands over the console.
Any ideas? Thanks :)

Sounds like meteor is not initializing the java side functions. We are not meteor experts, don't know about it, sorry.


Rule: no-unused-placeholders

Reports when a context.report call contains a data property that does not have a corresponding placeholder in the report message.
Example of invalid code:
context.report({
  node,
  message: "Do not use {{foo}}.",
  data: {
    foo: 1,
    bar: 2
  }
});

is this proper to add to rule no-missing-placeholders? they are so similar!

I don't have a strong opinion either way. I think it would be fine to have them as two separate rules because they are checking two separate things (one of them checks missing placeholders, and one of them checks missing data) but I'm also fine with combining them.


Rewrite of GitLab parsers

DD supports multiple GitLab formats (API fuzzing, container scan, DAST, Dep. Scan, SAST, Secret detection) but there is documentation only for SAST and Dep. scan
All GitLab scanners use the same common format (which is partially but nicely described here and full up-to-date examples are available here) so it should be merged into the one. If there will be some change in format, it is easier to maintain one common code than multiple of them. Plus it will automatically support newly created scan categories (for example, "Cluster Image Scanning", "IaC Scanning" and "Coverage-guided fuzz testing" are missing right now)
(real bug) "GitLab DAST Report" uses IDs as names of findings even there is a meaningful title in the report (field name is "message").

Can you close this @mtesauro because of: https://github.com/DefectDojo/django-DefectDojo/discussions/9690


No License?

We don't see any open source software licensure authorizing the use of DimVis in the repo: https://github.com/parisa-salmanian/DimVis
Can you update this? What license are you authorizing use of the code under?

Hi,
Thank you for notifying us. We have added an MIT License.


add Gopkg.toml; resolves #90

Signed-off-by: Mario Kozjak<EMAIL_ADDRESS>

@mkozjak didn't want you think I forgot about this. Having these files causes issues when generating new Buffalo apps, so those need to be resolved before this can be merge.

@markbates No problem. Looking forward to get ourselves vendored. :)

What's up with this one?

Still haven't resolved the issues around this. Haven't forgotten about it, but haven't fixed it yet either. :)

Fixed here https://github.com/markbates/pop/commit/b1f0237d112c6281debc0419205510979894ebf9


Implement taint analysis in datalog

I think we can call this done. The taint analysis has been being performed in Datalog for a while.


Team member can access a survey they are not assigned to, click a comment ID, and change its status from Comment validation page

3 bugs within this card
Team member should not be able to access a survey they are not assigned to.
Team member should not be able to click on a comment ID.
Team member should not be able to change the comment's status (ex. approved --> rejected)
Reported by Taya as a Team Member
Should not be able to change approved comments into other states:

ONLY SUPERUSER SHOULD HAVE THAT POWER

Passing in DEV environment


Using proxy behind corporate firewall

fresh windows 10 machine.
vs 2019 in place
cmake 3.1.4 installed
vcpkg installed and integrated
vckpg search sqlite       - works fine
vckpg install sqlite3
fails due to ssl error because of the proxy
tried
netsh winhttp set proxy "http://machine\user@password:proxyhost:port"
netsh winhttps set proxy "http://machine\user@password:proxyhost:port"
set http_proxy = "http://machine\user@password:proxyhost:port"
set https_proxy ="https://machine\user@password:proxyhost:port"
no luck
any other options?

tried the following where using "proxyhost:port"
http://woshub.com/using-powershell-behind-a-proxy/
New error
-- Downloading https://sqlite.org/2019/sqlite-amalgamation-3270200.zip... Failed. Status: 4;"A requested feature, protocol or option was not found built-in in this libcurl due to a build-time decision."
CMake Error at scripts/cmake/vcpkg_download_distfile.cmake:172 (message):
after which talks about https_proxy and http_proxy again

https://github.com/Microsoft/vcpkg/issues/125
CMake download uses BITS so you need to set Proxy via IE

#125
See if that helps?

Hi
#125 does not help, because I have already downloaded cmake and installed that without issue

as a temporary workaround I can manually download the zip, drop it into the downloads folder and install from that point on

Hi @markiemarkus, thanks for posting this issue. I can't reproduce this issue locally, does the issue persist?

Please open a new issue if this is still a problem for you.

This is still a problem :/

@cbruegg If this issue is still exist, could you open a new issue to submit this problem?


Expand xslt-saxon test coverage

Fix #5139

Is XSL params covered ? Like https://camel.apache.org/components/3.21.x/xslt-saxon-component.html#_getting_useable_parameters_into_the_xslt

xsl:include is test by XsltTest::xsltInclude and it does not support native mode because it needs to generate the template dynamically.
xsl:params should be covered by XsltAggregateTest and yes it does not support native mode.


Adding GetRound method

Description
This PR added GetRound method, as the round information is a nice-to-have information in metrics API
Changes include

[ ] Bugfix (non-breaking change that solves an issue)
[ ] Hotfix (change that solves an urgent issue, and requires immediate attention)
[x] New feature (non-breaking change that adds functionality)
[ ] Breaking change (change that is not backwards-compatible and/or changes current functionality)

Checklist

[x] I have assigned this PR to myself
[x] I have added at least 1 reviewer
[ ] I have added the relevant labels
[ ] I have added sufficient documentation in code

Codecov Report

Merging #23 (34bfb86) into main (0f95a9c) will decrease coverage by 0.14%.
The diff coverage is 0.00%.

@@            Coverage Diff             @@
##             main      #23      +/-   ##
==========================================
- Coverage   93.66%   93.52%   -0.15%
==========================================
  Files           6        6
  Lines        1311     1313       +2
==========================================
  Hits         1228     1228
- Misses         60       62       +2
  Partials       23       23

Impacted Files
Coverage Δ

core/ibft.go
91.86% <0.00%> (-0.24%)
:arrow_down:

:mega: Codecov can now indicate which changes are the most critical in Pull Requests. Learn more

Closing this PR because @dbrajovic discussed a more broader implementation 🙏


Dataset

Dear Yan, I have just read your article ——"Object Detection in Hyperspectral Images," in IEEE Signal Processing Letters, vol. 28, pp. 508-512, 2021, doi: 10.1109/LSP.2021.3059204. You have made a great contribution to the field of hyperspectrum that you created a hyperspectral dataset for object-level target detection. But I didn't find the download link, which doesn't match what you said in your article. Could you please give me the download link of the dataset? I will quote your article if I use it. Thanks sincerely.

Thanks for your attention for our work. It will be soon. Maybe about 2-3 days.

Hi, the link of dataset has been added.

I'm sorry. I can't download the dataset with the password 'y4mp'.The password is wrong. Could you please figure it out for me?

Sorry for the inconvenience. It was our negligence that caused this problem, and I have modified the link.

Hi,
for me it is near impossible to use Baidu Cloud. Can I kindly ask if it is possible to upload the same dataset on another cloud like Mega or whatever else?
Thank you in advance.

@bach05 ,Hi, I have uploaded the 96-channel data to Onedrive. Please see README file.


Update dscNodeCounts.json

Fixing an incorrect location of parameter introduced in:
https://github.com/Azure/azure-rest-api-specs/pull/3404
Ref:
https://github.com/Azure/azure-sdk-for-python/issues/4965

Automation for azure-sdk-for-python

Automation for azure-sdk-for-js

@AutorestCI rebuild azure-sdk-for-python

Automation for azure-sdk-for-go

@AutorestCI rebuild azure-sdk-for-js

Automation for azure-sdk-for-ruby

@AutorestCI rebuild azure-sdk-for-go

Can one of the admins verify this patch?

Automation for azure-sdk-for-net
A PR has been created for you:
https://github.com/azure/azure-sdk-for-net/pull/5992
.NET SDK Commits:
https://github.com/adxsdknet/azure-sdk-for-net/pull/5992/commits/d2b560829757cec184c807e4533896b9f39e09f8

Automation for azure-sdk-for-java

LGTM

FYI @avkaur

Is there any updates for this PR?

@AutorestCI regenerate azure-sdk-for-go

Encountered an unknown error
Traceback (most recent call last):
  File "/usr/local/lib/python3.6/dist-packages/azure_devtools/ci_tools/github_tools.py", line 33, in exception_to_github
    yield context
  File "/usr/local/lib/python3.6/dist-packages/azure_devtools/ci_tools/bot_framework.py", line 105, in manage_comment
    response = getattr(self.handler, orderstr)(webhook_data.issue, *split_text)
  File "/usr/local/lib/python3.6/dist-packages/swaggertosdk/restapi/restbot.py", line 54, in regenerate
    return self.rebuild(issue, repotag)
  File "/usr/local/lib/python3.6/dist-packages/swaggertosdk/restapi/restbot.py", line 36, in rebuild
    self.sdk_default_base
  File "/usr/local/lib/python3.6/dist-packages/swaggertosdk/restapi/github_handler.py", line 151, in rest_pr_management
    sdk_tag=sdk_tag
  File "/usr/local/lib/python3.6/dist-packages/swaggertosdk/SwaggerToSdkNewCLI.py", line 254, in generate_sdk_from_git_object
    with manage_git_folder(gh_token, Path(temp_dir) / Path("rest"), branched_rest_api_id, pr_number=pr_number) as restapi_git_folder, \
  File "/usr/lib/python3.6/contextlib.py", line 81, in __enter__
    return next(self.gen)
  File "/usr/local/lib/python3.6/dist-packages/azure_devtools/ci_tools/github_tools.py", line 272, in manage_git_folder
    clone_to_path(gh_token, temp_dir, split_git_id[0], branch_or_commit=branch, pr_number=pr_number)
  File "/usr/local/lib/python3.6/dist-packages/azure_devtools/ci_tools/github_tools.py", line 187, in clone_to_path
    login = user_from_token(gh_token).login
  File "/usr/local/lib/python3.6/dist-packages/github/AuthenticatedUser.py", line 229, in login
    self._completeIfNotSet(self._login)
  File "/usr/local/lib/python3.6/dist-packages/github/GithubObject.py", line 263, in _completeIfNotSet
    self._completeIfNeeded()
  File "/usr/local/lib/python3.6/dist-packages/github/GithubObject.py", line 267, in _completeIfNeeded
    self.__complete()
  File "/usr/local/lib/python3.6/dist-packages/github/GithubObject.py", line 272, in __complete
    self._url.value
  File "/usr/local/lib/python3.6/dist-packages/github/Requester.py", line 264, in requestJsonAndCheck
    return self.__check(*self.requestJson(verb, url, parameters, headers, input, self.__customConnection(url)))
  File "/usr/local/lib/python3.6/dist-packages/github/Requester.py", line 275, in __check
    raise self.__createException(status, responseHeaders, output)
github.GithubException.GithubException: 502 {'message': 'Server Error'}

@AutorestCI regenerate azure-sdk-for-go


Segmentation_evaluation with tomo_id with leading 0's [Minor issue]

Hi Frosina,
When using the segmentation_evaluation part of DeePiCt 3dcnn I ran into the issue that you cannot have leading 0's in the tomogram ids.
E.g. I had a tomogram named 00345, which had worked to perform the full pipeline (from training to prediction) but when I performed segmentation evaluation I run into the issue that the tomo_df (line 64 in the segmenation evaluation script):
    tomo_df = df[df[DTHeader.tomo_name] == tomo_name]
^leads to an empty dataframe. In the next line when this is then used to get the path to the membrane mask it fails:
   target_path = tomo_df.iloc[0][clean_mask_name]
Checking the value of tomo_name showed that the leading zero's were removed (whereas they were still present in the actual dataframe). My quick fix was just to rename the tomograms in the metadata file.
Best,
Rasmus

The commit 03986ad solved this issue


Faster state switch

We can add a layer of indirection at least to STStorage and DataMPT, maintain two prefixes for them and keep the one currently used in some settings (SYSVersion is a perfect place for it), then instead of moving one prefix to another just switch the setting and delete data for another prefix in background (can also be done safely wrt any restarts).
Refs. #2019.

This also can be a prologue to supporting state exchange-based synchronization for seriously outdated but not-freshly-started nodes.

Fixed in #2201.


custom URL path format

the current URL path format looks like
/$user/$repo/$command/branch/$branch/$filepath
i want the freedom to make it look like
/$user/$repo/branch/$branch/$filepath._$command
with the exception
/$user/$repo/branch/$branch/$filepath
if $command == raw
[redirect or alias from $path._raw to $path]
new restriction:
you cant store files with extension ._$command
as alternative, allow to use 'query format' as in
/$user/$repo/branch/$branch/$filepath?$command
which might annoy some web crawlers [SEO...]
examples:
/user/repo/raw/branch/master/file     to /user/repo/branch/master/file
/user/repo/src/branch/master/file     to /user/repo/branch/master/file._src
/user/repo/commits/branch/master/file to /user/repo/branch/master/file._commits
/user/repo/_edit/branch/master/file   to /user/repo/branch/master/file.__edit
/user/repo/_delete/branch/master/file to /user/repo/branch/master/file.__delete

... or make urls even shorter, by assuming 'branch/master' as default selector:
/user/repo/raw/branch/master/file     to /user/repo/file
/user/repo/src/branch/master/file     to /user/repo/file._src
/user/repo/commits/branch/master/file to /user/repo/file._commits
/user/repo/_edit/branch/master/file   to /user/repo/file.__edit
/user/repo/_delete/branch/master/file to /user/repo/file.__delete

use case. how is this useful? for example, to [easily] include other files from a markup file, such as images, scripts, videos, etc. without using the prefix ../../../raw/branch/master/ [static] or rewriting the path as in markdown.Image [dynamic]
this would make gitea more like a content management system.
the path format should be visible to api clients. [print as html meta tag?]
would gitea devs accept an implementation of this request?

Gitea version: 1.6.0

Theoretically this could be already possible to implement using nginx rewrite rules. I don't see much use case for this built in directly in gitea


[Question] Are there simple examples?

Hi there,
I wanted to start working with MapsUI since it looks really amazing in the sample-project you provided.
But I had 1 question, are there any more simple examples, that work with MAUI and MVVM?
I tried a couple of things but they don't seem to work for me.
I know that I am doing things wrong, hence why asking the question.
Kind regards
Erscroas

I will move to the discussion tab.


Prioritize High Gas Price Transactions

Fixed Issue(s)
fixes #1285
Changelog

[x] I thought about the changelog and included a changelog update if required.

Credit
credit to @JoshMelton for initial work.

Maybe once I fix the unit tests I broke I can think about that 😅

@abdelhamidbakhta Fixed the unit tests.
I didn't do any manual testing but I personally feel comfortable with the unit test coverage. Let me know if you don't think that's sufficient :)

@NicolasMassart @MadelineMurray told me to ping y'all when this is addressed. We now drop the remote, lowest gas-price, oldest transaction. Before we just sorted by remote and oldest.


Option to output schema as JSON

Schemas are currently output as YAML (as its more succinct) but user may want to output as JSON.
This issue is mentioned in the README.

The intention is to use those schema definitions in json format in order to be registered in a kafka schema registry. This feature would really help the avoid the conversion that I am forced to do now. Thanks!


Include actual and expected values in config test error message

this allows to debug config vars test by sending expected and actual value back

@rajatjindal Also could you please amend the commit message?  It makes sense close up, but to someone scanning the history it won't be clear what it refers to.

@rajatjindal Also could you please amend the commit message? It makes sense close up, but to someone scanning the history it won't be clear what it refers to.

done.

ok, sorry for the back and forth on the PR. current state:

ensure returns the error msg, but it was not clear. so I've updated it to include expected/actual values
changed the variable names to reflect expected/actual values correctly
I've removed other unnecessary changes.