Fix: Fixed cannot select Files in columns view

Resolved / Related Issues

[x] Were these changes approved in an issue or discussion with the project maintainers? In order to prevent extra work, feature requests and changes to the codebase must be approved before the pull request will be reviewed. This prevents extra work for the contributors and maintainers.
Closes #12090

Description

I simplified the code to find the last column that should remain open (I don't know why I wrote that complex code in the first place). Now it looks for the blade with the same path as the requested one.
As mentioned in #11898, there's a bug with double click to open

Notes

Please, test these changes deeply since they may cause many regressions
It may happen that the user creates a loop of columns (like: C:\Users\username\Desktop\shortcut_to_Users\username\Desktop\something_else). In this case, if the user clicks an item in Desktop, should we always close all columns after the first Desktop?

Validation
How did you test these changes?

[x] Did you build the app and test your changes?
[ ] Did you check for accessibility? You can use Accessibility Insights for this.
[ ] Did you remove any strings from the en-us resource file?

[ ] Did you search the solution to see if the string is still being used?

[x] Did you implement any design changes to an existing feature?

[x] Was this change approved?

[x] Are there any other steps that were used to validate these changes?
Test 1

Open app and a folder using colums view
Use Open folders with single click in columns view
Open a shortcut to a folder (try with a shortcut to a sub-subfolder of the current directory, a shortcut to a parent folder of the current and with one to a random folder)
Select a file
Test 2
Repeat all the steps above using double click to open
Navigate between folders using Up/Down arrows to ensure there's no regression from #11986
Test 3
Open a path such as C:\Windows\System32 in columns layout
Click on Windows (Single click to open option) (Check that there's no regression from #11898)

@ferrariofilippo can you target the servicing branch?

It may happen that the user creates a loop of columns

It is the same with Finder.

Do you have double click to open? In that case I know that bug (is the one I mentioned in the description) and I'm working on a fix

Do you have double click to open? In that case I know that bug (is the one I mentioned in the description) and I'm working on a fix

"Open items with a single click" is off, "Open folders with a single click in the Columns Layout" is on.
If the shortcut was not looped, the file could be opened without problems.

"Open items with a single click" is off, "Open folders with a single click in the Columns Layout" is on. If the shortcut was not looped, the file could be opened without problems.

Ok, I just understand what you meant. I mentioned that in the Notes

It may happen that the user creates a loop of columns (like: C:\Users\username\Desktop\shortcut_to_Users\username\Desktop\something_else). In this case, if the user clicks an item in Desktop, should we always close all columns after the first Desktop?

At the moment we can't know which column the user has clicked (that's an issue when we have three loops). Because of this, we have to choose between leaving open the first or the last occourence of the path

Everything should be fine now

There is still a little weird behavior with folder selection when columns are looping, but it's a different issue and much better than not being able to open files.

I can't reproduce it. Can you tell me more, please? (single or double click to open?)

I can't reproduce it. Can you tell me more, please? (single or double click to open?)

Look at this video.
https://user-images.githubusercontent.com/66369541/233562759-e38e01cb-7915-4994-a217-a874936ed012.mp4

Look at this video.

I can't reproduce it and, looking at the scrollbar on the bottom, it seems to work.
Do you have a loop like Documents/Downloads/Documents/Downloads/Documents? In that case clicking on the second Documents will close the following blades, but the view will also scroll and it will look like it's opening from the last column

I can't reproduce it and, looking at the scrollbar on the bottom, it seems to work.

Sorry, it is an oversight on my part. It works fine.

@ferrariofilippo @hishitetsu thank you for your work on this fix!


Configure Azure Pipelines

This pipeline configuration builds the application and produces a build for the Release configuration.

 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.:x: neperz sign nowYou have signed the CLA already but the status is still pending? Let us recheck it.


Find source of mystery file error with Java build.

Testing simple start/stop of the interpreter under Java reports java: : No such file or directory (no path given with the error).  Whisky Tango Foxtrot.
$ make run
POST4_PATH=".:../src:../examples" java -Djava.library.path="${POST4_PATH}" -cp ../.. post4.jni.Post4
java: : No such file or directory
CAFEBABE Monaco 377 e 2.718280PI 3.141590Planck's 6.626070E-34
ok

An addition error with the Java JNI build.
roche$ make testbye

***************************************************************
==> /home/achowe/git/post4/jni
***************************************************************

echo bye | POST4_PATH=".:../src:../examples" java -Djava.library.path="${POST4_PATH}" -cp ../.. post4.jni.Post4
post4: : No such file or directory
CAFEBABE Monaco 377 e 2.718280 PI 3.141590 Planck's 6.626070E-34

>> ARKER rm_user_words
>>                     ^
-5 thrown: return stack overflow
roche$

echo bye | POST4_PATH=".:../src:../examples" java -Djava.library.path="${POST4_PATH}" -cp ../.. post4.jni.Post4

In this command the variable POST4_PATH is defined for the child process only, not for the process that expands "${POST4_PATH}" when preparing the command line.
Try this for test:
POST4_PATH=".:../src:../examples" echo java -Djava.library.path="${POST4_PATH}" -cp ../.. post4.jni.Post4

It outputs: java -Djava.library.path= -cp ../.. post4.jni.Post4
To make the POST4_PATH environment variable available in both the parent and child process, you can do the following:
export POST4_PATH=".:../src:../examples" ; echo bye | java -Djava.library.path="${POST4_PATH}" -cp ../.. post4.jni.Post4

In my environment it also says about a fatal error:
post4: : No such file or directory
CAFEBABE Monaco 377 e 2.718280 PI 3.141590 Planck's 6.626070E-34
#
# A fatal error has been detected by the Java Runtime Environment:
#
#  SIGSEGV (0xb) at pc=0x0000000000000000, pid=266, tid=267
[...]
# An error report file with more information is saved as:
# /work/forth.data/repo/github/post4/jni/hs_err_pid266.log
[...]
Aborted (core dumped)

I've managed to duplicate it on Rocky Linux too (NetBSD works fine) from the terminal.  Oddly this error appears randomly with GitHub CI run (using Ubuntu Linux).  CI job fails, I ask to re-run without change and it passes.
Not sure how to debug this yet within Java.  It might be the case that some recent change hasn't been propagated to the JNI code.
As for the post4: : No such file or directory no clue yet.

Oddly this error appears randomly with GitHub CI run (using Ubuntu Linux). CI job fails, I ask to re-run without change and it passes.

This error may be random due to race conditions 🤔

Oddly this error appears randomly with GitHub CI run (using Ubuntu Linux). CI job fails, I ask to re-run without change and it passes.

This error may be random due to race conditions 🤔

You said an evil word(s): race conditions
Not sure where such would exist.

Post4 is single threaded, unless its something related to a signal (SIGSEGV) being queued before the Post4 SIGSEGV handler is installed.
Java being threaded might have some init threads running that haven't complete before the main context is created.

Food for thought fooood!</>

Another possible reason is that the address space layout is different in different runs (due to ASLR), and the bug is effective only in some cases.

Ya. That scares me too.

It might be the case that some recent change hasn't been propagated to the JNI code.

If you have a build/version that works fine, than git bisect can help to find the commit that introduces the bug.

Have moved the seg.fault issue into a separate issue #64.


PageUp/PageDown inside sap.m.StepInput also scrolls SplitPane content

OpenUI5 version: 1.52.5
Browser/version (+device/version): Chrome 64.0.3282.167
Any other tested browsers/devices(OK/FAIL):
URL (minimal example if possible):
User/password (if required and possible - do not post any confidential information here):
Steps to reproduce the problem:

Place a sap.m.StepInput in a SplitPane which has a vertical scrollbar
Put the cursor inside the input control and hit PageUp or PageDown

What is the expected result?
When focus is inside the StepInput control and user presses PageUp or PageDown to apply the largerStep to the value in the control the SplitPane should not change its scroll position
What happens instead?
Value is increased/decreased according to the largerStep setting but also the content of the SplitPane is scrolled up/down respectively
Any other information? (attach screenshot if possible)

@Frank683
Thank you for reporting the issue. It occurs when there is a scroll container around the StepInout. The issue is logged internally with ticket #1880197936 . My colleagues will follow up in this thread as well.


Fix bootDiskSize for gcp

bootDiskSize in the configuration file didn't work for gcp in my case, so I did a small fix.

Just released a new version with the correct fix. Closing this PR.


Group by 120 minutes

I thought it is easy and I just have to add a new option, but if I do so, the plugin disappears after a Grafana restart. If it is just adding a new option I am happy to create a pull request. Don't know if Grafana has a conflict if I make changes manually.
Maybe one additional question: If I have 2 overlapping entries, how would they be displayed? Next to each other or grouped?

I don't mind adding 120 minutes as well if you submit a pull request. Seems reasonable to me 👍
I'm not sure what you mean by "duplicate entries" though?


Andrew feature/update go version and fix golint

FT-2800
FT-2582

@kikito  could you please add some love here by reviewing :)

superseded by #112


Remove the http1 connection pool delay.

Remove the http1 connection pool delay.
This feature is incomplete in that libevent doesn't guarantee ordering of events
so delaying for a single poll cycle does not address the issue.
Also because the connection is left in the ready queue it is
available for another request coming in the same pool cycle or
in the next poll cycle before ready connection is processed.
Finally, this would only catch connections closed immediately
which should be very infrequent since the HTTP/1.0 fix which
eliminated those cases where a missing Connection: keep-alive
was not interpreted as Connection: close, resulting in reuse
of a connection which was immedately closed.
See https://github.com/envoyproxy/envoy/pull/7159 for details.
Signed-off-by: John Plevyak<EMAIL_ADDRESS>For an explanation of how to fill out the fields, please see the relevant section
in PULL_REQUESTS.md
Description:
Risk Level: low
Testing: existing tests
Docs Changes:
Release Notes:
[Optional Fixes #Issue]
[Optional Deprecated:]

I'm going to assign this over to @lizan since he did the previous change, but as we already discussed in the other PR, we cannot remove this code. This does catch a very specific case which is that Envoy is already read off EOF before dispatching data.
As I mentioned in the other PR, this change can be simplified by adding a halfClosedStatus() or similar API so we don't have to do a poll cycle.

So, this code as it stands doesn't actually do what it purports to do, so IMO it should be fixed (the previous PR does do what this code purports to do) or replaced (e.g. half-close semantics) or removed (this PR).  Leaving it as is I don't believe is a reasonable option.  IMO it is would be best to either resurrect the previous PR which fixes this or merge this PR and remove the non-working code and then decide on a replacement.  Leaving non-working code in the codebase adds complexity without providing benefit.

The code does work for the case it was implemented to fix, and we already discussed this in the comment thread in the other PR. I will let @lizan follow up.

To be specific, you said "This does catch a very specific case which is that Envoy is already read off EOF before dispatching data." but as I pointed out, this is in fact not true.   This was proven by testing in production where this code proved ineffective.  The previous PR did in fact address the issue in production.

I can provide a test setup to demonstrate that this code is ineffective and that the previous PR is effective if you like.

I would really prefer to not go back and forth on this infinitely, but for posterity, here are the two situations:

Envoy reads full response + EOF. It then dispatches data, and prevents reuse of the connection so the connection can be closed when the stack unwinds.

Envoy reads a full response but not EOF. EOF comes some time later.

The code you are deleting in this PR fixes (1). We won't be removing it, but it can be simplified as I already mentioned. Your previous PR "fixes" (2) which is a race condition that cannot be fixed in any sane way other than by implementing a delay timer.


Allow to retain X amount of data on indexers at handoff

Description
We use druid to store and query telemetry data. We ingest data into Druid via Kafka. Our ingestion rate is around 1.7M messages per sec.
Our query load is about 1000 qps and most queries request for for data that's in the time range [now-5, now-8].
Since we have a high ingestion rate, we produce a lot of segments - about 2180 segments every hour. We have a segment granularity of 10 mins.
And since our queries are for real-time data, Druid ends up querying all segments within a time chunk - about 360 segments.
We have configured our Druid instance to hand off segments every 10 mins.
With this, we see a query count pattern across indexers and historicals like this,

Right after segment handoff our real-time queries go to both indexers and historicals. This is in line with the current behaviour of segment handoff - all data on the indexers gets handed-off when a handoff happens.
I would like to have a way to retain, say 10mins(or 10M rows) of data on indexers at all the times - so that I can avoid the periodic  increased load on the historicals.
Adding @kfaraz because I discussed this with him in person.
With some direction, I'd be happy to implement this myself.

@abhishekagarwal87 do you have comments/opinions on this?

@abhishekagarwal87 doesn't matter if you use maxRowsPerSegment or maxTotalRows - at handoff time, all segments on the indexer get handed-off. This will again result in increased load on the historicals.
Quoting from here,

When the task reaches one of maxRowsPerSegment, maxTotalRows, or intermediateHandoffPeriod, it hands off all the segments and creates a new new set of segments will be created for further events

An increase in historical load is a problem because, I have to over-provision my historicals to be able to handle the additional load during the segment hand-off. If I can prevent this load on the historicals, I can move my historicals to cheaper instances or reduce their number.

You can still keep historical cheaper by introducing a tier that just
handles very recent data. This tier could be co-hosted with your indexer
processes. So any additional query load is really just moving to a
different process on same machine.
On Fri, 20 Oct 2023 at 12:56 PM, Mohammad Ghazanfar <
@.***> wrote:

@abhishekagarwal87 https://github.com/abhishekagarwal87 doesn't matter
if you use maxRowsPerSegment or maxTotalRows - at handoff time, all
segments on the indexer get handed-off. This will again result in increased
load on the historicals.
Quoting from here
https://druid.apache.org/docs/latest/development/extensions-core/kafka-supervisor-operations#deployment-notes-on-kafka-partitions-and-druid-segments
,
When the task reaches one of maxRowsPerSegment, maxTotalRows, or
intermediateHandoffPeriod, it hands off all the segments and creates a new
new set of segments will be created for further events

An increase in historical load is a problem because, I have to
over-provision my historicals to be able to handle the additional load
during the segment hand-off. If I can prevent this load on the historicals,
I can move my historicals to cheaper instances or reduce their number.
—
Reply to this email directly, view it on GitHub
https://github.com/apache/druid/issues/15167#issuecomment-1772221758,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AALIWUKPMP6I2K6IEAPSIR3YAIRUHAVCNFSM6AAAAAA6BUFOK6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONZSGIZDCNZVHA
.
You are receiving this because you were mentioned.Message ID:
@.***>

You can still keep historical cheaper by introducing a tier that just handles very recent data

We are already doing this and want to get rid of that tier. Our query load is pretty high, at peak we get about 1000 queries per sec on the broker, about 75% of which are for realtime data. Along with this, we also have a high ingestion rate.
Also, $0 is better than cheaper :D

This tier could be co-hosted with your indexer processes. So any additional query load is really just moving to a different process on same machine

The query load doesn't move - it expands to historicals along with indexers.

I would still consider it a "move" than "expansion" since there is less data being queried on historicals once handoff is done.
But if you insist on hacking :), you could configure your cluster to delay the handoff intentionally. You can do this through some clever setting of load rules. The segment would continue to be served by real-time nodes till the handoff is complete. You should verify that delayed handoff doesn't affect the event processing. Again, this is still a hack :)


Reduce onbattery threshold, refresh data faster

Lowers the threshold used in onbattery to determine whether the device is plugged in to 90%
Removes a call to onbattery that causes Nightscout to be updated closer to real-time (and removes two therefore redundant if statements)

Unless there's a consequence of pumphistory_daily_refresh I missed, I was trying to say the ! glucose-fresh conditional is redundant if you take the onbattery call out because then it becomes:
if ! glucose-fresh; then
    pumphistory_daily_refresh
    if ! glucose-fresh; then
        refresh_after_bolus_or_enact
    fi
fi

Anyway, let me do some tests over the next few days to see how this impacts battery life. What would you want the preference named?

You still need one instance of ! glucose-fresh to avoid delaying the next loop if there is not going to be any wait_for_bg.
Are you using / testing with an Edison and/or Pi rig?

Got it. This is a Pi Zero with the HAT.

Cool, then you’re in a good position to test. My goal is to get <5m loop times and >16h battery life out of a <3000mAh single-cell Li-ion.

My lipo is 2500mAh so I'll estimate the time based on that. I think we heard that with the underclock it's around 14.5 hours? And as for the < 5 minute loop time - so far so good, you're already there!

I just went looking for the Twitter thread where the person mentioned they got 14.5 hours and couldn't find it, but I don't recall the battery size they were using.
I tested with the 2500mAh battery yesterday on the misc-issues branch and got 10 hours exactly. Today with this PR as-is (rooted in misc-issues) on the same hardware and the same battery I got 9.5 hours. Not the biggest hit in the world, but I'm going to see if I can get a confirmation test tomorrow.

If you're not underclocking (to 500MHz) that would be worth a try as well.  If we can get the battery life we want with it underclocked and still do the faster data refresh, I think that'd be ideal.

Agreed! I am underclocking to 500MHz but I should probably add that Logger/xdrip-js running the Bluetooth stack constantly will impact the battery in addition to anything 0.7.0 is doing.
Do you have a link to a bigger battery you'd like me to try?

I think xdrip-js is a good realistic test. Some people might also use the g4-loop witch use Bluetooth

Follow up question, slightly off topic: when I change the battery in the pump I noticed I don't have to do an mmtune before the loop starts up again, so is there a reason we mmtune at device startup instead of saving previous mmtune data and using it across device reboots?

After about a week of testing with this PR I've noticed:

Using Bluetooth I can get 12 - 13 hours of use on a 2500mAh battery, so if your goal is 16 hours on a 3000mAh battery that looks realistic.
I use a meter that sends its result to the pump, which automatically shows up in Nightscout as a red dot. I've noticed those aren't showing up anymore.

We still need one instance of ! glucose-fresh - you want to re-add that @jaylagorio?
Once that's fixed, what are folks' thoughts on battery life and whether we want to re-enable post-loop pumphistory pulls while on battery?

@scottleibrand The one on line 71 isn't good enough on its own? What else needs that check around it that I'm missing?

Every time we do something that takes time, we want to do another check to see if we’ve gotten new fresh glucose before starting the next time-consuming thing.

I swear I'm not intentionally being obtuse, and ordinarily this is what I'd look to code comments to try and figure out., but I don't think I understand the point of adding more if statements with calls to glucose-fresh in relation to the whole loop when we're already inside an if statement because of the return value from glucose-fresh.
That said, I returned those lines to essentially what they were before - if I missed the mark please let me know explicitly what you're looking for? Removing the onbattery call was my main goal and I'm totally OK making the glucose-fresh calls look like whatever you want them to look like.

If glucose wasn’t fresh, and you did a thing that takes time, glucose may now be fresh where it wasn’t when the first if check was performed.

Right - but then in relation to the overall loop, what happens if you have a fresh one right when you're about to start an operation that takes some time? I think you have a more big-picture view that I haven't had a chance to get to yet.

All of these operations are optional, and there's not much point in doing them unless it's going to be awhile until the next loop.  For example, if you just got a fresh glucose value while performing the refresh_profile, it makes no sense to do pumphistory_daily_refresh when you can instead end the loop, start the next one, and immediately pull a fresh pumphistory (and use it to loop).

it makes no sense to do pumphistory_daily_refresh or refresh_after_bolus_or_enact when you can instead end the loop, start the next one, and immediately pull a fresh pumphistory (and use it to loop).

And there it is - doing these checks shortcircuits the current loop and instead makes execution fall through to the end so the next loop can start sooner.
That's what I was looking for, thank you!

Exactly.  And that's why I'm skeptical of removing the onbattery check: the pumphistory refresh is going to happen a couple minutes later regardless: we're just doing extra pump comms to speed it up by a minute or two, which may not be worth it while on battery.
So given that, and the measured battery life on the Pi, what are folks' thoughts on whether we want to re-enable post-loop pumphistory pulls while on battery?

Thoughts?

I'm consistently getting 13 hours on a Pi 0 + HAT with a 2500 mAh lipo using Bluetooth for data. Reliable for every day during the work week so far.

Going to go ahead and merge this, and use it as the basis for doing more frequent full pumphistory refreshes to minimize the impact of any race conditions while incrementally refreshing during bolus wizard runs.


Implement client serialize/unserialize

Added ability to pass in .configuration, .registration and .jwks into the constructor

To do:

Create a serialize() method that basically returns the options object that's passed into the parameter
Add round-trip tests

Looks good


(fuzzer) Bincode v1 accepts type that bincode v2 rejects with LimitExceeded

This isn't necessarily "there is a bug in bincode", but there may be a bug in the fuzzing harness.
Bytes:      [2, 0, 0, 0, 17, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 10, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0]
Bincode V1: Ok(VecDeque([BTreeMap({0: BTreeMap({})}), BTreeMap({}), BTreeMap({}), BTreeMap({}), BTreeMap({}), BTreeMap({}), BTreeMap({}), BTreeMap({}), BTreeMap({}), BTreeMap({}), BTreeMap({}), BTreeMap({}), BTreeMap({}), BTreeMap({}), BTreeMap({}), BTreeMap({}), BTreeMap({})]))
Bincode V2: Err(LimitExceeded)

Should this be considered a bug, or should I just throw out cases where either one says limits exceeded?

Yeah, bincode 1 has horribly busted limit estimation, especially when reading from a slice. In fact, with the current fuzzer the limit doesn't even get checked on bincode v1. v1 only does limit calculations when reading from a Read type, not a slice. I'd ignore limit errors for now.


qr code not scanning in dark mode

mobile_scanner 2.0.0
Describe the bug
Qr code not scanning in dark mode
that same Qr code scanning without dark mode
QR code picture

I think this is because there should be a white edge around the qr code, otherwise the scanner can't read the edge blocks correctly. This is not something i can fix in the scanner.


Fix for the associations drawer

Fixes #2713.

Closing in favor or #2726 which contains this commit


Is it possible to use 2 different maxY for 2 different ChartBarData on a lineChart?

I would like to show 2 lines with different data in each one in the same chart, but at the same time, i would like to make it scale to its own maxY. Is this possible?

I have the same question and thought of one possible implementation, please consider rightTitles as second yAxis and you need scale your data by yourself.

Follow #429


feat: add "id" column to Titanic dataset

Summary of Changes
Names alone were not unique, so I've added an "id" column.

🦙 MegaLinter status: ✅ SUCCESS

Descriptor
Linter
Files
Fixed
Errors
Elapsed time

✅ PYTHON
black
2
0
0
0.56s

✅ PYTHON
flake8
2

0
0.33s

✅ PYTHON
isort
2
0
0
0.24s

✅ PYTHON
mypy
2

0
1.46s

✅ PYTHON
pylint
2

0
1.42s

✅ REPOSITORY
git_diff
yes

no
0.04s

See detailed report in MegaLinter reports
Set VALIDATE_ALL_CODEBASE: true in mega-linter.yml to validate all sources, not only the diff
MegaLinter is graciously provided by

:tada: This PR is included in version 0.4.0 :tada:
The release is available on:

v0.4.0
GitHub release

Your semantic-release bot :package::rocket:


More incrementality features?

Gimsatul would be even more useful if it supported the IPASIR API (or something equivalent).

I totally agree, but there are many other more important features that are still lacking.  So I keep this on the 'enhancement' stack.


Retry for failed cert resource deploying

Hi @bitscuit
From the error in github workflow, should we run make cleanup-bundle to remove catalog source as well?
https://github.com/IBM/ibm-common-service-operator/pull/477/checks?check_run_id=2335097281

@Daniel-Fan Could we change retry to 10s? It can decrease the time of the installation and wouldn't cause much API pressure.

@horis233
Sure, BTW is that ok if I changed wait time for CRD from 10s to 30s?

@Daniel-Fan Could we change both of them to 10s?

@horis233
No problem, updated!

Hi @bitscuit
From the error in github workflow, should we run make cleanup-bundle to remove catalog source as well?
https://github.com/IBM/ibm-common-service-operator/pull/477/checks?check_run_id=2335097281

The workflow does have a step where cleanup is done https://github.com/IBM/ibm-common-service-operator/blob/master/.github/workflows/ocp.yaml#L98. But I think because the workflow runs multiple times in each PR due to being triggered whenever labels change, it's not cleaning up properly. I need to add additional checks for existing catalogsource and remove them for now


2.7.0

Codecov Report

Merging #433 into 2.7.0-release will not change coverage.
The diff coverage is 84.45%.

@@               Coverage Diff                @@
##             2.7.0-release     #433   +/-   ##
================================================
  Coverage            85.27%   85.27%
  Complexity             160      160
================================================
  Files                   33       33
  Lines                  455      455
  Branches                50       50
================================================
  Hits                   388      388
  Misses                  45       45
  Partials                22       22

Impacted Files
Coverage Δ
Complexity Δ

...ring/boot/actuate/health/DubboHealthIndicator.java
94.28% <ø> (ø)
18 <0> (ø)
:arrow_down:

...pache/dubbo/spring/boot/util/EnvironmentUtils.java
96.42% <ø> (ø)
12 <0> (ø)
:arrow_down:

.../context/event/WelcomeLogoApplicationListener.java
92% <ø> (ø)
5 <0> (ø)
:arrow_down:

...ubboDefaultPropertiesEnvironmentPostProcessor.java
91.42% <ø> (ø)
14 <0> (ø)
:arrow_down:

...actuate/health/DubboHealthIndicatorProperties.java
85.71% <ø> (ø)
2 <0> (ø)
:arrow_down:

...nfigure/DubboHealthIndicatorAutoConfiguration.java
100% <ø> (ø)
2 <0> (ø)
:arrow_down:

.../org/apache/dubbo/spring/boot/util/DubboUtils.java
81.81% <ø> (ø)
4 <0> (ø)
:arrow_down:

...uate/endpoint/DubboPropertiesMetadataEndpoint.java
100% <100%> (ø)
2 <2> (ø)
:arrow_down:

...g/boot/actuate/endpoint/DubboShutdownEndpoint.java
100% <100%> (ø)
2 <2> (ø)
:arrow_down:

...tuate/endpoint/metadata/AbstractDubboMetadata.java
82.6% <100%> (ø)
14 <1> (ø)
:arrow_down:

... and 38 more

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 fc519f1...f336fa6. Read the comment docs.


Remove broken links from dataframe supported apis Closes #3922

What do these changes do?
Remove the following broken links from dataframe supported apis:
('as_blocks', 'https://pandas.pydata.org/pandas-docs/stable/reference/api/pandas.DataFrame.as_blocks.html#pandas.DataFrame.as_blocks')
('as_matrix', 'https://pandas.pydata.org/pandas-docs/stable/reference/api/pandas.DataFrame.as_matrix.html#pandas.DataFrame.as_matrix')
('blocks', 'https://pandas.pydata.org/pandas-docs/stable/reference/api/pandas.DataFrame.blocks.html#pandas.DataFrame.blocks')
('clip_lower', 'https://pandas.pydata.org/pandas-docs/stable/reference/api/pandas.DataFrame.clip_lower.html#pandas.DataFrame.clip_lower')
('clip_upper', 'https://pandas.pydata.org/pandas-docs/stable/reference/api/pandas.DataFrame.clip_upper.html#pandas.DataFrame.clip_upper')
('from_items', 'https://pandas.pydata.org/pandas-docs/stable/reference/api/pandas.DataFrame.from_items.html#pandas.DataFrame.from_items')
('ftypes', 'https://pandas.pydata.org/pandas-docs/stable/reference/api/pandas.DataFrame.ftypes.html#pandas.DataFrame.ftypes')
('to_dense', 'https://pandas.pydata.org/pandas-docs/stable/reference/api/pandas.DataFrame.to_dense.html#pandas.DataFrame.to_dense')
('to_msgpack', 'https://pandas.pydata.org/pandas-docs/stable/reference/api/pandas.DataFrame.to_msgpack.html#pandas.DataFrame.to_msgpack')
('to_sparse', 'https://pandas.pydata.org/pandas-docs/stable/reference/api/pandas.DataFrame.to_sparse.html#pandas.DataFrame.to_sparse')

[ ] commit message follows format outlined here
[ ] passes flake8 modin/ asv_bench/benchmarks scripts/doc_checker.py
[ ] passes black --check modin/ asv_bench/benchmarks scripts/doc_checker.py
[ ] signed commit with git commit -s
[x] Resolves #3922
[ ] tests added and passing
[ ] module layout described at docs/developer/architecture.rst is up-to-date

@susmitpy thank you for the changes! The changes look fine. Could you please:

git commit --amend your first commit so that it follows the format here
Change the first line of the pull request so it matches the new first line of the commit message

@mvashishtha After amending commits and doing a merge due to changes, one commit became 3 commits.
So I have created another pull request: #3968 Can you close this pull request ?

@susmitpy now that you have #3968, we'll continue the review there. However, for future reference, it's okay if a pull request has multiple comments. We would squash the commits into a single commit before merging.

Sure !
On Fri, 14 Jan, 2022, 21:36 Mahesh Vashishtha, @.***>
wrote:

@susmitpy https://github.com/susmitpy now that you have #3968
https://github.com/modin-project/modin/pull/3968, we'll continue the
review there. However, for future reference, it's okay if a pull request
has multiple comments. We would squash the commits into a single commit
before merging.
—
Reply to this email directly, view it on GitHub
https://github.com/modin-project/modin/pull/3950#issuecomment-1013255014,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AIGHCM4ITHT7C6K3DDHRKGTUWBC2HANCNFSM5L3OL2AQ
.
You are receiving this because you were mentioned.Message ID:
@.***>


Ref: extracting schema helpers

Just moving some stuff

coverage: 100.0%. remained the same
when pulling 8cab11386100883f83ef3ce6d7155cf3085c1f39 on ref-schema-helpers
into c4b021d947e748c2a75ad02df8fca5dfa8d7cfa7 on master.


External SQL File Support

Description

This pull request adds support for .sql files in the sources/ directory. These files will behave as if they were inlined, meaning that file -> file, inline -> file and file -> inline query dependencies function as intended.
Query views for external files are placed at the bottom of the page.
Checklist

[x] I have added a changeset

This is fantastic.

For the frontmatter syntax. Can we set this up so that you set a name for the query when you reference it? I want to decouple the folder structure in sources from the names people have to use inside their pages. See probably incorrect yaml below.
Can we not allow standalone files to reference page queries. I think ideally they should be ignored by the query compiler. This is really cool that it works, but I think it'll take people down a pretty chaotic path if they try to use it.
For docs and examples, I think we should call this "standalone queries" or something along those lines, not external. To me, External reads like these queries are being governed in some wholly different system.

sources:
   - query_one: path/to/query.sql

[ ] @archiewood to review
[ ] @ItsMeBrianD to confirm vercel deploy


vsSideBar Position Right, has incorrect documentation and no support

Details about my setup

Ubuntu
10.16.2
3.10.8
Version 77.0.3865.120
npm

vsSideBar position right doesn't work, while using the code from the documentation

The issue being, rtl support, the options needs to explicitly set, for the direction injectors to work.
Vue.use(Vuesax, {
  rtl: false
})


Node editor rework: User-definable node & edge attributes

[x] Node labels
[ ] Node notes
[ ] Edge labels
[ ] Edge notes (?)
[ ] ?

The rest of this will be implemented as part of workflows.


feat: support custom vercel output configuration

❓ Type of change

[ ] 📖 Documentation (updates to the documentation or readme)
[ ] 🐞 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)
[ ] ⚠ Breaking change (fix or feature that would cause existing functionality to change)

📚 Description
Currently there is no way of changing or extending the vercel config.json. After this PR, vercel's config can be extended (or overridden) from nitro config. This behaviour is required in order to add support for vercel's image optimization in nuxt-image.
example:
import { defineNitroConfig } from 'nitropack'

export default defineNitroConfig({
  vercel: {
    config: {
      images: {
        sizes: [320, 640, 768, 1024, 1280, 1536, 1536],
        minimumCacheTTL: 60,
        formats: ['image/avif', 'image/webp']
      }
    }
  }
})

🔗 Linked issues and discussions
https://github.com/nuxt/image/issues/569
https://github.com/nuxt/image/discussions/548
📝 Checklist

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

Thanks 💯

Thanks @mahdiboomeri !!


Is there any way to extend size of linux Kernel?

I've tried to test a benchmark using fio in simplessd kernel.
But when I tried to random/seq write in simulator, there's an error shows not enough space left on device.
So, I tried several ways to fix this problems, but all things didn't work.
Can you tell me how to expand the size of simplessd kernel?

Hi,
I assume you want to create larger disk image for storing some big files, not the Linux Kernel.
Please check the SimpleSSD homepage for creating new disk image for gem5 simulator.
Thanks.


fix: remove patch in favor of skipTrailingSlashRedirect

This PR removes the patch to Next.js in favor of using the skipTrailingSlashRedirect config.
This disables the automatic normalization of href when using next/link (as well as the automatic server-side redirects) in favor of manually handling the trailing slash (meaning you need to add it manually to each href).

Cool this worked for me! thank you.

@salazarm Great, thanks!
Would you mind updating the blog post to mention this since the patch is not needed?
https://dagster.io/blog/dbt-docs-on-react

Sure, btw I noticed that with SSG every prefetched page redownloads the same layout. Are there plans to optimize that?

Yes, there are plans to optimize that. Thanks!


reducer js taking PATH and PARSE for same reducer functionality.

should be fixed to one command

@Bisonai/orakl-team The new version of Orakl Network Reducer does not accept PATH function, only PARSE is supported. Closing down.
https://github.com/Bisonai/orakl/blob/6b33b7294a5348b17bd030d468952af4c34aa665/node/pkg/utils/reducer/reducer.go#L43-L63


[Tech Debt] Normalized working version

Overview
Able to get the project to compile
Changes

Added PAD (Play Asset Delivery)

Cool! Thanks @kcw-grunt
What is fast_follow_asset_pack_01?

There are 3 levels of play store delivery and fast follow is one. The audio files or any videos when needed would be there.  It makes the app much smaller when downloaded

Wow cool! Thanks for the explanation! @kcw-grunt


DataSet.update causes chunked dask DataArray to evalute its values eagerly

What happened:
Used DataSet.update to update a chunked dask DataArray, but the DataArray is no longer chunked after the update.
What you expected to happen:
The chunked DataArray should still be chunked after the update
Minimal Complete Verifiable Example:
foo = xr.DataArray(np.random.randn(3, 3), dims=("x", "y")).chunk()  # foo is chunked
ds = xr.Dataset({"foo": foo, "bar": ("x", [1, 2, 3])})  # foo is still chunked here
ds  # you can verify that foo is chunked

update_dict = {"foo": (("x", "y"), ds.foo[1:, :]), "bar": ("x", ds.bar[1:])}
update_dict["foo"][1]  # foo is still chunked

ds.update(update_dict)
ds  # now foo is no longer chunked

Environment:
Output of xr.show_versions()
commit: None
python: 3.8.3 (default, Jul  2 2020, 11:26:31)
[Clang 10.0.0 ]
python-bits: 64
OS: Darwin
OS-release: 19.6.0
machine: x86_64
processor: i386
byteorder: little
LC_ALL: None
LANG: en_US.UTF-8
LOCALE: en_US.UTF-8
libhdf5: 1.10.6
libnetcdf: None

xarray: 0.16.0
pandas: 1.0.5
numpy: 1.18.5
scipy: 1.5.0
netCDF4: None
pydap: None
h5netcdf: None
h5py: 2.10.0
Nio: None
zarr: None
cftime: None
nc_time_axis: None
PseudoNetCDF: None
rasterio: None
cfgrib: None
iris: None
bottleneck: None
dask: 2.20.0
distributed: 2.20.0
matplotlib: 3.2.2
cartopy: None
seaborn: None
numbagg: None
pint: None
setuptools: 49.2.0.post20200714
pip: 20.1.1
conda: None
pytest: 5.4.3
IPython: 7.16.1
sphinx: None

that's because xarray.core.variable.as_compatible_data doesn't consider DataArray objects: https://github.com/pydata/xarray/blob/333e8dba55f0165ccadf18f2aaaee9257a4d716b/xarray/core/variable.py#L202-L203 and thus falls back to DataArray.values: https://github.com/pydata/xarray/blob/333e8dba55f0165ccadf18f2aaaee9257a4d716b/xarray/core/variable.py#L219 I think that's a bug and it should be fine to use
    if isinstance(data, (DataArray, Variable)):
        return data.data

but I didn't check if that would break anything. Are you up for sending in a PR?
For now, you can work around that by manually retrieving data:
In [2]: foo = xr.DataArray(np.random.randn(3, 3), dims=("x", "y")).chunk()  # foo is chunked
   ...: ds = xr.Dataset({"foo": foo, "bar": ("x", [1, 2, 3])})  # foo is still chunked here
   ...: ds
Out[2]:
<xarray.Dataset>
Dimensions:  (x: 3, y: 3)
Dimensions without coordinates: x, y
Data variables:
    foo      (x, y) float64 dask.array<chunksize=(3, 3), meta=np.ndarray>
    bar      (x) int64 1 2 3

In [3]: ds2 = ds.assign(
   ...:     {
   ...:         "foo": lambda ds: (("x", "y"), ds.foo[1:, :].data),
   ...:         "bar": lambda ds: ("x", ds.bar[1:]),
   ...:     }
   ...: )
   ...: ds2
Out[3]:
<xarray.Dataset>
Dimensions:  (x: 2, y: 3)
Dimensions without coordinates: x, y
Data variables:
    foo      (x, y) float64 dask.array<chunksize=(2, 3), meta=np.ndarray>
    bar      (x) int64 2 3

xarray.core.variable.as_compatible_data doesn't consider DataArray objects:

I don't think DataArrays are expected at that level though.

{"foo": (("x", "y"), ds.foo[1:, :]), "bar": ("x", ds.bar[1:])}

This syntax is weird. You should be able to do update_dict = {"foo": ds.foo[1:, :], "bar": ds.bar[1:]} .
For the simple example,  ds.update(update_dict) and ds.assign(update_dict) both fail because you can't align dimensions without labels when the dimension size is different between variables (I find this confusing).
@chunhochow What are you trying to do? Overwrite the existing foo and bar variables?

when the dimension size is different between variables (I find this confusing).

I guess the issue is that the dataset has x at a certain size and by reassigning we're trying to set x to a different size. I think the failure is expected in this case, and it could be solved by assigning labels to x.
Thinking about the original problem some more, it might be better to simply point to isel:
ds2 = ds.isel(x=slice(1, None))
ds2

should do the same, but without having to worry about manually reconstructing a valid dataset.

Yes, I'm trying to drop the last "bin" of data (the edge has problems) along all the DataArrays along the dimension x, But I couldn't figure out the syntax for how to do it from reading the documentation. Thank you! I will try isel next week when I get back to it!


Make model editable please

Hi and thanks for the library
It would be great if this model were editable.

I agree !
Should be easy . Need to find time and motivation !

Done!

Where did this get merged/implemented?
When I try to edit a cell I get the error NameError: name '__binding__' is not defined on line 167:
if __binding__ in ("PySide", "PyQt5"):
    self.dataChanged.emit(index, index)
else:
    self.dataChanged.emit(index, index, [Qt.EditRole])

to
try:
    if __binding__ in ("PySide", "PyQt5"):
        self.dataChanged.emit(index, index)
    else:
        self.dataChanged.emit(index, index, [Qt.EditRole])
except NameError:
    self.dataChanged.emit(index, index, [Qt.EditRole])

And I no longer got the error.


Geth fails cause 'invalid value "zgtendermint_9000-1" for flag -networkid: parse error' in engine container

Describe the bug
Just start docker containers with proposal
docker compose --profile proposer up -d
I have a warning during starting containers. May be I need to set something?
WARN[0000] The "GETH_ADDITIONAL_ARGS" variable is not set. Defaulting to a blank string.
Client: Docker Engine - Community
Version:           26.1.0
API version:       1.45
Go version:        go1.21.9
Git commit:        9714adc
Built:             Mon Apr 22 17:07:12 2024
OS/Arch:           linux/amd64
Context:           default
Server: Docker Engine - Community
Engine:
Version:          26.1.0
API version:      1.45 (minimum version 1.24)
Go version:       go1.21.9
Git commit:       c8af8eb
Built:            Mon Apr 22 17:07:12 2024
OS/Arch:          linux/amd64
Experimental:     false
containerd:
Version:          1.6.31
GitCommit:        e377cd56a71523140ca6ae87e30244719194a521
runc:
Version:          1.1.12
GitCommit:        v1.1.12-0-g51d5e94
docker-init:
Version:          0.19.0
GitCommit:        de40ad0
Docker Compose version v2.26.1
.env file
# Chain ID
CHAIN_ID=167009

# Exposed ports
PORT_L2_EXECUTION_ENGINE_HTTP=8547
PORT_L2_EXECUTION_ENGINE_WS=8548
PORT_L2_EXECUTION_ENGINE_METRICS=6065
PORT_L2_EXECUTION_ENGINE_P2P=30306
PORT_PROVER_SERVER=9876
PORT_PROMETHEUS=9091
PORT_GRAFANA=3002

# Comma separated L2 execution engine bootnode URLs for P2P discovery bootstrap
BOOT_NODES=enode://2f7ee605f84362671e7d7c6d47b69a3358b0d87e9ba4648befcae8b19453275ed19059db347c459384c1a3e5486419233c06bf6c4c6f489d81ace6f301a2a446@<IP_ADDRESS>:30303,enode://c067356146268d2855ad356c1ce36ba9f78c1633a72f9b7f686679c2ffe04bab6d24e48ef6eefb0e01aa00dff5024f7f94bc583da90b6027f40be4129bbbc5fd@<IP_ADDRESS>:30303,enode://acc2bdb6416feddff9734bee1e6de91e684e9df5aeb1d36698cc78b920600aed36a2871e4ad0cf4521afcdc2cde8e2cd410a57038767c356d4ce6c69b9107a5a@<IP_ADDRESS>:30303,enode://eb5079aae185d5d8afa01bfd2d349da5b476609aced2b57c90142556cf0ee4a152bcdd724627a7de97adfc2a68af5742a8f58781366e6a857d4bde98de6fe986@<IP_ADDRESS>:30303,enode://2294f526cbb7faa778192289c252307420532191438ce821d3c50232e019a797bda8c8f8541de0847e953bb03096123856935e32294de9814d15d120131499ba@<IP_ADDRESS>:30303

# Taiko protocol contract addresses
TAIKO_L1_ADDRESS=0x79C9109b764609df928d16fC4a91e9081F7e87DB
TAIKO_TOKEN_L1_ADDRESS=0x6490E12d480549D333499236fF2Ba6676C296011
ASSIGNMENT_HOOK_L1_ADDRESS=0x9e640a6aadf4f664CF467B795c31332f44AcBe6c
TAIKO_L2_ADDRESS=0x1670090000000000000000000000000000010001

# P2P
DISABLE_P2P_SYNC=false

############################### REQUIRED #####################################
# L1 Holesky RPC endpoints (you will need an RPC provider such as BlockPi, or run a full Holesky node yourself)
# If you are using a local Holesky L1 node, you can refer to it as "http://host.docker.internal:8545" and "ws://host.docker.internal:8546", which refer to the default ports in the .env for an eth-docker L1 node.
# However, you may need to add this host to docker-compose.yml. If that does not work, you can try the private local ip address (e.g. http://<IP_ADDRESS>:8545). You can find that with `ip addr show` or a similar command.
L1_ENDPOINT_HTTP=https://ethereum-holesky.blockpi.network/v1/rpc/6e....
L1_ENDPOINT_WS=wss://ethereum-holesky.blockpi.network/v1/ws/6e....
# HTTP RPC endpoint of a L1 beacon node. Everything behind the top-level domain is ignored. Make sure you don't need to work with subdirectories. The path will always be /eth/v1...
L1_BEACON_HTTP=http://unstable.holesky.beacon-api.nimbus.team/

# REQUIRED FOR PROVER
# If you are running your Taiko node on a separate server from your sgx prover, please provide the server hosting the taiko node's public IP address here (no slash at the end).
# Otherwise, if you are running both on one machine, set it to http://l2_execution_engine.
TAIKO_NODE_IP=

############################### OPTIONAL #####################################
# If you want to be a prover who generates and submits zero knowledge proofs of proposed L2 blocks, you need to change
# `ENABLE_PROVER` to true and set `L1_PROVER_PRIVATE_KEY`.
ENABLE_PROVER=false
# SGX Raiko service endpoint, required if not running a guardian prover.
SGX_RAIKO_HOST=
# How many provers you want to run concurrently.
PROVER_CAPACITY=1
# A L1 account private key (with a balance of TTKOh deposited on TaikoL1) which will be used to sign the bond for proving the block.
# WARNING: only use a test account, pasting your private key in plain text here is not secure.
L1_PROVER_PRIVATE_KEY=
# Minimum accepted fee for accepting proving a block (in Gwei).
MIN_ACCEPTABLE_PROOF_FEE=1
# Amount to approve AssignmentHook + TaikoL1 contracts for TaikoToken usage. i.e 250 TTKOh = 250
TOKEN_ALLOWANCE=
# Minimum ETH balance (in ETH) a prover wants to keep.
MIN_ETH_BALANCE=
# Minimum Taiko token balance (x10^-18) a prover wants to keep. i.e 250 TTKOh =<PHONE_NUMBER>00000000000
MIN_TKO_BALANCE=
# Whether to prove unassigned blocks or not (blocks that have expired their proof window
# without the original prover submitting a proof.).
PROVE_UNASSIGNED_BLOCKS=false

# If you want to be a proposer who proposes L2 execution engine's transactions in mempool to Taiko L1 protocol
# contract (be a "mining L2 node"), you need to change `ENABLE_PROPOSER` to true, then fill `L1_PROPOSER_PRIVATE_KEY`.
ENABLE_PROPOSER=true
# A L1 account (with balance) private key who will send TaikoL1.proposeBlock transactions.
L1_PROPOSER_PRIVATE_KEY=513.....
# Address of the proposed block's suggested L2 fee recipient.
L2_SUGGESTED_FEE_RECIPIENT=0xff.......
# Fee sent to prover for the off-chain bond (in Gwei).
BLOCK_PROPOSAL_FEE=50
# If nobody accepts block at initial tier fee, how many iterations to increase tier fee before giving up.
MAX_TIER_FEE_BUMPS=
# Comma-delineated list (no spaces) of prover endpoints proposer should query when attempting to propose a block
# If you keep this default value you must also enable a prover by setting ENABLE_PROVER=true.
PROVER_ENDPOINTS=http://taiko-a7-prover.zkpool.io
# Whether to send EIP-4844 blob transactions when proposing blocks.
BLOB_ALLOWED=true
# Amount (in Gwei) that you want to tip the L1 Block Builder.
BLOCK_BUILDER_TIP=

# Comma-delimited local tx pool addresses you want to prioritize, useful to set your proposer to only propose blocks with your prover's transactions.
TXPOOL_LOCALS=

# Transaction Manager Flags (Leave blank if using default values.) These only affect Prover and Proposer.
TX_FEE_LIMIT_MULTIPLIER=
TX_FEE_LIMIT_THRESHOLD=
TX_GAS_LIMIT=
TX_MIN_BASEFEE=
TX_MIN_TIP_CAP=
TX_NOT_IN_MEMPOOL=
TX_NUM_CONFIRMATIONS=
TX_RECEIPT_QUERY=
TX_RESUBMISSION=
TX_SAFE_ABORT_NONCE_TOO_LOW=
TX_SEND_TIMEOUT=```

### Steps to reproduce

Steps to reproduce here.

### Spam policy

- [X] I verify that this issue is NOT SPAM and understand SPAM issues will be closed and reported to GitHub, resulting in ACCOUNT TERMINATION.

@ipohosov are you on the most recent simple-taiko-node version? could you provide the logs from geth please?

Logs
geth.log

Logs
geth.log

I'm not able to replicate this error, could you try pulling the latest version of simple-taiko-node and try again?

closing as stale, please feel free to reopen if issue persists


🔎 Find AWS boot shenanigans

I'm ready to get osbuild/osbuild-composer#754 closed.
Signed-off-by: Major Hayden<EMAIL_ADDRESS>

Proposed a change to raw in #813.


Date and time without time zone

Hello!
I use humantime-serde to work with json and  a bit confused with it behavior with ISO 8601 formatted strings without timezone.
Strings like that: "2022-07-12T12:01:48" are interpreted like UTC time zone.
And I find similar conversion in your  test.
But WIkipedia told about such cases: "If no UTC relation information is given with a time representation, the time is assumed to be in local time."
Almost the same on StackOverflow
And now I totally confused, which time zone should be used for date +  time without implicit timezone.
I would really appreciate any help with this

This lib is just serde support for humantime, so I can't really change anything about the actual implementaion. Your issue should be filed here https://github.com/tailhook/humantime.
The behavior you describe seems to be an acknowledged limitation here: https://github.com/tailhook/humantime/blob/master/src/date.rs#L109.

@jean-airoldie Thanks a lot!
Everything is clear for me


"error: Not a constant expression: unexpected kernel tag ConstructorInvocation (31)"

If you run this:
class Test {
  Test({ this.test = Duration(minutes: 1) }); // the default value is not explicitly "const"
  final Duration test;
}

void main() {
  Test();
}

...you get:
Unhandled exception:
'file:///home/ianh/dev/scratch/test.dart': error: Not a constant expression: unexpected kernel tag ConstructorInvocation (31)
#0      main (file:///home/ianh/dev/scratch/test.dart:8:3)
#1      _startIsolate.<anonymous closure> (dart:isolate/runtime/libisolate_patch.dart:289:19)
#2      _RawReceivePortImpl._handleMessage (dart:isolate/runtime/libisolate_patch.dart:171:12)

...which is a horrible error message.

You can run:
class Test {
  Test({Duration test}) : test = test ?? Duration(minutes: 1);
  final Duration test;
}

void main() {
  Test();
}

Frankly speaking, I'm not sure about the difference between these two constructor invocations...
It seems like, we should use Test({...}): ...; when our classes contain other classes.

This appears to have been fixed:
$ dart tmp.dart
tmp.dart:2:22: Error: Constant expression expected.
Try inserting 'const'.
  Test({ this.test = Duration(minutes: 1) }); // the default value is not explicitly "const"
                     ^^^^^^^^

$ dart --version
Dart SDK version: 2.19.1 (stable) (Unknown timestamp) on "linux_x64"


Add 5s timeout to http.Client

The GET requests would stuck for a long time if the connections are being interrupted/blocked.

Thanks for the contribution! I need you to accept the CLA in order to merge this change.

Done.


[Backport] XContent Refactor to 2.x

XContent namespace refactor from common -> core is going to be merged to opensearch/2.x which will break the 2.x build.  This issue is for backporting #637 to 2.x after the core namespace change is merged.
Depends on https://github.com/opensearch-project/OpenSearch/pull/6470

https://github.com/opensearch-project/OpenSearch/pull/6470 merged


Cross cloud playbook

This adds a couple more helper scripts, and updates ansible commands to accommodate:

build_network_file.py. Builds the network.toml file from the keys stored in in-market-test/v2/deployed_keys. Works automatically if testing with 3 servers, or will work if copying those files in with 3 different parties.
parse_logs.py. Generates a report from the logs copies from the server with breakdown of run time and errors observed.

Why don't we have a separate repository with a python project? Like ipa-tools or something.

I wouldn't call this a "project", it's just some scripts used for deploying/testing for the in market test.


Return Result in Engine::start

Corresponding code to sawtooth-core#1903
Signed-off-by: Kenneth Koski<EMAIL_ADDRESS>

@knkski hold off on merging until hyperledger/sawtooth-core#1903 is merged, and then merge ASAP

@aludvik: Someone other than me will have to merge this, since I don't have write access

@knkski I can merge as soon as the core PR is merged


Application does not resume after calling CrossMedia.Current.TakePhotoAsync (Android)

This is a

[x] Bug

Which plugin does this impact:

[x] Media

Bug
Version Number of Plugin: 2.3.0 - 2.4.0-beta3
Device Tested On:  Sony M5(E5603) - 5.1.1
Simulator Tested On: 5.1.1 and 6.0
Expected Behavior
Application should resume after calling CrossMedia.Current.TakePhotoAsync
Actual Behavior
After calling CrossMedia.Current.TakePhotoAsync, and accepting the taken image, appears black screen with no response nor OnResume event.
Steps to reproduce the Behavior

Call CrossMedia.Current.TakePhotoAsync
Accept taken photo
Notice that the application doesn't resume

Solved with Xamarin Forms <IP_ADDRESS>-pre3


Added setup.py

This is a draft, not yet ready unless nothing needs to be changed.
Here is a few notes:

The package name is PyClock (from __program__ in pyclock.py) and the installed script is pyclock.py
Any changes? Make them same, or?

No long_description which is displayed on PyPI, usually I will just grab READYT.rst, but we don't have that. It would be fine, just a blank description there.

The code was copied and pasted from my other project, so there might be issues I didn't see.

No long_description which is displayed on PyPI, usually I will just grab READYT.rst

I'm assuming the README.md won't format correctly, right? It might be worthwhile to make a simple rst version of the readme eventually.
And the naming is good.

No, they won't. Quite different, so README.md won't work.


Share products in the online store

I have an online store that has a problem and I want to solve it
The problem is that every vendor adds a product and all the information
But there are a lot of refined products
I want to make a special profile for each product in the Data Base
And the shopkeeper fetch it via the barcode
The image and all information come with the default price, and the store owner can adjust the price anything he wants
What is the code to be added?
Is there a place where I can find all international products (pictures, product data, price, international code, barcode, classification)

This is outside the scope of this package.


fix(mistral): docs are a copy of llama2

Description
The mistral provider docs are accidentally a copy of the llama2 docs!
They need to specifically reference cloud-hosted mistral.ai, as the most common usage.
Checklist

[x] Review label added
[x] Conditional version tags added, if applicable.

For example, if this change is for an upcoming 3.6 release, enclose your content in {% if_version gte:3.6.x %} <content> {% endif_version %} tags (or if_plugin_version tags for plugins).
Use any of the following keys:

gte:<version> - greater than or equal to a specific version
lte:<version> - less than or equal to a specific version
eq:<version> - exactly equal to a specific version

You can do the same for older versions.

Please hold merge, one more issue...


feat: adding -o yaml/json option to cmd whoami

Adding possibility for -o json/yaml accommodating more usability in automations as stated by #726.

@pvasant @vkareh PTAL

@vkareh PTAL

/lgtm


broken style in todo mvc demo

Currently the todo demo looks like this:

https://skoppe.github.io/spasm/examples/todo-mvc/
(in Firefox)

Yeah, it lazy-loads the css, but sometimes that doesn't quite work or you see a flash of unstyled content, will change.

in Firefox it's constantly like this


Xtreme download manager (xdm)

Project description

A java app for people with a low bandwidth and an instable/unreliable internet connection (like me). I'm not sure how it works but it makes it possible to download extra large (or not) files with almost 100% success (instead of the famous HTTP error 200 (curl error: Transferred a partial file); retrying in 294 m). It also has a browser extension (directly synchronized with the desktop app).
Metadata

homepage URL: https://subhra74.github.io/
source URL: https://github.com/subhra74/xdm
license: gpl2 (not sure if it's plus or only, I'd put gpl2Plus by default).
platforms: all, it's java.

I mostly package stuff myself but here I really don't know anything about java. The project seems to be packaged with maven (pom.xml are maven only?) so I guess you could use https://github.com/NixOS/mvn2nix-maven-plugin.

I get this error ```
Save New Duplicate & Edit Just Text Twitter
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
building '/nix/store/rfizhz2g7al2vjbilyv7nd2mlr49b99p-xdman-0.0.1-SNAPSHOT.jar.drv'...
unpacking sources
unpacking source archive /nix/store/y3xiwixdhd4akq03z182k77k15568zp4-Xtreme-Download-Manager
source root is Xtreme-Download-Manager
patching sources
configuring
no configure script, doing nothing
building
[INFO] Scanning for projects...
[INFO]
[INFO] ----------------------------< xdman:xdman >-----------------------------
[INFO] Building xdman 0.0.1-SNAPSHOT
[INFO] --------------------------------[ jar ]---------------------------------
[INFO]
[INFO] --- maven-resources-plugin:2.6:resources (default-resources) @ xdman ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 139 resources
[INFO]
[INFO] --- maven-compiler-plugin:3.1:compile (default-compile) @ xdman ---
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 194 source files to /build/Xtreme-Download-Manager/target/classes
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time:  0.870 s
[INFO] Finished at: 2020-08-31T14:08:28Z
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.1:compile (default-compile) on project xdman: Fatal error compiling: invalid target release: 11 -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
builder for '/nix/store/rfizhz2g7al2vjbilyv7nd2mlr49b99p-xdman-0.0.1-SNAPSHOT.jar.drv' failed with exit code 1
error: while evaluating 'callPackageWith' at /nix/store/dy5wflhjd010iic3h3349dhs8j2g381j-nixpkgs-20.08.20/lib/customisation.nix:117:35, called from /home/scott/Documents/NixPackaging/Xtreme-Download-Manager/build.nix:14:1:
while evaluating 'makeOverridable' at /nix/store/dy5wflhjd010iic3h3349dhs8j2g381j-nixpkgs-20.08.20/lib/customisation.nix:67:24, called from /nix/store/dy5wflhjd010iic3h3349dhs8j2g381j-nixpkgs-20.08.20/lib/customisation.nix:121:8:
build of '/nix/store/rfizhz2g7al2vjbilyv7nd2mlr49b99p-xdman-0.0.1-SNAPSHOT.jar.drv' failed```

Has there been any updates on this?


Stance changes

It just doesn't work with stance changes? My action bars don't change during stealth, and they also stop working.

Hello,
Thanks for your report. I have indeed never played with a character that uses BonusActionButtons like Stealth or Stance bars with this addon. I just tried it and the stances are changed, but won't visually hide the below actionbar which gets easilly confusing. To solve this, I have just pushed an update that now hides the "original" actionbuttons while the "bonus" actionbuttons (stealth, stances) are in use.
It seems to be fixed now on my Lv2 Rogue :)
https://github.com/shagu/ShaguController/commit/5d3241a729441399ec0428a2429fc1fde2691565


Architecture diagram

Put together an architecture diagram of the whole system

Architecture Diagram #62. I believe I can contribute effectively to this task and help move the project forward. Please let me know how I can best assist with this issue.


form validation doesn't coerce to string

According to this the form validation does coercion before validating.
This seems to be not working if I want to ensure something is a string.
require 'bundler/inline'
gemfile true do
  gem 'dry-validation'
end

schema = Dry::Validation.Form do
  key(:user_id).required(:str?)
  key(:age).required(:int?)
end

p schema.call('user_id' => 123, 'age' => '55')
#<Dry::Validation::Result output={:user_id=>123, :age=>55} messages={:user_id=>["must be a string"]}>

So the age got coerced to an integer but user_id wasn't coerced to a string. This seems inconsistent and confusion. Right now it seems like I can't be sure when coercion is done and when not.

Hi there! You're right to expect form schemes to coerce the input data. However, it's set up only to do this when the input data are all strings, since this is the shape that form posts take in real usage. In a normal rack-processed form post, you'd never get a Ruby integer back, you'd always have it in string form.
This is why the form schema works as it does, and since it suits to use case (form posts), I don't expect it'd change to handle coercion a from arbitrary non-strong input data.

ok so required(:str?) is handled in a special way where as all other type checks try to perform coercion. We know that in real scenarios you have strings anyway so coercion to it is pointless. We just noticed this behavior during tests and where a bit surprised.

@andreaseger :str? in Form schemas is not handled at all, it's just being ignored since the assumption is that values are strings already.


version 1.0.0 at windwos 11 22622.601 can not run

can not start app, not show APP

Duplicate of #228


Issues in Installing scispacy , Building wheel for nmslib didnt not work

I have checked the required dependency:

However, it still give me an error: Building wheel for nmslib didnt not work.
Error:
error: subprocess-exited-with-error
Building wheel for nmslib (pyproject.toml) did not run successfully.
exit code: 1
[22 lines of output]
C:\Users\ZhenQuanTee\AppData\Local\Temp\pip-build-env-sur0gcij\overlay\Lib\site-packages\setuptools\dist.py:745: SetuptoolsDeprecationWarning: Invalid dash-separated options
!!
      ********************************************************************************
      Usage of dash-separated 'description-file' will not be supported in future
      versions. Please use the underscore name 'description_file' instead.

      By 2023-Sep-26, you need to update your project and remove deprecated calls
      or your builds will no longer be supported.

      See https://setuptools.pypa.io/en/latest/userguide/declarative_config.html for details.
      ********************************************************************************

!!
opt = self.warn_dash_deprecation(opt, section)
Dependence list: ['pybind11<2.6.2', 'psutil', "numpy>=1.10.0,<1.17 ; python_version=='2.7'", "numpy>=1.10.0 ; python_version>='3.5'"]
running bdist_wheel
running build
running build_ext
Extra compilation arguments: ['/EHsc', '/openmp', '/O2', '/DVERSION_INFO=\"2.1.1\"']
building 'nmslib' extension
error: Microsoft Visual C++ 14.0 or greater is required. Get it with "Microsoft C++ Build Tools": https://visualstudio.microsoft.com/visual-cpp-build-tools/
[end of output]
note: This error originates from a subprocess, and is likely not a problem with pip.
ERROR: Failed building wheel for nmslib
ERROR: Could not build wheels for nmslib, which is required to install pyproject.toml-based projects
Would appreciate if you guys could pls help. This is my final year project.

I'm on macOs and managed to installed nsmlib like this:
CFLAGS="-mavx -DWARN(a)=(a)" pip install nmslib

@davidsbatista
I am running on Windows, and have encounter with this error code:
'CFLAGS' is not recognized as an internal or external command,
operable program or batch file.

with poetry ( on MacOS with an Apple M1 Pro)
CFLAGS="-mavx -DWARN(a)=(a)" poetry add nmslib
works well

I highly recommend using windows subsystem for linux on windows. There are a variety issues here related to installing nmslib, and I encourage you to look for solutions there and on the nmslib repo itself. That being said, I have successfully installed nmslib using windows subsystem for linux and python 3.10 recently.

@dakinggg Hi, thanks for the guidance but I am still struggling to find the particular repo you mentioned using windows subsystem. Could you please provide me a link ?

hey @Teezq could you try installing with mamba as per https://github.com/allenai/scispacy/issues/520#issue-2438749767? I'm looking to see if it works for others.


add support for mobilenet, some cleanup, fix readme

abort this one, got an unwanted file in the pr,


Fixes 252: Fix TestRpmList unit test

Update limit to -1 into TestRpmList
Signed-off-by: Alejandro Visiedo<EMAIL_ADDRESS>

https://issues.redhat.com/browse/HMSCONTENT-252

closing as I was not able to replay again from the main branch.

i suspect that maybe the problem actually has to do with go 1.18 in the pr https://github.com/content-services/content-sources-backend/pull/125
have we seen it elsewhere?

I was actually able to reproduce this locally randomly :)
I fixed this here:  https://github.com/content-services/content-sources-backend/pull/125/files#diff-73ba5cff26e1cda8426ce77b3206b3b368b202a1ce40582dc8a37f96f23f217b
i think its related to the upgraded of go and deps, its treating limit 0 as actual limit 0, i'm not 100% why it wasn't doing that before


api: VPD 0xB0 add OPTIMAL UNMAP GRANULARITY support

Thanks.
Why no granularity alignment though?

Till now not very sure the use case about the alignment.
I have ever saw one VMWare bug about the UNMAP granularity alignment by Windows Guest OS:
when a Windows NTFS filesystem is formatted with 4KB blocks, Automated UNMAP is not working, but it is not caused by scsi proto, just the VMWare's bug.
(http://cormachogan.com/2017/03/15/vsphere-6-5-p01-important-patch-users-automated-unmap)

There is an example in the linux kernel in __blkdev_issue_discard.
On the device side, if the discard/unmap is not aligned then it could cause blocks to not be freed or cause it to hit a slow path depending on the implementation.


rosbridge_suite: 0.10.0-0 in 'lunar/distribution.yaml' [bloom]

Increasing version of package(s) in repository rosbridge_suite to 0.10.0-0:

upstream repository: https://github.com/RobotWebTools/rosbridge_suite
release repository: https://github.com/RobotWebTools-release/rosbridge_suite-release.git
distro file: lunar/distribution.yaml
bloom version: 0.6.9
previous version for package: 0.8.4-0

rosapi
* Drop use of ros Python module (#374 <https://github.com/RobotWebTools/rosbridge_suite/issues/374>)
* Fixes passing of globs to proxy (#355 <https://github.com/RobotWebTools/rosbridge_suite/issues/355>)
  * Fixes handling and passing of globs to proxy
  * Removes some confusing imports
* Fix a few problems (#350 <https://github.com/RobotWebTools/rosbridge_suite/issues/350>)
  * xrange is not available in Python3, range works for both Python versions
  * the variable v is undefined in search_param, comparing the implementation with the sibling functions I expect name to be the intended variable
  * The module udp_handler is using the Authentication service but wasn't importing the module
* use package format 2, remove unnecessary dependencies (#348 <https://github.com/RobotWebTools/rosbridge_suite/issues/348>)
* Contributors: Anwar, Dirk Thomas, Jochen Sprickerhof

rosbridge_library
* CBOR encoding (#364 <https://github.com/RobotWebTools/rosbridge_suite/issues/364>)
  * Add CBOR encoding
  * Fix value extraction performance regression
  Extract message values once per message.
  * Fix typed array tags
  Was using big-endian tags and encoding little-endian.
  Always use little-endian for now since Intel is prevalent for desktop.
  Add some comments to this effect.
  * Update CBOR protocol documentation
  More information about draft typed arrays and when to use CBOR.
  * Fix 64-bit integer CBOR packing
  Use an actual 64-bit format.
* use package format 2, remove unnecessary dependencies (#348 <https://github.com/RobotWebTools/rosbridge_suite/issues/348>)
* removing has_key for python3, keeping backwards compatibility (#337 <https://github.com/RobotWebTools/rosbridge_suite/issues/337>)
  * removing has_key for python3, keeping backwards compatibility
  * py3 change for itervalues, keeping py2 compatibility
* Contributors: Andreas Klintberg, Dirk Thomas, Matt Vollrath

rosbridge_server
* CBOR encoding (#364 <https://github.com/RobotWebTools/rosbridge_suite/issues/364>)
  * Add CBOR encoding
  * Fix value extraction performance regression
  Extract message values once per message.
  * Fix typed array tags
  Was using big-endian tags and encoding little-endian.
  Always use little-endian for now since Intel is prevalent for desktop.
  Add some comments to this effect.
  * Update CBOR protocol documentation
  More information about draft typed arrays and when to use CBOR.
  * Fix 64-bit integer CBOR packing
  Use an actual 64-bit format.
* Add param to enable ws per-message deflate (#365 <https://github.com/RobotWebTools/rosbridge_suite/issues/365>)
  * Add param to enable ws per-message deflate
  Tornado has its own per-message deflate compression option, which
  compresses each WebSocket message.  The compression level should be
  roughly equivalent to PNG compression, depending on whether the message is
  JSON or binary (CBOR).  The encoding/decoding time will be much faster
  than protocol PNG compression.
  This param should be enabled when wire size is important, e.g. not
  connecting to localhost.
* rosbridge_server: Publish number of connected clients on latched topic. (#359 <https://github.com/RobotWebTools/rosbridge_suite/issues/359>)
* Fix a few problems (#350 <https://github.com/RobotWebTools/rosbridge_suite/issues/350>)
  * xrange is not available in Python3, range works for both Python versions
  * the variable v is undefined in search_param, comparing the implementation with the sibling functions I expect name to be the intended variable
  * The module udp_handler is using the Authentication service but wasn't importing the module
* use package format 2, remove unnecessary dependencies (#348 <https://github.com/RobotWebTools/rosbridge_suite/issues/348>)
* Adding bson support for websockets (#327 <https://github.com/RobotWebTools/rosbridge_suite/issues/327>)
  * removed message that bson isn't supported. setting the bson only mode class attribute
  * added auth package inspection for bson only mode
* Contributors: Dirk Thomas, Hans-Joachim Krauch, Matt Vollrath, Sanic

rosbridge_suite
* use package format 2, remove unnecessary dependencies (#348 <https://github.com/RobotWebTools/rosbridge_suite/issues/348>)
* Contributors: Dirk Thomas

Holding for sync: https://discourse.ros.org/t/preparing-for-lunar-sync-2018-12-12/7106

Version 0.10.1 will follow soon


ApiGatewayV1 and ApiGatewayV2 should be restructured to allow route specific settings (throttling etc.)

ApiGatewayV2 constructor creates the stage automatically and therefore adding route specific settings does not work as the intended route keys haven't been created yet. And route keys can't be created without ApiGatewayV2 itself. This creates an unnecessary cyclic dependency. This can be avoided by necessitating an explicit stage() / deploy() method after routes have been added. Additionally, routes would need to be exposed as nodes so that an explicit dependency can be added on them before staging/deploying.
ApiGatewayV1 does have an explicit deploy() method but does not expose the already created stage and routes in nodes. If it did, one could use aws.apigateway.MethodSettings to add route specific settings with an explicit dependency on stage and routes.

Yes, I stumbled on to it because of #587 but felt that this issue can also come up without the situation presented #587.
The workaround for #587 involved abandoning a custom domain name and using a a CloudFront distribution instead and managing my own aws.apigatewayv2.DomainName, aws.apigatewayv2.ApiMapping and aws.apigatewayv2.Stage.

hey @vvashisht I haven't tried this, but can you transform the stage to define route settings (ie. throttling), and also disable autoDeploy. Then manually create a deployment?

That's sort of what I ended up doing. I haven't taken into account the #592 fix yet, but this is what I did:
When creating ApiGatewayV2, I specify transform.stage options to change stage name to 'dummy' and autoDeploy to false.
This ensures that the auto-created stage is disabled / dummy and not deployed.
I then add routes to this ApiGatewayV2 instance and keep track of their instances.
Finally, I 'deploy' this ApiGatewayV2 where I create:

A new Stage using the pulumi resource with name '$default' and specify route specific settings (throttling etc.)
Mark autoDeploy true for this stage
I hand copied the access log format from ApiGatewayV2 code
Add all route instances from before to this stage's dependsOn custom resource option (and parent as the api gateway instance)
A new DomainName using pulumi (the domain is already created at this point)
A new ApiMapping to map this new Stage and the DomainName just created

I might be able to simplify the last two steps because of the fix for #592.
I had to resort to a dummy stage because I can neither prevent its creation when instantiating ApiGatewayV2 nor specify route specific settings in the transform because then, the deployment throws an error where it can't find the route keys to routes as they haven't been created yet.
What I haven't tried (or forgot if I did; I was trying a lot of things) is to disable autoDeploy and specify route specific settings when creating ApiGatewayV2, add routes to it, then ... how do I deploy this stage? I haven't explored aws.apigatewayv2.Deployment yet. And I can't modify the stage during the deployment. I need to experiment to figure out if there is a way forward in this approach or not. And unfortunately, at least for now, I don't have the bandwidth. But I'll come back to it soon.
I'll say this though, I understand the convenience of auto-created $default stage, but I'm still of the opinion that ApiGatewayV2 would be more future-proof and open-ended if:

The stage name $default isn't hard-coded (in methods, createStage and createDomainMapping). $default should be the default value, but it should be customizable
The sequence of creating the api gateway > stage > domain > api mapping isn't completed in the ApiGatewayV2 constructor, and instead follows the ApiGatewayV1 model of explicitly invoking a deploy method

I tried what you suggested.
Set autoDeploy to false and specified routeSettings in transform.stage when instantiating ApiGatewayV2
It doesn't work, I get the same error:
Unable to find Route by key GET /xxx/xxx within the provided RouteSettings
Apparently AWS doesn't care if a stage is deployed or not; if you're going to specify route specific settings in the stage, those routes need to be created first. It's hard to say that this is unreasonable.
I didn't proceed further with this experiment for now.


{storage-preview} Add support for queue and message command groups

Add az storage queue create/delete/exists/stats/generate-sas commands using Python sdk track2
Add az storage message put/peek/get/update/delete/clear` commands using Python sdk track2
This checklist is used to make sure that common guidelines for a pull request are followed.

For new extensions:

[ ] My extension description/summary conforms to the Extension Summary Guidelines.

About Extension Publish
There is a pipeline to automatically build, upload and publish extension wheels.
Once your PR is merged into master branch, a new PR will be created to update src/index.json automatically.
The precondition is to put your code inside this repo and upgrade the version in the PR but do not modify src/index.json.

If this PR is for a new extension or change to an existing extension, use the following to try out the changes in this PR:
docker run -it mcr.microsoft.com/azure-cli:latest
export EXT=<NAME>
pip install --upgrade --target ~/.azure/cliextensions/$EXT "git+https://github.com/evelyn-ys/azure-cli-extensions.git@message_track2#subdirectory=src/$EXT&egg=$EXT"

storage-preview

Covered in #2631


Unable to Update Deployment with azureFunctionsDeploy Due to "BlobAlreadyExists" Error

Description:
After successfully deploying the initial version of my Java-based Azure Function app, I encountered difficulties updating its deployment with azureFunctionsDeploy. Each attempt resulted in a "BlobAlreadyExists" error. I am using the latest available version of this plugin (v1.15.0).
Details:
Despite ensuring that I increase the version of the JAR file generated with every gradle build, it appears that the azureFunctionsPackage task consistently creates the file with the same name. Consequently, when I execute azureFunctionsDeploy for subsequent deployments, I repeatedly encounter the following error:
com.microsoft.azure.toolkit.lib.common.exception.AzureToolkitRuntimeException:` Status code 409... BlobAlreadyExists ...

Workaround:
To mitigate this issue, I have resorted to manually deleting the blob from the java-functions-run-from-packages container before executing azureFunctionsDeploy. However, I have been unable to locate any setting within the plugin configuration that allows overwriting existing blobs.
Request for Guidance:
Could you please provide guidance on whether I am overlooking any configuration setting or best practice that would enable the plugin to overwrite existing blobs during deployment?

@Flanker32  @andxu - Can you please take a look into it once?

Reverting to v1.11.0 resolves the issue though. But please let me know if it's a bug in the upgraded version or if there's some other way to allow blob overwrite.

@varenyavv Thanks a lot for your report and sorry for the late response. We will investigate this issue soon, and update here once we get any updates


No such file or directory on start

Running this on Arch with Rust 1.72.0 -
$ cargo run --release
    Finished release [optimized] target(s) in 0.04s
     Running `target/release/btknmle`
Error: No such file or directory (os error 2)

Bluetoothd isn't running, libinput package is installed. What am I missing?

Some were not documented.

Requires root privileges

cargo build && sudo ./target/debug/btknmle
Or add the following to .cargo/config to make cargo run work with sudo.

[target.x86_64-unknown-linux-gnu]
runner = 'sudo -E'

State file

State file is required. The default is /var/lib/btknmle/db.toml, but it does not create a directory.Therefore, either of the following is required

mkdir /var/lib/btknmle or
cargo run -- -f /tmp/btknmle.toml

Sorry for your interest, but perhaps it may not work in your environment.
It did not work as expected when I got it to work in my environment, which is different from before...


WordPress #page div moves horizontally over background

This causes a WordPress #page div to slide back and forth horizontally over the background image on iPhone / iOS

There could be a conflict with the naming conventions of the plugin and the naming conventions of your theme.


FauxGen should be an MSBuild integrated solution

Is your feature request related to a problem? Please describe.
It would be better to allow the faux generated implementations are included in the build of the project.
Describe the solution you'd like
FauxGen creates the generated classes and those get included in the compilation of the target assembly.  Faux already handles finding the implementations and using them at runtime.
Describe alternatives you've considered
It's currently a command line tool only.  Not as useful as an MSBuild task with targets like other projects.  Should integrate similar to other MSBuild plugins.

After running into a number of issues, I have decided I was barking down the wrong path:
https://natemcmaster.com/blog/2017/11/11/msbuild-task-with-dependencies/
and should instead have a command line tool (as I do now) to have others use:
https://natemcmaster.com/blog/2017/11/11/build-tools-in-nuget/


rust-toolchain.toml forces windows-gnu which causes skia-bindings build script to fail

This is only an issue when cloning and using the freya workspace directly. I have been using freya as a dependency for a bit, and that initial experience was painless and seamless. However, if anyone running examples or setting up to contribute on Windows will likely run into this problem.
This is a known limitation with rust-toolchain.toml, apparently. https://github.com/rust-lang/rustup/issues/3546
I tried to explicitly install 1.79.0-x86_64-pc-windows-msvc toolchain, but it still overrides to windows-gnu.
It seems that the root issue is that rust-skia only supports pre-built binaries for x86_64-pc-windows-msvc target. First, it failed with a cryptic error about symlink failure (easily solved by turning on "Developer Mode" in Windows settings), but then ninja started failing with some deep-in-the-weeds build errors.
I could probably debug the build problems, but it was more immediately easy to just temporarily disable rust-toolchain.toml. Doing this, the examples built and ran without issue. I will likely put more effort into figuring this out when I get a chance, since I'd like to contribute to the project at some point.
I don't know what the best ultimate "fix" is here, but it's probably worth adding a small section to the README with a heads-up about this wrinkle and how to work around it.

Hey! Interesting issue! I always used msvc so I never noticed this. Thanks for opening an issue, much appreciated.
What do you think about changing this part of the README:
### Want to try it? 🤔

⚠ First, see [Setup guide](https://book.freyaui.dev/setup.html).

Clone this repo and run:

```shell
cargo run --example counter

to
### Want to try it? 🤔

👋 Make sure to check the [Setup guide](https://book.freyaui.dev/setup.html) first.

> ⚠ If you happen to be on Windows using `windows-gnu` and get compile errors, maybe go check this [issue](https://github.com/marc2332/freya/issues/794).

Clone this repo and run:

```shell
cargo run --example counter

That sounds like it would do the trick!
Yeah, I'm not sure why exactly my setup wants to default to windows-gnu, since I also near-exclusively use msvc. There was some crate I was using a while ago that required gnu, I think, and so now it's in my config somewhere. I guess? 🤷


note: Remove enter_critical_section from the sched_note module

Summary
noterpmsg: Remove enter_critical_section from the sched_note module to avoid recursive calls.
Impact
note
Testing
ci ostest

[Experimental Bot, please feedback here]
No, this PR does not fully meet the NuttX requirements.  While it provides a summary of the change itself, it lacks crucial information.  Here's a breakdown:

Insufficient Summary: While the summary describes what was changed, it doesn't explain why.  What problem did the recursive calls cause?  What functionality was affected?  Were there any bug reports (NuttX issue references) related to this?

Missing Impact Details:  Simply writing "note" under Impact is inadequate.  Each impact category (user, build, hardware, documentation, security, compatibility) needs a YES/NO answer followed by a description if the answer is YES. Even if the answer is NO for all, it should be explicitly stated (e.g., "Impact on user: NO").  Consider the implications of removing the critical section.  Could this lead to race conditions? Does it affect interrupt handling?

Inadequate Testing: "ci ostest" isn't sufficient.  What specific tests were run? Provide actual log output before and after the change.  What build host was used? What target architecture and board configuration?  The logs should demonstrate that the problem existed before the change and is resolved after the change.  Just saying "ci ostest" doesn't prove anything without the supporting details and logs.

In short, the PR needs to be significantly more detailed to meet the requirements. It needs to provide the missing context and evidence to justify the change and demonstrate its effectiveness.


Powerlevel 9K does not work in the PyCharm terminal

When I try to use the terminal in PyCharm, I get the following errors:
/Users/dheerajchand/.oh-my-zsh/custom/themes/powerlevel9k/functions/utilities.zsh:86: command not found: print_icon
powerlevel9k_vcs_init:32: command not found: print_icon
powerlevel9k_vcs_init:33: command not found: print_icon
powerlevel9k_vcs_init:43: command not found: print_icon
powerlevel9k_prepare_prompts:4: command not found: print_icon
left_prompt_segment:24: command not found: print_icon
left_prompt_segment:44: command not found: print_icon
prompt_dir:4: character not in range
powerlevel9k_prepare_prompts:4: command not found: print_icon
right_prompt_segment:32: command not found: print_icon
   3.16                                                                                 23:34  01.05.17

In my normal terminal, oh-my-zsh works fine. Here are the relevant settings.

#POWERLEVEL9K_MODE='awesome-patched'
DEFAULT_USER="$(whoami)"
POWERLEVEL9K_SHORTEN_DIR_LENGTH=3
POWERLEVEL9K_SHORTEN_STRATEGY="truncate_middle"
POWERLEVEL9K_STATUS_VERBOSE=false
POWERLEVEL9K_LEFT_PROMPT_ELEMENTS=(status os_icon load context dir vcs)
POWERLEVEL9K_RIGHT_PROMPT_ELEMENTS=(virtualenv time)
POWERLEVEL9K_SHOW_CHANGESET=true
POWERLEVEL9K_CHANGESET_HASH_LENGTH=6

#POWERLEVEL9K_CUSTOM_TIME_FORMAT="%D{\uf017 %H:%M:%S}"
POWERLEVEL9K_TIME_FORMAT="%D{\uf017 %H:%M \uf073 %d.%m.%y}"

POWERLEVEL9K_STATUS_VERBOSE=false

POWERLEVEL9K_PROMPT_ON_NEWLINE=true```

Any advice?

print_icon lives in functions/icons.zsh. It might be that there is an issue sourcing that file?

On my 2 laptops and 1 pc powerlevel9k works just fine in PyCharm (well except for cutting awesomefonts in half, but that's not powerlevel's issue).
Do you have correct Shell path in Settings (Tools->Terminal) - it should have '/bin/zsh'. In the options below I have everything checked.

Hey @dheerajchand - any thoughts on the comments, above?

Pycharm has the right shell set, I did check that. I reinstalled Power
level 9k as well before posting, but I will check the install again!
On May 9, 2017 8:17 PM, "Ben Hilburn"<EMAIL_ADDRESS>wrote:
Hey @dheerajchand https://github.com/dheerajchand - any thoughts on the
comments, above?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/bhilburn/powerlevel9k/issues/510#issuecomment-300346239,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAdeHCaHVawAUNLZIsA0KDENeDBw-2ICks5r4RAjgaJpZM4NNtNf
.

@iScrE4m Awesome! We had some complaints about P9K not working in the builtin JetBrains-Shell. Could you try this fix for the cut-off icons (well it's for Konsole, but it might work on the PyCharm shell as well)?

It's not ZSH specific, even editing in VIM - space doesn't help. http://i.imgur.com/9IeyVCL.png

What a pity. But thanks for testing @iScrE4m

Closing this one due to inactivity. Feel free to re-open if there is something further to discuss!


it won't build on Jetson JP4.6.1 but for isaac common script

-- stderr: isaac_ros_nvengine
/usr/bin/ld:/workspaces/isaac_ros-dev/isaac_ros_nvengine/gxf/lib/gxf_jetpack46_1/core/libgxf_core.so: file format not recognized; treating as linker script
/usr/bin/ld:/workspaces/isaac_ros-dev/isaac_ros_nvengine/gxf/lib/gxf_jetpack46_1/core/libgxf_core.so:1: syntax error
collect2: error: ld returned 1 exit status
make[2]: *** [libgxe_node.so] Error 1
make[1]: *** [CMakeFiles/gxe_node.dir/all] Error 2
make: *** [all] Error 2
---
Failed   <<< isaac_ros_nvengine [22.3s, exited with code 2]

after performing the isaac common image script I added src then cloned the repository; then executed colcon build
it won't work

Make sure to have git-lfs installed and run git lfs pull to download the binaries into place if you did not have it installed before cloning.

From: Andrey Volodin @.>
Sent: Thursday, April 21, 2022 3:56 AM
To: NVIDIA-ISAAC-ROS/isaac_ros_visual_slam @.>
Cc: Subscribed @.***>
Subject: [NVIDIA-ISAAC-ROS/isaac_ros_visual_slam] it won't build on Jetson JP4.6.1 but for isaac common script (Issue #24)
-- stderr: isaac_ros_nvengine
/usr/bin/ld:/workspaces/isaac_ros-dev/isaac_ros_nvengine/gxf/lib/gxf_jetpack46_1/core/libgxf_core.so: file format not recognized; treating as linker script
/usr/bin/ld:/workspaces/isaac_ros-dev/isaac_ros_nvengine/gxf/lib/gxf_jetpack46_1/core/libgxf_core.so:1: syntax error
collect2: error: ld returned 1 exit status
make[2]: *** [libgxe_node.so] Error 1
make[1]: *** [CMakeFiles/gxe_node.dir/all] Error 2
make: *** [all] Error 2
Failed   <<< isaac_ros_nvengine [22.3s, exited with code 2]
after performing the isaac common image script I added src then cloned the repository; then executed colcon build
it won't work
—
Reply to this email directly, view it on GitHubhttps://github.com/NVIDIA-ISAAC-ROS/isaac_ros_visual_slam/issues/24, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ASS44RSXVFSBWM6LZRTBQR3VGEX4JANCNFSM5T63FDTA.
You are receiving this because you are subscribed to this thread.Message ID: @.***>

@hemalshahNV
Thank you for the update.
after git lfs pull it seems got build
Finished <<< isaac_ros_test [5.03s]
Starting >>> isaac_ros_nvengine
Starting >>> isaac_ros_visual_slam
Finished <<< isaac_ros_nvengine [2.00s]
[Processing: isaac_ros_visual_slam]
[Processing: isaac_ros_visual_slam]
[Processing: isaac_ros_visual_slam]
[Processing: isaac_ros_visual_slam]
Finished <<< isaac_ros_visual_slam [2min 3s]

Summary: 6 packages finished [2min 9s]
  1 package had stderr output: isaac_ros_test

However, how do I run it for zed mini camera? I got to execute every time to run the container scripts/run_dev.sh from ros common isaac?

@hemalshahNV
Could you publish the zed launch file, please?
Previously ther ewas https://github.com/NVIDIA-ISAAC-ROS/isaac_ros_visual_odometry/blob/main/isaac_ros_visual_odometry/launch/isaac_ros_visual_odometry_zed2.launch.py
which is not present.
Moreover, could you share launch file for zed [  not zed2 but just zed]
Thanks
AV

@hemalshahNV
lfs pull helped building container from script but therre still seems something missed?
nvidia@nvidia-desktop:~/isaac_ros_common/src/isaac_ros_visual_slam$ git lfs pull
nvidia@nvidia-desktop:~/isaac_ros_common/src/isaac_ros_visual_slam$ cd ..
nvidia@nvidia-desktop:~/isaac_ros_common/src$ cd ..
nvidia@nvidia-desktop:~/isaac_ros_common$ ./scripts/run_dev.sh
isaac_ros_dev not specified, assuming /home/nvidia/isaac_ros_common
~/isaac_ros_common ~/isaac_ros_common
Attaching to running container: isaac_ros_dev-aarch64-container
admin@nvidia-desktop:/workspaces/isaac_ros-dev$ . /opt/ros/foxy/setup.bash
admin@nvidia-desktop:/workspaces/isaac_ros-dev$ . install/setup.bash
admin@nvidia-desktop:/workspaces/isaac_ros-dev$ ros2 launch isaac_ros_visual_odometry s isaac_ros_visual_odometry_zed2.launch.py
scripts/ src/
admin@nvidia-desktop:/workspaces/isaac_ros-dev$ ros2 launch isaac_ros_visual_odometry s isaac_ros_visual_odometry_zed2.launch.py
scripts/ src/
admin@nvidia-desktop:/workspaces/isaac_ros-dev$ ros2 launch isaac_ros_visual_odometry s isaac_ros_visual_odometry_zed2.launch.py
scripts/ src/
admin@nvidia-desktop:/workspaces/isaac_ros-dev$ ros2 launch isaac_ros_visual_odometry isaac_ros_visual_odometry_zed2.launch.py
Package 'isaac_ros_visual_odometry' not found: "package 'isaac_ros_visual_odometry' not found, searching: ['/workspaces/isaac_ros-dev/install/isaac_ros_visual_slam', '/workspaces/isaac_ros-dev/install/isaac_ros_visual_slam_interfaces', '/workspaces/isaac_ros-dev/install/isaac_ros_test', '/workspaces/isaac_ros-dev/install/isaac_ros_nvengine', '/workspaces/isaac_ros-dev/install/isaac_ros_nvengine_interfaces', '/workspaces/isaac_ros-dev/install/isaac_ros_common', '/opt/ros/foxy/install']"
admin@nvidia-desktop:/workspaces/isaac_ros-dev$ ros2 launch isaac_ros_visual_odometry isaac_ros_visual_odometry_zed2.launch.py

The package has been renamed isaac_ros_visual_slam.


follow/unfollow button is not visible in Firefox

Describe the bug
follow/unfollow button is not visible in Firefox
To Reproduce
Steps to reproduce the behavior:

Go to profile/following
Expect "unfollow" button right to the contact name
Not there. :)

Expected behavior
See all buttons
Desktop (please complete the following information):

OS: Linux
Browser Firefox
Version 112

Additional info: The button has a "display: none !important;" element. Don't know, why.
I use nos2x-fox to login.

This is the case for read-only logins with npub etc


NewDockerPlugin (ndp)

This patch adds a new command, ndp, for creating new, REX-Ray managed plug-ins for Docker. To create the files necessary for a new REX-Ray managed plug-in for the cinder driver, simply execute the following:
$ ./ndp cinder
The plug-in has been successfully created!

To build the plug-in, please execute the following command:

    $ DRIVERS=cinder make build-docker-plugin

To include this plug-in as part of REX-Ray's CI process,
please edit the .travis.yml file and find the section near
the top of the file that looks like this:

    env:
      - REXRAY_BUILD_TYPE=
      - REXRAY_BUILD_TYPE=client
      - REXRAY_BUILD_TYPE=agent
      - REXRAY_BUILD_TYPE=controller
      - REXRAY_BUILD_TYPE= DRIVERS=ebs
      - REXRAY_BUILD_TYPE= DRIVERS=efs
      ...

Create a new entry at the end of the above section:

      - REXRAY_BUILD_TYPE= DRIVERS=cinder

That's all there is to it! Now the new plug-in will be a
part of REX-Ray's CI proces, built and deployed with the
rest of the REX-Ray managed plug-ins for Docker!

The ndp command creates the following files:
$ find .docker/plugins/cinder -type f
.docker/plugins/cinder/config.json
.docker/plugins/cinder/README.md

Codecov Report

Merging #843 into release/0.9.1 will not change coverage.
The diff coverage is n/a.

@@              Coverage Diff              @@
##           release/0.9.1    #843   +/-   ##
=============================================
  Coverage           8.78%   8.78%
=============================================
  Files                 25      25
  Lines               2981    2981
=============================================
  Hits                 262     262
  Misses              2683    2683
  Partials              36      36

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 2a7458d...44c083f. Read the comment docs.


Consolidate labeling in the property & visual editors

Currently, we are displaying the default name of an action in the secondary label. As a result, when you first created an action node you get duplicate names in the main label and the secondary label. Let's change the secondary label content to the raw control name. i.e. Microsoft.IfCondition in the screenshot above.

https://github.com/microsoft/BotFramework-Composer/pull/2930


Add "secondary status" to Linodes

Description
Adds support for states like "disk duplicating" and "cloning" to the Entity Detail header.

Maybe the statuses and ellipsis could be placed on the line below the Linode label instead?

Good catch @DevDW, @tiffwong is going to have a look at this separately.