chore: Projen Touchup and Upgrade

Includes https://github.com/cdklabs/cdk-hyperledger-fabric-network/pull/2, but activates auto-upgrade now that ownership is fixed. Also includes a dependency upgrade.

@Mergifyio refresh


Add isFinal flag for (attached) signature V2 packets

Changes Unknown when pulling 0e3fa72faaf9d80d5a44b6bf8098bd89fb746dca on akalin/sign-final-flag into ** on akalin/sign-v2**.

This is basically an adaptation of #33 for signing.

Coverage decreased (-0.6%) to 84.71% when pulling c7b2063424182ebf62ceeb03ab8431982cccc68c on akalin/sign-final-flag into eb21fae1e407ea9ba86bf3459ef786ea57ea0c86 on master.


Conflicting implementation error after updating to 0.16 from 0.15

Setup
Versions

Rust: 1.20.0
Diesel: 0.16.0
Database: sqlite
Operating System Arch Linux

Feature Flags

diesel: "sqlite"
diesel_codegen: "sqlite"

Problem Description
My application builds fine when using diesel 0.15.2 and diesel_codegen 0.15.0. After running cargo update, both were updated to 0.16.0. When I try to build, I get the following error:
error: recursion limit reached while expanding the macro `table_body`
  --> src/db.rs:19:5
   |
19 |     infer_schema!("dotenv:DATABASE_URL");
   |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
   |
   = help: consider adding a `#![recursion_limit="128"]` attribute to your crate
   = note: this error originates in a macro outside of the current crate

OK, do what the compiler says, and add #![recursion_limit="128"] to the crate. Build now fails with:
error[E0119]: conflicting implementations of trait `diesel::JoinTo<db::schema::__diesel_infer_schema::infer_presols::presols::table>` for type `db::schema::__diesel_infer_schema::infer_awards::awards::table`:
  --> src/db.rs:19:5
   |
17 |     infer_schema!("dotenv:DATABASE_URL");
   |     ------------------------------------- first implementation here
18 |
19 |     joinable!(awards -> presols(presol_id));
   |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ conflicting implementation for `db::schema::__diesel_infer_schema::infer_awards::awards::table`
   |
   = note: this error originates in a macro outside of the current crate

error[E0119]: conflicting implementations of trait `diesel::JoinTo<db::schema::__diesel_infer_schema::infer_awards::awards::table>` for type `db::schema::__diesel_infer_schema::infer_presols::presols::table`:
  --> src/db.rs:19:5
   |
17 |     infer_schema!("dotenv:DATABASE_URL");
   |     ------------------------------------- first implementation here
18 |
19 |     joinable!(awards -> presols(presol_id));
   |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ conflicting implementation for `db::schema::__diesel_infer_schema::infer_presols::presols::table`
   |
   = note: this error originates in a macro outside of the current crate

error: aborting due to 2 previous errors

Based on older bugs, I tried to add the 'large-tables' feature to diesel, but it does not fix it. Reverting to 0.15* fixes it. In the meantime, I'll just make do by holding the version back, but it doesn't seem right that an update resulted in build failures.
Steps to reproduce
Module triggering error:
mod schema {
    use diesel::Table;

    infer_schema!("dotenv:DATABASE_URL");

    joinable!(awards -> presols(presol_id));
}

Schema:
$ diesel print-schema
table! {
    awards (id) {
        id -> Integer,
        date -> Nullable<Text>,
        awdDate -> Nullable<Text>,
        awdNbr -> Text,
        awardee -> Text,
        url -> Text,
        presol_id -> Integer,
    }
}

table! {
    presols (id) {
        id -> Integer,
        date -> Nullable<Text>,
        subject -> Text,
        description -> Text,
        naics -> Integer,
        url -> Text,
        solnbr -> Text,
        ignored -> Bool,
    }
}

table! {
    scanned_dates (date) {
        date -> Nullable<Text>,
    }
}

Checklist

[✓] I have already looked over the issue tracker for similar issues.

joinable! calls are now inferred by infer_schema!. Just remove it and it should work :)

Removed joinable! line and it works perfectly. Thank you!


bug: Sign in page problem in https://app.100xdevs.com/signin

Describe the bug
When you visit the signin page of 100xdevs URL: https://app.100xdevs.com/signin, you get a modal where you fill the credentials to log into the site, but if you dont fill the credentials or fill only one of the field and click on login button, on the bottom right corner of the screen the you get the message saying 'signing in...' with a loader icon.
To Reproduce
Steps to reproduce the behavior:

visit the home page of 100xdevs URL: https://app.100xdevs.com
click on the Login button on top right corner.
Without filling the fields or filling only one field click on login button below.
A error on the fields will be generated and a message saying 'signing in..' with loader will come

Expected behavior
only the error on the fields should be there without the signing in message
Screenshots or GIFs
Screenshot with none of the field filled with message.

Info (please complete the following information):

Browser [opera GX, Microsoft Edge]

Additional context
The user can safely log in if the credentials are correct or an error will pop up if the credentials are not correct which is expected.

Hi @TarunVishwakarma1, it has been fixed in this PR - #870

Is this Issue already solved? because in localhost the login button is disabled when the required fields are not filled, but in production app - https://app.100xdevs.com/signin  the login button is active even when the fields are empty.

Sure Closing the issue


Test that only one radio can be selected

For radios, only one should be selectable with the same name in the same form.
Same goes for options within a select, unless "multiple" attribute exists.
Adding the checked attribute should not affect anything, but setting the magic checked property to true should.

I've added some tests in https://github.com/PhpGt/Dom/blob/d1c58fd63d77e86f9b8dec98f2195caad1969acd/test/unit/FormTest.php#L8 that are currently failing. If anyone wants to pick this up and implement the functionality that'd be amazing.


Add [Agent] Jedis LETTUCE client plugin

Please answer these questions before submitting pull request

Why submit this pull request?

[x] New feature provided

Add [Agent] Jedis LETTUCE client plugin

Related issues
Jedis LETTUCE client plugin #766

Bug fix

Bug description.

How to fix?

New feature or improvement

Describe the details and related test reports.

@lytscu Please sync to master and update the version number to SNAPSHOT


Component mqtt binary_sensor log warning “No matching payload found for entity”

Home Assistant release with the issue:
0.89.2
Last working Home Assistant release (if known):
unsure maybe (0.89.0+);
Whichever made custom-components require all component files.
Operating environment (Hass.io/Docker/Windows/etc.):
Hass.io
Component/platform:
https://www.home-assistant.io/components/binary_sensor.mqtt/
Description of problem:
When using multiple Sonoff_RF components,  Error log outputs multiple
"[homeassistant.components.mqtt.binary_sensor] No matching payload found for entity: "

Used to add Custom_component for mqtt/binary_sensor.py which would disable output.
-- Now since 8.9.0 having to add all mqtt files via Configurator IS UN-WORKABLE.
-- also monitoring release updates to all mqtt component files against custom-components IS UN-WORKABLE.

Hass.io runs slow when issue outputs to log.

Hass.io takes 15-35 minutes to reboot.

MariadB is locking up due to too many of these errors recorded.
-- Snapshot takes 90 mins, as MariaDB takes ages.
-- this is eating up my SD Card's life expectancy.
-- Don't like losing my house data.

Please revert pull request (https://github.com/home-assistant/home-assistant/pull/11836)
or update code from components/mqtt/binary_sensor.py #Line: 147
To comment out LOGGER warning
Example of change:
        @callback
        def state_message_received(_topic, payload, _qos):
            """Handle a new received MQTT state message."""
            value_template = self._config.get(CONF_VALUE_TEMPLATE)
            if value_template is not None:
                payload = value_template.async_render_with_possible_json_value(
                    payload, variables={'entity_id': self.entity_id})
            if payload == self._config.get(CONF_PAYLOAD_ON):
                self._state = True
            elif payload == self._config.get(CONF_PAYLOAD_OFF):
                self._state = False
            else:  # Payload is not for this entity
#                _LOGGER.warning('No matching payload found'
#                                ' for entity: %s with state_topic: %s',
#                                self._config.get(CONF_NAME),
#                                self._config.get(CONF_STATE_TOPIC))
                return

Example Error log (1 entry below, but logs this 19 times):
2019-03-19 10:23:09 WARNING (MainThread) [homeassistant.components.mqtt.binary_sensor] No matching payload found for entity: pir a hall with state_topic: tele/sonoff-RF/RESULT
2019-03-19 10:23:09 WARNING (MainThread) [homeassistant.components.mqtt.binary_sensor] No matching payload found for entity: pir b bathroom with state_topic: tele/sonoff-RF/RESULT
2019-03-19 10:23:09 WARNING (MainThread) [homeassistant.components.mqtt.binary_sensor] No matching payload found for entity: kitchen smoke with state_topic: tele/sonoff-RF/RESULT
2019-03-19 10:23:09 WARNING (MainThread) [homeassistant.components.mqtt.binary_sensor] No matching payload found for entity: livingroom window r with state_topic: tele/sonoff-RF/RESULT
2019-03-19 10:23:09 WARNING (MainThread) [homeassistant.components.mqtt.binary_sensor] No matching payload found for entity: kitchen window with state_topic: tele/sonoff-RF/RESULT
2019-03-19 10:23:09 WARNING (MainThread) [homeassistant.components.mqtt.binary_sensor] No matching payload found for entity: bedroom window with state_topic: tele/sonoff-RF/RESULT
2019-03-19 10:23:09 WARNING (MainThread) [homeassistant.components.mqtt.binary_sensor] No matching payload found for entity: livingroom window l with state_topic: tele/sonoff-RF/RESULT
2019-03-19 10:23:09 WARNING (MainThread) [homeassistant.components.mqtt.binary_sensor] No matching payload found for entity: front door with state_topic: tele/sonoff-RF/RESULT
2019-03-19 10:23:09 WARNING (MainThread) [homeassistant.components.mqtt.binary_sensor] No matching payload found for entity: kitchen fridge door with state_topic: tele/sonoff-RF/RESULT
2019-03-19 10:23:09 WARNING (MainThread) [homeassistant.components.mqtt.binary_sensor] No matching payload found for entity: remote1 ab with state_topic: tele/sonoff-RF/RESULT
2019-03-19 10:23:09 WARNING (MainThread) [homeassistant.components.mqtt.binary_sensor] No matching payload found for entity: remote1 c with state_topic: tele/sonoff-RF/RESULT
2019-03-19 10:23:09 WARNING (MainThread) [homeassistant.components.mqtt.binary_sensor] No matching payload found for entity: remote1 cd with state_topic: tele/sonoff-RF/RESULT
2019-03-19 10:23:09 WARNING (MainThread) [homeassistant.components.mqtt.binary_sensor] No matching payload found for entity: remote1 d with state_topic: tele/sonoff-RF/RESULT
2019-03-19 10:23:09 WARNING (MainThread) [homeassistant.components.mqtt.binary_sensor] No matching payload found for entity: remote1 a with state_topic: tele/sonoff-RF/RESULT
2019-03-19 10:23:09 WARNING (MainThread) [homeassistant.components.mqtt.binary_sensor] No matching payload found for entity: remote1 b with state_topic: tele/sonoff-RF/RESULT
2019-03-19 10:23:09 WARNING (MainThread) [homeassistant.components.mqtt.binary_sensor] No matching payload found for entity: pir e bedroom with state_topic: tele/sonoff-RF/RESULT
2019-03-19 10:23:09 WARNING (MainThread) [homeassistant.components.mqtt.binary_sensor] No matching payload found for entity: pir d livingroom with state_topic: tele/sonoff-RF/RESULT
2019-03-19 10:23:09 WARNING (MainThread) [homeassistant.components.mqtt.binary_sensor] No matching payload found for entity: pir c kitchen with state_topic: tele/sonoff-RF/RESULT

Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant):
binary_sensor:
# Door
  - platform: mqtt
    name: 'front door'
    payload_on: 'SECRET_RF_CODE_ON'
    payload_off: 'SECRET_RF_CODE_OFF'
    device_class: door
    qos: 1
    state_topic: 'tele/sonoff-RF/RESULT'
    value_template: "{{ value_json.RfReceived.Data }}"
  - platform: mqtt
    name: kitchen fridge door
    payload_on: 'SECRET_RF_CODE_ON'
    payload_off: 'SECRET_RF_CODE_OFF'
    device_class: door
    qos: 1
    state_topic: 'tele/sonoff-RF/RESULT'
    value_template: "{{ value_json.RfReceived.Data }}"

# Window
  - platform: mqtt
    name: bedroom window
    payload_on: 'SECRET_RF_CODE_ON'
    payload_off: 'SECRET_RF_CODE_OFF'
    device_class: window
    qos: 1
    state_topic: 'tele/sonoff-RF/RESULT'
    value_template: "{{ value_json.RfReceived.Data }}"
  - platform: mqtt
    name: livingroom window l
    payload_on: 'SECRET_RF_CODE_ON'
    payload_off: 'SECRET_RF_CODE_OFF'
    device_class: window
    qos: 1
    state_topic: 'tele/sonoff-RF/RESULT'
    value_template: "{{ value_json.RfReceived.Data }}"
  - platform: mqtt
    name: livingroom window r
    payload_on: 'SECRET_RF_CODE_ON'
    payload_off: 'SECRET_RF_CODE_OFF'
    device_class: window
    qos: 1
    state_topic: 'tele/sonoff-RF/RESULT'
    value_template: "{{ value_json.RfReceived.Data }}"
  - platform: mqtt
    name: kitchen window
    payload_on: 'SECRET_RF_CODE_ON'
    payload_off: 'SECRET_RF_CODE_OFF'
    device_class: window
    qos: 1
    state_topic: 'tele/sonoff-RF/RESULT'
    value_template: "{{ value_json.RfReceived.Data }}"

Traceback (if applicable):

Additional information:
This is related to this change
https://github.com/home-assistant/home-assistant/pull/11836
plus referenced in
https://community.home-assistant.io/t/mqtt-py-log-warning-no-matching-payload-found-for-entity/42995/5
I really need this fixed, please let me know what I can do to fix this,
am I required to push a commit to fix / add configuration option to allow for Sonoff_RF or other devices acting on different codes.

Quick fix: change log level of homeassistant.components.mqtt.binary_sensor:
logger:
  default: info
  logs:
    homeassistant.components.mqtt.binary_sensor: critical

The reason why this is logged as warnings is to aid debugging, but maybe we should log a warning only once and then downgrade to debug severity.

Wow thank you @emontnemery, your solution worked a charm.
I agree, as its a debug level event & worth downgrading to a debug entry
Should I close this issue or wait for debug entry change ?

The reason why this is logged as warnings is to aid debugging

Precisely.
The problem is multiple sensors using the same MQTT topic. Sometimes the payload is intended  for Sensor A, sometimes it's for Sensor B. Nevertheless they both receive the same payload and, of course, one fails to translate it into a valid state (thereby producing the warning message about 'no matching payload').
The solution is not to suppress legitimate warning messages but to improve the entity's value_template so it always returns a valid state. It's really that simple.
In this post I provided two examples of how to create a value_template that converts  the received payload into a valid state.

I do not agree that we should all turn something that is simple YAML into a very complicated use of value_templates and code I would call a hack. The issue is the logging of something that is not an error and that does not really help anyone. The long thread on https://community.home-assistant.io/t/mqtt-py-log-warning-no-matching-payload-found-for-entity/42995/82 is a very convincing argument why this logging should be reverted. I have personally altered the log level of the mqtt component but it does not remove the logging from the /dev-info page and this is where is really annoys me at the many many any loggings there drown the real issues that require attention.
There is so much attention right now on making HA easier for beginners. Requiring that a binary sensor using MQTT with popular projects like Tasmota is setup using a complex Jinja language hack is not beginner friendly. Neither is the 1000s of errors you get in a normal house with a few RF motion sensors that are triggered all the time as the family walks around the house.

I would call a hack

Here's what I would call a hack: a single MQTT topic used to represent the states of multiple sensors.
This technique flies in the face of MQTT's best practices. MQTT topics cost nothing and Home Assistant adheres to the well-established practice of supporting one or more topics per sensor (not the odd practice of multiple sensors per topic).
https://www.hivemq.com/blog/mqtt-essentials-part-5-mqtt-topics-best-practices/

The issue is the logging of something that is not an error and that does not really help anyone.

Except it is an error and I want errors to be identified. If I agree to ship you black or white paint and you receive a drum of red paint, that's an error. Similarly, receiving a value that matches neither payload_on or payload_off is an error and ought to be reported.
For the case of devices that multiplex many sensors in one MQTT topic, the solution is to use a template to extract the correct values. That's standard procedure for JSON payloads. The template needed to extract values from the multiplexed topic isn't particularly complex.
An alternative solution for handling a multiplexed topic, especially when many sensors are involved, is to use a 'demultiplexer' automation to separate the multiplexed values into unique topics, one per sensor. The result is that each sensor's configuration requires no template.
I explained both techniques, in detail, in the following post:
Sonoff RF Bridge. Strategies for receiving data.

Welcome to the real world my friend.
The real world consists of Tasmota which is used by 10000 of HA users and 1000s use an RF bridge which converts 433 MHz messages to MQTT. And it does that in a single topic. And then there is OpenMQTTGateway also used by many and it can be made to either send in a single topic or it can append the data payload to the topic path. That is great for Motion sensors with one code. But it cannot be used for a single binary_sensor in HA because it can only listen to one topic. Then you have to use a hack of input_booleans and template sensors to turn a single sensor on and off.
You would have to implement these RF gateways so they decode messages in pairs of two codes per mqtt topic. Not easy. Tasmota has a very geeky command line rule feature that can do it but there is only room for few rules. The right place is to do it in HA in the definition of a binary sensor with on and off payloads. And it is implemented and it works great with the number of sensors that normal people have in a normal home. The issue is just the error messages. If they were debug only and only visible when you change logging to debug then it would be OK. But the issue is that it floods the report in the web UI
I use the Jinja hack to avoid the error mssages. Yes it works for you and for me, two geeks. But it annoys me on behalf of the new users that are not programmers that things have to be so geeky because someone insists on giving error messages that few can use for anything
Alternatively the error could be displayed if a given mqtt topic has a payload that does not match any sensors or automations. But that would be harder and not just removing 3 lines of code

I use the Jinja hack

Except it's not a hack, its merely a template to extract values as is commonly used for many other purposes in Home Assistant.
The number of users is immaterial for what is a fundamentally poor implementation of MQTT topic structure. Fortunately, it can be handled by Home Assistant but not at the expense of becoming lax about handling errors. Receiving any value other than the two defined in the sensor's configuration is indeed an error and I support it being reported as such. To avoid the error, use a template as is the custom for many other situations. Just par for the Home Assistant course and nothing 'geeky' about it.

Is it possible to re-open this issue? I've just started to get the same
‘No matching payload found for entity’
error on all devices that I have upgraded to Tasmota v6.7 from v6.6.
Or would it be better to open a new issue instead of re-opening this one?

@emontnemery Erik,
in my last update of Tasmota discovery .ino I've changed buttons and switches creation, following a new separated topic from relay to give a more granular control:
{
  "name": "Sonoff Switch1",
  "stat_t": "~stat/RESULT",
  "value_template": "{{value_json.SWITCH1}}",
  "pl_on": "ON",
  "avty_t": "~tele/LWT",
  "pl_avail": "Online",
  "pl_not_avail": "Offline",
  "uniq_id": "471078_SW_1",
  "device": {
    "identifiers": [
      "471078"
    ],
    "connections": [
      [
        "mac",
        "CC:50:E3:47:10:78"
      ]
    ]
  },
  "~": "sonoff/",
  "frc_upd": true,
  "pl_off": "OFF"
}

Some users are complains about the warning.
What should I change on json creation to match HA YAML?
Thanks.


Azure ModelPackage class returns wrong location

Package Name: Azure ModelPackage
Package Version: azureml-contrib-services-1.10.0 azureml-core-1.10.0.post1
Operating System: mcr.microsoft.com/azureml/intelmpi2018.3-ubuntu16.04:20200723.v1
Python Version: /opt/hostedtoolcache/Python/3.7.8/x64

Describe the bug
We got a bug that the  ModelPackage class does not return the correct location of a registered image.
From the Documentation one should do:
`from azureml.core import Model
package = Model.package(ws, [model], inference_config)
package.wait_for_creation(show_output=True)
"Display the package location/ACR path"
print(package.location)`
And the return should look like this:
<acrinstance>.azurecr.io/package@sha256:<imagename>
for example:
diml*********.io/package:20200729142244
However the return looks like this:
<acrinstance>.azurecr.io/package@sha256:<digest>
for example:
diml*********.io/package@sha256:f759498600bb248c08f73ee49*****716d63c6586e69d7e464568e*****
This is a big problem as we cant relay the information to our release pipeline to pull the correct image as we need the imagename tag and not the digest to pull the correct image.
We tried using the function package.get_container_registry() however there is also no image name returned.
We also noticed that the .package() function creates a second entry in our azure container registry with the naming of repository: azureml/azureml_5faac73d1c80b1***** were we can observe the same created docker image as under the naming diml*********.io/package:20200729142244 However other than scanning the log file, there is currently no way to retrieve the above mentioned location either.
Currently we are not able to make automatic releases as the the return of the image packages does not include the correct location were the image is created that can be used in a docker pull command.
We use this feature since about 6 months and we have that bug since yesterday as our automatic releases were falling.
To Reproduce
Steps to reproduce the behavior:

Create a simple ML Model
call package = Model.package(ws, [model], inference_config)
call package.wait_for_creation(show_output=True)
call package.location

Expected behavior
Retrieve the location of the created image that can be used in a docker pull command.

@Mystorius apologies for the delayed response. is this still an issue?

@Mystorius apologies for the delayed response. is this still an issue?

Currently the behavior is that model package will always return the digest associated with the built image. However it still does tag the image with the user requested tag, that is why you can see it in your ACR. If the digest is of no use to you, you can disregard it and construct the image path on your own, since you know what you expect it to look like (i.e: diml*********.io/package:20200729142244) That is the current work around that we have in place. I hope this helps.

Hi,
Closing the issue, please re-open if this didn't solve your problem.

#please-close


Fix typing and clearer code in evented-set.

First is mypy is not able to properly infer the types here but in particular **_events is incorrect if it contain a key named auto_connect as this is the name of the second parameter of EmitterGroup constructor.
We can just pass changed=changed directly.

Thanks for the conflict fixing.


Helper scripts to set the REACT_APP environment variables

Most of the the environment variable settings to use the React UI can be determined from langstream CLI outputs. I added a couple of helper scripts and some instructions in the README to make it easier to properly set the env vars.

@cdbartholomew can you please run
mvn generate-sources
in order to fix the style issues ?


Bump minor version to test github workflow publish

Pull Request Test Coverage Report for Build<PHONE_NUMBER>2
Details

1 of 1 (100.0%)  changed or added relevant line in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 80.482%

Totals

Change from base Build<PHONE_NUMBER>6:
0.0%

Covered Lines:
2202

Relevant Lines:
2736

💛  - Coveralls


Add "per host" feature

i think we should be able to do operation (deploy, restart, reconfigure) only on a single host or a group of host.
It will be useful for example if we add a worker to our cluster and want to deploy only to this new host.
Also it lays the groundwork for #288

To implement this functionality, we must have the basic elements to launch an operation on a host:

In the operation_log table, we need to add a host column which is a string that represents a single host. If the host column is "null" then the operation will be launched as it is today. If the host column has a value, the operation will be launched on this single host. Launching an operation on a specific host list is not necessary, it is enough to have the same operation several times with a different host for each. In addition, it allows us to know the state of the operation host by host.
In the deployment_log table we must add a host column which is a list of hosts to know the list of hosts that have been specified for this deployment.
We need to update the DeploymentRunner, DeploymentIterator and Executor classes to take into account the new host column of the operation_log table. To run a playbook on a host we need to use the --limit option of the ansible-playbook command.
We need to refactor the AnsibleTopologyReader class which is not used to be able to read the Ansible inventory. This is required for the functionality below. In addition, this will allow us, from a playbook, to have the list of hosts concerned by this playbook.
Before inserting an operation in the operation_log table, it is necessary to check if a host has been specified and if this host is indeed in the list of hosts of one of the plays in the playbook. This is not necessary for the ansible-playbook command to work but it avoids launching an operation which will do nothing since the specified host is not in the list of hosts of the playbook.

To be able to test this functionality, we will modify the tdp plan run command to be able to specify a list of hosts via a --host multiple option. If one of the operations in parameter does not contain all the hosts specified, the command must return an error and the plan must not be written in the database.
Then in the following issues, we will gradually use these basic elements in the other tdp plan ... commands.

In the operation_log table, we need to add a host column which is a string that represents a single host. If the host column is "null" then the operation will be launched as it is today. [...]

In that case, how could we handle the case where an operation fails on a single host?

If host is "null", so the operation run on all hosts defined in the playbook (the current behavior), if the playbook fail (return code other than 0), this is failure for all hosts and the operation must be run with a resume (current behavior) for example. We do not change the behavior.

In the deployment_log table we must add a host column which is a list of hosts to know the list of hosts that have been specified for this deployment.

It means, we duplicate the information about hosts affected by operations. How  the consistency is garantied in this case?
Do we really need this duplication (list of hosts can easily be know by requesting operation_log table)?

Columns in deployment_log table are used to log what arguments was used to generate this deployment. This issue does not change this behavior. I think we will have discussion about it when we will add the "plan edition" feature.


Improve datadog rum intake

Now using our brand new reverse proxy location for sending sessions to datadog!

LGTM, however I wonder what could happen to our https://gateway.onlydust.xyz URL if it starts getting blocked by some ad-blockers because of this. We'll see but maybe we'll have to use a distinct domain just to avoid being black listed.

I don't think ad blockers block a whole domain based on the content sent to it but I'm not sure neither


More options for content block preview (redirect)

User Story
As a CMS user, I want to be able to access content block options from a block, so that I can do this while reviewing the block at a page level.
Acceptance Criteria

[ ] Content blocks have a clickable ‘more options’ icon, as per the wireframe: https://projects.invisionapp.com/share/ZRL4T2HQAGB#/screens/301923101
[ ] Clicking the icon presents a popup with the following (clickable) options:
[ ] Clicking 'Content' takes user to existing content page tab
[ ] Clicking ‘History’ takes user to existing History page tab
[ ] Clicking ‘Settings’ takes user to existing Settings page tab
[ ] Any other tabs that are top level are also included and link to existing functionality, e.g link tracking
[ ] Mouse hover styling is present for options in popup
[ ] More options icon is still available when the block is expanded (as per https://github.com/silverstripe/silverstripe-elemental-blocks/issues/43)

Notes

Further options for versioning a block are captured here: https://github.com/dnadesign/silverstripe-elemental/issues/290

We are going to take a little bit of a performance hit by having to load all the CMS form fields for every block when you load a page in the CMS.
Relevant comment from @chillu on recent work for a similar feature: https://github.com/symbiote/silverstripe-gridfieldextensions/pull/225#issuecomment-347404105

Thanks for flagging this Robbie! Can we please measure before-after state on a non-trivial page (e.g. using ten instances of five different blocks)? In general, we should move this to a client-side cache which gets refreshed in the background, for the (usually small) chance that the form fields on this particular record are different from the ones we've cached. In which case React can re-render the fields. We've split out structure from data in the form schema to allow for this, right? There's potential for edge cases, where you started editing a form field which is then removed in the re-render (because of conditional logic in getCMSFields().
Ideally this should happen via GraphQL, which comes built-in with powerful client caching (and invalidation). Which means getting form schemas through GraphQL, and the "form registry" we're using for AssetAdmin.
Again, outlining the long term vision here, let's try to get as close as possible to this. OSSers team is happy to help with any GraphQL form schema work if that's required as a baseline.

So I've been thinking a little about this. The performance hit for only 3 blocks is pretty severe - about 20% of the request is spent on getCMSFields. This would be way higher for a full page of blocks - and that didn't include more complex blocks like elemental userforms (although this isn't intended to be edited in-line). I don't think we can realistically load tab names for each block on the page without a significant hit to performance.
There could be a compromise though - we can load and cache tab names per block type. This would give a list of options that's accurate most of the time. In the rare case that the state of an element affects the tabs that it shows, there is a hook that we can use in FormBuilderLoader to update the options - the downside being that the user would have to trigger in-line editing by either expanding the block or clicking one of the existing options.
End result:

Performance not affected when loading tab names from a cache
List of tab options may not be complete until the form is loaded for a block
Once the form is loaded the block will maintain an updated list of tab options
If the user manages to remove tab options from modifying block data, the options should automatically update.
Eliminates the need for an additional request when a block is added

@clarkepaul wasn't keen on just having some of the tabs as options, so hopefully this is an acceptable compromise.
There is one gotcha here. The way that "many" relations add tabs (eg. Link Tracking) means that we need an existing object to fetch form fields for, or we can do this hacky thing:
$object = self::singleton();
$object->ID = 1;
$fields = $object->getCMSFields();

This works and gives the right list of tabs though!

there is a hook that we can use in FormBuilderLoader to update the options - the downside being that the user would have to trigger in-line editing by either expanding the block or clicking one of the existing options

AFAIK you will need to expand the block in order to edit it, it'll show a preview by default.

The way that "many" relations add tabs (eg. Link Tracking) means that we need an existing object to fetch form fields for, or we can do this hacky thing:

Note that the presence of these two tabs has been raised as a core bug: https://github.com/silverstripe/silverstripe-cms/issues/2227

AFAIK you will need to expand the block in order to edit it, it'll show a preview by default.

This is true, but it appears the edit options still appear in the list even when you don't have the form loaded. If the A/C means the form has to be loaded before we get those options in the dropdown then that's ideal.

I don't think that sounds like it makes sense =(

The tabs don't show as tabs with this, the tab content is shown when the section is chosen form the dropdown. The dropdown is rendered regardless of whether the form is rendered. I assume when you click the tab option (eg. Content) the form will be loaded and that tab content will be shown. Maybe @clarkepaul can clarify.

The designs answered the question:

We should have the tab options before we load the form.

I have split this into a few issues: #323, #324 and #325


Read LOG freezes app and flipper needs to be restarted

when you clock Read LOG in the app it freezes/ crashes the app, and you need to restart the flipper.

Hi @throughthetrees, thank you for sharing this with us. We will try to replicate your issue and find a solution for it. Please share as much details as you can of what you were doing when you encountered the problem.

Hi @throughthetrees fixed in #9 , now in release, thanks for you feedback


Icalendar feed

There is a problem with the .ics feed found at webcal://school.brainhackmtl.org/schedule/index.ics.
It seems to be a problem related to Line 1, but I can't find out why.
Lines not delimited by CRLF sequence near line # 1
Reference: RFC 5545 3.1. Content Lines

The iCalendar object is organized into individual lines of text, called content lines. Content lines are delimited by a line break, which is a CRLF sequence (CR character followed by LF character).

Related thread on SO, but in PHP so I don't know what to do next. try to implement \r\n after each line?
@gkiar, do you have any idea since you are the pro of .ical feed?

@SamGuay can you point me to how we're generating the feed, if it's quick? (just to save me bouncing around looking for it). I think despite calendars that I've generated in the past not passing this validation, they still are functional in calendar apps I've tested (this is the case for https://raw.githubusercontent.com/gkiar/ical-cli/master/example_calendar.ics, for example).
Is the calendar failing to import, or have you not tried because it fails validation?

Thanks for looking into this!
So I generate the .ics based on the /data/en/schedule.yaml file. You can find the template in layouts/schedule/single.ics. It only ranges through all the 'sessions' for each day.
I'll send the .ics file to you on GH. I can import it, but nothing is showing up :shrug: .

Here's the validator and the feed:
https://icalendar.org/validator.html?url=http://school.brainhackmtl.org/schedule/index.ics


New landpage

Landpage redesign, following this layout: https://www.figma.com/file/xagvNrqo7rVpc1RJCIHzCD/?node-id=145%3A1290

[x] New design
[x] Lots of CSS media querries clean up
[x] Added a Button component

@discombobulateme ~ When I switch to the dark theme, the new landing page doesn't completely switch to dark mode like before -- The white text on the light blue background is a little difficult to read. Is that something we can change?

@lysannep good catch! I forgot the dark theme o_o
Will create a version of it

@lysannep could you please kindly check it now? I created a dark mode :D


Make Gradle property "provider" related error more descriptive by displaying property name

Expected Behavior
The signingKey is non existing property
val signingKeyProperty = providers.gradleProperty("signingKey")
Error
 Cannot query the value of this provider because its property ("signingKey") has no value available.
Current Behavior (optional)
The signingKey is non existing property
val signingKeyProperty = providers.gradleProperty("signingKey")
Error
 Cannot query the value of this provider because it has no value available.
Context
I was defining a custom conventions plugin. While running the Gradle task I got this error
* Where:
Build file '/Users/igorwojda/IdeaProjects/konsist/lib/build.gradle.kts' line: 3

* What went wrong:
An exception occurred applying plugin request [id: 'local.publish']
> Failed to apply plugin 'local.publish'.
   > Cannot query the value of this provider because it has no value available.

* Try:
> Run with --info or --debug option to get more log output.
> Run with --scan to get full insights.

* Exception is:
org.gradle.api.plugins.InvalidPluginException: An exception occurred applying plugin request [id: 'local.publish']

Error complains about the provider, but it is too generec

Thank you for your interest in Gradle!
This feature request is in the backlog of the relevant team, but this area of Gradle is currently not a focus one, so it might take a while before it gets implemented.

I believe I just ran into the same issue as well and happened to find this issue - it lead me to hunt down what was missing, ultimately it seemed like nothing, but a refactor (extracting out my usages of providers.gradleProperty(key).get() into variables like val foobar = providers.gradleProperty("foobar").get()) seemed to solve it.


FileOpen Plugin no longer working

Only x64 version returning a result.

Exe is multi-platform, MSI is x64 only.


iox-roudi report error when running in docker

Required information
Operating system:
docker Ubuntu 18.04 LTS
Compiler version:
GCC 9.4
Observed result or behaviour:
when I run iox-roudi in docker, it report a error,how to fix it?
root@3818a587b62e:~# iox-roudi
2021-10-19 02:37:22.268 [ Info  ]: No config file provided and also not found at '/etc/iceoryx/roudi_co
nfig.toml'. Falling back to built-in config.
Log level set to: [Warning]
SharedMemory still there, doing an unlink of /iceoryx_mgmt
Reserving 60126248 bytes in the shared memory [/iceoryx_mgmt]
While setting the acquired shared memory to zero a fatal SIGBUS signal appeared caused by memset. The s
hared memory object with the following properties [ name = /iceoryx_mgmt, sizeInBytes = 60126248, acces
s mode = AccessMode::READ_WRITE, ownership = OwnerShip::MINE, baseAddressHint = (nil), permissions = 0
] maybe requires more memory than it is currently available in the system.

@yooouxin To answer your question I require a little bit more details:

Did you follow the https://github.com/eclipse-iceoryx/iceoryx/tree/master/iceoryx_examples/icedocker example?
How does your setup look like. Do you have only one roudi instance or are there running multiple ones in different docker containers?
Can you please run rm -rf /dev/shm/* as root and then start iox-roudi again. Does the problem persist after this? If not then the remainings of a killed roudi instance seemed to be the cause of the issue.
Could you please send the output of cat /proc/meminfo from the machine where iox-roudi fails?

It seems that your docker container does not have enough memory. If this would be the case then you may have to create a custom mempools for roudi, (see: https://github.com/eclipse-iceoryx/iceoryx/blob/master/doc/website/advanced/configuration-guide.md). But with 60Mb this seems unlikely. Another idea would be that there are running multiple roudi instances in your iceoryx docker setup when there should only run one.


Solidity linting and testing in GitHub actions

Refs: https://github.com/keep-network/keep-core/issues/1551
In this PR we are adding Solidity linting and testing to GitHub workflow actions.
Based on this commit

@Shadowfiend not sure how to remove ci/circleci: test_solidity check, since GH workflow replaces it. Any hint?

I got you.


Causer id being truncated when using ULID as primary key

Describe the bug
After changing the id column on the users table to be a ULID I cannot save activities anymore.
To Reproduce
Change the column id on users table;
Schema::create('users', function (Blueprint $table) {
    $table->ulid('id')->primary();
});

Add the LogsActivity trait on the desired class and call the delete method of the class:
$product = Product::find($id);
$product->delete();

Expected behavior
Activity to be saved normally
Versions

PHP: 8.3.12
Database: mySQL
Laravel: 11.32
Package: 2.8.4

Additional context
Exception

Illuminate \ Database \ QueryException

Stack Trace

SQLSTATE[01000]: Warning: 1265 Data truncated for column 'causer_id' at row 1

insert into
  `activity_log` (
    `log_name`,
    `properties`,
    `causer_id`,
    `causer_type`,
    `batch_uuid`,
    `event`,
    `subject_id`,
    `subject_type`,
    `description`,
    `updated_at`,
    `created_at`
  )
values
  (
    default,
    { "old": { "price": 958,
    "stock": 1,
    "status": "inactive" } },
    01jcydjykn0n1nkw3bmz5v9t5d,
    App \ Models \ User,
    ?,
    deleted,
    1,
    App \ Models \ Product,
    deleted,
    2024 -11 -18 01: 49: 55,
    2024 -11 -18 01: 49: 55
  )

The solution was to change the defaultMorphKeyType on the Illuminate\Database\Schema\Builder class;
Builder::defaultMorphKeyType('ulid');

I noticed this issue is still existent in version 4.9.1 of this package. I am running Laravel 11.33.2 and php 8.3.13.

SQLSTATE[01000]: Warning: 1265 Data truncated for column 'causer_id' at row 1 (Connection: mysql, SQL: insert into activity_log (log_name, properties, causer_id, causer_type, batch_uuid, event, subject_id, subject_type, description, updated_at, created_at) values

How can I resolve this? Thank you!

I resolved by updating published migration create_activity_log_table:
- $table->nullableMorphs('subject', 'subject');
+ $table->nullableUlidMorphs('subject', 'subject');


CFFL

CFFL

Linter check found the following problems:
The following problems have been found:
ERROR: /tmp/abs_6btpo0jdil/clone/recipe/meta.yaml:15: pip_install_args: pip install should be run with --no-deps.
ERROR: /tmp/abs_6btpo0jdil/clone/recipe/meta.yaml:20: missing_wheel: For pypi packages, wheel should be present in the host section
ERROR: /tmp/abs_6btpo0jdil/clone/recipe/meta.yaml:26: missing_pip_check: For pypi packages, pip check should be present in the test commands
WARNING: /tmp/abs_6btpo0jdil/clone/recipe/meta.yaml:33: missing_description: The recipe is missing a description
ERROR: /tmp/abs_6btpo0jdil/clone/recipe/meta.yaml:33: missing_documentation: The recipe is missing a doc_url or doc_source_url
ERROR: /tmp/abs_6btpo0jdil/clone/recipe/meta.yaml:33: missing_dev_url: The recipe is missing a dev_url
Errors were found


health status values table is broken

The table for This table describes the possible resource health status values for a log search alert rule is broken.
Changing the separator under the header row from |—|—| to |—|—|—| will fix it."

Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

ID: fd055153-8f80-2518-1902-99c2cdc9ed33
Version Independent ID: a1659d8c-d0ea-7ef7-629a-ec2ad23f8f6c
Content: Monitor the health of log search alert rules - Azure Monitor
Content Source: articles/azure-monitor/alerts/log-alert-rule-health.md
Service: azure-monitor
Sub-service: alerts
GitHub Login: @AbbyMSFT
Microsoft Alias: abbyweisberg

Duplicated with #121078

@tomo-msft We have verified and updated the document as required. The update will go live in less than 24 hours again! Thank you.


Pass arguments to compilers

My source code is written using the 6to5 compiler on Node Harmony. And to test with mocha, I need to pass the argument --blacklist=generators to the 6to5 compiler, however it doesn't seem like there's any straightforward way to do this through the mocha CLI.
This definitely doesn't work:
mocha --compilers 6to5:6to5/register --blacklist=generators

Any suggestions here?
Thanks.

Compilers got deprecated. (Currently I'm figuring out how to achieve passing a different config file to ts-node that's how I found this question)...
https://github.com/mochajs/mocha/wiki/compilers-deprecation


[bug] Unable to create new project

Describe the bug
this is create
yarn create tauri-app
success Saved lockfile.
success Saved 1 new dependency.
info Direct dependencies
└─<EMAIL_ADDRESS>info All dependencies
└─<EMAIL_ADDRESS>Done in 5.30s.

Updating "package.json"
Running "tauri init"
yarn run v1.22.10
$ tauri init --app-name tauri-app --window-title "Tauri App" --dist-dir ../build --dev-path http://localhost:3000 --ci
Downloading Rust CLI...
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
Error with command: yarn
Error: Error: Command failed with exit code 1: yarn tauri init --app-name tauri-app --window-title Tauri App --dist-dir ../build --dev-path http://localhost:3000 --ci
at C:\Users\Administrator\AppData\Local\Yarn\Data\global\node_modules\create-tauri-app\dist\index.js:63:15
at Generator.throw ()
at rejected (C:\Users\Administrator\AppData\Local\Yarn\Data\global\node_modules\create-tauri-app\dist\index.js:40:65)
at processTicksAndRejections (node:internal/process/task_queues:96:5)
Done in 155.34s.

this is start
yarn tauri dev
yarn run v1.22.10
$ tauri dev
app:spawn Running<EMAIL_ADDRESS>tauri dev" +0ms
thread 'main' panicked at 'Couldn't recognize the current folder as a Tauri project.', src\helpers\app_paths.rs:29:3
note: run with RUST_BACKTRACE=1 environment variable to display a backtrace
app:spawn Command<EMAIL_ADDRESS>failed with exit code: 101 +1ms
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
Reproduction
No response
Expected behavior
No response
Platform and versions
yarn run v1.22.10
$ tauri info
 app:spawn Running<EMAIL_ADDRESS>tauri info" +0ms

Operating System - Windows, version 10.0.18362 X64
Webview2 - 97.0.1072.69

Node.js environment
  Node.js - 17.4.0
  @tauri-apps/cli - 1.0.0-beta.10

Global packages
  npm - 8.3.1
  yarn - 1.22.10

Rust environment
  rustc - 1.58.1
  cargo - 1.58.0

Done in 2.65s.

Stack trace
No response
Additional context
command_history.txt

did you try running it again? it seems that it failed to download the prebuilt cli when doing yarn create tauri-app but suceeded when doing yarn tauri info

thanks. i have solved it  by #3088
cargo install tauri-cli --git https://github.com/tauri-apps/tauri

I will close it then.


Do you plan to implement a fitBounds method?To zoom out to show all current markers.

I think this is a callback of an event, and it should not be a part of directive.
We still can have that callback(fitToBounds) function registered into a directive, however it won’t be called automatically
The implementation will look like this
<map .. on-zoom-changed=“fitToBounds()” ></map>
If you have a good example of fitToBounds function, please let me know.
Allen

On Jan 18, 2015, at 9:00 AM, Naume<EMAIL_ADDRESS>wrote:
—
Reply to this email directly or view it on GitHub https://github.com/allenhwkim/angularjs-google-maps/issues/130.


flux private registry instructions are wrong.

On the quay setup, "Launching and Configuring Flux", step 5, it says to go View Credentials then Docker Login, but instead of Docker Login it should be Docker Configuration, then </> View something-here-i-dont-know-what.json, to get the base64-encoded auth value.

thanks @paulbellamy will fix this ASAP.

updated via 686e2e1a66104aaf9ab31e385e3edb7d57ec4904


Dremio: Unified Analytics Platform

About
OSS

Dremio - the missing link in modern data.
Dremio enables organizations to unlock the value of their data.

Commercial

The Unified Lakehouse Platform for Self-Service Analytics and AI.
Dremio provides the fastest SQL engine with the best price-performance for Apache Iceberg, an Apache Iceberg catalog and Lakehouse Management service for next-gen dataops, and hybrid cloud deployment flexibility.

References

https://www.dremio.com/
https://github.com/dremio/dremio-oss
https://docs.dremio.com/
https://github.com/rongfengliang/cratedb-dremio-connector

/cc @hlcianfagna, @karynzv, @hammerhead

Search

datastore/src/main/protobuf/search_types.proto

Lucene Index

datastore/indexed/LuceneSearchIndex.java
datastore/indexed/LocalIndexedStore.java
datastore/indexed/LuceneQueryConverter.java

Remote Store

datastore/src/main/protobuf/remote_datastore.proto
datastore/src/main/java/com/dremio/datastore/RemoteKVStore.java

MongoDB, Elasticsearch, Dataplane

plugins/mongo/MongoStoragePluginConfig.java
elasticsearch/src/main/proto/elastic.proto
dataplane/store/DataplanePlugin.java

Dremio's documentation about its distributed storage subsystem also sparked my interest.

https://docs.dremio.com/current/get-started/cluster-deployments/architecture/distributed-storage/
https://docs.dremio.com/current/get-started/cluster-deployments/customizing-configuration/dremio-conf/dist-store-config/

There is this community connector https://github.com/rongfengliang/cratedb-dremio-connector/tree/master

Problem
When trying to build https://github.com/dremio/dremio-oss, this error is raised:
mvn clean install -DskipTests

[ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.12.1:compile (default-compile)
        on project errorprone-dremio: Compilation failure
[ERROR] [options] system modules path not set in conjunction with -source 11

NB: Isn't errorprone-dremio a bit too much of a stretch into self-fulfilling prophecy?
Details
Pretty old, but also happens on Maven 3.9.8, according to @karynzv.
$ mvn --version
Apache Maven 3.8.6 (84538c9988a25aec085021c365c560670ad80f63)
Maven home: /usr/local/Cellar/maven/3.8.6/libexec
Java version: 19.0.1, vendor: Homebrew, runtime: /usr/local/Cellar/openjdk/19.0.1/libexec/openjdk.jdk/Contents/Home
Default locale: en_GB, platform encoding: UTF-8
OS name: "mac os x", version: "10.15.7", arch: "x86_64", family: "mac"

[ERROR] [options] system modules path not set in conjunction with -source 11

Maybe related: https://github.com/google/error-prone/issues/3803

Adding -Derrorprone.skip makes the build progress further. At BUILD FAILURE with -Ddremio.oss-only, we also picked up two more build options.
mvn clean install -DskipTests -Derrorprone.skip -Ddremio.oss-only=true -Dlicense.skip=true -e

Problem
[ERROR] Failed to execute goal com.diffplug.spotless:spotless-maven-plugin:2.43.0:check (spotless-check) on project dremio-sabot-kernel: Unable to check file /Users/amo/dev/foss/dremio-oss/sabot/kernel/src/main/java/com/dremio/sabot/op/join/merge/MergeJoinComparatorTemplate.java: com.google.googlejavaformat.java.FormatterException: 215:10: error: invalid use of a restricted identifier 'yield'

@karynzv started to look into skipping the Dremio build, use its OCI image instead, trying to build and pluck the CrateDB connector into it. Thanks!

Let me document what I've done to test the community connector:
1 - Run a Dremio docker as documented here (https://docs.dremio.com/current/get-started/docker-quickstart/)
2 - Build the community connector but removed the problematic test files in src/test/java/com/dremio/ , I personally haven't tried to fix it (https://github.com/rongfengliang/cratedb-dremio-connector)
3 - Move the resulting .jar file to the docker jars/3rdparty folder and restart docker as described here
4 - Add a new source now choosing the CRATEDB option and configure with your cluster info access
5 - In Dremio, query a VIEW as SELECT * FROM VIEW_NAME, which will give an error
6 - Check in CrateDB for the queries run by Dremio with SELECT * from sys.jobs_log WHERE username = <DREMIO_USER>

Instead of using a specific connector, there the option to query CrateDB directly from Dremio as documented here. So, by using the default Postgres connector as explained above, use the following syntax to query CrateDB directly:
SELECT * FROM table(crate.external_query('SELECT o[''it''] FROM doc.test_view;'))

Further details on the syntax and use here

Hi. Thanks a stack for your reports, both how to set up a development sandbox for the community connector, and for educating us that the external queries connector works well.

Shall we document this fact by adding an item about Dremio to crate-clients-tools and cratedb-guide?

What's next?

These external queries, so called because they are passed by and run outside of Dremio.

Is it still applicable to continue working on fixing the native connector for CrateDB, because this is one major detail what Dremio is about, running the queries inside Dremio's core engine, and not by-passing it, in order to combine multiple data sources by using its federation layer?


License

Great work!! missing a license file
MIT license?

Thanks for you reminding. I may tried to add one later.

Did you decide on a license?

@holestine @aleshem Thanks. I have added one.


[WIP] Refactor mRNA module

The purpose of the existing mrna.primary function is to select a representative mRNA for each protein-coding gene, and discard all others. This pull request is intended to support an additional, more generic filter that selects a single representative transcript for each gene. It's impossible to anticipate every possible contingency, so the new function will be very conservative and strict and will complain loudly if it is uncertain about the "right" way to handle a particular gene.
Renaming the mRNA module to transcript to reflect its new and broader scope.

[ ] Full test coverage? Any additional tests that could easily be added?
[ ] API documentation up-to-date? Docstring examples?
[ ] Is the CHANGELOG up-to-date?

Codecov Report

Merging #60 into master will not change coverage.
The diff coverage is 100%.

@@          Coverage Diff          @@
##           master    #60   +/-   ##
=====================================
  Coverage     100%   100%
=====================================
  Files          17     17
  Lines         950    950
  Branches      224    224
=====================================
  Hits          950    950

Impacted Files
Coverage Δ

tag/cli/pmrna.py
100% <100%> (ø)
:arrow_up:

tag/transcript.py
100% <100%> (ø)

tag/__init__.py
100% <100%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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


Bug

Version
3.0.9 (4d8d5d6)
Seed
R720-XE7E-ZJNH70MZ9Y00HL27BVR4VYZZFY3XVZZZKPY
Scenario
RE 2 (Claire A)
Player Character
Piers
What happened?
After the initial area, it brings you to a room where the three new exits are all locked off.

This seed is for Claire B not Claire A.


[CAMEL-11141] Add support for VPC instances

Nice :-) I will review and merge tomorrow. Many thanks @tdiesler :-)

Thanks @tdiesler the PR has been merged. Can you close this?


update docs/

available at http://mxnet.dmlc.ml
compile with cd docs; make html
@tqchen got a bunch of errors for the python documents
/home/muli/work/mxnet/docs/packages/python/io.md:: WARNING: Pygments lexer name u'eval_rst' is not known

and no cpp and scala documents yet.

@pluskid do you think it's possible to provide a script such as
git clone mxnet.jl
cp mxnet.jl/doc/*.md docs/packages/julia/
make html

so the julia documents can be also viewed at
http://mxnet.dmlc.ml/packages/julia/index.html

You will need recommonmark parser on my private fork as markdown parser。
refer to the old doc configuration script
On Sat, Mar 19, 2016 at 5:44 PM Mu Li<EMAIL_ADDRESS>wrote:

@pluskid https://github.com/pluskid do you think it's possible to
provide a script such as
git clone mxnet.jl
cp mxnet.jl/doc/*.md docs/packages/julia/
make html
so the julia documents can be also viewed at
http://mxnet.dmlc.ml/packages/julia/index.html
—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
https://github.com/dmlc/mxnet/pull/1670#issuecomment-198816219

already included https://github.com/dmlc/mxnet/blob/master/docs/conf.py#L26
On Sat, Mar 19, 2016 at 8:47 PM, Tianqi Chen<EMAIL_ADDRESS>wrote:

You will need recommonmark parser on my private fork as markdown parser。
refer to the old doc configuration script
On Sat, Mar 19, 2016 at 5:44 PM Mu Li<EMAIL_ADDRESS>wrote:

@pluskid https://github.com/pluskid do you think it's possible to
provide a script such as
git clone mxnet.jl
cp mxnet.jl/doc/*.md docs/packages/julia/
make html
so the julia documents can be also viewed at
http://mxnet.dmlc.ml/packages/julia/index.html
—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
https://github.com/dmlc/mxnet/pull/1670#issuecomment-198816219

—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub
https://github.com/dmlc/mxnet/pull/1670#issuecomment-198816334

Also need to add Autostructify as transformer. See last lines of the
original conf
On Sat, Mar 19, 2016 at 5:50 PM Mu Li<EMAIL_ADDRESS>wrote:

already included
https://github.com/dmlc/mxnet/blob/master/docs/conf.py#L26
On Sat, Mar 19, 2016 at 8:47 PM, Tianqi Chen<EMAIL_ADDRESS>wrote:

You will need recommonmark parser on my private fork as markdown parser。
refer to the old doc configuration script
On Sat, Mar 19, 2016 at 5:44 PM Mu Li<EMAIL_ADDRESS>wrote:

@pluskid https://github.com/pluskid do you think it's possible to
provide a script such as
git clone mxnet.jl
cp mxnet.jl/doc/*.md docs/packages/julia/
make html
so the julia documents can be also viewed at
http://mxnet.dmlc.ml/packages/julia/index.html
—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
https://github.com/dmlc/mxnet/pull/1670#issuecomment-198816219

—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub
https://github.com/dmlc/mxnet/pull/1670#issuecomment-198816334

—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
https://github.com/dmlc/mxnet/pull/1670#issuecomment-198816460

fixed, see http://mxnet.dmlc.ml/packages/python/symbol.html

seems to be good

please retrigger the build after the lint on cu is merged


Where does init.db in sqlserver.bicep deployment script come from?

[ ] Make sure you've installed the latest version using instructions in the wiki

Output from azd version
Run azd version and copy and paste the output here: Bicep CLI version 0.12.40 (41892bd0fb)
Describe the bug
Looking for how the db schema is being deployed.
To Reproduce
Cannot find the initDb.sql that is being called.
Expected behavior
Instructions on how the db schema is deployed in the README. Also how to modify it.
Environment
Information on your environment:
* Language name and version: https://github.com/Azure-Samples/todo-csharp-sql
* IDE and version : VS Code
Additional context
I'm assuming its baked into the image?

Thanks, I learned how to use multiline cat today, thanks for the clear explatnation!


Revert "Add optional effective_caller_id parameter to vtgate_client.py."

This reverts commit 0b77390fbc41b356dd34fb9b8b3428444fa05a68.
Reason: Broke internal users.

I think @dumbunny just need to include his stubby changes to fix this. So I recommend @dumbunny to do the import, that will fix it

@guokeno0
I've talked to @dumbunny. He'll make the internal changes first and then merge the open-source changes.
To unblock current imports, I'll therefore revert his changes in this PR.
In general, we should always aim for states where we don't block other people from merging changes.

@michael-berlin you could delete these changes while doing import, an explicit revert is not quite necessary. I don't see a urgent to import at this time.

I didn't do this for multiple reasons:

Some changes from Dean got through without explicit review. So we fix that by reverting them.
It's difficult for the current person who does the import to know which changes have to be reverted.
Requiring to re-apply the changes to every import will make future imports more cumbersome. In general, I prefer fast reverts over forward fixes to unblock people. In addition, it makes life for the person easier who is supposed to fix it: They don't have to rush the fix and can test it intensively first.

I see, then it totally makes sense. I agree we need to be conscious about changes and may break internal code base. I usually send out an email saying that I will do a non-trivial change and let people do their imports first.


failed to run some FPGA samples

Describe the bug
I can run  dace/samples/fpga/rtl/fladd.py without issues but failed in running other rtl examples. Here is the error log:
python dace/samples/fpga/rtl/pipeline.py

Traceback (most recent call last):
  File "/home/<user>/Workspace/dace/pipeline.py", line 164, in <module>
    sdfg(A=a, B=b, N=N)
  File "/home/<user>/Applications/miniconda3/envs/dace/lib/python3.11/site-packages/dace/sdfg/sdfg.py", line 2342, in __call__
    binaryobj = sdfg.compile()
                ^^^^^^^^^^^^^^
  File "/home/<user>/Applications/miniconda3/envs/dace/lib/python3.11/site-packages/dace/sdfg/sdfg.py", line 2254, in compile
    program_objects = codegen.generate_code(sdfg, validate=validate)
                      ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/<user>/Applications/miniconda3/envs/dace/lib/python3.11/site-packages/dace/codegen/codegen.py", line 231, in genera
te_code
    (global_code, frame_code, used_targets, used_environments) = frame.generate_code(sdfg, None)
                                                                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/<user>/Applications/miniconda3/envs/dace/lib/python3.11/site-packages/dace/codegen/targets/framecode.py", line 831,
 in generate_code
    states_generated = self.generate_states(sdfg, global_stream, callsite_stream)
                       ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/<user>/Applications/miniconda3/envs/dace/lib/python3.11/site-packages/dace/codegen/targets/framecode.py", line 408,
 in generate_states
    callsite_stream.write(cft.as_cpp(self, sdfg.symbols), sdfg)
                          ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/<user>/Applications/miniconda3/envs/dace/lib/python3.11/site-packages/dace/codegen/control_flow.py", line 217, in a
s_cpp
    expr += elem.as_cpp(codegen, symbols)
            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/<user>/Applications/miniconda3/envs/dace/lib/python3.11/site-packages/dace/codegen/control_flow.py", line 129, in a
s_cpp
    expr += self.dispatch_state(self.state)
            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/<user>/Applications/miniconda3/envs/dace/lib/python3.11/site-packages/dace/codegen/targets/framecode.py", line 385,
 in dispatch_state
    self._dispatcher.dispatch_state(sdfg, state, global_stream, stream)
  File "/home/<user>/Applications/miniconda3/envs/dace/lib/python3.11/site-packages/dace/codegen/dispatcher.py", line 354, in dis
patch_state
    disp.generate_state(sdfg, state, function_stream, callsite_stream)
  File "/home/<user>/Applications/miniconda3/envs/dace/lib/python3.11/site-packages/dace/codegen/targets/fpga.py", line 637, in g
enerate_state
    self.generate_kernel(sdfg, state, kernel_name, single_sgs, function_stream, callsite_stream,
  File "/home/<user>/Applications/miniconda3/envs/dace/lib/python3.11/site-packages/dace/codegen/targets/fpga.py", line 2263, in
generate_kernel
self.generate_kernel_internal(sdfg, state, kernel_name, predecessors, subgraphs, kernel_stream,
  File "/home/<user>/Applications/miniconda3/envs/dace/lib/python3.11/site-packages/dace/codegen/targets/xilinx.py", line 1094, in generate_kernel_internal
    self.generate_modules(sdfg, state, kernel_name, subgraphs, subgraph_parameters, module_stream, entry_stream,
  File "/home/<user>/Applications/miniconda3/envs/dace/lib/python3.11/site-packages/dace/codegen/targets/fpga.py", line 2316, in generate_modules
    self.generate_module(sdfg, state, kernel_name, module_name, subgraph, subgraph_parameters[subgraph],
  File "/home/<user>/Applications/miniconda3/envs/dace/lib/python3.11/site-packages/dace/codegen/targets/xilinx.py", line 823, in generate_module
    self._dispatcher.dispatch_subgraph(sdfg,
  File "/home/<user>/Applications/miniconda3/envs/dace/lib/python3.11/site-packages/dace/codegen/dispatcher.py", line 393, in dispatch_subgraph
    self.dispatch_node(sdfg, dfg, state_id, v, function_stream, callsite_stream)
  File "/home/<user>/Applications/miniconda3/envs/dace/lib/python3.11/site-packages/dace/codegen/dispatcher.py", line 420, in dispatch_node
    disp.generate_node(sdfg, dfg, state_id, node, function_stream, callsite_stream)
  File "/home/<user>/Applications/miniconda3/envs/dace/lib/python3.11/site-packages/dace/codegen/targets/rtl.py", line 64, in generate_node
    self.dispatcher.dispatch_copy(src_node, node, edge, sdfg, dfg, state_id, function_stream,
  File "/home/<user>/Applications/miniconda3/envs/dace/lib/python3.11/site-packages/dace/codegen/dispatcher.py", line 562, in dispatch_copy
    target.copy_memory(sdfg, dfg, state_id, src_node, dst_node, edge, function_stream, output_stream)
  File "/home/<user>/Applications/miniconda3/envs/dace/lib/python3.11/site-packages/dace/codegen/targets/rtl.py", line 110, in copy_memory
    callsite_stream.write(line)
                          ^^^^
UnboundLocalError: cannot access local variable 'line' where it is not associated with a value

note that "line" is possibly unbound in dace/codegen/targets/rtl.py:110
Desktop (please complete the following information):

OS: Ubuntu 20.04.6 LTS x86_64
Dace: Version: 0.14.4

Anything I missed?

Hi @remifan ! You were right, some of the RTL samples weren't set up properly, resulting in them not using the workflow for which they were intended, which led to the error you encountered. After #1403 this shouldn't be the case anymore, and each sample should run as intended.
 And do say if you encounter any more problems. :)

Thanks a lot for the fixes, the examples are working now


cells.resize() invalidates the pointer to the current cell

The resize Operation at https://github.com/exafmm/exafmm/blob/4a884e63af87f736a2545588b1137461dda840eb/3d/build_tree.h#L66
can change the total size of the cells vector, which invalidates all references to elements from the vector, as created at
https://github.com/exafmm/exafmm/blob/4a884e63af87f736a2545588b1137461dda840eb/3d/build_tree.h#L67
I will look into it tomorrow, but possibly the easiest way to fix it is to replace the Cell * cell parameter by size_t cell_index and use cells[cell_index] everywhere, as it is probably hard to tell how much elements to reserve before the recursion.

The reserve() function is used outside of this function so that reallocation does not occur. I have experimented with many different designs and this seems to be the cleanest implementation for a dynamic allocation when the vector size is not known a priori.

I thought so, but access (just assigning it to a variable) to cell->numChilds just before works and just after the line it produces a segfault. I will debug it tomorrow.

I think I see the problem (I cannot test until tomorrow):
You reserve N cells
https://github.com/exafmm/exafmm/blob/4a884e63af87f736a2545588b1137461dda840eb/3d/build_tree.h#L90
And if I am not mistaken, you create O(N log N) cells in the tree. This works with a big enough NCRIT fine if N is not too big. I currently use NCRIT=1 while integrating the library, so I hit the limit of the vector during resize.

exaFMM is not meant to be used for NCRIT=1. You may see other problems if you use NCRIT=1. By the way, a tree with 0(N) leafs still has order O(N) cells. This is because the number of cells decreases exponentially as you go up the tree. It's basically a geometric series. For an octree with NCRIT=1 you may have up to N8/7 cells. For a binary tree you will have N3/2. For an extremely non-uniform distribution the number might increase slightly more. In any case cells.reserve(2*bodies.size()) should be safe.

FMM achieves O(N) complexity only when the P2P kernel is balanced with the M2L kernel. Decreasing NCRIT increases the M2L kernel time. This balance is affected by the order of expansion P. The default value is set to achieve the optimal time.

Thank you.
Then the problem will solve itself with a higher value. I hope you don't mind me posting this when I find such a segfault. I try only to post things which are relevant to the lib project.
Or do you prefer, when I create a fork? I am not sure if you want to maintain it as open source or merely released it with an open source licence but maintain it in your institute.

Please post any problems you find here. I usually respond quickly. You can submit a pull request when your fork is stable.

Just as Feedback: It works fine with increased NCRIT and the library works fine in my program.
For the other things I opened issues and for the windows stuff I will create pull requests when I implemented the fixes in a nice way. And I need to look at the other folders, currently I am just working in the 3d folder.


Make sure mongodb is restarted before shell commands are executed

This changes the order of the tasks executed for configuring mongodb. Make sure
mongodb is enabled and started before any shell commands are executed.
Additionally, flush handlers before executing shell commands. This makes sure
that mongodb was restarted if necessary before any shell commands are executed.
This fixes #23.

Thank you!


aeson-pretty: use Spaces with confIndent

Based on https://github.com/informatikr/aeson-pretty/blob/375afe8e/Data/Aeson/Encode/Pretty.hs#L124
Prevents the following error building Elm 0.17.1 with GHC 8.0.1:
    • No instance for (Num Json.Indent) arising from the literal ‘2’
    • In the ‘confIndent’ field of a record
      In the expression:
        Json.Config
          {Json.confIndent = 2, Json.confCompare = Json.keyOrder keys}
      In an equation for ‘config’:
          config
            = Json.Config
                {Json.confIndent = 2, Json.confCompare = Json.keyOrder keys}
            where
                keys = ["tag", ....]

That error would also be prevented by constraining aeson-pretty to a version < 0.8 in the .cabal file.

And does this PR break it with that older version?

Yes.

Then that dep should be bumped.

That's for @evancz to decide.

I said it should be bumped, not that it will be ;)

Since no one has confirmed that this code works with GHC 7.10.2 which I am using, I can't accept this PR for now. Not planning to do that kind of upgraded right now.
I have 0.7.2 of aeson-pretty, so if putting an upper bound on that package fixes it for GHC 8, I'd much rather go with that approach.

Gonna go with the constraint instead. Thanks for bring the issue up and suggesting a fix!

Guys, look at this patch https://github.com/gentoo-haskell/gentoo-haskell/blob/master/dev-lang/elm-compiler/files/elm-compiler-0.15-aeson-pretty-0.8.patch from Gentoo Haskell overlay


MB-12329: Service counselor can create partial PPM shipments

Jira ticket for this change; MB-12329 a sub-task of MB-11865
Summary
This pull request connects sub-components created in MB-12321, MB-12322, MB-12323, MB-12324, and MB-12325 into the ShipmentForm component, allowing Service Counselor users to create partial PPM shipments. Users can now add a partial PPM shipment through this form, capturing values in all of the fields in the first "page" of the form, and propagating it to the database. (Setting advance request/amount is not yet supported, as editing PPM shipments is captured in future work.)
Field validation is wired into this form (both local as well as server-side for postal codes), and new tests and stories are created for the added functionality.
Setup to Run Your Code

💻 You will need to use three separate terminals to test this locally.
Terminal 1
Start the Storybook locally.
make storybook

Terminal 2
Start the UI locally.
make office_client_run

Terminal 3
Start the Go server locally.
make server_run

Additional steps

In Storybook, view the "PPM Shipment" story inside of Office Components -> Forms -> ShipmentForm. Validate that the component correctly replicates the design.
Login to the office application locally as a Service Counselor user, and view on any move in a state that can have shipments added to it. In the "Add new shipment" dropdown in the top right for that move, select "PPM."
On the add PPM page, validate that all fields display correctly, and behave correctly.
Validate that ZIP code validation takes place -- invalid and malformatted ZIP codes should display a validation error.
Validate that the "Use current ZIP" and "Use ZIP for new duty location" check boxes pull the postal codes from the origin and destination duty locations for that move.
Validate that estimated PPM weight displays an error message if the user enters a value greater than the customer's weight allowance.
Validate that pro-gear and spouse pro-gear weights display an error message if the user enters a value greater than the maximum for those fields.
With valid input for all required fields, validate that the "Save and Continue" button is enabled. Click it.
Validate that you're taken a second page displaying incentive and advance information, and that the URL changed to the "edit" route, including the new (server-generated) shipment ID.
Click the browser's "back" button twice to return to the move page. Validate that the new partial PPM correctly displays as a shipment.
Click the "Edit Shipment" button for it and validate that the values you've entered previously display to the user.

Verification Steps for Author
These are to be checked by the author.

[ ] Request review from a member of a different team.
[ ] Have the Jira acceptance criteria been met for this change?

Verification Steps for Reviewers
These are to be checked by a reviewer.

Frontend

[ ] User facing changes have been reviewed by design.
[ ] There are no aXe warnings for UI.
[ ] This works in Supported Browsers and their phone views (Chrome, Firefox, IE, Edge).
[ ] There are no new console errors in the browser devtools
[ ] There are no new console errors in the test output
[ ] If this PR adds a new component to Storybook, it ensures the component is fully responsive, OR if it is intentionally not, a wrapping div using the officeApp class or custom min-width styling is used to hide any states the would not be visible to the user.

Screenshots

Create PPM shipment form, blank
Create PPM shipment form, values entered

Messages

:book:
:link: MB-12329

  Generated by :no_entry_sign: dangerJS against ba49e88f6736b9741baafe48c7f82c1b6c4f3bba

@kylehilltruss validation on the fields/issues I called our previously looks good!
Also roger that on width of fields to accommodate for "optional tag", the slight offset we have now works well enough.
Tho for some reason I'm unable to save and continue. I fill in the fields, there are no field level errors that I see, I hit save & continue, nothing happens except the button disabling, then I scroll up to see the vague "An error occurred A server error occurred adding the shipment" error. I tried playing around with the data I'm entering but that doesn't seem to unblock me.
Good news is I can cancel and it takes me back to move details.


Bug: Cannot select button more than once

If you select a button once, you cannot select it again unless you select a different one first. This comes into play when navigating deeper into the app and you want to go back to the beginning without using the back button.

maybe need a "up"-sytle back button, like android

What button are we talking about? Is this BROKEN behavior (are you doing the right thing labeling this as a bug) or is this an enhancement of the existing functionality?

Closing for lack of info.


Bump proxy SHA

@jwendell: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

release-notes_istio_release-1.7
1817e3b8e448aeae59b0d5e394ba8cc6d675acab
link
/test release-notes_istio_release-1.7

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@jwendell: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

release-notes_istio_release-1.7
1817e3b8e448aeae59b0d5e394ba8cc6d675acab
link
/test release-notes_istio_release-1.7

unit-tests_istio_release-1.7
1817e3b8e448aeae59b0d5e394ba8cc6d675acab
link
/test unit-tests_istio_release-1.7

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/retest


Should not animate the items which are already animated

Is there any method that Should not animate the items which are already animated

I having the same issue, I want to apply slideInUpAnimation only once.

@JgdshSeerm  @atabouraya are you discuss AnimationAdapter.setFirstOnly(true);?

Nop, AnimationAdapter.setFirstOnly(true or false); doesn't work, they are talking about how repeat animation with elements that were animated


pubnote search: journal_name together with the journal volume

Currently searches like Phys. Rev. D95 (2017) 123002 don't work because D is omitted by GROBID:
$ curl 'https://grobid.inspirebeta.net/api/processCitation' --data-raw 'citations=Phys. Rev. D95 (2017) 123002'

<biblStruct>
	<analytic>
		<title/>
	</analytic>
	<monogr>
		<title level="j">Phys. Rev</title>
		<imprint>
			<biblScope unit="volume">95</biblScope>
			<biblScope unit="page">123002</biblScope>
			<date type="published" when="2017" />
		</imprint>
	</monogr>
</biblStruct>

{
   'reference': {
       'publication_info': {
        'journal_volume': '95',
        'journal_title': 'Phys. Rev',
        'year': 2017,
        'page_start': '123002'
       }
    }
}

Currently inspire-matcher doesn't exact match on journal_title, instead we have to do a prefix search on journal_title i.e. Phys. Rev should match Phys. Rev D.
Acceptance:
The following search should work:

[ ] Phys. Rev. D95 (2017) 123002
[ ] Eur Phys J C73 2531
[ ] M. Dine, W. Fischler and M. Srednicki, Phys. Lett. B104 (1981) 19

IRL we decided to increase the matched records to 5 instead of 1 https://github.com/inspirehep/inspirehep/blob/master/backend/inspirehep/matcher/api.py#L61

Reopening because the change on https://github.com/inspirehep/inspirehep/blob/6b321d50b5aae129630088b3886f6d9f07fc1140/backend/inspirehep/matcher/api.py#L61 doesn't make sense:

it allows up to five matches (so if the ref without journal letter is ambiguous, you'lle still get results), but only returns the first one which defeats the purpose, as there's no reason for the first one to be the correct one
it also modifies the actual reference matcher (which we'll use later with refextract) to allow ambiguous matches, which is probably not what we want.


Provide no_std support

I will need to either bump the minimum rust version from 1.6 to 1.36 or introduce a feature to switch between std and nostd, let me know which way you wish to go.


Event format has changed

Hi -- I attempted to use this library yesterday and wanted to point out some issues that I encountered. These were both easy fixes and I like the lightweight nature of this library. I hesitated to open a PR or fork because I saw this was updated as recently as yesterday so figured it must be working for somebody.

This line causes an issue when body is set to None on the event (can't call encode None on line 69)

body_b = body.encode() if body else b'' # will do the trick on 69

The event structure seems to have changed in other ways too.

rawPath is now path
rawQueryString may not be present
request context no longer has an http key, now has an identity key
headers are not called multiValueHeaders
there are a lot of these type of changes, I won't enumerate them all

If others are running into the same issue I'll open a PR with the changes; if some are still using this successfully (perhaps for older versions of API v2?) I can open a PR that supports looking for keys in both formats.

are you sure you're not using the v1 format?

are you sure you're not using the v1 format?

yeah you're using the v1 format of api gateway (which has body: null) -- note that this library is called "api-gateway-v2" and intentionally does not use the v1 format

yeah you're using the v1 format of api gateway (which has body: null) -- note that this library is called "api-gateway-v2" and intentionally does not use the v1 format

from the aws docs here's a sample v1 request and here's a sample v2 request

from the aws docs here's a sample v1 request and here's a sample v2 request

lol. oops. I guess I'll fix that

lol. oops. I guess I'll fix that

if you're working with terraform, there's an example included in this repository: https://github.com/asottile/api-gateway-v2-to-wsgi/blob/master/testing/example/tf/lambda_sample_app.tf
otherwise you can probably map this to whatever system and/or the console

if you're working with terraform, there's an example included in this repository: https://github.com/asottile/api-gateway-v2-to-wsgi/blob/master/testing/example/tf/lambda_sample_app.tf
otherwise you can probably map this to whatever system and/or the console


Add docker-compose.yml to simplify local doc development

While doing docs development, I found it easier to run everything via containers to prevent the need to setup virtualenv/python on my machine. So, figured I'd offer it back in case it might be useful and help lower the barrier for someone else!

Ah thank you @mikesir87 - this is a good idea!

Thanks for the contribution @mikesir87!


Implement highlighting for NM reserved words

Examples of reserved words:
ID, DV, AMT, TIME, EVID, MDV, etc

Added


where should I put the downloaded weight file?

directly download the 'imagenet' weight file is extremely slow for my network condition. but i have downloaded it from other sources, but can i just put it into the work paths for the packages to load the  weight automatically? and where are the work path for weight file?

could u please help on how to load checkpoint or weight for models?

found the parameter weights – optional, path to model weights. solved my problem.

found the parameter weights – optional, path to model weights. solved my problem.

how do you solve this problem ?


FileServlet is throwing uncaught exceptions for not found files

Should catch and log this condition rather than just throwing exception. Maybe also return a 404.

Assigned to @nick-prat


[Volunteer]

Volunteer help
Support mqtt protocol.

Hi, do we have the plan to support storage message ?

done


[QUERY] Seeing Service Bus Lock Exceptions for Session Enabled Service Bus Subscriptions

Library name and version
Microsoft.Azure.ServiceBus
Query/Question
Hi team,
In our prod instances, we are seeing the following exception coming from Service bus.
"The session lock has expired on the MessageSession. Accept a new MessageSession"
Ours is a session enabled service bus subscription, and I was referring to this post https://github.com/Azure/azure-sdk-for-net/issues/19662, where one of the suggestions was to use sessionHandlerOptions (pls check last reply on that post).
While registering the session handler we make sure to use sessionHandlerOptions for a session enabled service bus subscription.

Also verified that autocomplete is set to false.
Could you point to what could be causing this error?
Environment
No response

@fazal60 , Thanks for reporting. I am looking into this issue, I will get back to you once I have an update

@fazal60 , Thanks for the follow up. I will provide an update tomorrow

@fazal60 , As mentioned in this issue This happens when the session lock is expired and needs to be reacquired.
You are using the sessionhandleroptions class to renew the lock. Are you getting the lock expired exception even after renewing the session lock? What is the timeout value that you have set.
By default, the messagewait timeout is 1 minute and the autorenew duration is 5 minutes while using the Sessionhandleroptions class

@MughundhanRaveendran-MSFT I checked in our code and it appears the MessageWaitTimeout value is 30 seconds and the Autorenew duration is 5 minutes. Does this make a difference?

@MughundhanRaveendran-MSFT what are the implications if the timeout is less than 1 min. Is this problem caused due to this?

@fazal60 , Apologies for the delay in response. 1 minute is the default timeout and I am not sure if the issue is caused due to setting the value to 30 seconds. You can try to set the MessageWaitTimeout value to 1 minute to see if the frequency of the issue is decreased. Also I would like to know the answer for the below query
Are you getting the lock expired exception even after renewing the session lock?

"Are you getting the lock expired exception even after renewing the session lock?"
Yes @MughundhanRaveendran-MSFT from the logs thats what seems to happen

@shankarsama @DorothySun216 Any updates on this?

I get the same issue when using an azure function app v5 where the function app itself is supposed to auto renew the message locks, it seems like whatever the message lock is on the topic/subscription is the max, it doesnt seem to auto renew when its a session based queue.


Copy/Paste Segments

Copying and pasting - if you select several joined items (sharing points) as a group, copy and paste them elsewhere, the pasted items are no longer connected and can be moved individually. I guess this will create an error of more than one node in the same place unless things are reconnected.

Yeah I can see how this would be an issue. I'm thinking if a user copies a bunch of stacked up nodes with uninteresting tags, we should only paste a single node.

On 12 April 2015 at 04:26, Bryan Housel<EMAIL_ADDRESS>wrote:

Yeah I can see how this would be an issue. I'm thinking if a user copies a
bunch of stacked up nodes with uninteresting tags, we should only paste a
single node.
—
Reply to this email directly or view it on GitHub
https://github.com/openstreetmap/iD/issues/2584#issuecomment-91977717.

Not keen on 'data loss'. Whatever's copied should be pasted as is - if
objects are joined at nodes then they should paste joined up too. That's
the issue.
--
Mike.
@millomweb https://sites.google.com/site/millomweb/index/introduction -
For all your info on Millom and South Copeland
via *the area's premier website - *
currently unavailable due to ongoing harassment of me, my family, property
& pets
T&Cs https://sites.google.com/site/pmailkeey/e-mail

Oh, I think I misunderstood...
You are saying if a user selects some points that are connected and copy/pastes them, they should stay connected as a way?
Copying this:

Should result in this:

Not this:

Is that right?

Good job you didn't change the issue number as well ;)
Yes, that's right and this (2 squares)

should paste like this:

and not like this:

i.e. shared nodes of the two squares remain shared, not as 2 separate squares with nodes in the same place but not connected.

This is out of scope for iD.

@jfirebaugh I'd agree on copying of segments beind out of scope. It is rarely required and other methods to acceive the result exist.
The original was describing a copy and paste bug which still exists and seem to be quite valid. The comments seem to be a series of misunderstandings. "Copy segments" is only what @bhousel has made out of the original issue due to misunderstanding.

Ah, I see. Thanks for clarifying.


MAINT: adds copydoc decorator

we have this pattern a lot which prevents us from using decorators as we would normally use them. I also ran into this issue with blaze where I couldn't mutate the __doc__ of an unbound method in python 2. If this change looks good, I will refactor blaze to use this too.

this looks good, can you just confirm locally that you can see the docstring as desired?

also pls add a blurb in whatsnew

What section should I put this in?

Looks like it is getting copied correctly
In [10]: print(URL.__doc__)
 Parent class for data accessed through ``URLs``

    Parameters
    ----------

    url : str
        full url to file
    chunk_size : int (default 1024)
        Size of chunks streamed into memory
    decode_unicode : bool (default False)
        If True, content will be decoded using the best available
        encoding based on the response.

     Examples
    --------

    >>> from odo import URL, CSV
    >>> u = URL(CSV)('http://foo.com/myfile.csv')

    Normally create through resource uris

    >>> data = resource('http://foo.com/myfile.csv')
    >>> data.url
    'http://foo.com/myfile.csv'
    >>> data.filename
    'myfile.csv'

What section should I put this in?

Could make a new Miscellaneous section

LGTM

I will open a PR soon on blaze that uses this new feature. That should fix that issue that we needed to revert with Node.map

awesome thanks!


Undefined offset: 0

I has get error when dumpzone.

in Cpanel.php line 343
at HandleExceptions->handleError('8', 'Undefined offset: 0', '/home/nginx/domains/xxx/public/vendor/gufy/cpanel-php/src/Gufy/CpanelPhp/Cpanel.php', '343', array('action' => 'dumpzone', 'arguments' => array('domain' => 'xxx.com'), 'host' => 'https://<IP_ADDRESS>:2087', 'client' => object(Client))) in Cpanel.php line 343

Resolve:
change
'query' => count($arguments) > 1 ? $arguments : $arguments[0],
to
'query' => $arguments,
Please check it :)

is this happen when the $arguments is null?

no, this happen when is has one item in array.

Try it again

tks guy :)

Use dev-master instead, i still haven't pushed it as a tag. :+1:

This is still a problem because the $arguments parameter of __call() is always an enumerated array containing the parameters passed to the method.
$accounts = listaccts(['searchtype'=>'domain', 'search'=>'', 'exact', 'search'=>'helloworld.com']);

This would result in the following $arguments:
array(1) {
  [0]=>
  array(3) {
    ["searchtype"]=>
    string(6) "domain"
    ["search"]=>
    string(14) "helloworld.com"
    [0]=>
    string(5) "exact"
  }
}

Which results in the following POST request:
> POST /json-api/listaccts?0%5Bsearchtype%5D=domain&0%5Bsearch%5D=helloworld.com&0%5B0%5D=exact HTTP/1.1

Hello,
This issue still not resolved. There is code like this:
include_once ('class.cpanel.php');
$cpanel = new Cpanel();

$account_info = $cpanel->callWHMApi('accountsummary',
    [
    'domain'        => $gsi['domain'],
    ]
);

if ( isset($account_info) ) {
    $result = json_decode ( $account_info, true );
    $results = $result[ 'data' ][ 'acct' ][0];
}

if ( isset($results) ) {

    $cgi_domain = $results[ 'domain' ];
    $cgi_inodes = $results[ 'inodesused' ];
    $cgi_mailboxes = $results[ 'maxpop' ];
    $cgi_mailsperhour = $results[ 'max_email_per_hour' ];
    $cgi_outgoingmail = $results[ 'outgoing_mail_suspended' ];
    $cgi_suspended = $results[ 'suspended' ];
    $cgi_suspend_reason = $results[ 'suspendreason' ];
    $cgi_ip = $results[ 'ip' ];
    $cgi_plan = $results[ 'plan' ];
    $cgi_user = $results[ 'user' ];
    $cgi_diskused = $results[ 'diskused' ];
    $cgi_maxsql = $results[ 'maxsql' ];
    $cgi_disklimit = $results[ 'diskused' ];
}

Code executed and result received, but with notice:

Notice: Undefined offset: 0

Sure, I can use "@" to supress that dirty notice, but it's not the best way...


Fix Keycloak health check in Compose

See the commit messages for details.
This will have to be rebased after #1643 was merged.
@lamppu @Etsija FYI

So, with these fixes, there is no more need to revert https://github.com/eclipse-apoapsis/ort-server/pull/1153, correct?

So, with these fixes, there is no more need to revert #1153, correct?

Yes.


Default agent

So everything seems to be working great, you've done a great job here. I'm testing this for implementation in one of my projects to start with and have plans to integrate it in my larger project if it works out. I did find one small thing. When using the library in Node, the default user-agent that is sent to the server is "undici". I would recommend setting the default to "esp-version".
It's not a big deal, it just gave me a reason to come in and give you props on a solid package.

Thanks for the kind words @andrew-d-moore :smile:
This library just let's the runtime set the default agent. I'll have to think about whether setting a custom user agent is something we wanna do.
I'm curious what node version are you on? The "undici" user-agent you are seeing is a node issue that's been fixed recently (see https://github.com/nodejs/undici/issues/2306). I just checked in v20.12.2 and v18.20.2 and the user-agent I get back is "node".
Do you think receiving "node" as the user-agent is good enough? Or would you prefer to know specifically that it's this library that is making the request?

Node 18.17.0, I updated to 22.1.0 and the problem went away. Shows node as the default user agent so it would seem as long as the version is recent this isn't a real issue.
I should report that from the browser, user-agents are showing up just fine. And they were on the 18.17.0 version as well.

Cool beans I'll close for now. We can reopen if it looks like adding a custom user-agent is a good idea.


Update index.rst

Include new file implementation_plan.md (in conjunction with pull request to add this file to General Overview page: https://github.com/mattermost/docs/pull/1783

@james-mm Thoughts on whether this belongs to the Admin's guide?

@jasonblais Good idea, we can add it as the first section in this link (https://docs.mattermost.com/guides/administrator.html), before the "Installing Mattermost" section

@james-mm Yeah, I think that looks like a good place.

This request can be closed since we will be adding this doc to the Admin guide section instead.


module

why there's no module named cnn_tf?

I am also getting error of "ModuleNotFoundError: No module named 'cnn_tf'" plase help

Same error for me

Is there anything we can do for that module error ?

cnn_tf is actually cnn_model_train.py.
we should change the cnn_tf to cnn_model_train in final.py file


Conditional JSX does not re-evaluate when state changes

When determining whether or not to display conditional JSX views, RN evaluates the condition once, and then renders views accordingly. But when I change my state's value that directly affects how the JSX conditional evaluates, the condition is not being re-evaluated. I have tried running forceUpdate() but that doesn't seem to work in RN like it does in browser-based React. Is there a work-around for this?
Is there a way to force my conditional JSX to be re-evaluated when state is updates or changed?

React does re-evaluate when state updates, you shouldn't need to run forceUpdate. There's probably a bug elsewhere in your code. I'm going to close this issue - if you have a repro app with code that shows state not updating, like on rnplay.org, then feel free to reopen or open a new one.


PowerToys Run - Percentage calculator

Description of the new feature / enhancement
Add simply possibility to calculate procentage from number for example (100-10%). In chrome it works directly in search bar

This feature will increase your work speed and will save a lot of time. I think it's very useful for different types of peoples, and yes, it's more easier and intuitive to write 100-10% instead 100-(100*10/100)
Scenario when this would be used?
In calculator plugin of PowerToys Run
Supporting information
No response

Duplicate of #13631

Thanks for your suggestion! This issue is a duplicate.
I'm linking this issue to #13631 to centralize the discussion thread, please go to that thread for discussion.
Thanks for your help to make PowerToys a better piece of software!

I think this is a dup of #13631 but not something we currently do nor the OS calculator does.  To me, i would just do 100*.9 as i've never seen that style notation personally before.


Remove unnecessary analysis input file update

If a job fails and is respawned, an analysis will attempt to update the job id to the most recently spawned job. If that update is required, old code would also update the analysis's input files to match the new job's inputs. Code prevents a change in inputs from one job attempt to the next, so this is unnecessary. It was causing issues in situations where inputs did not exist for a job, so it easier to just remove it.
Review Checklist

Tests were added to cover all code changes
Documentation was added / updated
Code and tests follow standards in CONTRIBUTING.md

Codecov Report

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

@@            Coverage Diff             @@
##           master    #1067      +/-   ##
==========================================
- Coverage   91.19%   91.18%   -0.02%
==========================================
  Files          50       50
  Lines        6931     6922       -9
==========================================
- Hits         6321     6312       -9
  Misses        610      610