bringup checksum error and publish error (have update messages and firmware (shell scripted update, successful)and all others here said

ISSUE TEMPLATE ver. 0.1.0

Which TurtleBot3 you have?

[ X] Burger
[ ] Waffle
[ ] Waffle Pi

Which SBC(Single Board Computer) is working on TurtleBot3?

[ X] Raspberry Pi 3
[ ] Intel Joule 570x
[ ] etc (PLEASE, WRITE DOWN YOUR SBC HERE)

Which OS you installed in SBC?

[ X] Ubuntu MATE 16.04 or later
[ ] Raspbian
[ ] etc (PLEASE, WRITE DOWN YOUR OS)

Which OS you installed in Remote PC?

[ X] Ubuntu 16.04 LTS (Xenial Xerus)
[ ] Ubuntu 18.04 LTS (Bionic Beaver)
[ ] Linux Mint 18.x
[ ] etc (PLEASE, WRITE DOWN YOUR OS)

Write down software version and firmware version

Software version: pc[1.12.12], turtlebot:[1.12.13]
Firmware version: [x.x.x]

Write down the commands you used in order
[Remote PC] roscore
[SBC] roslaunch turtlebot3_bringup turtlebot3_robot.launch

Copy and Paste your error message on terminal

roslaunch turtlebot3_bringup turtlebot3_robot.launch
... logging to /home/pi/.ros/log/5be4951c-8ab2-11e8-9c27-000c29c08b01/roslaunch-raspberrypi-948.log
Checking log directory for disk usage. This may take awhile.
Press Ctrl-C to interrupt
Done checking log file disk usage. Usage is <1GB.
started roslaunch server http://<IP_ADDRESS>:45935/
SUMMARY
PARAMETERS

/rosdistro: kinetic
/rosversion: 1.12.12
/turtlebot3_core/baud: 115200
/turtlebot3_core/port: /dev/ttyACM0
/turtlebot3_lds/frame_id: odom
/turtlebot3_lds/port: /dev/ttyUSB0

NODES
/
turtlebot3_core (rosserial_python/serial_node.py)
turtlebot3_diagnostics (turtlebot3_bringup/turtlebot3_diagnostics)
turtlebot3_lds (hls_lfcd_lds_driver/hlds_laser_publisher)
ROS_MASTER_URI=http://<IP_ADDRESS>:11311
process[turtlebot3_core-1]: started with pid [957]
process[turtlebot3_lds-2]: started with pid [958]
process[turtlebot3_diagnostics-3]: started with pid [959]
[INFO] [1531935538.696228]: ROS Serial Python Node
[INFO] [1531935538.849822]: Connecting to /dev/ttyACM0 at 115200 baud
[ERROR] [1531935541.137422]: Creation of publisher failed: Checksum does not match: d537ed7b8d95065b6c83830430b93911,7250c1dc0b61c4190e78f528f599285f
[INFO] [1531935541.241896]: Note: publish buffer size is 1024 bytes
[INFO] [1531935541.249434]: Setup publisher on version_info [turtlebot3_msgs/VersionInfo]
[INFO] [1531935541.303643]: Setup publisher on imu [sensor_msgs/Imu]
[INFO] [1531935541.335118]: Setup publisher on cmd_vel_rc100 [geometry_msgs/Twist]
[INFO] [1531935541.435899]: Setup publisher on odom [nav_msgs/Odometry]
[INFO] [1531935541.552832]: Setup publisher on joint_states [sensor_msgs/JointState]
[INFO] [1531935541.589040]: Setup publisher on battery_state [sensor_msgs/BatteryState]
[INFO] [1531935541.637533]: Setup publisher on magnetic_field [sensor_msgs/MagneticField]
[INFO] [1531936148.674006]: Setup publisher on /tf [tf/tfMessage]
[ERROR] [1531936148.677219]: Lost sync with device, restarting...
[INFO] [1531936150.080580]: Calibration End
[ERROR] [1531936150.090864]: Creation of publisher failed: Checksum does not match: d537ed7b8d95065b6c83830430b93911,7250c1dc0b61c4190e78f528f599285f
[INFO] [1531936150.097261]: Setup publisher on version_info [turtlebot3_msgs/VersionInfo]
[INFO] [1531936150.103793]: Setup publisher on imu [sensor_msgs/Imu]
[INFO] [1531936150.110164]: Setup publisher on cmd_vel_rc100 [geometry_msgs/Twist]
[INFO] [1531936150.116996]: Setup publisher on odom [nav_msgs/Odometry]
[INFO] [1531936150.123319]: Setup publisher on joint_states [sensor_msgs/JointState]
[INFO] [1531936150.130058]: Setup publisher on battery_state [sensor_msgs/BatteryState]
[INFO] [1531936150.136468]: Setup publisher on magnetic_field [sensor_msgs/MagneticField]
[INFO] [1531936150.143040]: Setup publisher on /tf [tf/tfMessage]
[INFO] [1531936150.221866]: Note: subscribe buffer size is 1024 bytes
[INFO] [1531936150.224826]: Setup subscriber on cmd_vel [geometry_msgs/Twist]
[INFO] [1531936150.305771]: Setup subscriber on sound [turtlebot3_msgs/Sound]
[INFO] [1531936150.430880]: Setup subscriber on motor_power [std_msgs/Bool]
[INFO] [1531936150.515101]: Setup subscriber on reset [std_msgs/Empty]
[ERROR] [1531936150.523830]: Tried to publish before configured, topic id 125
[ERROR] [1531936150.546721]: Mismatched protocol version in packet: lost sync or rosserial_python is from different ros release than the rosserial client
[INFO] [1531936150.549855]: Protocol version of client is unrecognized, expected Rev 1 (rosserial 0.5+)
[ERROR] [1531936150.616131]: Creation of publisher failed: Checksum does not match: d537ed7b8d95065b6c83830430b93911,7250c1dc0b61c4190e78f528f599285f
[INFO] [1531936150.620164]: Setup publisher on version_info [turtlebot3_msgs/VersionInfo]
[INFO] [1531936150.624245]: Setup publisher on imu [sensor_msgs/Imu]
[INFO] [1531936150.628227]: Setup publisher on cmd_vel_rc100 [geometry_msgs/Twist]
[INFO] [1531936150.632148]: Setup publisher on odom [nav_msgs/Odometry]
[INFO] [1531936150.636193]: Setup publisher on joint_states [sensor_msgs/JointState]
[INFO] [1531936150.640280]: Setup publisher on battery_state [sensor_msgs/BatteryState]
[INFO] [1531936150.644530]: Setup publisher on magnetic_field [sensor_msgs/MagneticField]
[INFO] [1531936150.648541]: Setup publisher on /tf [tf/tfMessage]
[ERROR] [1531936150.661293]: Tried to publish before configured, topic id 125
[ERROR] [1531936150.719103]: Creation of publisher failed: Checksum does not match: d537ed7b8d95065b6c83830430b93911,7250c1dc0b61c4190e78f528f599285f
[INFO] [1531936150.723150]: Setup publisher on version_info [turtlebot3_msgs/VersionInfo]
[INFO] [1531936150.727255]: Setup publisher on imu [sensor_msgs/Imu]
[INFO] [1531936150.731219]: Setup publisher on cmd_vel_rc100 [geometry_msgs/Twist]
[INFO] [1531936150.735344]: Setup publisher on odom [nav_msgs/Odometry]
[INFO] [1531936150.739362]: Setup publisher on joint_states [sensor_msgs/JointState]
[INFO] [1531936150.743644]: Setup publisher on battery_state [sensor_msgs/BatteryState]
[INFO] [1531936150.747827]: Setup publisher on magnetic_field [sensor_msgs/MagneticField]
[INFO] [1531936150.751858]: Setup publisher on /tf [tf/tfMessage]
[ERROR] [1531936150.764619]: Tried to publish before configured, topic id 125
[ERROR] [1531936150.789046]: Tried to publish before configured, topic id 125
[ERROR] [1531936150.801361]: Creation of publisher failed: Checksum does not match: d537ed7b8d95065b6c83830430b93911,7250c1dc0b61c4190e78f528f599285f
[INFO] [1531936150.805413]: Setup publisher on version_info [turtlebot3_msgs/VersionInfo]
[INFO] [1531936150.809365]: Setup publisher on imu [sensor_msgs/Imu]
[INFO] [1531936150.813659]: Setup publisher on cmd_vel_rc100 [geometry_msgs/Twist]
[INFO] [1531936150.817781]: Setup publisher on odom [nav_msgs/Odometry]
[INFO] [1531936150.821967]: Setup publisher on joint_states [sensor_msgs/JointState]
[INFO] [1531936150.826421]: Setup publisher on battery_state [sensor_msgs/BatteryState]
[INFO] [1531936150.830538]: Setup publisher on magnetic_field [sensor_msgs/MagneticField]
[INFO] [1531936150.834638]: Setup publisher on /tf [tf/tfMessage]
[ERROR] [1531936150.856827]: Tried to publish before configured, topic id 125
[ERROR] [1531936150.895145]: Creation of publisher failed: Checksum does not match: d537ed7b8d95065b6c83830430b93911,7250c1dc0b61c4190e78f528f599285f
[INFO] [1531936150.899234]: Setup publisher on version_info [turtlebot3_msgs/VersionInfo]
[INFO] [1531936150.903222]: Setup publisher on imu [sensor_msgs/Imu]
[INFO] [1531936150.907468]: Setup publisher on cmd_vel_rc100 [geometry_msgs/Twist]
[INFO] [1531936150.911602]: Setup publisher on odom [nav_msgs/Odometry]
[INFO] [1531936150.915785]: Setup publisher on joint_states [sensor_msgs/JointState]
[INFO] [1531936150.919759]: Setup publisher on battery_state [sensor_msgs/BatteryState]
[INFO] [1531936150.924155]: Setup publisher on magnetic_field [sensor_msgs/MagneticField]
[INFO] [1531936150.929945]: Setup publisher on /tf [tf/tfMessage]
[ERROR] [1531936150.952582]: Tried to publish before configured, topic id 125
[ERROR] [1531936150.983277]: Tried to publish before configured, topic id 125
[ERROR] [1531936151.028752]: Creation of publisher failed: Checksum does not match: d537ed7b8d95065b6c83830430b93911,7250c1dc0b61c4190e78f528f599285f
[INFO] [1531936151.032938]: Setup publisher on version_info [turtlebot3_msgs/VersionInfo]
[INFO] [1531936151.037027]: Setup publisher on imu [sensor_msgs/Imu]
[INFO] [1531936151.041006]: Setup publisher on cmd_vel_rc100 [geometry_msgs/Twist]
[INFO] [1531936151.045335]: Setup publisher on odom [nav_msgs/Odometry]
[INFO] [1531936151.049706]: Setup publisher on joint_states [sensor_msgs/JointState]
[INFO] [1531936151.054034]: Setup publisher on battery_state [sensor_msgs/BatteryState]
[INFO] [1531936151.058484]: Setup publisher on magnetic_field [sensor_msgs/MagneticField]
[INFO] [1531936151.062529]: Setup publisher on /tf [tf/tfMessage]
[ERROR] [1531936151.080259]: Tried to publish before configured, topic id 125
[ERROR] [1531936151.130999]: Tried to publish before configured, topic id 125
[ERROR] [1531936151.158246]: Tried to publish before configured, topic id 125
[ERROR] [1531936151.242376]: Creation of publisher failed: Checksum does not match: d537ed7b8d95065b6c83830430b93911,7250c1dc0b61c4190e78f528f599285f
[INFO] [1531936151.246666]: Setup publisher on version_info [turtlebot3_msgs/VersionInfo]
[INFO] [1531936151.250703]: Setup publisher on imu [sensor_msgs/Imu]
[INFO] [1531936151.254785]: Setup publisher on cmd_vel_rc100 [geometry_msgs/Twist]
[INFO] [1531936151.258764]: Setup publisher on odom [nav_msgs/Odometry]
[INFO] [1531936151.262758]: Setup publisher on joint_states [sensor_msgs/JointState]
[INFO] [1531936151.266865]: Setup publisher on battery_state [sensor_msgs/BatteryState]
[INFO] [1531936151.270952]: Setup publisher on magnetic_field [sensor_msgs/MagneticField]
[INFO] [1531936151.275000]: Setup publisher on /tf [tf/tfMessage]
[ERROR] [1531936151.306376]: Tried to publish before configured, topic id 125
[ERROR] [1531936151.330698]: Tried to publish before configured, topic id 125
[ERROR] [1531936151.339339]: Creation of publisher failed: Checksum does not match: d537ed7b8d95065b6c83830430b93911,7250c1dc0b61c4190e78f528f599285f
[INFO] [1531936151.343573]: Setup publisher on version_info [turtlebot3_msgs/VersionInfo]
[INFO] [1531936151.347560]: Setup publisher on imu [sensor_msgs/Imu]
[INFO] [1531936151.351830]: Setup publisher on cmd_vel_rc100 [geometry_msgs/Twist]

Hi :)
Because the version between software and firmware has crashed, the error is occurred.
Update all the latest version and try launch again. I attached reference for installation instruction.
https://discourse.ros.org/t/announcing-turtlebot3-software-v1-0-0-and-firmware-v1-2-0-update/4888

works like a charm. thank you very much.

Thanks, If you have any further questions, please feel free to open new issue page.

Hi,
though I have updated both software and firmware. I keep getting this error and then goes on in a loop.
roslaunch turtlebot3_bringup turtlebot3_robot.launch
... logging to /home/ubuntu/.ros/log/84f26836-9e9a-11eb-907b-c83dd43d6ebb/roslaunch-ubuntu-3151.log
Checking log directory for disk usage. This may take a while.
Press Ctrl-C to interrupt
Done checking log file disk usage. Usage is <1GB.
started roslaunch server http://<IP_ADDRESS>:38501/
SUMMARY
PARAMETERS

/rosdistro: melodic
/rosversion: 1.14.10
/turtlebot3_core/baud: 115200
/turtlebot3_core/port: /dev/ttyACM0
/turtlebot3_core/tf_prefix:
/turtlebot3_lds/frame_id: base_scan
/turtlebot3_lds/port: /dev/ttyUSB0

NODES
/
turtlebot3_core (rosserial_python/serial_node.py)
turtlebot3_diagnostics (turtlebot3_bringup/turtlebot3_diagnostics)
turtlebot3_lds (hls_lfcd_lds_driver/hlds_laser_publisher)
ROS_MASTER_URI=http://<IP_ADDRESS>:11311
process[turtlebot3_core-1]: started with pid [3160]
process[turtlebot3_lds-2]: started with pid [3161]
process[turtlebot3_diagnostics-3]: started with pid [3162]
[INFO] [1618567492.198433]: ROS Serial Python Node
[INFO] [1618567492.235257]: Connecting to /dev/ttyACM0 at 115200 baud
[INFO] [1618567494.356556]: Requesting topics...
[INFO] [1618567494.415237]: Note: publish buffer size is 1024 bytes
[INFO] [1618567494.423652]: Setup publisher on sensor_state [turtlebot3_msgs/SensorState]
[INFO] [1618567494.444378]: Setup publisher on firmware_version [turtlebot3_msgs/VersionInfo]
[INFO] [1618567495.035184]: Setup publisher on imu [sensor_msgs/Imu]
[INFO] [1618567495.058103]: Setup publisher on cmd_vel_rc100 [geometry_msgs/Twist]
[ERROR] [1618567495.138581]: Creation of publisher failed: nav_msgs
ROS path [0]=/opt/ros/melodic/share/ros
ROS path [1]=/home/ubuntu/catkin_ws/src
ROS path [2]=/opt/ros/melodic/share
[INFO] [1618567495.159651]: Setup publisher on joint_states [sensor_msgs/JointState]
[INFO] [1618567495.179594]: Setup publisher on battery_state [sensor_msgs/BatteryState]
[INFO] [1618567495.203986]: Setup publisher on magnetic_field [sensor_msgs/MagneticField]
[INFO] [1618567498.116951]: Setup publisher on /tf [tf/tfMessage]
[INFO] [1618567498.144873]: Note: subscribe buffer size is 1024 bytes
[INFO] [1618567498.155490]: Setup subscriber on cmd_vel [geometry_msgs/Twist]
[INFO] [1618567498.181052]: Setup subscriber on sound [turtlebot3_msgs/Sound]
[INFO] [1618567498.207696]: Setup subscriber on motor_power [std_msgs/Bool]
[INFO] [1618567498.231552]: Setup subscriber on reset [std_msgs/Empty]
[INFO] [1618567498.255811]: Setup TF on Odometry [odom]
[INFO] [1618567498.266555]: Setup TF on IMU [imu_link]
[INFO] [1618567498.276867]: Setup TF on MagneticField [mag_link]
[INFO] [1618567498.286379]: Setup TF on JointState [base_link]
[INFO] [1618567498.302020]: --------------------------
[INFO] [1618567498.311337]: Connected to OpenCR board!
[INFO] [1618567498.320980]: This core(v1.2.2) is compatible with TB3 Burger
[INFO] [1618567498.334510]: --------------------------
[INFO] [1618567498.345775]: Start Calibration of Gyro
[INFO] [1618567500.818804]: Calibration End
[ERROR] [1618567500.841298]: Tried to publish before configured, topic id 129
[INFO] [1618567500.852438]: Requesting topics...
[INFO] [1618567500.869723]: Setup publisher on sensor_state [turtlebot3_msgs/SensorState]
[INFO] [1618567500.881724]: Setup publisher on firmware_version [turtlebot3_msgs/VersionInfo]
[INFO] [1618567500.899354]: Setup publisher on imu [sensor_msgs/Imu]
[INFO] [1618567500.911653]: Setup publisher on cmd_vel_rc100 [geometry_msgs/Twist]
[ERROR] [1618567500.925351]: Creation of publisher failed: nav_msgs
ROS path [0]=/opt/ros/melodic/share/ros
ROS path [1]=/home/ubuntu/catkin_ws/src
ROS path [2]=/opt/ros/melodic/share
[INFO] [1618567500.938445]: Setup publisher on joint_states [sensor_msgs/JointState]
[INFO] [1618567500.951913]: Setup publisher on battery_state [sensor_msgs/BatteryState]
[INFO] [1618567500.963860]: Setup publisher on magnetic_field [sensor_msgs/MagneticField]
[INFO] [1618567500.975694]: Setup publisher on /tf [tf/tfMessage]
[ERROR] [1618567501.025573]: Tried to publish before configured, topic id 129
[INFO] [1618567501.032640]: Requesting topics...
[ERROR] [1618567501.104685]: Tried to publish before configured, topic id 129
[INFO] [1618567501.113985]: Requesting topics...
[ERROR] [1618567501.154256]: Tried to publish before configured, topic id 129
[INFO] [1618567501.163307]: Requesting topics...
[ERROR] [1618567501.199294]: Tried to publish before configured, topic id 129
[INFO] [1618567501.208329]: Requesting topics...


Merge concepts of the proposed render extension

The render extension has been proposed and we should either merge them or be clear about the purposes of each.
Both the render and web-map-links address the need to support visualizing raster data. web-map-links addresses this by defining link types for different visualization (or tiling) APIs. web-map-links supports parameters used to render raster data into image tiles via parameters included in href strings (I assume, I haven't seen an example that does this yet). The render extension, since it is mostly referring to dynamic tiling, overlaps with the xyz, wmts and proposed OGC-Tiles but explicitly includes those render parameters as part of its schema, which is separate from links.
I wonder if these 2 specs could be merged. From what I can tell web-map-links focuses on what API servers are available to render the data and render focuses on what parameters to pass to those servers. Would it make sense to merge these two specs?
A few options:

Add a titiler link type which includes those titiler parameters
Since titiler implements xyz, wmts and ogc tiles, than render parameters should be part of the spec for all of those link types
We keep the render extension separate, but presumably if some collection/item includes a link to a titiler instance in links, it would also include the render extension. And perhaps the render extension could grow in scope to consider the use cases of parameters which needs to be handled by the other tiling services.

@m-mohr @smohiudd @vincentsarago

As discussed on the STAC sprint this is related to this extension, but it will eventually be more capabale once templates links are defined by OGC. And then there's also the processing and composite extension that seem to do similar things. A combination of these extensions may replace the render extension.

Just to be clear, the render template is not a link, I think the goal of the render extension is to give hint about how an assets or set of assets can be rendered, without giving much information about a possible tiling service (meaning that the render information can be used by any client (tiling services or scripts)

@vincentsarago I think the composite extension can handle what the render extension is trying to achieve and I think the goal is to limit the number of extensions if possible to reduce the need to duplicate information across fields and increase adoption, so if we can appropriately modify or leverage an existing extension to meet our needs we should do so.
If I understand correctly, there are 2 things being proposed:

Use template-d links (@m-mohr suggested this as potentially superceding the current web-map-links but I can't find the OGC information about it) for tiling APIs to publish the existence of a service which supports a collection or item
Use the composite extension (which combines the use of virtual:assets, raster:bands, and processing:expression) to address the need to store tiling parameters in metadata


[Feature]: optional message on wandb.finish(..)

Description
Need the option to add a message to finish.
finish(
exit_code: Optional[int] = None,
message: Optional[str] = None,
quiet: Optional[bool] = None
) -> None
Suggested Solution
Should send the finish message to mail/slack, etc as well.
Alternatives
No response
Additional Context
No response

Hey @SushantGautam, thanks for writing in! Would using alerts (see our docs here) work for you?

I mean there is already a default alert on job finish that notifies through email/slack.
The idea:
I would like to avoid double alerts. So just want to embed the message on finish and send.

Got it, thanks for sharing this @SushantGautam! I'll create a feature request for you and share it internally


Fix a use-after-free bug on Win32 when calling lookupSymbol()

Fix a use-after-free bug on Win32 when calling lookupSymbol(). This function populates a structure SymbolInfo containing a field symbolName that is a std::unique_ptr<char, ...>. Several callers of this function get the underlying C string and pass it beyond the scope of the SymbolInfo instance. Thus, the field can be destructed before the string is used.
On platforms with dladdr(), the string in question is globally owned, so no use-after-free occurs. On Windows, the string is owned by the SymbolInfo structure and is freed when it is destructed. Hence, use-after-free occurs.
This change:

Moves SymbolInfo to its own file and provides functions to access its fields, to reinforce that they belong to the symbol info structure and not to the caller.
Removes the duplicate implementations of lookupSymbol().
Fixes call sites to use the accessor functions.
Modifies call sites that use symbolName after the structure dies to ensure they copy the string. The overhead of copying the string should be swamped by the overhead of calling dladdr() or SymFromAddr().

@swift-ci please test

@swift-ci please test

@swift-ci please test

@swift-ci please test

@swift-ci please test

@swift-ci please clean test linux

@swift-ci please test

@swift-ci please test

Failures don't look related to this branch. Trying clean builds.

@swift-ci please clean test

@swift-ci please test


Allow users to invite from Discord Bot List

Currently the bot is designed to work on one server. It requires the following:

3 channels for:

Submissions
Voting
Results

Admin
Server ID

If the user has a way of configuring these using bot commands or another method, then it could potentially work.
This idea has been explored in a new branch called servers.

for on_message, you will need to check which server the user came from. If they come from an known server, add the server object, otherwise create an object for their server in the json.
The server json objects should be the IDs of the servers stored as strings, but converted to ints in python when used.

Closing for now as it's not an important thing. Keeping it internal for now


Feature request: support DynamoDB image values to dict with built-in Python types

Use case
When using DynamoDBRecord class, the values for old_image and new_image are represented as Dict[str, AttributeValue]. This representation is sufficient when the data parsed is simple and does not contain nested maps/lists.
But when the data parsed contains nested maps/lists, then it becomes hard to get to the data that AttributeValue represents.
One would need to recursively parse the AttributeValue objects in the nested dicts to get to the underlying data.
Solution/User Experience
Using a deserializer similar to the TypeDeserializer provided by boto3 (link to code), one would be able to convert image to a Python dict where the values would be built-in Python types.
Alternative solutions
No response
Acknowledgment

[X] This feature request meets Lambda Powertools Tenets
[ ] Should this be considered in other Lambda Powertools languages? i.e. Java, TypeScript

Thanks a lot for taking the time to raise it Ahmed. I can’t wait to see
this PR.
On Sun, 7 Aug 2022 at 20:20, boring-cyborg[bot] @.***>
wrote:

Thanks for opening your first issue here! We'll come back to you as soon
as we can.
—
Reply to this email directly, view it on GitHub
https://github.com/awslabs/aws-lambda-powertools-python/issues/1432#issuecomment-1207460500,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAZPQBFDAIJWNCR57BOXDSTVX75ARANCNFSM5523LQSA
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***
com>

did you try using the parser? you can specify models for the images and it all gets parsed nicely.
https://awslabs.github.io/aws-lambda-powertools-python/latest/utilities/parser/#built-in-envelopes
There's a DynamoDBStreamEnvelope class.
It seems like the data classes features is trying to implement parsing features IMO.

@ran-isenberg the problem in our case was that the service was not using Pydantic, and we did not want to introduce it only to parse the DynamoDB record.
I agree that there is an overlap between data classes and Parser, but IMO data classes should still allow traversing the fields of a record.

hey @shanab Ahmed, checking in to see if you still have the bandwidth to contribute as you already had the code working.
Thank you!

@heitorlessa yes, I should have time this week to have a first draft. Sorry for leaving this open until now!

What about using boto3's TypeDeserializer ?

What about using boto3's TypeDeserializer ?

That can be an option, but to my knowledge then one would not be able to do the following:
@event_source(data_class=DynamoDBStreamEvent)
def lambda_handler(event: DynamoDBStreamEvent, context):
    pass

because you'd need the raw Python dictionary for NewImage and OldImage to be able to use TypeDeserializer, and the event won't expose that.

Released in V2 now ;) https://github.com/awslabs/aws-lambda-powertools-python/releases/tag/v2.0.0


[ts] Question: Types for entity relationships fetched via custom field resolvers

Assuming this schema:
type Author {
  id: ID!
  name: String!
}

type Article {
  id: ID!
  authorId: ID!
  author: Author!
  title: String
}

type Query {
  randomArticle: Article
}

The resolver type for Query.randomArticle query requires me to return an object with both author/title.
However, I want to define the author fetching in a field resolver of Article:
const resolvers = {
  Article: {
    author: obj => DB.authors.find(obj.authorId)
  },

  Query: {
    randomArticle: async () => {
      const a = await DB.articles.random()
      return {
        id: a.id,
        title: a.title,
        authorId: a.authorId,
      }
    }
  }
}

The generated type of randomArticle requires a mandatory author, but my implementation is somewhere else. I acknowledge author is possibly null, but I'd like to rely on GQL's schema validation, and not to have to make author optional.
The problem comes when a client type is generated with an optional author on an Article object. It forces me to test for if (article.author) in strict TypeScript.
My current workaround is to fake force casting the returned object as the full object, relying on the field resolver to fill the value in, and GQL schema validator to validate nothing is missing:
// ...

  Query: {
    randomArticle: async () => {
      const a = await DB.articles.last()
      return {
        id: a.id,
        title: a.title,
        authorId: a.authorId,
      } as Article // <--- this
    }
  }

Thoughts? Any better solution?

Hi @elado !
We have mapping configuration that allow you to specify custom object types for the resolvers plugin, please take a look here: https://graphql-code-generator.com/docs/plugins/typescript-resolvers
You can also specify generics to the resolver signature to override the parent/return type of the resolvers.


CAPM-based multiteant business applications with the HDI-Container separation approach.

SaaS / Multitenant Business Application / DB schema separation approach with CAPM.

Actually the Multi tenant aspects would be a bit complicated to integrate into this particular sample and would cause it to not be reproducible on the free trial landscape. So I'm afraid that would exclude it from here. However there is a colleague that is researching this specific topic and plans to publish some standalone content (probably a blog) on the topic.

Ich kann das nachvollziehen. Dann halte ich die Augen auf in der Hoffnung the von dir erwähnte publikation zu finden. Thanks!


Airlock manager can create user resources

Resolves #2499
What is being addressed
Adding Airlock Manager role to allow creation of a user resource
How is this addressed

Add get_current_workspace_owner_or_researcher_user_or_airlock_manager to Workspaces.py Router and Create user resource method.
For VM templates intended to be used by researchers (windowsvm and linuxvm), add authorizedRoles clause to include WorkspaceOwner and WorkspaceResearcher (so that Airlock Managers can't use them)

/test 777b72db4dc77e90208c4ed711561218164d8c27

/test 469d811468858a5d39f74f0ad056c2a3f9d33acf

Thanks, @JaimieWi, for this PR.
As we've discussed elsewhere, and based upon feedback, we're going to go in a slightly different direction.
I'm going to close this PR without merging.

The PR has been reopened: as https://github.com/microsoft/AzureTRE/pull/2623 is now in main, we can make use of authorizedRoles field in resource template and restrict template intended to be used by Researchers

/test

/test 777b72db4dc77e90208c4ed711561218164d8c27

/test b1a9a69cd3b8eb3fb07f071878b3a6d3c43476f3

Closing this as the work is complete in https://github.com/microsoft/AzureTRE/pull/2649


[Blackhole bringup] CommandQueueFixture.StressWrapTest hanging

Maybe related to some of the other errors. Needs further debug.
Machine needs to be power cycled through tt-board to get back into a usable state :(

Works when dram bank size is reduced from (4GB - 16MB) to 2 GB. This is because the upper 2GB of DRAM are untested on syseng-16


Replace git-changelog with conventional-changelog?

Previously, we prefer git-changelog because it is Python based application that can be easily installed, but acctually, we only need it in CI/CD, so maybe conventional-changelog is a more popular choice.
Ref:

https://github.com/conventional-changelog/conventional-changelog

or maybe we should integrate with semantic-release directly.

Close as we will keep current release process.


Group behavior change when deleting child monitor that has a "down" status

📑 I have found these related issues/pull requests
Can't find a related request.
🏷 Feature Request Type
Dashboard
🔖 Feature description
Current behavior:
When a child monitor is reporting down, the group its in will also report "down", but when you delete the child monitor from the group, the group status will remain in a "down" state until the next heartbeat.
✔ Solution
I suggest that if you delete a child that has a "down" status, this should trigger a heartbeat check of the entire group and therefore if there are no other issues, the group status should immediately return to green (up) status.
❓ Alternatives
No
📝 Additional Context
No response

Duplicate of https://github.com/louislam/uptime-kuma/issues/4572
=> closing as a duplicate
We know that the current behaviour is somewhat counterintutive, but resources..


Extraneous text on generated page.

On https://docs-dev.raku.org/syntax/S%2F%2F%2F non-destructive substitution reached by a search for s/ and selecting s/ / / , from  the composite options, the output's first body-line is:
 "See primary documentation in context for Lexical conventions 0"

The doc source shows nothing obvious that would create the '0'.

@0rir Sorry for the delay. Not sure how I missed these issues for so long.
If you go to the eventual destination page for s/ / / and look at the contents panel, then restrict the content lines by typing 'lexical' in the filter bar in the contents panel, then ...
you will find there are two headings with the same name. The renderer appends a _0 to the second (_1 to the next etc) occurrence so that a unique target is created for the URL.
So in one sense this occurs because there are two headings with the same name in the source.
But it could be seen as rendering error in that whatever the link is, it should not appear in the rendering.
I'll fix the rendering. (It seems to be in exactly the same place as the missing '.')

closing as completed with new PR


Consider a dedicated IntelliJ project generator template

Consider whether it's worth adding a dedicated "A+ Courses" project template in the IntelliJ's "New project" window, in the section marked on the screenshot above.
Note that it wouldn't actually do anything special, it would be the same thing as a generic, empty, module-less project. However it might make users less confused, especially that now there's a difference between "New project" and "Empty project".

Demonstrate in the next weekly, and make the decision whether or not we want this.


Allow android to respect currentPage setting

#81

@phil-r what do you think about this? It is not the prettiest workaround, but it fixes the problem.
We are using this patch and it seems to work fine on both platforms.

Sure, we need to merge this if it helps!


Nothing append

Hello did you know why nothing append ???

Wait or check your internet connection

Wait or check your internet connection
my connection is good and I waited one night, and nothing happens

Have you created a session?


Potential Enhancement - Adding transaction to "Budget"

Enhancement Idea:
Uplift the tool to allow for both categorisation and listed what "budget" it belongs to.
Training for budget name in the same way that the tool does for categorisation.
My use case:  Budget is a budget group, yes, but it's also the high-level classification of the transaction.  Then the categorisation is used for fine-grained classification of a transaction.
E.g. Coles Supermarket = Budget: FOOD AND DINING; Category: GROCERY
E.g. Uber Eats = Budget: FOOD AND DINING; Category: FOOD DELIVERY
E.g. Optus Billing Services = Budget: UTILITIES; Category: PHONE/INTERNET
E.g. Red Energy = Budget: UTILITIES; Category: ELECTRICITY
E.g. Westpac General Ins = Budget: INSURANCE; Category: HOME INSURANCE
E.g. NRMA = Budget INSURANCE; Category: AUTO INSURANCE
Implimentation idea:

Add-on functionality of the existing ffiiitc tool and each web-hook completes both the budget and category
a. if existing budget exists on the transaction, skip

It looks as if the ffiii API would allow for this, based on my search.
Get -> /v1/budgets |  List all budgets
Post -> /v1/transactions | Store a new transaction
"budget_id": "4",
"category_id": "43",
"category_name": "Groceries",

Thanks, added this to the enhancements.

Great news. Looking forward to giving it a try.


Add .pre-commit-config.yaml

Store all tools' configurations in pyproject.toml,
even if right now only the setup.py file is used.
Keep .pylintrc separately.
It is 300 lines; default --generate-toml-config gives 600 😅
Signed-off-by: Stavros Ntentos<EMAIL_ADDRESS>

@Pierre-Sassoulas here is the .pre-commit-config.yaml. Feel free to extend it, if you wish 🙏

WDYM? Remove the sha1 from the file AKA "not-ignore" its blame?

My bad I thougth it was a mistake in a changelog 😅


Column width option does not work

Description
The following setting:
plotOptions: {
                bar: {
                    columnWidth: '90%',
                },
            },

does not work as expected
We have a stacked bar chart of variable width (typically about 1200px) with variable number of bars (10 to 100, depending on the chosen time resolution).

Expected Behavior
Each bar should take 90% of the available width.
Actual Behavior
Sometimes it works but sometimes it does not (see the screenshots)
Screenshots

Reproduction Link

Did not provide required reproduction


Update benchmarks (.NET 8 only)

Bump to BenchmarkDotNet 0.13.11-nightly.20231116.103 to get AVX-512 info.

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Comparison is base (de3d2e6) 99.26% compared to head (cb5a0f0) 98.56%.

Additional details and impacted files
@@            Coverage Diff             @@
##             main      #64      +/-   ##
==========================================
- Coverage   99.26%   98.56%   -0.70%
==========================================
  Files          41       41
  Lines        2715     2715
  Branches      284      283       -1
==========================================
- Hits         2695     2676      -19
- Misses         18       26       +8
- Partials        2       13      +11

Flag
Coverage Δ

Debug
98.56% <ø> (ø)

Release
?

macos-latest
?

ubuntu-latest
98.56% <ø> (-0.45%)
:arrow_down:

windows-latest
?

Flags with carried forward coverage won't be shown. Click here to find out more.

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Adding pause support from external components.

Because the player plays when you switch page one of the requirements was to pause playing on all players. So I added a pause function.
Realized that I forgot the submit this.before Polymer Summit. :)
Here is a mobile phone commit, sorry for indentation errors.

Thanks @kalaspuffar! 👍 Could you cover it with tests?


Fixed typos

You, @pborreli , have the distinct honor of being the very first external contributor to the new Docker docs repo! Congratulations!
This isn't the production repo YET, but it will be by October 3rd. We're going to do a final content pull on Wednesday, at which time we can merge this (and hopefully there won't be conflicts).
Thank you so much, from the entire Docker docs team!

thank you, no problem I will resolve if conflicts, keep the good work 🐳

Can you please rebase this on current master and reopen? Sorry for the inconvenience. We had to pull in all the old commit history.

I don't see the option to reopen this PR 😞

Sorry about that. You might need to open a new PR. Hopefully this was a one time problem because the repo was not really ready for PRs yet.

On Sep 30, 2016, at 11:47 AM, Pascal Borreli<EMAIL_ADDRESS>wrote:
I don't see the option to reopen this PR 😞
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub, or mute the thread.

Pascal already took care of it, and we got his fixes in. :)
On Fri, Sep 30, 2016 at 1:41 PM, Misty Stanley-Jones <
<EMAIL_ADDRESS>wrote:

Sorry about that. You might need to open a new PR. Hopefully this was a
one time problem because the repo was not really ready for PRs yet.

On Sep 30, 2016, at 11:47 AM, Pascal Borreli<EMAIL_ADDRESS>wrote:
I don't see the option to reopen this PR 😞
—
You are receiving this because you modified the open/close state.

Reply to this email directly, view it on GitHub, or mute the thread.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/docker/docker.github.io/pull/15#issuecomment-250847141,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AFMAfz0e2gcg6iyhfJj96P_C4vBft7CWks5qvXPvgaJpZM4KFdGS
.

--
John Mulhausen
Lead Technical Writer, Docker
<EMAIL_ADDRESS>| GitHub/Docker ID: @johndmulhausen


fix: Add opacity to plot selection

Some plotters still had fully black objects in the scene due to plot selection not being able to separate edges from faces. This PR adds transparency to all objects represented through plot_selection.

Yep, go ahead! 😄


Update path to new prospectus

The prospectus was updated and should be updated on the webpage - https://blackpythondevs.com/leadership-summit-2024.
new prospectus path is - https://drive.google.com/file/d/1W-tdNcOiylVB7a3LzUj3oTtfCzWNNIzc/view?usp=sharing

Hi, Can you assign this task to me?Thanks


ESP8266 Wifi module config support via UART

The ESP8266 Wifi module is an ultra-low-cost serial to WIFI bridge ($7.00!) which could serve as a Wifi telemetry link for smartphones. It can be configured as access point: http://tech.scargill.net/esp8266-as-an-access-point/
It can be obtained from here:
https://www.sparkfun.com/products/13678
What we need is:

A small AT command parser / config library in src/lib which configures this module

SSID
UDP mode
IP of the GCS
baud rate

A MAVLink message which contains the SSID and password and sets a flag wether to create this network or join an infrastructure one. There should also be a way to request the existing settings from the GCS side.
The MAVLink instance listening on USB could relay the configuration to the MAVLink instance listening on the serial port where the ESP8266 is connected, allowing the GCS to set up the module via USB

@DonLakeFlyer @dogmaphobic I believe spending time on this is much more worthwhile compared to messing with the broken mobile serial port support. Do we have Android / iOS instructions somewhere already? I would love to start to get my hands dirty.

Where do you see this running? On the drone side or on the QGC side? I'm not sure I understand how this could be used without some extra hardware.

On the drone side of course. The MAV can host an AP and the rest of our GCS devices can connect to it using their in-built wireless radios.
The only thing I'm concerned about is the range. The internal radios on the tablet/laptop would be the limiting factor.

Just a comment: To my knowledge, the use of WLAN is not allowed on board of airborne systems. I can check the reference, but it should be written somewhere in the part of the documents, you normally don't read. Honestly speaking, I'm not 100'% sure and also, it could be the decision to ignore this "formality", and yes, I know there are plenty of WLAN based systems out there.

I'd appreciate a reference if you can find one and also where it applies.
On Sat, 15 Aug 2015 21:54 hkld<EMAIL_ADDRESS>wrote:

Just a comment: To my knowledge, the use of WLAN is not allowed on board
of airborne systems. I can check the reference, but it should be written
somewhere in the part of the documents, you normally don't read. Honestly
speaking, I'm not 100'% sure and also, it could be the decision to ignore
this "formality", and yes, I know there are plenty of WLAN based systems
out there.
—
Reply to this email directly or view it on GitHub
https://github.com/PX4/Firmware/issues/2666#issuecomment-131438331.

A collegue of mine pointed me to the source ... it's not a general issue, but a German legislation linked to the frequency regulations. It is written that the use of the frequencies 5470 - 5725 MHz for WLAN is not permitted for connections between aircrafts and ground stations ... see the following link (in German), footnote #6
http://www.bundesnetzagentur.de/SharedDocs/Downloads/DE/Sachgebiete/Telekommunikation/Unternehmen_Institutionen/Frequenzen/Allgemeinzuteilungen/2010_07_WLAN_5GHz_pdf.pdf?__blob=publicationFile
Therefore 2.4GHz is probably not an issue. In Austria the frequencies 5470 – 5750 MHz are allowed for outdoor applications, but there is no limitation concerning applications on aircrafts, see (also in German):
https://www.rtr.at/de/tk/Spektrum5GHz/1997_bmvit-info-052010de.pdf

@dogmaphobic Glad we almost fixed this 8). This is to track the ESP8266 SSID config we discussed.

Done via wifi - closing.


Error after updating Vue to v2.1.5

The following error was triggered after Vue has been updated to v2.1.5.

Thank you.

This is also happening in vuex-toast so I think its a problem with the 2.1.5 release

Agreed, and it looks like they've just released v2.1.6.
Errors are the same for v2.1.6.

Same issue.Need to fallback to v2.1.4.

I believe you just need to rebuild the dist, looks like this is the culprit https://github.com/vuejs/vue/commit/4b51ad048306367a6fb6fbee7445e086d855f31e

Thank you all very much! I already rebuild it with the latest vue-template-compiler and release a new version v2.0.0-rc.4, you can upgrade it with npm, please tell me if it still has problem :P

Thank you @PeachScript @RDelorier. I have tested<EMAIL_ADDRESS>with<EMAIL_ADDRESS>and they are working great! 👍


Stuck on loading pyv8 binary, please wait

I just updated ST Dev from build 3175 to 3179 and suddenly I am seeing pyv8 binary loading is taking forever.
PyV8: Creating new thread
Emmet: Creating thread
Emmet: Loading https://api.github.com/repos/emmetio/pyv8-binaries/contents

And I am not sure if this is related to emmet but I also have save_on_focus_lost: true enabled in my settings but that's not working either after I updated ST3.
In some other related issue I found that this could also be an issue related to proxy. However when I visit https://api.github.com/repos/emmetio/pyv8-binaries/contents the server respond is ok.
My OS: Linux

It's a similar issue to #703

And yes, save_on_focus_lost: true issue IS in fact related to emmet. How do I know? When I disable emmet it starts to work again.

Yes, it's loading forever in builds 3179 and 3180 for me as well (Ubuntu 64-bit).

It's loading forever in builds 3179 and 3180 for me too. Debian stretch x64.

I'm seeing this too on build 3180. Switching back to 3176 for now.

It's not necessarily stuck loading forever for me, it just loads extremely slow every time I start Sublime Text which kind of ruins the point of Sublime Text for me and makes this addon pointless for me to use. I use Sublime Text for it to be fast, and sadly, with this, it is not fast.

@sergeche Are the build scripts for PyV8 public somewhere? What compilers are you using for the various platforms?

@wbond Don‘t know, actually. The original PyV8 bundle was made by @sublimator
Also, I have upcoming new Emmet 2 code base, which is smaller and faster and we may not need a heavy PyV8. We can discuss it somewhere in chat

@sergeche is there any ETA for the upcoming V2?

Sorry, no ETA yet, too busy on my job

Just a FYI, this issue may have been solved since Sublime Text 3192.

Emmet works on Debian stretch x64 and Win10 with build 3194, 3195.


Bug: The debug adapter has terminated abnormally.

Trying to debug some async rust code.
#[tokio::test]
async fn test_async_binary_semaphone() {
    let s = tokio::sync::Semaphore::new(1);   // add a breakpoint, at this line
    println!("{:?}", s.available_permits());
    let sp = s.acquire().await.unwrap();
    println!("{:?}", s.available_permits());
    drop(sp); // release the permit
}

Cargo.toml file:
[dependencies]
tokio = { version = "1", features = ["full"] }

This would create this error:
configuration: {
  type: 'lldb',
  request: 'launch',
  name: 'test test_async_binary_semaphone',
  program: '${workspaceFolder}\\target\\debug\\deps\\page_lock-fb9ac44b70f6a5b8.exe',
  args: [ 'test_async_binary_semaphone', '--exact', '--nocapture' ],
  cwd: '${workspaceFolder}',
  sourceLanguages: [ 'rust' ],
  ...
}
Listening on port 14341
error: page_lock-fb9ac44b70f6a5b8.exe :: Class 'core::future::from_generator::GenFuture<tokio::net::windows::named_pipe::impl$4::ready::generator$0>' has a member '__0' of type 'generator$0' which does not have a complete definition.
[adapter\src\terminal.rs:104] FreeConsole() = 1
[adapter\src\terminal.rs:105] AttachConsole(pid) = 1
[adapter\src\terminal.rs:109] FreeConsole() = 1
error: page_lock-fb9ac44b70f6a5b8.exe :: Class 'enum$<core::option::Option<core::ptr::non_null::NonNull<tokio::runtime::task::core::Header> >, 1,<PHONE_NUMBER>3709551615, Some>::Some' has a member '__0' of type 'core::ptr::non_null::NonNull<tokio::runtime::task::core::Header>' which does not have a complete definition.
error: page_lock-fb9ac44b70f6a5b8.exe :: Class 'tokio::util::linked_list::PointersInner<tokio::io::driver::scheduled_io::Waiter>' has a member 'prev' of type 'enum$<core::option::Option<core::ptr::non_null::NonNull<tokio::io::driver::scheduled_io::Waiter> >, 1,<PHONE_NUMBER>3709551615, Some>' which does not have a complete definition.
error: page_lock-fb9ac44b70f6a5b8.exe :: Class 'tokio::util::linked_list::PointersInner<tokio::time::driver::entry::TimerShared>' has a member 'prev' of type 'enum$<core::option::Option<core::ptr::non_null::NonNull<tokio::time::driver::entry::TimerShared> >, 1,<PHONE_NUMBER>3709551615, Some>' which does not have a complete definition.
error: page_lock-fb9ac44b70f6a5b8.exe :: Class 'tokio::util::linked_list::PointersInner<tokio::sync::notify::Waiter>' has a member 'prev' of type 'enum$<core::option::Option<core::ptr::non_null::NonNull<tokio::sync::notify::Waiter> >, 1,<PHONE_NUMBER>3709551615, Some>' which does not have a complete definition.
error: page_lock-fb9ac44b70f6a5b8.exe :: Class 'tokio::util::linked_list::PointersInner<tokio::sync::batch_semaphore::Waiter>' has a member 'prev' of type 'enum$<core::option::Option<core::ptr::non_null::NonNull<tokio::sync::batch_semaphore::Waiter> >, 1,<PHONE_NUMBER>3709551615, Some>' which does not have a complete definition.

thread 'main' has overflowed its stack
Debug adapter exit code=3221225725, signal=null.

I can independently reproduce this on my own tokio project as well.

3221225725 = 0xc00000fd aka "stack overflow"

@chamons thank you. same here.

@vadimcn the same my project does not reproduce the issue when I build on:
Default host: x86_64-unknown-linux-gnu
stable-x86_64-unknown-linux-gnu (default)
rustc 1.60.0 (7737e0b5c 2022-04-04)
It happens on Windows.

Hi!
The issues doesn't reproduce on macOS for me, but it does on Windows.

Same here but as a workaround I`m using
"type": "cppvsdbg", instead of "type": "lldb".
https://github.com/vadimcn/vscode-lldb/issues/635#issuecomment-1047011456 does not worked for me.

"type": "cppvsdbg", instead of "type": "lldb".

Does not work for me, I get: "Error processing launch options at field: program"

Is this problem still being worked on ... ?

Not directly.   I do upgrade the bundled LLDB when a new version comes out, so bugs might get fixed eventually.   Currently I am preparing a release based on LLDB v16, you can try it out here.

Thanks for the feedback.
Whilst still hopeful that this issue on Windows may get fixed one day, for now I decided to switch to Linux (Ubuntu 18.04). And there my debugging works fine; no problems encountered yet.
Cheers,
Peter

@Peter-J-Jansen Would you mind checking if you still get a stack overflow on Windows with that build?

OK, I'll try to do that the next few days. I've already downloaded "codelldb-x86_64-windows.vsix" (about 40 MB), but how do I go about and update what I current have on vscode ? So far I've only ever installed vscode extensions by clicking on the "install" button they all have. And if this ".vsix" makes things worse, how can I back out and revert to what I have right now ?
Cheers,
Peter

I've already downloaded "codelldb-x86_64-windows.vsix" (about 40 MB), but how do I go about and update what I current have on vscode

Use "Extensions: Install from VSIX" command, pick the file you've downloaded.

And if this ".vsix" makes things worse, how can I back out and revert to what I have right now ?

Open the Extensions side panel, find CodeLLDB, click the gear button, choose "Install Another Version...".

Minimal test case:
#[cfg(test)]
mod test {
    fn get_foo_fn() -> impl Fn() -> () {
        let foo = 0;
        move || {
            // put a breakpoint here to trigger a stack overflow when starting debugging
            let _a = foo;
        }
    }

    #[test]
    // as long as I'm present, I will bork debugging
    fn bork_debugging() {
        let _tile_fn = get_foo_fn();
    }

    #[test]
    fn empty_test() {
        // trying to debug me will trigger a stack overflow
    }
}

CodeLLDB: 1.9.0
TL;DR: Workaround is to not put breakpoints in capturing lambdas returned by functions. Or I guess just try to disable all your breakpoints and see if that helps.

@johanhelsing -msvc target?   Yeah, that's known to happen...

If I use "launch" rerquest in launch.json instead of "cargo", the debugger always crashes like that? not sometimes.
{
        "type": "lldb",
        "name": "Tauri Development Debug",
        "request": "launch",
        "program": "${workspaceFolder}/src-tauri/target/debug/dream_spinner.exe",
        "preLaunchTask": "rust: cargo build devel",
      },


Remove the use of TargetPlatformWinMDLocation as the C++ build targets put a problematic path in it.

Fixes #790
Also added a Console application template to the test solution to validate the changes.

Looks like all the changes from the last few months are gone. Without those, there is no much point to take this change.

I'll be putting my MSBuild changes in my own fork for now: https://github.com/jlaanstra/cppwinrt


Update of node version to 16

@jdcargile Could you please check/merge?

@jdcargile could you help out? Would like to avoid breakage: https://github.blog/changelog/2022-09-22-github-actions-all-actions-will-begin-running-on-node16-instead-of-node12/
Node 12 has been out of support since April 2022, as a result we have started the deprecation process of Node 12 for GitHub Actions. We plan to migrate all actions to run on Node16 by Summer 2023. We will monitor the progress of the migration and listen to the community for how things are going before we define a final date.
To raise awareness of the upcoming change, we are adding a warning into workflows which contain Actions running on Node 12. This will come into effect starting on September 27th.


Optimize op call

OP_CLOSE (of OP_OPEN / normal capture) does not need to recurse. The backtracking can be handled entirely in OP_OPEN (the bounds will anyway not be valid until OP_OPEN restored the GrpStart, so we can defer GrpEnd untill then).

There were several occurrences of
     Result := MatchPrim(next);
     Exit;

If we continue the while-loop at the current level it will return the same result.
                                                           Time     Before |    OP_OPEN     |       exit     | Match count
==================================================================================================================
                                                  /Twain/ :          31 ms |      23 ms     |      23 ms     |       2388
                                              /(?i)Twain/ :          46 ms |      39 ms     |      47 ms     |       2657
                                             /[a-z]shing/ :         203 ms |     203 ms     |     203 ms     |       1877
                             /Huck[a-zA-Z]+|Saw[a-zA-Z]+/ :          23 ms |      31 ms     |      23 ms     |        396
                                                      /./ :         422 ms |     406 ms     |     398 ms     |   18905427
                                                    /(.)/ :         594 ms |     547 ms     |     547 ms     |   18905427
                                                      /e/ :          78 ms |      70 ms     |      78 ms     |    1781425
                                                    /(e)/ :          86 ms |      86 ms     |      86 ms     |    1781425
                                           /(?s).{1,45} / :          31 ms |      39 ms     |      31 ms     |     475715
                                         /(?s)\G.{1,45} / :          15 ms |      15 ms     |      16 ms     |      10616
                                         /\G(?s).{1,45} / :          16 ms |      15 ms     |      15 ms     |      10616
                                          /(?s).{1,45}? / :         148 ms |     156 ms     |     148 ms     |    3241534
                                        /(?s)\G.{1,45}? / :          15 ms |      15 ms     |      15 ms     |      69431
                                        /\G(?s).{1,45}? / :          16 ms |      15 ms     |      15 ms     |      69431
                                              /\b\w+nn\b/ :         203 ms |     195 ms     |     195 ms     |        359
                                       /[a-q][^u-z]{13}x/ :         609 ms |     609 ms     |     617 ms     |       4929
                            /Tom|Sawyer|Huckleberry|Finn/ :          31 ms |      31 ms     |      31 ms     |       3015
                        /(?i)Tom|Sawyer|Huckleberry|Finn/ :         125 ms |     133 ms     |     133 ms     |       4820
                    /.{0,2}(Tom|Sawyer|Huckleberry|Finn)/ :        1632 ms |    1656 ms     |    1679 ms     |       3015
                    /.{2,4}(Tom|Sawyer|Huckleberry|Finn)/ :        1859 ms |    1867 ms     |    1891 ms     |       2220
                      /Tom.{10,25}river|river.{10,25}Tom/ :          39 ms |      39 ms     |      46 ms     |          2
                                           /[a-zA-Z]+ing/ :         547 ms |     523 ms     |     539 ms     |      95863
                                  /\s[a-zA-Z]{0,12}ing\s/ :         242 ms |     242 ms     |     242 ms     |      67810
                          /([A-Za-z]awyer|[A-Za-z]inn)\s/ :         500 ms |     516 ms     |     515 ms     |        313
                              /["'][^"']{0,30}[?!\.]["']/ :          62 ms |      62 ms     |      62 ms     |       9857
                                /Tom(.{3,3}|.{5,5})*Finn/ :        2750 ms |    2703 ms     |    2695 ms     |         11
                                    /Tom(...|.....)*Finn/ :        1523 ms |    1132 ms +++ |    1125 ms     |         11
                                   /Tom(...|.....)*?Finn/ :        1336 ms |    1242 ms +++ |    1266 ms     |         11
                      /Tom((...|.....){2,9}\s){1,5}?Finn/ :        3593 ms |    3296 ms +++ |    3296 ms     |         11
                      /Tom((...|.....){2,9}?\s){1,5}Finn/ :        3586 ms |    3320 ms +++ |    3289 ms     |         11
                    /Tom((?:...|.....){2,9}\s){1,5}?Finn/ :        2851 ms |    2765 ms     |    2711 ms     |         11
                    /Tom((?:...|.....){2,9}?\s){1,5}Finn/ :        2812 ms |    2726 ms     |    2711 ms     |         11
                    /Tom((?>...|.....){2,9}\s){1,5}?Finn/ :          23 ms |      31 ms     |      31 ms     |          2
                    /Tom((?>...|.....){2,9}?\s){1,5}Finn/ :          31 ms |      23 ms     |      31 ms     |          2
                                        /\G(?is).(?=.*$)/ :         820 ms |     836 ms     |     804 ms +   |   20045118
                                /\G(?is).(?=(.){1,5}?$)?/ :        3101 ms |    2859 ms +++ |    2789 ms     |   20045118
                                       /\G(?is).(?=.*+$)/ :         836 ms |     875 ms     |     781 ms +++ |   20045118
                /\G(?is).{10,10}(?=(e|y|on|fin|.){0,20})/ :        1414 ms |    1234 ms +++ |    1250 ms     |    2004511
              /\G(?is).{10,10}(?=(?>e|y|on|fin|.){0,20})/ :        1406 ms |    1375 ms     |    1383 ms     |    2004511
                                          /Tom(?!.*Finn)/ :          23 ms |      31 ms     |      31 ms     |       2441
     /(?i)(?>[aeoui][bcdfghjklmnpqrstvwxyz \r\n]*){1,40}/ :         593 ms |     601 ms     |     594 ms     |     579843
                          /(?i)[ bdlm][abdegij][mnoprst]/ :         211 ms |     211 ms     |     210 ms     |     788955
Total:                                                            34491 ms |   32805 ms     |   32601 ms     |

Added "implement \K"
https://regex101.com/r/tFDGt8/1
Any part before the \K will not be reported as part of the match. (It can contain captures / and it must be present)
For look around regex101 does either report it is not supported, or (seems? to) always fail the expression.
However, it makes perfect sense in look behind bar|(?<=\K.)foo  would start the match one before foo (yes could be written without the look behind in this case).
For look ahead, it can happen that the start is set to after the match ends (?=...\K)a => since a negative match len makes no sense, I decided that counts as a "not matched".
Since regex101 reports errors (or non match) for this, the result does not conflict with any other engine.
Zero length matches are ok / also in regex101 https://regex101.com/r/O15wNt/1

you are programming genius! Respect. I will commit soon.

Can you add the docs text about \K, please?

Before I commit, please review:
Matched Result
--------------

The begin of the match can be set using ``\K``.

By default the entire text covered by a pattern is considered matched. However it is possible to set explicitly what will be reported.

The pattern ``a\Kb`` will require the text to contain "ab". But only the "b" will be reported as having been matched.
Their can be several ``\K`` in a pattern, The last one will set the match-start position.
Only ``\K`` in active parts of the pattern are considered. E.g. ``a(\Kb)?`` will not consider ``\K`` if there is no "b".
Captures can exist outside the match set by ``\K``.

Because it is somewhat similar to groups, I put it behind "Backreferences", before "modifiers"

Looks good.


Autocomplete labels when filter/searching nodes.

They are non-obvious to find (under help when you click/type ?). It would be great if they could be autocompleted!

non-obvious

We do have a ? next to the search bar actually. But you have to read the help section.

At least part of solving this would probably involve extending the Search component.


NNLS

Open questions:

[ ] Is projected gradient viable?
[ ] Try a careful implementation of lasso solve?

NNLS notes
Test case: 600 x 60000
n = 600
p = 60000
np.random.seed(1)
X = np.random.uniform(0, 1, (n, p))
X.ravel()[np.random.binomial(1, 0.8, X.size).astype(bool)] = 0
X /= np.std(X)
u = np.random.normal(0, 1, n)
D = (X.T @ u) >= 0
X = X * (2 * D - 1)
y = np.random.normal(0, 10, n)
X = np.asfortranarray(X)
lower = np.full(p, 0)
upper = np.full(p, np.inf)
weights = np.full(n, 1/n)

[ ] Impl 1: 3.8s

[ ] Prune screen (+active) boundary variables.
[ ] Add all non-screen violating variables.
[ ] Fit on screen (1 cycle) + active (many cycles) + prune active boundary.

[ ] Exit early if loss not changing enough
[ ]

This example seems to perform better than mosek
n = 784
p = 60000
np.random.seed(1)
X = np.random.uniform(0, 1, (n, p))
X.ravel()[np.random.binomial(1, 0.8, X.size).astype(bool)] = 0
u = np.random.normal(0, 1, n)
D = (X.T @ u) >= 0
X = X * (1 - 2 * D)
#X /= np.std(X, axis=0)
X = np.concatenate([X, X], axis=1)
D = np.concatenate([D, D])
X = np.asfortranarray(X)
n, p = X.shape
u = (
    np.random.normal(-1e-1, 1, p)
    #np.random.binomial(1, 0.8, p)
)
y = X @ (D * u) / n
lower = np.full(p, 0)
upper = np.full(p, np.inf)
weights = np.full(n, 1/n)


"no kind "Config" is registered for version "v1" in scheme"

While refactoring a unit-test (moved the pakage) I suddenly get the error :
	// decode config, empty if no bytes
	config, err := decode(data)
	if err != nil {
		return nil, errors.Errorf("could not read config: %v", err)
	}

no kind "Config" is registered for version "v1" in scheme, nothing in terms of dependencies changed ! I was wondering if you know what is the issue ?
    context_test.go:129: Error not expected but got could not read config: Error decoding config from data: apiVersion: v1
        clusters: []
        contexts: []
        current-context: "minikube"
        kind: Config
        preferences: {}
        users: []
        : no kind "Config" is registered for version "v1" in scheme "k8s.io/apimachinery@v0.0.0-20190801232353-f6278300bebbb750328ac16ee6dd3aa7d3549568/pkg/runtime/scheme.go:101"

I belive this issue was because my IDE was auto-importing the wrong dependecy simmilar to this interface.


Update Rust Thruster servers

          Unfortunately, I failed to easily update the thruster dependencies; I'll leave it as a separate issue to do.

Originally posted by @LesnyRumcajs in https://github.com/LesnyRumcajs/grpc_bench/issues/350#issuecomment-1605566285
It would be lovely to update the Thruster implementation (unless it is no longer maintained, then it should be deleted)

@trezm You may be interested in this. :)

Ah okay, I'll add it to my list!! Thank you!


Error's stack trace not being fully parsed

I have an error with a full stack trace that, when reported, does not include the full stack trace.
The error, when printed, looks like this.
Error: 6 ALREADY_EXISTS: User "faa85d666e773751" already has a position for question "42".
     at new GraphQLError (/usr/src/service/dist/bundle.js:1756:28)
     at Function.__dirname../app/lib/error.ts.GraphQLError.fromGRPC (/usr/src/service/dist/bundle.js:1776:16)
     at ContentService.<anonymous> (/usr/src/service/dist/bundle.js:276:47)
     at step (/usr/src/service/dist/bundle.js:119:23)
     at Object.throw (/usr/src/service/dist/bundle.js:100:53)
     at rejected (/usr/src/service/dist/bundle.js:92:65)
     at propagateAslWrapper (/usr/src/service/node_modules/async-listener/index.js:502:23)
     at /usr/src/service/node_modules/async-listener/index.js:539:70
     at <anonymous>

I'm reporting using:
errors.report(err)
The error is reported successfully, under the correct service, however, there is no stacktrace associated with the report:

The third line of the stacktrace is a little weird, (I guess it's generated from the typescript compilation somehow), and raw looks like this:

but I don't know if that's the issue.
Environment details

OS: Alpine latest
Node.js version: 8.9.4
@google-cloud/error-reporting version: 0.4.0

On further investigation, it looks like the issue you are seeing is an issue with Error Reporting service itself and not this specific library.  The team responsible for the Error Reporting service is investigating this issue, and I will update this thread with any additional information I receive.
Further, it looks like once the issue has been addressed in the service, the stack traces in question should be parsed correctly without you needing to use an updated version of the @google-cloud/error-reporting library.

I've talked with the Error Reporting team, and confirmed the issue is with the line:
     at Function.__dirname../app/lib/error.ts.GraphQLError.fromGRPC (/usr/src/service/dist/bundle.js:1776:16)

Unfortunately, it looks like the line is not a properly formatted Node.js stack trace and, as such, is something that the Error Reporting Service cannot parse and won't be able to fix.
Thus, at this point, I will close this issue, since it looks like the best approach is to determine why the code that is generating the stack trace is generating an invalid stack trace, which is outside the scope of this repo.


Workaround to make the project work on VS 7.5 for mac

Motivation
The xamarin IOS application does not works anymore if run inside VisualStudio 7.5 for mac
Details about the issue can be found here:
https://github.com/xamarin/xamarin-macios/issues/3830
Description
This PR contains a workaround to make the app work with VS 7.5 for mac.
The final fixes will be released in few months, so we should stick with this for quite some time.

Merged!


Fixed output of '0' in xml convert

I am currently building a export of orders, but all fields where the value is 0 will be droped. This Pull Request will solve the issue

Hello,
thank you for creating this pull request.
I have opened an issue on our Issue Tracker for you. See the issue link: https://issues.shopware.com/#/issues/.
Please use this issue to track the state of your pull request.

Hello,
thank you for creating this pull request.
I have opened an issue on our Issue Tracker for you. See the issue link: https://issues.shopware.com/#/issues/SW-16418.
Please use this issue to track the state of your pull request.

We decided to close this PR because of time constraints and limited overall benefit to the product.


Don't export just imported resources

Make monitor not export just imported resources, instead make it copy them, as it takes a long time for it to export, especially when for example importing multiple levels.

Not sure I can easily do this. I'm hijacking an internal Lunar Magic function that fires every time a level is written to the ROM and I'm not sure I can easily differentiate whether that function was called because of an import or just a "standard" level save.


Allow more properties to be specified in project/build.properties

It would be nice to be able to specify default values for the properties sbt.override.build.repos and sb.repository.config inside the project/build.properties file (alongside the sbt.version setting).
For the motivation see: https://groups.google.com/d/topic/sbt-dev/PNdYumYltlk/discussion.

:+1: All SBT_OPTS should be possible to set in build.properties IMO. Question is priority of different option origins, cmdline param > SBT_OPTS env > .sbtopts? > build.properties? > ?
Or perhaps .sbtopts should be deprecated in favor of build.properties? Thoughts?


2.0: UI - Short IP addresses malform the Machines table on the details page.

More Info
Reported by: eldridge henley<EMAIL_ADDRESS>Source URL: http://localhost:4200/clusters/d6dad514
BrowserChrome 70.0.3538.77Screen Size1680 x 1050OSOS X 10.14.1Viewport Size1488 x 1027Zoom Level100%Pixel Ratio@2x

Partial duplicate of https://github.com/supergiant/supergiant/issues/914, closing


Suggestion: Custom event emitter

My suggestion was originally made in the Roblox API discord.
This is a suggestion to remove the need for Client.initWS(). This can be pretty confusing, this solution could fix this.
My suggestion is that for classes which extend event emitters, (I.e. Group/GroupFunctions) A listener is added for the newListener event.
Within this listener, it would check if the websocket has been initialised. If it hasn't, it would initialise it. It would then emit an error if this fails.
This means that:

Users do not have to run this function somewhere in their code
It's simpler: People only need to run a single function

Disadvantages:

People may not expect adding an event listener to do other things 'under the hood' - I wouldn't say this is much of an issue as people generally just expect things to work. This could be remedied by making it clear in documentation that this is an extended EventEmiter.

Example implementation (Pseudo code):

const WS = // Get websocket object somehow

Class Example extends EventEmitter {
constructor () {
this.on('newListener', function (eventName, listener) {
    if (!WS.active) {
        WS.init()
}
})
}
}

Note that some of the points in this issue refer to versions of Bloxy as yet unreleased.

Thanks for suggesting this feature. I will definitely add it to the library.
This issue will remain open until implemented.
Thank you for contributing to the library.

Solved in v5


Create linklist.java

[ ] I have read freeCodeCamp's contribution guidelines.
[ ] My pull request has a descriptive title (not a vague title like Update index.md)
[ ] My pull request targets the master branch of freeCodeCamp.
[ ] None of my changes are plagiarized from another source without proper attribution.
[ ] My article does not contain shortened URLs or affiliate links.

If your pull request closes a GitHub issue, replace the XXXXX below with the issue number.
Closes #XXXXX

link list

Hi,
Thanks for this pull request (PR).
Unfortunately, we are marking this PR invalid for hacktoberfest. We believe it does not follow the recommended guidelines:

Quality Standards
In line with Hacktoberfest value #2 (Quantity is fun, Quality is key), we have provided examples of the quality standards we encourage. This applies mainly to beginners.

PRs that are automated e.g. scripted opening PRs to remove whitespace / optimize images.
PRs that are disruptive e.g. taking someone else's branch/commits and making a PR.
PRs that are regarded by a project maintainer as a hindrance vs. helping.
Something that's clearly an attempt to simply +1 your PR count for October.

Learn more at https://hacktoberfest.digitalocean.com/details


BotEngine.js : Add tests

Complete the following REQUIRED checkboxes:

[x] I have thoroughly read and understand The Odin Project Contributing Guide
[x] The title of this issue follows the command name: brief description of request format, e.g. /help: add optional @user parameter

The following checkbox is OPTIONAL:

[ ] I would like to be assigned this issue to work on it

1. Description of the Feature Request:
There are quite a lot of features stuck in one big pile within BotEngine.js, and none of them currently get tested. It would be nice to add tests related to these as well, so we are sure we aren't accidentally breaking them
2. Acceptance Criteria:

[ ] All code in https://github.com/TheOdinProject/odin-bot-v2/blob/main/botEngine.js has associated tests

3. Additional Information:

No longer relevant, given the greater refactoring off the code


3d buildings tms server datasrouce with texture

Is your feature request related to a problem? Please describe.
He, I have just learned about this library and saw this example https://www.harp.gl/docs/master/examples/#object-picking.html
I was wondering which standard are you using for 3d buildings? is it a tms based datasource which reads height data per each object and if the coordinates in each tile are based on vectortile standarad?
I was also thinking if it is possible to add texture to each of the buildings?
Describe the solution you'd like
Being able to feed the datasource from a tms layer and texture the 3d buildings based on the properties of the object

@am2222 , there is another issue where there is a request to texture the building, see: https://github.com/heremaps/harp.gl/issues/1854. We don't currently generate the correct texture coordinates to allow this, so there is a bit of work to be done before they can be textured.

@nzjony Thanks, But how about the backend? isharp.gl able to read from a tms datasource (which provides height property for each geometry) and extrude the buildings? or we need to provide other type of standards for it?

@am2222 , I don't know what a tms datasource means, maybe you can point me to what you mean exactly. Perhaps our current data sources already meet this standard?

@nzjony By TMS I mean tile map service (https://wiki.openstreetmap.org/wiki/TMS) which is mainly is supported by image based tile maps and vector tiles standards. and I think you already support it but I am nut sure if you support 3d extrusion for tms as well or not?

@am2222 , thanks for clarifying. I don't think we support TMS, though probably it could be implemented.
The data formats we support are mentioned here<EMAIL_ADDRESS>Does that help?

Should be possible, check out: https://github.com/heremaps/harp.gl/blob/master/%40here/harp-vectortile-datasource/lib/OmvRestClient.ts

Thanks @nzjony

@nzjony Hi,
May I ask you a question about 3d building extrusion? I noticed that it only extrudes the objects, but in osm buildings data we have different roof shapes (https://wiki.openstreetmap.org/wiki/Key:roof:shape), Is there any way to define those types of roof shapes in rendering? I am not very familiar to the harp.gl's APIs and classes. I wanted to give it a try to add these types of roofs but I am not sure which classes I should start to look at. I think this website shows the correct roof types
https://osmbuildings.org/?lat=52.52111&lon=13.41078&zoom=16.8&tilt=30

@am2222
Hi,
nzjony is out of the office until after christmas, so I ll try to help.
We currently do not support Roof Shapes in harp.gl, unfortunately its currently not even on our Roadmap.  So, we will probably not be able to support this in the near future, I can let you know if this changes.

@FraukeF Thanks for your reply,
But May I ask which classes can I have a look to see if I can make some changes by myself to add support for roof type?

Hi @am2222 ,
sure, that would be great, actually the code for the extruded polygons ins harp.gl is not one we fancy as it grew a bit wild quite some time ago, I ever since we are hoping to find some time to restructure it a bit, so already sorry in advance :)
Basically the code decoding the data and creating/preparing to create THREE.js meshes out of it you can find in
VectorTileDataEmitter::applyPolygonTechnique look out for const isExtruded = isExtrudedPolygonTechnique(technique);and everything related to this condition.
If the additional roof geometry is added there, this will finally create an instance of DecodedTile containing the prepared geometries, which then will be further processed and converted to THREE.js meshes in a class called TileGeometryCreator:createObjects,  and in theory the rest should be falling into place.
If you need more support here, you are very welcome, let me know if/when you have further question.

@FraukeF Thanks very much, I will get into it and see if I can add the roof support there. thanks

@FraukeF  If I am understanding the structure correctly here (https://github.com/heremaps/harp.gl/blob/2183218a104d77ce151e0975f5e2477c105e7fb0/%40here/harp-vectortile-datasource/lib/VectorTileDataEmitter.ts#L1361) we  make vertexes of polygons, so can I can make roofs here?

@am2222 , sorry for the late reply, I took some christmas break :) happy new year to you.
I think the code generating the roofs currently you can find some lines below, here: https://github.com/heremaps/harp.gl/blob/2183218a104d77ce151e0975f5e2477c105e7fb0/%40here/harp-vectortile-datasource/lib/VectorTileDataEmitter.ts#L1582
Its only copying the floor coordinates and moving them up along the normal with the given hight, I think this might be the place you could try to add custom roofs.

@am2222 , sorry for the late reply, I took some christmas break :) happy new year to you.
I think the code generating the roofs currently you can find some lines below, here: https://github.com/heremaps/harp.gl/blob/2183218a104d77ce151e0975f5e2477c105e7fb0/%40here/harp-vectortile-datasource/lib/VectorTileDataEmitter.ts#L1582
Its only copying the floor coordinates and moving them up along the normal with the given hight, I think this might be the place you could try to add custom roofs.

@FraukeF Thanks, Happy new year to you too,
Thanks for the help, I will start working on it now.

@FraukeF Thanks, Happy new year to you too,
Thanks for the help, I will start working on it now.

@FraukeF Hello again,
I just checked the https://developer.here.com/documentation/vector-tiles-api/dev_guide/topics/layers.html#buildings-and-addresses and it seems here building vactor tile does not have roof type information, it seems I have to use another mvt tile provider which have roof information, To enable extrusion technique, is it enough to set layer name in the pbf tile asbuildings?

@FraukeF Hello again,
I just checked the https://developer.here.com/documentation/vector-tiles-api/dev_guide/topics/layers.html#buildings-and-addresses and it seems here building vactor tile does not have roof type information, it seems I have to use another mvt tile provider which have roof information, To enable extrusion technique, is it enough to set layer name in the pbf tile asbuildings?

@am2222 , hope you can fid a provider with the information you need, and please reach out to us if you have trouble with what @FraukeF  mentioned.

@am2222 , hope you can fid a provider with the information you need, and please reach out to us if you have trouble with what @FraukeF  mentioned.

@nzjony yeah sure thanks

@nzjony yeah sure thanks


issue: icons do not get fully loaded inside st using nvchad

Hello there, siduck. I am arztareef, a great admirer of your work (both NvChad and chadwm). I have been using st as my terminal emulator since I started linux and just now I have found this issue. The icons do not get fully loaded in when i open up nvim tree using nvchad. All the other other terminal emulator like alacritty and kitty works but only this build of st can fully render the icons. I would like to know what you did to accomplish this.
The issue:

doesnt happen here,  i hope you're using latest build of this repo and jetbrains nerd font is latest too ( as this font's mentioned in Xresources )

no sir, i am not referring to your build, i was referring to my build.
Every st build but your one have that icon loading issue. Only your one has no problem whatsoever.
I would like to know what you have done to accomplish that :)

there's a patch wide glyphs one , try it

https://st.suckless.org/patches/glyph_wide_support/

may i please ask how you have implemented the patch (before adding ligatures or boxdraw or after), my build of st is breaking when im trying to apply the patch. my build of st (https://codeberg.org/arztareef/st)

i added it after all major patches

i fixed it after manipulating smoe codes, thanks siduck! irdk how i can repay you back lol
idk, have my dwm and st build which got highly inspired by you xd:
https://codeberg.org/arztareef/dwm
https://codeberg.org/arztareef/st

@arztareef as-salamu alaykum brother, remove that they/them thing from your bio

@arztareef as-salamu alaykum brother, remove that they/them thing from your bio. We have it like the lg 📺 people

walaikumassalam, thank you for telling me brother! 😄

@arztareef as-salamu alaykum brother, remove that they/them thing from your bio. We have it like the lg 📺 people

walaikumassalam, thank you for telling me brother! 😄

so you added the they/them just as a joke? :grimacing:  , ive to talk from this account or else i'll be  cancelled on github


Starting PerfView Collect Machine-Wide Latest Fails with "Error: Could not load file or assembly 'Microsoft.Win32.Registry"

Starting PerfView Collection fails. Status Logs:
Started with command line: "C:\Users\haengel.REDMOND\OneDrive - Microsoft\Desktop\PerfView.exe" /RestartingToElevelate:  /BufferSizeMB:256 /StackCompression GuiCollect
PerfView Version: 2.0.66  BuildDate: Mon, 22 Feb 2021 19:59:47 GMT
PerfView Start Time 2/26/2021 7:00:59 PM
Started: GuiCollect
Warning: PdbScope not found at C:\Users\haengel.REDMOND\OneDrive - Microsoft\Desktop\PerfViewExtensions\PdbScope.exe
Disabling the Image Size Menu Item.
Warning: ILSize not found at C:\Users\haengel.REDMOND\OneDrive - Microsoft\Desktop\PerfViewExtensions\ILSize.dll
Disabling the IL Size Menu Item.
Collection Dialog open.
Completed: GuiCollect   (Elapsed Time: 0.256 sec)
Started: Collecting data C:\Users\haengel.REDMOND\OneDrive - Microsoft\Desktop\PerfViewData.etl
[Kernel Log: C:\Users\haengel.REDMOND\OneDrive - Microsoft\Desktop\PerfViewData.kernel.etl]
Kernel keywords enabled: Default
Aborting tracing for sessions 'NT Kernel Logger' and 'PerfViewSession'.
Insuring .NET Allocation profiler not installed.
Detected 64 bit system, removing 64 bit keys
Completed: Collecting data C:\Users\haengel.REDMOND\OneDrive - Microsoft\Desktop\PerfViewData.etl   (Elapsed Time: 0.687 sec)
Error: Could not load file or assembly 'Microsoft.Win32.Registry, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. The system cannot find the file specified.

I tried downloading Microsoft.Win32.Registry.dll and placing it as a peer to the PerfView.exe. Now I get a different error:
Started with command line: "E:\PerfView (1).exe"
PerfView Version: 2.0.65  BuildDate: Sat, 23 Jan 2021 00:50:56 GMT
PerfView Start Time 2/27/2021 8:01:57 AM
Started: View
Warning: PdbScope not found at E:\PerfViewExtensions\PdbScope.exe
Disabling the Image Size Menu Item.
Warning: ILSize not found at E:\PerfViewExtensions\ILSize.dll
Disabling the IL Size Menu Item.
Completed: View   (Elapsed Time: 0.174 sec)
Collection Dialog open.
Started: Collecting data E:\PerfViewData.etl
[Kernel Log: E:\PerfViewData.kernel.etl]
Kernel keywords enabled: Process, Thread, ImageLoad
Aborting tracing for sessions 'NT Kernel Logger' and 'PerfViewSession'.
Insuring .NET Allocation profiler not installed.
Detected 64 bit system, removing 64 bit keys
Completed: Collecting data E:\PerfViewData.etl   (Elapsed Time: 0.122 sec)
Exception Occurred: System.ComponentModel.Win32Exception (0x80004005): The specified module could not be found
at Microsoft.Diagnostics.Tracing.Extensions.ETWKernelControl.LoadKernelTraceControl()
at Microsoft.Diagnostics.Tracing.Extensions.ETWKernelControl.StartKernelSession(UInt64& TraceHandle, Void* propertyBuff, Int32 propertyBuffLength, STACK_TRACING_EVENT_ID* stackTracingEventIds, Int32 cStackTracingEventIds)
at Microsoft.Diagnostics.Tracing.Session.TraceEventSession.EnableKernelProvider(Keywords flags, Keywords stackCapture)
at PerfView.CommandProcessor.Start(CommandLineArgs parsedArgs)
at PerfView.CommandProcessor.Collect(CommandLineArgs parsedArgs)
at PerfView.MainWindow.<>c__DisplayClass13_0.b__0()
at PerfView.StatusBar.<>c__DisplayClass22_0.b__0()
An exceptional condition occurred, see log for details.
Collection Dialog open.
Started: Collecting data E:\PerfViewData.etl
[Kernel Log: E:\PerfViewData.kernel.etl]
Kernel keywords enabled: Process, Thread, ImageLoad
Completed: Collecting data E:\PerfViewData.etl   (Elapsed Time: 0.067 sec)
Exception Occurred: System.ComponentModel.Win32Exception (0x80004005): The specified module could not be found
at Microsoft.Diagnostics.Tracing.Extensions.ETWKernelControl.LoadKernelTraceControl()
at Microsoft.Diagnostics.Tracing.Extensions.ETWKernelControl.StartKernelSession(UInt64& TraceHandle, Void* propertyBuff, Int32 propertyBuffLength, STACK_TRACING_EVENT_ID* stackTracingEventIds, Int32 cStackTracingEventIds)
at Microsoft.Diagnostics.Tracing.Session.TraceEventSession.EnableKernelProvider(Keywords flags, Keywords stackCapture)
at PerfView.CommandProcessor.Start(CommandLineArgs parsedArgs)
at PerfView.CommandProcessor.Collect(CommandLineArgs parsedArgs)
at PerfView.MainWindow.<>c__DisplayClass13_0.b__0()
at PerfView.StatusBar.<>c__DisplayClass22_0.b__0()
An exceptional condition occurred, see log for details.

This sounds like PerfView isn't able to unpack its dependencies into your %userprofile%\appdata\roaming\PerfView directory.  Can you look and see if perhaps this directory isn't writable?  You should expect to see a VER. directory with all of the dependencies in it.  One thing that might be worth doing is to delete the %userprofile%\appdata\roaming\PerfView directory if it exists, and let PerfView try to re-create it, which it will do each time you run it.

I tried deleting this folder and re-running Perf View. I can see there are some dependencies here, e.g Microsoft.Diagnostics.FastSerialization, but no Microsoft.Win32.Registry.


[FEATURE REQUEST] Request to add a new command: paste with format

Is your feature request related to a problem? Please describe.
Request to add a new command: paste with format. The paste in the screenshot below can only be pasted in plain text format, and links such as URLs will be lost.

Describe the solution you'd like
Request to add a new command: paste with format.
Additional context
Thank you.

+1 for this feature request.
BTW, I'd like to share some technical issues related to the feature request
The Paste command is implemented with navigator.clipboard.readText(). If we want to support paste with format, we have to leverage navigator.clipboard.read(). On mobile, the readText() works well but the read() will fail due to "permission denied".
Therefore, any implementatiion of paste with format will fail unless Obsidian requires for more permissions on Mobile.


Keyboard nav won't work unless flipster element is focused

Keyboard nav won't work unless flipster element is focused.

This worked for me.
    // focus carousel to enable keypress controls
    setTimeout(() => {
      this.$carousel.focus().trigger({
        type: 'keypress',
        which: 13
      });
    }, 100);

This repository is going into very-low-maintenance mode and declaring backlog bankruptcy


Testng integration test, that covers #553

Contains #563

Travis failed with script ci/test-mill-release.sh with the following error:
1 targets failed
caffeine.test.compileClasspath
Resolution failed for 1 modules:
--------------------------------------------
  com.lihaoyi:mill-contrib-testng:0.3.6-46-32c4a1
	not found: /home/travis/.ivy2/local/com.lihaoyi/mill-contrib-testng/0.3.6-46-32c4a1/ivys/ivy.xml
	not found: https://repo1.maven.org/maven2/com/lihaoyi/mill-contrib-testng/0.3.6-46-32c4a1/mill-contrib-testng-0.3.6-46-32c4a1.pom
	not found: https://oss.sonatype.org/content/repositories/releases/com/lihaoyi/mill-contrib-testng/0.3.6-46-32c4a1/mill-contrib-testng-0.3.6-46-32c4a1.pom
	not found: https://dl.bintray.com/sbt/sbt-plugin-releases/com.lihaoyi/mill-contrib-testng/0.3.6-46-32c4a1/ivys/ivy.xml
	not found: https://jcenter.bintray.com/com/lihaoyi/mill-contrib-testng/0.3.6-46-32c4a1/mill-contrib-testng-0.3.6-46-32c4a1.pom
	not found: https://jitpack.io/com/lihaoyi/mill-contrib-testng/0.3.6-46-32c4a1/mill-contrib-testng-0.3.6-46-32c4a1.pom
	not found: http://repo.spring.io/plugins-release/com/lihaoyi/mill-contrib-testng/0.3.6-46-32c4a1/mill-contrib-testng-0.3.6-46-32c4a1.pom
X mill.integration.local.CaffeineTests.test 64488ms
  utest.AssertionError: assert(eval("caffeine.test.compile"))
    utest.asserts.Asserts$.assertImpl(Asserts.scala:114)
    mill.integration.CaffeineTests.$anonfun$tests$2(CaffeineTests.scala:12)
1 targets failed
integration.test.test mill.integration.local.CaffeineTests mill.integration.local.CaffeineTests.test
The command "$CI_SCRIPT" exited with 1.

@lihaoyi Do you have an idea what's missing to fix the above Caffeine integration tests?

no idea, maybe they're just flaky? They've been unreliable in the past. If it's a consistent failure, you'll have to figure it out

Finally, with the new CI environment, these test pass as epected and this PR is good to go. Also thanks to @jeantil initial work.
I'll squash as appropriate and merge.


Add AddHoneycomb IServiceCollction extension method

Which problem is this PR solving?
Replaces the UseHoneycomb IServiceCollection extension methods to with AddHoneycomb variants, which are more idiomatic when registering ASP.NET core pipeline components.

Closes #94

Short description of the changes

Rename UseHoneycomb extension methods to AddHoneycomb

NOTE: I did originally think about marking the UseHoneycomb methods as obsolete but as this is beta, it feels right to outright replace it. It's a simple change that will be picked up at compile time.

Also, when merged, I can update the blog post and we can update docs.

Also, when merged, I can update the blog post and we can update docs.

We'll need to wait for release, but good idea to update blog post.


raidboss: TOP P5 Sigma Tower Orientation

This uses my TOP P5 Sigma Omega-M location work.
Basically the log indicates that the Omega NPCs that cast 7B74 Wave Cannon will also cast the 7B04, 7B05, and 7B06 Storage Violation spells. The point where they cast this from is seen as the center of the tower. Theoretically, if this position is accurate and available at time of tower spawning we can pull the tower data from the list of these combatants.
Initially this draft is just taking M's location and checking each NPC if it exists at where we think the tower should be, if it does, then we narrow down the two sides the tower's orientation could be to where it is.

This was revealed to not be possible with the combatants as they move within the second the towers expire.


misc: simplify fastpackages logic and reduce play time

@guidograzioli don't forget to change the comment from chore: to misc: !


Bump libmdns from 0.8.0 to 0.9.1

Hopefully resolves https://github.com/Spotifyd/spotifyd/issues/1285
Also fixed a cargo toml warning regarding rust 2024 dropping default_features in favor of default-features

Thanks!


Add Rich Enterprise Controls to the User Interface

Tutorials: https://developers.sap.com/tutorials/sapui5-fiori-cf-fiorify.html
Step 2: Use the smart filter bar
The ProductID filter value is entered wrong in the tutorial, must be >3 and <18 and in the screenshot it's the other way round.

Good catch @Sandervanlaarhoven!
I updates the screenshot and the change should be live within the next few minutes.


Maria Heinrich

Author

Name: Maria Heinrich

Affiliation: FH Kufstein

Keywords

earthquake prediction
radon anomalies time series prediction
earthquake likelihood
natural science
machine learning

Abstract
Earthquake prediction is currently the most important task required for probability, hazard, risk mapping, and mitigation. In the past, various traditional and machine learning models have been used for risk assessment.  It is unlikely that anyone will ever be able to accurately predict earthquakes, but with the advancement of deep learning algorithms, predictions can be made more accurately and with less distance to the natural disaster. Different machine learning approaches and deep learning models based on radon anomaly detection have been compared, opening the field for further developments
..
earthquake prediction-maria-heinrich.pdf
Full PDF: DOI, [Zenodo],
Github Repo.
Github Release
Zenodo WholeTale
Zenodo Github
..

The present literature research "Earthquake prediction with machine learning models based on peak of radon anomalies" gives very fundamental insights about earthquake prediction using radon concentration soil gases and different time series machine learning approaches. This literature research clearly states the problem statement and provides a very structured introduction for readers without any background in the earthquake research area. Explaining the forecast methodologies and data used for earthquake prediction, shows that the author gained a lot of background knowledge from different sources. The comparison of the different models and stages shows the structure of the proposed methodology. This article shows the approach using a meta learner, which can be leveraged also in other research areas using time series data and anomaly detection. For the presentation, it would be interesting to show the accuracy of the model, which uses the two-stage-approach, if this data is available. In general, this article gives fundamental insights of used machine learning models, which is a valuable contribution for data scientists and can be used as baseline for further model research in the earthquake research area.

Order accepted for review

The paper written by Maria Heinrich analyses the possible uses of machine learning for earthquake prediction. It compares different machine learning solutions for this task, including the use of deep learning models based on radon anomaly detection. The article formulates precisely the research question, including the challenges connected to it. The author’s vivid description of how earthquakes occur from the interaction of tectonic plates facilitate the introduction into the topic. The locates the prediction problem in the area of anomaly detection regarding the element radon.  Based on that, it describes concisely how the levels of the noble gas radon could be utilized in determined methods of machine learning.  The author introduces the necessary methodology regarding data collection for the purpose of detecting concentration changes of radon in seismically active areas.
After setting the introductory ground, the author keeps doing a good job and exposes different forecasting methods using ensemble and individual machine learning approaches to predict the concentration of radon in the soil, under consideration of numerous environmental features. The forecasting methods are described utilizing experiments of very robust grounds, whose results are well summarized by the author.
In my final consideration I see a very concise and well written article that succeeds to introduce into the area of calamity detection following a structured path. Larger sections like the second could eventually be divided in two smaller subsections in order to increase readability, although the differentiation between experiments is still possible without further problems.
Points: (18/20)


Rework per-tab buffer listing

Proposed fix for #6 and other 'glitches' when the ShowTabBuffer option is enabled. For example, old code would not correctly handle adding/deleting a tab that wasn't the highest-numbered tab
There are still some corner cases that I might address later, but fixing them may require more extensive refactoring

Thanks for the request.  I will take a look at it and merge it in to the code in the next day or so.


Merge Enum Variant Expressions into Struct Expressions?

Although the semantic of what is actually created differs based on the path, they have the same syntax and the struct expression page also includes unions. They were separate expressions when all expressions were listed on one page, but next to each other. It was easy to understand that way. But that's not been the case for a long time now. If my assessment is correct, then these pages should be merged together. So, is my assessment correct?

It makes sense to me to treat these both as a sort of "product type expression", but I'd check with a 2nd person to make sure.

@Centril, @scottmcm, and I discussed this further on Discord. We ultimately came to a conclusion of the following action items:

Merge enum struct variant literals and struct literals into a "Braced Literal Expression"
Move tuple struct and enum tuple variants into the "Call Expression"

We considered renaming "Struct expression" to "Nominal product type expression" and noted that tuple structs are really function calls when constructing.

Seems reasonable to me, since they are essentially identical.  It will just need to retain the note somewhere that functional record update syntax isn't supported (which seems like a weird limitation to me).
I think the grammar rule names should be renamed, I don't like what I picked.