Any image? I won't install it if it not cool

Any image? I won't install it if it not cool

You can customize it to your own style. For more details, see Configuration.


Assist Microphone - Unexpected error

Hi ! 👋
I just tried to install and use the addon Assist Microphone but got an "Unexpected error"
Here are the logs I get when I start the addon :
ERROR:__main__:Unexpected error
Traceback (most recent call last):
  File "/usr/local/lib/python3.11/dist-packages/homeassistant_satellite/__main__.py", line 200, in main
    async for _timestamp, event_type, event_data in stream(
  File "/usr/local/lib/python3.11/dist-packages/homeassistant_satellite/remote.py", line 28, in stream
    async with session.ws_connect(url) as websocket:
  File "/usr/local/lib/python3.11/dist-packages/aiohttp/client.py", line 1141, in __aenter__
    self._resp = await self._coro
                 ^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/dist-packages/aiohttp/client.py", line 779, in _ws_connect
    resp = await self.request(
           ^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/dist-packages/aiohttp/client.py", line 560, in _request
    await resp.start(conn)
  File "/usr/local/lib/python3.11/dist-packages/aiohttp/client_reqrep.py", line 899, in start
    message, payload = await protocol.read()  # type: ignore[union-attr]
                       ^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/dist-packages/aiohttp/streams.py", line 616, in read
    await self._waiter
aiohttp.client_exceptions.ServerDisconnectedError: Server disconnected

Nothing else and it just repeats this over and over.
I run HA on a RP4 with Home Assistant OS.
Happy to provide more information if needed as I am kind of stuck 😞
Thanks for your awesome work

I'm getting this also here : https://github.com/rhasspy/hassio-addons/issues/27

Please upgrade to 2.2.1 and try again. I'm getting the port/protocol from the supervisor API now.

Hi thanks for the updates, unfortunately it is still not working, I now have this error :
ssl.SSLCertVerificationError: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: Hostname mismatch, certificate is not valid for 'homeassistant'. (_ssl.c:992)

My installation is indeed not available with the host 'homeassistant'

@bourliam Can you update to 2.2.2 and let me know if it's fixed? I'm using the IP address now from core/info

I'm on 2.2.3 and am still encountering the same error as bourliam.  Hostname mismatch, cert not valid for 'homeassistant'

Do you have a self-signed certificate?

No, duckdns.  However, I seem to have solved my problem by filling in the
host field.  There is a suggestion below the field and since so many things
in home assistant require the FQDN:port, that's what I used.  I found after
several tries I had to omit the https and the port and then things began to
work with just servername.duckdns.org.  I think the help string in the
field should be very explicit about this.  After watching some youtube
videos I was left with the impression I should leave it blank, but then it
defaulted to homeassistant, which did not resolve.
On Tue, Oct 24, 2023 at 5:34 PM Michael Hansen @.***>
wrote:

Do you have a self-signed certificate?
—
Reply to this email directly, view it on GitHub
https://github.com/rhasspy/hassio-addons/issues/34#issuecomment-1778283213,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AFU3N55T2U7ZWJMFDXOTJHDYBBNAFAVCNFSM6AAAAAA6CE5DXSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONZYGI4DGMRRGM
.
You are receiving this because you commented.Message ID:
@.***>

Please try the official Assist Microphone add-on: https://github.com/home-assistant/addons/tree/master/assist_microphone


Iron out namespace labeling workflow for OSM monitoring

Currently, a namespace in OSM is configured for monitoring by adding the label openservicemesh.io/monitor=<ID> on the namespace. The ID is opaque and up to the user to specify. For ex, a user could deploy an OSM instance with an ID and use this ID to configure an OSM  instance to monitor the namespace.
A proposal to remove the ID and instead specify the namespace OSM deployed to is being discussed, in which case the label on the app namespace would be openservicemesh.io/monitor=<osm-namespace>.
This issue is to discuss the labeling workflow and decide on either of the two approaches to add a namespace to OSM's registry.

This is okay to close.


feat: add rn collapse component

Coverage decreased (-0.7%) to 95.628% when pulling 1d4d3e982f6391e5ac8fec0c80fd2469f81142fd on zhiyingzzhou:dev into 9b0b8b2676b5ffaa6d5d3478771b3051cb8c2bba on ZhonganTechENG:dev.


Crashing

So, it just crashes once you add the client log.

Ok well, nevermind, I found a more updated version you had however for some reason, the links took me too the older versions where it did crash, however 0.4.1 is the current working version. Thank you!

Hi! I just updated the link on reddit - was not the best idea to link it to a fixed version. Thanks for opening this issue!


[WIP] Read version stanza into Hbc::DSL::Version object

I've implemented a few of the methods outlined in #12827. I'll implement more as we decide on them.
Right now we delegate a lot of methods to to_s to avoid having to update a ton of casks in one go. We can remove the ones we don't want over time.

Alternatives to def_delegators include:

explicitly define all methods (redundant IMHO)
subclass String
delegate to to_s in method_missing


Uploading a file via chrome alert

Hi all,
We have a test case, where file a should be uploaded to server. Currently we have a button that opens a chrome alert and there user is suppose to choose a file.
How can I upload a file in UI like this?
Thanks.

Ok, I have managed to upload a file by entering path to the input directly. Can be closed!

 :-)
Thanks for letting me know 👍
Jan


Interval includes: discrepancy

Interval size is not consistent with Interval includes:
"This one is true"
(0.3 to: 1.2 by: 0.1) includes: 1.2.

"This one is false"
(0.3 to: 1.2 by: 0.1) anySatisfy: [:each | each = 1.2].

I like very much the definition of includes: from John Brandt, but things are not as consistent as possible.
Similarly, current definition of size can lead to an element greater than the stop bound:
"This is true..."
(0.3 to: 0.82 by: 0.01) anySatisfy: [:each | each > 0.82].

"But this is false because of range check"
(0.3 to: 0.82 by: 0.01) allSatisfy: [:each | (0.3 to: 0.82 by: 0.01) includes: each].

Should size be changed for accomodating the Float case ?
For example it could be in case of inexact arithmetic:
candidateSize := (stop - start / step) rounded.
step > 0
    ifTrue: [candidateSize * step + start < stop ifTrue: [^candidateSize + 1]]
    ifFalse: [candidateSize * step + start > stop ifTrue: [^candidateSize + 1]].
^candidateSize

Thanks for the bug report Nicolas. From the code history this is obviously of very long standing, but hasn't been reported before. This suggests it is not a common use case, and/or that impact is low. As such, although it would be nice to fix, any fix would have to be very carefully made so as not to significantly impact the performance of more mainstream cases. As Dolphin's VM is an interpreter, the lower layers of the class library need to remain "tight" to keep the system snappy.
I'll add some (skipped) tests to the system based on your examples to at least document the deficiency.

The 2nd example seems to be a common problem. I get the same incorrect results in Pharo 9.0 (build 1168), and in VW 8,3. Here is another expression of it with results from VW:
interval := (0.3d to: 0.82d by: 0.01d).
interval includes: interval asArray last. "false!"

Yes, this is neither specific to Dolphin, nor urgent. The strategies are the following:

let things as is and advertise that Interval of Float are not recommended and may behave surprisingly
try and fix the most inconsistent behaviors

In the 2nd option, we do not want to spoil the simplicity and efficiency of the most general case (Interval of Integer or eventually Fraction), so my recommandation would be to create a LimitedPrecisionInterval, and let to: and to:by: choose the adequate species. it's just a matter of testing is step hasLimitedPrecision or: [stop hasLimitedPrecision], and eventually start hasLimitedPrecision if the species dispatch is implemented in Interval class.
Note that stop has to be tested because of size... For example, following Interval is pathological, though containing no Float...
(1/5 to: 1.2 by: 1) includes: 6/5. "false"
(1/5 to: 1.2 by: 1) asArray last = (6/5). "true"
(1/5 to: 1.2 by: 1) asArray last > 1.2. "true - that's the problem"

I gave it a shot in Squeak
https://source.squeak.org/trunk/Kernel-nice.1376.diff
https://source.squeak.org/trunk/Collections-nice.925.diff
https://source.squeak.org/trunk/CollectionsTests-nice.351.diff

Yes, that seems like a good approach.


nested typecast via :: not handled

The :: syntax is a shorthand for CAST
A valid Postgresql expression such as
('x'||substr(md5(hostname),1,16))::bit(64)::bigint as id_,
results in a parse error.
The problem is that in JSqlParserCC.jjt, the repetition block for :: specifies zero or 1 occurrences
(that is, enclosed in square braces [ ... ])
The fix is to specify zero or more occurrences.
at line 2505 or so in JSqlParserCC.jjt, change the code from
[ "::" type=ColDataType() {
castExpr = new CastExpression();
castExpr.setUseCastKeyword(false);
castExpr.setLeftExpression(retval);
castExpr.setType(type);
retval=castExpr;
} ]
to
( "::" type=ColDataType() {
castExpr = new CastExpression();
castExpr.setUseCastKeyword(false);
castExpr.setLeftExpression(retval);
castExpr.setType(type);
retval=castExpr;
} )*
I rebuilt JSqlParser using
mvn package
and the revised code passes all tests.
The revised code parsers the statement, and the default SQL generator returns the :: sequence.

Could you provide a pull request?


Please fix the INFINITE loading of chunks!

I found an article on a paperMC thread:
`The issue looks to be the plugin WorldSchematics. From looking at your 2nd pastebin stack, this plugin is messing with BlockPopulators.
1.13 pretty much broke BlockPopulators in that trying to place a block at the edge of the chunk involved causes it's neighbor chunk to load. 1.14 compounds this behavior by going full async on chunk load/gen in vanilla.
In a nutshell, WorldSchematics is placing blocks in chunks that are loading/generating. This causes those neighbor chunks to load as well. Which since this plugin seems to be using custom generation blockpopulators has to populate those newly loaded chunks. But doing so causes those neighbors to load. Then those, too, have to be populated which causes even more chunk loads. Its a viscous cycle that started back in 1.13 for a few plugins but is now hurting every single world generation plugin that uses BlockPopulators.
Ultimately, what this all boils down to is the developer of that plugin needs to find a better way to populate chunks to not trigger infinite loads on 1.14`
Seems like using the current method may cause some issues. Using PlotSquared with this plugin is therefore impossible at the moment, as the queue will just get longer infinitly until the server crashes... Found at: https://github.com/PaperMC/Paper/issues/2244

I think this is the wrong project for this issue ticket?

No - the topic may be the same. It is about the problem with world generation, which is causing an infinite loop of loaded chunks for further updated lighting. Even when using /cleanlight 5 the queue will be at 40000 chunks after half an hour. We have a bot atm garbage collecting but thats no solution to the problem... I thought the above error would maybe contribute to the source of this problem. I am looking at the code at the moment.

Disable the light cleaning on chunkgen. It doesnt work as of 1.14 because the server generates too large amount of chunks around chunks loaded using chunk load tickets. There is also absolutely no point to enabling that feature on 1.14 because light glitches in chunk gen were also fixed around that version.
I have no plan to fix this.

And if its causing runaway chunk generation with that feature turned off, then this isnt a lightcleaner issue ticket at all, but something the chunk generator plugin or whatever should fix, instead.

There is a point with custom world generators. So you think this isnt your problem, but rather that from multiverse, or plotsquared or what....You plugin is not needed in the normal Version of minecraft, there is fixlight by paper, fawe etc. It is only needed, BECAUSE of the custom world generator. So you want your plugin to become obsolete in the future? And why is it that the plugin cant check if a chunk is a non-loaded chunk? The position shouldnt matter...
PlotSquared is stating to turn the mentioned setting ON - and the generator is coming from their end. Should I write a ticket at their plugin? I dont see how this is the Problem of plotsquared as this is also not working in my vanilla world on the same server...

I was not aware that custom chunk generator plugins still caused lighting glitches on chunkgen, so thats disappointing. I guess that feature will have to be fixed then, I guess.
You plugin is not needed in the normal Version of minecraft
people use it for FAWE.
there is fixlight by paper, fawe etc
Who have had various problems over the years while light cleaner carried on.
And why is it that the plugin cant check if a chunk is a non-loaded chunk?
It does.

Before you start throwing so many assumptions this way, Id like you to re-read the quoted part I posted earlier.
The server generates 9x9 chunks when a single chunk has a 'keep this chunk loaded' ticket created. Light cleaner gets a load ticket, operates on the chunk, and releases a ticket. This prompts the server to generate 9x9 more, neighbours fire population events, and so even more chunks are queued up into lightcleaner.
Lightcleaner does do a check to see if a 2-wide radius around chunks are already generated. Later on the server broke even that by generating 3 chunks away. I stopped trying to work with this horrible system and now tell people to turn that autofixing on chunkgen off.

Fundamentally here the problem is that it isnt possible to create a chunk load ticket and not generate the chunks around it.

Ok - so how is this solvable? If there is the possibility to check like you have been doing it, why not add an option to increase the range by yourself? Or did it hurt performance... I dont get why this big use case should be wasted, as FAWE has its own, working lighting system - even if it might not be as performant, it is at least working. This is not a state in which somebody with PlotSquared can use this plugin sadly, though I still contacted the authors. Hopefully this can get fixed at some end, maybe they will implement their own system. Who knows. It is only needed when the chunk is generated the first time, so maybe it is possible to make a function for that?

Several problems:

Performance is indeed impacted polling 24 chunks (or even more!) for every chunk to see if it exists on disk
It results in the edge of the world to have lighting glitches, something that players can see in the distance
Due to how populators work, it is very unpredictable when a runaway generation happens or not. In vanilla minecraft a good example is the mansion.

I was personally hoping to close this fix-on-gen chapter after 1.14 and leave light cleaner more as a relic for pre-1.14 and for worldwide operations. It would be better if PlotSquared worked with paper devs on a solution.

Thank you for the detailed explanation. It seems to be fixed by the means of PlotSquared-Developers - but the fix is not working with 1.16.5 as the newest versions only support Java 17 by now. Still seems like this isn't your Problem anymore and I thank you for your time - I might just have to update to newer Minecraft versions.


Please add adjustable hotkey settings

You can't have your mod installed and try running with ctrl+s key to drop items You end up activating the screen saver. I need to come up with a different key, than a movement key.

Did you get the mod from factorio mod portal? As far as I remember, hotkeys can already be adjusted via game settings (settings - controls - scroll down to mods)

Alright - strange - when I first had the mod loaded, I checked there first and hadn't seen it. Just loaded it again now, and the settings are there. Thanks, and sorry for the bother.


Carthage installation failed with --use-submodules

I am trying to install APIKit with carthage
And as the result of running
carthage update --platform iOS --use-submodules --no-use-binaries
I get error
A shell task (/usr/bin/env git submodule --quiet update --init --recursive) failed with exit code 1: fatal: reference is not a tree: 3c3be9d5f9735a034e5e9434e03f6db764e9125e Unable to checkout '3c3be9d5f9735a034e5e9434e03f6db764e9125e' in submodule path 'Carthage/Checkouts/OHHTTPStubs'
I use submodules as I am building a framework and want to be able to use it outside carthage. (I am following this guide: https://robots.thoughtbot.com/creating-your-first-ios-framework)

Hi rehsals,
I've just released APIKit 2.0.5 to fix the reference to OHHTTPStubs. Please run carthage update again and confirm that Carfile.resolved looks like below:
github "ishkawa/APIKit" "ee42834e908c893638e3f4ed2eb7fc9c7f164145"

The error message says git cannot checkout to 3c3be9d5f9735a034e5e9434e03f6db764e9125e. I guess that APIKit 2.0.4 has reference to the commit but it no longer exists on the repository.
I confirmed carthage update --platform iOS --use-submodules --no-use-binaries with following Cartfile completes successfully.
github "ishkawa/APIKit"

$ carthage update --platform iOS --use-submodules --no-use-binaries
*** Fetching APIKit
*** Fetching Result
*** Checking out Result at "2.1.2"
*** Checking out APIKit at "2.0.5"
*** xcodebuild output can be found in /var/folders/r_/k80kcyd57511kcs0fq1t12500000gn/T/carthage-xcodebuild.3efuvu.log
*** Building scheme "Result-iOS" in Result.xcodeproj
*** Building scheme "APIKit" in APIKit.xcworkspace

Hi ishkawa. Thank you for swift response. Indeed, with 2.0.5 it works just fine.
Offtop: watched your talk on try! Swift and can't resist trying your APIKit.

😎


Don't merge! Regression pull request perf test for no metavalidation

Docs Build status updates of commit 35009ce:
:clock10: Pending: waiting for processors (7 builds ahead of you)
:warning: Docs Build is busy, currently there are 7 builds ahead of this one, for more information you can view the Build queue graph on the Docs Portal.

Docs Build status updates of commit 35009ce:
:warning: Validation status: warnings

File
Status
Preview URL
Details
Dependent Files

api/overview/azure/TestingPullRequest.md
:warning:Warning
View
Details

api/overview/azure/TestingPullRequest.md

[Warning] Metadata with following name(s) are not allowed to be set in Yaml header, or as file level metadata in docfx.json, or as global metadata in docfx.json: content_type. They are generated by Docs platform, so the values set in these 3 places will be ignored. Please remove them from all 3 places to resolve the warning.
[Warning] the value invalid_type is undefined for metadata content_type
Line 7: [Warning] Invalid file link:(~/api/overview/nonexisted1.md).
Line 8: [Warning] Invalid file link:(~/api/overview/nonexisted2.md).
Line 9: [Warning] Invalid file link:(~/api/overview/nonexisted3.md).

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Update Blog “it-is-getting-easier-to-stay-up-to-date-with-pharmacy-informatics-new-rss-feed”

Automatically generated by Netlify CMS

👷 Deploy Preview for cool-toffee-ab3b21 processing.

Name
Link

🔨 Latest commit
173810b9c0494dfa4cb8e090d0b71aecc3e2d680

🔍 Latest deploy log
https://app.netlify.com/sites/cool-toffee-ab3b21/deploys/63e9a170465d4c0007519a96


Union Layout Should Not Support Separate Validity Mask

Describe the bug

Unlike other data types, unions do not have their own validity bitmap. Instead, the nullness of each slot is determined exclusively by the child arrays which are composed to create the union.

From https://arrow.apache.org/docs/format/Columnar.html#union-layout
To Reproduce
We currently support this, which aside from adding a lot of complexity, is incorrect
Expected behavior
We shouldn't support something not in the arrow specification

This does come with a rather strange implication, that nulls are typed which is a little odd...


sim_uart: fix printf error when use irq mode

Summary
sim_uart: fix printf error when use irq mode
Impact
sim printf
Testing
VELA

@GUIDINGLI @xiaoxiang781216 This PR breaks sim (and has stopped all our testing from working).
After this commit, sim output is not flushed when a task is exited.
Thus the last output before task exit is lost, and our CI cannot parse the test results.
For example, when running mmtest, this is the normal output before this change:
...

(31)Releasing memory at 0x7f93e1633f00 (size=24 bytes)
     mallinfo:
       Total space allocated from system = 66059728
       Number of non-inuse chunks        = 2
       Largest non-inuse chunk           = 65557792
       Total allocated space             = 432688
       Total non-inuse space             = 65627040
TEST COMPLETE

after this change:
...

(26)Releasing memory at 0x7f716cc34500 (size=25 bytes)
     mallinfo:
       Total space a

Can you please have a look?

@fjpanag
Which defconfig do you use ?
I got the following output when use sim:nsh:
(31)Releasing memory at 0x7ffff3e9e3a0 (size=24 bytes)
     mallinfo:
       Total space allocated from system = 67108192
       Number of non-inuse chunks        = 4
       Largest non-inuse chunk           = 65247392
       Total allocated space             = 1860608
       Total non-inuse space             = 65247584
TEST COMPLETE

@GUIDINGLI Please try to enable CONFIG_TESTING_MM_POWEROFF.

@fjpanag
https://github.com/apache/nuttx/pull/8408
Please have a try, thanks.


Remove SQLite from default init

а так ок :+1:

!test

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
http://jenkins.test//job/vmmaster.staging.regression/60/

!test

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
http://jenkins.test//job/vmmaster.staging.regression/61/

!test

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
http://jenkins.test//job/vmmaster.staging.regression/62/

!test

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
http://jenkins.test//job/vmmaster.staging.regression/63/

!test

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
http://jenkins.test//job/vmmaster.staging.regression/64/

!test

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
http://jenkins.test//job/vmmaster.staging.regression/65/

!test

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
http://jenkins.test//job/vmmaster.staging.regression/66/

!test

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
http://jenkins.test//job/vmmaster.staging.regression/67/

!test

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
http://jenkins.test//job/vmmaster.staging.regression/68/

!test

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
http://jenkins.test//job/vmmaster.staging.regression/69/

:+1:


Out of game taglist? (enhancement)

Any chance you could provide a readable taglist accessible out of game for those of us who get all our great ideas away from the PC, such as myself at work?
I know the wiki link leads to a taglist, but I've noticed the notice saying it's no longer being kept up to date, so can't rely on it.
Maybe a txt in an unused part of the jar?

Edit: Nevermind. Found it at "InGameInfoXML-#.#-#.#.#-universal.jar\assets\ingameinfo\lang\en_us.lang" (and the app I use can apparently read it.)

There used to be a list of all tags outside the game, however that quickly went out of sync because I often forgot to update the wiki page.


XCTest output is not recorded when using CodeLLDB

Describe the bug
When using CodeLLDB as the debug adapter XCTest output is not captured and so test results are not recorded. If swift.debugger.useDebugAdapterFromToolchain is true then output is captured and tests work as expected.
To Reproduce
Create a simple XCTest:
import XCTest

class MyTests: XCTestCase {
    func testFoo() {
        print("x")
    }
}

Right click testFoo()'s test icon, Debug Test
Notice there is Debug Console output for the test, but the test is not marked as passed.

Environment

OS: macOS
Swift version: swift-driver version: 1.115 Apple Swift version 6.0 (swiftlang-<IP_ADDRESS>.11 clang-16<IP_ADDRESS>)
vscode-swift version: 1.11.2

I will verify this one.

Verified with and without the patch, the bug is fixed with the patch applied.


yt-dlp: 2023.10.13 -> 2023.11.14

Description of changes

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[x] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
23.11 Release Notes (or backporting 23.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

https://github.com/yt-dlp/yt-dlp/security/advisories/GHSA-3ch3-jhc6-5r8x


root-signing: Prepare for tuf-on-ci migration

As part of https://github.com/sigstore/root-signing/issues/1247 root-signing requires some project setting changes:

Allow and encourage merge commits: signing event branches are collaboration branches where individual commits have different authors and actual meaning.
Do not require linear history: signing events make sense as slightly longer lived branches: preserving this history makes sense
Remove two required checks that are replaced by tuf-on-ci checks (which can be made required in a later commit)
Add branch protection for "publish"
Modify branch protection for "main":

Remove sigstore-keyholders from pushRestrictions list: this looks like a mistake, keyholders should not have permissions for main
Add sigstore-bot as a PR bypasser (this is how online signing happens)

CC @kommendorkapten @haydentherapper

@jku Is this good to go?

@jku Is this good to go?

yes LGTM.

This is now applied as of https://github.com/sigstore/community/actions/runs/9605680915


Using stack_logger with stack_crashlytics

According to README.md in stack_crashlytics, to integrate CrashlyticsService into our logger we can use:

Logger(
...
    output: MultipleLoggerOutput([
    ...
    CrashlyticsOutput(),
    ]),
);

However, this doesn't seem to be able to work with StackedLogger in
@StackedApp(
  routes: [
    ...
  ],
  dependencies: [
    LazySingleton(classType: CrashlyticsService),
    ...
  ],
  logger: StackedLogger(), // only has the single parameter String logHelperName
)
class App {}

Is there a way to generate app.logger.dart such that the MultipleLoggerOutput() in the getLogger() function can have the additional CrashlyticsOutput()? Maybe by adding a parameter in StackedLogger() that takes a list of other LogOutputs?

Released in stacked 2.1.9
Released in stacked_generator 0.4.8


Output file sizes in console.

As per frontendfriends/grunt-combine-mq#3.

Going to just do this in the grunt task - file itself isn't as easily accessible in the Node task at the moment.


Failure in callback after 5 minutes only Android 14 (API level 34)

Describe the bug
Firstly, all settings in capacitor.config.json are correct following community recommendations:
"plugins": {     "CapacitorHttp": {       "enabled": true     },     "android": {   "useLegacyBridge": true     }   }
I am using the libraries:
"@capacitor-community/background-geolocation": "^1.2.17",
"@capacitor/android": "5.2.2",
"@capacitor/core": "^5.7.2",
"@capacitor/geolocation": "^5.0.7",
"@capacitor/local-notifications": "^5.0.7",
Among others...
I conducted several tests with different versions of Android, and only the most current version, which is version 14 API 34 at the moment, exhibits this behavior. Sending data to a database isn't an issue; however, I've noticed that after five minutes, the callback stops working. It seems that the callback remains cached; thus, when I unlock the device and open the app, all the returns are sent at once.
I did some research on the Android website, and found that there were some changes related to background services for Android 14, but I was unable to identify what problem was occurring.
The problem occurs both on virtual devices in Android Studio and on the physical cell phone.
On other Android versions, such as 8.1, 10 and 13, the app works all day long.
In logcat:

code:
`BackgroundGeolocation.addWatcher(
    {
      backgroundMessage:
        "Dont close app.",
      requestPermissions: true,
      stale: false,
      distanceFilter: 0,
    },
    async (location) => {                      <<<------------HERE IS PROBLEM

      console.log("I am live")
      console.log(new Date())
      this.coords.push(location?.longitude, location?.latitude)
      await this.sendLocation(location)
    }
  );`

Can you reproduce the problem using the example app? https://github.com/capacitor-community/background-geolocation/tree/master/example

I upgraded my Samsung A52 to Android 14, and I have not been able to reproduce the problem with the example app. To use it, add a BG watcher and pay attention to the first two numbers in each line. The first is the time the location was generated, and second is the time the location was delivered to the callback. The two timestamps should be the same, meaning that there is no delay in delivering the location.

I'm doing some testing right now, I haven't tested it with the example code yet. But I made some changes to my code that seem to have resolved it.
The first change was in the capacitor configuration file, I was looking at the example code configuration file and noticed that android.useLegacyBridge is not a 'plugins' key and is actually in the main object.
The second change was in the addWatcher callback, I removed async and included a 'return' in my sendLocation method.

o capacitor.config.json ficou assim:
{   "webDir": "dist/spa",   "appId": "com.mycompany.test",   "appName": "test",   "plugins": {     "CapacitorHttp": {       "enabled": true     },     "Badge": {       "persist": true,       "autoClear": false     },     "SplashScreen": {       "launchShowDuration": 2000,       "launchFadeOutDuration": 1000,       "backgroundColor": "#000000",       "showSpinner": false,       "splashFullScreen": true,       "splashImmersive": true     },     "PushNotifications": {       "presentationOptions": ["badge", "sound", "alert"]     }   },   "android": {     "useLegacyBridge": true   } }

As I made these changes together, I'm not sure if it was because I included android.useLegacyBridge in the right place or because I made my sendLocation method synchronous.
I'm still doing some testing, but I must thank you for your help.
Thanks!

The example code works fine on Android 14:

Ah yes, because the useLegacyBridge probably only takes effect in newer versions of Android.
It doesn't look like you ran the example code for very long (the L and W values are seconds since startup), but since your problem is resolved I guess it doesn't matter.


C# Support

Will you make C# support? It is faster then GDscript

Will you make C# support? It is faster then GDscript

It's json, you can access it with whatever


Possible to exclude values from other fields ?

Hi.
I have several fields of type SearchTextField. And initially they should have all have the same list of filterStrings.
But I would like to exclude dynamically the values entered in any of those fields.
So that there won't be duplicate.
Is there a way to do that , or do I need to write my own logic ?

I'm afraid you have to write your own logic. Sorry!


[RFC] Enable overloaded extern static methods (GH #1851)

Closes #1851
Not sure if the approach I'm taking here is the best, but I tracked the issue down to overloads not being properly accounted for in AttributeNode.analyse_as_type_attribute.

@scoder @da-woods Thanks for your reviews. Is there anything else you would like to see on this PR?

Thanks!


Referral program

WIP Referral program

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


refactor: Use a TypedDict to annotate state dictionaries

📚 Documentation preview 📚: https://meltano-sdk--2419.org.readthedocs.build/en/2419/

Very little to gain from this at this point


[BUG] Preview images don't update in manage page

When looking at skins in your management page that have had their files updated, the images were never updated and remain what the first upload was like. It's fine when you go to any other page though.

Oh, right, I fixed this with https://github.com/Nensec/FRTools/commit/c14d3c7271bed947fdf30523cb3c12f00c89c3f7


Python: update numpy and scipy

Motivation for this change
Regular updates. Unfortunately we cannot merge yet because there's quite a lot of test failures. Therefore, I think we need to wait for at least a Pandas update but possibly also a Cython update.
Things done

[ ] Tested using sandboxing
(nix.useSandbox on NixOS,
or option build-use-sandbox in nix.conf
on non-NixOS)
Built on platform(s)

[ ] NixOS
[ ] macOS
[ ] Linux

[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Fits CONTRIBUTING.md.

why is it a mass rebuild?

numpy causes also non-python packages to be rebuild.

anyway, i push this eventually to staging

I've pushed these commits to master because it doesn't look like staging is going to be merged anytime soon.


[BUG] eve::negate does not compile

Describe the bug
I assume eve::negate usage is the same as other arithmetic operations like eve::abs, eve::sqr, etc. (link to documentation)
To Reproduce
https://godbolt.org/z/cKoKbP4KM
Expected behavior
Negation works properly
Setup:

Compiler and compiler's version: clang-17.0.1
OS: NixOS Linux
Processor Architecture: x86-64 (Ryzen 5950X)
Instructions Set used: AVX2 (I think?)

Additional context
The code snippet does not compile with gcc-13.2 either. Both eve-20230215 and eve-trunk have this issue.
Using std::negate{} instead of eve::negate works properly (but perhaps less efficient).

The eve::negate function is a  binary function that carry over the sign of one of its param to the other
https://jfalcou.github.io/eve/group__core__arithmetic_gad0dd8ae2cec6f99c1523ec4871efce3c.html#gad0dd8ae2cec6f99c1523ec4871efce3c

We could probably add an unary negate to mimic std negate

my bad! I should've read the documentation more carefully! I was quite convinced it should behave the same as std::negate

We will add an overload to -x

negate is named here according some x86 simd intrinsics

I think you can already use eve::minus(x) in place of -x.
The only differrence is that if x is scalar (not wide) there is no automatic C++ promotion
For instance short to int.

I think we can however also align with std behavior for the unary case ?

I don't know: look at the doc of std::negate. It's a part of

Oh I forgot about minus.
However we have a case where expected behavior w/r to an existing name is co fusing. So we do need to think about it.

The more I think about it, negate seems like a strange name for this function:
$$
f(x, y) = x \cdot \text{sgn}(y)
$$
For example $f(x, y) = x$ for positive $y$ (is this really a negate?).
I would maybe call it eve::mul_sgn or maybe even eve::sign (as a complement to the already existing unary eve::sign).
For the unary case, I guess some alternatives could be:

eve::zerominus (since there already is an eve::oneminus)
eve::flip_sign

Sign has a completely different semantic as it returns the sign bit.
The negate name comes from the intrinsic name most arch use for this.
For now, I will amen the doc to cross reference negate and unary minus and put some warnings there.


remove references to jvm-build-service

jvm-build-service is not used by anyone and will get reworked
buildah task contains references to jvm-build-service
Removal of the references is a breaking change

Remove analyse-dependencies-java-sbom step
Remove SBOM_JAVA_COMPONENTS_COUNT result
Remove JAVA_COMMUNITY_DEPENDENCIES result

Release buildah version 0.3
Upgrade buildah version in docker-build pipelines to 0.3

Note for reviewers:
I haven't found an easy way to compare different files in GitHub, I would probably checkout the branch locally and do something like:
diff task/buildah/0.2/buildah.yaml task/buildah/0.3/buildah.yaml

(I welcome different ideas)

Could you also update https://github.com/konflux-ci/build-definitions/blob/main/.github/workflows/temp-block-buildah.yaml to also check the 0.3 yaml?
It appears that the check is still relevant, no updates on https://issues.redhat.com/browse/KONFLUX-5706 :disappointed:


WIP - try removing most of globals.d.ts

I am not a fan of <any>global but it definitely is a start to getting rid of lib/globals.d.ts. We will need to have to move out IError.
Since we have the lib/exitCodes.ts,  it might be nice to stick both the IError interface and the exitCodes into an error(s)/ folder.


Reduce api token logging

Description

We've had a pretty large increase to our log storage costs in production. This PR tries to remove some of the logs from the API token process. I'm opening to keeping a subset of these or whatever the minimum amount of information we need to debug problems with this is.
Testing Instructions

Checklist

[ ] My pull request has a descriptive title (not a vague title like Update index.md).
[ ] My pull request targets the default branch of the repository (main) or a parent feature branch.
[ ] My commit messages follow best practices.
[ ] My code follows the established code style of the repository.
[ ] I added or updated tests for the changes I made (if applicable).
[ ] I added or updated documentation (if applicable).
[ ] I tried running the project locally and verified that there are no visible errors.

Developer Certificate of Origin

Developer Certificate of Origin
Developer Certificate of Origin
Version 1.1

Copyright (C) 2004, 2006 The Linux Foundation and its contributors.
1 Letterman Drive
Suite D4700
San Francisco, CA, 94129

Everyone is permitted to copy and distribute verbatim copies of this
license document, but changing it is not allowed.

Developer's Certificate of Origin 1.1

By making a contribution to this project, I certify that:

(a) The contribution was created in whole or in part by me and I
    have the right to submit it under the open source license
    indicated in the file; or

(b) The contribution is based upon previous work that, to the best
    of my knowledge, is covered under an appropriate open source
    license and I have the right under that license to submit that
    work with modifications, whether created in whole or in part
    by me, under the same open source license (unless I am
    permitted to submit under a different license), as indicated
    in the file; or

(c) The contribution was provided directly to me by some other
    person who certified (a), (b) or (c) and I have not modified
    it.

(d) I understand and agree that this project and the contribution
    are public and that a record of the contribution (including all
    personal information I submit with it, including my sign-off) is
    maintained indefinitely and may be redistributed consistent with
    this project or the open source license(s) involved.

@dhruvkb I'm not sure; they also clutter local development considerably too. Perhaps I should comment them out rather than delete for easy restoration if there's ever issues with the token implementation?


update barlow font(s)

internal discussion: https://prisma-company.slack.com/archives/C06F2DJ49K6/p1713887313466709?thread_ts=1712930321.220419&cid=C06F2DJ49K6


[0.5pt] Setup project with webpack and Jest

👇 The following feature was added to the branch
👉 Webpack configuration
👉 Jest Configuration

:green_circle:  Approved! :partying_face:
Hi @gergitokusse

Your milestone is complete!  There is nothing else to say other than... it's time to merge it :shipit:
Congratulations! 🎉
Highlights 🌟

✔ Set up Gitflow
✔ Set up Webpack
✔ Set up a JavaScript testing library (Jest)

Optional suggestions 🤷♂
Every comment with the [OPTIONAL] prefix is not crucial enough to stop the approval of this PR. However, I strongly recommend you take them into account as they can make your code better.
Cheers, and Happy coding!👏👏👏
Important Notes 📝

Feel free to leave any questions or comments in the PR thread if something is not 100% clear.
Please, remember to tag me in your question so I can receive the notification.


PriorityQueue   get error

in beam.py  file
"class BeamItem  " need to  amend    follows：

class BeamItem(object):
    """This is a node in the beam search tree.

    Each node holds four things: a log probability, a list of previous words, and
    the two hidden state vectors.
    """

    def __init__(self, prev_word, prev_hidden, log_prob=0.0):
        self.log_probs = log_prob
        if type(prev_word) == list:
            self.words = prev_word
        else:
            self.words = [prev_word]
        self.prev_hidden = prev_hidden

    **def __le__(self, other):
        return self.log_probs <= other.log_probs

    def __lt__(self, other):
        return self.log_probs < other.log_probs

    def __ge__(self, other):
        return self.log_probs >= other.log_probs

    def __gt__(self, other):
        return self.log_probs > other.log_probs**

    # 重定义等于比较
    def __eq__(self, other):
        return self.log_probs == other.log_probs

    def __str__(self):
        return "beam {0:.3f}: ".format(self.log_probs) + ''.join(self.words)

because  PriorityQueue  has Priority feature 。so ，it need add compare  function。

Thanks for raising this issue. Are you sure it's necessary? Does the priority queue get the priority from line 51 on beam.py?

I am sure  necessary。   because ,it can raise runtime Exception in python3 environment .  follows:
Traceback (most recent call last):   File "dynamic.py", line 150, in <module>     beam_size=100, stop=stop)  # always use userid=0   File "/home/jovyan/project/query_completion/code/beam.py", line 144, in GetCompletions     new_nodes.Insert(new_beam)   File "/home/jovyan/project/query_completion/code/beam.py", line 71, in Insert     self.Eject()   File "/home/jovyan/project/query_completion/code/beam.py", line 82, in Eject     score, _ = self.q.get()   File "/opt/conda/lib/python3.7/queue.py", line 180, in get     item = self._get()   File "/opt/conda/lib/python3.7/queue.py", line 236, in _get     return heappop(self.queue) TypeError: '<' not supported between instances of 'BeamItem' and 'BeamItem'
The exception above is due to the PriorityQueue . It has no function of comparison. So if we add some code, we can give the queue a right function

I added your suggested change. Thanks for reporting this!


added tests and root functionality

This PR extends the signature of href to href(cb, root), where root is an optional dom node that we will never capture clicks outside of.
When adding tests for this I also added missing test for the basic href functionality, including the data attribute thing that @jliuhtonen implemented in #27.

sweet, thanks!

Gah, apparently forgot to use my brain in that first comment signature fix. Should be better now. :P

Btw, to be exact, the function returns undefined, not null.
In addition to the tests in place, I think href needs actual browser tests, but this is something that we can look into later on.
👍

Whoops again, good catch @jliuhtonen.
Agreed on unit tests alone not really feeling sufficient here. Also agreed on dealing with that later. :)

Thanks! I'll publish this at a later time as master isn't published yet. Cheers!


Switch stays disabled

Hello there,
I followed the kb article here https://support.plesk.com/hc/en-us/articles/12376918716695-How-to-enable-Queues-in-the-Laravel-project-for-Plesk-Laravel-Toolkit but my switch is still disabled.

The composer extension is installed.
from shell php artisan queue:work  works without problems.
What am I missing?

There is a comment under the kb article which you are attached to the issue.
You have to run php artisan config:clear in the cli. Then the switch is switchable.


Add support for "Get Blob"

Add support according to spec at https://docs.microsoft.com/en-us/rest/api/storageservices/fileservices/get-blob
Range specification is here https://docs.microsoft.com/en-us/rest/api/storageservices/fileservices/specifying-the-range-header-for-blob-service-operations
For now we will only support Block Blobs.

range spec is still to be done


Use fsnotify instead of hinotify for file watching

Cross platform file watching support, issue #36 (and duplicate #39!)
Also bump resolver to lts-14.16.

Closes #36.


[MAIN-3] Investigate the dimension bug from MAIN-2

Pull Request
Story ID: MAIN-3
Title: [MAIN-3] Investigate the dimension bug from MAIN-2
Card URL: https://trello.com/c/5LRd6X5g
Author: @flukekd


Use SecureRandom rather than OpenSSL::Random

SecureRandom uses OpenSSL::Random under the hood anyway but
is apparently a more secure:
https://bugs.ruby-lang.org/issues/4579

Yep, makes sense. Thanks for fixing this. Pushed out under v3.0.1


typescript error Cannot write file ... because it would overwrite input file

my tsconfig file
{
  "compilerOptions": {
    "module": "commonjs",
    "target": "es2015",
    "jsx": "react",
    "allowJs": true
  }
}

I'm new to typescript but I don't think this should happen.
this is the script I'm running
"dev": "concurrently \"tsc --watch\" next",

You'll have to rename all your .js files to .jsx


Publish azd GHA to the marketplace

We should package up an azd GHA and publish on the marketplace so that folks can easily grab it!
See https://github.com/marketplace/actions/azure-cli-action as an example

@hemarina Is this closeable now?


Add merkle library

Cleaned up version of the naive merkle tree implementation. Has a basic unit test.

Hi, Mark.  My only comment at this time is that I'm skeptical if a fixed 3 levels is sufficient enough.  Oh, and support for trimmed regions needs to be added sometime. But it's a good base to work from, thanks!


V2.1.342 版本发布

Codecov Report

Merging #72 (93ef674) into V2.1.X (15bdf4a) will decrease coverage by 0.02%.
The diff coverage is 22.22%.

:exclamation: Current head 93ef674 differs from pull request most recent head c863ecc. Consider uploading reports for the commit c863ecc to get more accurate results

@@            Coverage Diff             @@
##           V2.1.X      #72      +/-   ##
==========================================
- Coverage   58.93%   58.91%   -0.03%
==========================================
  Files         394      394
  Lines       25899    25915      +16
==========================================
+ Hits        15264    15267       +3
- Misses      10635    10648      +13

Impacted Files
Coverage Δ

apps/backend/agent/tools.py
92.66% <ø> (ø)

apps/backend/views.py
56.83% <0.00%> (ø)

apps/node_man/handlers/permission.py
29.23% <0.00%> (-0.46%)
:arrow_down:

apps/backend/plugin/views.py
33.49% <15.00%> (-0.42%)
:arrow_down:

apps/node_man/models.py
74.03% <100.00%> (ø)

apps/node_man/serializers/ap.py
92.98% <100.00%> (ø)

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 15bdf4a...c863ecc. Read the comment docs.


Add a script launching a test network to the template project [ECR-4289]

Overview
Add a script launching a test network to the template project.
No .gitignore unfortunately: https://issues.apache.org/jira/browse/ARCHETYPE-505?jql=project %3D ARCHETYPE AND resolution %3D Unresolved AND text ~ "gitignore" ORDER BY priority DESC%2C updated DESC

See: https://jira.bf.local/browse/ECR-XYZ
Definition of Done

[ ] There are no TODOs left in the code
[ ] Change is covered by automated tests
[ ] The coding guidelines are followed
[ ] Public API has Javadoc
[ ] Method preconditions are checked and documented in the Javadoc of the method
[ ] Changelog is updated if needed (in case of notable or breaking changes)
[ ] The continuous integration build passes

No .gitignore unfortunately:

The workaround is terribly complicated: https://issues.apache.org/jira/browse/ARCHETYPE-505?focusedCommentId=16218074&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-16218074
and undocumented.


telegram bot InlineKeyboardButton  CallbackData

hi
I am using mvc controller and i set webhook with https. everythings is ok just i couldnot use InlineKeyboardButton  Callback, is there any way to do this?
public async Task Index()
{
try
{
var reader = new StreamReader(Request.InputStream);
var json = reader.ReadToEnd();
var myClass = JsonConvert.DeserializeObject(json);
if (myClass != null)
await SendMessage(myClass);
.
.
.

I don't see what exactly your issue has got to do with Telegram.Bot...

@majidazn Could you provide more info about your issue? Please always follow template issue.


AppCompatReactiveActivity and SupportReactiveFragment

Hi,
Could you please make two special versions of ReativeActivity and ReativeFragment which uses the support implementation. Porting is not possible since two many classes are internal or private.
It would be a super simple fix by just extending AppCompatActivity and SupportFragment instead of Activity and Fragment
Thank you!
...Something like:
public class AppCompatReactiveActivity<TViewModel> : AppCompatReactiveActivity, IViewFor<TViewModel>, ICanActivate
		where TViewModel : class
	{
		TViewModel _ViewModel;
		public TViewModel ViewModel {
			get { return _ViewModel; }
			set { this.RaiseAndSetIfChanged(ref _ViewModel, value); }
		}

		object IViewFor.ViewModel {
			get { return _ViewModel; }
			set { _ViewModel = (TViewModel)value; }
		}

		protected AppCompatReactiveActivity() { }

		protected AppCompatReactiveActivity(IntPtr handle, JniHandleOwnership ownership) : base(handle, ownership)
		{
		}
	}

	public class AppCompatReactiveActivity : AppCompatActivity, IReactiveObject, IReactiveNotifyPropertyChanged<ReactiveActivity>, IHandleObservableErrors
	{
		public event ReactiveUI.PropertyChangingEventHandler PropertyChanging {
			add { ReactiveUI.PropertyChangingEventManager.AddHandler(this, value); }
			remove { ReactiveUI.PropertyChangingEventManager.RemoveHandler(this, value); }
		}

		void IReactiveObject.RaisePropertyChanging(ReactiveUI.PropertyChangingEventArgs args)
		{
			ReactiveUI.PropertyChangingEventManager.DeliverEvent(this, args);
		}

		public event PropertyChangedEventHandler PropertyChanged {
			add { ReactiveUI.PropertyChangedEventManager.AddHandler(this, value); }
			remove { ReactiveUI.PropertyChangedEventManager.RemoveHandler(this, value); }
		}

		void IReactiveObject.RaisePropertyChanged(PropertyChangedEventArgs args)
		{
			ReactiveUI.PropertyChangedEventManager.DeliverEvent(this, args);
		}

		/// <summary>
		/// Represents an Observable that fires *before* a property is about to
		/// be changed.
		/// </summary>
		public IObservable<IReactivePropertyChangedEventArgs<ReactiveActivity>> Changing {
			get { return this.getChangingObservable(); }
		}

		/// <summary>
		/// Represents an Observable that fires *after* a property has changed.
		/// </summary>
		public IObservable<IReactivePropertyChangedEventArgs<ReactiveActivity>> Changed {
			get { return this.getChangedObservable(); }
		}

		protected AppCompatReactiveActivity()
		{
		}

		protected AppCompatReactiveActivity(IntPtr handle, JniHandleOwnership ownership) : base(handle, ownership)
		{
		}

		/// <summary>
		/// When this method is called, an object will not fire change
		/// notifications (neither traditional nor Observable notifications)
		/// until the return value is disposed.
		/// </summary>
		/// <returns>An object that, when disposed, reenables change
		/// notifications.</returns>
		public IDisposable SuppressChangeNotifications()
		{
			return this.suppressChangeNotifications();
		}

		public IObservable<Exception> ThrownExceptions { get { return this.getThrownExceptionsObservable(); } }

		readonly Subject<Unit> activated = new Subject<Unit>();
		public IObservable<Unit> Activated { get { return activated; } }

		readonly Subject<Unit> deactivated = new Subject<Unit>();
		public IObservable<Unit> Deactivated { get { return deactivated; } }

		protected override void OnPause()
		{
			base.OnPause();
			deactivated.OnNext(Unit.Default);
		}

		protected override void OnResume()
		{
			base.OnResume();
			activated.OnNext(Unit.Default);
		}

		readonly Subject<Tuple<int, Result, Intent>> activityResult = new Subject<Tuple<int, Result, Intent>>();
		public IObservable<Tuple<int, Result, Intent>> ActivityResult {
			get { return activityResult; }
		}

		protected override void OnActivityResult(int requestCode, Result resultCode, Intent data)
		{
			base.OnActivityResult(requestCode, resultCode, data);
			activityResult.OnNext(Tuple.Create(requestCode, resultCode, data));
		}

		public Task<Tuple<Result, Intent>> StartActivityForResultAsync(Intent intent, int requestCode)
		{
			// NB: It's important that we set up the subscription *before* we
			// call ActivityForResult
			var ret = ActivityResult
				.Where(x => x.Item1 == requestCode)
				.Select(x => Tuple.Create(x.Item2, x.Item3))
				.FirstAsync()
				.ToTask();

			StartActivityForResult(intent, requestCode);
			return ret;
		}

		public Task<Tuple<Result, Intent>> StartActivityForResultAsync(Type type, int requestCode)
		{
			// NB: It's important that we set up the subscription *before* we
			// call ActivityForResult
			var ret = ActivityResult
				.Where(x => x.Item1 == requestCode)
				.Select(x => Tuple.Create(x.Item2, x.Item3))
				.FirstAsync()
				.ToTask();

			StartActivityForResult(type, requestCode);
			return ret;
		}
	}
}

Hi! Is there any plan to add this in the near future? Thanks!

Ditto..please add.  Also need an example/docs on how to use it...
@richarddd : you should just submit a PR


Question: Origin of guid value in extension identifiers

Hi,
extension properties are named like "extension_55dc0861f9a44eb999e0a8a872204adb_Jersey_Number"
Where does the value 55dc0861f9a44eb999e0a8a872204adb come from?
Is this a static guid that identifies each extension property?

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

ID: 4a4b8453-d2bc-9c8d-bb16-26fa7e4c6363
Version Independent ID: 160642fc-b5a9-1ebe-7daf-105509b6e2f4
Content: Use the Graph API in Azure Active Directory B2C
Content Source: articles/active-directory-b2c/manage-user-accounts-graph-api.md
Service: active-directory
Sub-service: b2c
GitHub Login: @mmacy
Microsoft Alias: marsma

Extension attributes in the Graph API are named by using the convention extension_ApplicationObjectID_attributename. If you use user flows extension attributes it's the object id of an application called b2c-extensions-app. Do not modify. Used by AADB2C for storing user data.. As for custom policy, it's the object id of the application you created.
This document is about to be updated using MS Graph instead of AAD Graph. Please check the update document next week.
Yoel

@yoelhor  Thank you! 👍

@sven5 Let us know if you need further assistance with this.
@yoelhor, Thank you for the update.


CircleCI: update to Docker 19.03.12, and enable BuildKit

The "stable" option gave Docker 17.09, which is pretty old

@arkodg @tiborvass PTAL

shouldn't the fix be to update stable mapping to 19.03.X ?

Yeah, not sure why "stable" doesn't pick something more current; I've seen similar weird issues in the past with CircleCI


Add table aws_api_gateway_integration

References
https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/api_gateway_integration
https://docs.aws.amazon.com/sdk-for-go/api/service/apigateway/#APIGateway.GetIntegration

APIGateway do not have List API call for listing out the available integrations.
For making Get API call we need three required param, 1. HttpMethod, 2. ResourceId and 3. RestApiId.
We can get HttpMethod and RestApiId from parent hydrate but we will not get the ResourceId, so this is blocked.


libxcb: Update sha256 for patch

For some reason, the sha256 has changed on the patch for libxcb. It's not clear what has changed in the diff file. But the build succeeds with the updated hash.
Build error:
$ brew install libxcb
==> Installing libxcb from linuxbrew/xorg
==> Downloading https://xcb.freedesktop.org/dist/libxcb-1.12.tar.bz2
Already downloaded: /home/jlever/.cache/Homebrew/libxcb-1.12.tar.bz2
==> Downloading https://cgit.freedesktop.org/xcb/libxcb/patch/?id=8740a288ca468433141341347aa115b9544891d3
Already downloaded: /home/jlever/.cache/Homebrew/libxcb--patch-fef834cb600cdeafac052be9535f9e84e5e71d2434bdd43deef8b116a459123b
Error: SHA256 mismatch
Expected: fef834cb600cdeafac052be9535f9e84e5e71d2434bdd43deef8b116a459123b
Actual: aa3bdbf37c951d6b42b6aeb3c182b87065761027b3180b6f381088fdd13809b4
Archive: /home/jlever/.cache/Homebrew/libxcb--patch-fef834cb600cdeafac052be9535f9e84e5e71d2434bdd43deef8b116a459123b
To retry an incomplete download, remove the file above.

Contributing to homebrew-xorg:
You can erase any parts of this template not applicable to your Pull Request.

[X] Have you followed the guidelines in our Contributing document?
[X] Have you checked to ensure there aren't other open Pull Requests for the same update/change?
[ ] Have you included a log of the failed build without your patch using brew gist-logs <formula>?
No logs were found for this.

$ brew gist-logs libxcb
Error: No logs.

[ ] Does your submission pass
brew audit --strict <formula> (where <formula> is the name of the formula you're submitting)?

The following error was found (but is not related to this change as it occurs without it)
linuxbrew/xorg/libxcb:
  * C: 1: col 1: A `test do` test block should be added
Error: 1 problem in 1 formula

[X] Have you built your formula locally prior to submission with brew install <formula>?

I got the same error today and will wait for acceptance of PR!

Thank you, @jakelever for the fix and @whiter462 for the confirmation!


Imperative API does not work

new Clipboard('', {
    text: function(trigger) {
        return "TEST1234";
    }
});

This does not set my clipboard to TEST1234. Am I missing something?

Missing some dom element to work with? I would rather make a global function to do this job than installing a plugin for this. What am I missing?

Hey @avindra, the first argument is missing.
Here's a simple working example: http://jsfiddle.net/zenorocha/5b8r8hg5/1/

I don't understand - are you saying that some abritrary DOM element is required? If so... why?

Yes, user interaction is required for security reasons. That's how the browser works, not my fault ;)

Yes, user interaction is required for security reasons. That's how the browser works, not my fault ;)

@zenorocha I suggest documenting those things, to prevent abstraction leak, see #130.


fix: clean up TS errors

Description
This PR cleans up a lot of TS errors throughout the repo in preparation of switching our build step to use the TypeScript compiler. There's a bit of leg work that needs to be done(or maybe just some configuration) before that can happen, so I'd like to get these changes merged, and then capture that switch in a subsequent PR
note: in FPSCounter, I've added .toString() calls to all the numbers since Text wants strings, not numbers. Is this how we'd prefer to do that, or do we want to loosen the children type of Text?
Changes

improves type safety of various components
adds ts-expect-error lines where we're waiting on updates from outside libraries
references the l3-ui-theme-base for the theme type for development

Testing
ensure we're no longer receiving type errors inside the packages/solid workspace, ensure all components render and function as expected

I would read all the files... but... I have a life. I'll assume you know what you're doing on this one...

@slhay28 can you just test the PR by opening the branch and running storybook


Build broken with bevy dependencies

Minimal crate with dependency: https://github.com/jrobsonchase/hello-rust-nix
It works fine when building directly with cargo, but I get this error when trying to build via nix:
$ nix build -L 2>&1 | sed -n '/> {/s/^ \+> //p' | jq -r .message.rendered
error[E0433]: failed to resolve: could not find `DynamicStruct` in the crate root
  --> src/geometry.rs:29:41
   |
29 | #[derive(Copy, Clone, PartialEq, Debug, Reflect)]
   |                                         ^^^^^^^ not found in the crate root
   |
   = note: this error originates in the derive macro `Reflect` (in Nightly builds, run with -Z macro-backtrace for more info)
help: consider importing this struct
   |
1  | use bevy_reflect::DynamicStruct;
   |

error[E0412]: cannot find type `ReflectRef` in the crate root
  --> src/geometry.rs:29:41
   |
29 | #[derive(Copy, Clone, PartialEq, Debug, Reflect)]
   |                                         ^^^^^^^ not found in the crate root
   |
   = note: this error originates in the derive macro `Reflect` (in Nightly builds, run with -Z macro-backtrace for more info)
help: consider importing this enum
   |
1  | use bevy_reflect::ReflectRef;
   |

error[E0433]: failed to resolve: could not find `ReflectRef` in the crate root
  --> src/geometry.rs:29:41
   |
29 | #[derive(Copy, Clone, PartialEq, Debug, Reflect)]
   |                                         ^^^^^^^ not found in the crate root
   |
   = note: this error originates in the derive macro `Reflect` (in Nightly builds, run with -Z macro-backtrace for more info)
help: consider importing this enum
   |
1  | use bevy_reflect::ReflectRef;
   |

error[E0412]: cannot find type `ReflectMut` in the crate root
  --> src/geometry.rs:29:41
   |
29 | #[derive(Copy, Clone, PartialEq, Debug, Reflect)]
   |                                         ^^^^^^^ not found in the crate root
   |
   = note: this error originates in the derive macro `Reflect` (in Nightly builds, run with -Z macro-backtrace for more info)
help: consider importing this enum
   |
1  | use bevy_reflect::ReflectMut;
   |

error[E0433]: failed to resolve: could not find `ReflectMut` in the crate root
  --> src/geometry.rs:29:41
   |
29 | #[derive(Copy, Clone, PartialEq, Debug, Reflect)]
   |                                         ^^^^^^^ not found in the crate root
   |
   = note: this error originates in the derive macro `Reflect` (in Nightly builds, run with -Z macro-backtrace for more info)
help: consider importing this enum
   |
1  | use bevy_reflect::ReflectMut;
   |

error: aborting due to 32 previous errors

Some errors have detailed explanations: E0405, E0412, E0432, E0433.

For more information about an error, try `rustc --explain E0405`.

I get the same result when trying to build the bevy_math crate directly on its own (see here), but oddly, it works fine when built in the main repository (fork with nix here). It does not however, work when rebased on the v0.5.0 tag (here), which makes me think it's likely something in one of its dependencies that's getting compiled differently than with cargo.
Additionally, the bevy_dylib crate fails to build in the main repository with a rather long linker error, which I'm attaching separately.
log.txt

I reproduced the build failure in your example on the release-0.9.1 branch.  I believe the features might not be the same with cargo & nix, so you end up missing a dependency.  Do you know which dependency is supposed to be providing Reflect and how it might be toggled with features?  There is an outstanding issue of features not matching what results from cargo invocation.

Here's bevy 0.7.0 nix build: https://github.com/psionic-k/bevy-build-example
I ran into one hangup with the features I need to check.  I had to disable some features on wgpu-hal crate by modifying the Cargo.nix (you just find the features and delete them).  Very non-ideal to touch generated code.  There's no way to turn these off from rootFeatures AFAIK
[ ] - add alsa-sys override to cargo2nix master
[ ] - inspect feature logic and figure out why wgpu-hal had all render backends enabled

I also ran into this problem with wgpu-hal, I set up a minimal project in case it can help.

What I do to fix these is run into main.rs and add some dbg! to show for which feature activation a dx12 feature shows up.  Once I know that, I can look at the toml's, straight down the dependencies, and figure out if there's a bug (there's a bug).
Looking at the Cargo.nix's some more, it seems too many features are activated farther down the dependency tree.  The last work done was to make features depend correctly on root crate features.  As you get deeper in the tree, it's just an enumeration of all the features and no conditions :-1:

One thing that could be related; for correct feature detection with wgpu Cargo.toml needs to contain resolver = "2" or edition = "2021"(which uses resolver = "2"), see this line of code. I think I read somewhere that cargo2nix builds a synthetic Cargo.toml, perhaps that one does not have resolver = "2" or edition = "2021" set.

That's during build phase.  When generating the Cargo.nix, we're using cargo 0.61.0 and it can do everything cargo does.  Since the extra features show up in Cargo.nix, it's generation that's bugged.

cargo tree -e features is helpful to see what the feature expression dependency should look like.
Currently in cargo2nix, the goal was to build with all root crates at least built, meaning any features or dependencies they express in the no default features case will always be on unconditionally.
This behavior involves  marking a lot of features downstream as "required", which is whey their expressions have no logic.  They are not enabled by anything else, they just are.

Looks like another situation where the model is going to need to be more fully implemented.  Expressing the intersection of root features and platforms will be expensive.  I don't see a way around it that can be correct.
Might finally be the situation that drives me to look at using guppy to handle the metadata instead of the cargo library.
https://docs.rs/guppy/latest/guppy/graph/struct.EnabledStatus.html

Thanks for working on this @psionic-k :heart:

You're welcome :smiling_face_with_tear:      I haven't had any bright ideas.  I believe I have to re-architect the expressions and the generator to get reasonable sized expressions that are, most importantly, correct as they can possibly be

Updating with information that will later get refined into the readme.
At a high level, cargo2nix is really cargo metadata to Nix.  Compared to the JSON output of metadata, we have the advantage of logic expressions.  The JSON metadata just prints both versions of a dependency if necessary.  We encode variants using logic and using unique attributes like devDependencies.
  cargo2nixVersion = "0.11.0";
  workspace = {
    foo = rustPackages.unknown.foo."0.1.0";
  };
  "registry+https://github.com/rust-lang/crates.io-index".arm."0.0.1" = overridableMkRustCrate (profileName: rec {
    name = "arm";
    version = "0.0.1";
    registry = "registry+https://github.com/rust-lang/crates.io-index";
    src = fetchCratesIo { inherit name version; sha256 = "439b38e7fbde01cff2f66ac3f0270a1dbf826a91b75c3c6f9e9f39cc71f777a2"; };
  });

  "unknown".foo."0.1.0" = overridableMkRustCrate (profileName: rec {
    name = "foo";
    version = "0.1.0";
    registry = "unknown";
    src = fetchCrateLocal workspaceSrc;
    features = builtins.concatLists [
      (lib.optional (rootFeatures' ? "foo/default") "default")
      (lib.optional (rootFeatures' ? "foo/default" || rootFeatures' ? "foo/python") "python")
    ];
    dependencies = {
      ${ if hostPlatform.parsed.cpu.name == "armv7" then "arm" else null } = rustPackages."registry+https://github.com/rust-lang/crates.io-index".arm."0.0.1" { inherit profileName; };
      ${ if hostPlatform.parsed.cpu.name == "x86_64" then "unicode_ident" else null } = rustPackages."registry+https://github.com/rust-lang/crates.io-index".unicode-ident."1.0.1" { inherit profileName; };
      ${ if hostPlatform.parsed.kernel.name == "windows" && hostPlatform.parsed.cpu.name == "aarch64" || hostPlatform.parsed.kernel.name == "windows" && hostPlatform.parsed.cpu.name == "x86_64" then "winapi" else null } = rustPackages."registry+https://github.com/rust-lang/crates.io-index".winapi."0.3.9" { inherit profileName; };
    };
    devDependencies = {
      libc = rustPackages."registry+https://github.com/rust-lang/crates.io-index".libc."0.2.126" { inherit profileName; };
      ${ if hostPlatform.parsed.kernel.name == "linux" then "time_macros" else null } = buildRustPackages."registry+https://github.com/rust-lang/crates.io-index".time-macros."0.2.4" { profileName = "__noProfile"; };
    };
    buildDependencies = {
      spin = buildRustPackages."registry+https://github.com/rust-lang/crates.io-index".spin."0.5.2" { profileName = "__noProfile"; };
    };
  });

At build time, features are enabled to drive conditional compiles using [cfg(feature = "bar")] etc.  There is some backend normalization of how the default feature is expressed in mkcrate.nix.  The feature consumption in mkcrate.nix has to be right or we get the wrong crate output even if the Cargo.nix is correct.
Varying dependencies, which can happen per-target, can vary features on those dependencies (two variants of the same dependency).  Features of course can enable optional deps.  Due to all of the reasons why feature logic was changed in resolver=2 or edition=2021, we have to be able to express features per platform, per profile.  Currently, dependencies can vary a lot more than features.  Features can only change based on rootFeatures, which is improperly implemented still.  This breaks platform-specific features / deps such as those in bevy.
The version 0.9.0 logic in main.rs is still interesting.   There was a bug with rootFeatures, but it was minor.  I'm revisiting this work after finding out more about the results of resolve_ws_with_opts calls.
Cargo's own metadata source shows the correct way in cargo 0.62.0 to get resolve information for all targets and features.  Encoding the JSON in Nix requires a bit of plumbing since Nix can express logic but JSON does not.
Reducing cargo metadata for comparison to Cargo.nix
cargo metadata --format-version 1 | jq 'walk(if type == "object" then del(.metadata .authors, .categories, .description, .license, .license_file, .readme, .repository, .homepage, .keywords, .publish, .manifest_path, .documentation, .targets, .registry, .rust_version, .links, .default_run, .edition, .rename) else . end)
' -C | less

Use --filter-platform aarch64-pc-windows-msvc etc to look at metadata output with different options passed to resolve_ws_with_opts
Cargo's own metadata source is useful for maintaining cargo2nix because changes to cargo that affect the metadata command likely affect how cargo2nix needs to work.

is there a patchset in work that i can track for this?

@natto1784  I'm not tracking burn down toward working on this and there is no branch.
What does exist is design and similar code.
There is a Nix expression generator already in /src.  There is code in Cargo metadata from the cargo library that is outputting to JSON what we need instead in Nix expressions.
The work that needs to be done is to create the inputs for metadata's JSON and write Nix expressions instead of JSON.  Nix expressions collapse to slightly more compact forms since they can contain logic.
IIRC Bevy specifically exposes some situation where features in dependents need to activate based on the platform or CPU, something I don't think the current expression generator is capable of because it's not supposed to happen - it's an artifact of platform dependencies that have different features enabled when switched on for that platform


Use custom_show_command instead as per guidelines

Need to update command file to use custom_show_command as per guidelines

Tested show and list locally, everything worked

And you also tested show where the HanaInstance or SapMonitor resource didn't exist?

yes
pak@pakman-desktop:~/src/azure-hanaonazure-cli-extension$ az sapmonitor show -g "tniek-sapmons" -n "sapmon-ru1asdsad"
ResourceNotFoundError: Operation returned an invalid status code 'Not Found'
pak@pakman-desktop:~/src/azure-hanaonazure-cli-extension$ az hanainstance show -g asd -n asd
ResourceNotFoundError: Operation returned an invalid status code 'Not Found'


disable the repo

I would like to have "disable the repository action available".
Do you think it can be useful?
I might look into that...

Can you elaborate?
yum_repository has an "enabled" property. Setting it to false disables it.

My bad, did not see that.


WARNING  Failed to check if we can skip restoring outputs for xyz#abc: Unavailable. Proceeding to check cache

Verify canary release

[X] I verified that the issue exists in the latest Turborepo canary release.

Link to code that reproduces this issue
Occurs regardless of mono-repository.
What package manager are you using / does the bug impact?
pnpm
What operating system are you using?
Linux
Which canary version will you have in your reproduction?
1.11.3
Describe the Bug
HI! I'm getting the following anytime I run any command within my monorepo setup. I suspect this is related to turbo daemon. Running turbo daemon stop && turbo daemon clean && turbo daemon start, temporarily fixes this bug but after some time it occurs again and you have repeat the command for it to work again normally.
➜  lune git:(master) ✗ nr lint

> lune@ lint /home/ayush/personal/lune
> turbo lint --continue

• Packages in scope: @lune/backend, @lune/landing, @lune/lint, @lune/mobile, @lune/tsconfig
• Running lint in 5 packages
• Remote caching disabled
 WARNING  Failed to check if we can skip restoring outputs for @lune/mobile#lint: Unavailable. Proceeding to check cache
 WARNING  Failed to check if we can skip restoring outputs for @lune/landing#lint: Unavailable. Proceeding to check cache
 WARNING  Failed to check if we can skip restoring outputs for @lune/backend#lint: Unavailable. Proceeding to check cache
@lune/landing:lint: Failed to mark outputs as cached for @lune/landing#lint: GrpcFailure(Cancelled)
 WARNING  Failed to mark outputs as cached for @lune/mobile#lint: Error with daemon: bad grpc status code: The operation was cancelled
@lune/mobile:lint: Failed to mark outputs as cached for @lune/mobile#lint: Error with daemon: bad grpc status code: The operation was cancelled
 WARNING  Failed to mark outputs as cached for @lune/backend#lint: Error with daemon: bad grpc status code: The operation was cancelled
@lune/backend:lint: Failed to mark outputs as cached for @lune/backend#lint: Error with daemon: bad grpc status code: The operation was cancelled

Expected Behavior
The warnings should not show up.
To Reproduce
I do not yet have an idea what causes this.
Additional context
It occurs regardless of repository. I'm attaching the turbo daemon --verbosity 3,
➜  lune git:(master) ✗ turbo daemon --verbosity 3
2024-01-08T05:11:33.820+0530 [DEBUG] turborepo_lib::shim: Global turbo version: 1.10.13
2024-01-08T05:11:33.822+0530 [DEBUG] turborepo_lib::shim: Local turbo path: /home/ayush/personal/lune/node_modules/turbo-linux-64/bin/turbo
2024-01-08T05:11:33.822+0530 [DEBUG] turborepo_lib::shim: Local turbo version: 1.11.3
2024-01-08T05:11:33.822+0530 [DEBUG] turborepo_lib::shim: Repository Root: /home/ayush/personal/lune
2024-01-08T05:11:33.822+0530 [DEBUG] turborepo_lib::shim: Running local turbo binary in /home/ayush/personal/lune/node_modules/turbo-linux-64/bin/turbo

2024-01-08T05:11:33.822+0530 [DEBUG] turborepo_lib::shim: supports_skip_infer_and_single_package true
2024-01-08T05:11:33.823+0530 [DEBUG] turborepo_lib::shim: Global turbo version: 1.11.3
2024-01-08T05:11:33.823+0530 [TRACE] log: registering event source with poller: token=Token(1), interests=READABLE
2024-01-08T05:11:33.825+0530 [DEBUG] turborepo_telemetry: telemetry sender not initialized
2024-01-08T05:11:33.825+0530 [DEBUG] turborepo_telemetry: telemetry sender not initialized
2024-01-08T05:11:33.825+0530 [DEBUG] turborepo_telemetry: telemetry sender not initialized
2024-01-08T05:11:33.826+0530 [DEBUG] turborepo_telemetry: telemetry sender not initialized
2024-01-08T05:11:33.826+0530 [DEBUG] turborepo_telemetry: telemetry sender not initialized
2024-01-08T05:11:33.826+0530 [TRACE] turborepo_lib::commands::daemon: logging to file: AbsoluteSystemPathBuf("/home/ayush/.local/share/turborepo/logs/7235b59ab98c05df-turbo.log")
2024-01-08T05:11:33.827+0530 [TRACE] turborepo_lib::tracing: created non-blocking file writer
2024-01-08T05:11:33.827+0530 [TRACE] turborepo_lib::daemon::endpoint: acquiring pidlock
 WARNING  daemon already running
2024-01-08T05:11:33.827+0530 [DEBUG] turborepo_telemetry: telemetry sender not initialized
2024-01-08T05:11:33.827+0530 [DEBUG] turborepo_telemetry: telemetry sender not initialized
2024-01-08T05:11:33.827+0530 [DEBUG] turborepo_lib::cli: Skipping telemetry close - not initialized

Note "Global turbo version: 1.10.13" , that's not true. The global version on my machine for turbo is 1.11.3-canary.2.

Can you include the contents of the daemon log file when this occurs? They should be present in /home/ayush/.local/share/turborepo/logs
Unrelated to the actual issue, but you might be using a different turbo then the one shown by pnpm. Can you quick run turbo --skip-infer --version? Maybe which -a turbo to display all of the binaries that are found.

Hi @chris-olszewski, The log files are huge (22.4 Mb) and therefore I've attached 'three' different subsets below where the word daemon appears. If you need the whole file, let me know. I'll attach it.

7235b59ab98c05df-turbo.log.2024-01-08

subset 1

2024-01-08T01:01:06.723557Z  INFO daemon_server:set_daemon_logger: turborepo_lib::tracing: exit
2024-01-08T01:01:06.724111Z  INFO daemon_server:set_daemon_logger: turborepo_lib::tracing: close
2024-01-08T01:01:06.724173Z  INFO daemon_server:listen_socket{daemon_root=AbsoluteSystemPath("/mnt/sda4/tmp/turbod/7235b59ab98c05df") running=true}: turborepo_lib::daemon::endpoint: new
2024-01-08T01:01:06.724179Z  INFO daemon_server:listen_socket{daemon_root=AbsoluteSystemPath("/mnt/sda4/tmp/turbod/7235b59ab98c05df") running=true}: turborepo_lib::daemon::endpoint: enter
2024-01-08T01:01:06.724187Z TRACE daemon_server:listen_socket{daemon_root=AbsoluteSystemPath("/mnt/sda4/tmp/turbod/7235b59ab98c05df") running=true}: turborepo_lib::daemon::endpoint: acquiring pidlock
2024-01-08T01:01:06.724261Z DEBUG daemon_server:listen_socket{daemon_root=AbsoluteSystemPath("/mnt/sda4/tmp/turbod/7235b59ab98c05df") running=true}: turborepo_lib::daemon::endpoint: pidlock acquired at /mnt/sda4/tmp/turbod/7235b59ab98c05df/turbod.pid
2024-01-08T01:01:06.724265Z DEBUG daemon_server:listen_socket{daemon_root=AbsoluteSystemPath("/mnt/sda4/tmp/turbod/7235b59ab98c05df") running=true}: turborepo_lib::daemon::endpoint: listening on socket at /mnt/sda4/tmp/turbod/7235b59ab98c05df/turbod.sock
2024-01-08T01:01:06.724294Z  INFO daemon_server:listen_socket{daemon_root=AbsoluteSystemPath("/mnt/sda4/tmp/turbod/7235b59ab98c05df") running=true}: turborepo_lib::daemon::endpoint: exit
2024-01-08T01:01:06.724298Z  INFO daemon_server:listen_socket{daemon_root=AbsoluteSystemPath("/mnt/sda4/tmp/turbod/7235b59ab98c05df") running=true}: turborepo_lib::daemon::endpoint: close time.busy=116µs time.idle=8.60µs
2024-01-08T01:01:06.724312Z TRACE daemon_server: turborepo_lib::daemon::server: acquired connection stream for socket
2024-01-08T01:01:06.725507Z DEBUG turborepo_filewatch: starting filewatcher
2024-01-08T01:01:06.725575Z TRACE turborepo_filewatch: manually watching /home/ayush/personal/lune
2024-01-08T01:01:06.725637Z TRACE turborepo_filewatch: manually watching /home/ayush/personal/lune/node_modules
2024-01-08T01:01:06.725774Z TRACE turborepo_filewatch: manually watching /home/ayush/personal/lune/node_modules/eslint-utils
2024-01-08T01:01:06.725821Z TRACE turborepo_filewatch: manually watching /home/ayush/personal/lune/node_modules/eslint-utils/node_modules
2024-01-08T01:01:06.726217Z TRACE turborepo_filewatch: manually watching /home/ayush/personal/lune/node_modules/eslint-utils/node_modules/eslint-visitor-keys
2024-01-08T01:01:06.726625Z TRACE turborepo_filewatch: manually watching /home/ayush/personal/lune/node_modules/eslint-utils/node_modules/eslint-visitor-keys/lib
2024-01-08T01:01:06.727103Z  INFO daemon_server: turborepo_lib::commands::daemon: exit
2024-01-08T01:01:06.727264Z TRACE turborepo_filewatch: manually watching /home/ayush/personal/lune/node_modules/babel-plugin-react-native-web
2024-01-08T01:01:06.727346Z TRACE turborepo_filewatch: manually watching /home/ayush/personal/lune/node_modules/babel-plugin-react-native-web/src

subset 2

2024-01-08T17:11:16.774190Z TRACE turborepo_filewatch::package_watcher: file event: Event { kind: Remove(File), paths: ["/home/ayush/personal/lune/node_modules/@eslint/_tmp_205860_1cec410afcd3b9d7226006dc7fca1f5b/lib"], attr:tracker: None, attr:flag: None, attr:info: None, attr:source: None }
2024-01-08T17:11:16.774195Z TRACE turborepo_filewatch::package_watcher: file event: Event { kind: Remove(Folder), paths: ["/home/ayush/personal/lune/node_modules/@eslint/_tmp_205860_1cec410afcd3b9d7226006dc7fca1f5b/lib"], attr:tracker: None, attr:flag: None, attr:info: None, attr:source: None }
2024-01-08T21:11:10.516756Z  INFO daemon_server: turborepo_lib::commands::daemon: enter
2024-01-08T21:11:10.524584Z  INFO daemon_server: turborepo_lib::commands::daemon: exit
2024-01-08T21:11:10.524590Z  INFO daemon_server: turborepo_lib::commands::daemon: enter
2024-01-08T21:11:10.528549Z  INFO turborepo_filewatch::package_watcher: exiting package watcher
2024-01-08T21:11:10.530616Z  INFO daemon_server: turborepo_lib::daemon::server: gRPC server exited
2024-01-08T21:11:10.530627Z TRACE daemon_server: turborepo_lib::daemon::server: root watching exited
2024-01-08T21:11:10.531813Z TRACE daemon_server: turborepo_lib::daemon::server: filewatching handle joined
2024-01-08T21:11:10.534393Z TRACE daemon_server: turborepo_lib::commands::daemon: shutting down daemon: Timeout
2024-01-08T21:11:10.534399Z  INFO daemon_server: turborepo_lib::commands::daemon: exit
2024-01-08T21:11:10.534404Z  INFO daemon_server: turborepo_lib::commands::daemon: close
2024-01-08T21:11:10.535901Z DEBUG turborepo_telemetry: telemetry sender not initialized
2024-01-08T21:11:10.535905Z DEBUG turborepo_telemetry: telemetry sender not initialized
2024-01-08T21:11:10.535907Z DEBUG turborepo_lib::cli: Skipping telemetry close - not initialized

subset 3 (this is where I believe the above event occurred where I ran turbo daemon --verbosity 3.

2024-01-08T01:01:13.645757Z TRACE turborepo_filewatch::package_watcher: file event: Event { kind: Create(Folder), paths: ["/home/ayush/personal/lune/node_modules/turbo_tmp_156601"], attr:tracker: None, attr:flag: None, attr:info: None, attr:source: None }
2024-01-08T01:01:13.645838Z TRACE turborepo_filewatch::package_watcher: file event: Event { kind: Create(Folder), paths: ["/home/ayush/personal/lune/node_modules/turbo_tmp_156601/bin"], attr:tracker: None, attr:flag: None, attr:info: None, attr:source: None }
2024-01-08T01:01:13.645848Z TRACE turborepo_filewatch::package_watcher: file event: Event { kind: Create(File), paths: ["/home/ayush/personal/lune/node_modules/turbo_tmp_156601/bin/turbo"], attr:tracker: None, attr:flag: None, attr:info: None, attr:source: None }
2024-01-08T01:01:13.645856Z TRACE turborepo_filewatch::package_watcher: file event: Event { kind: Create(Folder), paths: ["/home/ayush/personal/lune/node_modules/turbo_tmp_156601"], attr:tracker: None, attr:flag: None, attr:info: None, attr:source: None }
2024-01-08T01:01:13.645863Z TRACE turborepo_filewatch::package_watcher: file event: Event { kind: Create(File), paths: ["/home/ayush/personal/lune/node_modules/turbo_tmp_156601/README.md"], attr:tracker: None, attr:flag: None, attr:info: None, attr:source: None }
2024-01-08T01:01:13.645906Z TRACE turborepo_filewatch::package_watcher: file event: Event { kind: Create(File), paths: ["/home/ayush/personal/lune/node_modules/turbo_tmp_156601/LICENSE"], attr:tracker: None, attr:flag: None, attr:info: None, attr:source: None }
2024-01-08T01:01:13.645916Z TRACE turborepo_filewatch::package_watcher: file event: Event { kind: Create(File), paths: ["/home/ayush/personal/lune/node_modules/turbo_tmp_156601/package.json"], attr:tracker: None, attr:flag: None, attr:info: None, attr:source: None }
2024-01-08T01:01:13.646260Z TRACE turborepo_filewatch::package_watcher: file event: Event { kind: Modify(Name(From)), paths: ["/home/ayush/personal/lune/node_modules/turbo_tmp_156601"], attr:tracker: Some(141595), attr:flag: None, attr:info: None, attr:source: None }
2024-01-08T01:01:13.646279Z TRACE turborepo_filewatch::package_watcher: file event: Event { kind: Modify(Name(To)), paths: ["/home/ayush/personal/lune/node_modules/turbo"], attr:tracker: Some(141595), attr:flag: None, attr:info: None, attr:source: None }
2024-01-08T01:01:13.646286Z TRACE turborepo_filewatch::package_watcher: file event: Event { kind: Modify(Name(Both)), paths: ["/home/ayush/personal/lune/node_modules/turbo_tmp_156601", "/home/ayush/personal/lune/node_modules/turbo"], attr:tracker: Some(141595), attr:flag: None, attr:info: None, attr:source: None }
2024-01-08T01:01:13.646296Z TRACE turborepo_filewatch::package_watcher: file event: Event { kind: Modify(Name(From)), paths: ["/home/ayush/personal/lune/node_modules/turbo_tmp_156601"], attr:tracker: None, attr:flag: None, attr:info: None, attr:source: None }
2024-01-08T01:01:13.648059Z  WARN turborepo_filewatch: encountered error watching filesystem enumerating recursive watch: IO error for operation on /home/ayush/personal/lune/node_modules/@eslint-community/eslint-utils_tmp_156601: No such file or directory (os error 2)
2024-01-08T01:01:13.648090Z TRACE turborepo_filewatch::package_watcher: file event: Event { kind: Remove(File), paths: ["/home/ayush/personal/lune/node_modules/@eslint-community/eslint-utils_tmp_156601"], attr:tracker: None, attr:flag: None, attr:info: None, attr:source: None }
2024-01-08T01:01:13.648108Z TRACE turborepo_filewatch::package_watcher: file event: Event { kind: Remove(Folder), paths: ["/home/ayush/personal/lune/node_modules/@eslint-community/eslint-utils_tmp_156601"], attr:tracker: None, attr:flag: None, attr:info: None, attr:source: None }
2024-01-08T01:53:55.809958Z  INFO daemon_server: turborepo_lib::commands::daemon: enter
2024-01-08T01:53:55.812552Z  INFO daemon_server: turborepo_lib::commands::daemon: exit
2024-01-08T02:09:34.629820Z  INFO daemon_server: turborepo_lib::commands::daemon: enter
2024-01-08T02:09:34.631010Z  INFO daemon_server: turborepo_lib::commands::daemon: exit
2024-01-08T05:01:06.733404Z  INFO daemon_server: turborepo_lib::commands::daemon: enter
2024-01-08T05:01:06.741552Z  INFO daemon_server: turborepo_lib::commands::daemon: exit
2024-01-08T06:09:34.633189Z  INFO daemon_server: turborepo_lib::commands::daemon: enter
2024-01-08T06:09:34.643932Z  INFO daemon_server: turborepo_lib::daemon::server: gRPC server exited
2024-01-08T06:09:34.643944Z TRACE daemon_server: turborepo_lib::daemon::server: root watching exited
2024-01-08T06:09:34.645353Z TRACE daemon_server: turborepo_lib::daemon::server: filewatching handle joined
2024-01-08T06:09:34.647918Z TRACE daemon_server: turborepo_lib::commands::daemon: shutting down daemon: Timeout
2024-01-08T06:09:34.648089Z  INFO daemon_server: turborepo_lib::commands::daemon: exit
2024-01-08T06:09:34.648095Z  INFO daemon_server: turborepo_lib::commands::daemon: close
2024-01-08T06:09:34.649696Z DEBUG turborepo_telemetry: telemetry sender not initialized
2024-01-08T06:09:34.649700Z DEBUG turborepo_telemetry: telemetry sender not initialized
2024-01-08T06:09:34.649702Z DEBUG turborepo_lib::cli: Skipping telemetry close - not initialized
2024-01-08T17:11:10.507058Z  INFO daemon_server:set_daemon_logger: turborepo_lib::tracing: exit
2024-01-08T17:11:10.507097Z  INFO daemon_server:set_daemon_logger: turborepo_lib::tracing: close
2024-01-08T17:11:10.507373Z  INFO daemon_server:listen_socket{daemon_root=AbsoluteSystemPath("/mnt/sda4/tmp/turbod/7235b59ab98c05df") running=true}: turborepo_lib::daemon::endpoint: new
2024-01-08T17:11:10.507380Z  INFO daemon_server:listen_socket{daemon_root=AbsoluteSystemPath("/mnt/sda4/tmp/turbod/7235b59ab98c05df") running=true}: turborepo_lib::daemon::endpoint: enter
2024-01-08T17:11:10.507389Z TRACE daemon_server:listen_socket{daemon_root=AbsoluteSystemPath("/mnt/sda4/tmp/turbod/7235b59ab98c05df") running=true}: turborepo_lib::daemon::endpoint: acquiring pidlock
2024-01-08T17:11:10.507485Z DEBUG daemon_server:listen_socket{daemon_root=AbsoluteSystemPath("/mnt/sda4/tmp/turbod/7235b59ab98c05df") running=true}: turborepo_lib::daemon::endpoint: pidlock acquired at /mnt/sda4/tmp/turbod/7235b59ab98c05df/turbod.pid
2024-01-08T17:11:10.507490Z DEBUG daemon_server:listen_socket{daemon_root=AbsoluteSystemPath("/mnt/sda4/tmp/turbod/7235b59ab98c05df") running=true}: turborepo_lib::daemon::endpoint: listening on socket at /mnt/sda4/tmp/turbod/7235b59ab98c05df/turbod.sock
2024-01-08T17:11:10.507519Z  INFO daemon_server:listen_socket{daemon_root=AbsoluteSystemPath("/mnt/sda4/tmp/turbod/7235b59ab98c05df") running=true}: turborepo_lib::daemon::endpoint: exit
2024-01-08T17:11:10.507523Z  INFO daemon_server:listen_socket{daemon_root=AbsoluteSystemPath("/mnt/sda4/tmp/turbod/7235b59ab98c05df") running=true}: turborepo_lib::daemon::endpoint: close time.busy=139µs time.idle=10.9µs
2024-01-08T17:11:10.507536Z TRACE daemon_server: turborepo_lib::daemon::server: acquired connection stream for socket
2024-01-08T17:11:10.507778Z DEBUG turborepo_filewatch: starting filewatcher
2024-01-08T17:11:10.507854Z TRACE turborepo_filewatch: manually watching /home/ayush/personal/lune
2024-01-08T17:11:10.507917Z TRACE turborepo_filewatch: manually watching /home/ayush/personal/lune/node_modules
2024-01-08T17:11:10.508156Z TRACE turborepo_filewatch: manually watching /home/ayush/personal/lune/node_modules/eslint-utils
2024-01-08T17:11:10.508201Z TRACE turborepo_filewatch: manually watching /home/ayush/personal/lune/node_modules/eslint-utils/node_modules
2024-01-08T17:11:10.508708Z TRACE turborepo_filewatch: manually watching /home/ayush/personal/lune/node_modules/eslint-utils/node_modules/eslint-visitor-keys
2024-01-08T17:11:10.509044Z  INFO daemon_server: turborepo_lib::commands::daemon: exit
2024-01-08T17:11:10.509106Z TRACE turborepo_filewatch: manually watching /home/ayush/personal/lune/node_modules/eslint-utils/node_modules/eslint-visitor-keys/lib
2024-01-08T17:11:10.509356Z TRACE turborepo_filewatch: manually watching /home/ayush/personal/lune/node_modules/babel-plugin-react-native-web
2024-01-08T17:11:10.509409Z TRACE turborepo_filewatch: manually watching /home/ayush/personal/lune/node_modules/babel-plugin-react-native-web/src
2024-01-08T17:11:10.509564Z TRACE turborepo_filewatch: manually watching /home/ayush/personal/lune/node_modules/babel-plugin-react-native-web/src/__tests__
2024-01-08T17:11:10.509663Z TRACE turborepo_filewatch: manually watching /home/ayush/personal/lune/node_modules/babel-plugin-react-native-web/src/__tests__/__snapshots__
2024-01-08T17:11:10.509851Z TRACE turborepo_filewatch: manually watching /home/ayush/personal/lune/node_modules/setimmediate
2024-01-08T17:11:10.509905Z TRACE turborepo_filewatch: manually watching /home/ayush/personal/lune/node_modules/array-flatten
2024-01-08T17:11:10.509960Z TRACE turborepo_filewatch: manually watching /home/ayush/personal/lune/node_modules/emoji-regex
2024-01-08T17:11:10.510003Z TRACE turborepo_filewatch: manually watching /home/ayush/personal/lune/node_modules/emoji-regex/es2015
2024-01-08T17:11:10.510178Z TRACE turborepo_filewatch: manually watching /home/ayush/personal/lune/node_modules/csstype
2024-01-08T17:11:10.510254Z TRACE turborepo_filewatch: manually watching /home/ayush/personal/lune/node_modules/ci-info
2024-01-08T17:11:10.510321Z TRACE turborepo_filewatch: manually watching /home/ayush/personal/lune/node_modules/is-set

turbo --skip-infer --version
![image](https://github.com/vercel/turboget /assets/36449128/7bc2c4d1-5b1e-44bf-99fa-1e24b068a9f2)
which -a turbo

I ran turbo daemon --verbosity 3 again (at the time of writing this comment) and here is the result.

The issue still occurs if I were to run turbo lint from the root of my monorepo. I get,

I'm running in to this, too!
It tends to happen when I blow away node_modules, it seems

I added some more logging information in #6993 that I hope will shed some light on why the service is unavailable. If you could upgrade to 1.11.4-canary.1 and report back with the new "Unavailable" warning that would help me debug this further.

Hi @chris-olszewski! I upgraded turbo globally and locally to 1.11.4-canary.1. The following is the result of running turbo lint from the root of the monorepo.
 WARN  Unsupported engine: wanted: {"node":">18"} (current: {"node":"v18.16.1","pnpm":"8.6.7"})

> lune@ lint /home/ayush/personal/lune
> turbo lint --continue

• Packages in scope: @lune/backend, @lune/landing, @lune/lint, @lune/mobile, @lune/tsconfig
• Running lint in 5 packages
• Remote caching disabled
 WARNING  Failed to check if we can skip restoring outputs for @lune/backend#lint: server is unavailable: failed to write cookie file at /home/ayush/personal/lune/.turbo/cookies/28.cookie: No such file or directory (os error 2). Proceeding to check cache
 WARNING  Failed to check if we can skip restoring outputs for @lune/landing#lint: server is unavailable: failed to write cookie file at /home/ayush/personal/lune/.turbo/cookies/29.cookie: No such file or directory (os error 2). Proceeding to check cache
@lune/backend:lint: Failed to mark outputs as cached for @lune/backend#lint: Unavailable("failed to write cookie file at /home/ayush/personal/lune/.turbo/cookies/30.cookie: No such file or directory (os error 2)")
@lune/landing:lint: Failed to mark outputs as cached for @lune/landing#lint: Unavailable("failed to write cookie file at /home/ayush/personal/lune/.turbo/cookies/31.cookie: No such file or directory (os error 2)")
 WARNING  Failed to check if we can skip restoring outputs for @lune/mobile#lint: server is unavailable: failed to write cookie file at /home/ayush/personal/lune/.turbo/cookies/32.cookie: No such file or directory (os error 2). Proceeding to check cache
@lune/mobile:lint: cache miss, executing e37a8c315e74be1e
@lune/mobile:lint:
@lune/mobile:lint: ><EMAIL_ADDRESS>lint /home/ayush/personal/lune/apps/mobile
@lune/mobile:lint: > eslint . --cache --cache-location "node_modules/.cache/.eslintcache" --max-warnings 0
@lune/mobile:lint:
@lune/mobile:lint:
@lune/mobile:lint: /home/ayush/personal/lune/apps/mobile/expo-env.d.ts
@lune/mobile:lint:   3:73  warning  Insert `⏎`  prettier/prettier
@lune/mobile:lint:
@lune/mobile:lint: /home/ayush/personal/lune/apps/mobile/src/app/_layout.tsx
@lune/mobile:lint:   30:1  warning  Delete `⏎`  prettier/prettier
@lune/mobile:lint:
@lune/mobile:lint: /home/ayush/personal/lune/apps/mobile/src/app/index.tsx
@lune/mobile:lint:   26:16  warning  Replace `'lune.hello'` with `"lune.hello"`  prettier/prettier
@lune/mobile:lint:   27:19  warning  Insert `⏎·····`                             prettier/prettier
@lune/mobile:lint:
@lune/mobile:lint: ✖ 4 problems (0 errors, 4 warnings)
@lune/mobile:lint:   0 errors and 4 warnings potentially fixable with the `--fix` option.
@lune/mobile:lint:
@lune/mobile:lint: ESLint found too many warnings (maximum: 0).
@lune/mobile:lint:  ELIFECYCLE  Command failed with exit code 1.
@lune/mobile:lint: command finished with error, but continuing...
@lune/mobile#lint: command (/home/ayush/personal/lune/apps/mobile) /home/ayush/.local/share/pnpm/pnpm run lint exited (1)

 Tasks:    2 successful, 3 total
Cached:    2 cached, 3 total
  Time:    2.11s
Failed:    @lune/mobile#lint

 ERROR  run failed: command  exited (1)
 ELIFECYCLE  Command failed with exit code 1