Stuck in endless while loop startmultiple() with _tare set to false

I am trying to get data from 2 load cells but the startmultiple function returns some arbitrary value when _tare is set to false how shall I combat that? Also the while loop runs endlessly if I use the 2x load cell example.
Please help

Hi!
If you set tare false in startmultiple function, the tare offset avlue will not be set and the output value without load will not be zero (it will be some number very far from zero). If you don't wish to let the startmultiple function calculate and set the tare offset, you can do it later in the loop, see example file, "send 't' from serial terminal", line no 87 in the  2x load cell example.
The endless loop issue under discribed circumstances has now been fixed in 1.2.6, thanks.

Hi!
If you set tare false in startmultiple function, the tare offset avlue will not be set and the output value without load will not be zero (it will be some number very far from zero). If you don't wish to let the startmultiple function calculate and set the tare offset, you can do it later in the loop, see example file, "send 't' from serial terminal", line no 87 in the  2x load cell example.
The endless loop issue under discribed circumstances has now been fixed in 1.2.6, thanks.

How can I set it manually like apply that offset value. Basically what is happening is I calibrate my sensor using the calibration sketch then I load my code and when it runs there is some value other than zero as you described. So will that value be same everytime the sensors and board powers on? And how shall I get that value and store it and use it in my code?

How can I set it manually like apply that offset value. Basically what is happening is I calibrate my sensor using the calibration sketch then I load my code and when it runs there is some value other than zero as you described. So will that value be same everytime the sensors and board powers on? And how shall I get that value and store it and use it in my code?

Hi!
If you set tare false in startmultiple function, the tare offset avlue will not be set and the output value without load will not be zero (it will be some number very far from zero). If you don't wish to let the startmultiple function calculate and set the tare offset, you can do it later in the loop, see example file, "send 't' from serial terminal", line no 87 in the  2x load cell example.
The endless loop issue under discribed circumstances has now been fixed in 1.2.6, thanks.

How can I set it manually like apply that offset value. Basically what is happening is I calibrate my sensor using the calibration sketch then I load my code and when it runs there is some value other than zero as you described. So will that value be same everytime the sensors and board powers on? And how shall I get that value and store it and use it in my code?

Hi!
If you set tare false in startmultiple function, the tare offset avlue will not be set and the output value without load will not be zero (it will be some number very far from zero). If you don't wish to let the startmultiple function calculate and set the tare offset, you can do it later in the loop, see example file, "send 't' from serial terminal", line no 87 in the  2x load cell example.
The endless loop issue under discribed circumstances has now been fixed in 1.2.6, thanks.

How can I set it manually like apply that offset value. Basically what is happening is I calibrate my sensor using the calibration sketch then I load my code and when it runs there is some value other than zero as you described. So will that value be same everytime the sensors and board powers on? And how shall I get that value and store it and use it in my code?

Yes the output value will be aprox. the same ea time you start, but be aware that it may change a bit by temperature etc.
If you want to manually apply the zero offset value you first need to obtain the value like this:

start without any mass on the loadcell
run the function loadcell.tare() or loadcell.tareNoDelay() to calculate the zero offset value
run long zero_offset_val = loadcell.getTareOffset() and note the returned value zero_offset_val

You can now use this value to manually set the zero offset in your sketch: loadcell.setTareOffset(zero_offset_val)

Yes the output value will be aprox. the same ea time you start, but be aware that it may change a bit by temperature etc.
If you want to manually apply the zero offset value you first need to obtain the value like this:

start without any mass on the loadcell
run the function loadcell.tare() or loadcell.tareNoDelay() to calculate the zero offset value
run long zero_offset_val = loadcell.getTareOffset() and note the returned value zero_offset_val

You can now use this value to manually set the zero offset in your sketch: loadcell.setTareOffset(zero_offset_val)

I’m closing this issue because it has been inactive for some time.
Please reopen if you still encounter this issue with the latest version, or if the postings in this thread don't solve your problem .
Thank you!


docs: Port docs to mkdocs

Description
This PR ports the docs to mkdocs.  We'd like to be able to write docs in Markdown.
A previous PR ported the docs to mkBook, but we think mkdocs is better, so the mkBook PR will be closed.
Related Issue(s)
n/a
Documentation
n/a

You can build the new docs and run them locally with mkdocs serve.
The new docs look quite similar to the existing docs, but they're easier to navigate and have a URL structure that's better for SEO.

Not sure if there has been much discussion around hosting the site but I'd be happy to help setup Cloudflare Pages (disclaimer, I work at Cloudfare)

@cmackenzie1 - thanks for the offer.  I think the original idea was to just use GitHub pages and the same URL where the current docs are hosted: https://delta-io.github.io/delta-rs/python/
I am open to other ideas from the community of course.

@rtyler - yea, would be great to use this as an opportunity to improve the Rust documentation as well.
Here is how Polars organizes their URLs:

User guide: https://pola-rs.github.io/polars-book/user-guide/
Python documentation: https://pola-rs.github.io/polars/py-polars/html/reference/
Rust documentation: https://pola-rs.github.io/polars/polars/

The user guide has tabbed code blocks to switch between languages:

Would you be OK if we organize the delta-rs documentation in a similar manner?


Appreciation

Hello Martin, I really love this project you've started and I'm using it as a guide to help me create an algorithm visualizer which has a graph chart to visualize the Big O like you did (hope that's okay?).
I'll like to know if you plan on adding more algorithms, such as searching and the likes, if you do, I'll love to know and also contribute to the project.

Okay, thanks; I'll love to contribute to the project. I'm currently studying the codebase to customise it into my liken for my school project.


Fix pseudocode inside readme

Move o out of the loop so it doesnt get reset every loop iteration

LGTM. Thanks.


UI change to Bluetooth/Gateway connection text on card view

Make the text and icon smaller and place them on the same row.

Icons should take the same space so that the text won't jump.

QA passed


Starting member with dynamically allocated port

Motivation: streamline testing and development and deployments with zero configuration.
the enhancement is to enable creating instance without specifying specific port
Current:
....
ICluster clusterA = Cluster.newInstance(3000).join();
ICluster clusterA = Cluster.newInstance(3001).join();
....
After enhancement it will be possible to run on same  vm several cluster instances:
...
ICluster clusterA = Cluster.newInstance().join();  -- > starts on default port
ICluster clusterB = Cluster.newInstance().join();  ---> starts on default port +1
...

Actually if you run this code right now:
ICluster clusterA = Cluster.newInstance().join();
It will start transport on default port 29001.

Dynamically allocated means on nodes start on default port 29001 + 1
After enhancement it will be possible to run on same vm several cluster instances:
...
ICluster clusterA = Cluster.newInstance().join(); -- > starts on default port
ICluster clusterB = Cluster.newInstance().join(); ---> starts on default port +1

We can do dynamically allocated ports, but there is one problem here.
Cluster creates transport instance in newInstance() method, but start in join() method.
This will cause situation when next code will not work as expected
for (int i = 0; i < 10; i++) {
      clusters.add(Cluster.newInstance());
    }
 for (ICluster cluster : clusters) {
      cluster.joinAwait();
    }

I wonder why we really need to separate newInstance from join?
@antonkharenko @ronenhamias WDYT?

IMHO there are 2 options:
Option 1 (base port)
ICluster clusterA = Cluster.newInstance(3000).join(); // start on port 3000
ICluster clusterB = Cluster.newInstance(3000).join(); // start on port 3001 since 3000 is taken.
Option 2 (port 0)
it means that these 2 lines are the same:
ICluster clusterA = Cluster.newInstance().join();
ICluster clusterA = Cluster.newInstance(0).join();

Don't you think that this approach might lead to unpredictable behavior?
Zero configuration == good defaults, but it does not mean "find some random port just to do not fail".
What if some other application already uses this port (for example, old server instance that was not killed / stuck), and correct behavior in this case should be just fail to start?

@kshchepanovskyi  Basically idea is somewhat similar to what Hazelcast do (see http://docs.hazelcast.org/docs/3.3/manual/html/ports.html) that it doesn't find some random port, but search in the configured ports range (with meaningful defaults) for the free port to bind. If all ports from the configured range are bound then fail. Having only one port basically is just a special case of port range where this range contains single element.

@antonkharenko
Ok, with "automatic cluster node discovery" - similar to Hazelcast's multicast/tcp - it might be good idea.
Anyway, there still are few tricky moments.

Hazelcast always check if service that listens on remote port is actually hazelcast.
Hazelcast has a concept of "cluster name". Cluster nodes should check remote node's "cluster name" so that they are confident they do not connect to wrong node.

That's why I consider this feature danger.

Motivation: streamline testing and development and deployments with zero configuration.

If we do not handle all corner cases, instead of improving things we can make them only worse.

@kshchepanovskyi Basically automatic node discovery is supported  via seed members (it means you need to provide address of at least one existing node on cluster join to discover all other nodes in the cluster). It is not supported multicast discovery (as for now) since it I am not sure it has much value outside of demo or dev environment - multicast often disabled.
Also we have the concept of "cluster name" too. It is called "syncGroup" and it is a part of cluster configuration (ClusterConfiguration.ClusterMembershipSettings.syncGroup) which you can set to arbitrary string identifier. In addition to that Transport send handshake messages on connect so basically node on the other end need to run Transport too in order to pass handshake.

Done at PR: https://github.com/scalecube/scalecube/pull/57


Don't crash and burn when object_name() returns a null

Fixes: When object_name(objectid) returns DbNull because of lack of permissions to interrogate the object, SqlCover crashed on trying to generate its report.
Changes proposed in this pull request:
Ignore objects for which this is the case, as we can't get a meaningful report for them.
Has been tested on (remove any that don't apply):
SQL Server 2014

Slightly worried this gives people an inflated idea of their coverage? I feel like we should at least surface some kind of warning in this situation? That might be too much work as this is a nice simple change, but I'm not necessarily convinced that 'display false-positive results' is much of an improvement on 'at least let the user know something is wrong by dying horribly'.


No rollback on failed transactions

I'm trying to get transactions to work using this library, but some reason rollback is not working. My expectation is that if any statement in the transaction failed, the whole transaction should be rollbacked. Instead it appears to commit all statements except the failed one.
Below is my test code. Any idea what might be the issue?
const queries = [
	{
		sql: `DROP TABLE IF EXISTS testing`,
		params: [],
	},
	{
		sql: `
			CREATE TABLE testing (
				id TEXT PRIMARY KEY,
				title TEXT NOT NULL DEFAULT ""
			)`,
		params: [],
	},
	{
		sql: `INSERT INTO testing (id, title) VALUES (?, ?)`,
		params: ["1", "one"],
	},
	{
		sql: `INSERT INTO doesnotexist (id, title) VALUES (?, ?)`,
		params: ["2", "two"],
	},
]

try {
	await db.transaction(tx => {
		for (const query of queries) {
			tx.executeSql(query.sql, query.params);
		}
	});
} catch (error) {
	console.error('SQL error:', error);
}

const result = await db.executeSql('SELECT * FROM testing');

// Displays "["1", "one"]", which shows that the transaction was not rollbacked:

console.info('RESULT:', result[0].rows.item(0));

Hello, i'm searching about this library. To start an Transaction you must specify it, something like this:
`
//instace is my db connection.
instance.transaction(async (tx) => {
await tx.executeSql('BEGIN TRANSACTION');
//add your functions.
method().catch(() => {
//if it fails make the rollback
tx.executeSql('ROLLBACK');
})
tx.executeSql('COMMIT');
});
`
That's i have searched, any way, i'm testing.

Hi,
I just tested and I confirm transaction are not rollback on Android (it work fine on iOS).
I've created a fork of this repository that bring multiple things:

Fix this issue
Add UUID support
Update SQLite version to 3.43.1 (release on 2023-09-11)
Bring same version of SQLite for iOS & Android, independent of OS version (this mean SQLite is also compiled for iOS)

I hope that this fork will become the new reference for using SQLite with react native and will be regularly updated.
Do you have any idea of how to address this issue ? Or, alternatively, a direction in which to look for a solution (in which file it happens, for example) ?
The fork: https://www.npmjs.com/package/@boltcode/react-native-sqlite-storage
If you want to understand what I've done in this fork, there is a documentation about it.
Have a good day.


Mystery number (DART)

💥 Proposal
Program to check if a number is a mystery number or no
Have you read the Contributing Guidelines on Pull Requests?
Yes

/assign


DRVEGRD 171 MSE Support

Hello,
I am trying to create a setup with one DRVEGRD 171 and two DRVEGRD 169s. I have correctly set up the connections via Ethernet and can receive target pointclouds from all three sensors.
I am using the umrr9f_t169_msev1.0.0 user interface for the 169s. I chose "mse" because I want to use the detected objects from the radars alongside the targets in my system.
https://github.com/smartmicro/smartmicro_ros2_radars/blob/ad4e9b211cbfe1d64565ed07559cd841aaadc398/umrr_ros2_driver/src/smartmicro_radar_node.cpp#L280-L288
https://github.com/smartmicro/smartmicro_ros2_radars/blob/ad4e9b211cbfe1d64565ed07559cd841aaadc398/umrr_ros2_driver/src/smartmicro_radar_node.cpp#L303-L322
However, I couldn't find any "mse" interface for the 171. There are three options available for the 171: ummra4_v1.0.0, v1.0.1, and v1.2.1, but they are limited to producing only target output.

Will there be support for retrieving ObjectList from the DRVEGRD 171s soon?
Or is there a solution for this that I might have missed?
What does "mse" mean in this context, and why is it required for accessing objects?
Why can't every radar model produce both targets and objects?

Hey @sinanyamaan ,
Great to hear that you have successfully set up the driver and sensors. Regarding your questions:

The MSE feature for DRVEGRD 171 is currently under development, which is why it's not yet available. While I can't provide a specific release date, it's in the pipeline and should be included in an upcoming driver release.

MSE stands for Mobile Speed Enforcement, a proprietary software module for specific tracking. Only sensors equipped with the MSE software are capable of tracking and outputting objects; others only publish target data.

MSE is a specialized software application designed for specific radar types, and not all of our sensors are compatible with it due to varying use cases and hardware limitations.

I hope to have answered all your questions, if you require further details or documentations about MSE you may get in contact with our customer support.

Thank you very much for your clear explanations. I am looking forward to the next release!

Thank you very much for your clear explanations. I am looking forward to the next release!


I cant find any information or configuration examples on Pool Clustering (shareRelay).

I cant find any information or configuration examples on Pool Clustering (shareRelay).
Do I need a separate ZMQ?
Pool configuration?

A lot of information
https://github.com/coinfoundry/miningcore/blob/master/src/Miningcore/Configuration/ClusterConfig.cs#L586
https://github.com/coinfoundry/miningcore/blob/master/src/Miningcore/Configuration/ClusterConfig.cs#L595
https://github.com/coinfoundry/miningcore/blob/master/src/Miningcore/Configuration/ClusterConfig.cs#L605
https://github.com/coinfoundry/miningcore/issues/409#issuecomment-426335307


How install-it ?

I know it's ridiculous but, how can I install it ? ^^

Are you downloading the installer? Make sure you click "Releases" up the top and it will take you there.
http://i.imgur.com/AbVvdxL.png

@indefa Thanxs I didnt see that :p


Eliminate all hlint warnings

Hlint warnings should be zero.

[ ] Start using code climate to track hlint warnings
[ ] check test code for hlint warnings as well as src code.


feat(tier4_perception_launch): remove configs and move to autoware_launch

…unch
Signed-off-by: kminoda<EMAIL_ADDRESS>Description
Move config to autoware_launch.
Two PRs should be merged at the same time.

https://github.com/autowarefoundation/autoware.universe/pull/2539
https://github.com/autowarefoundation/autoware_launch/pull/131

Related links
https://github.com/autowarefoundation/autoware_launch/issues/66

Tests performed

Notes for reviewers

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.

@kminoda It looks there is still config files in launch/tier4_perception_launch/config directory. They are not removed in this PR. Is it okay?

@miursh Thank you for pointing it out. Resolved here https://github.com/autowarefoundation/autoware.universe/pull/2539/commits/a33f40988edf17103778025007746816b7206ffc


Appearance.addChangeListener() does nothing

Description
I am writing my first react-native app and would like to switch themes, without restarting the app; like GMail does.
Indeed GMail get darker colors when we change the theme mode, or set automatic dark theme during nights, into the phone settings.
So I try to implement the Appearance.addChangeListener as explained in the doc but unfortunately the feature doesn't work.
React Native version:

System:

OS: Linux 5.4 Linux Mint 20 (Ulyana)
CPU: (12) x64 Intel(R) Core(TM) i5-10400 CPU @ 2.90GHz
Memory: 23.42 GB / 31.29 GB
Shell: 5.0.17 - /bin/bash

Binaries:

Node: 14.15.1 - /usr/bin/node
Yarn: Not Found
npm: 6.14.9 - /usr/bin/npm
Watchman: 20200920.192359.0 - /usr/local/bin/watchman

SDKs:

Android SDK: Not Found

IDEs:

Android Studio: Not Found

Languages:

Java: 14.0.2 - /usr/bin/javac
Python: Not Found

npmPackages:

@react-native-community/cli: Not Found
react: 16.13.1 => 16.13.1
react-native: 0.63.3 => 0.63.3

npmGlobalPackages:

react-native: Not Found

Steps To Reproduce

Create an application implementing Appearance.addChangeListener
Launch the application
Switch to split screen with the settings
Change theme
Notice that the application doesn't change.
Try with GMail to see that the feature work with other apps.

Expected Results
When the user change phone theme setting the addChangeListener should call the function pass in argument.
Snack, code example, screenshot, or link to a repository:
useEffect(() => {
    dispatch(changeTheme(Appearance.getColorScheme()));
    Appearance.addChangeListener(onThemeChange);

    return () => Appearance.removeChangeListener(onThemeChange);
}, []);

// This function is never call
const onThemeChange = ({ colorScheme }) => {
    console.log("onThemeChange", colorScheme)
    dispatch(changeTheme(colorScheme));
}

Also reported on StackOverflow

This issue is quite old and not sure if the same problem, but on my Galaxy Note 10+ with one UI 3.1 (android 11) the listener for the color scheme doesn't work, the color scheme detection only works after restarting the app.

Same here, fresh react native project created today, and the listener  never gets called, neither on the android emulator nor on my actual device. Also the typescript types for addChangeListener are outdated

Will this ever get fixed?


Add support for regular expressions in search bar

What's the Problem?
Search queries can be even more powerful leveraging regular expressions.
Instead of the clunky Windows Query Syntax we could move from
.exe OR .pdf
to
\.exe|\.pdf

and queries like
path/to/*/something

Solution/Idea
Add a checkbox to choose between windows default and regexp.
Also allow making regexp the standard.
Alternatives
None
Priorities
No response
Files Version
<IP_ADDRESS>
Windows Version
Windows 10 Pro 21H2
Comments
No response

A good option for this, used in many code languages, is to treat an input surrounded by / characters as a regular expression.
For example:

\.exe will search for "*.exe" explicitly, including the * and \ characters.
/*\.exe/ will instead use regex, and search for any file finishing with .exe (assuming the regex is set to single-line search by default, which would make sense for file name searching).

Note
It may be useful to either change the color of the search input or add a small "regex" tag to the end of it when this type of string is detected, so the user can clearly understand what they are doing. As an example, here is how VS Code displays the difference:


Precipiation

How can we know either there is precipitation over a day or not .
Can we extract it from PostWRF.

You can extract accumulated precipitation (rain) as RAINC+RAINNC.


Using radio menu items for themes & languagges

If I look at the theme/language selection, I can't see what is currently configured:

So, my suggestion is that use RadioMenuItems instead of regular MenuItems.
Here is an example:

So the user can see what is the currently configured option.

Yes, same is true for the languages. Will be the next thing on my list. Shouldn't be so hard to do 😊

Voilà! Please find it in the newest SNAPSHOT build:
https://repository.sophisticatedapps.com/snapshots/com/sophisticatedapps/archiving/document-archiver/1.6.0-SNAPSHOT
Thanks again for the good input! 🙏🏻


Add functions to initialize single cylindrical cell in fov center

This PR expands on the class used to sample images to generate initial agent positions for a single cylindrical cell, sampled using the existing hexagonal grid sampling functionality.
The existing and unchanged get_hex_sample_indices method creates a 3D rectangular lattice of sampled positions on a hexagonal grid.
This PR adds a function which uses get_hex_sample_indices to create a hexagonally sampled rectangular grid size the desired cell radius in the x and y directions, and desired cell height in the z direction. It then crops this box to a cylinder of sampled positions, and offsets that cylinder to the (xy) center of an FOV of a given size.

Codecov Report

Merging #11 (381086c) into main (8ca2614) will decrease coverage by 0.39%.
The diff coverage is 31.25%.

@@            Coverage Diff             @@
##             main      #11      +/-   ##
==========================================
- Coverage   56.53%   56.14%   -0.40%
==========================================
  Files          13       13
  Lines        1017     1033      +16
==========================================
+ Hits          575      580       +5
- Misses        442      453      +11

Impacted Files
Coverage Δ

...l_abm_pipeline/initial_conditions/sample_images.py
60.18% <31.25%> (-5.04%)
:arrow_down:

Continue to review full report at Codecov.

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

How do we want to handle this PR now? We all saw the code edits together. Who needs to review and accept it and who should merge it? Just don't want to leave this stale or merge it if we need another step of reviewing it....

@jcass11 I was planning on writing a couple tests for the new code, and then I can merge after that?

@jcass11 I was planning on writing a couple tests for the new code, and then I can merge after that?

Sounds good, thank you!


Vite 4.4.9 is causing Unexpected character '@' errors

Hello there,
I'm using nuxt-vitest: 0.10.4 and vite: 4.3.9 and everything is working fine but when I tried to update vite to 4.4.9 I started getting a bunch of Unexpected character '@' errors from my decorators. At first I thought I'd open the issue in the vitejs repo but the project itself seems to run fine with the updated vite so I ended up opening it here instead, thanks :)

Would you be able to provide a reproduction? 🙏

Hey @danielroe thanks for the quick reply! Having a few busy days now but I will add a reproduction as soon as I can 😅

Heyo, update here. When I tried to update the Nuxt version to 3.7.x, I started getting the same error in the actual project as well. After some investigation and trial-error, I could solve it this way. It fixed it both for the project and the tests :)


Showbreak bug when visible lines end exactly at the last character

set wrap
set showbreak=..
I have two lines like so:

On the first line i press A and look where cursor shows:

Is this how it's supposed to be? Because cursor now shows on (over) the second line, even though I'm appending text to the first line.
This is what happens with nowrap:

Can you reproduce this starting Vim with  vim -N -u NONE?

Yes.

I see the problem. I think this happens, because Vim is expecting you to enter something and as soon as you enter something, it will add the 'showbreak' setting to the line, so that the cursor won't be off anymore. It is a particularity, not sure if this classifies as bug and should be fixed.

It is a particularity, not sure if this classifies as bug and should be fixed.

To me, this definitely is a bug. Have another look at the second screenshot. Based on the cursor position, it appears that the next typed character would be inserted between the second and third b in the second line. In reality, it is appended at the end of the first line!
So, there's a clear discrepancy between where Vim hints text would be entered, and what actually happens. If you type blindly, and then quit the buffer or move away, there's a real potential for wrong data entry. I've learned to recognize and ignore this particular situation, but it still makes you stop and annoys. Unless the fix means a complete rewrite of the rendering engine, please correct this!

This only happens when 'number' is on.  Otherwise the cursor shows at the very start of the second line, not two characters to the right.

Does this bug still exist? I think it has been fixed.

Oh, actually #9884 is the same as this one, and it has been fixed.

closing then as resolved.


fix(workspace): completionProvider and other bulk operations for engine v3

fix(workspace): completionProvider and other bulk operations for engine v3
There's an issue with bulk operations (or any operations passing in an array as a query parameter) where an array param exceeding 20 items will get converted to an object. This may cause engine side logic to fail. See https://github.com/expressjs/express/issues/2661
This was causing an issue with the wikilink completion provider not providing results for bigger workspaces while on v3, and potentially other issues as well that call bulkGet, bulkGetMeta, bulkAdd

@hikchoi

maybe it's just safe to set to limit to zero and assume an object? weird that that isn't the default.

This would maybe cause us to catch issues more quickly, but it may be confusing while developing the code as to why arrays are getting converted to JSON.  I think leaving as a high limit may be better for now? But maybe it'll bite us later...
I'm not really sure why there's a limit - not sure if there's some perf consideration, or maybe the URL's can be better condensed when it's an object.

Most likely to avoid iterating everything when something large like 5000 comes in


Examples and readme

added examples and readme

Added the submodule with the specific commit.

I have included the requests.


Add PodDisruptionBudget to router components

Add PDB config
Add component label
Modify updateFunc to use generic

I'm closing this since I'm raising similar PR from my fork: #346


multi-gpu or distributed training failed

Hi,
I try to use pynvvl to do multi-GPU training.
But it seems that it will fail.
CUDA runtime error 3 at line 15 in file /nvvl/src/detail/Decoder.cpp: initialization error CUDA runtime error 3 at line 21 in file  /nvvl/src/detail/Decoder.cpp: initialization error
Could you give me some hints?

Hi, I met the same problem when use multi-GPU, have you solved this problem?

Hi,
I try to use pynvvl to do multi-GPU training.
But it seems that it will fail.
CUDA runtime error 3 at line 15 in file /nvvl/src/detail/Decoder.cpp: initialization error CUDA runtime error 3 at line 21 in file /nvvl/src/detail/Decoder.cpp: initialization error
Could you give me some hints?

Hi, I met the same problem when use multi-GPU, have you solved this problem?


No editor class for the element WeaponSwitch

When I clicked on the element, the editor it said there was no editor class. The editor also asked me to report this issue, which linked me here.

This is a custom element used on Proving Grounds and the COD Zombies maps.


Triggering API call from click event

I'm trying to trigger a .select() call when clicking a button next to the awesomplete input, but whatever function I call (I've tried open(), evaluate() and others too) absolutely nothing happens except that the awesomplete dropdown closes.
It seems as if the normal "click outside awesomplete to close it" code has higher priority or something?
If I change my click event to a mousedown event it starts working so this is how I've solved it at the moment, but just thought I'd point this out and perhaps get some clarification as to why this is happening.
Thanks

@powerbuoy Yes, the item is selected on mousedown event. See a related discussion here https://github.com/LeaVerou/awesomplete/pull/16715#issuecomment-114005608
I'm closing this issue for now, until we have a super robust test suite with cross-browser testing setup. However...
@LeaVerou What's your opinion on this:
I think we should later consider using click as it makes more sense than mousedown. A standard behavior is for click to work after mouseup only if it happens on same element as a mousedown event.
For example you can press mouse button on item, then move mouse cursor outside completer, then un-press mouse button. This shouldn't be considered as item was really selected.

Yes, we should. As I've mentioned elsewhere, I originally had click there and changed it to mousedown because Safari was a douchebag.


[DDW-131] Connecting a hardware wallet

This PR adds Connecting to a Hardware wallet screens with instructions how to setup and connect your device with Daedalus.
Todos

[x] Fix lint/flow issues
[x] Adding missing elements
[x] Fix scss styling issues

Screenshots

Testing Checklist

Slack QA thread
[ ] Test

Review Checklist
Basics

[ ] PR has been assigned and has appropriate labels (feature/bug/chore, release-x.x.x)
[ ] PR is updated to the most recent version of the target branch (and there are no conflicts)
[ ] PR has a good description that summarizes all changes
[ ] PR has default-sized Daedalus window screenshots or animated GIFs of important UI changes:

[ ] In English
[ ] In Japanese

[ ] CHANGELOG entry has been added to the top of the appropriate section (Features, Fixes, Chores) and is linked to the correct PR on GitHub
[ ] Automated tests: All acceptance and unit tests are passing (yarn test)
[ ] Manual tests (minimum tests should cover newly added feature/fix): App works correctly in development build (yarn dev)
[ ] Manual tests (minimum tests should cover newly added feature/fix): App works correctly in production build (yarn package / CI builds)
[ ] There are no flow errors or warnings (yarn flow:test)
[ ] There are no lint errors or warnings (yarn lint)
[ ] There are no prettier errors or warnings (yarn prettier:check)
[ ] There are no missing translations (running yarn manage:translations produces no changes)
[ ] Text changes are proofread and approved (Jane Wild / Amy Reeve)
[ ] Japanese text changes are proofread and approved (Junko Oda)
[ ] UI changes look good in all themes (Alexander Rukin)
[ ] Storybook works and no stories are broken (yarn storybook)
[ ] In case of dependency changes yarn.lock file is updated

Code Quality

[ ] Important parts of the code are properly commented and documented
[ ] Code is properly typed with flow
[ ] React components are split-up enough to avoid unnecessary re-renderings
[ ] Any code that only works in main process is neatly separated from components

Testing

[ ] New feature/change is covered by acceptance tests
[ ] New feature/change is manually tested and approved by QA team
[ ] All existing acceptance tests are still up-to-date
[ ] New feature/change is covered by Daedalus Testing scenario
[ ] All existing Daedalus Testing scenarios are still up-to-date

After Review

[ ] Merge the PR
[ ] Delete the source branch
[ ] Move the ticket to done column on the YouTrack board
[ ] Update Slack QA thread by marking it with a green checkmark

@DeeJayElly boxes missing borders

theme-red

Added

@DeeJayElly boxes missing borders

regular border color = input border coor
active item border color = link color
error item border color = theme-red

Added

middle border is doubled
can we remove non-active one?

middle border is doubled can we remove non-active one?

Done

@DeeJayElly are you going to apply themes here too?
Or it's just for light-blue one only?

BTW https://zpl.io/aworEw1 here you can see all crops dedicated to one device (if we can differentiate ledger x from s)

@DeeJayElly are you going to apply themes here too?
Or it's just for light-blue one only?

Themes are applied

Add stories with connected HW, so with HW sidebar, pages etc.
Fix flow issues
Fix eslint issues
You forgot to define scss variables in thems/utils/createTheme
Run translations manager

Done with all of these items @tomothespian

@DeeJayElly in netlify borders disappeared

@DeeJayElly in netlify borders disappeared

UPD: and all screens are the same

Fixed

@a-rukin can you check the latest changes?

Well, I've checked
Steps looks ok
I'm curious if this PR will include:

theming
specific cases when we detect specific device (atm trezor has image with 3 devices and ledger with 2)


Any plan to use llvm/clang

Any plan to build toolchains using llvm/clang?
Similar to this:
https://github.com/aka-mj/musl-cross-make-clang/blob/clang/litecross/Makefile.clang

At the moment, there are no plans for this.


Added support for nest.land modules

Fixes #31.
Description
These changes allow the user to update and check x.nest.land dependencies (including std ones) using dmm, in the same way that deno.land/x modules are currently handled.
Other Notes

dmm info still only looks for deno.land modules - it could be nice for it to look for a nest.land package as well.
I changed the module interface a little so that denoLandURL is now moduleURL and githubURL is now repositoryURL, so that it isn't as deno.land/x specific.

Oh, I need to update the readme too...

Hye @TheWizardBear really nice work!! :D I don't suppose 1 or tests could be added for the check command? Just to ensure that works when it checks a dep that is a nest import eg dmm check cliffy

Done.

Thanks :)

Hi, I think the label should be hacktoberfest-accepted. Would you be able to change it?

@TheWizardBear sure, all done, by mad!

Sorry to be a pain but you managed to misspell hacktoberfest this time.  🙃

For crying out loud! xD There we go, and it's no problem :P


[BUG]

Describe the bug
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior:

Go to '...'
Click on '....'
Scroll down to '....'
See error

Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
Add any other context about the problem here.

2562-05-06 5:47 GMT+07:00, Jason Etcovitch<EMAIL_ADDRESS>
Closed #211.
--
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub:
https://github.com/JasonEtco/todo/issues/211#event-2319834218


docs: add useSupportedLocalesOnly in changelog

Description
Follow-up #6073
Checklist:

[x] Securely signed commits
[] Component(s) with PHPDoc blocks, only if necessary or adds value
[] Unit testing, with >80% coverage
[x] User guide updated
[] Conforms to style guide

Fixed conflicts. Merging.


How to evaluate the LINEMOD dataset?

I appreciate this work on 6D Pose Estimation very much. In particular, I would like to ask, how to get the metrics on the LINEMOD dataset. How to process the LINEMOD dataset into the corresponding dataset of the project?

Hi, we are planning to release the dataset structure transformation code from the LINEMOD to our data structure and configs this week. Please stay tuned!


Information about anonymous policy usage doesn't make sense - please update

[Hello, in the below link there's contradictory information.
Example:
"You can use either policy, organization-wide or per-organizer, to manage anonymous join." (not really true, it's depending on what you want achieve. You can't only use per-organizer policy for allowing).
Followed by:
"Since both the organization-wide and per-organizer policies control anonymous join, the more restrictive setting will be effective."
Also the purple box doesn't really make sense. Please consider rephrasing that part too.
https://docs.microsoft.com/en-us/microsoftteams/meeting-settings-in-teams#using-powershell-to-configure-per-organizer-policy
You can perhaps use this purple box instead? https://docs.microsoft.com/en-us/powershell/module/skype/set-csteamsmeetingpolicy?view=skype-ps
-AllowAnonymousUsersToJoinMeeting (located at this parameter)
]
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 470478ed-3b4e-ced8-0e28-6cda545b8400
Version Independent ID: 95b4044b-3a47-a511-c726-b5ee75863441
Content: Manage meeting settings - Microsoft Teams
Content Source: Teams/meeting-settings-in-teams.md
Service: msteams
GitHub Login: @SerdarSoysal
Microsoft Alias: serdars

@ChristianJBergstrom thank you for reaching out. The article does mention that organization-wide policy setting will be deprecated in the future and the per-organizer policy will be the only way to control anonymous join, so it might be better to leave the wording as is, but please let me know if you still recommend having anything changed.


Alphabet text onreplay select screen it's weird, i mean position.

What it this dude?

oh shoot that wasn't supposed to happen

i'm gonna fix that

oh shoot that wasn't supposed to happen

Yeah i see LOL


cleanup and correct modifications for writable mtvec CSR

Hi Ivan,
My PR basically does the following things:

Rebase your changes on top of the current upstream master (lowrisc/ibex)
Squash your changes into a single commit with a different commit message.
Add 3 fixup commits, these should of course be squashed as well into your changes, but for you to see what was wrong I let them be. Please have a look and then do squash them into the main commit.

If you have any questions, please let me know.
Kind regards,
Pirmin
PS: I tested the changes and it works.

Please only squash the fixup! commits into your commit named "Make BASE field of mtvec CSR writeable".
All the previous commits are due to the rebase I did. If you rebase your branch first, they should disappear.

Hi,
I'm quite new to the more advanced features of git (rebase, squashing) so I'm sorry if i did something wrong in force-pushing. I tried rebasing the branch using the latest commit from ibex/master that was in the list above, but could only apply the changes by force-pushing and I was hoping it wouldn't mess anything up. The original changes are still in the branch ibex_mtvec_implementation_backup. Should I continue with the new state of this branch and merge the changes from your branch, or do you suggest something else?
Thanks,
Ivan

Hi Ivan,
thanks for your feedback.

If it is okay for you, will directly squash the 3 fixup commits locally and then push to master. So you don't have to mess with the rebasing and squashing at all.

I'm not sure what you mean here. If you mean squash the commits in your branch and push them to ibex/master from there, that's fine with me.

Yes, that is what I meant. Sorry for the confusion.
Best,
Pirmin


[CodeComplete] Return true from canParseType if type contains code completion token

From my point of view, a type that contains a code completion token can still be parsed as a type and as such, canParseType should return true for e.g. #^COMPLETE^# or SomeType.#^COMPLETE^#.
Changing this fixes an issue that caused no type completions to be shown inside a enum case decl.
Fixes rdar://71984715

@swift-ci Please test

Build failed
Swift Test OS X Platform
Git Sha - 695c725f1e2ee2bfa7860db4b2c969f8f326b57b

@swift-ci Please test macOS

Build failed
Swift Test OS X Platform
Git Sha - 695c725f1e2ee2bfa7860db4b2c969f8f326b57b

Test failures in LLDB for the full test suite seem unrelated. Let’s go for smoke tests only.
@swift-ci Please smoke test macOS


Remove the publishing process to s3.

It worked from Dario's local machine, was never integrated into TeamCity process and does not make that much sense anyway.

Are you sure that none of our builds use that?

I didn't see references at least.


Some floating content inside one of the selected elements breaks equal height of subsequent ones

Hi there,
first of all, this is by far the best equal heights plugin out there. So thank you.
However, I've found this case (simplified in the jsfiddle) where it fails:
http://jsfiddle.net/qoaa7d96/1/
I broke this down to the floating figure in the first box being the cause. Switch off float: left for the figure and everything works as expected.
Thanks for looking into it.
Regards
Danilo

Anyone please?

I have the same problem. One extra line made it work, namely adding overflow: hidden to the set of CSS rules that are used to determine rows.
See my fiddle at https://jsfiddle.net/xk8du4zp/1/. The line is at line 193.

Yes, but something like a box-shadow gets clipped with overflow: hidden. The clearing method I use in my fiddle is surely among best practices for clearing floats. So I still think, this is a problem with the plugin, not the CSS, isn't it?

What do you mean with this? The overflow: hidden is only applied when matchHeight changes the heights to 100px so measure the rows. Afterwards, it should be removed.

Ah, I didn't look at your fiddle. I thought you mean adding overflow: hidden; to clear the floats to my CSS (not the plugin), which would've worked, too, but in my real code I have a box-shadow on the .box that gets clipped with overflow: hidden;.
So, yeah, your suggestions seems worth a pull request?

It took me a while to make a good test case to go with the pull request.

Looks good guys, I'm super busy right now but I'll try it out and merge soon.
Thanks for tracking down the solution @jorrit!

Thanks for letting us know!

Awesome. Thanks a lot @jorrit and @liabru.


Partially revert #4091 (fix release mode crash)

Resolved / Related Issues
Fixes #4117
Details of Changes
Partially reverts #4091 to fix a (WinUI 2.6?) issue for which the app crashes in Release mode.
Reverts UI changes in #4091, while keeping the fixed logic.
Validation
How did you test these changes?

[ ] Built and ran the app -> waiting for Release build from CI
[x] Tested the changes for accessibility

Uooa ok, it's not #4091 fault after all.

@gave92 The issue appears to be because of WinUI 2.6, this issue will likely be resolved once WinUI 2.6 is out of preview. For the meantime, I have been reverting back to WinUI 2.5 for the preview builds.


Add configurable storage class name for image resource

If set, will be used as the storageClassName in the pvc

I'm wondering if we actually need to validate that the storage class exists since that will require additional rbac for our controller. If we create a pod with an invalid storage class can't we just let pod fail?

Does this need to be supported in v1alpha1 apis? https://github.com/pivotal/kpack/pull/934#issuecomment-1063374631

@matthewmcnew

Does this need to be supported in v1alpha1 apis? https://github.com/pivotal/kpack/pull/934#issuecomment-1063374631

converting v1alpha1 -> v1alpha2:
storageClassName is always "", v1alpha2 clients will use ""
converting v1alpha2 -> v1alpha1:
v1alpha1 client (old version of kp) patches existing v1alpha2 image, causing storageClassName to be set to "" which will violate the immutability constraint causing blocking error. This is not great.
My 2c is that if an old v1alpha1 client runs into an immutability error it will not lose data. If the storageClassName is unset in v1alpha2 behavior will not be affected by v1alpha1 clients. Users should upgrade kp.

v1alpha1 client (old version of kp) patches existing v1alpha2 image, causing storageClassName to be set to "" which will violate the immutability constraint causing blocking error. This is not great.

This seems rare but, not great. It essentially means we are not supporting v1alpha1.

It essentially means we are not supporting v1alpha1.

risk seems very high

If our strategy for v1alpha1 headaches is to say not use v1alpha1 we should probably just begin removing v1alpha1.

If we don't do this will we need to migrate all new fields to prevent data loss? ex DefaultProcess, ProjectDescriptorPath, CreationTime ?

If we don't do this will we need to migrate all new fields to prevent data loss? ex DefaultProcess, ProjectDescriptorPath, CreationTime

We probably should provide support for these. Hitting an expected immutability constraint seems slightly worse to me.

Hitting an expected immutability constraint seems slightly worse to me.

I think data loss is equal if not worse

I think we should probably add migrations

I think we should probably add migrations

Do you think we should do that as this PR or create an issue to support it for all susceptible fields?

I've added the conversion for this one here and have added https://github.com/pivotal/kpack/issues/1036

Codecov Report

Merging #1029 (fe5d98d) into main (e9d424b) will decrease coverage by 0.06%.
The diff coverage is 54.54%.

:exclamation: Current head fe5d98d differs from pull request most recent head 425de88. Consider uploading reports for the commit 425de88 to get more accurate results

@@            Coverage Diff             @@
##             main    #1029      +/-   ##
==========================================
- Coverage   70.53%   70.47%   -0.07%
==========================================
  Files         122      122
  Lines        5726     5740      +14
==========================================
+ Hits         4039     4045       +6
- Misses       1313     1319       +6
- Partials      374      376       +2

Impacted Files
Coverage Δ

pkg/apis/build/v1alpha2/image_builds.go
69.49% <0.00%> (-1.61%)
:arrow_down:

pkg/apis/build/v1alpha2/image_types.go
50.00% <ø> (ø)

pkg/apis/build/v1alpha2/image_conversion.go
85.26% <57.14%> (-3.11%)
:arrow_down:

pkg/apis/build/v1alpha2/image_validation.go
98.21% <100.00%> (+0.01%)
:arrow_up:

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more

will merge after 0.7.1 is released


TLSOptions do not get applied

Welcome!

[X] Yes, I've searched similar issues on GitHub and didn't find any.
[X] Yes, I've searched similar issues on the Traefik community forum and didn't find any.

What version of the Traefik's Helm Chart are you using?
21.2.1
What version of Traefik are you using?
2.9.9
What did you do?
We have two ingress controllers in one namespace, handling different workloads.
I want to define a tlsoption for a namespace and apply it to every ingress object a traefik provides. Therefore, I defined the following values.yaml:
fullnameOverride: ${fullnameOverride}

image:
  registry: <registry>
  repository: traefik
  # defaults to appVersion
  tag: ""
  pullPolicy: IfNotPresent

service:
  spec:
    loadBalancerIP: ${loadBalancerIP}
  annotations:
    loadbalancer.openstack.org/timeout-client-data: "300000"
    loadbalancer.openstack.org/timeout-member-data: "300000"

ports:
  websecure:
    tls:
      enabled: true
      options: ${namespace}-tls-traefik-${instance}@kubernetescrd

tlsOptions:
  tls-traefik-${instance}:
    minVersion: VersionTLS12
    cipherSuites:
      - TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
      - TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256
      - TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
      - TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384
      - TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256
      - TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA256
      - TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305
      - TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305
      - TLS_AES_128_GCM_SHA256
      - TLS_AES_256_GCM_SHA384
      - TLS_CHACHA20_POLY1305_SHA256
      - TLS_FALLBACK_SCSV
    curvePreferences:
      - CurveP256
      - CurveP384
      - CurveP521
      - X25519

rbac:
  namespaced: false

logs:
  general:
    level: INFO
  access:
    enabled: true

providers:
  kubernetesCRD:
    labelSelector: expose_via in (${labelSelector_expose_via}, all)
  kubernetesIngress:
    labelSelector: expose_via in (${labelSelector_expose_via}, all)

additionalArguments:
  - "--providers.kubernetescrd.namespaces=${namespace}"
  - "--providers.kubernetesingress.namespaces=${namespace}"

However, when applying everything, the resources are present but no route is started because of an "unknown tlsoption" error.
What did you see instead?
Traefik cannot find the tlsoptions
What is your environment & configuration?
kubernetes v.1.24.8
Additional Information
No response

Hello @eddykaya ,
Thanks for your interest in Traefik and this report.
It seems to be a duplicate of #779, since you're using labelSelector.
You can workaround this issue by using extraObject. You can also submit a PR for fixing it.

PR: https://github.com/traefik/traefik-helm-chart/pull/815


[backport] Avoid zero division in F.normalize

Backport of #4769

[automatic post] Jenkins, test this please.

Jenkins CI test (for commit 9d84ff0de48f0f1f94d9493e3e2a4c8d15d34e88) failed with status FAILURE.
(For contributors, please wait until the reviewer confirms the details of the error.)

The test failures are not related to the PR.


Fix failing to read from blob store when upload checkpoint

What problem does this PR solve?
Issue Number: ref #6827
Problem Summary: When upload checkpoint, it is possible to read page which are already deleted and may fail to read it.
What is changed and how it works?
Previously, we always use the output of dumpSnapshotToEdit, but it may contain deleted page id which have not been gced. And if the page id is gced during the process of uploading checkpoint, the read may fail with all kinds of error;
Now we create a temp page directory use the output from dumpSnapshotToEdit, then do gc on it, and dumpSnapshotToEdit again to filter out all deleted page id to eliminate this kind of error.
Check List
Tests

[x] Unit test
[ ] Integration test
[ ] Manual test (add detailed scripts or steps below)
[ ] No code

Side effects

[ ] Performance regression: Consumes more CPU
[ ] Performance regression: Consumes more Memory
[ ] Breaking backward compatibility

Documentation

[ ] Affects user behaviors
[ ] Contains syntax changes
[ ] Contains variable changes
[ ] Contains experimental features
[ ] Changes MySQL compatibility

Release note

None

/run-all-tests

/rebuild

/run-all-tests

/run-all-tests

/run-integration-test

PTAL @JaySon-Huang @JinheLin

/merge

/merge

/run-integration-test

/cherrry-pick release-7.1

/cherry-pick release-7.1


Add associations for networks and nics on Vms

There is an association to get disks through hardware which is a nice
convenience to not have to go to the hardware.
This makes it easier to do e.g.:
GET /api/vms?expand=resources&attributes=name,networks,nics,lans,disks
in a single API call
Fixes https://bugzilla.redhat.com/show_bug.cgi?id=1805789

Ivanchuk backport details:
$ git log -1
commit d5ffc54033fc902016cba5b0086c27a02717b442
Author: Jason Frey<EMAIL_ADDRESS>Date:   Fri Feb 21 09:36:20 2020 -0500

    Merge pull request #19861 from agrare/add_networks_and_nics_to_vm_or_template

    Add associations for networks and nics on Vms

    (cherry picked from commit 504aab9c408c3990f8cfa4da5e4ff570a926e5b8)

    Fixes https://bugzilla.redhat.com/show_bug.cgi?id=1805923


Move tests in cli/src to different directory

There's too much going on in that directory.

someone did this.


fix auth pls

can't auth with plugin :(

Did this get resolved? I didn't realize until now that the recent cookie reauth changes would likely affect this repo.

yep, i fix it.
i added &nonce=1 at the end
const signInUrl = 'https://auth.riotgames.com/authorize?redirect_uri=https%3A%2F%2Fplayvalorant.com%2Fopt_in&client_id=play-valorant-web-prod&response_type=token id_token'&nonce=1;


Add user lightcurve pre-processing open function

As well as we do a savgol filter with a short cadence, we could provide an open function as we do for ois filtering to do any processing wanted by the user before sherlock begins with the runs.

Done.


[FEATURE REQUEST]: Add a window pop up on each paste/drop for people to make a choice

I hope that when an image is pasted, a window can pop up for people to make a choice, as people's requirements are not always the same. If this can be achieved, I would both know that I need to perform an operation on the image to avoid accidental actions and have the option to choose how to handle the image differently.

And also allowing to edit the filename


No droplets show up

My account is authenticated well, since I see my snapshots etc. I can't see or access any droplets though.
Device google Nexus 5. DO with 2FA.

Update: uninstalled and reinstalled Swimmer, re-authenticated with DO. Still the same issue...

Update: I'm uninstalling. App's useless like this and I don;t like having a full access API key hooked up to a defective app.

Can you elaborate? What device are you using? do you get an error or any message to help investigate?

Nexus 5 device, no errors showing up.

Do you still run into this issue ?

Uninstalled, sorry. It didn't work and this conversation spans months.

If you ever install it again please let me know.

I had a similar issue recently, on install, no droplets, but images etc show up. After closing the app and reopening it shows them.

@hamid-elaosta i guess it is an edge case and i need to do more tests.

same here, I'm on a Samsung Galaxy S5. Seems not to be a Problem with the Device.

@okaufmann is it only droplets or all the other screens that are empty ?

Just Droplets. I try to find it ou this morning by just reviewing the code but don't found abything suspect... in this context. Why you don't write a little contribution guide for people like want to help?

You can fork the application and make a pull request! you are always welcome. Meanwhile i will look into this issue.

Yes, I know how to contribute on github.
But it's been a while since my last Android Studio Project. So I though you could write the main points when set up the project in one's android studio and what you use to run (Native on a Phone, a vm or genymotion) and so on. So a helpful buddy like me do not walk right into common traps :sweat_smile:
sorry for the obscurity

Same thing here. Able to authenticate. I can see my domain list. But the droplet list is empty.

When I first opened it, my droplets weren't listed, but I pulled-down to refresh and BOOM they were all there.
The solution could be as simple as forcing a refresh when the view changes.

No. Tried that...
On Wed, Jun 8, 2016, 08:18 jmeit<EMAIL_ADDRESS>wrote:

When I first opened it, my droplets weren't listed, but I pulled-down to
refresh and BOOM they were all there.
The solution could be as simple as forcing a refresh when the view changes.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/yassirh/digitalocean-swimmer/issues/45#issuecomment-224499406,
or mute the thread
https://github.com/notifications/unsubscribe/AIprFu-3zyrXiYTNPn87X9lS2meCpz2oks5qJl7QgaJpZM4Ftd0S
.

@jmeit This is what happened to me, they did load after I refreshed, so this particular issue should be as simple as refreshing the page.
@actuallymentor Perhaps yours is a different issue.


Fix draft order tax mismatch

Tax for draft order calculated by us and returned by Avalara differ. It's caused because of division total price be quantity and then multiplying the unit price by this quantity.
This PR introduces calculate_order_line_total plugin method that returns the total price for the order, returned by the plugin.

Impact

[ ] New migrations
[ ] New/Updated API fields or mutations
[ ] Deprecated API fields or mutations
[ ] Removed API types, fields, or mutations
[ ] Documentation needs to be updated

Pull Request Checklist

[ ] Privileged queries and mutations are guarded by proper permission checks
[ ] Database queries are optimized and the number of queries is constant
[ ] Database migration files are up to date
[ ] The changes are tested
[ ] GraphQL schema and type definitions are up to date
[ ] Changes are mentioned in the changelog

Task linked: SALEOR-2715 Avalara draft orders tax mismatch


Rate limit fix

🚀 🚀 Pull Request
Impact

[ ] Bug fix (non-breaking change which fixes expected existing functionality)
[ ] Enhancement/New feature (adds functionality without impacting existing logic)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Description
When sending too much data to openai it was raising RateLimitIssue as they seem to set some restrictions on how many bytes can be sent in one minute. In this PR I propose a solution when manually put sleep after certain amount of  data has been transferred. This solution applies only to extend.

Things to be aware of

Things to worry about

Additional Context

 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.adolkhan seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


One dep pr to rule them all part2

Pulls in minor/patch updates for main dependencies, and some major updates for test dependencies. Ignores major updates for core deps.
Closes these dependabot PRs:

https://github.com/Cray-HPE/canu/pull/511
https://github.com/Cray-HPE/canu/pull/512
https://github.com/Cray-HPE/canu/pull/513
https://github.com/Cray-HPE/canu/pull/515
https://github.com/Cray-HPE/canu/pull/516
https://github.com/Cray-HPE/canu/pull/517

@trad511 I tested this PR with the following commands on redbull:
canu validate shcd -a tds --shcd ./Shasta\ River\ Redbull\ CCD_RevA16.xlsx --tabs 25G_10G,NMN,HMN --corners I15,Q50,I9,S10,I20,S30 --log DEBUG --json --out ccj.json
ll
canu generate network config --ccj ccj.json --csm 1.6 --sls-file redbull/sls_input_file.json --folder generated
canu validate switch config --ip <IP_ADDRESS> --generated ./generated/sw-spine-001.cfg --remediation


Document IoT pattern for Business Integration

This document is pretty complete, but my team and I were looking deeper into this subject and we noticed that it covers generic patterns for IoT, but no mention to business integration. Does it make sense to add it here?
Integration to Field Service (Dynamics 365) could be a pattern to be described here.
We have created some internal documentation that could be included here with these information. Let me know if that makes sense.

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

ID: 31ca594d-a7ec-c1d3-cda0-6c151b32093f
Version Independent ID: 40f1584c-50fe-c690-9529-fc168853e001
Content: IoT monitor and manage loops - Azure Example Scenarios
Content Source: docs/example-scenario/iot/monitor-manage-loop.md
Service: architecture-center
Sub-service: example-scenario
GitHub Login: @hanuk
Microsoft Alias: pnp

Thanks for reporting - this issue is under review.  This is a Microsoft Internal DevOps Bug ID AB#337286

@squassina Thanks for the question! We are investigating and will update you shortly.

#please-close


1D, 2D, 3D viewing

The viewer should supports 3 modes:
1D: Using vispy plotting integrated in the scene graph
2D: current code
3D: Vispy volume renderer
The number of sliders is automatically adapted,
other types of objects (lines, points, etc..) should also be displayed
by simple projection in a straightforward manner.

We've made good progress towards 3D rendering recently including #493 where we have merged support for 3D rendering with many of our layer types.
We haven't begun to address 1D rendering yet, but that could be a useful feature so I've made a new issue #516 to explicitly discuss 1D rendering and am closing this one.


Add google calendar support for publish events

This PR adds the support of google calendar. When an image is successfully published, it will add an event in a dedicated google calendar (see credentials and ID in gopass).

@arnaud-morvan  for the readme I have put an entry that says to call the script with the -h option for more info. It's a bit minimalistic maybe should be enough IMO. Tell me if I have to write more in the readme.

@arnaud-morvan  for the readme I have put an entry that says to call the script with the -h option for more info. It's a bit minimalistic maybe should be enough IMO. Tell me if I have to write more in the readme.


Clippy Allow too many arguments on generated file.

As a result of the BalancerV2WeightedPool contract we were running into a too many arguments warning:
for
    impl Contract {
        #[doc = "Generated by `ethcontract`"]
        pub fn builder<F, T>(
            web3: &self::ethcontract::web3::api::Web3<T>,
            vault: self::ethcontract::Address,
            name: String,
            symbol: String,
            tokens: Vec<self::ethcontract::Address>,
            normalized_weights: Vec<self::ethcontract::U256>,
            swap_fee_percentage: self::ethcontract::U256,
            pause_window_duration: self::ethcontract::U256,
            buffer_period_duration: self::ethcontract::U256,
            owner: self::ethcontract::Address,
        ) -> self::ethcontract::dyns::DynDeployBuilder<Self>

This PR adds #[allow(clippy::too_many_arguments)] to the top of just this method although it might be better off at the top of the file as a global thing to ignore.
Also fixed a few typos.

We appear to be failing some CI because of an unrelated issue:
 error: failed to parse artifact from source Npm("<EMAIL_ADDRESS>
Caused by:
    0: invalid artifact JSON ''
    1: failed to parse contract artifact JSON: EOF while parsing a value at line 1 column 0
    2: EOF while parsing a value at line 1 column 0
 --> examples/examples/sources.rs:8:24
  |
8 | ethcontract::contract!("npm:@gnosis.pm/owl-token@3.1.0/build/contracts/TokenOWL.json");
  |                        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

error[E0433]: failed to resolve: use of undeclared type `TokenOWL`
  --> examples/examples/sources.rs:27:20
   |
27 |     let instance = TokenOWL::deployed(&web3)
   |                    ^^^^^^^^ use of undeclared type `TokenOWL`

Is this something I should try and fix here?

Is this something I should try and fix here?

I restarted the CI. I had issues with unpkg.com (what we use for un-packaging npm packges) today that may be related to the error.

@bh2smith It looks like the failure was just an intermittent issue :tada:

Although it's still failing one of the builds.

Although it's still failing nightly

Nightly has allowFailure: true. Feel free to merge even if the build is failing.


Extracting the reusable bits

If you are watching this, please feel free to vote on what you'd like to see.  Otherwise, this is just some notes to myself.
Basic idea
Find the bits that could be reused and repackage them for reusability.
Two general kinds of reuse

standalone tools that take input files and produce output files
libraries which can be imported and used in a program

Almost everything here is Python, and that has the good fortune to be usable either way:

python package/foo.py blah blah to use it as a tool
from package import foo to use it in a Python script.

Thing is, the first way, the tools can inter-operate with generators/other tools in other languages.
Other thing is that, for the second, the directory that package is in has to be on your PYTHONPATH.  (Then this degenerates into a discussion about how best to do that, and how I don't like almost every packaging system, etc.)
So the first way should generally be preferred, but ideally, support both.
Possible things to extract

guten-gutter: yes.  It does at least as good a job as gutenizer now, and is more extensible (can clean out illustrations, etc.)  Built on a framework of "cleaners", which are just line-based filters/transformers.
fetch-chronam: probably not.  Or, rather, only if it is possible to merge it with wikimedia-illustrations somehow.  (The scraping code there really deserves to be extracted.)
image-calipers: ehh, probably not.
autoseed: yes; needs to be fleshed out since it is currently only a sketch in my NaNoGenMo-2014 issue, and makes slightly more sense as a library, but could probably be turned into a tool too.
zzzpostprocess.py: yes; several entries had extra spaces between punctuation and so forth, so this could definitely be useful if refactored/expanded upon.  Would need some unit tests.
various copy-and-pasted code for splitting the input into sentences: well, maybe.  Apparently NLTK can do this too, and it probably does it better.  (But still, this would be public domain.)

What repo to put 'em in?
Could keep them in this repo, but it's a "lab".  Probably better to put them in a different (and new) repo.
What to call package?

NaNoGenLib -- I see what I did there, but maybe it's a little presumptuous.  You certainly don't need to use it for NaNoGenMo, and for NaNoGenMo you certainly don't need to use it.
KTLN, a toolkit for unnatural language processing -- I also see what I also did there.  Putative backronym is "Kitten Talks Like Nixon", although if "N" could stand for "Novel" somehow...
Maybe something more laconic like GenLabEquipment
Or maybe something perfectly strange and oblique like Bowl of ceramic abbots

Well, I said I'd do something with this, so, with NaNoGenMo 2015 fast approaching, I did eventually do something with this.

T-Rext cleans up spacing and punctuation in a text file.
Guten-gutter attempts to strip Project Gutenberg boilerplate from a text file (and succeeds more often than gutenizer does)
seedbank allows a 1-line change to any Python script to allow its random seeds to be recorded and replayed.

I abandoned the idea of exposing the over-engineering pipeline framework as a library, but it's still in the first two.
They all require Python 2.x (tested on Python 2.7.6 but will probably still work on some earlier versions) but only seedbank requires that you write your script in Python - the other two can be used as stand-alone tools.
They're all in the public domain.  Issues of bug reports and pull requests for reasonable enhancements welcome.


delete error handling function to avoid auto script running impact

Proposed change(s)
Delete error handling function to avoid auto script running impact
Useful links (GitHub issues, forum threads, etc.)
None
Types of change(s)

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[*] Code refactor (non-breaking change which refactor the code)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Documentation update only
[ ] Other (please describe)

Testing and Verification
This is a separate module, just run the install script.
Test Configuration
Mini Pupper Version
Mini Pupper 2
Raspberry Pi OS + ROS version
Ubuntu 22.04, ROS 2 Humble
PC OS + ROS version
Ubuntu 22.04, ROS 2 Humble
Checklist

[*] I have read the CONTRIBUTING guidelines.
[*] I have checked to ensure there aren't other open Pull Requests for the same change.

Other comments

OK


Custom command import fails

Hello.
Import of the sdk doesn't work.
Simple test.py with:
from splunklib.searchcommands import  dispatch, GeneratingCommand, Configuration
sdk installed with (Centos 8):
pip3 install -t . splunk-sdk
[root@splunk bin]# /opt/splunk/bin/python3 ./test.py
Traceback (most recent call last):
File "./test.py", line 1, in
from splunklib.searchcommands import  dispatch, GeneratingCommand, Configuration
File "/opt/splunk/etc/apps/test/bin/splunklib/searchcommands/init.py", line 145, in
from .environment import *
File "/opt/splunk/etc/apps/test/bin/splunklib/searchcommands/environment.py", line 120, in
splunklib_logger, logging_configuration = configure_logging('splunklib')
File "/opt/splunk/etc/apps/test/bin/splunklib/searchcommands/environment.py", line 103, in configure_logging
fileConfig(filename, {'SPLUNK_HOME': splunk_home})
File "/opt/splunk/lib/python3.7/logging/config.py", line 79, in fileConfig
handlers = _install_handlers(cp, formatters)
File "/opt/splunk/lib/python3.7/logging/config.py", line 126, in _install_handlers
hlist = cp["handlers"]["keys"]
File "/opt/splunk/lib/python3.7/configparser.py", line 958, in getitem
raise KeyError(key)
KeyError: 'handlers'

Ok. Managed to fix it. The splunk-sdk-python/examples/searchcommands_template/default/logging.conf doesn't work out of the box.


Ask only for the username for Joind.in-Link

Feature-Request:
Currently users can add a link to their joind.in profile. For that they need to enter the complete URL.
In my opinion it would be easier to let users enter their joind.in-username and to create the link  for them. That would then be the same process as for twitter.

@derrabus Fortunately (?), it looks like the validation for the URL had been restricted to joind.in links anyways, so users wouldn't have been able to put in other URLs


Make a more thorough heat map test

We should test that the position, size and pad arguments are respected.
https://github.com/quantumlib/Cirq/blob/3c0cf121bed80a88cdc94aebc29706e4ff858c6e/cirq/vis/heatmap_test.py#L244

Hi @pingyeh - are you still planning to work on this?

Not in Q3... but I definitely wants to resume my Cirq work in Q4 when my main project is in good shape.

cc @tanujkhattar to confirm but we can tackle this post 1.0 as this is for improving test coverage on visualizations.


Convert the diff_drive_controller into a ChainableControllerInterface in the master branch

I am currently working on designing a differential drive robot with advanced navigation and balancing capabilities using ROS2 Jazzy. I would like to configure my controllers in a chained configuration similar to the one described in the Controller Chaining Tutorial. However, in the ros2_controllers master branch it looks like the diff_drive_controller is still a standard ControllerInterface, not a ChainableControllerInterface, so I cannot put controllers that precede the diff_drive_controller.
I propose to convert the diff_drive_controller into a ChainableControllerInterface, and push these changes to the master branch.
I noticed that there is a chainable-diff-drive branch from last year that converts the diff_drive_controller into a ChainableControllerInterface as I desire. The problem is that this branch is many commits behind master at this point, and lacks functionality such as using TwistStamped instead of Twists for the velocity_command subscriber, among others. I would like to see the chainable-diff-drive branch merged with master (or, since this would be a complex merge, simply start from scratch using chainable-diff-drive as a guide).
I have not contributed to ros2_controllers before, but would be interested in taking this on as a challenge. My questions are:
Why was this merge not made before? What are the blockers or nuances that I should watch out for?

I created this for the 2023 ROSCon workshop but it never made it upstream, hence why it is out of date.
Let me put it here in link form for posterity: https://github.com/ros-controls/ros2_controllers/tree/chainable-diff-drive
You'd be welcome to follow up on this by creating a branch from this branch in your fork and creating a pull request that passes all CI checks, tests and adds new tests for the chainable functionality. Sounds good?

Sounds good. I will let you know if I have more questions.


Fix coverage

PR:

Resolves #291
Adds a .solcover.js config file with a test command that allows truffle to exceed node's default memory limit. (See solidity-coverage/issues/59 for details on why this is necessary.)
Updates coverage.sh to track recent changes in Zeppelin's testrpc launch
Updates yarn.lock to latest solidity-coverage (0.1.7)
Filters Migrations.sol from the coverage reports.
Modifies travis.yml to use sudo: required in order to get around container memory constraints. (Hat tip @federicobond)

Changes Unknown when pulling 5afbdf00dba439078e696bddbce7daccb8ce43e0 on cgewecke:fix-coveralls into ** on OpenZeppelin:master**.

Awesome!! Thanks a lot @cgewecke !! :D


HBASE-22490 Nightly client integration test fails with hadoop-3.0.3

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

0
reexec
41
Docker mode activated.

_ Prechecks _

0
shelldocs
0
Shelldocs was not available.

+1
@author
0
The patch does not contain any @author tags.

_ master Compile Tests _

_ Patch Compile Tests _

+1
shellcheck
2
There were no new shellcheck issues.

+1
whitespace
0
The patch has no whitespace issues.

_ Other Tests _

+1
asflicense
15
The patch does not generate ASF License warnings.

121

Subsystem
Report/Notes

Docker
Client=17.05.0-ce Server=17.05.0-ce base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-265/1/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/265

Optional Tests
dupname  asflicense  shellcheck  shelldocs

uname
Linux 5eda6945ab2f 4.4.0-137-generic #163~14.04.1-Ubuntu SMP Mon Sep 24 17:14:57 UTC 2018 x86_64 GNU/Linux

Build tool
maven

Personality
/testptch/patchprocess/precommit/personality/provided.sh

git revision
master / 25c6cd3a4f

maven
version: Apache Maven 3.5.4 (1edded0938998edf8bf061f1ceb3cfdeccf443fe; 2018-06-17T18:33:14Z)

shellcheck
v0.4.4

Max. process+thread count
41 (vs. ulimit of 10000)

modules
C: . U: .

Console output
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-265/1/console

Powered by
Apache Yetus 0.9.0 http://yetus.apache.org

This message was automatically generated.


[popup] Popup addTouchEvents setting is not applied

http://jsfiddle.net/2hm3nmLx/
Try this fiddle on touch device. Popup is still opened.
hasTouch in code is always true, not based on popup settings?

This issue was opened a year ago, and based on my attempt on blocking the popups on my test phone, it's still valid.

true story, happens here to

Reproducible with latest Semantic-UI build.
Reproduced by enabling touch events on Firefox and clicking the text.

Wanted to fix it, but encountered some problems. Here’s the part that sets the touchstart event:
if(settings.on == 'hover' && hasTouch) {
  $module
    .on('touchstart' + eventNamespace, module.event.touchstart)
  ; // Show a popup on `touchstart`.
}

As mentioned above, hasTouch is always true, and addTouchEvents is actually never used:
hasTouch = (true),

As far as I understand, the whole point of addTouchEvents is to disable any kind of interactivity on touch devices. The problem is with this part that immediately follows the touchstart:
if( module.get.startEvent() ) {
  $module
    .on(module.get.startEvent() + eventNamespace, module.event.start)
    .on(module.get.endEvent() + eventNamespace, module.event.end)
  ; // Show a popup on `mouseenter` and hide it on `mouseleave`.
}

Most of the touch devices will still trigger mouseenter and mouseleave, maybe it won’t be happening most of the time, but some accidental slide towards a div instead of a tap will still show a popup, so it’s rather pointless to disable touchstart.
We could detect touch devices and disable mouseenter/mouseleave for them, but the detection is unreliable, and there’s a lot of devices that support both touch and mouse inputs—it would make the experience bad for these people.
There’re other solutions to allow all types of events exist at the same time, but I personally find them terrible, and I’m not sure if we can do better. The fact that different browsers might implement event order differently also makes things harder, for example, in Chrome, we can’t disable mouse events on touchstart and enable them again on touchend, because mouse events will be fired after touchend.
The last thing I tried was the timer that basically temporarily disables mouse events while touchstart is active:
if(settings.on == 'hover' && settings.addTouchEvents) {
  $module
    .on('touchstart' + eventNamespace, module.event.touchstart)
  ;
} else if (settings.on == 'hover' && !settings.addTouchEvents) {
  $module
    .on('touchstart' + eventNamespace, function (event) {
      if (!timeoutIsRunning) { // Initially, set it to `false` at the top.
        timeoutIsRunning = true;

        $module
          .off('mouseenter mouseleave')
        ;

        window.setTimeout(function () {
          $module
            .on('mouseenter' + eventNamespace, module.event.start)
            .on('mouseleave' + eventNamespace, module.event.end);

          timeoutIsRunning = false;
        }, 2000) // The number might be even lower.
      }
    })
  ;
}

It works, nobody will probably notice the delay. I don’t know what to do with it, maybe I missed something, what do you think? Here’s a minified and embedded JSFiddle with the timer if you’d like to take a look.

Wow how is this still a thing? They added a setting to disable adding the touch even and never used it.  TWO years later after being reported and being a very simple thing to do I find myself here.

Fixed. See http://jsfiddle.net/2hm3nmLx/7/show


Turn off bean removal by ArC

By default ArC removes unused beans but that does not work very well with Camel as it does use BeanManager behind the scenes to look-up beans from the container and ArC can't be aware of what Camel need.
We probably need to discuss this topic with the Quarkus team and see if through a build item it could be possible to reverse the behaviour so not to remove beans unless that feature is turned on explicitly.
Taken from: https://github.com/apache/camel-quarkus/pull/1344#discussion_r440015225

I'll close this as it's superseded by https://github.com/apache/camel-quarkus/issues/2822.


No Item from Vote Crate :(

https://user-images.githubusercontent.com/106904622/172041145-84d172a0-433d-462e-b7d7-7bdb7609777a.png

Was bout to make a ticket for the chat broadcast. But I'll post it here instead lol

This is now fixed, thank you for the report :)


Update Release Docs TODOs leveraging Jonathan's recent guidelines

Migrated from GitLab: https://gitlab.com/meltano/meltano/-/issues/1285
Originally created by @derek-knox on 2019-11-08 16:29:36

Regarding our release process https://meltano.com/docs/contributing.html#release-process, we know have some updated guidelines to follow. @kressaty Can you provide the links to these? IIRC we at least have one for YouTube, but maybe others.
The goal of this issue is to then update our release process docs with Jonathan's shared links so we have a single-source-of-truth to reference during releases.

[ ] add links to the various guidelines for social communications (YouTube at least, maybe more)

View 3 previous comments from the original issue on GitLab


Add multiple delete command

delete 1, 2 will delete indices 1 and 2
delete 1 will work as per normal

LGTM!


[Bug]: 'Arkanoid' Game Errors

Give a brief about the bug discovered✍
Many factors in the design of this game are creating bad experience for user. The most prominent is that the ball hiter and the heading are colliding thus text of heading is not visible. Besides that, color and other designing of the game can also be improved by working on styling.
What is the expected behavior?
Clear design of the game.
Give a brief description to get the expect behaviour.
By working on the styling of the game, I can remove these bugs and improve its design.
Screenshots
Current Design

Expected Updated Design

Are you contributing for a program?
GSSoC2023
Code of Conduct

[X] I follow CONTRIBUTING GUIDELINE of this project.

@panwar8279

Hi @iamRabia-N , I have assigned this issue to you. Kindly complete within 2 days. Good luck!


Feature Proposal: support components

Hello, great library, useful for many common scenarios. After some time I have a need to extend the functionality in a way that we could use React components in TruncateMarkup .
Common use case: display a list of components, either created with react html markup or actual react (class/functional) components, and display only as many components as possibly - based on their size.

I understand there is no way how to possibly split react components. That's not my intention.
Proposal:
Solution 1 - Atomic Elements
This option was already discussed in some older PR
<TruncateMarkup>

    { /* ... can have custom Components inside */ }
    { /* ... can have more DOM nodes inside */ }
   {/* or possibly with a custom component provided by this lib */}
    <TruncateMarkupAtom>{ /* ... can have custom Components inside */ }</TruncateMarkupAtom>
    <TruncateMarkupAtom>{ /* ... can have more DOM nodes inside */ }</TruncateMarkupAtom>

</TruncateMarkup>

This seems to be a easy solution as long as there is good way to indicate that a element/Component should not be analyzed any further.
Props types stay the same thus it doesn't introduce breaking changes.
1.1 Is a component preferred over some custom prop? Or maybe let's just see what ever is easier to do..
1.2 In either way, I think we'll need to check children (=potential Atom) props - that doesn't sounds great, but to some extend that is already happening in the lib. Right now, I am not aware of a way how to easily and reliably check if a node is create by a specific React component. Or is there a way ?
Solution 2 - New tokenize Option
a new tokenize option could be aslo a way, but the more I think about it, the more complex it is. Either to document what that option would and wouldn't do, or to provide multiple tokenize options for slightly different usecases. The complexity of the code handling these options would get just more complicated than it needs to be.
I am willing to do a PR. I'd like to reach some kind of agreement here before doing that so the time is well spent :smile:

@stropho I think this is a good idea! I'd definitely prefer the simplicity of providing a component like TruncateMarkupAtom 👍 there should be ways to easily and safely detect this component. checking node.type === TruncateMarkupAtom should work fine 🤞


Handle 100 file limit for EIA 860M Zenodo archiving

Zip all months for one year into a list of year_months.

This should live in the pudl-archiver repo.


Move BuildServiceRegistry up to the Build service scope

Move its SharedResourceLeaseRegistry dependency along with it.
So other build scoped services can have access to it.

@bot-gradle test this

OK, I've already triggered the following builds for you:

PullRequestFeedback build

@bot-gradle test and merge


Add support for getSupportedVoices() on iOS

This is at least a quick fix for issue #37 which is working for my use case.

Thank you for your contribution. I will review it in the next few days.

Please always submit unrelated changes in separate pull requests.
I will test your first change soon.
For the second change I've found another fix which supports IETF BCP 47 language tag strings (see #66).
So the second change should not be necessary anymore.

Sorry for that second commit — meant to commit it to my own local branch, not add it to the PR. My mistake!

@robingenz Any chance we can get an update on this?

@ecc521 This pr is waiting for the requested changes. Feel free to submit a new PR.

@robingenz Done! #89

I'd completely forgotten this one even existed -- apologies and thanks for the new PR, @ecc521.


Formatting according to YAML data

I'm falling in love with this plugin and I am implementing it in my everyday use.
To set my vault I followed your tutorial (https://www.youtube.com/watch?v=gOkniMkDPyM&t=1499s) and I changed the style of some of my tags.
In my case unfortunately I don't use tags to specify if that note is a permanent or a literature note but I use a different field in the YAML section. So in this case is impossible to customize the appearance of my notes according to their type.
Do you know if exist a way or an implementing path in the next future for this appearance setting?
Thank you for your work.

formatting is currently limited to tags.
Can you show me a sample of YAML data you'd like to use for formatting?

Sure! Here I upload a sample of my YAML data


GSD Request

--- GSD JSON ---
{
  "vendor_name": "Linux",
  "product_name": "Kernel",
  "product_version": "versions from v4.5 to before v5.15.25",
  "vulnerability_type": "unspecified",
  "affected_component": "unspecified",
  "attack_vector": "unspecified",
  "impact": "unspecified",
  "credit": "",
  "references": [
    "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=2f4ce5ec1d447beb42143a9653716a2ab025161e",
    "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=f8ba235c4927b5f970c868ac101ec42ca16c183a"
  ],
  "extended_references": [
    {
      "type": "commit",
      "value": "2f4ce5ec1d447beb42143a9653716a2ab025161e",
      "note": "introduced"
    },
    {
      "type": "commit",
      "value": "f8ba235c4927b5f970c868ac101ec42ca16c183a",
      "note": "fixed"
    }
  ],
  "reporter": "joshbressers",
  "reporter_id": 1692786,
  "notes": "",
  "description": "libsubcmd: Fix use-after-free for realloc(..., 0)\n\nThis is an automated ID intended to aid in discovery of potential security vulnerabilities. The actual impact and attack plausibility have not yet been proven.\nThis ID is fixed in Linux Kernel version v5.15.25 by commit f8ba235c4927b5f970c868ac101ec42ca16c183a, it was introduced in version v4.5 by commit 2f4ce5ec1d447beb42143a9653716a2ab025161e. For more details please see the references link."
}
--- GSD JSON ---

This issue has been assigned GSD-2022-1000468


[Task]: Scroll to a line with a hidden comment

What needs to happen?
Currently examples use conext-line hidden comment with an index of a line to scroll to.
Allow to mark a line with // scroll-to comment instead.
Issue Priority
Priority: 3
Issue Component
Component: beam-playground

.take-issue


Connect to TestDataCenter and use generic phone number and Code

closes #115
closes #121
Added new API-Key
Important
Usage of your phone number is only activated if your account is registred in testmode.
Do this here: Register
Better: Use the phone number and code written in the README.

Please refactor this so that default behaviour is that we have a normal api, that user doesnt need to register, and the test-api is only used in Test-cases.

this is no longer needed due to #142


Sunsetting phat-binary for Windows

In reference to #2181 we will do the same for Windows.

[x] Upgrade should be posible
[x] Tray install and autostart (the deamon process is started by the tray so we only need to setup the tray to autostart)
[ ] #2469

[x] Clearer message about running crc setup after the installation (https://github.com/code-ready/crc/issues/2429)
[ ] Show clear failed message when installation fails (https://github.com/code-ready/crc/issues/2421)

[ ] Upgrade should be posible
[ ] Daemon install and autotstart
[ ] ...

The MSI installer is now the default, we no longer ship publicly the binary, but some of the items listed in the initial comment are still being worked on.

With the new electron tray, we'll launch the setup from the tray. The remaining items need to be implemented on the msi installer anymore


refactor auth

DO NOT CATCH THROWABLE, EXCEPTION, RUNTIMEEXCEPTION!
DO NOT CATCH THROWABLE, EXCEPTION, RUNTIMEEXCEPTION!
DO NOT CATCH THROWABLE, EXCEPTION, RUNTIMEEXCEPTION!
DO NOT DISCARD EXCEPTIONS!
DO NOT DISCARD EXCEPTIONS!
DO NOT DISCARD EXCEPTIONS!
Important things need to be said 3 times.

233


sort autofix incorrectly removes nested sorts

Minimal reproduction:
values = [(2, "b"), (2, "a"), (1, "b"), (1, "a")]
print(sorted(sorted(values, key=lambda x: x[1]), key=lambda x: x[0]))

prints out: [(1, 'a'), (1, 'b'), (2, 'a'), (2, 'b')]
After running ruff check reproduce_sort_issue.py
 Found 1 error (1 fixed, 0 remaining).
The "fixed" code is:
values = [(2, "b"), (2, "a"), (1, "b"), (1, "a")]
print(sorted(values, key=lambda x: x[0]))

prints out: [(1, 'b'), (1, 'a'), (2, 'b'), (2, 'a')]
> ruff --version
ruff 0.0.277

Looks like we need to avoid collapsing sorts with different keys.