fix @edgedb/generate issue Error SchemaDefinitionError specified migration parent is not the most recent migration, expected

windows 11
node v14.19.0
yarn 1.22.18

if the folder with the name generated was not created manually, it will throw an error

$ yarn generate:edgeql:client && yarn generate:edgeql:queries
yarn run v1.22.18
$ npx @edgedb/generate edgeql-js --output-dir ./generated/edgeql --target cjs --force-overwrite
Generating query builder...
Introspecting database schema...
(node:21456) UnhandledPromiseRejectionWarning: Error: ENOENT: no such file or directory, mkdir 'C:\Documents\edgedb-nestjs-example\generated\edgeql'
(Use `node --trace-warnings ...` to show where the warning was created)
(node:21456) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
(node:21456) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
Done in 1.42s.

there was some updates in @edgedb/generated, which probably conflicts with edgedb package

$ npx @edgedb/generate queries --file ./generated/edgeql/queries --target cjs --force-overwrite
Generating functions from .edgeql files...
Detected project root via edgedb.toml:
   C:\Documents\edgedb-nestjs-example
Connecting to database...
Analyzing .edgeql files...
   ./../C:\Documents\edgedb-nestjs-example\dbqueries\getUserByEmail.edgeql
   ./../C:\Documents\edgedb-nestjs-example\dbschema\migrations\00001.edgeql
(node:28116) UnhandledPromiseRejectionWarning: Error: SchemaDefinitionError: specified migration parent is not the most recent migration, expected 'm1tcya4emanq45tktoqkca64w6xvriojendyqhwk7lmbssdigrhjpq'
    at Object.analyzeQuery (C:\Documents\edgedb-nestjs-example\node_modules\edgedb\dist\reflection\analyzeQuery.js:26:15)
    at processTicksAndRejections (internal/process/task_queues.js:95:5)
    at async generateQueryFiles (C:\Documents\edgedb-nestjs-example\node_modules\@edgedb\generate\dist\queries.js:37:27)
    at async run (C:\Documents\edgedb-nestjs-example\node_modules\@edgedb\generate\dist\cli.js:264:13)
(Use `node --trace-warnings ...` to show where the warning was created)
(node:28116) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
(node:28116) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
Done in 0.85s.

suggested solutions:

replace generate:edgeql with:

"generate:edgeql": "mkdir -p generated && yarn generate:edgeql:client && yarn generate:edgeql:queries",

update @edgedb/generate to ^0.0.6


Needed some more explanation regarding sensor dashboard application.

I have gone through the project but am running wear application in emulator,so that am not able to get the service notifications from wear to mobile.please provide demo screenshots for reference.It will helps others too alot.And am dont know where to mention this comment,so only I have added this in issue block.

you have to pair your emulator to a real device. See official documentation for this step:
https://developer.android.com/training/wearables/apps/creating.html#SetupEmulator

yeap.I have paired my real mobile device to emulator and in that am not getting any changes in the mobile this is what am getting after running the application in mobile and as well as wear emulator.

Sorry, I didn't noticed: Emulators don't have any sensor!
You will see this in your logcat:
No Heartrate Sensor found
Samsungs Heartrate Sensor not found
No Light Sensor found
No Linear Acceleration Sensor found
No uncalibrated Magnetic Field Sensor found
No Pressure Sensor found
No Humidity Sensor found
No Rotation Vector Sensor found
No Significant Motion Sensor found
No Step Counter Sensor found
No Step Detector Sensor found


text

Executing the following command:
["convert", "-size", "320x100", "xc:lightblue", "-font", "Candice", "-pointsize", "72", "-tile", "pattern:checkerboard", "-annotate", "+28+68", "asdas", "out.png"]

Throws the following error:
magick.js:74 convert: UnableToOpenConfigureFile `colors.xml' @ warning/configure.c/GetConfigureOptions/714.
magick.js:74 convert: UnableToOpenConfigureFile `type.xml' @ warning/configure.c/GetConfigureOptions/714.
magick.js:74 convert: UnableToReadFont `Candice' @ warning/annotate.c/RenderType/1009.
magick.js:74 convert: DelegateLibrarySupportNotBuiltIn 'Candice' (Freetype) @ warning/annotate.c/RenderFreetype/1847.
magick.js:74 convert: FailedToExecuteCommand `'gs' -q -dQUIET -dSAFER -dBATCH -dNOPAUSE -dNOPROMPT -dMaxBitmap=500000000 -dAlignToPixels=0 -dGridFitTT=2 '-sDEVICE=pngalpha' -dTextAlphaBits=4 -dGraphicsAlphaBits=4 '-r72x72' -g504x144  '-sOutputFile=/tmp/magick-42QA_0BEfbiCPa%d' '-f/tmp/magick-42Gf4sw7fbIDPa' '-f/tmp/magick-42AaUWWpkLaNIP'' (-1) @ error/delegate.c/ExternalDelegateCommand/462.
magick.js:74 convert: FailedToExecuteCommand `'gs' -q -dQUIET -dSAFER -dBATCH -dNOPAUSE -dNOPROMPT -dMaxBitmap=500000000 -dAlignToPixels=0 -dGridFitTT=2 '-sDEVICE=pngalpha' -dTextAlphaBits=4 -dGraphicsAlphaBits=4 '-r72x72' -g504x144  '-sOutputFile=/tmp/magick-42QA_0BEfbiCPa%d' '-f/tmp/magick-42Gf4sw7fbIDPa' '-f/tmp/magick-42AaUWWpkLaNIP' -c showpage' (-1) @ error/delegate.c/ExternalDelegateCommand/462.
magick.js:74 convert: UnableToReadFont `Candice' @ warning/annotate.c/RenderType/1009.
magick.js:74 convert: DelegateLibrarySupportNotBuiltIn 'Candice' (Freetype) @ warning/annotate.c/RenderFreetype/1847.
magick.js:74 convert: FailedToExecuteCommand `'gs' -q -dQUIET -dSAFER -dBATCH -dNOPAUSE -dNOPROMPT -dMaxBitmap=500000000 -dAlignToPixels=0 -dGridFitTT=2 '-sDEVICE=pngalpha' -dTextAlphaBits=4 -dGraphicsAlphaBits=4 '-r72x72' -g504x144  '-sOutputFile=/tmp/magick-42BZwKN-LaAgcA%d' '-f/tmp/magick-42fyXQyXLCAaPp' '-f/tmp/magick-42ryaITPaKIaPp'' (-1) @ error/delegate.c/ExternalDelegateCommand/462.
magick.js:74 convert: FailedToExecuteCommand `'gs' -q -dQUIET -dSAFER -dBATCH -dNOPAUSE -dNOPROMPT -dMaxBitmap=500000000 -dAlignToPixels=0 -dGridFitTT=2 '-sDEVICE=pngalpha' -dTextAlphaBits=4 -dGraphicsAlphaBits=4 '-r72x72' -g504x144  '-sOutputFile=/tmp/magick-42BZwKN-LaAgcA%d' '-f/tmp/magick-42fyXQyXLCAaPp' '-f/tmp/magick-42ryaITPaKIaPp' -c showpage' (-1) @ error/delegate.c/ExternalDelegateCommand/462.

Probably text is not supported by wasm-IM but just in case I wanted to track this limitation here and make sure so we can update README with this information. Thanks

Researching I see that for text support ImageMagick must be linked with libfreetype which is currently not. We should document which features are not supported (like this one).
Besides that I tried to add the library and I'm not sure if it was inked but each time I try to print text it seems that ImageMagick try to call the program gs (ghostscript I think) - so even if the library is linked OK I doubt it will work. But I'm not an expert with emscripten so I'm not 100% sure of this...

It's now explicitly documented in readme that this is not supported, so I'm closing this

Since I think this is an important ImageMagick feature and since emscripten supports freetype library as a port (-s USE_FREETYPE=1) and I will try to make it work and since I will try to make it work I'm reopening this issue to track the work here.

Solved by https://github.com/KnicKnic/WASM-ImageMagick/pull/28

Solved in magica - closing this in favor of https://github.com/KnicKnic/WASM-ImageMagick/issues/52


Fix events pagination in the events_backfill() function

Also fixes https://github.com/zseta/python-opensea/pull/17


fix: add title to Link type

https://developer.mozilla.org/en-US/docs/Web/HTML/Element/link#title
I found that title is missing in  tag!

Thank you!
I want you to create a changeset by executing pnpm changeset.

Thanks! I added the changeset!


Fix for #35 and new integration test

This PR fixes issue #35 and proposes a new integration test suite for zend-db (using the travis-ci services, mysql at the moment).
The issue #35 has been solved removing the internal mapping of the field name with PDO parameter name, using a c_$i incremental naming convention.
The new test folder contains unit test (test/unit) and integration test (test/integration) in separate folders. The test databases for integration are created using a ZendIntegrationTest\Db\IntegrationTetListener file. This new approach simplify the travis-ci integration without the usage of the *_fixtures.sh files in .ci folder.

ping @alextech

ping also @dkmuir, @alshayed, @webimpress, @alextech involved in #35, #224, #289.

@alextech I think we should have specific integration tests for all the db engine that we support. Even for special cases like #35, where we need to reproduce issues like #288 and https://github.com/zendframework/zend-db/pull/178#issuecomment-255564783.

I also do not think separating engines for high level utility tests, such as TableGateway, is good. This again creates false positive passes when someone modifies TableGateway, writes test for it in MySQL and does not replicate the test to other platforms.

If you change TableGateway and write a specific test for MySQL you are testing the changes with a specific adapter, that maybe will fail even if the high level tests of TableGateway are passing. This is good to find specific issue or bad design. I don't see false positive here. Integration test and unit test are completely different and can be also executed as separated thing (that's why I split in two folder and created two commands: composer test and composer test-integration).

...If same abstraction test fails and needs engine-specific handling, then abstraction is badly designed at that point

Again, this is actually very good, because we can discover issue and bad design. Tests are useful to find mistakes, they don't prove that everything is ok (it's never ok as you know, even if you have 100% test coverage).
Anyway, I'm reviewing your comment and I'm glad that you improved the PR with https://github.com/ezimuel/zend-db/pull/1, thanks!

If you change TableGateway and write a specific test for MySQL you are testing the changes with a specific adapter, that maybe will fail even if the high level tests of TableGateway are passing.

Exactly.  So I did not mean that unit tests should be used instead of integration. I meant that integration should not be in an adapter specific namespace for Design Pattern implementations.
Design Pattern implementations, unlike direct adapter interaction have added responsibility of having same API work simultaneously on all engines. When you write TableGateway test in MySQL namespace that ends up not working for some reason in SqlServer, PostgreSQL as the documentation advertises, its a problem. As random example, https://github.com/zendframework/zend-db/pull/304/files#diff-56dd6fd011c00c8a8c735d14eed5c841R27  If that test passes for MySQL but not PostgreSQL, is that not a false positive?
Is everyone going to be diligent to copy, https://github.com/zendframework/zend-db/pull/304/files#diff-56dd6fd011c00c8a8c735d14eed5c841R88 4 times to our 4 supported platforms to verify something as basic as $tableGateway->update() works as advertised?
That does not mean don't keep them as integration. I mean it should not be isolated to one namespace or manually copied to all namespaces, but live in top level integration namespace and reran automatically for each integration engine in travis yaml config.

@alextech ok, now I see your point. I agree to move the TableGateway at top level. That said, we can still have some special cases where we need to test TableGateway only for a specific vendor, to reproduce am issue coming for a bad design or environment related.

Yes, there are some integration tests for TableGateway that are engine specific, eg, using delimited path as a table name for Pgsql and SqlServer.  I just remembered that case, sorry! So yes to

we can still have some special cases where we need to test TableGateway only for a specific vendor, to reproduce am issue coming


synchronous producer hangs when kafka is unreachable

This issue was brought to my attention by Michael Kowalchik in the mailing list
Steps to reproduce

Run a synchronous producer pointing at a kafka cluster with a single node
Kill the single kafka node while the producer is running
Observe that the producer's main thread hangs and must be killed externally

The expected result is that the producer's main thread should raise a SocketDisconnectedError from produce().
The following sequence of events causes this bug. When a broker is unavailable, SocketDisconnectedError is raised and caught. If there are no brokers available, this call to _update() raises an exception. This in turn kills the worker thread, meaning that code after the _update call, including pushing the original SocketDisconnectedError onto the delivery reports queue, does not execute. On the main thread, produce() is still waiting for the delivery report, which will never come because the worker has died.
Possible solutions include ignoring certain exception types from the _update() call, or catching any exception that happens between to_retry being populated and the delivery report being enqueued. I'd lean toward simply catching and warning about this specific exception, maybe giving it a more specific name in the process.

I've opened #450, which depends on #451. Once #451 is in master, I can rebase this branch, making it testable.

Duplicated by #456

I wanted to remove the try...except introduced in #450 as a fix for #629, and I realized that I'm actually not able to reproduce this issue anymore. It seems that this commit actually fixed this issue after the fact by ensuring that produce() didn't block the main thread in cases where there were exceptions pending. The try...except introduced in #450 had the unfortunate side effect of making NoBrokersAvailable result in all worker threads being permanently killed, thus I think it makes sense to remove it.

Using pykafka 2.6.0.dev2 (Python3 on MacOS X, Kafka server <IP_ADDRESS>) I see the sync producer still hangs when trying to send a message after the Kafka server has been terminated (using docker stop kafka) and re-started (using docker start kafka). This behaviour is fully reproducible, using just topic.get_sync_producer(max_retries=5) and producer.produce(message).
When killed, the stacktrace is:
File "/usr/local/lib/python3.6/site-packages/pykafka/producer.py", line 336, in produce
reported_msg, exc = self.get_delivery_report(timeout=1)
File "/usr/local/lib/python3.6/site-packages/pykafka/producer.py", line 359, in get_delivery_report
return self._delivery_reports.queue.get(block, timeout)
File "/usr/local/Cellar/python3/3.6.0/Frameworks/Python.framework/Versions/3.6/lib/python3.6/queue.py", line 173, in get
self.not_empty.wait(remaining)
File "/usr/local/Cellar/python3/3.6.0/Frameworks/Python.framework/Versions/3.6/lib/python3.6/threading.py", line 299, in wait
gotit = waiter.acquire(True, timeout)
KeyboardInterrupt

while True:     try:         report = self.get_delivery_report(timeout=1)         break    except Empty:         continue
Hi, we met the same issue that sync producer hangs when kafka dead and recovery soon. I thick the code above will cause this issue:
When kafka broker dead and recovery, the dilivery report response message from kafka broker to pykafka may be lost. And if lost response message, the code above will get into dead loop.
How could we handle this situation? Should we have 'timeout' parameter in 'produce' function?

Sounds like this needs another look.

@beniji @zhanghan987 Can you be more specific about the exact producer and broker settings you're using to reproduce this issue, as well as the specific sequence of steps you're performing? I'm unable to replicate it. In my local tests, I'm using a single broker with an unreplicated topic. I produce repeatedly to it with a synchronous consumer in a while True loop. As that loop is running, producing one message each iteration, I kill the broker. As soon as the broker dies, the consumer retries the connection a few times in quick succession before throwing an exception and dying. That is, it doesn't hang, it just dies immediately, which is the expected behavior.
How can I adjust my local test to see the behavior you're seeing?

i have a producer writing to a local kafka and zookeeper.  i let the producer write millions of messages - one message at a time - using the HighLevelProducer
Before all the writes are done, I stop the kafka and the send never exits.  This is perhaps the hanging we are talking about?

@emmett9001  Hi, thanks for your reply. We have one broker and one producer in our environment as same as your tests, but our producer and broker are in the different network segment from different IDC room. And when the network between the two IDC  not stabilization like lost connection for a while, this issue happens.
It happens for several times, sorry for that I don't know how to reproduce it in your local test.

I think I finally got my head around the situation that can cause this hang - essentially it's when mark_as_delivered is never called for a given message in sync mode. https://github.com/Parsely/pykafka/pull/769 makes the producer resilient to that case.


[Remote Store] Add support to reload repository metadata inplace

Description
This PR adds the support to reload repository metadata in-place. Starting out, we limit this feature to only system repository reloads and the specific S3 repository implementation. This can be extended to make all repositories reloadable in-place in the future.
Related Issues
Resolves #9118
Check List

[x] New functionality includes testing.

[x] All tests pass

[x] New functionality has been documented.

[x] New functionality has javadoc added

[x] Commits are signed per the DCO using --signoff
[x] Commit changes are listed out in CHANGELOG.md file (See: Changelog)

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Lets also add ITs for the reloadable settings.

org.opensearch.repositories.blobstore.BlobStoreRepositoryRemoteIndexTests.testRetrieveShallowCopySnapshotCase1 => reported flaky in https://github.com/opensearch-project/OpenSearch/issues/10314

org.opensearch.index.translog.RemoteFsTranslogTests.testMetadataFileDeletion => reported flaky in https://github.com/opensearch-project/OpenSearch/issues/9605

#10372

Gradle Check (Jenkins) Run Completed with:

RESULT: FAILURE ❌
URL: https://build.ci.opensearch.org/job/gradle-check/26987/
CommitID: b16af58
Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green.
Is the failure a flaky test unrelated to your change?


Security vulnerability updates KB4506163 and KB4506164 detected, unable to install

Unable to reopen https://developercommunity.visualstudio.com/content/problem/660716/security-vulnerability-updates-kb4506163-and-kb450.html
Please create new ticket there and move my post with attachements.
Paulius Petkevičius Jan 07 at 01:54 PM

This is VS Code, a different product than VS 2013 and VS 2015.

Please, guys, then I need to install Visual Studio to raise a ticket. I do not use any of these VS Codes, I just cannot install updates for client servers. Could make a favor and register the case for me?


Set code coverage enabled for schemes

Status

in development
Issue

resolves #7
Todos

[ ] Add Quick and Nimble
[ ] Setup unit tests

Codecov Report

:exclamation: No coverage uploaded for pull request base (develop@f2fe087). Click here to learn what that means.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             develop   #12   +/-   ##
=======================================
  Coverage           ?    0%
=======================================
  Files              ?    10
  Lines              ?   148
  Branches           ?     0
=======================================
  Hits               ?     0
  Misses             ?   148
  Partials           ?     0

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 f2fe087...dca0cc8. Read the comment docs.


Waveform doesn't show up

I tried redownloading 3 times and the waveform still doesn't show up.

Also is there anyway i can make the chart goes slower ? Like x0,5 because it goes so fast and i want to make sure that i place to notes correctly

Can you send me the audio file?
And no, there isn't a way to control playback speed at the moment

ANU.mp3
https://drive.google.com/file/d/19JnG_Y04OLmMmh2tEgHaKbly_O8ZG2uG/view?usp=drive_web
Send this again because the file was too large to be sent
Vào Th 3, 21 thg 11, 2023 vào lúc 21:48 Sherif @.***>
đã viết:

Can you send me the audio file?
And no, there isn't a way to control playback speed at the moment
—
Reply to this email directly, view it on GitHub
https://github.com/crash5band/MikuMikuWorld/issues/49#issuecomment-1821069834,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BEE7VCXVBYR36LQQZCJ56HLYFS5NRAVCNFSM6AAAAAA7UVAFEWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMRRGA3DSOBTGQ
.
You are receiving this because you authored the thread.Message ID:
@.***>

Mine doesn't show up, no matter what audio i use

Same issue here:

mmw_debug.zip
Still not quite sure why it isn't showing up... Can you try this build and tell me what is showing up under Audio > Waveform in the debug window?

Here:

So I managed to reproduce it by switching to integrated graphics which I'm guessing is the case for you both. In any case I managed to identify the cause and will release a fix soon

Fixed with beb6cb1

Thanks!
Do you think you can provide a build of this fix (or build instructions)?

I'll leave the release for when I complete #50 but if you want to build it yourself I'm pretty sure building the solution with VS2022 is all that is needed.


A few issues encountered

I've just started implementing AirBrake into one of our projects as a trial, however I'm having a few issues - hopefully someone here might be able to answer them (though I notice this library hasn't been updated in 2 years...)

Our app has request validation enabled, however when a "A potentially dangerous Request.Form value was detected from the client" is triggered, AirBrake is itself throwing an exception when trying to process the Form data.  This means that we have to Try Catch the SendToAirBrake itself.

We are trialing this just now, so it has to run along side our existing error notification system, however when we call the exception.SendToAirBrake function, this seems to be causing the thread to lock and the request never ends, leaving the user hanging indefinitely - this is requiring us to run the SendToAirBrake command in a separate Task in order to prevent locking, which seems like it should be unnecessary (this fix also only seems to work locally in dev, when live we are still seeing the request 'hanging' when an error occurs).     Looks like it might be issue with an Async function being called in a non-async manner.

All errors logged in the dashboard are coming through with the URL of http://www.example.com/ rather than the actual URL being requested.

Any feedback on these issues would be appreciated.

These issues should be resolved in our new notifier. Among other features it's totally asynchronous, so your code shouldn't become slower or be blocked. Please keep us in touch on your integration and let us know if any new issues happen. Thanks.


Jms Message Driven Channel Adapter Typo

The following 3 methods may be renamed:
Current/From: Jms.messageDriverChannelAdapter(...)
To: Jms.messageDrivenChannelAdapter(...)
This is really a tiny typo of the method signature that would be a breaking change when updating. I just decided to share it because I use the spring-integration-java-dsl in my projects and I like it :)
Thanks for the amazing work!

Hi @magiccrafter !
Thank you for catching that out!
As you see it is fixed already. We found the good compromise in face of @Deprecated :smile:


Update are applied

All updates are applied.
Includes:

LICENSE
Structure project

Main.java第九行可以不需要，反正注册物品和方块在其他文件里面
把这些东西放到ChemisCraftNeedApi里面

Added license just now


Add git binary as a dependency

We should add the git binary as a dependency to permit git clone on freshly installed machines

Yes sir!

Yes sir!

I'll give it a shot, just struggling with cross-compilation on macOS

I'll give it a shot, just struggling with cross-compilation on macOS

Reopening because we need git also inside the container.

Reopening because we need git also inside the container.

Why executing the apt-get install inside the container?
Shouldn't we bake the required packages insite the image itself?

Why executing the apt-get install inside the container?
Shouldn't we bake the required packages insite the image itself?

Docker buildx cannot still build the multiarch images right if I run apt during build.. so this is a workaround. We need an issue for this.

Docker buildx cannot still build the multiarch images right if I run apt during build.. so this is a workaround. We need an issue for this.

fixed in current master, will go to the releases (likely 0.0.8) once travis comes back from oblivion

fixed in current master, will go to the releases (likely 0.0.8) once travis comes back from oblivion


[iOS] Add data Uri support

Solves this issue: https://github.com/Microsoft/AdaptiveCards/issues/2130

it looks like this PR picked up some previous commits.

Rebuilt the android version and it worked


[Crash] World Folder Corruption Bug

Hey, I've been trying to contact you about your car's extended warranty. Please call me back as soon as possible!
Thanks!
Geicosto
Make: Oldsmobile
Model: Cutlass Supreme
Color: Red
Year: 1997
Miles: 185,378

GOOD! You deserve it!


Disable cardfield autofocus

resolves #135

Hi @thorsten-stripe , I have stripe-react-native 0.1.5 but this is still happening. Once I touched the CardField, it would never go blur which resulted in me not able to click on anything else on in the View. Is there anyway I could resolve
react-native : 0.64.2


Housekeeping: python package deps upgrade

Proposed changes:

twilio upgrade: https://github.com/RasaHQ/rasa/pull/12583
ruff upgrade: https://github.com/RasaHQ/rasa/pull/12618

No upgrade:

matplotlib: https://github.com/RasaHQ/rasa/pull/12629
tarsafe: https://github.com/RasaHQ/rasa/pull/12525
rocketchat-api: https://github.com/RasaHQ/rasa/pull/12402

Status (please check what you already did):

[ ] added some tests for the functionality
[ ] updated the documentation
[ ] updated the changelog (please check changelog for instructions)
[x] reformat files using black (please check Readme for instructions)

@varunshankar I've bumped pyyaml to >6.0 in #12678 which seems to address the CI errors


VCS Parsing Error

The commit I am looking at: 6515c42
With VCS 2022, when compiling pod_X1Y1_ruche_X16Y8_hbm_one_pseudo_channel/bigblade-vcs/exec/simv during "make regression", I will get the following error:

Source file "tb_timescale=1ps/1ps" cannot be opened for reading due to 'No such file or directory'.

Looks like VCS thinks "tb_timescale=1ps/1ps" is a filename instead of some parameter. Not sure if it is a bug from 2022 VCS.
https://github.com/bespoke-silicon-group/bsg_replicant/blob/65a2398c3f256370f4f315bd12f6fa9c89deee3a/libraries/platforms/bigblade-vcs/link.mk#L61

Seems like you can track it down YM
On Tue, Mar 28, 2023 at 6:12 PM Yuan-Mao @.***> wrote:

The commit I am looking at: 6515c42
https://github.com/bespoke-silicon-group/bsg_replicant/commit/6515c42b03730a1f2e584d81612976a4615d0ac8
With VCS 2022, when compiling
pod_X1Y1_ruche_X16Y8_hbm_one_pseudo_channel/bigblade-vcs/exec/simv during
"make regression", I will get the following error:
Source file "tb_timescale=1ps/1ps" cannot be opened for reading due to 'No
such file or directory'.
Looks like VCS thinks "tb_timescale=1ps/1ps" is a filename instead of some
parameter. Not sure if it is a bug from 2022 VCS.
https://github.com/bespoke-silicon-group/bsg_replicant/blob/65a2398c3f256370f4f315bd12f6fa9c89deee3a/libraries/platforms/bigblade-vcs/link.mk#L61
—
Reply to this email directly, view it on GitHub
https://github.com/bespoke-silicon-group/bsg_replicant/issues/821, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AEFG5AFIBMY2EQD3AZVIS2DW6OEBTANCNFSM6AAAAAAWLJCCVE
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

It seems like the error is caused by the -L flag, removing the -L would fix everything. I could not find the -L and -M flags in the VCS user guide and the vcs -help page, and I guess these two flags might have been accidentally added?

If we actually want to link, it should be -LDFLAGS "-L ..."
https://github.com/black-parrot/black-parrot/blob/08edfb479c7b5d55d665a63464785044c6b4cd35/bp_common/syn/Makefile.vcs#L40

but it looks like maybe we're trying something else there. I think one wrinkle is that was probably written for VCS-MX which may have slightly different options. I would propose we change to whatever works for a modern VCS


Remove redundant space to fix release job

@giladgurvich It should :sweat_smile:
The space was added to the docker build tags after a "-", causing the tag to be read as a flag


Hide Results List on Blur

Issue Description
Hello, I'm having an issue with the results list not hiding if a user doesn't select an option.  I thought maybe the trigger param might allow for this, but adding 'blur' to the event array doesn't seem to help.
Example:

JS Config:
  const autoCompletejs = new autoComplete({ // eslint-disable-line
    data: {
      async src() {
        // Fetch External Data Source
        const source = await fetch('us_institutions.json');
        const data = await source.json();
        // Returns Fetched data
        return data;
      },
      key: ['institution'],
      cache: true,
    },
    trigger: {
      event: ['input','blur'],
    },
    searchEngine: 'strict',
    highlight: true,
    selector: '.gf_auto_complete input',
    threshold: 3,
    debounce: 300,
    maxResults: 5,
    resultsList: {
      render: true,
    },
    onSelection(feedback) {
      // Add value
      document.querySelector('.gf_auto_complete input').value = feedback.selection.value.institution;
    },
  });

Desired Behavior
I would like for the results list to hide when the focus of the input moves to another element.

I was able to resolve this by adding a blur event listener to the input field, and then calling this function:
const hideResultsList = () => {
  const autoCompleteList = document.getElementById('autoComplete_list');

  if (autoCompleteList) {
    autoCompleteList.innerHTML = '';
  }
};

It would still be nice to have access to clearResults so that this could be called programmatically.

I also had the same issue with the results list not hiding by default. Here is the pure CSS workaround I used with the OOB element IDs:
#autoComplete + ul#autoComplete_list{
  display:none;

}
#autoComplete:focus + ul#autoComplete_list {
  display: block;
}

My solution taken from demo
// Toggle event for js-delivery input
// showing & hidding results list onfocus / blur

["focus", "blur"].forEach(function (eventType) {
	const resultsList = document.querySelector("#autoComplete_list");

	inputEl.addEventListener(eventType, function () {
		if (eventType === "blur") {
			// Hide results list
			resultsList.style.display = "none";
		} else if (eventType === "focus") {
			// Show results list
			resultsList.style.display = "block";
		}
	});
});

v8.0


4_cv_basics/1_image_representation/Makefile Updated

The error encountered indicates that the compiler cannot find the SDL2 header file. The sdl2 library is only used in 4_cv_basics/1_images_representation/main.cpp, so I have only updated its makefile.
This PR Resolves the issue #117

@SuperChamp234, have a look at the PR.

This PR needs to update all the makefiles in all folders, as #107 did. Make sure you test the Makefiles in the folders because some might have a conflicting file structure.

This PR will be assigned to someone else, hence closing it.


Upgrading to 3.2?

Hi, I followed the instructions to upgrade to 3.2 (https://laravel-backpack.readme.io/docs/whats-new-november-2016) - although I did not see the 3.2 release, but only the dev one.
I still get the old Save buttons. Any ideas?

Hey,
It's probably easier to update your composer.json to
'backpack/crud": "^3.2 as 3.1"'
To make sure other packages are happy.
Then run 'composer update' and paste us the output
You'll also need to make sure you republish any form related views like form_content etc

Hi @slickorange ,
Backpack\CRUD 3.2 is not officially released yet. We're waiting for Laravel to move to 5.4, so we can bump the version at the same time. This way, developers will only need to go through the upgrade process once, for both Laravel and Backpack.
If you want to be ahead of the curve and use Backpack 3.2 right now, you can use the process Owen has described above.
Cheers!


Cilium version v1.15.5 missing

Cilium version: v0.16.7 compiled with go1.22.2 on linux/amd64
Kubectl version: v1.28.2
How to reproduce the issue:

Try to install cilium v1.15.5 - cilium install --version v1.15.5
Error occurs: looks like "https://helm.cilium.io" is not a valid chart repository or cannot be reached: Get "https://helm.cilium.io/index.yaml": tls: failed to verify certificate: x509: certificate signed by unknown authority

List available version for install - cilium install --list-versions
v1.16.0-pre.2
v1.16.0-pre.1
v1.16.0-pre.0
v1.15.4 (default)
v1.15.3
v1.15.2
v1.15.1
v1.15.0
Version v.15.5 is missing
I am not able to install this version, which is the latest most stable one. Am I missing something ?
Thank you in advance for the help. Live long and prosper !

cilium version
cilium-cli: v0.16.8 compiled with go1.22.3 on linux/amd64
cilium image (default): v1.15.5
cilium image (stable): v1.15.5
cilium image (running): 1.15.4

cilium install --list-versions | head
v1.16.0-pre.2
v1.16.0-pre.1
v1.16.0-pre.0
v1.15.5 (default)
v1.15.4
v1.15.3
v1.15.2
v1.15.1
v1.15.0
v1.15.0-rc.1


Putting a space in tag loses all flags

If I have a tag containing long: "blah", all options are lost from the parser, and Parse completes without any usage printed.

This will not happen. We conform to the Go standard. Please have a look at #92.
Also you should check if your parsing produces any errors. Using a malformed tag will produce one.
package main

import (
	"fmt"

	"github.com/jessevdk/go-flags"
)

func main() {
	var opts struct {
		Foo string `long :"bar"`
	}

	_, err := flags.Parse(&opts)
	if err != nil {
		fmt.Printf("Error: %v\n", err)
	}
}

go run tt.go
Error: expected `:' after key name, but got `32' (in `long :"bar"`)


Printing long text to console fails on iOS

Steps to Reproduce
See #8460 for original issue, reported as a problem with interop messaging. It is not. On iOS:

flutter create myapp
Add the code below after _counter++ on line 58 of the generated myapp/lib/main.dart.
flutter run (using iOS Simuator)
Tap the button twice
Observe: the app terminates.

      print('''
Paris (French: [paʁi] ( listen)) is the capital and most populous city of France. It has an area of 105 square kilometres (41 square miles) and a population in 2013 of 2,229,621 within its administrative limits.[4] The city is both a commune and department, and forms the centre and headquarters of the Île-de-France, or Paris Region, which has an area of 12,012 square kilometres (4,638 square miles) and a population in 2014 of 12,005,077, comprising 18.2 percent of the population of France.[5]The agglomeration has grown well beyond the city's administrative limits. The Paris unité urbaine is a measure of continuous urban area for statistical purposes, including both the commune and its suburbs, and has a population of 10,601,122 (Jan. 2013 census) which makes it the largest in the European Union.[2] The aire urbaine de Paris, a measure of metropolitan area, spans most of the Île-de-France region and has a population of 12,405,426 (Jan. 2013 census),[6] constituting nearly one-fifth of the population of France.[7] The Metropole of Grand Paris was created in 2016, combining the commune and its nearest suburbs into a single area for economic and environmental co-operation. Grand Paris covers 814 square kilometres (314 square miles) and has a population of 6.945 million persons.[8] Paris was founded in the 3rd century BC by a Celtic people called the Parisii, who gave the city its name. By the 12th century, it was the largest city in the western world, a prosperous trading centre, and the home of the University of Paris, one of the oldest universities in history. By the 17th century Paris was one of Europe's major centres of finance, commerce, fashion, science, and the arts, and it retains that position still today. The Paris Region had a GDP of €624 billion (US \$687 billion) in 2012, accounting for 30.0 percent of the GDP of France, and ranking it as one of the wealthiest regions in Europe; it is the banking and financial centre of France, and contains the headquarters of 29 of the 31 French companies ranked in the 2015 Fortune Global 500. The city is also a major rail, highway, and air-transport hub, served by the two international airports Paris-Charles de Gaulle (the second busiest airport in Europe after London Heathrow Airport with 63.8 million passengers in 2014) and Paris-Orly. Opened in 1900, the city's subway system, the Paris Métro, serves 5.23 million passengers daily.[9] It is the second busiest metro system in Europe after Moscow Metro. Paris is the hub of the national road network and is surrounded by three orbital roads: the Périphérique, the A86 motorway, and the Francilienne motorway. Paris Gare du Nord is the busiest railway station in the world, outside of Japan, with 262 millions passengers in 2015.[10] Among Paris's important museums and cultural institutions are the most-visited art museum in the world, the Louvre, as well as the Musée d'Orsay, noted for its collection of French Impressionist art, and the Musée National d'Art Moderne in the Pompidou Centre, the largest collection of modern and contemporary art in Europe. The central area of the city along the Seine River is classified as a UNESCO Heritage Site, and includes many notable monuments, including Notre Dame Cathedral (12th century to 13th century [11]); the Sainte-Chapelle (13th century); the Eiffel Tower (1889); the Grand Palais and Petit Palais (1900); and the Basilica of Sacré-Cœur in Montmartre (1914). In 2015 Paris received 22.2 million visitors, making it one of the world's top tourist destinations.[12] and is also known for its fashion, particularly the twice-yearly Paris Fashion Week, and for its haute cuisine, and three-star restaurants. Most of France's major universities and grandes écoles are located in Paris, as are France's major newspapers, including Le Monde, Le Figaro, and Libération. The association football club Paris Saint-Germain and the rugby union club Stade Français are based in Paris. The 80,000-seat Stade de France, built for the 1998 FIFA World Cup, is located just north of Paris in the neighbouring commune of Saint-Denis. Paris hosts the annual French Open Grand Slam tennis tournament on the red clay of Roland Garros. Paris hosted the 1900 and 1924 Summer Olympics and is bidding to host the 2024 Summer Olympics and thus become the second city to have hosted the Games three times. The 1938 and 1998 FIFA World Cups, the 2007 Rugby World Cup and UEFA Euro 2016 were also held in the city, and every July, the Tour de France of cycling finishes in the city.
      ''');

debugPrint works around this issue.  We should probably change print to work around it directly.

https://github.com/flutter/flutter/issues/232 is the bug for moving the debugPrint logic to print itself.

Is this an engine issue or a framework issue? cc @abarth

Dupe of https://github.com/flutter/flutter/issues/6758.


How to contribute to the wiki?

I made some docs for the wiki but I cant push them, so I guess I'll just drop it here unless I can be given access to push changes. Cheers.
NOTE: this list may not show all snippets included with this repository.
You can look where they are defined (here)[https://github.com/rafamadriz/friendly-snippets/blob/main/snippets/sql.json]
createt Create Regular Table
CREATE TABLE tableName (
  attribute(s)
);

createi Create Table with Conditional
CREATE TABLE IF NOT EXISTS tableName (
  attribute(s)
);

created Create Regular Database
CREATE DATABASE name;

createdi Create Database with Conditional
CREATE DATABASE IF NOT EXISTS;

insert Insert value(s)
INSERT INTO tableName (
  attribute(s)
) VALUES ( values )

dropt Drop table
DROP TABLE tableName;

dropd Drop Database
DROP DATABASE dbName;

dropti Drop Table with Conditional
DROP TABLE IF EXISTS tableName;

dropdi Drop Database with Conditional
DROP DATABASE IF EXISTS tableName;

showt Show Tables
SHOW TABLES;

showd Show Databases
SHOW DATABASES;

select Regular Select
SELECT attribute(s) FROM tableName;

selectd Select Distinct
SELECT DISTINCT attribute(s)
  FROM tableName;

selectw Select with Condition
SELECT attribute(s)
  FROM tableName
  WHERE condition;

selector Select with order
SELECT attribute(s)
  FROM tableName
  ORDER BY attribute(s) ASC|DESC;

updatet Update table
UPDATE tableName
  SET attribute(s)
  WHERE condition;

delete Delete records
DELETE FROM tableName
  WHERE condition;

altert Alter table
ALTER TABLE tableName
   intructions;

alterad Alter table - Add column
ALTER TABLE tableName
  ADD COLUMN col_name;

alteraf Alter table - Add column after

ALTER TABLE tableName
  ADD COLUMN col_name
  AFTER col_name;

alterdb Alter database

ALTER DATABASE dbName
  CHARACTER SET charset
  COLLATE utf8_unicode_ci;

ijoin Inner Join

SELECT attribute(s)
  FROM tableName
  INNER JOIN tableName2
  ON match;

rjoin Right Join

SELECT attribute(s)
  FROM tableName
  RIGHT JOIN tableName2
  ON match;

ljoin Left Join

SELECT attribute(s)
  FROM tableName
  LEFT JOIN tableName2
  ON match;

fjoin Full Join

SELECT attribute(s)
  FROM tableName
  FULL JOIN OUTER tableName2
  ON match
  WHERE condition;

union Regular Union

SELECT attribute(s) FROM tableName
UNION
SELECT attribute(s) FROM tableName2;

uniona All union

SELECT attribute(s) FROM tableName
UNION ALL
SELECT attribute(s) FROM tableName2;

groupb Group by

SELECT attribute(s)
  FROM tableName
  GROUP BY attribute(s);

bakupd Backup database

BACKUP DATABASE dbName
  TO DISK filepath;

bakupdw Differential backup database
BACKUP DATABASE dbName
  TO DISK filepath
  WITH DIFERENTIAL;

primaryk Primary Key
PRIMARY KEY(attribute)

primarykc Constraint Primary Key
CONSTRAINT attribute PRIMARY KEY(attribute(s))

foreingk Foreign Key
FOREIGN KEY(attribute) REFERENCES tableName(attribute)

foreingkc Constraint foreign Key
CONSTRAINT attribute FOREIGN KEY (attribute(s))
  REFERENCES tableName(attribute)

check Check
CHECK ( condition )

createuser Create User
CREATE USER 'username'@'localhost' IDENTIFIED BY 'password';

deleteuser Delete User
DELETE FROM mysql.user WHERE user = 'userName';

grantuser Grant Privileges
GRANT ALL PRIVILEGES ON db.tb TO 'user_name'@'localhost';

Appreciate the help @0neMiss ! While I can make the updates to the wiki, I think @rafamadriz would need to grant access per individual (to ensure random edits aren't being made).
Though if this understanding is wrong, feel free to correct me (it has been some time since I last configured a repository wiki :sweat_smile: )

No worries! I don't mind if the updates are made for me, unless you would like more help with doing wiki updates which I would gladly participate in! Thanks

My apologies on the delay @0neMiss, but the page has been created here!
I modified the initial "note" message on format, but otherwise it's basically just a copy-paste to the page.
Let me know if you'd like anything modified or if it's good to go for now :sunglasses:


Build tool support to aid issue reporting

It would be useful for build.py to report the status of all loaded libraries in a succinct way, such that it can be copy/pasted into github issues.
We already have --status but this needs to be revisited to ensure it meets all the requirements for reporting issues... perhaps an enhanced github-centric --info call which would include all current changesets, all current version hashes (inc tags, if on a tagged branch) the current build target and so forth.
Needs discussion as to what would be included here; here is a non-exhaustive list of what I think would be useful right now, but if anyone has any ideas for further inclusion... @microbit-carlos or @finneyj perhaps?

[ ] Current target platform
[ ] Current git tag or hash for each library
[ ] Current git tag or hash for the root project
[ ] The contents of codal.json, for the flags being used

Sounds good! We can also create a GitHub issue template in the codal repos showing the command to print the info and asking users to paste the results.
I think there is a git command to print the latest tag + number of additional commits since the tag, so that'd be useful to have.
But let's make sure we don't go too overboard, for the vast majority of users this will be a command they'll likely run only to paste the results in a GitHub bug report.

agree - this sounds great, but let's keep it to the basics. I think your list above looks spot on @JohnVidler


Update Button component to support outputting standalone CSS

^ for externally using Bolt as a standalone library via  and

@remydenton @mikemai2awesome can either of you guys take a quick peek at this?
I just fixed the merge conflicts -- just need this small update to get OK'd so we can get this version of the button component down to master.

This passes a quick gut check.  I will try to take a closer look a little later (feel free to merge it in in the meantime if you're trying to get this out the door).


docs: correct spelling of CHANGELOG

Fix minor type in the variables naming

@googlebot I signed it!

Closing this now as the typo is present in multiple places so more work is required


[feature] disclose web3modal version somewhere

What problem does this new feature solve?
I want to confirm whether a recent web3modal version is used to confirm it is subject to any issues/bugs
Describe the solution you'd like
Maybe behind the "?" symbol

Closing as resolved per our conversation about this being available in localStorage


allow appears missing from the GoogleOAuth2 options

Coverage remained the same at 88.889% when pulling 2ebe554c85c5da39358bbb587229882f08919b59 on mikekoetter:patch-1 into 0651ef518710833a1ac3cf3f3f89f49f34f91031 on waterlock:master.


refactor pipelineTask validation

Changes
Introducing pipelineTask and pipelineTaskList validation receiver functions to simplify the way tasks are validated for taskRef and taskSpec.
This is a pure refactoring, no functional changes expected.
/kind cleanup
Submitter Checklist
These are the criteria that every PR should meet, please check them off as you
review them:

[x] Includes tests (if functionality changed/added)
[x] Includes docs (if user facing)
[x] Commit messages follow commit message best practices
[x] Release notes block has been filled in or deleted (only if no user facing changes)

See the contribution guide for more details.
Double check this list of stuff that's easy to miss:

If you are adding a new binary/image to the cmd dir, please update
the release Task to build and release this image.

Reviewer Notes
If API changes are included, additive changes must be approved by at least two OWNERS and backwards incompatible changes must be approved by more than 50% of the OWNERS, and they must first be added in a backwards compatible way.
Release Notes
NONE

/test pull-tekton-pipeline-integration-tests

thanks @vdemeester for the feedback, the new changes are much easier to read now 🙏

/retest

/lgtm

/test pull-tekton-pipeline-integration-tests

one more attempt to retest 🤞
/test pull-tekton-pipeline-integration-tests


EFI boot?

Does RancherOS support EFI booting? Looking at the distribution iso for 0.4.3, I see /boot directory but no *.efi files, which leads me to suspect that it does not?

We don't package an EFI image, but it will boot from EFI if you already have a bootloader in place.  It would be nice if we created an image, it would make it much easier to run on my Minnowboard Max.

Shouldn't be too hard to extend the image to do it. Use efilinux from Intel or shim from Fedora could even get it working with SecureBoot, although that is less of an issue. I would be happy with an iso that boots straight from EFI with SecureBoot disabled.
Minnowboard Max?

I got it working. There still are 2 issues:

It takes an extra 10 seconds or so to start up (although I suspect that is VirtualBox's EFI implementation)
It doesn't yet support SecureBoot (but easily could with shim)

You want a pull request?

I'd be interested in this

Gosh, this was a month ago. @ibuildthecloud do you want a PR on this? I would like to add all of it, but:

I need to find some time (paid work comes first)
I am not putting in the effort unless I know it will get merged

We 100% would want a PR.  Sorry for the delay.

A little busy, @ibuildthecloud ? I cannot imagine! :-)
I need to dig back in and find this stuff. I just implemented a platform with secure and encrypted apps on a root drive that even physical access to the machine cannot give you... but no need for a user to be present to enter the unlock password. I did it on Debian, but since the apps themselves are just containers, I would love to do it over Rancher too. If only I had the time.
Either way, got all the way into initram and MBR and UEFI and GPT and TPM and encryption and kernel and and ....
I will try to dig this part out and set you up for UEFI boot.

@ibuildthecloud when I run a full build, what platform do I build it on? What are the prereqs?

@ibuildthecloud yes, completely confused. How does the build process work? Do I run it on my local Mac? On a Linux machine, and of what flavour? Does it build inside a docker container or locally? There isn't much info there.

And my head is spinning around the dependencies. What is vbox doing in the initrd?

@deitch You might want to work off the v0.5 branch we have the build is completely different there.  We are in the middle of a bit of a transition.  The build in that branch is kicked off by running make.  It runs in a container so you can run it on a Mac assuming you have Docker setup (Docker for Mac or Boot2Docker).

@deitch There are almost zero dependencies of the host required, just make and curl.  vbox is in the build because people want vbox tools for docker-machine to work right.  Currently it is not fully used.

That works, much easier.
Yeah, I have D4Mac on my MBA for a while. Even got on the latest Beta, but it requires a CPU feature not available on my 5.5-yr-old Air.... and Apple's offerings are so pathetic (and old) now, that I cannot bring myself to spend the money to upgrade. Contemplating an alternate ultrabook and running Hackintosh or Win10 with Linux/Hack VM, or maybe even Linux desktop. Insane.
I am forking now.

Do you have any idea why github only includes 5 branches in the fork? I can always do it locally on my laptop - add upstream, add tracking branch, then push to origin - but that is a pain.

OK, got the branch. Next question. Running make pulls a large list of targets from scripts/, basically every file there except clean and run. Each of those is just a target for .dapper <script>.
How does this all tie together?
And for EFI, we essentially need:

wget (or curl) a package, unzip a file out of it,
install the correct directories and files in the right place in the image - I figured this out
some changes to the iso creation process - I figured this out

The above will handle booting the iso; booting when installed local is more, but one step at a time.
Where do I run the wget and curl? images/ directory looks like boot-up processes; package-iso is where I actual install onto the CD image, but not getting the files needed. Do I put it in Dockerfile.dapper? Where is a better place?

I am having an issue with the build. Will open a separate issue.

As for the build, I finally am getting my head around how this is structured. A doc would have saved lots of headache, but OK, here we are:

make calls the default target of ci
default target of ci calls ./.dapper scripts/ci, which sets up the entire environment in a container, and then in that container calls scripts/ci
scripts/ci itself calls just 4 scripts: build, test, prepare, package

Each of those scripts in turn calls others:

build: calls build-target, which builds the ros binary via go; build-host, which just ensures host_ros is a copy of ros
test: runs tests
prepare: runs four scripts:

template: generates build/os-config.yml from its template

build-images: builds an image for each of the ones in images/ directory, which serve as the system-docker images to run services

tar-images: saves all of the above images to a tar file once built

layout: creates the initrd directory structure

package: runs three scripts:

package-rootfs: creates the root file system structure and zips it up into a .tar.gz, then creates an initrd cpio file

package-initrd: identical to package-rootfs, no clue why it is there

package-iso: builds the iso file

So... given all of the above, I think that the right place to put the steps is:

Download necessary files in Dockerfile.dapper - that is our build environment
Do installations in iso in package-iso - that is what is responsible for packaging stuff into the ISO format.

Is that correct?

PR in. Ball in your court, @ibuildthecloud

+1
EFI boot would be nice.

@pwFoo PR is in and ready to run. That will, at least, get the live iso to boot on EFI. Once someone gets ros install working on v0.5, then we can get the local install bootable on EFI as well.

Once someone gets ros install working on v0.5, then we can get the local install bootable on EFI as well

Are you saying that your PR will allow me to boot Rancheros from a USB drive using UEFI, but once there I won't be able to install it onto the internal HD in a way that will allow me to boot the new internal install using UEFI?

Just about @jeff-h. I can get that working as well. But I was stuck on two things:

ros install was not working.
The first step - making it work off of a live cd/usb which is the PR - was open as a PR.

I didn't want to put the extra effort of getting the second step - local install - working until the effort for the first step paid off (PR merged). And I couldn't until ros install worked.
It looks like ros install might be working. If so, once they merge the PR, I will look at getting local install to work in between client work.
I'm a little hesitant, since the effort for the first step doesn't appear to have been accepted and used, but if it gets merged, I will look at it.

I think I've blurred my comments on this issue and the PR, sorry! My question asking if you "have any suggestions for how I could use your ISO to actually install a usable RancherOS onto my little PC?" actually belongs here, I think.

I'm doing this all on my iPhone over 3G, so I couldn't tell you where anything goes!
Sorry, no suggestions. I know how to do it, but haven't put in the effort yet.
I love the idea behind rancheros, which is why I put the effort on. I have a secure appliance OS build; I would look quite seriously at merging the security into rancheros and use it if I felt that the effort would get merged.

@joshwget @SvenDowideit @ibuildthecloud so... we getting this one back in?

yes. I need to finish up #1361 first tho (and then go out and buy some ssd's for my ARM build boxes.

I need to finish up #1361 first tho (and then go out and buy some ssd's for my ARM build boxes

I am all for good toys and new build environments, but why does that need to finish first? We know the issues (see the PR), let's get it working conditionally (Intel only, no EFI on ARM), then we can add a PR to get EFI working on ARM. (then we can get ros install working with EFI...)

Just surprised at the complexity. The merge happened very quickly once we decided to do it. Granted, we had to back it out because we didn't think about ARM, but we can add the exception case there, like @ibuildthecloud suggested.

basically, it happened very quickly because we didn't have a trivial build system that let us quickly build&test on all 3 HW platforms - my goal for this week is to change that at minimum for amd64...

There was no automated CI for all potential deployment platforms? Ouch.
Once that is in place, I will be able to submit a PR, and the entire system with the PR as if it had been merged will be run on all targets and report before we accept the merge?
Love it! This kind of building platforms is just fun. I am doing something similar with a company, although it is more software, so simpler.
Which CI system are you using?

all 3 HW platforms

3?
Either way, will you comment here when ready so I can resubmit the PR and get it in?

don't wait for me - make the PR, and it'll get built as soon as things look like they might hold together :)

OK @SvenDowideit but...

I am traveling the next week or so, and have been doing this on a Linux machine I have, so it will have to wait until I am back
It will get merged in, right? Once it passes tests? I don't like putting work in that goes nowhere.

Is there any update on this?

@Xe when Rancher and @SvenDowideit are ready for it (committed to putting it in), I will redo it (or Sven will?). After having done the work and getting it a year ago (pre-0.6) and it went nowhere, reluctant to put in even a few minutes unless I know it will go in.

+1 on this one.  Would love to see it added.

+1 for this feature to be added

[Trump]Still no (u)EFI support? So sad[/Trump]

+1 immediately.
I need to boot into RancherOS in my Ockel Sirius B Black Cherry. It doesn't support legacy mode so I need to boot in EFI mode soon.


Sample Headers and date type?

Is there a way to generate sample headers for response?
Also, I had to change my spec to use date-time instead of date which is a valid format. It throws an exception unknown generator for "date". Is there a way to inject a custom generator?

You can generate samples for any parameter or response.  If you have a header parameter, you can generate a sample.  There is no way to generate a sample header for a response but we could possibly support it.
As for date, date and date-time are valid formats when type: string.  As for right now, we do not expose any way to register a custom format because we only support the formats OpenAPI/Swagger supports.  I'm not even sure you can specify a different format but if you can, we should support registering custom generators.

This is what I have in spec:
```

dateOfBirth:
type: string
format: date

and I get this expection : `unknown generator for "date" in /properties/applicantResponse/properties/dateOfBirth`

If I change the format to date-time, I am able to execute it successfully. So am not sure `date` is supported or am I doing something wrong?

It looks like date isn't a JSON Schema format so we'll need to add this to the custom generators.  We already support some custom generators (https://github.com/apigee-127/sway/blob/master/lib/validation/format-generators.js) and it looks like we'll be adding another one.

I'm closing this issue since it was really two issues merged into one.  I will link this issue with the newly created issue.


BUG: Fix crash in registering markups displ. man. when connecting to device

When registering the markups displayable manager, and then it creates widgets for the existing markups, it wants to use the application logic to get the markups logic, which it is supposed to get from the factory, but since in the factory it was not set, getting the markups logic failed in absence of the application logic and it caused a crash. Fixed by setting the application logic directly.

@cpinter Thanks for the contribution :pray:
I amended the commit to keep the line endings and add a check like what was done in SlicerVirtualReality extension.

Makes sense, thank you!
On Wed, May 18, 2022, 18:56 Jean-Christophe Fillion-Robin <
@.***> wrote:

Merged #21 https://github.com/KitwareMedical/SlicerLookingGlass/pull/21
into master.
—
Reply to this email directly, view it on GitHub
https://github.com/KitwareMedical/SlicerLookingGlass/pull/21#event-6634483402,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAKDXHBA3MMGQXWYWBJT463VKUVNRANCNFSM5WJAEDRA
.
You are receiving this because you were mentioned.Message ID:
@.***
com>


Discussion for API authentication and Identity Server

Some of you may have noticed that the Identity Server integration is now in the master branch along with a sample on how it all hangs together.
This issue is meant to centralize feedback as much as possible, so let's first discuss what this feature is aimed at and its limits

The feature will appear as an authorization option for API and SPA templates where you require Individual Authentication with a local database.
This will not appear as an option for MVC or Razor Pages applications, those will continue as is for now.
It is meant as a simple starting point, supporting APIs and first party clients.
It uses conventions to register the clients and apis without the need for configuring Identity Server beyond the helper methods in ConfigureServices()

            services.AddDbContext<ApplicationDbContext>(options =>
                options.UseSqlite(Configuration.GetConnectionString("DefaultConnection")));

            services.AddDefaultIdentity<ApplicationUser>()
                .AddEntityFrameworkStores<ApplicationDbContext>();

            services.AddIdentityServer()
                .AddApiAuthorization<ApplicationUser, ApplicationDbContext>();

            services.AddAuthentication()
                .AddIdentityServerJwt();

It still uses ASPNET Identity for the user database, and thus requires EF.
It will not support any advanced usage of Identity Server, like federation, WS-Fed, client certificates etc. although nothing will stop you migrating to those should you require them, you just have to abandon the helper functions and go full throttle with Identity Server's configuration system.
We'll be examining service to service authentication at some point.

So, have at it.

We'll be examining service to service authentication at some point.

Please do


[Enhancement] Method invocation may produce 'NullPointerException'[MessageUtils]

Search before asking

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

Enhancement Request

located at:
eventmesh-sdk-java/src/main/java/org/apache/eventmesh/client/tcp/common/MessageUtils.java line 97,102
Describe the solution you'd like
e.g.

Are you willing to submit PR?

[ ] Yes I am willing to submit a PR!

created pull request for #3096; I commit changes for this there.

created pull request for #3096; I commit changes for this there.

No changes were found in https://github.com/apache/eventmesh/pull/3135 to fix this issue. This issue is unfixed and open for contribution.

@Pil0tXia
This seems like an easy job, I wonder if I could be assigned it? 🫣

@cnzakii Of course


Fix #15665

Please make sure to label your PR with "bug", "new feature" or "breaking change" label(s).
To prevent this PR from going to the changelog marked it with the "skip changelog" label.

Snapshot stored with reference name:
refs/pull/15666/merge
Test environment:
https://snapshots-cvgtc2eugrd3cgfd.z01.azurefd.net/refs/pull/15666/merge/index.html
To test a playground add it to the URL, for example:
https://snapshots-cvgtc2eugrd3cgfd.z01.azurefd.net/refs/pull/15666/merge/index.html#WGZLGJ#4600
Links to test babylon tools with this snapshot:
https://playground.babylonjs.com/?snapshot=refs/pull/15666/merge
https://sandbox.babylonjs.com/?snapshot=refs/pull/15666/merge
https://gui.babylonjs.com/?snapshot=refs/pull/15666/merge
https://nme.babylonjs.com/?snapshot=refs/pull/15666/merge
To test the snapshot in the playground with a playground ID add it after the snapshot query string:
https://playground.babylonjs.com/?snapshot=refs/pull/15666/merge#BCU1XR#0

Visualization tests for WebGPU (Experimental)
https://snapshots-cvgtc2eugrd3cgfd.z01.azurefd.net/refs/pull/15666/merge/testResults/webgpuplaywright/index.html


Tagging of artifacts needs to be investigated and improved

We don't have a good release strategy for this project and the versioning "tag" seems arbitrary.
Describe the solution you would like

[ ] Release process is documented in CONTRIBUTING.md
[ ] Appropriate tagging/release strategy is chosen (TBD)
[ ] Appropriate tags are used for all artifacts (TBD)

This is now handled by the auto release process


cannot find vaccum

Hello,
I am having an issue with the homebridge unable to find the vacuum i have setup everything correct, any ideas why it won't discover the vacuum?
[2023-01-10, 9:54:48 p.m.] [Robo] [Model=unknown] getSerialNumber | No vacuum cleaner is discovered yet.
[2023-01-10, 9:54:48 p.m.] [Robo] [Model=unknown] INF ensureDevice | unknown model | The socket was destroyed or not initialised, initialising the device
[2023-01-10, 9:54:48 p.m.] [Robo] [Model=unknown] getFirmware | No vacuum cleaner is discovered yet.
[2023-01-10, 9:54:48 p.m.] [Robo] [Model=unknown] INF ensureDevice | unknown model | The socket was destroyed or not initialised, initialising the device
[2023-01-10, 9:54:48 p.m.] [Robo] [Model=unknown] getCleaning | Failed getting the cleaning status. Error: Not connected yet
at DeviceManager.get device [as device] (/usr/lib/node_modules/homebridge-xiaomi-roborock-vacuum/src/services/device_manager.ts:86:13)
at DeviceManager.property (/usr/lib/node_modules/homebridge-xiaomi-roborock-vacuum/src/services/device_manager.ts:92:17)
at DeviceManager.get state [as state] (/usr/lib/node_modules/homebridge-xiaomi-roborock-vacuum/src/services/device_manager.ts:73:17)
at DeviceManager.get isCleaning [as isCleaning] (/usr/lib/node_modules/homebridge-xiaomi-roborock-vacuum/src/services/device_manager.ts:77:43)
at MainService.getCleaning (/usr/lib/node_modules/homebridge-xiaomi-roborock-vacuum/src/services/main_service.ts:108:45)
at On.getHandler (/usr/lib/node_modules/homebridge-xiaomi-roborock-vacuum/src/services/main_service.ts:38:25)
at On. (/usr/lib/node_modules/homebridge/node_modules/hap-nodejs/src/lib/Characteristic.ts:2399:32)
at step (/usr/lib/node_modules/homebridge/node_modules/tslib/tslib.js:144:27)
at Object.next (/usr/lib/node_modules/homebridge/node_modules/tslib/tslib.js:125:57)
at /usr/lib/node_modules/homebridge/node_modules/tslib/tslib.js:118:75
[2023-01-10, 9:54:48 p.m.] [Robo] [Model=unknown] getSpeed | No vacuum cleaner is discovered yet.
[2023-01-10, 9:54:48 p.m.] [Robo] [Model=unknown] INF ensureDevice | unknown model | The socket was destroyed or not initialised, initialising the device

Same here:
Homebridge v18.12.1 (Syno Docker, 'Homebridge Fritz Platform' as the only other plugin working fine)
homebridge-xiaomi-roborock-vacuum v0.28.1
Model: rockrobo.vacuum.v1 (FW 3.3.9_003502, itself working via seamlessly Xiaomi Home app (iOS)
Token and IP double-checked and correct
[1/12/2023, 7:44:31 PM] [Xiaomi Mi Robot] [Model=unknown] getSpeed | No vacuum cleaner is discovered yet.
[1/12/2023, 7:44:31 PM] [Xiaomi Mi Robot] [Model=unknown] INF ensureDevice | unknown model | The socket was destroyed or not initialised, initialising the device
[1/12/2023, 7:44:31 PM] [homebridge-xiaomi-roborock-vacuum] This plugin threw an error from the characteristic 'On': Unhandled error thrown inside read handler for characteristic: Not connected yet. See https://homebridge.io/w/JtMGR for more info.
[1/12/2023, 7:44:31 PM] [homebridge-xiaomi-roborock-vacuum] This plugin threw an error from the characteristic 'Filter Change Indication': Unhandled error thrown inside read handler for characteristic: Not connected yet. See https://homebridge.io/w/JtMGR for more info.
[1/12/2023, 7:44:31 PM] [homebridge-xiaomi-roborock-vacuum] This plugin threw an error from the characteristic 'Filter Life Level': Unhandled error thrown inside read handler for characteristic: Not connected yet. See https://homebridge.io/w/JtMGR for more info.
[1/12/2023, 7:44:31 PM] [homebridge-xiaomi-roborock-vacuum] This plugin threw an error from the characteristic 'Status Low Battery': Unhandled error thrown inside read handler for characteristic: Not connected yet. See https://homebridge.io/w/JtMGR for more info.
[1/12/2023, 7:44:31 PM] [homebridge-xiaomi-roborock-vacuum] This plugin threw an error from the characteristic 'Battery Level': Unhandled error thrown inside read handler for characteristic: Not connected yet. See https://homebridge.io/w/JtMGR for more info.
[1/12/2023, 7:44:31 PM] [homebridge-xiaomi-roborock-vacuum] This plugin threw an error from the characteristic 'Charging State': Unhandled error thrown inside read handler for characteristic: Not connected yet. See https://homebridge.io/w/JtMGR for more info.
[1/12/2023, 7:44:31 PM] [homebridge-xiaomi-roborock-vacuum] This plugin threw an error from the characteristic 'Occupancy Detected': Unhandled error thrown inside read handler for characteristic: Not connected yet. See https://homebridge.io/w/JtMGR for more info.
[1/12/2023, 7:44:31 PM] [homebridge-xiaomi-roborock-vacuum] This plugin threw an error from the characteristic 'Filter Change Indication': Unhandled error thrown inside read handler for characteristic: Not connected yet. See https://homebridge.io/w/JtMGR for more info.
[1/12/2023, 7:44:31 PM] [homebridge-xiaomi-roborock-vacuum] This plugin threw an error from the characteristic 'Filter Life Level': Unhandled error thrown inside read handler for characteristic: Not connected yet. See https://homebridge.io/w/JtMGR for more info.
[1/12/2023, 7:44:31 PM] [homebridge-xiaomi-roborock-vacuum] This plugin threw an error from the characteristic 'Filter Change Indication': Unhandled error thrown inside read handler for characteristic: Not connected yet. See https://homebridge.io/w/JtMGR for more info.
[1/12/2023, 7:44:31 PM] [homebridge-xiaomi-roborock-vacuum] This plugin threw an error from the characteristic 'Filter Life Level': Unhandled error thrown inside read handler for characteristic: Not connected yet. See https://homebridge.io/w/JtMGR for more info.
[1/12/2023, 7:44:31 PM] [homebridge-xiaomi-roborock-vacuum] This plugin threw an error from the characteristic 'Filter Change Indication': Unhandled error thrown inside read handler for characteristic: Not connected yet. See https://homebridge.io/w/JtMGR for more info.
[1/12/2023, 7:44:31 PM] [homebridge-xiaomi-roborock-vacuum] This plugin threw an error from the characteristic 'Filter Life Level': Unhandled error thrown inside read handler for characteristic: Not connected yet. See https://homebridge.io/w/JtMGR for more info.
[1/12/2023, 7:44:31 PM] [homebridge-xiaomi-roborock-vacuum] This plugin threw an error from the characteristic 'Filter Change Indication': Unhandled error thrown inside read handler for characteristic: Not connected yet. See https://homebridge.io/w/JtMGR for more info.
[1/12/2023, 7:44:31 PM] [homebridge-xiaomi-roborock-vacuum] This plugin threw an error from the characteristic 'Filter Life Level': Unhandled error thrown inside read handler for characteristic: Not connected yet. See https://homebridge.io/w/JtMGR for more info.
[1/12/2023, 7:44:33 PM] [Xiaomi Mi Robot] [Model=unknown] ERR connect | miio.device, next try in 2 minutes | Error: Could not connect to device, handshake timeout
[1/12/2023, 7:44:33 PM] [homebridge-xiaomi-roborock-vacuum] This plugin threw an error from the characteristic 'Rotation Speed': Unhandled error thrown inside read handler for characteristic: Could not connect to device, handshake timeout. See https://homebridge.io/w/JtMGR for more info.

@nail299 from your comment... am I right to assume you use a fritz! router?
For some reason, they are very picky with UDP packets and filter treat them in a way that breaks this plugin (that uses UDP to communicate with the router).
Can you look into the configuration of your router to see if there's a way to allow those UDP packets to flow in your network?

For the Fritz routers, please refer to #444. I'll go ahead and close this one as duplicate.


The "Read All" Link doesn't seem to work

Describe the bug
The "Read All" link from the sidebar leads to an empty page
To reproduce
Visible in the demo site:

https://www.drassil.org/git-wiki/blog/
Read All link, goes to https://www.drassil.org/git-wiki/blog/

Expected behavior
A list of all Posts
Screenshots

Thank you for your report
I've fixed it in latest version. Please, update your _config.yml with following 2 changes:
https://github.com/Drassil/git-wiki-theme/commit/ad95f616560f2f02f948d79e1aa26a0a1d8c74d6
https://github.com/Drassil/git-wiki-theme/commit/b8326b1400db850fb4142d569f095a33465aa5c6


Fix status for publish/conda

https://github.com/energy-quants/.github/blob/0fb509d54ddc7fdfca4c8c79d686d22de3687fe3/.github/workflows/publish-conda.yml#L56
The status should be set on commits to main as well so they have a link to the publish workflow.


Improve/fix Home Assistant MQTT integration

Could you please make small addition in your code so Home Assistant (HA) integration via internal HA MQTT Mosquitto broker works properly? The current version of miflora-mqtt-daemon allows only partial integration because of missing information in MQTT data which is sent by miflora-mqtt-daemon resulting in partial plant sensor visibility and HA GUI warnings like "This entity does not have a unique ID, therefore its settings cannot be managed from the UI"...
Goals:
The main goal of this request is to have each Miflora Plant sensor visible under Mosquitto broker as a separate HA Device with its Entities/Sensors (temperature, moisture, conductivity, light intensity, battery).  Result:

Another goal is to be able to place miflora sensor into HA "Areas". This requires the main goal to be implemented (miflora sensor needs to be visible as Device in HA not as separate entities/sensors).
Result:

Explanation:
According to HA MQTT Sensor Discovery (https://www.home-assistant.io/integrations/sensor.mqtt/) miflora-mqtt-daemon should also send sensor's  "unique_id" along with it's "parent device" information (identifiers, connections, firmware, ... ) configuration variables.
After that, the discovered MQTT sensor is added automatically into HA Device Registry (https://developers.home-assistant.io/docs/device_registry_index/) and visible in HA GUI.
Tested patch which needs to be merged:
diff --git a/miflora-mqtt-daemon.py b/miflora-mqtt-daemon.py
index 1209779..096c5d3 100755
--- a/miflora-mqtt-daemon.py
+++ b/miflora-mqtt-daemon.py
@@ -307,6 +307,15 @@ elif reporting_mode == 'homeassistant-mqtt':
             payload['name'] = "{} {}".format(flora_name, sensor.title())
             if 'device_class' in params:
                 payload['device_class'] = params['device_class']
+            payload['unique_id'] = "%s-%s" % ( flora['mac'].lower().replace(":", ""), sensor, )
+            payload['device'] = {
+                    'identifiers': [ "MiFlora{}".format( flora['mac'].lower().replace(":", "") )],
+                    'connections': [[ "mac", flora['mac'].lower() ]],
+                    'manufacturer': 'Xiaomi',
+                    'name': flora_name,
+                    'model': 'HHCCJCY01',
+                    'sw_version': flora['firmware']
+                    }
             mqtt_client.publish('{}/{}_{}/config'.format(topic_path, flora_name, sensor).lower(), json.dumps(payload), 1, True)
 elif reporting_mode == 'wirenboard-mqtt':
     print_line('Announcing Mi Flora devices to MQTT broker for auto-discovery ...')

Thank you!
PS: In case no new Miflora devices are visible in your HA after patching miflora-mqtt-daemon, try restarting HA.

Hey @bangom,
thanks for this. I'll patch this in the next 1-3 days.
Out of personal interest: Where does your miflora-mqtt-daemon run, on a normal Linux machine or inside docker on a raspberry pi with Hass.io?

Great, should I create git pull request or attached patch is enough?
I'm running miflora-mqtt-daemon on multiple separate raspberrypi-zero
devices which work as btle gateways for nearby miflora sensors. Hass.io is
on a separate central device.
I'm also thinking to enhance miflora-mqtt-daemon with passive btle readings
by default (each miflora broadcasts everything except battery status
multiple times per minute) which will save miflora batteries in long-term
use. Active btle pooling only few times per day for battery status. Passive
btle Miflora reading, see ESPhome or HA component sensor.mitemp_bt.
Miflora-mqtt-daemon would be first to combine passive and active (battery
status) reading.
po 23. 3. 2020 v 15:38 odesílatel Thomas Dietrich<EMAIL_ADDRESS>napsal:

Hey @bangom https://github.com/bangom,
thanks for this. I'll patch this in the next 1-3 days.
Out of personal interest: Where does your miflora-mqtt-daemon run, on a
normal Linux machine or inside docker on a raspberry pi with Hass.io?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/ThomDietrich/miflora-mqtt-daemon/issues/101#issuecomment-602635428,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AKBL3AEL4EGOP3BBEFIC7RDRI5X4ZANCNFSM4LRODVTQ
.

--
Moris Bangoura

Just recently I gave Home Assistant a chance and tested the built-in miflora integration. I am not happy with it and will continue to use the miflora-mqtt-daemon. I was thinking to build a Dockerfile to provide a Hassio add-on.
Regarding your patch: I could commit it but please open a pull request and the contribution will be in your name ;)

Regarding passive reading:

I wasn't aware of that. Did you bring it up in the miflora library repository? Ideally we should try to contribute this kind of addition there.
I found that a polling rate of even 30min will not drain the battery fast enough for me to really care about the issue. Especially as the battery level itself is known and can be used to trigger a "please change battery" notification.

Just recently I gave Home Assistant a chance and tested the built-in miflora integration. I am not happy with it and will continue to use the miflora-mqtt-daemon. I was thinking to build a Dockerfile to provide a Hassio add-on.
Regarding your patch: I could commit it but please open a pull request and the contribution will be in your name ;)

I'm not saying that HA sensor.mitemp_bt is best solution. For example for me, this approach is not feasible because I need multiple miflora btle gateways running outside of hass.io device to cover large area.
But passive Miflora reading can be usable, increase coverage, improve communication and also fix some problems like inaccurate light reading because of blinking led during active btle communication (https://github.com/open-homeautomation/miflora/issues/136). I will suggest this in miflora library repo.
Of course, Dockerfile can be usable in some deployments.
Pull request finished :)

OK, merged pull works OK. Thanks!
You can also update main readme so it says, latest 3.2.1 firmware is working (also Vegtrug sensors -with MAC prefix "80:EA:CA").
Just from curiosity, why did you change MQTT topic structure for home-assistant?? Now each sensor from Miflora is advertised straight in homeassistant/sensor/ level. Also state topic moved from /homeassistant/sensor/flora_name/state to /homeassistant/sensor/flora_name.
IMHO if you have a lot of Miflora sensors, you don't want to have each sensor (lux, temp, ...) as separate topic under homeassistant/sensor/ but rather grouped under common Miflora device.
This also supports HA documentation (https://www.home-assistant.io/docs/mqtt/discovery/):
Recommended MQTT HA structure is: <discovery_prefix>//[<node_id>/]<object_id>/config, where:

<discovery_prefix> = homeassistant
= sensor
<node_id> = flora_name variable from your script
<object_id> = a flora sensor (flora_name_light, flora_name_moisture, ...).

Hey!
Thanks for your continued comments!
I've added the firmware version info.

Just from curiosity, why did you change MQTT topic structure for home-assistant??

The code had an issue with the base topic even before your Pull Request. I believe communication is better structured when announcements appear under homeassistant/# topics but actual data under a clean miflora/# structure. I fixed that and "tuned" the topics while doing so. I adopted the topic structure from Tasmota devices in my network and while I was surprised that the structure is homeassistant/sensor/devicename_Humidity/config I might have thought this is as it is intended. You are of course right, we should fix this here.

Also state topic moved from /homeassistant/sensor/flora_name/state to /homeassistant/sensor/flora_name.

For me it is miflora/sensor/flora_name and I left the "state" part out as it is kind of redundant. Now I can see the this is also part of the Home Assistant discovery definition. I'll re-add it. (Even though documentation hints that this "automatic setting of state_topic is deprecated")

<object_id> = a flora sensor (flora_name_light, flora_name_moisture, ...).

The documentation is a bit unclear here imho. I believe we can leave out the redundant flora_name. Wdyt?
Btw. feel free to finalize your help here by adding miflora-mqtt-daemon under https://www.home-assistant.io/docs/mqtt/discovery/#support-by-third-party-tools

Hey!
Thanks for your continued comments!
I've added the firmware version info.

Just from curiosity, why did you change MQTT topic structure for home-assistant??

The code had an issue with the base topic even before your Pull Request. I believe communication is better structured when announcements appear under homeassistant/# topics but actual data under a clean e.g. miflora/# structure (it's logically not part of the home assistant domain, if you know what I mean). I fixed that and "tuned" the topics while doing so. I adopted the topic structure from Tasmota devices in my network and while I was surprised that the structure is homeassistant/sensor/devicename_Humidity/config I might have thought this is as it is intended without even looking at documentation. You are of course right, adding an optional node_id is useful and we should fix that.

<object_id> = a flora sensor (flora_name_light, flora_name_moisture, ...).

The documentation is a bit unclear here imho. I believe we can leave out the redundant flora_name. Wdyt?

Will HA generate sensor names correctly? In your example if you have Plant01 Miflora sensor advertising via miflora-mqtt-daemon, then you will have
MQTT:
homeassistant/sensor/plant01/light
homeassistant/sensor/plant01/conductivity
...
From HA point of view, autogenerated name of the sensor is light, conductivity...  so we will have sensors:
sensor.light
sensor.conductivity
(not sure if good thing will happen when adding another Miflora device...)
My proposition:
MQTT:
homeassistant/sensor/plant01/plant01_light
homeassistant/sensor/plant01/plant01_conductivity
...
HA sensor autogenerated names:
sensor.plant01_light
sensor.plant01_conductivity

Also state topic moved from /homeassistant/sensor/flora_name/state to /homeassistant/sensor/flora_name.

For me it is miflora/sensor/flora_name

This is good idea, will divide miflora mqtt topics configuration in the same manner. In feature we can add there for example miflora-mqtt-daemon distributed configuration of "slave daemons"  #35 .

and I left the "state" part out as it is kind of redundant. Now I can see the this is also part of the Home Assistant discovery definition. I'll re-add it. (Even though documentation hints that this "automatic setting of state_topic is deprecated")
Did a direct commit instead of creating a PR branch. Commit: 04e43f2
Btw. feel free to finalize your help here by adding miflora-mqtt-daemon under https://www.home-assistant.io/docs/mqtt/discovery/#support-by-third-party-tools

OK, will do that when we finalize this improvement.

Will HA generate sensor names correctly?

I believe so. Check this out: https://github.com/home-assistant/core/issues/10220
The name field from your PR is used as the entity_id. Why HA installation works with the latest version of this daemon

In feature we can add there

Believe it or not, that is why even though I removed "/state" initially, I left "/sensor/" in. For #35 I envision "miflora/config/..."

``

Will HA generate sensor names correctly?

I believe so. Check this out: home-assistant/core#10220
The name field from your PR is used as the entity_id. Why HA installation works with the latest version of this daemon

Good point, homeassistant/sensor/plant01/light is OK then.
Thanks for re-checking.

In feature we can add there

Believe it or not, that is why even though I removed "/state" initially, I left "/sensor/" in. For #35 I envision "miflora/config/..."

Great, looking forward to seeing your idea of #35.


Greenshot and Fancyzones struggle with one option in Fancyzones

Microsoft PowerToys version
0.35.0
Running as admin
Yes
Area(s) with issue?
FancyZones
Steps to reproduce
Use Greenshot and enable the Option to move new Windows in Zones in Fancyzones
Press Print on Keyboard to make a Screenshot with Greenshot
Youtube Video demonstration: https://www.youtube.com/watch?v=G39GReaNFyk
I didnt find this Bug in Issues. If i double post it, close it.
✔ Expected Behavior
You can make a Screenshot
❌ Actual Behavior
The Monitor moves down
Youtube Video demonstration: https://www.youtube.com/watch?v=G39GReaNFyk
Workaround: disasble "move Windows in known zones"
Other Software
No response

@corincorvus
what version of Greenshot are you using.
Users reported compatibility problems in the past but then it seemed they were resolved https://github.com/microsoft/PowerToys/wiki/Application-Compatibility#screen-capture-software


Create fork merge documentation

Let's have a documentation page with steps on how to merge main Spack into our fork. This would also be a good place to inventory known differences between our fork and the upstream (container stuff, binary relocation stuff, provider hashes in module directory hierarchy, etc.).

@AlexanderRichert-NOAA Going through old issues, is this something you still want to do?

Yes, I'll try to do this next time we do an upstream merge.

Thanks @AlexanderRichert-NOAA!

@AlexanderRichert-NOAA Do you want to do this on the release/1.6.0 branch or postpone to 1.7.0?

Postpone

Postpone

Thanks, done!

We seem to be doing fine without documentation here, so I'm going to close for now and we can reopen later if needed.


[Enhancement] Get Current Window

I want to talk with you about "Get Current Window", we can implement through python native libs in picture below, but not rf-flaui method. What about your idea @Nepitwin

@JimRevolutionist
That there may be an implementation in this regard is of course true. However, this is of course another way how you can integrate small own keywords for yourself in the robot framework.
That this functionality is offered via the Robotframework-FlaUI I do not see because it then implements different approaches for test automation.
The approach could be implemented on C# level of the FlaUI in the lib and then offer this.
This is a great strength of the Robotframework that you can quickly and flexibly integrate keywords on Python base. But mixing of many libraries leads in the end to long-term problems from my point of view even if the source code looks very small and simple.


Select all order not respected

When choosing the select all order it doesn't actually select them in the correct order, making each of the frames export in the proper order. Tried with numerous sprite sheets. The order seems all over the place. Top left may export 1, 0, 4, 3, etc.

It's been a long time, I forgot I made this post, but I did end up fixing this, atleast for top left ONLY (selectAllOrder is completely ignored). This will force the order to top left down no matter what.  Obviously, this isn't optimal, but it gets the job done.
Just change OrderBoxes to the following and compile.:
public static List<Rectangle> OrderBoxes(List<Rectangle> boxes, Enums.SelectAllOrder selectAllOrder, Size spriteSheetSize)
        {
            List<List<Rectangle>> listsOfBoxes = new List<List<Rectangle>>();
            bool found = false;

            List<Rectangle> returnedOrder = boxes.OrderBy(w => w.Y + w.Height).ToList();
            foreach (Rectangle box in returnedOrder)
            {
                foreach (Rectangle compareBox in returnedOrder)
                {
                    // Find a rect on the same Y axis.
                    if (box.Top < compareBox.Bottom && box.Bottom > compareBox.Top)
                    {
                        found = false;
                        // Look for a list containing the matched rect.
                        foreach (List<Rectangle> groupedList in listsOfBoxes)
                        {
                            // Add our rect to a list we found.
                            if (groupedList.Contains(compareBox))
                            {
                                groupedList.Add(box);
                                found = true;
                                break;
                            }
                        }

                        // No list was found, create a new list and put the rect in it.
                        if (found == false)
                        {
                            List<Rectangle> newList = new List<Rectangle>();
                            listsOfBoxes.Add(newList);

                            newList.Add(box);
                        }
                        // We found a rect, stop searching for others.
                        break;
                    }
                }
            }

            // Begin to sort all of the lists by the X axis and dump into a single list.
            List<Rectangle> properOrder = new List<Rectangle>();

            foreach (List<Rectangle> groupedList in listsOfBoxes)
            {
                List<Rectangle> orderedList = groupedList.OrderBy(w => w.X).ToList();
                properOrder.AddRange(orderedList);
            }

            return properOrder;
        }


[cxx-interop] add a build setting to control whether the <swift/bridg…

…ing> header is shipped with compiler
rdar://109050483
Explanation:
Right now <swift/bridging> header is always shipped with the compiler. However, there exit certain build configurations where this header should not be shipped. Therefore, this change adds a new CMake and build script setting that allows the users and/or custom build preset to prevent the <swift/bridging> header from being shipped with the compiler.
Scope: CMake, build script , Swift's and C++ interoperability <swift/bridging> header
Risk: Low.
Testing: Swift build script unit tests, build toolchain, manual testing of the new flag.
PR: https://github.com/apple/swift/pull/65781

@swift-ci please test

@swift-ci please build toolchain


Support geopos command

Added missing GEOPOS command.
But I'm not sure about part of code below, redis could produce "nil" as element of array response. If there are another solution tell me
// response may contain nil results
if err == Nil {
    positions = append(positions, nil)
    continue
}

Overall looks good - thanks. I am going to tweak it in separate branch before releasing.

Released v4.1.4


error 500 when opening https://tvr-decoder.appspot.com/

the app is responding the url with error 500.
Should you need any other info, i'd be glad to help.

@wcurrie yeah this was the far best decoder out there.
Do you have any instructions on how to run in locally?
Unfotunately it does not use spring boot =(
Any plans on putting this up again?


Guake theme

Guake Terminal is one popular top-down terminal for Gnome. Would you like to add supports for it. Thanks!

Nord Guake is already available as a official port project 😄

Great! I did not notice it.

No problem, I try to keep the port project section up-to-date to make it easy for users to find available projects, but there are also plans for a project website with a nice presentation of all available ports.