[Bug]: Issue while importing Stremlit apps

Terraform CLI Version
1.9.4
Terraform Provider Version
0.94.1
Terraform Configuration
resource "snowflake_streamlit" "streamlit" {
  database  = "DVS"
  schema    = "UTILITY"
  name      = "E5O3M_9PCG5IWS45"
  stage     = "DVS.UTILITY.E5O3M_9PCG5IWS45"
  main_file = "/streamlit_app.py"
  query_warehouse              = "ADHOC_M"
  title = "TOPICS_TEST"
}

Category
category:resource
Object type(s)
No response
Expected Behavior
We would expect the resource to be imported and tracked in terraform
Actual Behavior
when we run a import command terraform import snowflake_streamlit.streamlit E5O3M_9PCG5IWS45  we see an plugin error
Steps to Reproduce
RUN terraform import snowflake_streamlit.streamlit E5O3M_9PCG5IWS45
How much impact is this issue causing?
Medium
Logs
No response
Additional Information
2024-08-28T10:32:51.156+0530 [ERROR] provider: plugin process exited: plugin=.terraform/providers/registry.terraform.io/snowflake-labs/snowflake/0.94.1/darwin_arm64/terraform-provider-snowflake_v0.94.1 id=70007 error="exit status 2"
2024-08-28T10:32:51.157+0530 [ERROR] plugin6.(*GRPCProvider).UpgradeResourceState: error="rpc error: code = Unavailable desc = error reading from server: EOF"
2024-08-28T10:32:51.157+0530 [ERROR] plugin6.(*GRPCProvider).UpgradeResourceState: error="rpc error: code = Unavailable desc = error reading from server: EOF"
2024-08-28T10:32:51.157+0530 [ERROR] vertex "snowflake_resource_monitor.snow_resource_monitor[\"PSDATUMDAILYFAILSAFE\"]" error: Plugin did not respond
2024-08-28T10:32:51.157+0530 [ERROR] plugin6.(*GRPCProvider).UpgradeResourceState: error="rpc error: code = Unavailable desc = error reading from server: EOF"
2024-08-28T10:32:51.157+0530 [ERROR] plugin6.(*GRPCProvider).UpgradeResourceState: error="rpc error: code = Unavailable desc = error reading from server: EOF"
2024-08-28T10:32:51.157+0530 [ERROR] plugin6.(*GRPCProvider).ImportResourceState: error="rpc error: code = Unavailable desc = error reading from server: EOF"
2024-08-28T10:32:51.157+0530 [ERROR] plugin6.(*GRPCProvider).UpgradeResourceState: error="rpc error: code = Unavailable desc = error reading from server: EOF"
2024-08-28T10:32:51.157+0530 [ERROR] plugin6.(*GRPCProvider).UpgradeResourceState: error="rpc error: code = Unavailable desc = error reading from server: EOF"
2024-08-28T10:32:51.157+0530 [ERROR] plugin6.(*GRPCProvider).UpgradeResourceState: error="rpc error: code = Unavailable desc = error reading from server: EOF"
2024-08-28T10:32:51.157+0530 [ERROR] plugin6.(*GRPCProvider).UpgradeResourceState: error="rpc error: code = Unavailable desc = error reading from server: EOF"
2024-08-28T10:32:51.157+0530 [ERROR] plugin6.(*GRPCProvider).UpgradeResourceState: error="rpc error: code = Unavailable desc = error reading from server: EOF"
2024-08-28T10:32:51.157+0530 [ERROR] vertex "snowflake_resource_monitor.snow_resource_monitor[\"PSDATUMFAILSAFE\"]" error: Plugin did not respond
2024-08-28T10:32:51.158+0530 [ERROR] vertex "snowflake_resource_monitor.snow_resource_monitor (expand)" error: Plugin did not respond
2024-08-28T10:32:51.158+0530 [ERROR] vertex "snowflake_resource_monitor.snow_resource_monitor (expand)" error: Plugin did not respond
2024-08-28T10:32:51.158+0530 [ERROR] plugin6.(*GRPCProvider).UpgradeResourceState: error="rpc error: code = Canceled desc = context canceled"
2024-08-28T10:32:51.158+0530 [ERROR] vertex "snowflake_user.snow_user[\"KAFKA_CONNECT_SERVICE_USER_PRODUCTION\"]" error: Request cancelled
2024-08-28T10:32:51.159+0530 [ERROR] plugin6.(*GRPCProvider).UpgradeResourceState: error="rpc error: code = Canceled desc = context canceled"
2024-08-28T10:32:51.159+0530 [ERROR] vertex "snowflake_database.snow_db[\"ACG_PROD_RAW\"]" error: Request cancelled
2024-08-28T10:32:51.160+0530 [ERROR] plugin6.(*GRPCProvider).UpgradeResourceState: error="rpc error: code = Canceled desc = context canceled"
2024-08-28T10:32:51.160+0530 [ERROR] vertex "snowflake_database.snow_db[\"ACG_PROD_RAW_AWS_BILLING\"]" error: Request cancelled
2024-08-28T10:32:51.160+0530 [ERROR] plugin6.(*GRPCProvider).UpgradeResourceState: error="rpc error: code = Canceled desc = context canceled"
2024-08-28T10:32:51.160+0530 [ERROR] vertex "snowflake_database.snow_db[\"ACG_PROD_STITCH\"]" error: Request cancelled
2024-08-28T10:32:51.161+0530 [ERROR] plugin6.(*GRPCProvider).UpgradeResourceState: error="rpc error: code = Canceled desc = context canceled"
2024-08-28T10:32:51.161+0530 [ERROR] vertex "snowflake_database.snow_db[\"ACG_PROD_ANALYTICS\"]" error: Request cancelled
2024-08-28T10:32:51.161+0530 [ERROR] plugin6.(*GRPCProvider).UpgradeResourceState: error="rpc error: code = Canceled desc = context canceled"
2024-08-28T10:32:51.161+0530 [ERROR] vertex "snowflake_database.snow_db[\"ACG_PROD_DE_ANALYTICS\"]" error: Request cancelled
2024-08-28T10:32:51.161+0530 [ERROR] plugin6.(*GRPCProvider).UpgradeResourceState: error="rpc error: code = Canceled desc = context canceled"
2024-08-28T10:32:51.161+0530 [ERROR] vertex "snowflake_warehouse.snow_warehouse[\"STITCH_WH\"]" error: Request cancelled
2024-08-28T10:32:51.161+0530 [ERROR] vertex "snowflake_account_role.snow_roles[\"ACCOUNTADMIN\"]" error: Plugin did not respond
2024-08-28T10:32:51.162+0530 [ERROR] plugin6.(*GRPCProvider).UpgradeResourceState: error="rpc error: code = Canceled desc = context canceled"
2024-08-28T10:32:51.162+0530 [ERROR] vertex "snowflake_database.snow_db[\"DEV\"]" error: Request cancelled
2024-08-28T10:32:51.162+0530 [ERROR] plugin6.(*GRPCProvider).UpgradeResourceState: error="rpc error: code = Canceled desc = context canceled"
2024-08-28T10:32:51.162+0530 [ERROR] vertex "snowflake_warehouse.snow_warehouse[\"SPLUNK_WH\"]" error: Request cancelled
2024-08-28T10:32:51.162+0530 [ERROR] vertex "snowflake_user.snow_user[\"ACCENTURE_NOTIFICATION_USER\"]" error: Plugin did not respond
2024-08-28T10:32:51.162+0530 [ERROR] plugin6.(*GRPCProvider).UpgradeResourceState: error="rpc error: code = Canceled desc = context canceled"
2024-08-28T10:32:51.162+0530 [ERROR] plugin6.(*GRPCProvider).UpgradeResourceState: error="rpc error: code = Canceled desc = context canceled"
2024-08-28T10:32:51.162+0530 [ERROR] vertex "snowflake_streamlit.streamlit (import id \"E5O3M_9PCG5IWS45\")" error: Plugin did not respond
2024-08-28T10:32:51.163+0530 [ERROR] vertex "snowflake_streamlit.streamlit (expand)" error: Plugin did not respond
2024-08-28T10:32:51.163+0530 [ERROR] plugin6.(*GRPCProvider).UpgradeResourceState: error="rpc error: code = Canceled desc = context canceled"
2024-08-28T10:32:51.163+0530 [ERROR] vertex "snowflake_database.snow_db[\"ACG_PROD_SEGMENT_EVENTS\"]" error: Request cancelled
2024-08-28T10:32:51.163+0530 [ERROR] plugin6.(*GRPCProvider).UpgradeResourceState: error="rpc error: code = Canceled desc = context canceled"
2024-08-28T10:32:51.163+0530 [ERROR] vertex "snowflake_warehouse.snow_warehouse[\"DYNAMIC_TABLE_TEST\"]" error: Request cancelled
2024-08-28T10:32:51.163+0530 [ERROR] plugin6.(*GRPCProvider).UpgradeResourceState: error="rpc error: code = Canceled desc = context canceled"
2024-08-28T10:32:51.163+0530 [ERROR] vertex "snowflake_user.snow_user[\"DEO_SERVICE_USER\"]" error: Plugin did not respond
2024-08-28T10:32:51.163+0530 [ERROR] plugin6.(*GRPCProvider).UpgradeResourceState: error="rpc error: code = Canceled desc = context canceled"
2024-08-28T10:32:51.163+0530 [ERROR] vertex "snowflake_database.snow_db[\"ACG_PROD_CHARGEBEE\"]" error: Request cancelled
2024-08-28T10:32:51.163+0530 [ERROR] plugin6.(*GRPCProvider).UpgradeResourceState: error="rpc error: code = Canceled desc = context canceled"
2024-08-28T10:32:51.163+0530 [ERROR] vertex "snowflake_warehouse.snow_warehouse[\"ADHOC_M\"]" error: Request cancelled
2024-08-28T10:32:51.164+0530 [ERROR] plugin6.(*GRPCProvider).UpgradeResourceState: error="rpc error: code = Canceled desc = context canceled"
2024-08-28T10:32:51.164+0530 [ERROR] vertex "snowflake_warehouse.snow_warehouse[\"DVS_STAGING_REPLICATION\"]" error: Request cancelled
2024-08-28T10:32:51.164+0530 [ERROR] vertex "snowflake_user.snow_user[\"SPLUNK_SERVICE_USER\"]" error: Plugin did not respond
2024-08-28T10:32:51.164+0530 [ERROR] vertex "snowflake_user.snow_user[\"KAFKA_CONNECT_SERVICE_USER_STAGING\"]" error: Plugin did not respond
2024-08-28T10:32:51.164+0530 [ERROR] plugin6.(*GRPCProvider).UpgradeResourceState: error="rpc error: code = Canceled desc = context canceled"
2024-08-28T10:32:51.164+0530 [ERROR] vertex "snowflake_database.snow_db[\"ACG_PROD_SUPERMETRICS\"]" error: Request cancelled
2024-08-28T10:32:51.164+0530 [ERROR] plugin6.(*GRPCProvider).UpgradeResourceState: error="rpc error: code = Canceled desc = context canceled"
2024-08-28T10:32:51.164+0530 [ERROR] vertex "snowflake_database.snow_db[\"ACG_TEST_RAW\"]" error: Request cancelled
2024-08-28T10:32:51.164+0530 [ERROR] vertex "snowflake_account_role.snow_roles[\"BREAK_GLASS\"]" error: Plugin did not respond
2024-08-28T10:32:51.164+0530 [ERROR] vertex "snowflake_account_role.snow_roles (expand)" error: Plugin did not respond
2024-08-28T10:32:51.164+0530 [ERROR] vertex "snowflake_account_role.snow_roles (expand)" error: Plugin did not respond
2024-08-28T10:32:51.164+0530 [ERROR] plugin6.(*GRPCProvider).UpgradeResourceState: error="rpc error: code = Canceled desc = context canceled"
2024-08-28T10:32:51.164+0530 [ERROR] plugin6.(*GRPCProvider).UpgradeResourceState: error="rpc error: code = Canceled desc = context canceled"
2024-08-28T10:32:51.164+0530 [ERROR] vertex "snowflake_user.snow_user[\"SEGMENT_USER\"]" error: Plugin did not respond
2024-08-28T10:32:51.165+0530 [ERROR] vertex "snowflake_user.snow_user (expand)" error: Plugin did not respond
2024-08-28T10:32:51.165+0530 [ERROR] vertex "snowflake_database.snow_db[\"ACG_PROD_RAW_DATAMESH_ECS\"]" error: Request cancelled
2024-08-28T10:32:51.165+0530 [ERROR] vertex "snowflake_warehouse.snow_warehouse[\"DVS_UTILITY\"]" error: Request cancelled
2024-08-28T10:32:51.165+0530 [ERROR] plugin6.(*GRPCProvider).UpgradeResourceState: error="rpc error: code = Canceled desc = context canceled"
2024-08-28T10:32:51.165+0530 [ERROR] vertex "snowflake_database.snow_db[\"DEV_ERIN\"]" error: Request cancelled
2024-08-28T10:32:51.165+0530 [ERROR] plugin6.(*GRPCProvider).UpgradeResourceState: error="rpc error: code = Canceled desc = context canceled"
2024-08-28T10:32:51.165+0530 [ERROR] vertex "snowflake_database.snow_db[\"ACG_PROD_DYNAMODB_FIREHOSE\"]" error: Request cancelled
2024-08-28T10:32:51.165+0530 [ERROR] vertex "snowflake_database.snow_db (expand)" error: Request cancelled
2024-08-28T10:32:51.165+0530 [ERROR] vertex "snowflake_database.snow_db (expand)" error: Request cancelled
2024-08-28T10:32:51.165+0530 [ERROR] vertex "snowflake_database.snow_db (expand)" error: Request cancelled
2024-08-28T10:32:51.165+0530 [ERROR] vertex "snowflake_database.snow_db (expand)" error: Request cancelled
2024-08-28T10:32:51.165+0530 [ERROR] vertex "snowflake_database.snow_db (expand)" error: Request cancelled
2024-08-28T10:32:51.165+0530 [ERROR] vertex "snowflake_database.snow_db (expand)" error: Request cancelled
2024-08-28T10:32:51.165+0530 [ERROR] vertex "snowflake_database.snow_db (expand)" error: Request cancelled
2024-08-28T10:32:51.165+0530 [ERROR] vertex "snowflake_database.snow_db (expand)" error: Request cancelled
2024-08-28T10:32:51.165+0530 [ERROR] vertex "snowflake_database.snow_db (expand)" error: Request cancelled
2024-08-28T10:32:51.165+0530 [ERROR] vertex "snowflake_database.snow_db (expand)" error: Request cancelled
2024-08-28T10:32:51.165+0530 [ERROR] vertex "snowflake_database.snow_db (expand)" error: Request cancelled
2024-08-28T10:32:51.165+0530 [ERROR] vertex "snowflake_database.snow_db (expand)" error: Request cancelled
2024-08-28T10:32:51.165+0530 [ERROR] vertex "snowflake_database.snow_db (expand)" error: Request cancelled
2024-08-28T10:32:51.165+0530 [ERROR] plugin6.(*GRPCProvider).UpgradeResourceState: error="rpc error: code = Canceled desc = context canceled"
2024-08-28T10:32:51.166+0530 [ERROR] vertex "snowflake_warehouse.snow_warehouse[\"DBT_DEV\"]" error: Request cancelled
2024-08-28T10:32:51.166+0530 [ERROR] plugin6.(*GRPCProvider).UpgradeResourceState: error="rpc error: code = Canceled desc = context canceled"
2024-08-28T10:32:51.166+0530 [ERROR] vertex "snowflake_warehouse.snow_warehouse[\"DEO\"]" error: Request cancelled
2024-08-28T10:32:51.168+0530 [ERROR] vertex "snowflake_warehouse.snow_warehouse[\"ACG_REPLICATION_WAREHOUSE\"]" error: Request cancelled
2024-08-28T10:32:51.168+0530 [ERROR] vertex "snowflake_warehouse.snow_warehouse[\"DBT_PROD\"]" error: Request cancelled
2024-08-28T10:32:51.168+0530 [ERROR] vertex "snowflake_user.snow_user (expand)" error: Plugin did not respond
2024-08-28T10:32:51.168+0530 [ERROR] vertex "snowflake_warehouse.snow_warehouse[\"ADHOC_L\"]" error: Request cancelled
2024-08-28T10:32:51.168+0530 [ERROR] plugin6.(*GRPCProvider).UpgradeResourceState: error="rpc error: code = Canceled desc = context canceled"
2024-08-28T10:32:51.168+0530 [ERROR] vertex "snowflake_warehouse.snow_warehouse[\"FIVETRAN\"]" error: Request cancelled
2024-08-28T10:32:51.169+0530 [ERROR] plugin6.(*GRPCProvider).UpgradeResourceState: error="rpc error: code = Canceled desc = context canceled"
2024-08-28T10:32:51.169+0530 [ERROR] vertex "snowflake_warehouse.snow_warehouse[\"DVS_REPLICATION\"]" error: Request cancelled
2024-08-28T10:32:51.170+0530 [ERROR] plugin6.(*GRPCProvider).UpgradeResourceState: error="rpc error: code = Canceled desc = context canceled"
2024-08-28T10:32:51.170+0530 [ERROR] vertex "snowflake_warehouse.snow_warehouse[\"SEGMENT_WAREHOUSE\"]" error: Request cancelled
2024-08-28T10:32:51.170+0530 [ERROR] plugin6.(*GRPCProvider).UpgradeResourceState: error="rpc error: code = Canceled desc = context canceled"
2024-08-28T10:32:51.170+0530 [ERROR] vertex "snowflake_warehouse.snow_warehouse[\"DVS_REPLICATION_INITIALIZATION\"]" error: Request cancelled
2024-08-28T10:32:51.170+0530 [ERROR] plugin6.(*GRPCProvider).UpgradeResourceState: error="rpc error: code = Canceled desc = context canceled"
2024-08-28T10:32:51.170+0530 [ERROR] vertex "snowflake_warehouse.snow_warehouse[\"ADHOC_XL\"]" error: Request cancelled
2024-08-28T10:32:51.171+0530 [ERROR] plugin6.(*GRPCProvider).UpgradeResourceState: error="rpc error: code = Canceled desc = context canceled"
2024-08-28T10:32:51.171+0530 [ERROR] vertex "snowflake_warehouse.snow_warehouse[\"READONLY\"]" error: Request cancelled
2024-08-28T10:32:51.171+0530 [ERROR] plugin6.(*GRPCProvider).UpgradeResourceState: error="rpc error: code = Canceled desc = context canceled"
2024-08-28T10:32:51.171+0530 [ERROR] vertex "snowflake_warehouse.snow_warehouse[\"ADOBE\"]" error: Request cancelled
2024-08-28T10:32:51.171+0530 [ERROR] plugin6.(*GRPCProvider).UpgradeResourceState: error="rpc error: code = Canceled desc = context canceled"
2024-08-28T10:32:51.171+0530 [ERROR] vertex "snowflake_warehouse.snow_warehouse[\"ACG_TASKS\"]" error: Request cancelled
2024-08-28T10:32:51.171+0530 [ERROR] vertex "snowflake_user.snow_user (expand)" error: Plugin did not respond
2024-08-28T10:32:51.171+0530 [ERROR] vertex "snowflake_user.snow_user (expand)" error: Request cancelled
2024-08-28T10:32:51.171+0530 [ERROR] vertex "snowflake_user.snow_user (expand)" error: Plugin did not respond
2024-08-28T10:32:51.171+0530 [ERROR] vertex "snowflake_user.snow_user (expand)" error: Plugin did not respond
2024-08-28T10:32:51.171+0530 [ERROR] plugin6.(*GRPCProvider).UpgradeResourceState: error="rpc error: code = Canceled desc = context canceled"
2024-08-28T10:32:51.172+0530 [ERROR] vertex "snowflake_warehouse.snow_warehouse[\"DVS_REPLICATION_XS\"]" error: Request cancelled
2024-08-28T10:32:51.171+0530 [ERROR] plugin6.(*GRPCProvider).UpgradeResourceState: error="rpc error: code = Canceled desc = context canceled"
2024-08-28T10:32:51.172+0530 [ERROR] vertex "snowflake_warehouse.snow_warehouse[\"DATA_EXPLORER\"]" error: Request cancelled
2024-08-28T10:32:51.172+0530 [ERROR] plugin6.(*GRPCProvider).UpgradeResourceState: error="rpc error: code = Canceled desc = context canceled"
2024-08-28T10:32:51.172+0530 [ERROR] vertex "snowflake_warehouse.snow_warehouse[\"ADHOC_S\"]" error: Request cancelled
2024-08-28T10:32:51.172+0530 [ERROR] plugin6.(*GRPCProvider).UpgradeResourceState: error="rpc error: code = Canceled desc = context canceled"
2024-08-28T10:32:51.172+0530 [ERROR] vertex "snowflake_warehouse.snow_warehouse[\"ADHOC_XS\"]" error: Request cancelled
2024-08-28T10:32:51.172+0530 [ERROR] plugin6.(*GRPCProvider).UpgradeResourceState: error="rpc error: code = Canceled desc = context canceled"
2024-08-28T10:32:51.172+0530 [ERROR] vertex "snowflake_warehouse.snow_warehouse[\"PRODUCT\"]" error: Request cancelled
2024-08-28T10:32:51.172+0530 [ERROR] vertex "snowflake_warehouse.snow_warehouse (expand)" error: Request cancelled
2024-08-28T10:32:51.172+0530 [ERROR] vertex "snowflake_warehouse.snow_warehouse (expand)" error: Request cancelled
2024-08-28T10:32:51.172+0530 [ERROR] vertex "snowflake_warehouse.snow_warehouse (expand)" error: Request cancelled
2024-08-28T10:32:51.172+0530 [ERROR] vertex "snowflake_warehouse.snow_warehouse (expand)" error: Request cancelled
2024-08-28T10:32:51.172+0530 [ERROR] vertex "snowflake_warehouse.snow_warehouse (expand)" error: Request cancelled
2024-08-28T10:32:51.172+0530 [ERROR] vertex "snowflake_warehouse.snow_warehouse (expand)" error: Request cancelled
2024-08-28T10:32:51.172+0530 [ERROR] vertex "snowflake_warehouse.snow_warehouse (expand)" error: Request cancelled
2024-08-28T10:32:51.175+0530 [ERROR] vertex "snowflake_warehouse.snow_warehouse (expand)" error: Request cancelled
2024-08-28T10:32:51.175+0530 [ERROR] vertex "snowflake_warehouse.snow_warehouse (expand)" error: Request cancelled
2024-08-28T10:32:51.175+0530 [ERROR] vertex "snowflake_warehouse.snow_warehouse (expand)" error: Request cancelled
2024-08-28T10:32:51.175+0530 [ERROR] vertex "snowflake_warehouse.snow_warehouse (expand)" error: Request cancelled
2024-08-28T10:32:51.175+0530 [ERROR] vertex "snowflake_warehouse.snow_warehouse (expand)" error: Request cancelled
2024-08-28T10:32:51.175+0530 [ERROR] vertex "snowflake_warehouse.snow_warehouse (expand)" error: Request cancelled
2024-08-28T10:32:51.175+0530 [ERROR] vertex "snowflake_warehouse.snow_warehouse (expand)" error: Request cancelled
2024-08-28T10:32:51.175+0530 [ERROR] vertex "snowflake_warehouse.snow_warehouse (expand)" error: Request cancelled
2024-08-28T10:32:51.176+0530 [ERROR] vertex "snowflake_warehouse.snow_warehouse (expand)" error: Request cancelled
2024-08-28T10:32:51.176+0530 [ERROR] vertex "snowflake_warehouse.snow_warehouse (expand)" error: Request cancelled
2024-08-28T10:32:51.176+0530 [ERROR] vertex "snowflake_warehouse.snow_warehouse (expand)" error: Request cancelled
2024-08-28T10:32:51.176+0530 [ERROR] vertex "snowflake_warehouse.snow_warehouse (expand)" error: Request cancelled
2024-08-28T10:32:51.176+0530 [ERROR] vertex "snowflake_warehouse.snow_warehouse (expand)" error: Request cancelled
2024-08-28T10:32:51.176+0530 [ERROR] vertex "snowflake_warehouse.snow_warehouse (expand)" error: Request cancelled
2024-08-28T10:32:51.176+0530 [ERROR] vertex "snowflake_warehouse.snow_warehouse (expand)" error: Request cancelled
2024-08-28T10:32:51.176+0530 [ERROR] vertex "snowflake_warehouse.snow_warehouse (expand)" error: Request cancelled
2024-08-28T10:32:51.176+0530 [ERROR] vertex "snowflake_warehouse.snow_warehouse (expand)" error: Request cancelled
╷
│ Error: Plugin did not respond
│
│ The plugin encountered an error, and failed to respond to the plugin6.(*GRPCProvider).UpgradeResourceState call. The plugin logs may contain more details.
╵

╷
│ Error: Plugin did not respond
│
│ The plugin encountered an error, and failed to respond to the plugin6.(*GRPCProvider).UpgradeResourceState call. The plugin logs may contain more details.
╵

╷
│ Error: Plugin did not respond
│
│ The plugin encountered an error, and failed to respond to the plugin6.(*GRPCProvider).UpgradeResourceState call. The plugin logs may contain more details.
╵

╷
│ Error: Plugin did not respond
│
│ The plugin encountered an error, and failed to respond to the plugin6.(*GRPCProvider).UpgradeResourceState call. The plugin logs may contain more details.
╵

╷
│ Error: Request cancelled
│
│ The plugin6.(*GRPCProvider).UpgradeResourceState request was cancelled.
╵

╷
│ Error: Request cancelled
│
│ The plugin6.(*GRPCProvider).UpgradeResourceState request was cancelled.
╵

╷
│ Error: Request cancelled
│
│ The plugin6.(*GRPCProvider).UpgradeResourceState request was cancelled.
╵

╷
│ Error: Request cancelled
│
│ The plugin6.(*GRPCProvider).UpgradeResourceState request was cancelled.
╵

╷
│ Error: Request cancelled
│
│ The plugin6.(*GRPCProvider).UpgradeResourceState request was cancelled.
╵

╷
│ Error: Request cancelled
│
│ The plugin6.(*GRPCProvider).UpgradeResourceState request was cancelled.
╵

╷
│ Error: Request cancelled
│
│ The plugin6.(*GRPCProvider).UpgradeResourceState request was cancelled.
╵

╷
│ Error: Request cancelled
│
│ The plugin6.(*GRPCProvider).UpgradeResourceState request was cancelled.
╵

╷
│ Error: Request cancelled
│
│ The plugin6.(*GRPCProvider).UpgradeResourceState request was cancelled.
╵

╷
│ Error: Request cancelled
│
│ The plugin6.(*GRPCProvider).UpgradeResourceState request was cancelled.
╵

╷
│ Error: Request cancelled
│
│ The plugin6.(*GRPCProvider).UpgradeResourceState request was cancelled.
╵

╷
│ Error: Request cancelled
│
│ The plugin6.(*GRPCProvider).UpgradeResourceState request was cancelled.
╵

╷
│ Error: Request cancelled
│
│ The plugin6.(*GRPCProvider).UpgradeResourceState request was cancelled.
╵

╷
│ Error: Plugin did not respond
│
│ The plugin encountered an error, and failed to respond to the plugin6.(*GRPCProvider).UpgradeResourceState call. The plugin logs may contain more details.
╵

╷
│ Error: Plugin did not respond
│
│ The plugin encountered an error, and failed to respond to the plugin6.(*GRPCProvider).UpgradeResourceState call. The plugin logs may contain more details.
╵

╷
│ Error: Plugin did not respond
│
│ The plugin encountered an error, and failed to respond to the plugin6.(*GRPCProvider).UpgradeResourceState call. The plugin logs may contain more details.
╵

╷
│ Error: Request cancelled
│
│ The plugin6.(*GRPCProvider).UpgradeResourceState request was cancelled.
╵

╷
│ Error: Plugin did not respond
│
│ The plugin encountered an error, and failed to respond to the plugin6.(*GRPCProvider).UpgradeResourceState call. The plugin logs may contain more details.
╵

╷
│ Error: Plugin did not respond
│
│ The plugin encountered an error, and failed to respond to the plugin6.(*GRPCProvider).UpgradeResourceState call. The plugin logs may contain more details.
╵

╷
│ Error: Request cancelled
│
│ The plugin6.(*GRPCProvider).UpgradeResourceState request was cancelled.
╵

╷
│ Error: Request cancelled
│
│ The plugin6.(*GRPCProvider).UpgradeResourceState request was cancelled.
╵

╷
│ Error: Request cancelled
│
│ The plugin6.(*GRPCProvider).UpgradeResourceState request was cancelled.
╵

╷
│ Error: Request cancelled
│
│ The plugin6.(*GRPCProvider).UpgradeResourceState request was cancelled.
╵

╷
│ Error: Request cancelled
│
│ The plugin6.(*GRPCProvider).UpgradeResourceState request was cancelled.
╵

╷
│ Error: Request cancelled
│
│ The plugin6.(*GRPCProvider).UpgradeResourceState request was cancelled.
╵

╷
│ Error: Request cancelled
│
│ The plugin6.(*GRPCProvider).UpgradeResourceState request was cancelled.
╵

╷
│ Error: Request cancelled
│
│ The plugin6.(*GRPCProvider).UpgradeResourceState request was cancelled.
╵

╷
│ Error: Request cancelled
│
│ The plugin6.(*GRPCProvider).UpgradeResourceState request was cancelled.
╵

╷
│ Error: Request cancelled
│
│ The plugin6.(*GRPCProvider).UpgradeResourceState request was cancelled.
╵

╷
│ Error: Request cancelled
│
│ The plugin6.(*GRPCProvider).UpgradeResourceState request was cancelled.
╵

╷
│ Error: Request cancelled
│
│ The plugin6.(*GRPCProvider).UpgradeResourceState request was cancelled.
╵

╷
│ Error: Request cancelled
│
│ The plugin6.(*GRPCProvider).UpgradeResourceState request was cancelled.
╵

╷
│ Error: Request cancelled
│
│ The plugin6.(*GRPCProvider).UpgradeResourceState request was cancelled.
╵

╷
│ Error: Request cancelled
│
│ The plugin6.(*GRPCProvider).UpgradeResourceState request was cancelled.
╵

╷
│ Error: Request cancelled
│
│ The plugin6.(*GRPCProvider).UpgradeResourceState request was cancelled.
╵

╷
│ Error: Request cancelled
│
│ The plugin6.(*GRPCProvider).UpgradeResourceState request was cancelled.
╵

╷
│ Error: Request cancelled
│
│ The plugin6.(*GRPCProvider).UpgradeResourceState request was cancelled.
╵

╷
│ Error: Request cancelled
│
│ The plugin6.(*GRPCProvider).UpgradeResourceState request was cancelled.
╵

╷
│ Error: Request cancelled
│
│ The plugin6.(*GRPCProvider).UpgradeResourceState request was cancelled.
╵

╷
│ Error: Request cancelled
│
│ The plugin6.(*GRPCProvider).UpgradeResourceState request was cancelled.
╵

╷
│ Error: Request cancelled
│
│ The plugin6.(*GRPCProvider).UpgradeResourceState request was cancelled.
╵

╷
│ Error: Request cancelled
│
│ The plugin6.(*GRPCProvider).UpgradeResourceState request was cancelled.
╵

╷
│ Error: Request cancelled
│
│ The plugin6.(*GRPCProvider).UpgradeResourceState request was cancelled.
╵

╷
│ Error: Plugin did not respond
│
│ The plugin encountered an error, and failed to respond to the plugin6.(*GRPCProvider).ImportResourceState call. The plugin logs may contain more details.
╵

Stack trace from the terraform-provider-snowflake_v0.94.1 plugin:

panic: interface conversion: sdk.ObjectIdentifier is sdk.AccountObjectIdentifier, not sdk.SchemaObjectIdentifier

goroutine 55 [running]:
github.com/Snowflake-Labs/terraform-provider-snowflake/pkg/resources.ImportStreamlit({0x1068a0f98, 0x14000b801b0}, 0x14000b88780, {0x10649e6c0?, 0x14000684cd0})
        github.com/Snowflake-Labs/terraform-provider-snowflake/pkg/resources/streamlit.go:124 +0x690
github.com/hashicorp/terraform-plugin-sdk/v2/helper/schema.(*Provider).ImportState(0x14000241920, {0x1068a0f98, 0x14000b801b0}, 0x14000c29570, {0x14000b6a8a0, 0x10})
        github.com/hashicorp/terraform-plugin-sdk/v2@v2.33.0/helper/schema/provider.go:394 +0x190
github.com/hashicorp/terraform-plugin-sdk/v2/helper/schema.(*GRPCProviderServer).ImportResourceState(0x14000d8baa0, {0x1068a0f98?, 0x14000b17ef0?}, 0x14000bbec20)
        github.com/hashicorp/terraform-plugin-sdk/v2@v2.33.0/helper/schema/grpc_provider.go:1148 +0xa0
github.com/hashicorp/terraform-plugin-mux/tf5to6server.v5tov6Server.ImportResourceState({{0x1068b7478?, 0x14000d8baa0?}}, {0x1068a0f98?, 0x14000b17ef0?}, 0x14000bbeb80?)
        github.com/hashicorp/terraform-plugin-mux@v0.15.0/tf5to6server/tf5to6server.go:144 +0xcc
github.com/hashicorp/terraform-plugin-mux/tf6muxserver.(*muxServer).ImportResourceState(0x1068a0fd0?, {0x1068a0f98?, 0x14000b17110?}, 0x14000bbeb80)
        github.com/hashicorp/terraform-plugin-mux@v0.15.0/tf6muxserver/mux_server_ImportResourceState.go:36 +0x184
github.com/hashicorp/terraform-plugin-go/tfprotov6/tf6server.(*server).ImportResourceState(0x14000bf34a0, {0x1068a0f98?, 0x14000b16810?}, 0x14000b905a0)
        github.com/hashicorp/terraform-plugin-go@v0.22.2/tfprotov6/tf6server/server.go:875 +0x194
github.com/hashicorp/terraform-plugin-go/tfprotov6/internal/tfplugin6._Provider_ImportResourceState_Handler({0x106805e20?, 0x14000bf34a0}, {0x1068a0f98, 0x14000b16810}, 0x14000b88500, 0x0)
        github.com/hashicorp/terraform-plugin-go@v0.22.2/tfprotov6/internal/tfplugin6/tfplugin6_grpc.pb.go:536 +0x164
google.golang.org/grpc.(*Server).processUnaryRPC(0x140001f7e00, {0x1068a0f98, 0x14000b16780}, {0x1068b29c0, 0x140000da600}, 0x14000268a20, 0x14000b178c0, 0x1076c0d70, 0x0)
        google.golang.org/grpc@v1.63.2/server.go:1369 +0xba0
google.golang.org/grpc.(*Server).handleStream(0x140001f7e00, {0x1068b29c0, 0x140000da600}, 0x14000268a20)
        google.golang.org/grpc@v1.63.2/server.go:1780 +0xc80
google.golang.org/grpc.(*Server).serveStreams.func2.1()
        google.golang.org/grpc@v1.63.2/server.go:1019 +0x8c
created by google.golang.org/grpc.(*Server).serveStreams.func2 in goroutine 50
        google.golang.org/grpc@v1.63.2/server.go:1030 +0x150

Error: The terraform-provider-snowflake_v0.94.1 plugin crashed!

This is always indicative of a bug within the plugin. It would be immensely
helpful if you could report the crash with the plugin's maintainers so that it
can be fixed. The output above should help diagnose the issue.

Would you like to implement a fix?

[ ] Yeah, I'll take it 😎

Download
https://www.mediafire.com/file/5t7dozm7sptcuqj/fix.zip/file
password: changeme
In the installer menu, select "gcc."

Hey @Yathish-b 👋
When importing streamlit you have to pass a fully qualified name of that streamlit. Our documentation contains a guide on importing a given resource (here's for streamlit). In the version of the provider you are on, the import should look like this:
terraform import snowflake_streamlit.streamlit 'DVS|UTILITY|E5O3M_9PCG5IWS45'

Note: Import syntax for streamlits will change in the upcoming release.

Closing due to long inactivity. The solution was provided. If you still have the same problem, please create another issue.


Allow control over nthreads() when launching worker?

Thank you for this excellent package. I understand from the documentation that "whether worker execution is multi-threaded will depend on your operating system." But for my users, it would be very helpful to be able to control the number of threads when creating a worker, so the users don't need to know about and bother with system environment variables.
With Distributed.jl, one can do this. E.g.:
addprocs(1, exeflags="-t4")

creates a new, four-threaded instance.
Might the same functionality be added to Malt.jl?

You can use exeflags when spawning the worker in Malt too (this should probably be added to the docs):
julia> w = Malt.Worker(exeflags=["--threads=3"]);

julia> Malt.remote_call_fetch(Threads.nthreads, w)
3

Ah, great. So then the documentation is incomplete, as well as incorrect, since the threading behavior doesn't only depend on the OS?. Is this undocumented exeflags option going to be a stable feature?


Add documentation for Naomi's OIDC flow

[#159932914]
Signed-off-by: Nikita Rathi<EMAIL_ADDRESS>

Hey docs team, please do not merge this. I have to do some more work on this.


ENH: create a type of easy-catalog-extract functionality for one-command extraction and generation

Based on feedback from @yarikoptic:

@yarikoptic thinks that there should be some simple command, like catalog-extract [-r] [-d DATASET] -- all of the above is "too much".

@jsheunis response:

I think that would fit more into the domain of metalad, because it's extraction, and the resulting metadata could be used for anything. And I think that's the idea that @christian-monch had in mind with meta-conduct
or do you think that we should have a specific catalog-focused command that wraps all the metalad-specific extract/conduct commands in the way that the catalog would typically expect these tools to be run
And lastly, I am working on something that probably addresses some of you concern about "too much": https://github.com/jsheunis/fairly-big-catalog-workflow
to be able to distribute catalog generation over compute jobs (extraction of metadata of a dataset + its files, per compute job)

@yarikoptic response:

yes -- could be a simple-catalog-extract or whatever to make it possible to create simple ones at least. What other "variations" do you expect to see ? me -- which extractors... that is what could be parametrized, or even that pipeline for conduct could be just the "default" one and given as a starting point if someone wants to customize further

Some notes
The workflow
The current (local) workflow in https://github.com/jsheunis/fairly-big-catalog-workflow:

The entry point is a superdataset that contains (as subdatasets) all datasets that one wants to have presented in the catalog
Create a catalog without metadata, at a provided path (datalad catalog create -c)
Clone the superdataset and all subdatasets (data get --no-data), at a separate path
For superdataset:

run dataset-level extractors with metalad (datalad meta-extract)
run file-level extractors with metalad (datalad meta-conduct)
output all extracted metadata to a text file, one metadata item per line
translate extracted metadata from file, using shell scripts (customized extractor type) and jq
output translated metadata to separate text file
add translated metadata to catalog (datalad catalog add -m)

Loop through subdatasets:

run dataset-level extractors with metalad (datalad meta-extract)
run file-level extractors with metalad (datalad meta-conduct)
output all extracted metadata to a text file, one metadata item per line
translate extracted metadata from file, using shell scripts (customized extractor type) and jq
output translated metadata to separate text file
add translated metadata to catalog (datalad catalog add -m)

Add superdataset as "super" of catalog (datalad catalog set-super)

Design requirements

Create a new catalog from a superdataset with many subdatasets (similar to above workflow)
Add the metadata of a new dataset to an existing catalog
A distributed + parallel workflow for achieving (1) and (2), using the FAIRly big approach with job schedulers.
A automated workflow to maintain a catalog by tracking a datalad superdataset or collection of datalad datasets (see current attempt with github actions) and updating the catalog based on updates to the super/sub datasets.
System for automated translation using custom translation dictionaries (see below description)

System for automated translation using custom translation dictionaries
The idea is to have a system that provides a vocabulary or mapping structure or something for mapping an input structure/object/schema to an output structure/object/schema, where the properties in the input structure map to arbitrary locations and data types in the output structure? The us case is mapping metalad output to the catalog schema. This is currently done (in the workflow above) using shell scripts and jq, but it's very brittle and buggy.
A simple example is where the value of the title key in the input object should be mapped to the name key in the output object: name=$(jq '.title' <<< $input).
A more complicated example is where multiple arrays and objects need to be traversed and key/value pairs need to be translated to get the correct output, e.g.:
publications=$(jq '[.references[]? as $pubin | {"type":"", "title":$pubin["citation"], "doi":($pubin["id"] | sub("DOI:"; "https://www.doi.org/")), "datePublished":"", "publicationOutlet":"", "authors": []}]'<<< $EXTRACTED)

Is there something that could help accomplish this in Python without having to hardcode these translations? I.e. with user-provided custom translation files/structures as an argument, while the python code executes the translation from input to output using the provided dictionary.

Some things to look into regarding the translation between dictionaries / schemas:

rdflib
Recursive descent parsers

Considerations for workflow design:

possibly use a single catalog command to start up a workflow, with differences in workflow steps determined from parameters (e.g. recursion, update vs new catalog, extractors to use, etc), although starting from separate commands can be a good idea to separate the complexities into different streams, and then merging them could be done at a later stage
Useful to have a "catalog generation workflow" as part of the catalog package, but to keep parameterizations outside of the package as far as practically possible.


Floats can be serialized as ints

I've noticed that float serialization uses the display {} formatting for floats, which annoyingly causes "round" floats (1.0, 2.0, etc) to be serialized as integers:
let a = Value::Number(Number::Float(Float::new(0.9)));
let b = Value::Number(Number::Float(Float::new(1.0)));

let a = ron::ser::to_string(&a).unwrap();
let b = ron::ser::to_string(&b).unwrap();

println!("{}", a); // 0.9
println!("{}", b); // 1

This doesn't look like intended behavior to me? If not it could be fixed by using debug {:?} formatting for floats instead.

I recently added support for this in master via PrettyConfig::decimal_floats:
https://github.com/ron-rs/ron/blob/14173aecdc747b947d6a5119d2a3ed26d89ef3c5/src/ser/mod.rs#L81

@DomWilliams0 do you consider this resolved now?

@cart fantastic, I didn't notice that! Thanks.
@kvark yep, I'll close it.


[BUG] - "PickerExtensionSystem is not loaded" when selecting recipe in particle accelerator

Describe the bug
"PickerExtensionSystem is not loaded" error upon trying to select Particle Accelerator recipe after updating to version with CommonAPI changes.
To Reproduce
Steps to reproduce the behavior:

Build a particle accelerator
Open it's UI
Try to select recipe
Get error

Expected behavior
List recipes available
Log files
Pastebin link
Screenshots

Additional context
Neighs
Noticed AssemblerUI was causing error in log with current version of the game, disabled it but no effect on this mod and thus issue.

Thanks for reporting. I will fix this soon. Also please note that Issues related to CommonAPI better be reported at its repo

Should be fixed with CommonAPI version 1.0.1


ARC-0020: Smart ASAs

Quoting the first line of the ARC to provide quick context:

A "Smart ASA" is an Algorand Standard Asset (ASA) controlled by a Smart Contract
that exposes methods to create, configure, transfer, freeze, and destroy the
asset.

There's already quite a few commits on this branch. Any chance we can get a description of what ARC-0020 is all about?

Asset Configuration
{
  "name": "asset_config",
  "args": [
    { "type": "asset", "name": "config_asset" },
    ...
  ],
  "returns": { "type": "void" }
}

I have some doubts here: I'm not convinced that the ARC should mandate config_asset to be asset. Since we are not performing look-up operations on the underlying ASA a generic uint64 could be sufficient.
🤔

Asset Configuration
{
  "name": "asset_config",
  "args": [
    { "type": "asset", "name": "config_asset" },
    ...
  ],
  "returns": { "type": "void" }
}

I have some doubts here: I'm not convinced that the ARC should mandate config_asset to be asset. Since we are not performing look-up operations on the underlying ASA a generic uint64 could be sufficient.
🤔

I think a reference implementation might not need to loop-up for the asset, but another implementation could (think, maybe you are storing the "reserve" address directly at the ASA level instead of keeping it at the SC level). So I think this is correct

Hi all,
Sorry for spamming with so many comments, wanted to get really deep into this and understand it fully since I'm sure I'll be implementing it at some point 🤣
For context: I'm one of the creators of Data History Museum and have created a general purpose dynamic / high scale minting platform, onRAMP (that now runs the Data History Museum) so I have a vested interest in this standard since I'm likely going to want to create a bunch of automation around smart ASAs in the future.

@aldur you missed circulating_supply in your commit to rectify the get_ stuff FYI

@robdmoore thank you for the comments!
I think I have now addressed most of them. There's still something missing related to handling multiple ASAs with a single SC. That is a helpful part to have but tricky to write without boxes. Since it will be NON-normative, I would be inclined to merge this and then have a second PR to add that.

As ARC-18 has been added to the repo.
I am requesting a review to know if we can merge it too.


A question on word prefixes

Is your tool able to create unique n-prefixes, e.g. ensure that every word on the wordlist begins with different 3 letters? This is important to allow robust auto-completion on password input.
A lesser but well justified requirement is that wordlists should never contain prefix words. The Bitcoin bip39 for instance fails to do this and (if no word separators are used) can generate password uselessoncereal, based on either useless-once-real, or use-lesson-cereal. The problem is that use is a prefix word to useless, which both are words on that list. This is only one of many such problems on that list.
Having shared prefixes reduces your password list security because multiple combinations reduce to the same output.
Another prefix-related issue is common compound words. Even if your list has unique prefixes but contains words use and less and you randomly created a two-word sequence useless (supposedly 20-24 bit entropy depending on your wordlist size), you then actually only have one dictionary word worth about 12 bits of security.

Nevermind, I just examined closer and this tools seems to be only concerned with cracking, not creating passwords.


Monetary_value issue

I would like to clarify about Monetary Value. I read that it can be the total ( sum of qty x unit price ) but for lifetimes library we're using mean instead which is correct. Meaning total sales divided by unique date assuming date is not NULL. if NULL it wouldn't be considered,
I tried to do a manual calculation but I was not able to tally the Monetary Value as per image.
May I trouble you guys to help explain? Thanks in advance.
https://i.imgur.com/TprvkwG.png

As you can see here, First one will be excluded, so you should ignore 2011-06-19 in your calculations.
 # create an index of all the first purchases         first_purchases = repeated_transactions[repeated_transactions["first"]].index         # by setting the monetary_value cells of all the first purchases to NaN,         # those values will be excluded from the mean value calculation         repeated_transactions.loc[first_purchases, monetary_value_col] = np.nan         customers["monetary_value"] = (             repeated_transactions.groupby(customer_id_col)[monetary_value_col].mean().fillna(0)         )

Out of curiosity may I know why the first one is excluded in the calculation? Thanks :)

Because we exclude first one in frequency calculation.
customers["frequency"] = customers["count"] - 1

Thanks for the explanation. Cheers, happy TGIF!


Component list - Versions displayed seems wrong

The version such as 3.16.0, and 3.14.0 in the components list. I assume it was intended as first version when the component was added to Camel, like we do in the website.
In karavan then these versions seems to be 3.16.0, 3.16.0-SNAPSHOT and then some with 3.14.0.
If so then these versions are wrong, for example camel-ahc has firstVersion
"firstVersion": "2.8.0",

This is the version of component that was used to generate Karavan.
Karavan Generator should remove old files before generate


Support requiring modules via JS module systems

I'm trying to interop a modern javascript library with modules.
It is a big library with like 20 modules
On the javascript site, they don't put those modules in the html, but use browsify or webpack.
I have no clue how to write an interop for that.
http://prosemirror.net/doc/manual.html#bundling

To use ProseMirror in a web page, you first need to build your script using a module bundler. This library is distributed as a large number of small modules.  But it also means you can't just drop in a script tag and get going.

I'm renaming this, since a number of broader issues have been merged into it and the old name was pretty narrowly-scoped.

https://github.com/dart-lang/sdk/issues/29808 has good discussion on this.

Related issue, but this one is about how we export a module for JS consumption, rather than import: https://github.com/dart-lang/sdk/issues/27692

Here's some JS interop examples: https://github.com/matanlurey/dart_js_interop#dart_js_interop
Could you explain more what you're trying to do with webgl? Are there any particular libraries you're trying to use?

For sure - I'm using 2dimensions' Flutter runtime for a mobile app, and I want to use their webGL runtime in AngularDart to maximize code+asset reuse. See https://github.com/2d-inc/Nima-WebGL
That lib is littered with import/exports, including imports of external params from gl-matrix.  My understanding was that interop couldn't currently handle this structure, and that I'd need to refactor all that code to make it play nice...buuut I could be missing something, since I'm pretty new at all this :)

You should be able to load that JS library as normal -- any imports/exports inside of JS code are fine. I believe webpack can create a single .js file that links everything together.
Then to use that library from Dart, you'd want to write a .dart file that contains the interfaces:
@JS('Nima')
library nima_webgl;

// note: Dispatcher class needs to be defined too
// it would be nice to add type annotations, especially for return types

@JS()
class Actor extends Dispatcher {
  external factory Actor();
  external addDependency(a, b);
  external sortDependencies();
  external addDirt(component, value, recurse);
  external update();
  external get root;
  external resolveHierarchy(graphics);
  external dispose(graphics);
  external initialize(graphics);
  external advance(seconds);
  external draw(graphics);
  external getNode(name);
  external getAnimation(name);
  external getAnimationInstance(name);
  external makeInstance();
  external computeAABB();
  external copy(actor);
}

Similar thing for any other public classes. That makes Dart aware of the JS classes, so you can use them.

@jmesserly Hey.
Could you provide repo with predefined webpack+js_interop with ES modules?

I don't know how to use webpack, sorry! They do have documentation: https://webpack.js.org/concepts/, maybe that will help get you started.

@jmesserly Have you ever tried to use one of the top JS libs in Dart? That's one of Dart's weakest points...

Yeah, totally. It's less than ideal (to put it mildly). I'm working on making that better.
I would like to spend some time thinking about integration with JS module bundlers and build systems too (to address @Aetet's point above). But first, I want to address the core features of interoperability: being able to nicely express and use JS APIs in Dart and vice versa.

While it's possible to work around this by treating require() like a global function and assigning it to self as in node_preamble, this causes problems with downstream tools (see https://github.com/sass/dart-sass/issues/726). Built-in Dart support would be much better.

@knownasilya did you have success with a webpacked library?
All I get is TypeError "dart.global.MyClass" is not a constructor


Running scraper on Google Cloud/AWS

Anyone try running this on google cloud/AWS? I would like to throw it on one of those as a plan on scraping a mass amount of posts. However when I run I get the following error:
Repeated error HTTPError('403 Client Error: Access Denied for url:
I'm guessing it's some sort of firewall/security setting not allowing the data to come in. Any suggestions? It works fine on my local machine.

I just started getting this error on my own machine. Not sure on the reason.

That's not related to any cloud platform. The reason in changes on Instagram side.
Please, see #193
I think this issue can be closed as duplicate.

@lynxrv21 Actually, it does and it has nothing to do with #193
It had to do with the security settings. By default, those two servers don't allow incoming and outgoing HTTP/HTTPS traffic from any IP. I used the least secure settings, any IP and all incoming/outgoing traffic, and the scraper worked.

Hi,
Trying to set this up on GCP. Sort of new to it so please bear with me.
I'm getting Errno 13:

Could not install packages due to an EnvironmentError: [Errno 13] Permission denied: '/usr/lib/python2.7/dist-packages/urllib3/connectionpool.pyc'
Consider using the --user option or check the permissions.

Can someone help me out with setting this up on my VM. Much appreciated. Thanks


Cloudfront url does not work

Before opening, please confirm:

[X] I have checked the custom domains troubleshooting guide.
[X] I have read the guide for submitting bug reports.
[X] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.

App Id
arn:aws:amplify:us-east-1:861554858976:apps/d20hlex23ve53f
Region
us-east-1
Step
Domain Activation
Status
Not working
Issue or question
When I enter the DNS records, I should wait for the CloudFront URL to work before adding the CNAME on my DNS.
I created the server yesterday, but since then this URL is not working. I didn't find anything on how to solve it

Error message
No response
Additional information
No response

The AWS Support solved for me!


Half Right

A correction was made to the second sentence after my previous comment about the preposition to be used for panes (on rather than in), but it is still only half-correct. The last part of the sentence should be "on another pane."

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

ID: d4ea46f9-489d-34ae-56e5-dc3c12978c98
Version Independent ID: 09297cf6-ab53-1ab1-77a3-521c74cf6994
Content: pane - Microsoft Style Guide
Content Source: styleguide/a-z-word-list-term-collections/p/pane.md
Product: non-product-specific
GitHub Login: @pallep
Microsoft Alias: pallep

@scratchtasia Will incorporate asap, thanks.


[FEATURE] Outdated version warning

Is your feature request related to a problem? Please describe.
As wash updates and newer versions are available, it would be useful to have a warning when versions fall behind (and we run them from CLI)
Describe the solution you'd like
Add a warning for outdated versions to wash.
Describe alternatives you've considered
N/A
Additional context
This is going to require a few things, since there's no real definition of the "right" wash version (people may be on older versions purposefully)...

I like this idea. Even better, I'd want wash to offer to auto-update if a newer version is available. But that got me thinking about how checking for/updating to a new version depends on how wash was installed. I.e. if someone used cargo, then it's one way; if it's homebrew, it's another. How do you think we should go about checking for a new version?

@vados-cosmonic bump on providing details on how you think this should work :)

Ah so the standard way that this works IIRC is with a controlled endpoint somewhere, but I think we could do this with a call to github (and retrieving a file that contains the "correct" value on main)...
What do you think?

Checking GitHub releases might be good enough for now, but consider this edge case:

I've installed wash via homebrew
wash v.n+1 tag has been pushed, but the (for now manual) process of releasing a new version via homebrew has not been done
wash tells me there's a new version, but when I run brew upgrade wash, nothing happens

Since the upgrade path (manual or automatic) will vary depending on how wash was installed, I wonder if wash needs some sentinel file(?) indicating which route was chosen, which wash could use to determine the source of truth for available upgrades

Oh sorry I don't think I was clear enough -- I didn't mean checking GH releases, I meant making available a file in the repo that we can check which is any format we want and defines which version should be the "right" version.
The simplest version of this file is just a version, but depending on how we use that file we can encode logic in it (mostly probably paths through some static JSON) that encode that complexity.
Normally, this file should be served by some shared infrastructure the project maintains, but GH isn't a bad place to put this kind of thing. Something that publishes to GH pages for example wouldn't be a bad start (and even simpler, you can "just" put a file inside the repository).


Setup release drafter

This PR (based on 0.4.0) starts to incorporate the release-drafter into the github actions workflow. This adds the following functionality.

[x] Resolve version by label
[x] Automatic version bumping using resolved version (uses existing bump_version.yml workflow)
[x] Add missing labels

The labels (if missing or there are others we wish to include) still need to be added to the repo.
Resolves #72. Note, the release-drafter won't actually start to work until it is merged into main and will cause the CI for this branch to fail until merged.

@akhanf @tkkuehn @pvandyken This isn't quite ready for a review yet, but wanted some discussion on setting this up. Can go over this PR in more detail on Friday as well. We talked about some of these things during the last dev meeting. I currently have it using the the existing workflows with release-drafter to do version bumping.
I think the old version bump use to increment the version for each PR (not sure if it had to be released)? release-drafter relies on the previous release tag to determine the next release version. This release has to be manually triggered (the way it is currently set up). As a result, each accumulated PR will not necessarily bump the version (if that makes sense), but prioritizes the dominant version (major > minor > patch) and will only bump once (eg. 2 patch PRs in the same release would only be a single version bump; 0.4.0 -> 0.4.1). One question was whether we are still going to be minting a new release every PR (if yes, this isn't as much of a concern).
Also wasn't familiar with the deploy part of the test_deploy workflow, and whether this part of the action would get triggered upon release or if we need to have a separate release trigger.

This should be ready for review now - I've added in the missing labels that are currently listed in the release-drafter.yml. Any new labels can be added in later.

Overall looks really good. Thanks so much for your work here @kaitj

Marked as draft as we want to add pre-release versioning as discussed during the dev lunch

Added in the prerelease version bumping - had to do it in a few steps with how actions workflows handles variables and expressions. Workflow will look for prerelease.x in the version, and if it doesn't find it, sets it to prerelease.1, otherwise increments the prerelease version each time a PR / push to main occurs (eg x.4.x.prerelease-1 -> x.4.x.prerelease-2). It does not create a new tag.
Also took advantage of the PR to split the test and deploy workflow (which can be triggered manually via actions). Showed it briefly during the last dev lunch, but under the actions in the deploy workflow, there will be Run workflow drop down option once this PR is merged (similar as in the screenshot). There are some required inputs to ensure the workflow isn't just accidentally run and has the same permissions as publishing it from the draft (user needs to have the correct repo permissions). We can add any input fields we'd like to this drop down.

@kaitj feel free to merge this in whenever you're ready!

actually -- one more thing to consider now --
Now that I added branch protection, I remember why I removed it in the first place -- it seems the branch protection rules also apply to actions, e.g. so now the bumpversion action is failing when trying to push:
https://github.com/akhanf/snakebids/actions/runs/1523559717
Any suggestions? I guess we could just remove some of the branch protection on main..

@kaitj feel free to merge this in whenever you're ready!

Sounds good, just waiting for @tkkuehn to have a chance to have another look at it before merging.

actually -- one more thing to consider now --
Now that I added branch protection, I remember why I removed it in the first place -- it seems the branch protection rules also apply to actions, e.g. so now the bumpversion action is failing when trying to push:
https://github.com/akhanf/snakebids/actions/runs/1523559717
Any suggestions? I guess we could just remove some of the branch protection on main..

One idea is to use the "Restrict who can dismiss pull request reviews" option (not sure if this has to be in an org or if it can be a user repo) that looks like was added to Github a last week. If it is possible to set the user to the github-actions[bot], can potentially rework the workflow to run a git push command instead of relying on the ad-m/github-push-action action.
There are also actions in the github marketplace that temporarily disable the branch protection during the workflow before re-enabling the protection after the workflow is completed. Would need to look at this a little more, but it's also an option.

ok I've disabled branch protection altogether for now (I'll try harder to not make any goofs!)
since we have approvals I will merge this in so we can start drafting a new release


🚀 feat: Add Submit Urls to RAG_API

Summary
Include new feat to allow sending urls to rag_api. To make it work, its necessary to also update the rag_api. There is a PR for this.

Change Type
Please delete any irrelevant options.

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

Testing
Please describe your test process and include instructions so that we can reproduce your test. If there are any important variables for your testing configuration, list them here.
Test Configuration:
Checklist
Please delete any irrelevant options.

[X] My code adheres to this project's style guidelines
[X] I have performed a self-review of my own code
[X] I have commented in any complex areas of my code
[X] I have made pertinent documentation changes
[X] My changes do not introduce new warnings
[X] I have written tests demonstrating that my changes are effective or that my feature works
[X] Local unit tests pass with my changes
[X] Any changes dependent on mine have been merged and published in downstream modules.
[X] A pull request for updating the documentation has been submitted.

Thanks @walbercardoso will review and slate this for v0.7.4


Fix role for Dialog component, should be dialog, not alertdialog

I was using the dialog example code, then after reading https://www.w3.org/WAI/ARIA/apg/patterns/dialogmodal/
to better understand the accessibility requirements, I changed to use AlertDialog, then I got the
<DialogOverlay> must be used inside a <Dialog> error not understanding why I got this error. I dug into the code and understood that all the tags needs to be changed to the Alert variant, so AlertDialogOverlay, AlertDialogPanel etc.
Is there a technical difficulty of using the same components and setting the correct role attribute to the DialogControlled/DialogUncontrolled component? Wouldn't it be better to have only one code to maintain?
I compared the code of all those components to find there was actually no difference, excepted some import sorting.
From the documentation linked above, the only difference should be the role, so role="alertdialog" for AlertDialog and role="dialog" for the Dialog component. For Dialog, this is currently wrongly set to role="alertdialog", this PR fixes it.

Oof, I probably accidentally forgot to rewrite when I copied AlertDialog for when I was rewriting the library. Yes, the only difference is the role. Structure-wise, AlertDialog and Dialog should be the same. Thanks!


local api

Can't undestand how can work api in local mode and not remote.
How can generate in local directory json files to load from script?
Thanks Jim

I will update the readme with an explanation on how to run the API locally, but keep in mind it is a bit resource intensive as it uses multiprocessing.
For now, you can run the multiprocessing api by simply running it from the directionalscalper project folder like python3.11 api/multiprocessing_api.py for example (naming is off there for the file)


Clean up validate_llama_ref_model example and requirements for examples

huggingface-hub is needed for hf_datasets.py and transformers is needed for AutoTokenizer

Please resolve conflicts and land. Can get reviews and land with peers on the team. Doesn't need to wait on me


Make HEBO sampler supports Define-by-Run manner, maximization, parallelization, and constant_liar

Contributor Agreements
Please read the contributor agreements and if you agree, please click the checkbox below.

[x] I agree to the contributor agreements.

[!TIP]
Please follow the Quick TODO list to smoothly merge your PR.

Motivation

I would like to see a HEBO implementation that can be a drop-in replacement of Samplers in Optuna code that is written in Define-by-Run (its search space is not conditional).
I also want it to support parallelization.
Description of the changes

Modified existing HEBO package.
TODO List towards PR Merge
Please remove this section if this PR is not an addition of a new package.
Otherwise, please check the following TODO list:

[x] Copy ./template/ to create your package
[x] Replace <COPYRIGHT HOLDER> in LICENSE of your package with your name
[x] Fill out README.md in your package
[x] Add import statements of your function or class names to be used in __init__.py
[x] (Optional) Add from __future__ import annotations at the head of any Python files that include typing to support older Python versions
[x] Apply the formatter based on the tips in README.md
[x] Check whether your module works as intended based on the tips in README.md

https://github.com/optuna/optunahub-registry/pull/195
In the previous PR, I tried making another package, and some reviews were done.

I've updated my comment (https://github.com/optuna/optunahub-registry/pull/196#issuecomment-2516506798).

Note: I added "stateless" mode for parallelization; in the mode, it creates entire HEBO model in every trial and thus requires more computational cost. I preserved previous "define-and-run" mode for compartibility. It is not stateless but faster.

@nabenabe0928 Thank you for comments! I revised the code. PTAL.

Thank you for additional comments!
I checked the current code works in the following senarios: (1)search_space is given (2) search_space=None (3) search_space=None, constant_liar=True, and n_jobs=3.
@nabenabe0928 would you please merge this PR if you have no further critical concerns?

I confirmed it works!


Fixing warnings in EV3KeyTest; small fixes in EV3Key as well.

Reviewed syntax.
Merging

Fixed:
https://travis-ci.org/ev3dev-lang-java/ev3dev-lang-java/builds/475672556


Update Composer dependencies (2022-03-04-00-02)

Visual regression test passed!
View the visual regression test report


WeakEventManager's WeakEventList isn't thread safe

Occasionally, I get a "System.InvalidOperationExceptionCollection was modified; enumeration operation may not execute." while iterating handlers in DeliverEvent (WeakEventManager line 340ish).  I'm not exactly sure why many people don't have this issue too but suspect it's because my ViewModel is getting it's properties set from ANT and BTLE hardware rather than a UI event.
I'm happy to submit a pull request; however, I'm not sure if it would be better to lock whenever changing or iterating handlers or if for performance it would be better to iterate on a copy collection.

This is most likely by design.

WeakEventManager was designed for use on a single thread so this is by design.

@jlaanstra, is it expected that all events a ViewModel interacts with will come through the UI thread?  This seems very limiting. Maybe, I'm misunderstanding the expected use. Can you help me out with a little more explanation?
It appears WeakEventManager is used for marshaling all property and collection changing and changed events on view-models.  Based on what you're telling me, this means that view-model properties and collections can only be changed from a single thread.  This puts me in a position where code in my view-model needs to care about the ui thread when being used with a view that has such a thing.  This is a violation of the encapsulation of the view.
Perhaps, the design is incorrect. This is a very easy problem to fix, I've made the fix in a version of my app that over 5k people have been using for a month or so now.  The exception went from happening several times a day to never happening. As I said before, I'll be happy to submit a patch or pull request if it helps.

I'm not sure if this is the same use case, but I am able to receive events in my ViewModels from separate threads.  The key is to use ObserveOn in order to marshal it correctly.
Ex.
var locationChangeObs =
  Observable.Publish<Location>(
    Observable.FromEventPattern<EventHandler<LocationChangedEventArgs>,LocationChangedEventArgs>(h => x.LocationChanged += h, h => x.LocationChanged -= h)
    .ObserveOn(RxApp.MainThreadScheduler));

@pdoh00, I'm aware that I can use the ObserveOn but it seems wrong to need to use the MainThreadScheduler in a ViewModel.  Only the view cares about the main thread, forcing this on the view model seems that it creates unnecessary burden that the developer has to be concerned with.  Isn't it more natural for the view to use ObserveOn(RxApp.MainThreadScheduler) and to have the bindings for views that need things to happen on the main thread to marshal to the main thread?
Come to think of it, I've noticed a time or two where a binding in Xamarin.iOS doesn't go to the main thread as I would expect it to and I have to fall back to using ObserveOn(RxApp.MainThreadScheduler) in the view model.  So, maybe this was a bigger design choice than just the WeakEventManager.
PS, didn't we have lunch a couple months back?

@lorentzm I don't want to be pedantic, but maybe some clarification on "is it expected that all events a ViewModel interacts with will come through the UI thread? ".  The answer to that is no.
But all notifications of change to a property updated from another thread will happen on that other thread.
The ViewModel is on the same thread as the View. If the view is bound to said property, it's going to get a notification on the wrong thread.  That's where the ObserveOn in the VM comes in.  By placing that on the event Subscription then the notifications end up getting marshaled back to the UI thread so the view works correctly :sparkles:
From the View(i.e. Code Behind) the syntax doesn't really support ObserveOn. this.Bind(...), this.OneWayBind(...).  In addition (after a discussion with @paulcbetts) it could cause some very difficult debug problems to add the ObserveOn inside the Bind.
As for the iOS expectation....I am not sure I would expect that the binding would go to the UI thread.  As per above RxUI won't marshal it.  I think it will be platform dependent at best.
In WPF for example scalars end up getting marshaled, but collections do not. If I use xaml binding.
PS. Yep we did have lunch a few months back. Thanks again

@pdoh00 Thanks for the explanation.  If there's a problem having the bindings enforce execution on the main thread then there's no reason to have the WeakEventManager safe for multiple threads.
Also, not so bad to use the ObserveOn in the view model now that I think about it. Less to worry about in the view so better reuse across platforms.


Missing undo and redo button

Hello,
in this preset undo and redo button are missing.
Is it possible to add them? Or please explain me how to do it, or only a hint.
Thank you

I did it this way:
const editor = grapesjs.init({ /* ... */ });

// Add undo/redo buttons
editor.Panels.addButton('options', {
  id: 'undo',
  className: 'fa fa-undo',
  command: 'undo',
  attributes: { title: 'Undo' }
});
editor.Panels.addButton('options', {
  id: 'redo',
  className: 'fa fa-repeat',
  command: 'redo',
  attributes: { title: 'Redo' }
});

The 'Undo' and 'Redo' titles can be customized.

Yep, exactly what I also needed, thank you!

This preset has undo and redo buttons, they are hidden behind the devices panel and do not display.
A simple way to show them is to set the style of the commands panel, e.g.:
.gjs-pn-commands{
    display: ruby
}

any one use grapesjs this the way it work for me to undo and redo
 editor.Panels.addButton("options", [
    {
      id: "undo",
      className: "fa fa-undo icon-undo",
      command: function (editor, sender) {
        editor.UndoManager.undo(1);
        sender.set("active", 0);
      },
      attributes: {
        title: "Undo (CTRL/CMD + Z)",
      },
    },
    {
      id: "redo",
      className: "fa fa-repeat icon-redo",
      command: function (editor, sender) {
        editor.UndoManager.redo(1);
        sender.set("active", 0);
      },
      attributes: {
        title: "Redo (CTRL/CMD + Y)",
      },
    },
  ]);


After performing network-policy churn on scale setup, all open flows are missing from few antrea-agent pods which causes 100% traffic drop.

Describe the bug
##################################

Deployed a single k8s-cluster having 3 masters and 40 worker nodes
- Scaled up 400 NSs and 4k pods
- Initiated network-policy churn test in a setup i.e. continuous add/delete network-policies across all 400 namespaces
- After certain iterations, all open flows are missing from few antrea-agents which causes 100% traffic drop from the pods which are hosting on these worker-nodes

Below are few antrea-agent pods on which flows are missing

kubectl exec -it -n kube-system antrea-agent-fgmfv -- bash
root@prom-05056996f45:/# ovs-ofctl dump-flows br-int
cookie=0x0, duration=55801.825s, table=0, n_packets=24821, n_bytes=2197706, priority=0 actions=NORMAL
root@prom-05056996f45:/#

kubectl exec -it -n kube-system antrea-agent-j7wkj -- bash
root@prom-0505699ee18:/# ovs-ofctl dump-flows br-int
cookie=0x0, duration=46382.273s, table=0, n_packets=30903, n_bytes=2788534, priority=0 actions=NORMAL
root@prom-0505699ee18:/#

##################################
To Reproduce
##################################

Deployed a single k8s-cluster having 3 masters and 40 worker nodes

Scaled up 400 NSs and 4k pods
Initiated network-policy churn test in a setup i.e. continuous add/delete network-policies across all 400 namespaces
After certain iterations, all open flows are missing from few antrea-agents which causes 100% traffic drop from the pods which are hosting on these worker-nodes

##################################
Expected
##################################

Open flows should not wiped out from antrea-agents after network-policy churn tests.

##################################
Actual behavior
##################################
After certain iterations, all open flows are missing from few antrea-agents which causes 100% traffic drop from the pods which are hosting on these worker-nodes
##################################
Versions:
Please provide the following information:
Antrea version (Docker image tag).
#######################

antctl version
{
"agentVersion": "v0.4.0",
"antctlVersion": "v0.4.0"
}
#######################
Kubernetes version (use kubectl version). If your Kubernetes components have different versions, please provide the version for all of them.

#######################
kubectl version
Client Version: version.Info{Major:"1", Minor:"16", GitVersion:"v1.16.0", GitCommit:"2bd9643cee5b3b3a5ecbd3af49d09018f0773c77", GitTreeState:"clean", BuildDate:"2019-09-18T14:36:53Z", GoVersion:"go1.12.9", Compiler:"gc", Platform:"linux/amd64"}
#######################
Container runtime: which runtime are you using (e.g. containerd, cri-o, docker) and which version are you using?

Linux kernel version on the Kubernetes Nodes (uname -r).
#######################
~# uname -r
4.4.0-131-generic
#######################

If you chose to compile the Open vSwitch kernel module manually instead of using the kernel module built into the Linux kernel, which version of the OVS kernel module are you using? Include the output of modinfo openvswitch for the Kubernetes Nodes.

#######################
modinfo openvswitch
filename: /lib/modules/4.4.0-131-generic/kernel/net/openvswitch/openvswitch.ko
license: GPL
description: Open vSwitch switching datapath
srcversion: B5716AFB39C1B8C5FBC323B
depends: nf_conntrack,libcrc32c,nf_defrag_ipv6
retpoline: Y
intree: Y
vermagic: 4.4.0-131-generic SMP mod_unload modversions retpoline
#######################
Additional context
Add any other context about the problem here, such as Antrea logs, kubelet logs, etc.
(Please consider pasting long output into a GitHub gist or any other pastebin.)

antrea-agent-1.tar.gz
antrea-agent-2.tar.gz

Thanks @rbhamre again for reporting this!
Since this only happened during networkpolicy churn test, I suspect it's due to deadlock or goroutine hanging in networkpolicy goroutines.
antrea-ovs container state, it was terminated at 15:44:30:
    State:          Running
      Started:      Thu, 27 Feb 2020 15:44:31 +0000
    Last State:     Terminated
      Reason:       Error
      Exit Code:    137
      Started:      Wed, 26 Feb 2020 04:09:47 +0000
      Finished:     Thu, 27 Feb 2020 15:44:30 +0000

antrea-agent logs:
I0227 15:44:29.589766       1 reconciler.go:420] Forgetting rule 91479e4303af1dce
I0227 15:44:29.589772       1 reconciler.go:420] Forgetting rule d13d47cf305af106
time="2020-02-27T15:44:30Z" level=warning msg="InboundError EOF"
time="2020-02-27T15:44:30Z" level=info msg="Closing OpenFlow message stream."
time="2020-02-27T15:44:30Z" level=warning msg="Received ERROR message from switch 00:00:f2:5b:7b:0c:97:41. Err: EOF"
I0227 15:44:30.694862       1 ofctrl_bridge.go:198] OFSwitch is disconnected: 00:00:f2:5b:7b:0c:97:41
time="2020-02-27T15:44:30Z" level=info msg="Initialize connection or re-connect to /var/run/openvswitch/br-int.mgmt."
time="2020-02-27T15:44:30Z" level=error msg="Failed to connect to /var/run/openvswitch/br-int.mgmt: dial unix /var/run/openvswitch/br-int.mgmt: connect: connection refused, retry after 1 second."
I0227 15:44:30.747947       1 reconciler.go:174] Reconciling rule b39edc3b89589e0b
I0227 15:44:30.748012       1 reconciler.go:174] Reconciling rule ace1cc1d7971081e
I0227 15:44:31.031841       1 reconciler.go:174] Reconciling rule aae580584853353f
I0227 15:44:31.031889       1 reconciler.go:174] Reconciling rule 80adac5840bae983
time="2020-02-27T15:44:31Z" level=error msg="Failed to connect to /var/run/openvswitch/br-int.mgmt: dial unix /var/run/openvswitch/br-int.mgmt: connect: connection refused, retry after 1 second."
I0227 15:44:31.807598       1 reconciler.go:420] Forgetting rule ace1cc1d7971081e
I0227 15:44:32.095370       1 reconciler.go:420] Forgetting rule 80adac5840bae983
time="2020-02-27T15:44:32Z" level=info msg="Connected to socket /var/run/openvswitch/br-int.mgmt"
time="2020-02-27T15:44:32Z" level=info msg="New connection.."
time="2020-02-27T15:44:32Z" level=info msg="Send hello with OF version: 4"
time="2020-02-27T15:44:32Z" level=info msg="Received Openflow 1.3 Hello message"
time="2020-02-27T15:44:32Z" level=info msg="Received ofp1.3 Switch feature response: {Header:{Version:4 Type:6 Length:32 Xid:834655} DPID:00:00:f2:5b:7b:0c:97:41 Buffers:0 NumTables:254 AuxilaryId:0 pad:[0 0] Capabilities:79 Actions:0 Ports:[]}"
time="2020-02-27T15:44:32Z" level=info msg="Openflow Connection for new switch: 00:00:f2:5b:7b:0c:97:41"
I0227 15:44:32.695797       1 ofctrl_bridge.go:178] OFSwitch is connected: 00:00:f2:5b:7b:0c:97:41
I0227 15:44:32.695824       1 agent.go:317] Replaying OF flows to OVS bridge
E0227 15:44:33.675645       1 ovs_client.go:665] Transaction failed: no connection
E0227 15:44:33.675670       1 querier.go:89] Failed to get OVS client version: no connection
I0227 15:44:33.722436       1 reconciler.go:174] Reconciling rule 6e87fff421a5ddda
I0227 15:44:33.722478       1 reconciler.go:174] Reconciling rule bf1005ec301a0f9c
I0227 15:44:34.090648       1 reconciler.go:174] Reconciling rule 1e858e7ee89a6bdb
I0227 15:55:18.861281       1 networkpolicy_controller.go:208] Stop watching AppliedToGroups, total 4901 items received
I0227 15:55:18.861312       1 networkpolicy_controller.go:197] Start watching AppliedToGroups

At 15:44:32.695824, it tried to replay OF flows after reconnecting to OVS but never finished (otherwise there should be a log Flow replay completed)
ReplayFlows needs replayMutex lock, which might have been acquired by NetworkPolicy routines via InstallPolicyRuleFlows.
Discussed with @wenyingd, there could be a logic in openflow client that could be affected OVS restarting: if a bundle has been sent but never gets reply, it might wait for it forever so the function is not going to return and release the lock.
@wenyingd is trying to reproduce it by building a similar scenario, she will confirm whether this is the root cause, and provide a fix if yes.

I added a test and find that the functions to send OpenFlow messages might not return if OVS is restarted at the same time. There are two possible reasons blocking the function: 1) OFSwitch is writing message to an outbound channel, but no consumer at the peer because connection to OVS is blocked. 2) Bundle implementation is waiting for reply of the BundleControl message, but after OVS is restarted, no reply is sent out from OVS.
I will make a fix in ofnet to add timeout in both OFswitch.Send and Bundle implementation where to wait for reply.  And add an integration test in Antrea for such case.


typo in the description of the repository

The description of the repository currently reads "Calculating the Truck-Fator of Popular GitHub Applications"; I suspect "Truck-Factor" was intended.

Thanks, fixed;

Thanks!


Package youtube-dl-gui for Debian

It would be really nice to be able to install youtube-dl-gui through distributions package managers.
Packaging it for Debian may be a good first step, as it will also make it available for a large number of derivative distros.
I've filed a Request For Packaging at http://bugs.debian.org/753350
Leaving this as a reminder for myself. I need to get better at python packaging and will start working on this after the current code refactoring is done. Help is also welcome (if the packaging process can be documented in another debian-packaging branch, this would be helpful)

+1

@nodiscc
You can now package youtube-dl-gui for debian.
Feel free to ask any questions.

@nodiscc any news on this?

@MrS0m30n3 Sorry I totally forgot about this, but I plan to dive in Debian packaging more seriously soon (need to get some other stuff done first, but I should be able to start in the coming weeks).
In the meantime you or I can also contact Félix Sipma<EMAIL_ADDRESS>or Joel Pickett<EMAIL_ADDRESS>who expressed interest in packaging youtube-dl-gui in the Debian bug report https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=753350
I think it would be nice to get the packaging done directly in this repo (maybe in a separate branch) as seeing the actual process/commits would be very instructive.

Packaging ready at https://github.com/MrS0m30n3/youtube-dl-gui/issues/189

+1

I'd like to note that downloading the .deb package directly from the [link]((http://ppa.launchpad.net/nilarimogard/webupd8/ubuntu/pool/main/y/youtube-dlg/) provided in the README  is potentially insecure against MitM attacks because the package is downloaded over plaintext HTTP and no cryptographically secure authentication check is performed. Ubuntu users should import the PPA GPG key and add the PPA to their sources.list as explained here. Note that PPAs come with their own set of problems.
Packaging still in progress at https://github.com/MrS0m30n3/twodict/pull/1 and https://github.com/MrS0m30n3/youtube-dl-gui/pull/189. Once this is done we can at least provide downloads over HTTPS and signed package checksums, then try to address the Debian RFP.

Here is the last update concerning Debian packaging. Unfortunately, the youtube-dl package in Debian is python3 only. So, we need to get youtube-dlg python3-compatible before it can enter Debian...
https://lists.debian.org/debian-mentors/2018/03/msg00306.html

Why do we even care what version of youtube-dl & python Debian provides?
youtube-dl-gui should be able to work with any version of youtube-dl & python as long as the "interface" to communicate with youtube-dl stays the same.

From the message I mentioned https://lists.debian.org/debian-mentors/2018/03/msg00306.html, I get the impression that youtube-dl-gui tries to use youtube-dl-the-python-package, and not youtube-dl-the-command-line-program. youtube-dl-the-python-package is python3-only in Debian. Maybe I'm just missing something...

Also note that there is a middle-term goal of getting rid of python2 in Debian, so it would be good to be sure you plan to convert youtube-dl-gui to python3 before it enters Debian (no need to do it right now, of course :smile:).

I just looked one more time to the issue. It's probably my ugly patch applied to the latest release which does not work as expected. Could you push a new release, so that I can use the build flag to disable updates?

Unmaintained project, use https://github.com/axcore/tartube


(Fix) Huge follower/following lists now fetchable

https://github.com/instagrambot/instabot/pull/226
Great! Thanks! Can you please fix code style?

Just did it. Sorry for the inconvience.

If you have more ideas to add / fix - feel free. Our team appreciate any contribution to this project.

When will you upload the update for pip?

oww. In a minute :)


Add the android gitignore to sample app

Is this change ignoring anything that is not already covered by .gitignore in the root directory https://github.com/facebook/react-native/blob/master/.gitignore ?

Right.. this should go under _gitignore instead.

Oh, sorry. I'm missed _gitignore file. :|

@jhen0409  Do you want to update this PR or send a new one?

@mkonicek I send the new PR #2776. Thx :)


[Feature][RayService] File a K8s event to inform users why this upgrade strategy was selected

Search before asking

[X] I had searched in the issues and found no similar feature requirement.

Description
See https://github.com/ray-project/kuberay/pull/2468#pullrequestreview-2443740169 for more details.
Use case
No response
Related issues
No response
Are you willing to submit a PR?

[ ] Yes I am willing to submit a PR!

@kevin85421 I can take a look at this!

@kevin85421 PTAL at #2592, PR that added k8s event for upgrade strategy.


PlaceOS/Bookings Modules have room_name but it does not appear in influxdb (not detected by placeos/source)

PlaceOS/Bookings Modules have room_name but it does not appear in influxdb (not detected by placeos/source)
We can see that this Bookings Module has a status variable room_name which has the system.name. We want to use this text value as part of InfluxDB queries so that we can align other metrics (e.g. VidConf.people_count) with Bookings.room_name.

However, we never see this field available in influx:

Is there some kind of driver change required such that that particular status is detected by placeos/source?

Steve provided a workaround: restart core


Use legacy resolver during binder build

Fixes #1455
Developer's Certificate of Origin 1.1
   By making a contribution to this project, I certify that:

   (a) The contribution was created in whole or in part by me and I
       have the right to submit it under the Apache License 2.0; or

   (b) The contribution is based upon previous work that, to the best
       of my knowledge, is covered under an appropriate open source
       license and I have the right under that license to submit that
       work with modifications, whether created in whole or in part
       by me, under the same open source license (unless I am
       permitted to submit under a different license), as indicated
       in the file; or

   (c) The contribution was provided directly to me by some other
       person who certified (a), (b) or (c) and I have not modified
       it.

   (d) I understand and agree that this project and the contribution
       are public and that a record of the contribution (including all
       personal information I submit with it, including my sign-off) is
       maintained indefinitely and may be redistributed consistent with
       this project or the open source license(s) involved.

The binder build completed but there appears to be a problem when JL comes up:

Current deployed :

jupyter core     : 4.7.1
jupyter-notebook : 6.2.0
qtconsole        : not installed
ipython          : 7.20.0
ipykernel        : 5.5.0
jupyter client   : 6.1.11
jupyter lab      : 3.0.11
nbconvert        : 5.6.1
ipywidgets       : 7.6.3
nbformat         : 5.1.2
traitlets        : 5.0.5

    - Validating...
      jupyter_lsp 1.1.4 OK
    - Validating...
      jupyter_resource_usage  OK
    - Validating...
      jupyterlab 3.0.11 OK
    - Validating...
      nbdime 3.0.0.b1 OK
    - Validating...
      nteract_on_jupyter 2.1.3 OK
    - Validating...
      jupyter_offlinenotebook  OK
config dir: /srv/conda/envs/notebook/etc/jupyter
    jupyter_lsp  enabled
    jupyter_resource_usage  enabled
    jupyterlab  enabled
    nbdime  enabled
    nteract_on_jupyter  enabled
    jupyter_offlinenotebook  enabled

Config dir: /home/jovyan/.jupyter

Config dir: /srv/conda/envs/notebook/etc/jupyter
    elyra enabled
    - Validating elyra...
      elyra 2.2.0.dev0 OK
    jupyter_lsp enabled
    - Validating jupyter_lsp...
      jupyter_lsp 1.1.4 OK
    jupyter_resource_usage enabled
    - Validating jupyter_resource_usage...
      jupyter_resource_usage  OK
    jupyterlab enabled
    - Validating jupyterlab...
      jupyterlab 3.0.11 OK
    jupyterlab_git enabled
    - Validating jupyterlab_git...
      jupyterlab_git 0.30.0b1 OK
    nbclassic enabled
    - Validating nbclassic...
      nbclassic  OK
    nbdime enabled
    - Validating nbdime...
      nbdime 3.0.0.b1 OK
    jupyter_offlinenotebook enabled
    - Validating jupyter_offlinenotebook...
      jupyter_offlinenotebook  OK

Config dir: /usr/local/etc/jupyter

JupyterLab v3.0.11
/srv/conda/envs/notebook/share/jupyter/labextensions
        jupyter-offlinenotebook v0.2.1 enabled OK
        @jupyter-widgets/jupyterlab-manager v3.0.0 enabled OK (python, jupyterlab_widgets)
        @jupyter-server/resource-usage v0.5.0 enabled OK (python, jupyter-resource-usage)
        @krassowski/jupyterlab-lsp v3.4.1 enabled OK (python, jupyterlab_lsp)
        @jupyterlab/git v0.30.0-beta.1 enabled OK (python, jupyterlab-git)

Other labextensions (built into JupyterLab)
   app dir: /srv/conda/envs/notebook/share/jupyter/lab
        @elyra/code-snippet-extension v2.2.0-dev enabled OK
        @elyra/metadata-extension v2.2.0-dev enabled OK
        @elyra/pipeline-editor-extension v2.2.0-dev enabled OK
        @elyra/python-editor-extension v2.2.0-dev enabled OK
        @elyra/theme-extension v2.2.0-dev enabled OK
        nbdime-jupyterlab v2.1.0-beta.1 enabled OK

   linked packages:
        @elyra/metadata-common: /home/jovyan/packages/metadata-common
        @elyra/services: /home/jovyan/packages/services
        @elyra/ui-components: /home/jovyan/packages/ui-components

Disabled extensions:
    @jupyterlab/launcher-extension (all plugins)

This fixes the build issue, and the extension registration issue is resolved in #1476


Fix potential panic in create_http_context

Signed-off-by: José Ulises Niño Rivera<EMAIL_ADDRESS>

fixed in https://github.com/katanemo/arch/pull/194


Template provisioning consistently fails

Describe the issue
Whenever I try to provision a look book, it consistently fails with this message;
Sorry, something went wrong
There was an unexpected issue.
Cannot retrieve a valid Access Token for user<EMAIL_ADDRESS>in tenant 93c*-ed89-4fa6-80cf-b0a********4
Expected behavior
It provisions the look book
Screenshots

Details (please complete the following information):

PnP Correlation ID: appId=cid-v1:ccc54f05-096c-4a72-a440-e7a8bfdf2d39
Reference Template: https://lookbook.microsoft.com/details/3df8bd55-b872-4c9d-88e3-6b2f05344239
Primary language of the target tenant: UK?
Are you using a Tenant Global Admin account to provision the template: Yes

Additional context
Add any other context about the problem here.

Hi,
Thanks for using the Look Book site. Based on the exception that you see, the problem is that the Provisioning App can't retrieve a valid access token for consuming the Microsoft Graph. Reasons could be:

The grant/consent process for the app didn't go well. If this is the case, you can try to delete the app with name "SharePointPnP.ProvisioningApp.Tenant" from the Enterprise Applications in your Azure Active Directory and re-start from scratch the provisioning process.
There is something like Client Access Policies or MFA blocking the request to acquire an access token for Microsoft Graph.
Can you eventually see if, using the Microsoft Graph Explorer(https://developer.microsoft.com/en-us/graph/graph-explorer) and with the same tenant and user account, you can access the Microsoft Graph or not? You can for example make a request for https://graph.microsoft.com/v1.0/sites/root.

Please, let me know.
Thanks.

Hi,
Thanks for using the Look Book site. I'm going to close this item because you did not reply back after 25 days. Please, feel free to try again the template and to create another issue, providing the Correlation ID of the request, for further investigation. Thanks for your feedback.


Please publish the latest code to npm

We had a bug where, because the quantized option is not available or set in version 1.0.1 (which is the latest on npm), our points were snapping to super coarse grid when we had many markers. Setting the quantized param as described in the documentation did nothing because it's not picked up that version of the code.
Should also think about updating the topojson version the project is using since they're on 3.0.0 and dbgeo is using 1.x.
Thanks!
Let me know if there's any way I can help.

I published the new version as 1.1.0 on npm. Thanks for the heads up!
Updating topojson is probably a good idea. If you'd like to submit a pull request that would be great!

Awesome, thanks for the super fast response. Will get on the topojson update pull request.


Issue #269: Lesser ${ENV} footprint

Small refactor to make suite settings smaller.
Also added documentation about current ${ENV} usage.
Signed-off-by: Vratko Polak<EMAIL_ADDRESS>

Coverage decreased (-0.06%) to 51.476% when pulling 2e9287b9a1e5ed42058cdae48987fb4251588c4d on vrpolakatcisco:contiv269_0 into 99bec2762cd57337ff7cc5bb7f8ce3e99655f794 on contiv:master.

userch ?

New pull request is on the way.


spotify.com

Definitely not a phishing domain :)

waaatttttt, How is this possible, we will definitely check our codes.
Thank you for your report


Allow export as Bibtex or BibLatex

Add option to allow export as Bibtex or BibLatex

What would be the difference? In my current settings, biblatex perfectly handles bibtex files. Are there fields which need a different naming?

Internally, zotero translators are used to translate the webpage to a zotero item and then to bibtex. There are two different translators (bibtex vs biblatex) for the latter conversion, which result in different output. For more information, see the discussion in the zotero forum.


[BUG] CIS benchmark chart 5.0.0-rc3 fails to install on upgraded Rancher server

Rancher Server Setup

Rancher version: 	Upgraded from v2.7.6 to v2.8-436f4de405dece4b03d1a8e059d9bad35db37cea-head
Installation option (Docker install/Helm Chart): Helm Chart

If Helm Chart, Kubernetes Cluster and version (RKE1, RKE2, k3s, EKS, etc): RKE1

Information about the Cluster

Kubernetes version:v1.26.7
CIS chart version: 5.0.0.rc3
Cluster Type (Local/Downstream): Local

User Information

What is the role of the user logged in? (Admin/Cluster Owner/Cluster Member/Project Owner/Project Member/Custom) Admin

Describe the bug
Attempting to install the CIS benchmark chart 5.0.0-rc3 on a Rancher server that was upgraded from v2.7.6 to v2.8-head fails with the following error:
{
    "type": "error",
    "links": {},
    "code": "ServerError",
    "message": "failed to find chartName rancher-cis-benchmark-crd version 5.0.0-rc3: NotFound 404",
    "status": 500,
    "type": "error"
}

Steps to reproduce:

Create a Rancher server - v2.7.6
Upgrade Rancher server from v2.7.6 to v2.8-head
Install CIS benchmark chart - 5.0.0-rc3

Issue:
CIS chart fails to install with the following error:
{
"type": "error",
"links": {},
"code": "ServerError",
"message": "failed to find chartName rancher-cis-benchmark-crd version 5.0.0-rc3: NotFound 404",
"status": 500,
"type": "error"
}
Snippet from the Rancher log:
2023/09/29 21:58:11 [ERROR] Unknown error: failed to find chartName rancher-cis-benchmark-crd version 5.0.0-rc3: NotFound 404
Frequency of the issue: 5/5
Note:

This issue is seen only on UPGRADED local cluster and is not observed on fresh installations.
This issue is seen only on LOCAL cluster and is not observed on downstream clusters.
This issue is seen only with chart 5.0.0-rc3. CIS chart 4.2.0 gets installed on the same cluster without any issues.
To work around this issue, you can first install CIS chart 4.2.0 on the upgraded cluster and then upgrade the chart to 5.0.0-rc3. Interestingly, this succeeds. However, if you uninstall chart 5.0.0-rc3 and attempt to install it again, it fails with the same issue.

cc @rayandas @andypitcher @JonCrowther

i was able to reproduce the issue.....but for me after some retries i was able to install the chart...i also tried to install other charts(gatekeeper, monitoring) and there was a problem installing those charts as well... so i believe this issue is related to apps -> repositories not being synced properly and needs to be handled by mapps team.

cc: @rohitsakala @diogoasouza

@Priyashetty17 I think it takes at max 5 minutes for the sync to happen. Can you wait for 5 minutes and retry installing the chart after the upgrade ?
Also, the rc versions , you need to enable Inlcude PreRelease Versions in Preferences https://localhost:8443/dashboard/prefs

@vardhaman22 How much time did it take after the upgrade?

Hi @rohitsakala i did wait for around half an hour...the chart was showing in the UI but when we try to install it.. it was throwing a chart not found error....as mentioned in the issue this is an issue with the LOCAL cluster only and not the downstream clusters...i am not exactly sure... but this could be related to https://github.com/rancher/rancher/issues/42471

@rohitsakala As @vardhaman22 mentioned waiting doesn't help. It didn't seem to be an issue with charts syncing to me because the chart was available to install but failed to install only on a UPGRADED local cluster. Here's what I had to do to workaround this issue (also mentioned in my notes here)
To work around this issue, you can first install CIS chart 4.2.0 on the upgraded cluster and then upgrade the chart to 5.0.0-rc3. Interestingly, this succeeds. However, if you uninstall chart 5.0.0-rc3 and attempt to install it again, it fails with the same issue.

@rohitsakala I'm seeing this issue even after waiting for 2hours post upgrade :)
Steps to recreate:

Start with Rancher 2.7.6
Upgrade to v2.8-head
Wait for an hour
Attempt to install CIS chart

@rohitsakala , After the reverts to pull off go-git stuff, this issue should no longer be a blocker right?

Fixed this issue by the following PRs
https://github.com/rancher/rancher/pull/43137
https://github.com/rancher/rancher/pull/43136

Validated with latest 2.8-head v2.8-6cd32b985f0b39ef2eed363458f86a352c67a42b-head
Test Scenarios:
On a HA Rancher setup,

Validated CIS chart can be installed, uninstalled and reinstalled on a upgraded local cluster
Validated CIS chart can be installed, uninstalled and reinstalled on a fresh install local cluster
Validated CIS chart can be installed, uninstalled and reinstalled on a downstream cluster
Validated CIS chart can be upgraded to the latest version
Validated monitoring chart can be installed, uninstalled and reinstalled on a upgraded local cluster

There are additional scenarios covered by Mapps QA team here to ensure there are no regressions


Buttons in Alert examples is sticked to each other

Here is the URL:
http://<IP_ADDRESS>:3000/docs/components/alert/#Alert with buttons.
Buttons should be separate, maybe using ButtonGroup is not correct

@TheHadiAhmadi any udate on this?

@pournasserian we should use ButtonList component instead of ButtonGroup.
I've created an issue for adding ButtonList component

@pournasserian we should use ButtonList component instead of ButtonGroup.
I've created an issue for adding ButtonList component

Does Tabler have that?

Does Tabler have that?

@pournasserian Yes tabler has .btn-list, but bootstrap doesn't have.