More up-to-date examples in documentation

I've added notebooks showing examples of DFT, iDFT and Parseval's theorem using synthetic data. This addresses issues #75 and #86 .

Thanks for this Takaya. I will review this on Wednesday. Sorry for the delays.
If anyone else wants to review (e.g. @dougiesquire, @lanougue), that would also be very helpful.

Can we get this merged?? :)

Thanks for the review @dougiesquire! I'm having a look now.

Ok, this looks great! Thanks so much Takaya for your hard work here.


Signal is already connected to given method in that object - error when script reloading

Godot version:

3.2.3
OS/device including version:

Windows
Issue description:

I have this error when hot reloading the tool script with Ctrl+S or Ctrl+Alt+S
Signal 'renamed' is already connected to given method 'on_renamed' in that object
tool
extends Control

signal child_added

func _init():
	if not is_connected("child_added", self, "on_child_added"):
		connect("child_added", self, "on_child_added")

	if get_parent():
		for ch in get_children():
			emit_signal("child_added", ch)

func on_child_added(node:Node):
	if not is_connected("renamed", self, "on_renamed"):
		node.connect("renamed", self, "on_renamed")

func on_renamed():
	print('renamed')

Steps to reproduce:

In empty project create a Control node with the script (above)
Add any child node (so that the scene would be like: Control-SomeOtherNode)
Save the scene
Resave the script with Ctrl+Alt+S (press it once or twice)

Now the error should appear in Output log (every time you resave the script with Ctrl+Alt+S):
 Signal 'renamed' is already connected to given method 'on_renamed' in that object
though renamed signal still works and on_renamed is triggered (you can change name of the child node added in [2] and see renamed printed in Output)
Reproducing with the project:
Steps:

Open the project (below)
Open Control.gd script code in Godot Code Editor
Press Ctrl+Alt+S twice to resave the script
The error should appear in Output

Minimal reproduction project:

signal is already connected error.zip

This was my mistake, here:
if not is_connected("renamed", self, "on_renamed"):
	node.connect("renamed", self, "on_renamed")

apologize for my carelessness


Use interface as the model when Updates

Your Question

The following code works well in gorm v1.
type Object struct {
       ...
}

func (obj *Object) Scan(value interface{}) error {
	if value != nil {
		if e := json.Unmarshal(value.([]byte), r); e != nil {
			return e
		}
	}
	return nil
}

var face interface{}
var model Object{}
face = model

db.Model(face).Updates(...)

But in gorm v2, db.Model(face).Updates(...) will call the Scan() function, and panics with the following.
test panicked: interface conversion: interface {} is Object, not []uint8

I don't know why gormv2 calls Scan() when using interface as the model. And if I want to use interface as the model to support different structs, how can I do that? Thank you so much!
The document you expected this should be explained

Expected answer

I think that Value() should be called before Scan(), but I didn't see it in the log stack.

refer to https://gorm.cn/docs/data_types.html


ISSUES-9 add README doc

Add readme doc, will be merged after #9

Please add issues info in commit eg. ISSUES-9 add readme doc

#8


Add a class for global (non-suffixed) Storage

TODO: Add some method/class that would use the config stored in this variable:
https://github.com/stancl/tenancy/blob/6473806d0de4c8b1f10e781a814e78dce4d46761/src/Traits/BootstrapsTenancy.php#L7

Creating a disk and not putting it in tenancy.filesystem.disks config can be used to achieve this.


Special folders names are not localized according to their mapping in Settings but keep the IMAP name

Checklist

[X] I have used the search function to see if someone else has already submitted the same bug report.
[X] I will describe the problem with as much detail as possible.

App version
8.0b2
Where did you get the app from?
Google Play
Android version
12
Device model
Xiaomi Note 10 Pro
Steps to reproduce

Use a localized version of Thunderbird for Android
Set an IMAP account
Go to hamburger menu
Check the names of the special folders (Inbox, Draft, Sent, Spam, Trash, ...) and their icons
Go to Settings/Account//Folders
Check that the names of each setting (not the values!) for special folders are translated in the UI

Expected behavior
Step 4 : Special folders displayed names are localized as they are in their own settings titles in Folders mapping (squared in blue in the screenshot)
Actual behavior
Special folders displayed names are NOT localized in the folders tree.
Maybe they stay in EN-US. Maybe they keep the IMAP name.
Logs

If you go to Settings/Manage folders you will notice that only Inbox and Outbox use their translated special names

Duplicate of #6799


Use datetime.now as datetime.utcnow is deprecated

Closes #820

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


Use recommended Sentry integration method

The Sentry C# client appears to recommend a different way of integrating it to what Sentry's wizard shows you initially; this updates to leverage useSentry() instead of Sentry.Init directly.
Also includes temporary operations endpoint to enable testing the integration in production.

Yep, I'll remove the legacy SENTRY_URL once this has shipped.


Prefix message not working on commit and PR

Is there an existing issue for this?

[X] I have searched the existing issues

Package ecosystem
npm
Package manager version
No response
Language version
Nodejs
Manifest location and content before the Dependabot update
No response
dependabot.yml content
version: 2
updates:

package-ecosystem: "npm"
directory: "/"
target-branch: "main"
schedule:
interval: "weekly"
day: "tuesday"
time: "07:00"
timezone: "Asia/Tokyo"
allow:

dependency-type: "all"
commit-message:
prefix: "DEV-000: "
include: "scope"

Updated dependency
No response
What you expected to see, versus what you actually saw
Expected:

What i got:

Native package manager behavior
No response
Images of the diff or a link to the PR, issue, or logs
No response
Smallest manifest that reproduces the issue
No response

we're facing this same issue, with nuget ecosystem

This part is a GitHub issue. The bot has returned to normal operation


Connection to host is refused

I have been trying to use foxy to connect my ur3e. I followed the instructions on read.me exactly and several times. (except adding gitclone part where I also added -b foxy). When I launch on fake hardware I can see the model on rviz and even send the .py code to move it on rviz. My problem starts when I try to use real hardware. When I launch ur_bringup the model on rviz shows up folded on itself as white parts and terminal gives multiple Invalid frame ID error. The same outcome also happens when I just unplug the ethernet cable from my computer, so it suggests that my connection to the robot is not properly established. However when I ping the robot IP I get returns as regular. I also checked the pc IP and host IP settings several times. and followed the URCap installation steps. I am quite inexperienced on the subject so any kind of help is much appreciated. Thanks in advance

Thank you for your answer here is the complete output for the command line you have given.
[INFO] [launch]: All log files can be found below /home/baris/.ros/log/2022-06-30-10-29-17-793904-baris-GF65-Thin-9SD-50844
[INFO] [launch]: Default logging verbosity is set to INFO
[INFO] [dashboard_client-2]: process started with pid [50850]
[INFO] [controller_stopper_node-3]: process started with pid [50852]
[INFO] [ros2_control_node-1]: process started with pid [50848]
[INFO] [robot_state_publisher-4]: process started with pid [50854]
[INFO] [spawner.py-5]: process started with pid [50856]
[INFO] [spawner.py-6]: process started with pid [50858]
[INFO] [spawner.py-7]: process started with pid [50860]
[INFO] [spawner.py-8]: process started with pid [50862]
[INFO] [spawner.py-9]: process started with pid [50864]
[ros2_control_node-1] [INFO] [1656574158.166380284] [URPositionHardwareInterface]: Starting ...please wait...
[ros2_control_node-1] [INFO] [1656574158.166448197] [URPositionHardwareInterface]: Initializing driver...
[ros2_control_node-1] [WARN] [1656574158.166973978] [UR_Client_Library]: No realtime capabilities found. Consider using a realtime system for better performance
[dashboard_client-2] [INFO] [1656574158.165781400] [UR_Client_Library]: Connected: Universal Robots Dashboard Server
[dashboard_client-2]
[controller_stopper_node-3] [INFO] [1656574158.171516880] [Controller stopper]: Waiting for switch controller service to come up on controller_manager/switch_controller
[robot_state_publisher-4] Parsing robot urdf xml string.
[robot_state_publisher-4] Link base had 0 children
[robot_state_publisher-4] Link base_link_inertia had 1 children
[robot_state_publisher-4] Link shoulder_link had 1 children
[robot_state_publisher-4] Link upper_arm_link had 1 children
[robot_state_publisher-4] Link forearm_link had 1 children
[robot_state_publisher-4] Link wrist_1_link had 1 children
[robot_state_publisher-4] Link wrist_2_link had 1 children
[robot_state_publisher-4] Link wrist_3_link had 1 children
[robot_state_publisher-4] Link flange had 1 children
[robot_state_publisher-4] Link tool0 had 0 children
[robot_state_publisher-4] [INFO] [1656574158.175847044] [robot_state_publisher]: got segment base
[robot_state_publisher-4] [INFO] [1656574158.176006526] [robot_state_publisher]: got segment base_link
[robot_state_publisher-4] [INFO] [1656574158.176025004] [robot_state_publisher]: got segment base_link_inertia
[robot_state_publisher-4] [INFO] [1656574158.176032697] [robot_state_publisher]: got segment flange
[robot_state_publisher-4] [INFO] [1656574158.176038470] [robot_state_publisher]: got segment forearm_link
[robot_state_publisher-4] [INFO] [1656574158.176044048] [robot_state_publisher]: got segment shoulder_link
[robot_state_publisher-4] [INFO] [1656574158.176049665] [robot_state_publisher]: got segment tool0
[robot_state_publisher-4] [INFO] [1656574158.176057248] [robot_state_publisher]: got segment upper_arm_link
[robot_state_publisher-4] [INFO] [1656574158.176067011] [robot_state_publisher]: got segment wrist_1_link
[robot_state_publisher-4] [INFO] [1656574158.176073231] [robot_state_publisher]: got segment wrist_2_link
[robot_state_publisher-4] [INFO] [1656574158.176078819] [robot_state_publisher]: got segment wrist_3_link
[spawner.py-5] [INFO] [1656574158.361892775] [spawner_joint_state_broadcaster]: Waiting for /controller_manager services
[spawner.py-6] [INFO] [1656574158.364327319] [spawner_io_and_status_controller]: Waiting for /controller_manager services
[spawner.py-9] [INFO] [1656574158.367966714] [spawner_joint_trajectory_controller]: Waiting for /controller_manager services
[spawner.py-7] [INFO] [1656574158.375257582] [spawner_speed_scaling_state_broadcaster]: Waiting for /controller_manager services
[spawner.py-8] [INFO] [1656574158.377170704] [spawner_force_torque_sensor_broadcaster]: Waiting for /controller_manager services
[ros2_control_node-1] [INFO] [1656574158.726928915] [UR_Client_Library]: Negotiated RTDE protocol version to 2.
[ros2_control_node-1] [INFO] [1656574158.727572940] [UR_Client_Library]: Setting up RTDE communication with frequency 500.000000
[ros2_control_node-1] [FATAL] [1656574164.738318586] [URPositionHardwareInterface]: Variable 'speed_slider_mask' is currently controlled by another RTDE client. The input recipe can't be used as configured
[controller_stopper_node-3] [INFO] [1656574164.744411262] [Controller stopper]: Service available
[controller_stopper_node-3] [INFO] [1656574164.744450288] [Controller stopper]: Waiting for list controllers service to come up on controller_manager/list_controllers
[controller_stopper_node-3] [INFO] [1656574164.744475415] [Controller stopper]: Service available
[ros2_control_node-1] [INFO] [1656574164.746318866] [controller_manager]: update rate is 600 Hz
[ERROR] [ros2_control_node-1]: process has died [pid 50848, exit code -11, cmd '/home/baris/install/controller_manager/lib/controller_manager/ros2_control_node --ros-args --params-file /tmp/launch_params_f8ws86wi --params-file /home/baris/install/ur_bringup/share/ur_bringup/config/ur_controllers.yaml'].
The connection is probably the issue like you said since I get the same exact output if I do not plug the ethernet cable to my pc and run the bringup code. Like I said I can ping the robot and and don't know how to further test out whether I estabilished a connection or not.

Solved the problem thanks for your attention. My problem was caused by Fieldbus EtherNet/IP being enabled. I do not know what that option is really used for but I guess it causes the connection issues.

Solved the problem thanks for your attention. My problem was caused by Fieldbus EtherNet/IP being enabled. I do not know what that option is really used for but I guess it causes the connection issues.


Warning: The set-output command is deprecated and will be disabled soon

Lots of these.

@thomastvedt do you know where these come from? Was unable to find them in the source code at first glance.

set-output is not in our code. We have updated all packages.

I think we can close this @ralftar , we could not reproduce the warning message after bumping packages. v3.11.


The code for FluentValidation Validation Template Implementation in the readme.md is wrong

target is not a IValidationContext.
public ValidationTemplate(INotifyPropertyChanged target)
{
    this.target = target;
    validator = GetValidator(target.GetType());
    validationResult = validator.Validate(target); // target is not a IValidationContext.
    target.PropertyChanged += Validate;
}

void Validate(object sender, PropertyChangedEventArgs e)
{
    validationResult = validator.Validate(target); // target is not a IValidationContext.
    foreach (var error in validationResult.Errors)
    {
        RaiseErrorsChanged(error.PropertyName);
    }
}

@CodingOctocat can you provide a PR with the correct code?

@tom-englert
I am a beginner and I tried to do this and it work well, But I'm not sure it makes sense:
private ValidationContext<INotifyPropertyChanged> _validationContext;
// ...
// create a context.
_validationContext = new ValidationContext<INotifyPropertyChanged>(target);
_validationResult = _validator.Validate(_validationContext);

I just opened a PR for this, since I dealt with this exact thing today.

@msieker are the failing tests also related to this change in fluent validation?


Templates paste under current process, only parents template parent process and not children.

When pasting a template under current process using the templates menu, if the parent process is a folder (grey not full process) then only the template process and none of its children get pasted.

This seems to be working now


use meters instead of feets

Is your feature request related to a problem? Please describe.
I'm not use feet but meter for distance calculing
Describe the solution you'd like
Premades effects in the ATL compendium ("ATL.light.dim" and "ATL.light.bright") are set in feet
Describe alternatives you've considered
A option to transform all feet reference to meter
Additional context
Thanks
Of course I could modify the compendium, but with each update this will be lost.

While the dnd5e system, what those premade items are for, has an option to use metric weights, it doesn't change the items in the SRD compendium packs. While I see the convenience of being able to adjust weights of items in the pack, that sounds out of scope for this module to add. Meaning, this feature should be in the system or a separate module that can change the weights of the items in all compendium packs. Building that feature into this module to only adjust its items doesn't sound as useful since other packs also need adjusting.


HTTPS support is a lot cheaper

Also three examples to show how to obtain free HTTPS support.

Thank you @qgustavor :)


feat: global componets for nuxt/ui for md

🔗 Linked issue

#49
❓ Type of change

[ ] 📖 Documentation (updates to the documentation, readme, or JSdoc annotations)
[ ] 🐞 Bug fix (a non-breaking change that fixes an issue)
[ ] 👌 Enhancement (improving an existing functionality like performance)
[X] ✨ New feature (a non-breaking change that adds functionality)
[ ] 🧹 Chore (updates to the build process or auxiliary tools and libraries)
[ ] ⚠ Breaking change (fix or feature that would cause existing functionality to change)

📚 Description

Resolves: #49
This will help us reuse components within nuxt ui that are not global.
📝 Checklist

[X] I have linked an issue or discussion.
[ ] I have updated the documentation accordingly.

Thanks for PR but is there any specific components missing as global today? Mainly I want to avoid introducing more configuration as much as possible (also consider .docs is a nuxt project. One could use .docs/nuxt.config.

@pi0 That is good to know, but since the nuxt/ui is not global we can't use any of the components without exposing them.
I was trying to use the UButton from nuxt/ui that doesn't exist in .md and there is not button component currently. I wanted to keep the theme matching nuxt/ui and pro. Pro only has a handful of other Prose components.

@pi0 testing the .docs/nuxt.config doesn't seem to change or do anything. I tried adding a plugin directory but doesn't do. anything either when testing.

I think we might expose ::button mdc if it is a generic enough component and needed. Extra config in external repos is a no no no!


Missing Import in/since v2.12.5

In commit 9f276015  a check was added if BaseNode::getDeprecation() exists.
Plottwist: BaseNode was not included via "use". So this check is always false and the old deprecation params are always used.

Thanks for the report!
Fixed in https://github.com/lexik/LexikJWTAuthenticationBundle/releases/tag/v2.12.6.


0.14.0 returns wrong version string 0.13.3

https://github.com/zenodraft/zenodraft/blob/068570865e36baa49114b99fa1626a4af11425e4/src/cli.ts#L11C18-L11C26
(also check if maintainer tests work)

test exists, but something is going wrong in the jest config

Test discovery fixed in #88, closing


Do you have plan to release Qwen-7B version

Thanks for your attention, we will definitely consider this if the manpower and the computational resources allow.


Update tutorials

Pull Request Template
Description
I propose a new structure for the tutorials: Part 0 as is but updated, Part 1 to quickly get started with Docker Compose, and Part 2 to get set up for the CLI (more advanced). Right now, I only updated the Part 1 tutorial. I still need to update the Part 0 and Part 2 tutorials.
I wanted the tutorials to be more in-depth for someone who has never used PyGrid before, without being too long. Does this look like an acceptable balance?
Fixes #564
Type of change
Please mark options that are relevant.

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

How Has This Been Tested?
I ran the Part 1 notebook in my dev environment, and it all worked as expected.
I don't see any tests/notebook/test_notebooks.py file as mentioned in CONTRIBUTING.md. So I assume we're not writing tests for PyGrid noteboooks?
Checklist:

[X] I did follow the contribution guidelines
[ ] New Unit tests added
[ ] Unit tests pass locally with my changes

I'm also open to creating brief tutorials to explain tools that users may not be familiar with, such as Docker Compose. Then link to them in the Part 0/1/2 tutorials to keep the length shorter.

Ready to merge? I don’t think we can while it’s still a draft. 🙂


Update README.md

Add one paper about RLHF with crowd preference distributions.

Please resolve the conflicts and modify the name of the pull request as our previous format, then we will merge this PR.


ci: automate publishing package to npm

Before merging this PR, NPM_TOKEN must be provided to GitHub:
repository > Settings > Secrets and variables > Actions > New repository
secret
The NPM_TOKEN can be created at https://www.npmjs.com/
profile pic > Account > Access Tokens > Generate New Token > Granular
Access Token

Example run: https://github.com/llllvvuu/vscode-solidity/actions/runs/6282710348/job/17062453049
Example published: https://www.npmjs.com/package/@llllvvuu/vscode-solidity-langserver

@llllvvuu I saw this, and forgot to mention that pushing automatically to npm is a bit scary with key management.

GitHub Actions secrets are pretty secure, but you could publish manually if you prefer.


Solver for quadratic constraint?

Hi, Mr. Zeng
Thanks for your contributions.  I have some questions about this code.
It seems that the CBF constraint is quadratic constraint w.r.t. the u. So what kind of solver do you use? (sorry I am not familiar with MATLAB solver.) Is there any Python solver for this kind of optimization problem?   Btw, will you share the code for car racing case?
Thanks a lot.

Yes, the control barrier function is quadratic to system state in our double integrator example and is quartic to system state in our car racing example.
In Matlab, I use Ipopt solver with Yalmip as modelling language. In python, I use Ipopt solver with casadi as modelling language. I included Ipopt solver with MATLAB interface in this repo already if you want to try that.
For your last question, as I mentioned in readme, we will release car racing code after the paper is accepted.

I'm moving the car racing part of this repo as it might not looks great with both matlab and python in one repo, and will notify you when my repo of car racing becomes public.

I'm moving the car racing part of this repo as it might not looks great with both matlab and python in one repo, and will notify you when my repo of car racing becomes public.

I comment here just for timely notification of the upcoming release of the car racing example. Very interesting work!

I comment here just for timely notification of the upcoming release of the car racing example. Very interesting work!

Thanks Qin, will let notify you soon later :)

Car racing numerical examples will be moved to this repo.
The code will be shown there and this issue will be closed after I upload all code there.

A quasi-complete version of the code is uploaded in the link. @Zhenyu-Li  @qinlincmu

@Zhenyu-Li I updated the name of PR in case of other people having the same confuse, hope you don't mind.


Keep javadocs on Forge added classes

Currently Forge's javadocs are lost which can make development quite a bit harder. It would be great to at least have javadocs on Forge's own classes like its events.

This has been implemented since <IP_ADDRESS> as an experimental feature.


Chore: add dev setup information in contributing.md doc

Added information about dev mode features namely:

Multiple Jam Instances and their use in simulating collaborative transactions locally
Block explorer and RPC terminal
Dev setup page for accessing the above-named features

Partially resolves #724

Hey @Dayvvo!
Thanks for the PR.
There is some code in BitcoinQR.tsx I do not quite understand, as it has nothing todo with the linked issue or the description of your PR. There should already be a share button, when the navigator.share method is available.. Would you be able to explain your reasoning behind the change?

Hello @theborakompanioni . Thanks for pointing that out!
You're right. Those changes were not supposed to be in this branch. Initially I was trying to attempt another feature. Sharing the QR image of an address along with the address with the share button and then raise an issue and a PR about that, but then I found that to not be possible with the navigator.share() implementation in the code and decided not to attempt that anymore. I believed those changes to not be present in this branch.
I have removed them and pushed only the changes related to the issue in the comment. Do take a look again. Thanks!


Replace custom Docker class with upstream docker library

There's a docker python module that implements run etc.
https://pypi.python.org/pypi/docker
Reusing the upstream module will likely be more robust in the long term. However, note that there are some very different versions available currently on common platforms. And a large API change in version 2.0

Reusing the upstream module will likely be more robust in the long term.

Sounds like a good idea to me!

@tfoote PR is up! I just swapped out the subprocess calls to use the sdk.


[RIP-10] Fix-bug : ScheduleMessageServiceTest

fix-bug:
1.send delay message,then the msg.getTopic() will change topic_XXXX
so,I'dont get message By msg.getTopic()
2.queueId is dependence by delayLevel
3.consumer delay , inc sleep time
4.add delete file before
Follow this checklist to help us incorporate your contribution quickly and easily. Notice, it would be helpful if you could finish the following 5 checklist(the last one is not necessary)before request the community to review your PR.

[x] Make sure there is a Github issue filed for the change (usually before you start working on it). Trivial changes like typos do not require a Github issue. Your pull request should address just this issue, without pulling in other changes - one PR resolves one issue.
[x] Format the pull request title like [ISSUE #123] Fix UnknownException when host config not exist. Each commit in the pull request should have a meaningful subject line and body.
[x] Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
[x] Write necessary unit-test(over 80% coverage) to verify your logic correction, more mock a little better when cross module dependency exist. If the new feature or significant change is committed, please remember to add integration-test in test module.
[x] Run mvn -B clean apache-rat:check findbugs:findbugs checkstyle:checkstyle to make sure basic checks pass. Run mvn clean install -DskipITs to make sure unit-test pass. Run mvn clean test-compile failsafe:integration-test  to make sure integration-test pass.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

Coverage decreased (-0.01%) to 47.752% when pulling d3a2f137ff43ae509eae5ed62451729656edeb31 on ranqiqiang:develop into 580037fc43d4ffb55bd59b60cfa6e8a9b57e8ca1 on apache:develop.


Unable to render URI images in WebChat- Adapative Card that have a large number of characters

Hello Bot Framework support,
I am attempting to show an image in an adaptive card using the actual Base64 data for the image.(Data URI) The images that I show are run-time generated, and one of them has 84,000 characters in it. The image shows properly in the Bot Emulator, but not in WebChat. Any help on this is appreciated.

**Other auto generated images with a smaller amount of characters work properly in the WebChat. **

@007-fr, please check the size of the overall file being sent. There is a 4MB size limitation, as specified here. Direct Line, which Web Chat is built off of, has adopted this default limitation; this limitation cannot be bypassed, unfortunately.

If I take that data and save it as a file, the file is only 62KB.  (the saved image works as well)

@007-fr, can you go into greater detail as to how the image is being generated during runtime (assuming server-side), including attaching your code? I tested passing a PNG file, length ~155k characters, with the same name shown in your attached pic, and I have had no issue with either a local or Azure deployed bot. You said a smaller image works - how about a larger image? Does the issue present itself if the same image is simply attached and not runtime generated?
Since the image is runtime generated, I'm leaning towards the adaptive card potentially sending before the image has been fully generated / attached. Is this a possibility that you can check? While the activity may show an attached but non-rendered, possibly incomplete, image, I'd feel better if you could test adding a short the time out, or similar, where the image is attached before the card is sent, approx. 1-2 secs (or more).

@007-fr, please also look at the response I posted in the above linked issue, #3650, as it may pertain to you here.  They do have to be remotely sourced.

The image is generated from SSRS via a webservice call at runtime. Once this data is generated, I use the base64 data to display the image in the webchat.  I also save the image in a file system so the user can view a larger size of it if needed. For the image in question, it does not show in the webchat, however the saved image in the file system works fine.
I will add a delay and see what happens.

The image is generated from SSRS via a webservice call at runtime. Once this data is generated, I use the base64 data to display the image in the webchat.  I also save the image in a file system so the user can view a larger size of it if needed. For the image in question, it does not show in the webchat, however the saved image in the file system works fine.
I will add a delay and see what happens.

#3650  is not related to the issue I am seeing because I am using the raw base64 image data itself on the adaptive card(not a URL). This data is returned directly from the webservice call. Once I get the raw data back, I place it in a string(.Net Code) and use the data directly on the Adaptive Card. Here is a snippet of the actual .lg file

#3650  is not related to the issue I am seeing because I am using the raw base64 image data itself on the adaptive card(not a URL). This data is returned directly from the webservice call. Once I get the raw data back, I place it in a string(.Net Code) and use the data directly on the Adaptive Card. Here is a snippet of the actual .lg file

I tested sending a data URI (base64 string) in as a template value and it worked just fine for me. This is what I used.
lg file
# profileImage
- data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAACAAAAAgCAYAAABzenr0AAAABmJLR0QA/wD/AP+gvaeTAAAACXBIWXMAAAsTAAALEwEAmpwYAAAAB3RJTUUH4QkeCyss5OdeMQAABRxJREFUWMPtl3lsFFUYwH9vZmd3Zq92t9Bu6RYKbUVo5FKglEMOOQVUkGAiYGKMoonGxCAxEDRqgoRASFBAIvEIpkIAEVIMAQFRNEBAwHIUikBZkIa7m9LdmdkZ/ygUF2i75Qgx8Ute8uYd3/fLvO94T9ACWbZigyctEKyRZUWEcsJg20nzWT6J87WCE5VHdhkxvd/k8UPM5nQKWigDBw2VFy5fZ8ZjdXi8/oZxlwN0E86dPc3A7u1T1iu1FGDsxJecejyOYehJ4w5JgABd11ukr8UA2NxXkXjI8j/Afw9ACPFwAULhtqqmuVE1T9J4zLSRBASCGcz4aJ76wAC8Pt/xvyor0DR30njCgvZBGV96kKKuPcc8EIDS9dtLOhZ1CaSlB7Ht2xNCddRCwiKnXd7KAf2GyKnolFM1PnLU89LQMc+eMqpPUJTfDs3W8QgzqQnDICfDhepNIyuvcO+qb5dVNKfXkSrApNffnODObEOfUgFVjR/xmj4GM7/fx6IBrdemUmtSOoIXXnzVmZ9f8N3Qb/ajFeajKTTaxu1wsHZSZ+xAG1Zs2DHqvgCMn/LyW6cNxa5VfWA1vVZzCaJCZXrZYUKZrcvuGWDajNn+vPb5cyesOia03I4pHdfgLbB4XCF1vjaUlv06/J4A+j81Yta2s3VIXh+2Q0maM2suYVw4g23qSVERk2Sygn5mbawgHMpcf9cAH8z5LDMrt+070zZFcGblJpVis+YSRvVJzMvVxE6UJ2VICXhuq8GHw9pyUQ0py9f9POKuAEr6Pzn3ywPnkfxuhD89+Vqg1yV/W8nOsTuqUJzfivc3H6V9OHtNiwE+Wfh1B61VaMqSfTXIviAkbonf9EyQ6rfLviBCSlbllmH2foOpxTlEHJnaV6s3Pd0igJKS4kUfb69CqDJKdu7tRcmhIFVfQNECSHrijhenOYcUpvYKMfOnYzzaIa80ZYD5n5d2rXWlDd94FmRPGnYjd1sregW7Nop19dId590aLD1m8srj2Rwjw7e0tGx0SgD9insumb4lApKJktMhlRrd6PXxtV2Cd/vnMGtLJT2KOi1sFmDBFyv6nkx4ig/USMgeP9jJym3bxtbjxHduBZeKnBUmceYk+p+77wihumQ2RhJM7pbNIcOTt2DZykFNvgt2Hjy1+o1tF8ftuWyiFXQDWWkwbF78G6FqGLt+QenYFavmMomqSpQuvUlUR5D8AUjzI2RHvZNeF6ed4MoEmd6L/uDTgRlrehW1G99oMfIqjsF7zuhI6W5QlIbUGz9Zjm0aAChP9MX4fStyKIyz9yD0vTuQA62wVAfWpXP1wIaO0joMwFVbpvyyRTu/G68iD26yGhpmwo8kIxQ1KfHcMA5gXYuiDhyNcNVXRW3wWOy6a8QiR26uiV+7+WqS4HiNhVd1oCcsf5M+IJxKRciXwDJiCPmWuL/RD2Q2GG/Yp7lxZLS5ueZf/bgJnQMy1/Q6JIdS0STAwcOVi+cPK8COmeiRE4jr/0hpHUbN74ZW2APJ5b6jwynBEGpB/RpZ8wJQF4N5XQxOX4wy/JFsyo9ULm72cbp558FD5XFfp7c3R8ChQEYIoXoQLg2hOBGKhG3Vx5mwwbSp95U4pHksOnhsCvyC7unwXpHEZzuqiFsyXZxXDw8tLuqc0ut45Y+/zXmssO0zuyPR/GjcclwPhXqrloXkdIHThS1JBCSLXA+EvRK6BbEEmLbAjOvsqY6bAwrSj5cfPfXDxJEl02+18w8hWMOkl9o05QAAAABJRU5ErkJggg==

template.json
"items": [
  {
    "type": "Image",
    "style": "Person",
    "url": "${profileImage()}",
    "size": "Small"
  }
],

The result is the blue beaker image displays in the adaptive card.

Can you share a base64 string of an image that is not rendering for you? Then I can attempt passing that value thru and see if I can repro that way.

I tested sending a data URI (base64 string) in as a template value and it worked just fine for me. This is what I used.
lg file
# profileImage
- data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAACAAAAAgCAYAAABzenr0AAAABmJLR0QA/wD/AP+gvaeTAAAACXBIWXMAAAsTAAALEwEAmpwYAAAAB3RJTUUH4QkeCyss5OdeMQAABRxJREFUWMPtl3lsFFUYwH9vZmd3Zq92t9Bu6RYKbUVo5FKglEMOOQVUkGAiYGKMoonGxCAxEDRqgoRASFBAIvEIpkIAEVIMAQFRNEBAwHIUikBZkIa7m9LdmdkZ/ygUF2i75Qgx8Ute8uYd3/fLvO94T9ACWbZigyctEKyRZUWEcsJg20nzWT6J87WCE5VHdhkxvd/k8UPM5nQKWigDBw2VFy5fZ8ZjdXi8/oZxlwN0E86dPc3A7u1T1iu1FGDsxJecejyOYehJ4w5JgABd11ukr8UA2NxXkXjI8j/Afw9ACPFwAULhtqqmuVE1T9J4zLSRBASCGcz4aJ76wAC8Pt/xvyor0DR30njCgvZBGV96kKKuPcc8EIDS9dtLOhZ1CaSlB7Ht2xNCddRCwiKnXd7KAf2GyKnolFM1PnLU89LQMc+eMqpPUJTfDs3W8QgzqQnDICfDhepNIyuvcO+qb5dVNKfXkSrApNffnODObEOfUgFVjR/xmj4GM7/fx6IBrdemUmtSOoIXXnzVmZ9f8N3Qb/ajFeajKTTaxu1wsHZSZ+xAG1Zs2DHqvgCMn/LyW6cNxa5VfWA1vVZzCaJCZXrZYUKZrcvuGWDajNn+vPb5cyesOia03I4pHdfgLbB4XCF1vjaUlv06/J4A+j81Yta2s3VIXh+2Q0maM2suYVw4g23qSVERk2Sygn5mbawgHMpcf9cAH8z5LDMrt+070zZFcGblJpVis+YSRvVJzMvVxE6UJ2VICXhuq8GHw9pyUQ0py9f9POKuAEr6Pzn3ywPnkfxuhD89+Vqg1yV/W8nOsTuqUJzfivc3H6V9OHtNiwE+Wfh1B61VaMqSfTXIviAkbonf9EyQ6rfLviBCSlbllmH2foOpxTlEHJnaV6s3Pd0igJKS4kUfb69CqDJKdu7tRcmhIFVfQNECSHrijhenOYcUpvYKMfOnYzzaIa80ZYD5n5d2rXWlDd94FmRPGnYjd1sregW7Nop19dId590aLD1m8srj2Rwjw7e0tGx0SgD9insumb4lApKJktMhlRrd6PXxtV2Cd/vnMGtLJT2KOi1sFmDBFyv6nkx4ig/USMgeP9jJym3bxtbjxHduBZeKnBUmceYk+p+77wihumQ2RhJM7pbNIcOTt2DZykFNvgt2Hjy1+o1tF8ftuWyiFXQDWWkwbF78G6FqGLt+QenYFavmMomqSpQuvUlUR5D8AUjzI2RHvZNeF6ed4MoEmd6L/uDTgRlrehW1G99oMfIqjsF7zuhI6W5QlIbUGz9Zjm0aAChP9MX4fStyKIyz9yD0vTuQA62wVAfWpXP1wIaO0joMwFVbpvyyRTu/G68iD26yGhpmwo8kIxQ1KfHcMA5gXYuiDhyNcNVXRW3wWOy6a8QiR26uiV+7+WqS4HiNhVd1oCcsf5M+IJxKRciXwDJiCPmWuL/RD2Q2GG/Yp7lxZLS5ueZf/bgJnQMy1/Q6JIdS0STAwcOVi+cPK8COmeiRE4jr/0hpHUbN74ZW2APJ5b6jwynBEGpB/RpZ8wJQF4N5XQxOX4wy/JFsyo9ULm72cbp558FD5XFfp7c3R8ChQEYIoXoQLg2hOBGKhG3Vx5mwwbSp95U4pHksOnhsCvyC7unwXpHEZzuqiFsyXZxXDw8tLuqc0ut45Y+/zXmssO0zuyPR/GjcclwPhXqrloXkdIHThS1JBCSLXA+EvRK6BbEEmLbAjOvsqY6bAwrSj5cfPfXDxJEl02+18w8hWMOkl9o05QAAAABJRU5ErkJggg==

template.json
"items": [
  {
    "type": "Image",
    "style": "Person",
    "url": "${profileImage()}",
    "size": "Small"
  }
],

The result is the blue beaker image displays in the adaptive card.

Can you share a base64 string of an image that is not rendering for you? Then I can attempt passing that value thru and see if I can repro that way.

Closing due to no activity.

Closing due to no activity.

@stevkan I can send it via email since we have an NDA with Microsoft.

@stevkan I can send it via email since we have an NDA with Microsoft.

@stevkan  , I sent an email over your way on Friday 1/15, Let me know if you received it.

@stevkan  , I sent an email over your way on Friday 1/15, Let me know if you received it.

@007-fr, please accept my apologies for the delayed response. I hadn't noticed that the issue was re-opened. I am not seeing the email you had sent me. It was possibly caught up in junk mail and since removed. Could you please send, again?

Closing due to inactivity. If the issue persists or there are new details that can be provided, please feel free to re-open.


Disable on production

Hello, I know that Alpine doesn't have anything to specify "production mode" like Vue and others do.
But is there some way to disable AlpineDevtools?
Thanks

If you're using v3 and import Alpine without setting it as a global (so don't use the CDN build), the devtools won't detect Alpine (since they just look for the global).


PowerToys causes extreme delay when pressing keys on the keyboard.

Microsoft PowerToys version
0.37.2
Running as admin

[X] Yes

Area(s) with issue?
General
Steps to reproduce

Setup PowerToys
Setup FancyZones
Setup Alt-Gr as KB13
Do something else and use your keyboard.

✔ Expected Behavior
Keyboard working as expected.
In Valorant:
I press W, my character takes a step forward.
I hold W for 2 seconds, my character walks forward for 2 seconds.
❌ Actual Behavior
Keys take too long before registering and sometimes stick.
In Valorant:
I press W, nothing happens. My character takes a step forward 6 seconds later.
I hold W for 2 seconds, nothing happens. My character walks forward for 14 seconds by itself.
Other Software
The bug happens everywhere.
In Discord, my push to talk(Alt Gr bound to KB13) gets stuck until I press it again.
In Valorant, I can't move properly.
In any other text software, my typing is delayed.

Setup Alt-Gr as KB13

What do you mean by it? Have you added key remappings to the Keyboard Manager?

@NoThrottle
Right-click on the PowerToys icon in the tray menu and select Report Bug

Drag and drop report into a GitHub comment.

Go to C:\Program Files\PowerToys\Tools
Run BugReportTool.exe
Drag and drop the bug report from the desktop into the github comment

Hi! I will provide the bug report in another comment.
The only thing i remapped was my Alt-Gr key to KB13. Nothing more.
The issue persists everywhere until I end powertoys (usually through task manager).

PowerToysReport_2021-06-18-11-51-06.zip

Don't see anything weird in logs

@NoThrottle
Is the issue solved if you delete Setup Alt-Gr as KB13?
Disable the Keyboard Manager module in the settings and verify if the issue still persists.

Apologize for the late reply. As far as what I have experienced, no, the issue no longer persists when I turn off the Keyboard Manager.


fix docker build

Signed-off-by: tabokie<EMAIL_ADDRESS>What is changed and how it works?
Issue Number: Ref #11312
Fix a series of errors during make docker:

failed to parse manifest
Could not find protoc installation
the linking modifiers +bundle and +whole-archive are not compatible with each other when generating rlibs
error while loading shared libraries: libstdc++.so.6

Fix `make docker`.

Related changes
Check List
Tests

Unit test

Release note
None

I checked out this PR and "make docker" still failed:
   Compiling server v0.0.1 (/tikv/components/server)
error: the linking modifiers `+bundle` and `+whole-archive` are not compatible with each other when generating rlibs

error: could not compile `tikv-ctl` due to previous error
warning: build failed, waiting for other jobs to finish...
error: could not compile `tikv-server` due to previous error
+ r=101
+ set +x
make[1]: *** [Makefile:426: x-build-dist] Error 101
make[1]: Leaving directory '/tikv'
make: *** [Makefile:257: build_dist_release] Error 2
The command '/bin/sh -c source /opt/rh/devtoolset-8/enable && make build_dist_release' returned a non-zero code: 2
make: *** [Makefile:392: docker] Error 2

/merge

/run-test


astype on fields of different locations violates ITIR

The following stencil from Icon4Py currently fails when using temporaries:
@field_operator
def _mo_velocity_advection_stencil_17(
    e_bln_c_s: Field[[CEDim], wpfloat],
    z_v_grad_w: Field[[EdgeDim, KDim], vpfloat],
    ddt_w_adv: Field[[CellDim, KDim], vpfloat],
) -> Field[[CellDim, KDim], vpfloat]:
    z_v_grad_w_wp, ddt_w_adv_wp = z_v_grad_w, ddt_w_adv
    ...

The resulting ITIR contains the following:
(↑(λ(__arg0, __arg1) → {·__arg0, ·__arg1}))(z_v_grad_w, ddt_w_adv)

However since z_v_grad_w and ddt_w_adv live on different domains this is invalid. This currently breaks the temporary pass (as type inference fails). However when all lifts are force inlined the problem disappears so it never surfaced before.

Where is the astype in the example code? Is that a foast to itir lowering problem?


Fix double-indirection bug in logging IDs (#12294)

This PR fixes a bug in log.NewColoredIDValue() which led to a double
indirection and incorrect IDs being printed out.
Backport: #12294
credit: @zeripath
Signed-off-by: Andrew Thornton<EMAIL_ADDRESS>

🚀


name 'basestring' is not defined :: python3

Hi there - thanks for this!
There is an error in Python3 (works in Python2) triggered with v.upload_picture:
File "/usr/local/lib/python3.4/site-packages/vimeo/upload.py", line 105, in upload_picture
    if isinstance(obj, basestring):
NameError: name 'basestring' is not defined

I think this can be fixed fairly easily with a try/except statement upon import ... is it something you would be willing to fix?  I can create a pull request if that would help.
Could use this as a model: https://github.com/oxplot/fysom/issues/1
Damon

Thanks for the info! Sending it off to one of our python devs.


Change cli remote login instructions for windows

Purpose
cli remote login command not working in windows if the user tries to log by adding username and then enter the password. It does not allow user to add the password. As a workaround in windows, the user can add the user name and the password together with the command as shown below,
mi remote login username password
Related Issues
https://github.com/wso2/micro-integrator/issues/1034

This should send to the 7.0.0 branch. Hence close this PR and send to 7.0.0 branch
https://github.com/wso2/docs-ei/pull/759


Icons are stored without normalization in data.json and therefore are not shown in UI

Describe the bug
Icons are sometimes not shown in the UI
To Reproduce
Steps to reproduce the behavior:

Fresh install the plugin
Download fontawesome-solid
Set some folder and note icons, works fine
close and restart obsidian
some of the icons are no longer shown

Expected behavior
All icons should be shown, even after restart.
Possible cause of error
Only icons that have a hyphen or underscore are not shown, so it is likely to be caused by the icon name normalization.
Suggested Fix
Inside data.json replace underscores and hyphens with empty string followed by capitalized next letter, e.g.
from
  "x1": "FasChalkboard-user",
  "x2": "FasUser-group",
  "x3": "FasBook",
  "x4": "FasCity",
  "x5": "FasDesktop",
  "x6": "FasCalendar-week",
  "x7": "FasCalendar-days",
  "x8": "FasImages",
  "x9": "FasH",
  "x10": "FasDiagram-project",
  "x11": "FasQ",
  "x12": "FasK",
  "x13": "FasBook-open",
  "x14": "FasDatabase",
  "x15": "FasI"

to
  "x1": "FasChalkboardUser",
  "x2": "FasUserGroup",
  "x3": "FasBook",
  "x4": "FasCity",
  "x5": "FasDesktop",
  "x6": "FasCalendarWeek",
  "x7": "FasCalendarDays",
  "x8": "FasImages",
  "x9": "FasH",
  "x10": "FasDiagramProject",
  "x11": "FasQ",
  "x12": "FasK",
  "x13": "FasBookOpen",
  "x14": "FasDatabase",
  "x15": "FasI"

(folder and file names censored for privacy reasons)
Additional context
Operating System: Windows 11
Obsidian V: 1.1.16
Icon Folder V: 1.7.0
Screenshots

Unfortunately, I cannot reproduce this issue. I am always testing this with RPG-Awesome, and everything works fine for me. Icons are recognized even when they have a - inside their name.

This sounds like a variation of the issue I submitted, except in my case the icon pack itself goes missing from the plugin list on relaunching obsidian, though is still recognized as existing when I try to readd it and have to remove and manually add it through the plugin. I only get a "you have to create an icon pack" message when trying to select icons, and none are shown. And yet the vault items that have icons set prior to relaunch still display.
There's no hyphens or uppercase characters in the folder/filenames, but disappearing on relaunch might be related.
Do the missing icons on your issue still display after relaunch, if you set them prior?

Yes, I was testing the same functionality with the downloaded solid fontawesome pack.
When I download the fontawesome solid pack, I don't have any - in the icon names (same for the data.json, when I set an icon).
So basically, no matter what the name of the icon is, it should directly match in the dom.

This sounds like a variation of the issue I submitted, except in my case the icon pack itself goes missing from the plugin list on relaunching obsidian, though is still recognized as existing when I try to readd it and have to remove and manually add it through the plugin. I only get a "you have to create an icon pack" message when trying to select icons, and none are shown. And yet the vault items that have icons set prior to relaunch still display.
There's no hyphens or uppercase characters in the folder/filenames, but disappearing on relaunch might be related.
Do the missing icons on your issue still display after relaunch, if you set them prior?

I think, it would be really good if you can create a minimal reproduction version of your vault (discard all the personal files, plugins etc.), so that I can reproduce it.

When I download the fontawesome solid pack, I don't have any - in [...] the data.json, when I set an icon

Wow, I did not expect that. On my two different vaults on different systems, every fontawesome icon is saved to data.json with the - in the name.

it would be really good if you can create a minimal reproduction version of your vault

Done! I just created an empty vault, put some notes in it, downloaded your plugin, downloaded fontawesome-solid, set icons to folders and notes, closed obsidian, opened obisidian - error is here 😄
Before re-opening Obsidian:

After:

data.json:
{
  "settings": {
    "migrated": true,
    "iconPacksPath": ".obsidian/plugins/obsidian-icon-folder/icons",
    "fontSize": 16,
    "emojiStyle": "none",
    "iconColor": null,
    "recentlyUsedIcons": [
      "FasBriefcase-medical",
      "FasArrows-up-down-left-right",
      "FasBattery-three-quarters"
    ],
    "recentlyUsedIconsSize": 5,
    "rules": [],
    "extraMargin": {
      "top": 0,
      "right": 4,
      "bottom": 0,
      "left": 0
    }
  },
  "Note in Folder.md": "FasBattery-three-quarters",
  "Example Folder/Note in Root.md": "FasArrows-up-down-left-right",
  "Example Folder": "FasBriefcase-medical"
}

After this observation, i deleted all non-relevant icons (there were over 1100 downloaded) to reduce vault size and put the whole vault into the attached .zip file icontest.zip.

Ok beautiful, now I can reproduce this as well, thanks for the reproduction. I've tested this on my Dev Fault and could reproduce it as well.
I'll try to provide a fix today.

Ok, thanks for reporting. I've now fixed the issue. You can check out the main branch with the current code to check, if everything works. However, I've changed a lot of things in the codebase compared to the last update. So be aware that there could be some other potential bugs.

This should be fixed in 2.0.0.


export <> noexport feels like the wrong distinction

Basically, it seems a spec has a "public interface" and a "private interface". However, often other specifications will still want to refer to the "private interface" for various reasons. Therefore noexport doesn't really help, since really everything should be exported and easily linkable.
Perhaps for the private stuff there should be some keyword and then if bikeshed detects usage in a normative context, it can flag it?

Paging @mikewest @jyasskin @domenic @zcorpan for potentially different viewpoints.

The only case for noexport is really HTML, where it explicitly takes terms from other specifications and puts them inline. In that case it's actually annoying that you can overwrite noexport with ... as those terms really never ought to be found other than by HTML's own tooling.

Public vs private is on fact precisely what the export/noexport distinction captures, and you can indeed refer to any spec's unexported terms of you really want to. (The trigger is that you need to specify the spec attribute, to indicate that you're sure about exactly what spec your trying to pull a definition from.)
And no, HTML is definitely not the only usecase.

So maybe HTML needs something like "don't index at all" for terms that are not actually defining anything whatsoever?
Note that when folks add export/noexport to specs they don't really take into account whether the entry point is public or private. They just put export on stuff they want to use. So they're not used as intended...

Yeah, that's reasonable. Maybe an empty linking text (data-lt=""), like you use to indicate an  isn't an autolink? Trivial to add.

Or maybe we should change those dfns in HTML to a with some new attribute so it's never picked up by bikeshed but gives the intended behavior in wattsi? (Needs some changes to wattsi and HTML though.)

My perspective, FWIW:

I agree that export/noexport ~ public/private
I agree that people aren't using it this way. Due to the fact that there are defaults (especially the noexport default for dfn), they're just slapping export on things as other specs ask for them, instead of thinking about their public API from first principles. If I were dictator of Bikeshed and had a time-travel machine, I'd go back and make one of the two mandatory on all dfns.

We could try to address this by adding a per-organization flag that warns on dfns that don't explicitly specify, and turn it on for WHATWG. But it would generate a lot of busywork for us, and wouldn't solve HTML.

In general I would weakly prefer there to be no escape hatch to reach into another spec's private API. But I'm sure that would mess a lot of things up.
It sounds like some of this is just working around https://github.com/tabatkins/bikeshed/issues/792 and https://github.com/tabatkins/bikeshed/issues/786 ? That is, if those were straightened out, then we wouldn't need to mark up our stuff as never-link-to-this, since most of the problem is around Bikeshed/Shepherd's heuristics picking these up for unknown reasons, not around people adding spec="html"?
Idle thought: I wonder why https://streams.spec.whatwg.org/#index-defined-elsewhere doesn't use <dfn> but HTML's https://html.spec.whatwg.org/multipage/infrastructure.html#dependencies does. They seem semantically the same.

I agree with @annevk in seeing at least 3 categories of definitions:

public: designed to be called from other specs.
descriptive: only designed to be "called" from the local spec, but can be used as part of another spec's explanatory text.
private: only designed to be used from the local spec. For example, some locally-used terms might be too short to be used from elsewhere.

I think it's essential to have a way to locally override a remote spec's decisions, in order to make progress while we get that remote spec fixed. I'd be very happy if every one of those overrides caused a warning in the local spec that it's not stable until all such overrides are fixed.

Re: people not using it this way: Not much I can do about that. I agree that the export/noexport semantics aren't expressed well, and I'd redo it if possible. Given the way the defaults work, maybe I can just redo it, and use words that are more evocative of purpose?

We could try to address this by adding a per-organization flag that warns on dfns that don't explicitly specify, and turn it on for WHATWG. But it would generate a lot of busywork for us, and wouldn't solve HTML.

If your first reaction is that it'll create a lot of "busywork" even tho you're the one suggesting it, then it's probably not a good idea. ^_^

In general I would weakly prefer there to be no escape hatch to reach into another spec's private API. But I'm sure that would mess a lot of things up.

Definitely not.  For one, as jyasskin says, you need a way to route around mistakes. For two, I can't stop people from just manually linking anyway, and that just results in greater fragility (no error-checking if you misspell something, or the target spec changes its anchors around, etc). So giving an escape hatch is definitely always necessary.  Might be willing to make it more obvious you're doing something "wrong", tho.

It sounds like some of this is just working around #792 and #786 ?

Given that autolinking (and this aspect of it in particular) dates back to the start of Bikeshed, no, it's not working around those issues.  (Which are largely a result of a non-Bikeshed spec using s in ways that Bikeshed/Shepherd don't quite agree with.)

Idle thought: I wonder why https://streams.spec.whatwg.org/#index-defined-elsewhere doesn't use  but HTML's https://html.spec.whatwg.org/multipage/infrastructure.html#dependencies does. They seem semantically the same.

Because they're two different specs using markup in different ways? In particular, I think HTML uses those external definitions to enable a half-manual sort of external autolinking in Wattsi, right?  In Bikeshed, the index is just a companion to the internal definition index, and neither of those indexes contain definitions; one just points to the definition internally, the other externally.
In other words, I think Bikeshed is doing things correctly; HTML's use of DFN in the index is a Wattsi-ism that is correct locally but weird globally.

public: designed to be called from other specs.
descriptive: only designed to be "called" from the local spec, but can be used as part of another spec's explanatory text.
private: only designed to be used from the local spec. For example, some locally-used terms might be too short to be used from elsewhere.

That's basically already captured, with a combination of noexport and local-lt - "public" is anything exported, "descriptive" is anything unexported, and "private" is the term you use in local-lt, which is only usable locally and not collected by Shepherd (so it never enters Bikeshed's databases). local-lt is intended for precisely the purpose of "I want to use a short term that would be bad to export globally, here's a longer version of the name for other people to use".
The only possibility not hit currently is something you really, truly only want to refer to locally; you can't currently use <dfn local-lt> without also happening to create a global term as well.  If it's important enough to be referred to locally, tho, it's probably actually in your "descriptive" category, and possibly appropriate for other specs to refer to.
Anyway, this is giving me some action items and things to think on:

[ ] Provide some way to annotate a DFN to indicate that it's not a definition that Bikeshed should pay any attention to.  (Probably by just looking for an empty lt.)
[ ] Consider how better to express the public/private distinction, and see if I can migrate things over to that automatically (presumably by making everything "public" by default, as the "dfns are unexported" thing is somewhat confusing and unintuitive).

[ ] Figure out some UI that, without being too annoying, bugs people if they're not marking things appropriately. Maybe a bikeshed source command that'll annotate everything as public, and the error message says "hey, looks like you've got X definitions not explicitly marked; mark them, or run bikeshed source publicize-everything to make everything explicitly public"?

@annevk Do you have some good examples of terms that should only be used from non-normative content? You mentioned "navigate" before; are there others?

E.g., in Fetch terms like "main fetch", "basic fetch", "HTTP-network fetch" are implementation details. They are private to Fetch. Standards still want to reference sometimes from a non-normative context to point out their implications on their algorithms (e.g., CSP does this).
Now, another thing. The problem with term to override noexport is that you also need the former when several standards use the same term. E.g., I use identifier here and there. So that means you cannot use the presence of the spec attribute coupled with it appearing in a normative context as an error.
I didn't mention that in OP, but that was part of my thinking when filing this, that the system is not completely thought out.

It would be really great if we could make some progress here. This is still a problem and we're starting to think about exposing public/private more clearly through stylesheets.
Another place where I think it would make sense to expose the difference is indexes. That way you can see at a glance which of your terms are public/private and whether or not they should be.
A thing @domenic came up is that perhaps we could make export/noexport public/private, but we'd additionally support a export+private combination for the couple times where folks want to reference private terms for some reason.

but we'd additionally support a export+private combination for the couple times where folks want to reference private terms for some reason.

Can you elaborate on this more?

(I'm very open to abandoning export/noexport entirely; given that nearly everything is exported, and most unexported "dfn" terms are accidental, it's not serving its purpose right now.  Moving to a clearer public/private distinction and making it required would be nice. We just need to be really clear on what the desired model is before I force people into it.)

@tabatkins basically what I wrote in https://github.com/tabatkins/bikeshed/issues/797#issuecomment-243341658. "Main fetch" is private to Fetch, but is currently exported so another standard can explain in a note how its algorithms are affected by it (CSP and Mixed Content for instance have rather tightly coupled integration).

Ok, so that sounds like just a two-state public/private, where private can only normatively be referenced from inside the defining spec, but can informatively be referenced from anywhere. Right?
Are we certain that we want to actually make it impossible to autolink to a private thing normatively? I'm gonna be annoyed if it turns out a few weeks after I do this that y'all want some "friend" specs that can link each other's private state.

Well, we definitely want to give access to internal slots and such, but I guess those would simply be public, even though they're private state from the perspective of JavaScript.
We have some cases where something is public, but really only for one consumer, but those I tend to call out with a note of sorts as well. I think the distinction you make should be sufficient and will be an improvement over the status quo.

I'm not sure informatively referenced is correct, e.g. for monkeypatches or statements of fact.
I think what would make more sense to me is something similar to the current model in terms of how you reference these things: you need an explicit spec=fetch, or yesireallymeantoaccesstheprivatething attribute or some metadata block listing the private things you expect to access.
I'm on board with flipping things to public-by-default though.
Will this change span Bikeshed and Shepherd, or will we keep using Shepherd's data-export="" attributes?

Domenic: So it sounds like you want precisely the current model, just possibly with things defaulting to public?  Or maybe instead just start being stricter about marking everything as export or noexport?

I think with the current model if you're explicit about a private thing, it can still match a public thing. That should probably stop too. Maybe as simple as making public/private part of the key.

Oh, hm, so allow a public and private thing to overlap in name?

Or maybe that should just error to begin with. Dunno. I guess it was mostly HTML that had that problem and it's mostly been resolved.

Domenic: So it sounds like you want precisely the current model, just possibly with things defaulting to public? Or maybe instead just start being stricter about marking everything as export or noexport?

Yeah, I guess so. Re-reading my earlier responses in the thread, that's pretty much what I said in https://github.com/tabatkins/bikeshed/issues/797#issuecomment-243180290, I now see.

Okay, so here's a draft plan:

Introduce a new public/private attribute pair for dfns. (The public API would be data-dfn-public/etc, but in Bikeshed it'll just be the word.)
Require public/private on every dfn. Fatal error if missing.
Public definitions can be autolinked normally. Private definitions can be autolinked normally from within non-normative sections. To link to a private definition from a normative section, require some obvious i-know-what-i'm-doing attribute to the autolink or a direct parent; this'll only handle this case, not pull double-duty like spec does currently.  (Probably just a private-dfn attribute on the autolink?)
Add some opt-out metadata to help with migration, that auto-applies public/private based on the current export/noexport rules. (But probably permanently logs a warning while in use.)
Just assume that everything is public otherwise, for specs that aren't using the new markup at all.

How does this sound?

That sounds pretty good. For IDL there's probably a fine line to walk, I think we actually want interface members to be "private" as other specifications shouldn't use them directly to define their features, but you're right that interfaces names have to be public (and globally unique).

That sounds pretty good. I'm curious though how this affects the dfn contract and Shepherd database, especially since HTML will be continuing to author all its attributes manually. Will we have to mass-update HTML from data-export="" to data-dfn-public="" or similar? Or does that fall under (6)?
I'm not sure about interface members. I might be conservative and default them to private for now, as all the legit uses I can think of will be in non-normative text, but I might be wrong and people want to refer to interface members all the time.
Looking through the other definition types: IDL arguments should definitely be private; IDL stringifiers and serializers should probably be private?; I'm not really sure what an iterator/maplike/setlike dfn is but they might also be private?

Yeah, stringifiers/serializers are just methods with magic names, so they should act the same as any other method.
That said, I'm not sure I agree that arguments/methods should be private.  People should definitely be linking to the slot/algorithm definitions instead, but unless/until WebIDL defines that there are automatically backing slots for all them, linking to the attr/method and referring to the private backing slot (like I do in TypedOM is probably the best I can do automatically.  Maybe we should prioritize that change?
(Basically, since you almost 100% want to refer to the backing slot / backing algorithm, not the actual property of the given name on the object, we can probably default to interpreting references to an attr/method to be talking about the backing slot/algo instead, and in the super-rare cases you actually want to access an object's property, you can do that with ES-ish syntax.)
I'm... actually not sure what iterator/maplike/setlike are supposed to do.  I might have intended them to link to the map entries/etc definition for the interface?  Given that widlparser doesn't ever output them, I think I can just drop those from Bikeshed.

we can probably default to interpreting references to an attr/method to be talking about the backing slot/algo instead

In a way that seems reasonable, but I'd rather we not, as it's another level of indirection readers will have to become familiar with. I'd rather we describe things as they actually are.

I think arguments should definitely be private though, regardless of what we do about attributes/operations.

Yeah, I agree about arguments.
@annevk Hmm. I guess it's fine for me to call attrs/methods private for now. Outside of a given spec you should rarely be calling into another object's slots/algos anyway.  I'll just jump up the WebIDL effort to make all attributes/methods automatically backed by a slot/algo, with Bikeshed supporting that automatically. (Then the TypedOM stuff would just switch to referring to {{[[unit]]}} etc, instead of {{unit}} internal slot like I'm doing right now to handwave it.)


Intermitten error "Failed to attach to remote debugee.."

Extension Name: vscode-gradle
Extension Version: v3.12.2
OS Version: windows 10
VSCode version: 1.69.2
Vscode-java extension version: v1.9.0
Describe the bug
Clicking on the debug icon beside the task "bootRun"  intermittently throw error, as shown below

When this feature is first implemented, i never encounter such issue.
Note that this is intermittent error...4 out of 5 times of debugging, this error will keep appearing each time i click the debug icon.

Same.
Goes away if you run task few time or tasks can start quickly..
My assumption it's something with 'debugger' timeouts

Same.
Goes away if you run task few time or tasks can start quickly..
My assumption it's something with 'debugger' timeouts

Thanks! I initially still thought I am the only one encountering this issue.
Pray hard this issue can be resolved fast.

The current timeout to wait the debugger to launch is 10s.
https://github.com/microsoft/vscode-gradle/blob/a3d41be8049d1f60ab251f404862fb4d2dcbd7b4/extension/src/util/index.ts#L11
Does this message appear within this timeout or after this timeout?

Hi, I have tested it out a few times. It appears within the timeout (approx around 6-7s)

@hanct Get it, emmm but I can't reproduce it locally. Could you provide a sample project? I'm guessing it's the bug about the current mechanism of querying debug port.

Noted. Will provide the sample project soon. Meanwhile, i have just updated my vscode to the latest version v1.70.0, and realize that now i could not even debug.  Below is what i see...It seem to hang down there indefinitely.

*Do note that the value 55011 is always changing.

Attached is a sample project. Note that i have just updated my vscode to v1.70, but issue persist.
sbur-redis.zip

Thanks for the sample. Unfortunately, I still can't reproduce it on my PC (with 10+ tries). maybe this issue is related to system performance, and I would have another try in my laptop (with a worse performance)
Here are some findings:

we will start the debug session after waitOnTcp() promise:
https://github.com/microsoft/vscode-gradle/blob/e3992ea5b78f88b03afcaa73b4bbfc691024fc4f/extension/src/terminal/GradleRunnerTerminal.ts#L61-L76

In waitOnTcp() function, it will try to connect the target socket in tcpExists(), until it gets connected, and has a connect timeout 300ms and total timeout 10s.
https://github.com/microsoft/vscode-gradle/blob/e3992ea5b78f88b03afcaa73b4bbfc691024fc4f/extension/src/util/index.ts#L14-L46

Strange.. Is your vscode-java extension latest version?

I agree that it's unlikely to be system performance as I am also experiencing this issue with an AMD 5900X on Desktop with 32GB of RAM on Windows 10. I also concur that it's not likely to be the timeout as I manually changed the timeout in the extension code and it had no effect. The project I am working on is: https://github.com/SleepyTrousers/EnderIO-Rewrite and I am trying to run the runClient gradle task, if you want to try that. I'm sorry it's not exactly a small sample project 😅

I try to debug without going thru gradle, and i got error message "Missing Gradle project configuration file: .settings/org.eclipse.buildship.core.prefs". This issue has been raised out at the vscode-java github.  I mention this, cos not sure if this error message has anything to do with the "Failed to attach to remote debugee" in one way or another.

I try to debug without going thru gradle, and i got error message "Missing Gradle project configuration file: .settings/org.eclipse.buildship.core.prefs". This issue has been raised out at the vscode-java github. I mention this, cos not sure if this error message has anything to do with the "Failed to attach to remote debugee" in one way or another.

The root cause of this issue is that your project has been imported via another way or there is any metadata files (.settings, .project and .classapth) ramaining. To solve this, I recommended:

If you want to keep them in your project folder: See: https://github.com/redhat-developer/vscode-java/issues/2528#issuecomment-1166891481
Otherwise, set java.import.generatesMetadataFilesAtProjectRoot to false(default value), delete all metadata files in your project folder and sub project folder, then clean workspace, this issue can be resolved.

BTW, I think this issue is not related to the debug issue, it's about the project importing.

I can reproduce this in @34will's  sample project, it seems that the extension try to start the debug session before the Gradle task is going to run. Let me investigate a bit more.

I presume this is still under investigation.

@hannah23280 sorry for late response. There was a PR tring to fix this issue via serveral retries, could you try if it works?
https://github.com/CsCherrYY/vscode-test/blob/main/vscode-gradle-3.12.5.vsix

@hannah23280 sorry for late response. There was a PR tring to fix this issue via serveral retries, could you try if it works?
https://github.com/CsCherrYY/vscode-test/blob/main/vscode-gradle-3.12.5.vsix

Hi, I have update the extension to v3.12.5 inside the vscode (but not from the link u show above,, which i presume its the same) but unfortunately the issue still persist

@hannah23280 sorry for late response. There was a PR tring to fix this issue via serveral retries, could you try if it works?
https://github.com/CsCherrYY/vscode-test/blob/main/vscode-gradle-3.12.5.vsix

Hi, I have update the extension to v3.12.5 inside the vscode (but not from the link u show above,, which i presume its the same) but unfortunately the issue still persist

Actually they are not the same :). The one I paste here comes from the private build in https://github.com/microsoft/vscode-gradle/pull/1272, which is not included in the offical release since I'm not confident this issue could be fixed via that PR. You can just uninstall the current one and install the one I provided manually to see if it works.
After that, you can re-install the one from the marketplace.

I can reproduce this in @34will's sample project, it seems that the extension try to start the debug session before the Gradle task is going to run. Let me investigate a bit more.

I download the private build in #1272 and tested it out.  Run multiple times and not yet encounter the issue.  Seem to me, the fix work.
Since u have reproduced the issue in @34will 's sample project previously, does the issue goes away with this fix too?

Yeah I tested and it seems to be fixed in that project. It seems this issue can be regarded via serval retries... I will test more times and then release it via pre-release verisons to let more users see if it works.

@hannah23280 @34will @NogrTL I have investigated a new way which might fix this issue in https://github.com/microsoft/vscode-gradle/pull/1289. Would you mind trying it via pre-release 3.12.2022103106?

Cool! But where to download the vsix for 3.12.2022103106

just click "switch to pre-release version" button, any version newer than 3.12.2022103106 will contain this change.

I presume 3.12.20221101  has superceded the 3.12.2022103106.

Unfortunately, still encounter the same issue

thank you @hannah23280, it looks like we should still apply the workaround in #1272...


Reference in CONTRIBUTING.md to the Contributor Guide on gardener.cloud

Related to gardener/documentation#144. The single source of trust is the contributor guide on gardener.cloud. All CONTRIBUTING.md files should refer to this guide

Thank you @berendt for your contribution. Before I can start building your PR, a member of the organization must set the required label(s) {'reviewed/ok-to-test'}. Once started, you can check the build status in the PR checks section below.


asenum - AssociatedEnum

Containers:
asenum - AssociatedEnum: header-only library for C++ for enumerations with associated values

up


Update scalafmt-core to 3.7.7

About this PR
📦 Updates org.scalameta:scalafmt-core from 3.7.6 to 3.7.7
📜 GitHub Release Notes - Version Diff
Usage
✅ Please merge!
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

⚙ Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.scalameta", artifactId = "scalafmt-core" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "org.scalameta", artifactId = "scalafmt-core" }
}]

labels: library-update, early-semver-patch, semver-spec-patch, commit-count:1

Codecov Report
Patch and project coverage have no change.

Comparison is base (57ce720) 95.31% compared to head (fe2c948) 95.31%.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
Additional details and impacted files
@@           Coverage Diff           @@
##           master     #382   +/-   ##
=======================================
  Coverage   95.31%   95.31%
=======================================
  Files           5        5
  Lines          64       64
  Branches        3        3
=======================================
  Hits           61       61
  Misses          3        3

Flag
Coverage Δ

2.12.17
95.31% <ø> (?)

2.13.10
?

Flags with carried forward coverage won't be shown. Click here to find out more.
see 2 files with indirect coverage changes

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


fix country-currency-name-and-code

Why was there trailing whitespace?

Yeah, I'll search around if I can find something on this. Actually, the whole repo has a big problem with some country names not existing in other files .. so I becomes a hustle to import all data into databases. tbh, I didn't notice the whitespace thing was an issue .. but I'll look into it.


feat(image_projection_based_fusion): unrectify image projection based fusion

Description
In image_projection_based_fusion, only the internal parameters of the camera were considered, and no distortion correction was applied. As a result, when projecting onto images with significant distortion, misalignments occurred. This Pull Request has been modified to account for distortion.

Related links
TIER IV INTERNAL
Tests performed
In roi_cluster_fusion, operation has been confirmed on the actual machine.
before

after

Notes for reviewers

Interface changes

Effects on system behavior

Pre-review checklist for the PR author
The PR author must check the checkboxes below when creating the PR.

[ ] I've confirmed the contribution guidelines.
[ ] The PR follows the pull request guidelines.

In-review checklist for the PR reviewers
The PR reviewers must check the checkboxes below before approval.

[ ] The PR follows the pull request guidelines.
[ ] The PR has been properly tested.
[ ] The PR has been reviewed by the code owners.

Post-review checklist for the PR author
The PR author must check the checkboxes below before merging.

[ ] There are no open discussions or they are tracked via tickets.
[ ] The PR is ready for merge.

After all checkboxes are checked, anyone who has write access can merge the PR.

@yukkysaito I checked there is a compile failure. It was caused by https://github.com/autowarefoundation/autoware.universe/pull/7224, and it was fixed.

@kminoda DCO warning seems to be shown by your Co-authored-by. Can you resolve it?

@kminoda DCO warning seems to be shown by your Co-authored-by. Can you resolve it?

done


text_rectangular justify keyword doesn't do anything

Describe the bug
Text produced by gf.components.text_rectangular is always left justified regardless of the value of the justify keyword.
To Reproduce
c_left = gf.components.text_rectangular("text", justify="left")
c_left.show()  # properly left justified text

c_right = gf.components.text_rectangular("text", justify="right")
c_right.show()  # still left justified

Expected behavior
Justification should change.
Suggested fix
The for loop that fixes the justification in this function is not run because of the component.absorb(ref) a few lines up

Thank you for the fix!


Lazily perform searches by yielding results instead of collecting into an array

Actually meant to open this in our fork, but I'll leave this open in case your team finds this useful!


How to post tweets to a different account, not developer's?

Currently I'm using tweepy to update_status of my developer's account, it works great.
Now I'm about to deploy a different app and I want to do the same, how can I use tweepy to post to that account?, is it possible?
UPDATE: I found a way to do it with twython, however I'd like to stick with tweepy, I'll close the issue but I'd really appreciate if someone could point me in the right documentation to do it with tweepy
Best Regards

You need to authenticate as the other user.
See https://tweepy.readthedocs.io/en/latest/auth_tutorial.html, https://developer.twitter.com/en/docs/basics/authentication/overview/oauth, and https://developer.twitter.com/en/docs/basics/authentication/overview/3-legged-oauth (or https://developer.twitter.com/en/docs/basics/authentication/overview/pin-based-oauth).


No UDP data in v3.0.0

After upgrading the add-on in HA, I see the new mqtt topic and sensors created with the Tempest ID, but no data is available in the new sensors.  Is it necessary to install the pyweatherudp package somewhere separately?

pyweatherflowudp is installed by in the container, so no need to add that.
I saw the same behaviour, try and do a hard refresh of your browser and see if the sensors are not being populated.
Else turn on the Debug flag, and look in the log to see if anything shows up.

Hard refresh didn't make a difference.  Debug log captures a few events upon restart and then appears to stop when reaching hub_status.
INFO:weatherflow2mqtt.weatherflow_mqtt:🏠 Home Assistant Supervisor Mode 🏠
INFO:weatherflow2mqtt.weatherflow_mqtt:Timezone is America/Denver
INFO:weatherflow2mqtt.weatherflow_mqtt:Connected to the MQTT server at core-mosquitto:1883
DEBUG:pyweatherflowudp.client:Started listening
INFO:weatherflow2mqtt.weatherflow_mqtt:The UDP server is listening on port 50222
DEBUG:pyweatherflowudp.client:Received message from <IP_ADDRESS>:49270 - b'{"serial_number":"ST-00050852","type":"rapid_wind","hub_sn":"HB-00063380","ob":[1639156896,11.30,317]}'
DEBUG:pyweatherflowudp.client:Received message from <IP_ADDRESS>:49270 - b'{"serial_number":"ST-00050852","type":"rapid_wind","hub_sn":"HB-00063380","ob":[1639156899,8.39,318]}'
DEBUG:pyweatherflowudp.client:Received message from <IP_ADDRESS>:49270 - b'{"serial_number":"HB-00063380","type":"hub_status","firmware_revision":"177","uptime":1187205,"rssi":-37,"timestamp":1639156900,"reset_flags":"BOR,PIN,POR","seq":118572,"radio_stats":[25,1,0,3,4364],"mqtt_stats":[436,15]}'

The UDP part is running, and is receiving Rapid Wind data and Hub Data, but not the other Tempest data.
@natekspencer Could you have a look at this?

It looks like your hub is on a newer revision (177) where they dropped the "fs" field on hub status updates. I'll get this patched ASAP

We just pushed V3.0.1 out. Could you try that and let us know if it fixes your problem. Thanks

Sure will.  I see the update in the repo but not in the HA add-on yet.  Stay tuned...

Sure will. I see the update in the repo but not in the HA add-on yet. Stay tuned...

If you click on "Reload" from the Supervisor add-on store, it should find it quicker.

Confirmed this is now working, thanks!


Duplicate positions and lost items

We're using acts_as_list in an Ajax UI to allow users to re-order items in a list by dragging and dropping items.
If the user drags and drops a few items in quick succession, this can lead to items being lost and duplicated in the list, e.g. "Item A, Item B, Item C" becomes "Item A, Item C, Item C".
It seems the gem doesn't cope well with overlapping operations, and there is no locking. There doesn't seem to be any behaviour to protect against two items having the same position value.
I have some ideas about how to approach this problem but I wanted to get some guidance first.
Any thoughts?

This issue still happens - we have a frontend where several records for a model can be created at once, which results in separate queries to the create action of the respective controller. Some records have the same position when the queries overlap. This could also occur in environments were lots of users create records concurrently.
I just looked quickly at the code, and it seems there is no locking in place in add_to_list_bottom which is called on creation.

Hi this issue still happens.
The following test in shared_list.rb in test_insert_at would fail.
last1 = ListMixin.order(:pos).last
last2 = ListMixin.order(:pos).last
last1.insert_at(1)
last2.insert_at(1)
assert_equal [1, 2, 3, 4, 5], ListMixin.where(parent_id: 20).order('pos').map(&:pos)
```

The `insert_at_position` method would need to `reload_position` or something to fix it.

Hi @danielross, thank you for your pull request. Do you think there's scope for locking the record when reloading it in order to ensure there isn't a race condition where two processes are doing something at the same time?

Yes I think so and actually reload_position won't fix it properly. It is probably better to wrap the content of insert_at_position in with_lock

Thanks @danielross, would you be keen to add a test that simulates the race condition, then we can work on a fix :)

For reference: #195 is working on this issue.

This issue is still not solved for me, using version 0.8.1. This happens for me when creating records, not when updating records.
I think the problem is that this line https://github.com/swanandp/acts_as_list/blob/16cc8af5583040a54ee92257c568ee560856c7fa/lib/acts_as_list/active_record/acts/list.rb#L351 is outside of the with_lock-block. I cannot say if this is an oversight or on purpose, but it seems sensible to require a lock also when creating a record, not only on update?

That's a strange one :) I'm not sure how locking the new record would fix that.
In the current case, locking the record that's about to be inserted at a new position (update) should hold off other insertions that have anything to do with this record by acts_as_list (i.e. those records in the same scope). This is probably more of a beneficial side effect?
Perhaps we should be locking the whole scope before shuffling things around? I've experimented with this in the past but couldn't get it to work.
If you wouldn't mind, would you be able to create a failing test case (see the current test case for this issue as a start), then investigate locking the scope for that entire method?

To be honest I just took a quick glance at the code, and misinterpreted what with_lock is actually doing - I though it was a table level lock instead of a row level lock.
It's very easy to write a failing test, but I had to switch to postgres to do that. As simultaneous writes are AFAIK impossible in sqlite, it's not possible to trigger this behavior with it. If the test suite would support other databases, I could put together a pull request for a failing test (by the way, there are 11 test failures in test_list.rb alone with postgres - maybe worthwhile exploring).
As for a solution, there's a gem for table level locking (https://github.com/norman/fatalistic, it's actually very little code), and I could make my failing test green by updating the callback as follows:
if add_new_at.present?
  before_create do
    self.class.lock do
      send("add_to_list_#{add_new_at}".to_sym)
    end
  end
end

However, I have no idea what impact this has on performance, portability, etc. (Besides, when including this gem a LOT of tests start failing in the test suite, probably because it's overwriting the existing ActiveRecord-method lock instead of defining a new one.).
Maybe this is something which helps people out facing the same problem.

Thanks @fschwahn, that's some very interesting info! Mildly depressing that the suite is failing a lot in postgres! I wonder what it's like in mysql?
Right now it's so simple to get a test environment up and running. Adding those dependencies adds a bit of complexity but it's probably worth it.
As a start, would you like to see if you can get a test suite up and running that tests against sqlite, mysql, and postgres? I've found some notes here:
http://madebynathan.com/2011/12/13/testing-multiple-databases-for-a-rails-app-on-travis-ci/
https://github.com/chiliproject/chiliproject/blob/master/.travis.yml#L7
See the second link (mentioned at the bottom of the first link) as I think they found an even simpler way to do it.
Let me know if I need to modify travis at all, though @swanandp may need to do that mod as I don't think I have full access to the travis setup.

Regarding the locking, I think locking the whole table is a bit dangerous given this code is used amongst larger codebases that we don't have any idea about. I think it's probably safer to lock the records that belong to the scope that the record belongs to. In the case of a scope change, either first lock the old scope while the removal takes place, then lock the new scope while the insertion takes place. We could probably add some DB specific locking types that lock for write but not for read also.
In my experimenting, calling .with_lock on a AR scope didn't lock the scope (Actually did nothing). Though I could have been using it wrong. I hope we don't have to loop all the records to lock them...

I'll have a look at the travis setup, but I had a brief look at the test failures, and all the failures are because they test database specific details (default order, order of NULLs). These tests need to be adjusted, but there was nothing dramatic.

Oh ok, that's good then. Still, probably a good idea that we're testing against the databases that people actually use :)

And about the locking issue:
It's possible to just lock the relevant scope with something like acts_as_list_class.lock.where(scope_condition).to_a (with_lock only operates on individual models) - I briefly tested it and it almost works:
It does not work when several records are inserted when there are no other records yet (ie. on position 1), because there are no rows to lock yet. I fear in that case you need a table level lock - I could be wrong though, I'm far from an expert.

About Travis, sure, just me know.

@fschwahn, that's some fine sleuthing :) If there are no records yet in that scope then there's no need for a lock because there's nothing to effect unless you're worried about multiple threads adding to the same empty scope. In that case there'd need to be something lower level. Perhaps it's possible to lock that scope as SQL directly (bypassing the Rails stuff). Then I'd assume you could lock the empty scope? Or perhaps I'm thinking of a feature that doesn't actually exist :D
@swanandp, are you able to expand or add me as a travis admin on the project?

I am seeing duplicate positions in 0.8.2 and Rails <IP_ADDRESS>.

Hi @prosanelli, are you able to give a bit more information? Under what circumstances is this happening?

I am creating records using sidekiq jobs.

So it's probably a locking issue? Is it due to no locking on an empty scope? (i.e. a list with no items yet)


Exception in display_interface.py

rosrun display_interface display_interface.py results in an exception:
 $ rosrun display_interface display_interface.py
Traceback (most recent call last):
  File "/home/ubuntu/mnpp_ws/src/minipupper_ros/display_interface/scripts/display_interface.py", line 6, in <module>
    from cv_bridge import CvBridge, CvBridgeError
  File "/opt/ros/noetic/lib/python3/dist-packages/cv_bridge/__init__.py", line 6, in <module>
    from cv_bridge.boost.cv_bridge_boost import cvtColorForDisplay, getCvType
SystemError: initialization of cv_bridge_boost raised unreported exception

I found the following answer on "ROS answers": cv_bridge_boost raised unreported exception when importing cv_bridge.
The fix is to import cv2 before cv_bridge:
import cv2
from cv_bridge import CvBridge, CvBridgeError

Hi Joep,
Many thanks for your feedback, we confirmed your advice, you are right.
Could you please post a pull request directly?
I will merge your pull request?
Thanks!


Works when it auto starts, error when launching 'npm run start' (Raspi)

Hello,
I am running dasher on a Raspberry Pi 3 and receive the following error when running the sudo npm run start
`npm ERR! Linux 4.4.50-v7+
npm ERR! argv "/usr/bin/nodejs" "/usr/bin/npm" "run" "start"
npm ERR! node v4.8.1
npm ERR! npm  v2.15.11
npm ERR! path /home/pi/package.json
npm ERR! code ENOENT
npm ERR! errno -2
npm ERR! syscall open
npm ERR! enoent ENOENT: no such file or directory, open '/home/pi/package.json'
npm ERR! enoent This is most likely not a problem with npm itself
npm ERR! enoent and is related to npm not being able to find a file.
npm ERR! enoent
npm ERR! Please include the following file with any support request:
npm ERR!     /home/pi/npm-debug.log
`
But when I use sudo /etc/init.d/dasher start, it works perfectly.

I am seeing the same thing on a new install.

it doesn't look like you're in the correct directory when running sudo npm run start

Yep, turned out to be it. Thank you.


Consider providing a single-file binary to make powershell similar to docker image.

Summary of the new feature / enhancement
release a single-file binary of powershell
Proposed technical implementation details (optional)
This is just my imperfect expectation. AOT in . net7 makes this idea possible. Welcome to discuss.

In fact, the binary powershell on win and linux is green software, which is easy to deploy.

Single file binaries, slightly easier to deploy.

Single file binaries can help attract more customers to try. This may make powershell even greater.

Single file binary program can reduce some functions. Or put some functions in the external dll.

It is better to support freebsd and unix. Or put these support in an external dll.

Provide a "file system" that allows users to embed ps1 scripts into it. It also supports automatic operation.
For example： force the name of the autorun script file to be "main.ps1"

Provide a packaging script, or syntax: similar to using dockerfile to generate docker-image

Single file binaries liks docker-image ,easy self update.

Single file binaries are NOT “powershell docker-image”. The former can run without a docker.

A single file binary program that supports existing external module directories.
There is also a module directory in "Internal file system", which has the highest priority.

Maybe these are easy to implement.
just need to implement the file system in memory, decompress binaries self, and run it.

Maybe Appimage would be useful for someone. For example there is bash on Appimagehub

AOT in . net7 makes this idea possible.

There are several very large (for us specifically) limitations on what you can do with native AOT deployments.

Trimming to only the APIs you use is required (which we can't do as we don't know what PowerShell scripts will use, and we heavily use reflection anyway)
No built-in COM interop
Cannot dynamically load assemblies (so no binary modules period)
No runtime code generation (I believe there is some limited support for expression trees, but interpreted only so actual PowerShell code would be slower)

Even with native AOT, you still need to ship a few extra libs alongside your application anyway.
(Source: Limitations of Native AOT deployment)

There is a build option to create a single file, but it's important to note that it's essentially a self extracting (to temp:) archive. Personally, I'm not sure that the benefit is high enough to publish a separate self-contained executable that simply dumps the contents into temp:\

It seems that AOT technology can not be used for requirements.
self-extracting to temporary directory is one of the options. Self-decompression to memory is a better option.
I think it is not difficult to realize these, but it can bring great benefits.
If there is a "single file powershell and auto-run mechanism", the developer only needs to provide a ps1 script to the customer without considering the deployment issue.


Support non-standard Gradle library catalog locations

Is there an existing issue for this?

[X] I have searched the existing issues

Feature description
Hello!
The current documentation states that Dependabot will look at one and only one specific file when trying to update TOML-based library catalogs:
https://docs.github.com/en/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file#gradle
Specifically, it'll look at gradle/libs.versions.toml.
We put our dependency catalog file in a separate repository and share it between multiple repositories using a git submodule. We realistically can't put the catalog file where Dependabot expects to find it.
Any chance you could add a file parameter so that we could specify a custom location for our catalog file?

:+1: on this, from a quick search on code it seems pretty-much hard-coded for now https://github.com/search?q=repo%3Adependabot%2Fdependabot-core "libs.versions.toml"&type=code, thus having the ability to configure multiple paths (or even wildcards) would really be nice here.


Added target to saslPlainAuth userpassword interface

Added the target to the SaslPlainAuth UserPassword interface
Added new test case to cover that new case

Fixes #98

This is the only way I have found to make this work
@SaslPlainAuth.UserPassword(user="XXX", password="XXX") KafkaCluster cluster

Setting only the @Target{} annotation in UserPassword as stated in the issue does not work because of the provision strategy used in the framework so I allowed to use SaslPlainAuth.UserPassword() as a supported constraint.
The issue states:

This can be fixed by annotating the declaration of @interface UserPassword with @Target({})

That's why I tried to follow this approach.

Not for this PR, but of the two ideas expressed above, I think there is a third:

If we only support one auth mechanism maybe we should have annotations like
@Scram(type=PLAIN, users={@User(name="tom", password="foo")})
If we only support multiple mechanisms maybe we should have annotations like
@Scram(type={PLAIN, SCRAM_256}, users={@User(name="tom", password="foo")})

How about @Sasl being @Repeatable?

Technically the SCRAM-SHA annotations could support additional methods today (iterations for example). I'm not saying we need that. And while I don't expect any new mechanisms it's not exactly certain that they'd conform to username and password and nothing else. If you used a single annotation type and some mechanisms need extra or different properties then you end up with the union of their properties in the annotation type and it's all a bit of a mess.

@k-wall @tombentley I have made it Repeatable, modified the tests to make use of the new config and it works fine.
WDYT?

This change breaks the API, so we should really bump the major when it is released.

Totally agree. It is breaking change for old tests

As we are still in the 0.x phase, my comments about bumping the major are spurious.


Whether my implementation for maximum_search_time incorrect or its could not be work?

I want to apply Pynguin to generate the test cases for my project in a specific time. However, the "maximum_search_time" option in Pynguin's command could not work. My command was bellow.  I do not know whether my implementation is correct or if there are some problems with Penguin. Even if I set the maximum search time, the algorithms will run a long time and will not stop if they cannot generate a test suite. The docker container of the module I want to generate the test stays up forever, as I observe. I built Penguin using Docker.
 If I remember correctly, the maximum_search_time only makes Pynguin stop by checking the time passed after the generation of the initial population of each Search Algorithm (which is updated after every iteration). Did you check the logs of the Docker container to see if the actual search starts?

As @darklambda pointed out, --maximum-search-time only affects the test-generation algorithm, e.g., DynaMOSA or MIO, but not the other components of the Pynguin framework.  Besides, this check is only applied at every loop iteration.  Thus, if one iteration of the test-generation loop lasts long, e.g., because the execution of the generated test cases lasts long, the timeout will probably applied a couple of seconds later.
Regarding your concrete issue: could you please provide a fully working minimal example that shows this behaviour?  Otherwise, I could only guess what the actual reason could be.


VIDEO READY !!!

I hope you will enjoy the crack idm video on the idm crack website
Watch Video 🎥

Overview of Security Monitor Pro Crack
Security Monitor Pro Crack is a comprehensive video monitoring software designed to monitor and record activities using webcams, IP cameras, and other connected security devices. It provides real-time monitoring with features like motion detection, audio alarms, and automatic video recording when unusual activity is detected. Users can monitor multiple cameras simultaneously, making it a great solution for homes, offices, or even larger commercial spaces that require increased security. Thanks to its user-friendly interface, it is accessible to both beginners and experienced users looking for reliable monitoring software.

Overview of Chris-PC CPU Booster Crack
Chris-PC CPU Booster Crack gives you the opportunity to boost your CPU performance and optimize your favorite programs and games to run faster and smoother without any hardware upgrade. The program is especially useful for users who run resource-intensive applications such as gaming, video editing, or multitasking workflows. It works by adjusting CPU priority levels, ensuring that foreground applications that require more processing power are prioritized. This means that less important background processes are deprioritized, resulting in improved speed and performance for more demanding tasks.


Display red text on login page instead of throwing popups as alerts

Will not change, this is actually fine.


TestWorkflowRule get workerInterceptors from two different sources and merges them incorrectly

Expected Behavior
@Rule
public TestWorkflowRule workflowRule =
       TestWorkflowRule.newBuilder()
            .setWorkerFactoryOptions(WorkerFactoryOptions.newBuilder().setWorkerInterceptors(interceptor).build())
            .setWorkflowTypes(TestWorkflowImpl.class)
            .setActivityImplementations(new TestActivities())
            .build();

You would expect that interceptor will be respected and used.
Actual Behavior
TestWorkflowRule inside will create WorkerFactoryOptions without interceptors.
The reason is an incorrect refactoring when TestWorkflowRule first got setWorkerInterceptors() method and after that WorkerFactoryOptions as a parameter with forced rewriting of WorkerFactoryOptions#workerInterceptors with collection provided (or nor provided) in the separate setWorkerInterceptors().

@vkoby this bug is introduced by the recent refactorings.