Adds a case insensitive index on user login and display name for LIKE queries

Used by zooniverse/Talk-Api#90 for autocompleting usernames.

If you'd rather avoid casting to ::text and use varchar_pattern_ops instead, I can rewrite this as an execute -- apparently schema_plus_pg_indexes always casts case_insensitive to ::text for some reason.

I have absolutely no idea about the characteristics of those operators, so I'm fine with any of them until proven otherwise :P
LGTM

@marten: Looks like this picked up conflicts on db/structure.sql so I recreated the commit

The structure.sql file is fixed now by the way.

@parrish i may be missing something but we already have 2 indexes (here & here) that support these like queries.
irb(main):002:0> User.where("lower(login) like 'cam'").explain
=> EXPLAIN for: SELECT "users".* FROM "users" WHERE (lower(login) like 'cam')
                                     QUERY PLAN
------------------------------------------------------------------------------------
 Index Scan using index_users_on_login on users  (cost=0.43..8.45 rows=1 width=445)
   Index Cond: (lower((login)::text) = 'cam'::text)
   Filter: (lower((login)::text) ~~ 'cam'::text)
(3 rows)

irb(main):003:0> User.where("lower(display_name) like 'cam'").explain
=> EXPLAIN for: SELECT "users".* FROM "users" WHERE (lower(display_name) like 'cam')
                                        QUERY PLAN
-------------------------------------------------------------------------------------------
 Index Scan using index_users_on_display_name on users  (cost=0.43..8.45 rows=1 width=445)
   Index Cond: (lower((display_name)::text) = 'cam'::text)
   Filter: (lower((display_name)::text) ~~ 'cam'::text)
(3 rows)

irb(main):004:0> User.where("lower(login) like 'cam' or lower(display_name) like 'cam'").explain
=> EXPLAIN for: SELECT "users".* FROM "users" WHERE (lower(login) like 'cam' or lower(display_name) like 'cam')
                                               QUERY PLAN
---------------------------------------------------------------------------------------------------------
 Bitmap Heap Scan on users  (cost=8.88..16.89 rows=2 width=445)
   Recheck Cond: ((lower((login)::text) ~~ 'cam'::text) OR (lower((display_name)::text) ~~ 'cam'::text))
   Filter: ((lower((login)::text) ~~ 'cam'::text) OR (lower((display_name)::text) ~~ 'cam'::text))
   ->  BitmapOr  (cost=8.88..8.88 rows=2 width=0)
         ->  Bitmap Index Scan on index_users_on_login  (cost=0.00..4.44 rows=1 width=0)
               Index Cond: (lower((login)::text) = 'cam'::text)
         ->  Bitmap Index Scan on index_users_on_display_name  (cost=0.00..4.44 rows=1 width=0)
               Index Cond: (lower((display_name)::text) = 'cam'::text)
(8 rows)

Looks like it was the lack of the wildcard in your query that caused the query planner to use a different index.  (These queries are all rooted LIKE queries, by the way)
explain analyze verbose

select * from users where lower(login) like 'cam%' and lower(display_name) like 'cam%' limit 5

Limit  (cost=0.44..48.82 rows=1 width=890) (actual time=0.159..0.334 rows=5 loops=1)
  Output: id, email, encrypted_password, reset_password_token, reset_password_sent_at, remember_created_at, sign_in_count, current_sign_in_at, last_sign_in_at, current_sign_in_ip, last_sign_in_ip, created_at, updated_at, hash_func, password_salt, display_name, zooniverse_id, credited_name, classifications_count, activated_state, languages, global_email_communication, project_email_communication, admin, banned, migrated, valid_email, project_id, beta_email_communication, login, unsubscribe_token, api_key, ouroboros_created, subject_limit, private_profile, tsv, upload_whitelist
  ->  Index Scan using index_users_on_lower_names on public.users  (cost=0.44..48.82 rows=1 width=890) (actual time=0.155..0.320 rows=5 loops=1)
        Output: id, email, encrypted_password, reset_password_token, reset_password_sent_at, remember_created_at, sign_in_count, current_sign_in_at, last_sign_in_at, current_sign_in_ip, last_sign_in_ip, created_at, updated_at, hash_func, password_salt, display_name, zooniverse_id, credited_name, classifications_count, activated_state, languages, global_email_communication, project_email_communication, admin, banned, migrated, valid_email, project_id, beta_email_communication, login, unsubscribe_token, api_key, ouroboros_created, subject_limit, private_profile, tsv, upload_whitelist
        Index Cond: ((lower((users.login)::text) ~>=~ 'cam'::text) AND (lower((users.login)::text) ~<~ 'can'::text) AND (lower((users.display_name)::text) ~>=~ 'cam'::text) AND (lower((users.display_name)::text) ~<~ 'can'::text))
        Filter: ((lower((users.login)::text) ~~ 'cam%'::text) AND (lower((users.display_name)::text) ~~ 'cam%'::text))
Planning time: 0.451 ms
Execution time: 0.395 ms


🐛 Bug Report: sources component flash on Safari

📜 Description
Sources component appears on Safari for a moment even when no source document is selected.
👟 Reproduction steps
Set source document as none or Chunks processed per query to 0. Then start the conversation, you will see blank sources appear for a sec.
👍 Expected behavior
The sources component should not appear at all if None is selected in sources or Chunks processed per query set to 0.
👎 Actual Behavior with Screenshots

💻 Operating system
MacOS
What browsers are you seeing the problem on?
Safari
🤖 What development environment are you experiencing this bug on?
Docker
🔒 Did you set the correct environment variables in the right path? List the environment variable names (not values please!)
No response
📃 Provide any additional context for the Bug.
No response
📖 Relevant log output
No response
👀 Have you spent some time to check if this bug has been raised before?

[X] I checked and didn't find similar issue

🔗 Are you willing to submit PR?
None
🧑⚖ Code of Conduct

[X] I agree to follow this project's Code of Conduct

@pabik please assign me this issue!

Hey @AwadhootK just wanted to check in on this issue to see how things are going

@pabik Could you please assign these tickets to me? I will begin working on them right away.


FTP_ITC_EXT.1 & FTP_ITE_EXT.1 -> FTP_PRO.1/2/3

Consider changing these two extended SFRs to the new FTP_PRO SFRs. The match is not exact, but it is more explicit in terms of the expected crypto operations for either of those two SFRs. The FTP_ITP_EXT.1 could still be left to handle physical security.

I'm going to say no to this change as it takes what are 2 single line SFRs and replaces each one of them with 3 SFRs with a total of 11 requirements (so changing 2 requirements for 22 doesn't seem like a good idea).


Add Razor Evolution Engine and primitives

/cc @NTaylorMullen

This looks interesting - is there a corresponding issue, or is it something you can discuss yet?

hi @daveaglick - We don't have a good high level issue for this right now (should create some).
Some information that I can share, we're doing some long-lead work to improve Razor's extensibility. This was prototyped roughly as part of the effort building https://github.com/aspnet/RazorPages and is being adding to the mainline codebase of Razor and MVC so that we can ship packages.
Unfortunately there's not a particular release version or date that this is associated with, but I can say that it won't be part of the upcoming 1.1.0 release.
When we do release this, we will make the new Razor functionality the default experience in MVC but provide a shim to keep using the old host until we reach a major version release. There isn't much extensibility in current Razor, but we're committed to not removing what is there until it's a major version.
===============
Without committing to any specific goals, I'll say that pretty much anything you can imagine is in scope. That includes investment in our VS, and lighting up high quality Razor support in tools that don't have it today. We think that Razor has a lot more to give, and this is a chance for us to clean up the basement so we can start delivering those features.

@rynowak Thanks a lot for the detailed info. The vision sounds fantastic. I'll watch with interest as this is built out.

We don't have a good high level issue for this right now
pretty much anything you can imagine is under consideration by the team

I'd like to suggest the establishment of an issue for feature requests (or point us to UserVoice).

Thanks for the feedback, I opened an issue to track the high level goals of this work.


Some way to add dependencies when adding courses

Some courses depend on another course, so adding this information when creating this course could be used for creating the graph view

This issue has been implemented, closing the issue.


Docs: Spark integration page: SimilarWeb case study is hidden inside Databricks tab under "Hadoop FileSystem in Presigned mode" section

@kesarwam can you expand on what you want changed here please?

@kesarwam can you expand on what you want changed here please?

Case Study should be visible on main Spark integration page. Currently it is inside Databricks tab. So, it should be moved outside the tab and onto the main page.


V2: Get UserData form Group

There is no call to get users details from a group id.
Before this commit https://github.com/carpedm20/fbchat/commit/5e09cb9cab5d93db81dd42e7566d068f01d35b61, there was fetch_all_users_from_threads.
I can get User objects with Thread.participants, but i can't find a way to get a UserData
Is there a new method to fetch users détails from group id ?

You can get UserData with thread.fetch_thread_info([user_id1, user_id2...])


Fix wallet name attempt for production

@nicolasburtey I think this can fix the current issue in production.


[FLINK-7068][blob] change BlobService sub-classes for permanent and transient BLOBs

This splits up the BLOB store classes into two different use cases which is the biggest change of FLIP-19:

a PermanentBlobStore should resemble use cases for BLOBs that are permanently stored for a job's life time (HA and non-HA).
a TransientBlobStore should reflect BLOB offloading for logs, RPC, etc. which even does not have to be reflected by files.

The BlobServer implements both while the BlobCache provides access to individual implementations of the two. HA files may only be uploaded by the BlobServer (and the (now) only publicly useful method of BlobClient to upload jar files). All other accesses should go through the two BLOB store classes.
This PR is based upon #4238 in a series to implement FLINK-6916. It contains some development history and should be squashed.

[X] General

The pull request references the related JIRA issue ("[FLINK-XXX] Jira title text")
The pull request addresses only one issue
Each commit in the PR has a meaningful commit message (including the JIRA id)

[X] Documentation

Documentation has been added for new functionality
Old documentation affected by the pull request has been updated
JavaDoc for public methods has been added

[X] Tests & Build

Functionality added by the pull request is covered by tests
mvn clean verify has been executed successfully locally or a Travis build has passed

Hi Nico, I'm still waiting for Travis before merging FLINK-7056. In the meantime could you rebase this PR and squash all FLINK-7068 commits into one? Thanks.

I've merged #4238. Could you please rebase onto the latest master? Moreover, I've noticed that JobManagerCleanupITCase.testBlobServerCleanupCancelledJob failed in one of the Travis runs. Not sure if this is related.

Rebased onto master, but had to drag in #4402 early to fix the end-to-end tests failing due to spurious warnings. The test failure you observed was actually a test instability introduced with #4238 for which I added a hotfix to this PR.

sorry for the mess, but let me also drag in #4568 and adapt the code in here (which is moved from BlobCache to PermanentBlobCache by this PR)

After an offline discussion with @tillrohrmann, we agreed to have more of the transient vs. permanent BLOB handling inside the BlobServer by including the type into the BlobKey. The caches, however, remain separate (with a common base class for shared code) because of the different cache guarantees they give. In addition, we decided upon having a get-and-delete functionality for transient BLOBs (as planned by a TODO item previously).
This means the following changes:

the BlobServer deletes transient BLOBs after they have been successfully downloaded to a BLOB cache (the client acknowledges that)
the TransientBlobCache and PermanentBlobCache differ in the functionality they provide:

PermanentBlobCache uses ref-counting for cleaning up its resources
TransientBlobCache imposes the user to manually delete requested BLOB files (from the cache!)
TransientBlobCache allows uploading (transient) BLOBs
TransientBlobCache allows non-job-related BLOBs
both have a GET method: #getTransientFile() vs. #getPermanentFile()
irrespective of the actual cache being used, the BlobServer decides whether to delete the BLOB (transient BLOBs only) or not (permanent BLOBs)
theoretically, a permanent BLOB could also be retrieved from the TransientBlobCache (and the other way around if job-related) - this behaviour is not used though but basic tests exist to cover it

Rebased and extended the PR as requested - the last two commits contain the changes compared to the last review.
I tried to clean up some of the commits for a better merge but please note that this PR also includes #4568, #4238 and #4402 fixes and commits. For some of those, changes were applied afterwards in the review process which will cause conflicts in their respective PRs that I will close (fixed after merging this PR).

Thanks a lot for your work and patience with me @NicoK. Changes look good to me. I've rebased it onto the latest master and once Travis gives green light, I'll merge it :-)


lack of Ant-v2 task related

Hello,
I am wondering  learning results of Ant-v2's dataset, like ant-random-v0/2 ant-medium-v0/v2. I think it is not listed in d4RL original paper but it's supplemented in github later.
Do you have the interest to evaluate thoes ant-* environment? Cuz I get very strange result for ant, even ant-random gives great result. So I am curious to compare with your result.
Best,

@im-Kitsch Hi, thanks for the issue. It takes long to benchmark all algorithms with Ant dataset. But, if you give me which algorithm you want me to test, I can prioritize it.

Okay, I started BCQ benchmark with ant-x-v0 dataset first. I'll be back to you later once I get results.

@im-Kitsch Sorry, it took time, but I've added BCQ results with ant-x-v0 datasets.
https://github.com/takuseno/d3rlpy-benchmarks/blob/main/d4rl_table.csv

I've added v2 dataset results as well.

cool, @takuseno , really thanks a lot, it's really helpful


Bug 2231834: [release-4.13] Add multus related annotations to ceph toolbox

This is a manual backport of #2128

/retest

/retest

Closing for a new PR, with one more fix.


"SALCEA" is listed in the drop-down menu

Description:
"SALCEA" is listed in the drop-down menu alongside its corresponding county and commune, according to the law
Precondition:
The website is up an running.

Step 1
Type "SALCEA" in the search bar.

Expected results
The location is listed in the drop-down menu as "Oraș SALCEA, SUCEAVA".


Simplify helm chart installation

Helm 3.x does now finally support the creation of not existing namespaces, again this was already the case in Helm 2.x.
This PR simplifies the installation via helm upgrade by using --create-namespace to create the target namespace (if not exist) w/o the need for an additional kubectl apply statement.
DRAFT - Waiting for proper testing till the issue with the ingress path was fixed. https://helm.sh/docs/helm/helm_install/

Testing it here: https://dev.azure.com/mission-critical/Online/_build/results?buildId=1134&view=results

is this ready to merge now?

is this ready to merge now?

Yes, the e2e run was successful and is getting destroyed now.


Feature Request: function call when there is input available on stdin

I'm working with the FreeRTOS port, and finding it difficult to use standard input (stdin) from a terminal. Polling stdin with getchar_timeout_us() either stalls or burns up all the CPU cycles, which doesn't play well in a multitasking OS. I can see how to make a UART-connected terminal work in an interrupt-driven fashion in pico-examples/uart/uart_advanced. However, I would like to maintain the ability to change the destination for stdin and stdout using CMake directives, with input/output directed to UART or USB CDC.
How about an enhancement to Serial input and output on Raspberry Pi Pico that would make it possible to register a callback or something that could receive keystrokes from a terminal as they are typed, asynchronously, regardless of whether serial input (stdin) and output (stdout) are directed to either serial UART or to USB CDC (USB serial)?

merged into develop


Cant change profile in Preferences menu

My friend is too stubborn, to admit that any functionality regarding installing mods should happen in the packages tab. Could you please add in the functionality to send the user back to the packages list upon selecting a different profile, regardless of which menu the user is currently in

Yeah that's a totally reasonable request and one that should be pretty easy. I'm on vacation right now but when I get back I can take a look a implementing that.


Implementation details / example required?

I was looking at GpioController with a view to building a library for some custom PC hardware.
I found someone asking the same questions, and implemented
public  class MyGpioProvider : IGpioProvider
public  class MyGpioPinProvider : IGpioPinProvider
public  class MyGpioControllerProvider : IGpioControllerProvider
but I couldn't see how to wire in the new classes so that we could use
var gpio = GpioController.GetDefault();
I was misled by the names ending in "Provider" - these are not providers in the regular sense, they don't derive from ProviderBase they are simply interfaces, as denoted by the "I" at the front and I can't find an abstract factory to instantiate one. Also as they deal with hardware (unmanaged resources), shouldn't they implement IDisposable?
After much boogling, I discovered
LowLevelDevicesController.DefaultProvider = new SimulatedProvider.AggregateProvider();
and after implementing an AggregateProvider, it did indeed return a MyGpioController object.
However
GpioController.GetDefault() returns a GpIoController, not IGpioControllerProvider, so not quite there yet.
Also I can't find a way of adding more than one, so the method
public static IAsyncOperation<IReadOnlyList<MyGpioController>> GetControllersAsync(IGpioProvider provider)
seems rather redundant, and potentially broken - it takes a parameter IGpioProvider but returns a list of MyGpioController?
All told, the whole thing seems a little half-baked, I'm really not sure its worth the effort.

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

ID: e5edd752-2d2c-152d-3d92-5b612bfec73e
Version Independent ID: 4cbe1b61-b319-8507-9f3b-6d5b86e44e6b
Content: Windows.Devices.Gpio.Provider Namespace - Windows UWP applications
Content Source: https://cpubwin.visualstudio.com/DefaultCollection/windows-uwp/_git/winrt-api-build?path=%2fwinrt-api-build%2fwindows.devices.gpio.provider.yml&version=GBlive&_a=contents
Product: uwp
Technology: winrt-reference
Git Login: eliotcowley
Microsoft Alias: elcowle

Hi, @bjthomson. Thanks for filing this issue, and my apologies for the delay in responding.
I've reached out to the feature team for more info/clarification here, and in case we need to add more content.
Thanks again!
Steve

I'll go ahead and close this issue now since it's been a while, and it feels resolved. Please reopen if I made a mistake in closing. ~Steve


Derlys/ui content

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


[iOS build warnings] Remove deprecation warning for RCTExecuteOnMainThread

As per @janicduplessis recommendation, provide a new synchronous method to replace the necessary synchronous calls and use a warning in the comments (and method name).
Motivation
There are currently a number of XCode warnings that show up in a fresh 0.40 install of a react native project. While the project can still be run, this contributes negatively to the development experience -- valid warnings may be ignored and new ones may be added as per https://en.wikipedia.org/wiki/Broken_windows_theory
This addresses one of the warnings, by providing the functionality of a deprecated method in two specific cases where we can't avoid doing synchronous work on the main queue. See https://github.com/facebook/react-native/issues/11736 for more context.
Test plan (required)
I ran a project that relied on screen size and it didn't crash...happy to do more involved testing if someone can share better methodology.

Looks good, thanks for doing this. Would you be interested in sending a followup PR that deletes the deprecated method?
@facebook-github-bot shipit

@ide looks like there are a few third party components that still rely on this https://github.com/search?p=1&q=RCTExecuteOnMainThread&type=Code&utf8=✓
How long do things generally stay deprecated for before being removed? Happy to remove it for 0.41 if you think that's enough warning for people, although it should be mentioned in release notes as well, let me know how to indicate that.

This would ship with 0.42 and we'd announce the breaking in the release notes when the RC is cut (in about 3 weeks). Then 0.42 final would ship a month after that, so in total people have about 7 weeks of advance notice if they're following master (which most people don't) and a month's notice from the RC's release notes.

Looks like most of the results are RN forks so it shouldn't be too bad.


Added a new animated button.[gssoc23]

I have added a new animated button as assigned.

Hi, there seems to be a merge conflict, please resolve it

I have resolved it @PoorviShetty @Spyware007

@Binitha12
Looking forward to more contributions from you. 🧑💻

Thank you so much for your contribution.🌟
Make sure to ⭐ and follow me.

I would love to connect with you all ❤

https://www.linkedin.com/in/om-gawande/


Recaptcha rate limit and headless issue

Trying this out and have a couple issues Im hoping I can get assistance with.
In headless mode it never seems to work, I get an error that that recaptcha limit has been exceeded. It will generally work in headed mode however. I am using the chromium browser and this does not seem to be an issue when using this with FireFox. Also, this is on a site OTHER than the demo google site.
any advice?
Thanks!

Google is most likely detecting headless chromium as being automated. When Google detects requests that are most likely coming from an automated source (either by an automated browser or script), then they will display an error message. An easy workaround for this is using Firefox as you mentioned. You could also try using the playwright-stealth library, although I cannot confirm this will help.

Not working ((

playwright_recaptcha.errors.RecaptchaTimeoutError: The reCAPTCHA solve timeout has been exceeded.

playwright_recaptcha.errors.RecaptchaTimeoutError: The reCAPTCHA solve timeout has been exceeded.

Hello, could you please open a separate issue


Macro for setting the contract's state version in the compiled binary

The purpose of the new macro is to provide the contract's state version directly in the contract's binary. Once provided, the VM could implement the conditional migrate call procedure to reduce redundant migrate entry point calling.
Procedural attribute-like macro
A proc-macro that can be called on the migrate entry point only.
#[entry_point]
#[set_contract_state_version(3)]
pub fn migrate(deps: DepsMut, env: Env, info: MigrateInfo, _msg: MigrateContract) -> StdResult<Response> {
    // [...]
}

I personally think a good solution would be something like cw_contract_state_version as the name of a custom section, and the value is just the value of the version
(maybe as an integer, maybe we could also make the affordance and enforce it to be UTF-8 bytes, therefore allowing for more complex versions, such as SemVer-encoded versions)

Another thing to keep in mind: If we want to have tests for this (and we most definitely do), creating a WASM binary from WAT with a custom section requires the payload to be a string, simply because of how the WAT is defined.
The binary format has no such limitations.
For example, this works, but this does not, so if we want to write tests in WAT, then we pretty much have to choose strings.
Otherwise we can try to assemble these things ourselves by using wasm-encoder

I would like the value to be readable using wasm-objdump (see notes here for the working title cw2++). This would then also require the value to be a string and not some big endian number.

Okay, now that we pretty much settled on using strings, should we enforce the usage of something like SemVer? Because that way it's nicely structured from a user point of view, and we can do easy comparisons whether the contract is newer, older, or the same version.

In the context of state versioning, I don't see a value in using anything non-integer. It just adds complexity but what you need is incremental steps for migrations.

Almost:

If state_version_new_code  != state_version_old_code, wasmd calls the migrate entry point of the contract. Otherwise the code is swapped but the migrate implementation is bypassed
In fn migrate( the contract developer gets the old version and can do anything smart with that information. You can imagine an implementation in version 5 that is able to migrate from 2, 3 and 4 but not 1.

the contract developer gets the old version and can do anything smart with that information

Fair, I was thinking in terms of lock-step migration, but that makes sense.

After #2124 what we also need is a function in the VM that can read the version from a contract by checksum. Wasmd could do that directly but then we'd have to copy the whole Wasm blob around. The VM can implement that more efficiently and in Rust.

The VM can implement that more efficiently and in Rust.

Yeah, it's actually also not that hard to implement. wasmparser and then just step through the components.


Pagination not restored on reload()

Having modified the item list via Ajax/javascript, the pagination still retains the old number of items and doesn't update when list is scrolled after calling reload().
Is there a way to 'reload' the pagination?

Hi Jan,
Thanks for Jcarousel !
When you press the button pagination I upload new ellementy carousel and then reload carousel. This becomes the first active ellement. How can I make the active ellement which I pressed?


Create Start-PSRelease helper function

Addresses first two items in #2712
The intention is to make release process easier and put safety checks everywhere to reduce the probability of creating a bad package.
The command is wrapper of Start-PSPackage that follows https://github.com/PowerShell/PowerShell/blob/master/docs/maintainers/releasing.md

[ ] releasing.md updated
[ ] verified on Windows
[ ] verified on macOS
[ ] verified on Linux

Usage
Start-PSRelease -CommitSHA1 <commit> -Name v6.0.0-alpha.13

@vors I kind of want this merged, even in an incomplete state so that we can continue adding to it. I scripted Windows image generation during the last release and I could add that as my contribution to this function.

@mirichmo great, want to merge it then?


Missing try statement

The code sample to retrieve an answer needs a "try" statement at the beginning to match the "except" statement.

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

ID: 08b2163b-b0c8-1976-a753-421b8b17f54b
Version Independent ID: dfb1d831-867d-50e0-cfdb-0226dec7a9a5
Content: Quickstart: Get answer from knowledge base - REST, Python - QnA Maker
Content Source: articles/cognitive-services/QnAMaker/Quickstarts/get-answer-from-knowledge-base-python.md
Service: cognitive-services
Sub-service: qna-maker
GitHub Login: @diberry
Microsoft Alias: diberry

@GraemeMalcolm Thank you for your feedback, we will investigate it and get back to you soon.

@GraemeMalcolm  Hi Graeme, it has been fixed. Thank you for your feedback. We will now proceed to close this thread. If there are further questions regarding this matter, please respond here and @YutongTie-MSFT and we will gladly continue the discussion.

Hello Sir, this code sample is not working for me. I'm getting socket error. What does that mean and how should I rectify?.

@sruthiiyer Can you please post your code (removing your key value) and the exact error?


Importing WorkflowGenerator from scriptcwl does not work

When trying to import WorkflowGenerator (from scriptcwl import WorkflowGenerator) I get "cannot import name validate_document".
I tried on a clean environment with python 2.7 and python 3, both failed.
Initially, I was trying to run the ICDAR2017_shared_task_workflows notebook from ochre

I fixed that last week! If you install the development version (so, cloning the repository, and not using pip), it should work.

Thanks a lot !


WIP: GH-41169: [CI][Release] Pin CMake temporary to test Windows verification

Rationale for this change
I am testing if the issue on the verification job is due to CMake 3.29.2
What changes are included in this PR?
Only pinning to test the Windows verification
Are these changes tested?
Archery job
Are there any user-facing changes?
No

GitHub Issue: #41169

I'm trying --build-config Release in #41178.

Thanks @kou! I am closing this


Connection problem or invalid lnurl / lightning address.

Describe the bug
I tried to send sats to a video youtube and I see this error: Connection problem or invalid lnurl / lightning address.
Screenshots (If Any)

To Reproduce
Steps to reproduce the behavior:
1- Go to: https://www.youtube.com/watch?v=PqNRpStZRAE
2- Go to blue alby icon from extension and try to send sats
Expected behavior
Able to send sats
Alby information

Alby Version: 1.15.1

@im-adithya can you have a look at this. the algorithm is confused with the tipping .me URL. We need to adjust it that it does not match characters like : or /


add tests for use ImmutableTriple as key in java.util.HashMap and java.util.TreeMap

add tests for use ImmutableTriple as key in java.util.HashMap and java.util.TreeMap

Coverage remained the same at 95.233% when pulling 29937f04c6de046ca3456305cdaece81a913b73b on apirom9:tasks/add-tests-for-immutable-triple into 0fcd4ce92ad860a47ae85b1fc7b7e5cd35c8738e on apache:master.

@apirom9 does this pull request number #379 supersedes yours previous one, number  #378? It looks to me like the tests from #378 are present in this pull request too? If so then we should close #378 to avoid confusion when reviewing & merging.
Thanks
Bruno

@kinow Yes, it is. Sorry for my mistake, I already close pull request #378
Thank you
Apirom


Allow proxy passthrough list

This pull request allows users to configure the proxy to ignore certain URL paths. The pattern format only allows an asterisk as a wildcard. For example, /assets/* would match all URLs with a /assets/ path prefix. It would not, however, match /assets. This can be used for matching suffixes (e.g. *.png) and infixes (*foo*) as well.
Fixes #275
Usage
The litefs.yml config file now has a proxy.passthrough field:
proxy:
  addr:   ":8080"
  target: "localhost:8081"
  db:     "my.db"
  passthrough:
    - "/debug*"
    - "*.png"

or you can use the JSON array syntax:
proxy:
  addr:   ":8080"
  target: "localhost:8081"
  db:     "my.db"
  passthrough: ["/debug/*", "*.png"]

The staticcheck failure looks like it's coming from an upgraded bazil.org/fuse dependency. I'll fix that in a separate PR.

@kentcdodds I add the passthrough functionality. I opted for a simpler asterisk-only wildcard format. I feel like regular expression matching on URL paths involves a lot of escaping. :)
I tested this on a small test app and it's working well. I enabled proxy.debug so I could see the logging. You should see messages that look like this if they're matching a passthrough:
proxy: GET /favicon.ico: matches passthrough expression, proxying to target

Let me know if this works for you and I'll merge in.

I went ahead and merged. We can tweak it if you have any issues.

I'm pushing a passthrough config now. If you don't hear from me then it worked great :)

It didn't go well. I wasn't watching logs when it deployed, but now I'm getting a lot of:
error.message="could not send HTTP request to instance: connection error: timed out" 2023-02-06T17:25:28Z proxy[ce89afef] den [error]request.method="POST" request.id="01GRKW3XVE3DNDPEGBZA1JXB3H-lhr"
error.message="could not send HTTP request to instance: connection error: timed out" 2023-02-06T17:25:33Z proxy[ce89afef] den [error]request.method="GET" request.id="01GRKW41XZKQPR0CZBNVB5BWVW-cdg"
error.message="could not send HTTP request to instance: connection error: timed out" 2023-02-06T17:25:35Z proxy[ce89afef] den [error]request.method="GET" request.id="01GRKW44JW336A65JMSX2Y0NW8-cdg"
error.message="could not send HTTP request to instance: connection error: timed out" 2023-02-06T17:25:57Z proxy[ce89afef] den [error]request.method="GET" request.id="01GRKW4SM3MBT72AB2S8M0K3G0-fra"
error.message="could not send HTTP request to instance: connection error: timed out" 2023-02-06T17:25:59Z proxy[ce89afef] den [error]request.method="GET" request.id="01GRKW4VJK2HW5C1AQA8SJDC99-fra"
error.message="could not send HTTP request to instance: connection error: timed out" 2023-02-06T17:26:02Z proxy[ce89afef] den [error]request.method="GET" request.id="01GRKW4Y9JBF44HMJA0MZFNCJC-jnb"
error.message="could not send HTTP request to instance: connection error: timed out" 2023-02-06T17:26:02Z proxy[ce89afef] den [error]request.method="GET" request.id="01GRKW4Y9K8ZT11PPJ6A82KBS2-jnb"
error.message="could not send HTTP request to instance: connection error: timed out" 2023-02-06T17:26:02Z proxy[ce89afef] den [error]request.method="GET" request.id="01GRKW4Y9K0RW0WN6CPMRV0BVR-jnb"
error.message="could not send HTTP request to instance: connection error: timed out" 2023-02-06T17:26:02Z proxy[ce89afef] den [error]request.method="GET" request.id="01GRKW4Y9N9KSZQJ6JB60H544Y-jnb"
error.message="could not send HTTP request to instance: connection error: timed out" 2023-02-06T17:26:02Z proxy[ce89afef] den [error]request.method="GET" request.id="01GRKW4Y9NKXGBBJ7ET52TJ77R-jnb"
error.message="could not send HTTP request to instance: connection error: timed out" 2023-02-06T17:26:02Z proxy[ce89afef] den [error]request.method="GET" request.id="01GRKW4Y9KXNCP3BMJFZ3CT92R-jnb"
error.message="could not send HTTP request to instance: connection error: timed out" 2023-02-06T17:26:03Z proxy[ce89afef] den [error]request.method="GET" request.id="01GRKW5068NN59EN7A11N4BGE5-cdg"
error.message="could not send HTTP request to instance: connection error: timed out" 2023-02-06T17:26:07Z proxy[ce89afef] den [error]request.method="GET" request.id="01GRKW53YBMWFWJ4BEH3B3HA0R-ams"
error.message="could not send HTTP request to instance: connection error: timed out" 2023-02-06T17:26:11Z proxy[ce89afef] den [error]request.method="GET" request.id="01GRKW57HF78QE5NZR58E19EXH-cdg"
error.message="could not send HTTP request to instance: connection error: timed out" 2023-02-06T17:26:12Z proxy[ce89afef] den [error]request.method="GET" request.id="01GRKW589ST4RFF4GEXZKVA5Z5-lax"
error.message="could not send HTTP request to instance: connection error: timed out" 2023-02-06T17:26:17Z proxy[ce89afef] den [error]request.method="POST" request.id="01GRKW5DRGHYA0QEA4744PV2DY-gru"
error.message="could not send HTTP request to instance: connection error: timed out" 2023-02-06T17:26:18Z proxy[ce89afef] den [error]request.method="POST" request.id="01GRKW5E8QEZVD4F6J6SCN7CB1-jnb"
error.message="could not send HTTP request to instance: connection error: timed out" 2023-02-06T17:26:24Z proxy[ce89afef] den [error]request.method="GET" request.id="01GRKW5KVSA8YYP7F9BCAPF7XX-yul"
error.message="could not send HTTP request to instance: connection error: timed out" 2023-02-06T17:26:25Z proxy[ce89afef] den [error]request.method="POST" request.id="01GRKW5MYZ4ZFQ0QQHP2WVAW21-bos"
error.message="could not send HTTP request to instance: connection error: timed out" 2023-02-06T17:26:25Z proxy[ce89afef] den [error]request.method="GET" request.id="01GRKW5MTQP4Q3MAPFQ53ZF1HM-maa"
error.message="could not send HTTP request to instance: connection error: timed out" 2023-02-06T17:26:29Z proxy[ce89afef] den [error]request.method="GET" request.id="01GRKW5S1PNR1GNJPCYRM6SZ50-lax"
error.message="could not send HTTP request to instance: connection error: timed out" 2023-02-06T17:26:36Z proxy[ce89afef] den [error]request.method="POST" request.id="01GRKW60DN985GM5ZXWPNZHZ8V-fra"
error.message="could not send HTTP request to instance: connection error: timed out" 2023-02-06T17:26:37Z proxy[ce89afef] den [error]request.method="GET" request.id="01GRKW60WXR215V8B2A8QG1DFJ-yyz"
error.message="could not send HTTP request to instance: connection error: timed out" 2023-02-06T17:26:42Z proxy[ce89afef] den [error]request.method="GET" request.id="01GRKW65E91NHZ9XZDTV8B571P-dfw"
error.message="could not send HTTP request to instance: connection error: timed out" 2023-02-06T17:26:48Z proxy[ce89afef] den [error]request.method="GET" request.id="01GRKW6BTN3T2VTTPGZWV5STZK-ams"
error.message="could not send HTTP request to instance: connection error: timed out" 2023-02-06T17:26:49Z proxy[ce89afef] den [error]request.method="GET" request.id="01GRKW6CPJGRQQEVQZ0JPR5G8K-fra"
error.message="could not send HTTP request to instance: connection error: timed out" 2023-02-06T17:26:55Z proxy[ce89afef] den [error]request.method="GET" request.id="01GRKW6JPZSW4MD8H42XX844TT-arn"
error.message="could not send HTTP request to instance: connection error: timed out" 2023-02-06T17:26:59Z proxy[ce89afef] den [error]request.method="GET" request.id="01GRKW6PA2Q4HMX9M4T865DMZ0-maa"
error.message="could not send HTTP request to instance: connection error: timed out" 2023-02-06T17:27:03Z proxy[ce89afef] den [error]request.method="GET" request.id="01GRKW6SX2NC8CGFRFZEDP6PEP-jnb"
error.message="could not send HTTP request to instance: connection error: timed out" 2023-02-06T17:27:10Z proxy[ce89afef] den [error]request.method="GET" request.id="01GRKW70T1G0VSZDAW1NA8TNEY-fra"
error.message="could not send HTTP request to instance: connection error: timed out" 2023-02-06T17:27:12Z proxy[ce89afef] den [error]request.method="GET" request.id="01GRKW72TQWJB0ZD5F13AAJRSM-ams"
error.message="could not send HTTP request to instance: connection error: timed out" 2023-02-06T17:27:16Z proxy[ce89afef] den [error]request.method="GET" request.id="01GRKW76PTFKS2NJYHBA5VHPG0-jnb"
error.message="could not send HTTP request to instance: connection error: timed out" 2023-02-06T17:27:16Z proxy[ce89afef] den [error]request.method="GET" request.id="01GRKW76QSM3KHWA72JVRSBNJV-arn"
error.message="could not send HTTP request to instance: connection error: timed out" 2023-02-06T17:27:32Z proxy[ce89afef] den [error]request.method="GET" request.id="01GRKW7Q1DD4M2PNVQNFHB512X-lax"
error.message="could not send HTTP request to instance: connection error: timed out" 2023-02-06T17:27:33Z proxy[ce89afef] den [error]request.method="GET" request.id="01GRKW7Q5A2241G88G440SDK2D-lhr"
error.message="could not send HTTP request to instance: connection error: timed out" 2023-02-06T17:27:36Z proxy[ce89afef] den [error]request.method="GET" request.id="01GRKW7TFM78720NFYNYYE6BMQ-yyz"
2023-02-06T17:27:49Z proxy[ce89afef] den [error]could not send HTTP request to instance: connection error: timed out

Here's the commit: https://github.com/kentcdodds/kentcdodds.com/commit/d59a041d9978617174a74886e935706d4c01e356
I'm pushing a revert commit right now. I'm not sure what went wrong.
Seems like it shouldn't have passed health checks though 🤔

Ah, looks like the logs I have include the bad deploy logs:
error.message="could not find an instance to route to" 2023-02-06T17:22:55Z proxy lhr [warn]request.method="POST" request.url="https://kentcdodds.com/__metronome" request.id="01GRKW0MDSRCVM681P79N2ECXA-lhr"
error.message="could not find an instance to route to" 2023-02-06T17:22:55Z proxy lhr [warn]request.method="POST" request.url="https://kentcdodds.com/__metronome" request.id="01GRKW12YWB5YVGYKW6XY5NFVF-lhr"
error.message="could not find an instance to route to" 2023-02-06T17:22:55Z proxy iad [warn]request.method="POST" request.url="https://kentcdodds.com/__metronome" request.id="01GRKW0YXF9TBH5NHC1PTXREEJ-iad"
error.message="could not find an instance to route to" 2023-02-06T17:22:55Z proxy lhr [warn]request.method="POST" request.url="https://kentcdodds.com/__metronome" request.id="01GRKW137S8FAA2BQ3VTF1FM7P-lhr"
error.message="could not find an instance to route to" 2023-02-06T17:22:56Z proxy jnb [warn]request.method="POST" request.url="https://kentcdodds.com/__metronome" request.id="01GRKW0CKWNT5EKA3V3MK9A2HX-jnb"
2023-02-06T17:22:57Z runner[ce89afef] den [info]Preparing kernel init
2023-02-06T17:22:57Z runner[ce89afef] den [info]Setting up volume 'data'
2023-02-06T17:22:57Z runner[ce89afef] den [info]Opening encrypted volume
2023-02-06T17:22:58Z runner[ce89afef] den [info]Configuring firecracker
2023-02-06T17:22:58Z runner[ce89afef] den [info]Starting virtual machine
2023-02-06T17:22:58Z app[ce89afef] den [info]Starting init (commit: e3cff9e)...
2023-02-06T17:22:58Z app[ce89afef] den [info]Mounting /dev/vdc at /data w/ uid: 0, gid: 0 and chmod 0755
2023-02-06T17:22:58Z app[ce89afef] den [info]Preparing to run: `docker-entrypoint.sh litefs mount -- node ./other/start.js` as root
2023-02-06T17:22:58Z app[ce89afef] den [info]2023/02/06 17:22:58 listening on [fdaa:0:23df:a7b:d828:4:263a:2]:22 (DNS: [fdaa::3]:53)
2023-02-06T17:22:58Z app[ce89afef] den [info]config file read from /etc/litefs.yml
2023-02-06T17:22:58Z app[ce89afef] den [info]LiteFS main, commit=9ff02a303b5fc2e5c8bef5a173ab96dc4ab1c393
2023-02-06T17:22:58Z app[ce89afef] den [info]Using Consul to determine primary
error.message="could not find an instance to route to" 2023-02-06T17:22:58Z proxy iad [warn]request.method="POST" request.url="https://kentcdodds.com/__metronome" request.id="01GRKW0R0VHV7AW8NZZAXVM3AS-iad"
error.message="could not find an instance to route to" 2023-02-06T17:22:59Z proxy lax [warn]request.method="GET" request.url="https://kentcdodds.com/blog/static-vs-unit-vs-integration-vs-e2e-tests" request.id="01GRKW0ESDP9QQKVKZ2C4DD3EG-lax"
error.message="could not find an instance to route to" 2023-02-06T17:22:59Z proxy lhr [warn]request.method="POST" request.url="https://kentcdodds.com/__metronome" request.id="01GRKW12YWB5YVGYKW6XY5NFVF-lhr"
error.message="could not find an instance to route to" 2023-02-06T17:22:59Z proxy lhr [warn]request.method="POST" request.url="https://kentcdodds.com/__metronome" request.id="01GRKW05NC3W3JVGT4YTK3M0P4-lhr"
error.message="could not find an instance to route to" 2023-02-06T17:23:00Z proxy lhr [warn]request.method="POST" request.url="https://kentcdodds.com/__metronome" request.id="01GRKW137S8FAA2BQ3VTF1FM7P-lhr"
2023-02-06T17:23:00Z app[ce89afef] den [info]initializing consul: key=litefs/kcd<EMAIL_ADDRESS>hostname=ce89afef advertise-url=http://ce89afef.vm.kcd.internal:20202
2023-02-06T17:23:00Z app[ce89afef] den [info]wal-sync: no wal file exists on "cache.db", skipping sync with ltx
2023-02-06T17:23:01Z app[ce89afef] den [info]wal-sync: no wal file exists on "sqlite.db", skipping sync with ltx
2023-02-06T17:23:01Z app[ce89afef] den [info]ERROR: cannot init file system: cannot open file system: fusermount: exec: "fusermount3": executable file not found in $PATH
2023-02-06T17:23:01Z app[ce89afef] den [info]waiting for signal or subprocess to exit
2023-02-06T17:23:01Z app[ce89afef] den [info]6515368117173208084CEBF0: primary lease acquired, advertising as http://ce89afef.vm.kcd.internal:20202
error.message="could not send HTTP request to instance: connection error: timed out" 2023-02-06T17:24:02Z proxy[ce89afef] den [error]request.method="POST" request.id="01GRKW0CKWNT5EKA3V3MK9A2HX-jnb"
error.message="could not send HTTP request to instance: connection error: timed out" 2023-02-06T17:24:02Z proxy[ce89afef] den [error]request.method="GET" request.id="01GRKW191ZWQQ0X54KNXHBKADY-gig"
error.message="could not send HTTP request to instance: connection error: timed out" 2023-02-06T17:24:02Z proxy[ce89afef] den [error]request.method="POST" request.id="01GRKW0MDSRCVM681P79N2ECXA-lhr"
error.message="could not send HTTP request to instance: connection error: timed out" 2023-02-06T17:24:02Z proxy[ce89afef] den [error]request.method="POST" request.id="01GRKW137S8FAA2BQ3VTF1FM7P-lhr"
error.message="could not send HTTP request to instance: connection error: timed out" 2023-02-06T17:24:04Z proxy[ce89afef] den [error]request.method="POST" request.id="01GRKW1BMY2MHQR77Q123F8R6J-jnb"
error.message="could not send HTTP request to instance: connection error: timed out" 2023-02-06T17:24:12Z proxy[ce89afef] den [error]request.method="POST" request.id="01GRKW1K3WWNYRFK93RWWB40HP-ams"
error.message="could not send HTTP request to instance: connection error: timed out" 2023-02-06T17:24:14Z proxy[ce89afef] den [error]request.method="GET" request.id="01GRKW1MVDAS6MRRYVRR53FFC9-fra"
error.message="could not send HTTP request to instance: connection error: timed out" 2023-02-06T17:24:16Z proxy[ce89afef] den [error]request.method="POST" request.id="01GRKW1Q53MRNN0J24QHYMK7Y8-lhr"
error.message="could not send HTTP request to instance: connection error: timed out" 2023-02-06T17:24:21Z proxy[ce89afef] den [error]request.method="POST" request.id="01GRKW1WB9KFDZK0FVA89W9HC1-arn"
error.message="could not send HTTP request to instance: connection error: timed out" 2023-02-06T17:24:28Z proxy[ce89afef] den [error]request.method="GET" request.id="01GRKW23766WN1SJF5YV1W5DDY-ams"
error.message="could not send HTTP request to instance: connection error: timed out" 2023-02-06T17:24:35Z proxy[ce89afef] den [error]request.method="GET" request.id="01GRKW29SN652PE7M4H4B03N9A-yyz"
error.message="could not send HTTP request to instance: connection error: timed out" 2023-02-06T17:24:50Z proxy[ce89afef] den [error]request.method="GET" request.id="01GRKW2R1W5VV0SBXRWCRNCW5E-fra"
error.message="could not send HTTP request to instance: connection error: timed out" 2023-02-06T17:24:53Z proxy[ce89afef] den [error]request.method="GET" request.id="01GRKW2V9ZKB6YRH9T6XWR456A-waw"
error.message="could not send HTTP request to instance: connection error: timed out" 2023-02-06T17:24:53Z proxy[ce89afef] den [error]request.method="GET" request.id="01GRKW2VA061Z2T4MNWG3B7AFG-waw"
error.message="could not send HTTP request to instance: connection error: timed out" 2023-02-06T17:24:56Z proxy[ce89afef] den [error]request.method="POST" request.id="01GRKW2YPZYRQR8FC4N9XDK6W7-waw"
error.message="could not send HTTP request to instance: connection error: timed out" 2023-02-06T17:25:01Z proxy[ce89afef] den [error]request.method="GET" request.id="01GRKW334AG4KCRYD3BSFNQ7B8-lhr"
error.message="could not send HTTP request to instance: operation was canceled: request has been canceled" 2023-02-06T17:25:02Z proxy[ce89afef] jnb [warn]request.method="GET" request.url="https://kentcdodds.com/build/_shared/chunk-24YL4M67.js" request.id="01GRKW4Y9KXNCP3BMJFZ3CT92R-jnb"
error.message="could not send HTTP request to instance: operation was canceled: request has been canceled" 2023-02-06T17:25:02Z proxy[ce89afef] jnb [warn]request.method="GET" request.url="https://kentcdodds.com/build/routes/about-XELTKZA5.js" request.id="01GRKW4Y9JBF44HMJA0MZFNCJC-jnb"
error.message="could not send HTTP request to instance: operation was canceled: request has been canceled" 2023-02-06T17:25:02Z proxy[ce89afef] jnb [warn]request.method="GET" request.url="https://kentcdodds.com/build/_shared/chunk-O7KWAUU4.js" request.id="01GRKW4Y9K0RW0WN6CPMRV0BVR-jnb"
error.message="could not send HTTP request to instance: operation was canceled: request has been canceled" 2023-02-06T17:25:02Z proxy[ce89afef] jnb [warn]request.method="GET" request.url="https://kentcdodds.com/build/_shared/chunk-VU65GJMD.js" request.id="01GRKW4Y9NKXGBBJ7ET52TJ77R-jnb"
error.message="could not send HTTP request to instance: operation was canceled: request has been canceled" 2023-02-06T17:25:02Z proxy[ce89afef] jnb [warn]request.method="GET" request.url="https://kentcdodds.com/build/_shared/chunk-XJWXA63U.js" request.id="01GRKW4Y9K8ZT11PPJ6A82KBS2-jnb"
error.message="could not send HTTP request to instance: operation was canceled: request has been canceled" 2023-02-06T17:25:02Z proxy[ce89afef] jnb [warn]request.method="GET" request.url="https://kentcdodds.com/build/_shared/chunk-GTQJJ7P5.js" request.id="01GRKW4Y9N9KSZQJ6JB60H544Y-jnb"
error.message="could not send HTTP request to instance: connection error: timed out" 2023-02-06T17:25:02Z proxy[ce89afef] den [error]request.method="GET" request.id="01GRKW33XR1HXX99KBGWHGAJMZ-lax"
error.message="could not send HTTP request to instance: connection error: timed out" 2023-02-06T17:25:02Z proxy[ce89afef] den [error]request.method="GET" request.id="01GRKW33XR5JN8FYE1DBF4KPPM-lax"
error.message="could not send HTTP request to instance: connection error: timed out" 2023-02-06T17:25:02Z proxy[ce89afef] den [error]request.method="GET" request.id="01GRKW33XSX5S72VBKEKKVK8AF-lax"
error.message="could not send HTTP request to instance: connection error: timed out" 2023-02-06T17:25:02Z proxy[ce89afef] den [error]request.method="GET" request.id="01GRKW33XRVWABY2QTAZZ8SS61-lax"
error.message="could not send HTTP request to instance: connection error: timed out" 2023-02-06T17:25:02Z proxy[ce89afef] den [error]request.method="GET" request.id="01GRKW33XR7PVRTBHA0ZSNC97K-lax"
error.message="could not send HTTP request to instance: connection error: timed out" 2023-02-06T17:25:02Z proxy[ce89afef] den [error]request.method="GET" request.id="01GRKW33XSK6BB9Y3S8Z7AV5QQ-lax"
error.message="could not send HTTP request to instance: operation was canceled: request has been canceled" 2023-02-06T17:25:02Z proxy[ce89afef] lax [warn]request.method="GET" request.url="https://kentcdodds.com/blog/common-mistakes-with-react-testing-library" request.id="01GRKW4YQARNCNN3NE54HQX8PH-lax"
error.message="could not send HTTP request to instance: connection error: timed out" 2023-02-06T17:25:05Z proxy[ce89afef] den [error]request.method="GET" request.id="01GRKW377M558N8QGWNW0WPF2X-lax"
error.message="could not send HTTP request to instance: connection error: timed out" 2023-02-06T17:25:12Z proxy[ce89afef] den [error]request.method="GET" request.id="01GRKW3DJQZ44ETPETTHBW1G3M-lax"
error.message="could not send HTTP request to instance: connection error: timed out" 2023-02-06T17:25:12Z proxy[ce89afef] den [error]request.method="GET" request.id="01GRKW3EFXDB26R7YFKENYXP2B-fra"
error.message="could not send HTTP request to instance: connection error: timed out" 2023-02-06T17:25:13Z proxy[ce89afef] den [error]request.method="GET" request.id="01GRKW3F63PVY9Q9YGJGHRGRRZ-waw"
error.message="could not send HTTP request to instance: connection error: timed out" 2023-02-06T17:25:14Z proxy[ce89afef] den [error]request.method="GET" request.id="01GRKW3FYWWBR0Z53DSQF1ENQS-fra"
error.message="could not send HTTP request to instance: connection error: timed out" 2023-02-06T17:25:17Z proxy[ce89afef] den [error]request.method="GET" request.id="01GRKW3JM3Q9G8DV8CFQSAGEZ3-lax"
error.message="could not send HTTP request to instance: connection error: timed out" 2023-02-06T17:25:24Z proxy[ce89afef] den [error]request.method="GET" request.id="01GRKW3SY9TSCRH03EAAVCBVJB-sjc"
error.message="could not send HTTP request to instance: connection error: timed out" 2023-02-06T17:25:28Z proxy[ce89afef] den [error]request.method="POST" request.id="01GRKW3XVE3DNDPEGBZA1JXB3H-lhr"

Based on this I realized that the reason I'm having the problem is because this version includes the fuse3 requirement 🤦♂
Trying again.

I should have the proxy shut down if LiteFS is unable to mount. I’ll add a fix for that.

@kentcdodds The write forwarding work sidetracked me for a while but I finally got this fixed. The proxy now shuts down if there's an error on startup and exit-on-error is false. https://github.com/superfly/litefs/pull/284

Thanks for the update!


[WIP] Add support for tracking dimesions/metrics

Params are line with the way GA handles these:

cd<Index>=value for dimensions
cm<Index>=value for metrics

Because we need access to the hit we have to call build_<type>

Just a bump on this when you have a moment @timriley


cargo liquid 编译合约错误

根据说明文档 https://liquid-doc.readthedocs.io/zh_CN/latest/docs/quickstart/prerequisite.html 配置好环境之后。
尝试编译 HelloWorld 例子合约，开始遇到 proc-macro2 等一些依赖库报错，在修改 HelloWorld 示例合约部分依赖库版本之后继续编译，提示需要 edition2021 特性，编译出现如下错误：
[1/4] 🔍  Collecting crate metadata
[2/4] 🚚  Building cargo project
error: failed to parse manifest at `/tmp/cargo-xbuildqtQwtT/Cargo.toml`

Caused by:
  feature `edition2021` is required

  consider adding `cargo-features = ["edition2021"]` to the manifest
ERROR: Building with xargo

Caused by:
    `"/home/john/.rustup/toolchains/nightly-2021-06-23-x86_64-unknown-linux-gnu/bin/cargo" "rustc" "-p" "alloc" "--release" "--manifest-path" "/tmp/cargo-xbuildqtQwtT/Cargo.toml" "--target" "wasm32-unknown-unknown" "--" "-Z" "force-unstable-if-unmarked"` failed with exit code: Some(101)

根据提示修改 Cargo.toml，在文件顶部增加 cargo-features = ["edition2021"]，报错如下：
[1/4] 🔍  Collecting crate metadata
[2/4] 🚚  Building cargo project
   Compiling core v0.0.0 (/home/john/.rustup/toolchains/nightly-2021-06-23-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/core)
   Compiling compiler_builtins v0.1.45
   Compiling rustc-std-workspace-core v1.99.0 (/home/john/.rustup/toolchains/nightly-2021-06-23-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/rustc-std-workspace-core)
   Compiling alloc v0.0.0 (/tmp/cargo-xbuildLJMsg2)
    Finished release [optimized] target(s) in 19.60s
error[E0463]: can't find crate for `std`
  |
  = note: the `wasm32-unknown-unknown` target may not support the standard library
  = note: `std` is required by `predicates_core` because it does not declare `#![no_std]`
  = help: consider building the standard library from source with `cargo build -Zbuild-std`

error: aborting due to previous error

For more information about this error, try `rustc --explain E0463`.
error[E0463]: can't find crate for `std`
  |
  = note: the `wasm32-unknown-unknown` target may not support the standard library
  = note: `std` is required by `bumpalo` because it does not declare `#![no_std]`
  = help: consider building the standard library from source with `cargo build -Zbuild-std`

error: could not compile `predicates-core`

To learn more, run the command again with --verbose.
error: aborting due to previous error

For more information about this error, try `rustc --explain E0463`.
error: build failed
ERROR: xbuild failed with status exit status: 101

目前提供的编译链因为当时使用的版本老旧，很多库已升级（patch不兼容），使得编译链无法正常使用，似乎难以找到整套兼容的依赖。
官方有无好的解决方案，或是当时有无封装可用容器？

现在这个问题是liquid锁定的编译器版本过于老旧导致的，我们已经在着手解决这个问题了
按下述步骤尝试一下

重新安装最新版的caego-liquid

cargo install --git https://github.com/WeBankBlockchain/cargo-liquid --branch main --locked --force

更新合约项目中Cargo.toml的liquid，如下

liquid_lang = { git = "https://github.com/WeBankBlockchain/liquid", rev = "c678d9586b4335fc302a4c02a564d8ee6964be1d", package = "liquid_lang", default-features = false, features = ["contract"] }
liquid_primitives = { git = "https://github.com/WeBankBlockchain/liquid", rev = "c678d9586b4335fc302a4c02a564d8ee6964be1d", package = "liquid_primitives", default-features = false }
liquid_prelude = { git = "https://github.com/WeBankBlockchain/liquid", rev = "c678d9586b4335fc302a4c02a564d8ee6964be1d", package = "liquid_prelude", default-features = false }
liquid_macro = { git = "https://github.com/WeBankBlockchain/liquid", rev = "c678d9586b4335fc302a4c02a564d8ee6964be1d", package = "liquid_macro", default-features = false }
liquid_abi_gen = { git = "https://github.com/WeBankBlockchain/liquid", rev = "c678d9586b4335fc302a4c02a564d8ee6964be1d", package = "liquid_abi_gen", default-features = false, optional = true }

再次编译

已看到最新版本对该问题的解决，非常感谢官方作者的艰苦付出，谢谢！


Not all items in the recyclerview is being added to the pdf

To print a stock list used a scroll view containing recycler view inside it, and for a short amount of data's inside recycler view its working fine but when the amount of item's increase the pdf is only showing the data's at top of the recycler view and not the complete list.
Is there any solution to solve the issue...

@GeorgeSanu05  I already solved it yesterday night. And I will try to push it by today. I will email you when it will be available. Please then update the library version and let me know that is it ok or not. I will help you to resolve your issue. No problem.

@Gkemon  thank you for the reply. I will wait for your response

Hi Sanu, Good day.  please check my new release named  v.2.0 and let me
know that is it working or not. Thank you.
On Wed, Feb 10, 2021 at 4:11 PM GeorgeSanu05<EMAIL_ADDRESS>wrote:

@Gkemon https://github.com/Gkemon thank you for the reply. I will wait
for your response
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/Gkemon/Android-XML-to-PDF-Generator/issues/10#issuecomment-776598778,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AFJOLUWM4HPYRUG7QOU6ILLS6JLVRANCNFSM4XMLUMXQ
.

@Gkemon  thank you so much for helping,
I checked the latest version 2.0 it prints all the items in the recycler view but the only problem I felt in this version in relation to the earlier one is the file is not visible in the provided directory or folder.

yeah sanu, I'm trying to fix it. But now you can get the file path in the
success response. So primarily deal with this file path now.
On Mon, Feb 15, 2021 at 12:38 PM GeorgeSanu05<EMAIL_ADDRESS>wrote:

@Gkemon https://github.com/Gkemon thank you so much for helping,
I checked the latest version 2.0 it prints all the items in the recycler
view but the only problem I felt in this version in relation to the earlier
one is the file is not visible in the provided directory or folder.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/Gkemon/Android-XML-to-PDF-Generator/issues/10#issuecomment-778985829,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AFJOLUSYDA6WU3PFWT7YLSTS7C6M7ANCNFSM4XMLUMXQ
.

And If you find it helpful then you are most welcome to hit a star and
fork. Thank you.
On Mon, Feb 15, 2021 at 6:12 PM G.K. Emon<EMAIL_ADDRESS>wrote:

yeah sanu, I'm trying to fix it. But now you can get the file path in the
success response. So primarily deal with this file path now.
On Mon, Feb 15, 2021 at 12:38 PM GeorgeSanu05<EMAIL_ADDRESS>wrote:

@Gkemon https://github.com/Gkemon thank you so much for helping,
I checked the latest version 2.0 it prints all the items in the recycler
view but the only problem I felt in this version in relation to the earlier
one is the file is not visible in the provided directory or folder.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/Gkemon/Android-XML-to-PDF-Generator/issues/10#issuecomment-778985829,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AFJOLUSYDA6WU3PFWT7YLSTS7C6M7ANCNFSM4XMLUMXQ
.

I am showing data into the views, Recyclerview , but when i create pdf it show only initial views, not loading the json data into the pdf. Can you help me or please provide me a working example of how to create a pdf of network data. Thanks

@hemant00007  First of all, Thanks for your feedback. Can you please confirm that you are using the latest version of this library? It was the bug I already fixed a few days ago. If you are using the latest version then please share your code snippet also (XML and your java code). I will try to fix it if the issue exists yet.

implementation 'com.github.Gkemon:XML-to-PDF-generator:2.3'

@hemant00007  I got your problem bro. In the current implementation of this library, it is possible only to print the items which are showing in recycler view actually. And suppose you wanna print a recycler view that containing 100 items then you need to first load it into the recycler view then print it.
If you think that showing 100 items for the user is a bad user experience then you can do a thing. Create the recycler view with 100 items but don't show it to users. Then just print it when users wants. This  part of the doc will help you very much. Just add your recycler view in a separate layout. Inflate the layout into a view object and finally print it.

Hi @hemant00007 @GeorgeSanu05
Thank you all for the support. Please kindly star and fork and send me the app links you all are using it. If there is no confidentiality then I will list them in my readme.md file.


Add rusbase extension

Description

Screencast

Checklist

[x] I read the extension guidelines
[x] I read the documentation about publishing
[x] I ran npm run build and tested this distribution build in Raycast
[x] I checked that files in the assets folder are used by the extension itself
[x] I checked that assets used by the README are placed outside of the metadata folder

@pernielsentikaer Good evening, it's just a media resource in a different language. You mean I need to translate the searchBar items into English?

Yes, that's not allowed according to the documentation

Okay, I'll fix it soon, thank you

Hello, for some reason there is another file package-lock.json outside the extension folder. I can't delete it. Could you please help me with this problem to get the extension into the store?


Backport more ES patches

Summary of the changes / Why this improves CrateDB
See commits
Checklist

[x] Added an entry in CHANGES.txt for user facing changes
[x] Updated documentation & sql_features table for user facing changes
[x] Touched code is covered by tests
[x] CLA is signed
[x] This does not contain breaking changes, or if it does:

It is released within a major release
It is recorded in CHANGES.txt
It was marked as deprecated in an earlier release if possible
You've thought about the consequences and other components are adapted
(E.g. AdminUI)

seems like https://github.com/crate/crate/pull/10317/files#diff-3fa4e051d3f4f29524dbaa47310ee845R195 is flaky :(

seems like https://github.com/crate/crate/pull/10317/files#diff-3fa4e051d3f4f29524dbaa47310ee845R195 is flaky :(

@kovrus I added a ignore annotation for now. The test was/is flaky upstream as well.


FONT

Type: Bug
Currently I'm learning to program in HTML, I'm in the "FONT SIZE, FONT FACE" phase, but when I use "FONT" it's like it doesn't exist.
VS Code version: Code 1.81.1 (6c3e3dba23e8fadc360aed75ce363ba185c49794, 2023-08-09T22:22:42.175Z)
OS version: Windows_NT x64 10.0.19045
Modes:

System Info

Item
Value

CPUs
AMD A4-4000 APU with Radeon(tm) HD Graphics     (2 x 3232)

GPU Status
2d_canvas: unavailable_softwarecanvas_oop_rasterization: disabled_offdirect_rendering_display_compositor: disabled_off_okgpu_compositing: disabled_softwaremultiple_raster_threads: disabled_offopengl: disabled_offrasterization: disabled_softwareraw_draw: disabled_off_okvideo_decode: disabled_softwarevideo_encode: disabled_softwarevulkan: disabled_offwebgl: unavailable_softwarewebgl2: unavailable_softwarewebgpu: unavailable_software

Load (avg)
undefined

Memory (System)
3.43GB (0.38GB free)

Process Argv
--crash-reporter-id 21bdeb6d-4608-40bf-9f3a-deb26c9321f8

Screen Reader
no

VM
0%

Extensions: none
A/B Experiments
vsliv368:30146709
vsreu685:30147344
python383cf:30185419
vspor879:30202332
vspor708:30202333
vspor363:30204092
vslsvsres303:30308271
vserr242:30382549
pythontb:30283811
vsjup518:30340749
pythonptprofiler:30281270
vshan820:30294714
vstes263:30335439
vscoreces:30445986
vscod805cf:30301675
binariesv615:30325510
bridge0708:30335490
bridge0723:30353136
vsaa593:30376534
pythonvs932:30410667
py29gd2263cf:30792227
vscaac:30438847
vsclangdc:30486549
c4g48928:30535728
dsvsc012:30540252
pynewext54:30695312
azure-dev_surveyone:30548225
vscccc:30803845
2e4cg342:30602488
f6dab269:30613381
vscrp:30673768
showlangstatbar:30737416
a2ce3375:30757347
pythonfmttext:30731395
pythoncmvfstrcf:30756944
fixshowwlkth:30771522
showindicator:30805244
pythongtdpath:30769146
i26e3531:30792625
gsofa:30804715
pythonnosmt12:30797651
pythonidxpt:30805730
pythonnoceb:30805159
synctok:30815622
dsvsc013:30795093
dsvsc014:30804076
diffeditorv1:30812748

idk if i'm missing something

The <font> tag is deprecated, as specified in https://developer.mozilla.org/en-US/docs/Web/HTML/Element/font.
You should use CSS instead:
.my-span {
  font-family: monospace;
  font-size: 1.3em;
}

/question

We closed this issue because it is a question about using VS Code rather than an issue or feature request. Please search for help on StackOverflow, where the community has already answered thousands of similar questions. You may find their guide on asking a new question helpful if your question has not already been asked. See also our issue reporting guidelines.
Happy Coding!


SELECT * does not project all in-scope variables

According to https://www.w3.org/TR/sparql11-query/#selectproject, SELECT * selects all of the variables that are in-scope at that point in the query. It excludes variables only used in FILTER, in the right-hand side of MINUS, and takes account of subqueries.
For example:
PREFIX :    <http://example/>

SELECT *
{
    :x1 :p ?v .
    OPTIONAL
    {
      :x3 :q ?w .
      OPTIONAL { :x2 :p ?v }
    }
}

has two variables in-scope: ?v and ?w. But if the query result does not bind to ?w, it is omitted from the variable list in the solution. This is because the result set is created from the actual results, which do not include ?w in this case.
To properly solve this, Algebra::Operator should implement an #in_scope_vars method that uses the described logic to find all variables and create a projection.

Fixed in 1b9d21309d000366e97cb312e18405c2bf3cdfde  and 5541bb42317e2124b59ae5053eab5d37b2395d53.
Add :all_vars option to parser, which will emit a (project () (...)) when a SELECT * is parsed. This currently defaults to false, but will become true, or non=optional in a future release. This causes SELECT * to project all in-scope variables.


HowTo set a value from component parent?

Hi,
I'm trying to use your component but I'm facing a problem: how to set a value from outside the component? The v-model is used for the filter input value...
Is there a way?
Thanks.

not sure exactly what you are asking, but v-model is the value of the in <input /> so it can be used in the component parent:
  You are searching for {{ query }}
  <vue-autosuggest  v-model="query" ...

Sorry, I forgot how autocomplete works...
I was more looking for a select with options load dynamically.
Thanks for your answer ;)


Restructure spec folder

Coverage decreased (-67.4%) to 26.325% when pulling b5e714f1393e0d5fce875e814875f495ede9df76 on master into 54e3a72cff011168b3d97e33bb2f960ebc94f10a on develop.

Coverage increased (+0.6%) to 94.322% when pulling 8ab2ee73440ca4a2f4d99a02320d5f931d8a2fb6 on master into 54e3a72cff011168b3d97e33bb2f960ebc94f10a on develop.

Coverage decreased (-66.5%) to 27.239% when pulling b686f34a3823f8ff1805796bd36059c4a53bc290 on master into 54e3a72cff011168b3d97e33bb2f960ebc94f10a on develop.

Coverage decreased (-64.0%) to 29.799% when pulling 5fd8f402b9f4d203b7444154f6d054e8cdafcebc on master into 54e3a72cff011168b3d97e33bb2f960ebc94f10a on develop.


Update ZAP to v2023.04.05-nightly

The current Matter SDK examples are failing to build with an error like this:
cd /var/chip/examples/lighting-app/nrfconnect/build && /var/chip/scripts/tools/zap/generate.py --no-prettify-output --templates /var/chip/src/app/zap-templates/app-templates.json --output-dir /var/chip/examples/lighting-app/nrfconnect/build/gen/app-zapgen/zapgen/app-templates/zap-generated --lock-file /var/chip/examples/lighting-app/nrfconnect/build/zap_gen.lock --parallel /var/chip/examples/lighting-app/nrfconnect/../lighting-common/lighting-app.zap
Searching for zcl file from /var/chip/examples/lighting-app/nrfconnect/../lighting-common/lighting-app.zap
Checking ZAP from ['/var/zap/v2023.01.19-nightly/zap-cli']:
  !!! Version validation failed: required at least 2023.4.5, got 2023.1.19 instead
[127/532] Building C object zephyr/CMakeFiles/zephyr.dir/lib/os/cbprintf_complete.c.obj
ninja: build stopped: subcommand failed.
FATAL ERROR: command exited with status 1: /usr/local/bin/cmake --build /var/chip/examples/lighting-app/nrfconnect/build

I got an "authorization failed" error when trying to build the image so I wasn't able to actually test this change.

 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.

@tpmanley Thanks for your contribution! Btw. we were wondering if this Docker image is still useful for people now that Toolchain Manager is supported on all operating systems: https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/nrf/getting_started/assistant.html#install-toolchain-manager. Did you maybe try to use it?

@Damian-Nordic Thanks for the response. I got to the Docker image by following the instructions here, but I can give the Toolchain Manager a try instead if that's the recommended path now. Also, since there was a new ZAP release since I opened this PR I'll go ahead and close it.


Energy Minimization Code and Forcefield with Removed Non-Bonded Terms

Two codes in pull request:
-Energy Minimization Code
-Forcefield with Removed Non-Bonded Terms, and edited impropers

@jmaat are you ready for someone to review this? Make sure to tag one/all of us when you want attention here.


Fix IMU orientation

Fixes https://github.com/tasts-robots/upkie_description/issues/2

Using the new example script:
python examples/display_frames.py --only imu

(We know we're looking at the back of the robot even with transparency from the battery pack.)
This matches the pi3hat convention:


remove lit-siwe

lit-siwe was created to shrink the size of the siwe lib.  but we're importing the new version of the siwe lib anyway, so lit-siwe actually just makes everything bigger.  we need the new siwe to be compatible with siwe-recap, so we can't really avoid importing the normal siwe.
so this PR just removes lit-siwe and replaces it with normal siwe

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.2 out of 4 committers have signed the CLA.:white_check_mark: Ansonhkg:white_check_mark: glitch003:x: Garandor:x: cairomassimoYou have signed the CLA already but the status is still pending? Let us recheck it.


Plugin crashes when terraform plan

Just doing a simple example an when executing terraform plan it crashes with a segmentation violation. Terraform init was great tho.
Error log:
`╷
│ Error: Plugin did not respond
│
│   with data.spotify_track.overkill,
│   on main.tf line 30, in data "spotify_track" "overkill":
│   30: data "spotify_track" "overkill" {
│
│ The plugin encountered an error, and failed to respond to the plugin.(*GRPCProvider).ReadDataSource call.
This is always indicative of a bug within the plugin. It would be immensely
helpful if you could report the crash with the plugin's maintainers so that it
can be fixed. The output above should help diagnose the issue.`
main.tf:
`terraform {
required_providers {
spotify = {
version = "~> 0.1.6"
source  = "conradludgate/spotify"
}
}
}
provider "spotify" {
api_key = var.spotify_api_key
}
resource "spotify_playlist" "playlist" {
name        = "playlist name"
description = "some description"
public      = false
tracks = [
data.spotify_track.overkill.id
]
}
data "spotify_track" "overkill" {
url = "https://open.spotify.com/track/4XdaaDFE881SlIaz31pTAG"
}
variable "spotify_api_key" {
type = string
}
output "playlist_url" {
value       = "https://open.spotify.com/playlist/${spotify_playlist.playlist.id}"
description = "Visit this URL in your browser to listen to the playlist"
}`

Running on a mac.
Versions:
Terraform v1.0.2
on darwin_amd64

provider registry.terraform.io/conradludgate/spotify v0.1.6

I've encountered same error.

And another "me too" - same versions in use as mentioned above.
Weird thing is: it DID work the first time. I managed to create a new playlist, was able to destroy it and re-create, adapt and apply again, etc., etc.
When I was happy with the first results, I stopped the Docker container onradludgate/spotify-auth-proxy and stepped away for app. 1 hour. Then tried all the required steps  again and ran into this issue.
See my repo for a reference: https://github.com/hbokh/spotify-playlist

I think I found what I did wrong:
every time you start the container onradludgate/spotify-auth-proxy, a different APIKey is generated, that needs to be replaced in file terraform.tfvars too:
spotify_api_key = "..."

Editing this specific file manually fixed my issue.
Wondering if this is possible to automate.

Hi, @hbokh I looked into what you see and although this is important and true, it's not the solution, but luckily I find out why this error happens! I turns out that when you run the docker, you have to access the http address that appears below the token because there you will have to approve that you give acces to you account(weird). Once done this step, terraform plan worked great.

Hi, @hbokh I looked into what you see and although this is important and true, it's not the solution, but luckily I find out why this error happens! I turns out that when you run the docker, you have to access the http address that appears below the token because there you will have to approve that you give acces to you account(weird). Once done this step, terraform plan worked great.

This worked @PauSabatesC Thank  you!!

Fixed in #15. Running a release now. Thanks everyone

a different APIKey is generated, that needs to be replaced in file terraform.tfvars too:

Yeah good point. Currently it's random everytime you run. I should add an environment variable so that you can manually specify the auth key

I should add an environment variable so that you can manually specify the auth key

Added in v0.1.10 :)


race condition with docc preview that appears to be acerbated by including snippets in DocC content

Description
Originally logged in swift-docc-plugin as https://github.com/swiftlang/swift-docc-plugin/issues/99
I found that adding snippet connect (Snippets/somefile.swift) to a caused the preview-documentation command to intermittently fail in terms of rendering all the content. The top-level module symbol graph file (in my case, voxels.json) is missing in some iterations of invoking this command, and present in others.
After iterating with various plugin versions and nailing down that this was, in fact, an intermittent issue, I found the plugin to be invoking the following command:
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/docc preview /Users/heckj/src/Voxels/Sources/Voxels/Documentation.docc --emit-lmdb-index --fallback-display-name Voxels --fallback-bundle-identifier Voxels --additional-symbol-graph-dir /Users/heckj/src/Voxels/.build/plugins/Swift-DocC\ Preview/outputs/.build/symbol-graphs/unified-symbol-graphs/Voxels-7 --output-path /Users/heckj/src/Voxels/.build/plugins/Swift-DocC\ Preview/outputs/Voxels.doccarchive
I'm Opening this bug on swift-docc to continue to debug, and closing the issue on swift-docc-plugin since it doesn't appear to be related to the plugin content.
Checklist

[x] If possible, I've reproduced the issue using the main branch of this package.
[X] This issue hasn't been addressed in an existing GitHub issue.

Expected Behavior
When invoking swift package --disable-sandbox preview-documentation --target MyTarget on a package using swift-docc-plugin and containing any snippet content, I expect the documentation archive to be fully rendered. In my example. showing something akin to:
========================================
Starting Local Preview Server
	 Address: http://localhost:8080/documentation/voxels
========================================

Actual behavior
Intermittently, and accerbated by having snippet content in the project, the preview fails to render, showing instead:
========================================
Starting Local Preview Server
	 Address: http://localhost:8080/documentation/
========================================

And inside the docs-archive output path that preview used, the top-level target symbol graph JSON file (in my case, voxels.json) is missing. But this is intermittent, and repeated invocations will get different results.
Steps To Reproduce

Get example Swift package (public repository)

git clone https://github.com/heckj/voxels
cd voxels

Check out content before snippets were added:

git checkout 0.2.4

(commit shows 7048693)

repeatedly invoke the preview command:

swift package --disable-sandbox preview-documentation --target Voxels

For 5 runs:

content rendered

content rendered

content rendered

content rendered

content rendered

Check out content with snippet content added:

git checkout 6089364

repeatedly invoke the preview command:

swift package --disable-sandbox preview-documentation --target Voxels

For 5 runs:

content missing
content rendered
content rendered
content rendered
content missing

Swift-DocC Version Information
'6.0.2' (included with Xcode 16.1)
Swift Compiler Version Information
swift-driver version: 1.115 Apple Swift version 6.0.2 (swiftlang-<IP_ADDRESS>.2 clang-16<IP_ADDRESS>)
Target: arm64-apple-macosx15.0

repeating with main branch of docc:
export DOCC_HTML_DIR=/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/share/docc/render/
/Users/heckj/src/swift-project/swift-docc/.build/debug/docc preview /Users/heckj/src/Voxels/Sources/Voxels/Documentation.docc --emit-lmdb-index --fallback-display-name Voxels --fallback-bundle-identifier Voxels --additional-symbol-graph-dir /Users/heckj/src/Voxels/.build/plugins/Swift-DocC\ Preview/outputs/.build/symbol-graphs/unified-symbol-graphs/Voxels-7 --output-path /Users/heckj/src/Voxels/.build/plugins/Swift-DocC\ Preview/outputs/Voxels.doccarchive

5 runs:

no content
content rendered
no content
no content
content rendered

So the same behavior exists with the main development branch.

I'd be curious to see if it also reproduces with the changes from https://github.com/swiftlang/swift-docc/pull/1070 or if race conditions fixed in that PR (aimed at fixing flaky tests) also fix this issue. 🤔
I can give that a try tomorrow.

I can easily give it a shot later today - I've continued debugging it. Away from my laptop for lunch, but I'll give that specific PR a run and see how it does.

Narrowing this down a bit more, I dropped into ConvertActionConverter.convert() and added a bit of extra code to understand what was flowing, and what wasn't.
Within the concurrentPerform iteration that does the lifting, I looked for an entity for the module, and sometimes it appeared, and when the result was "missing content" it wouldn't.
Shimmed in code, and I tacked a breakpoint onto the print statement
                    if entity.name.plainText == "Voxels" {
                        print("FOUND IT!: \(entity.name)")
                    }

This is leading me to believe there's a possible issue with context.knownPages.concurrentPerform() - in some iterations, it's never returning the identifier for the top-level module.

continuing my poking, and it's above/earlier than concurrentPerform - I checked the contents of context.knownPages - and in some cases that doesn't include the expected resolved page.

Tracking it back to line 281 in ConvertAction:
let context = try DocumentationContext(bundle: bundle, dataProvider: dataProvider, diagnosticEngine: diagnosticEngine, configuration: configuration)

I've got a stupid bit of printf debugging running:
for page in context.knownPages {
    //print(page.absoluteString)
    if page.url.absoluteString == "doc://Voxels/documentation/Voxels" {
        print("PING")
    }
}

And in the race condition cases where the node is missing, it's missing from the start of the context generation.

After digging back into the registerSymbols() function (line 1142) where the topic is set up in it's tree, I realized that the key piece that's being established that wrong in the race condition is the node's isVirtual property is resolving to true (which prevents it from being renderered/included) in some cases.
I've tracked back how/where that's set up to the iteration over symbolGraph files (https://github.com/swiftlang/swift-docc/blob/784ba5801b4bd8b092bff695a288b4053ce53c65/Sources/SwiftDocC/Infrastructure/DocumentationContext.swift#L1172) that loads up the information.

The source of the isVirtual are the upstream symbol graphs that come from the compiler (or from symbol-graph-extract). I haven't sorted out entirely how they're merged, but notably when you have a Snippet, the symbol graph for that snippet lists its module with isVirtual=true.
My updated hypothesis is that the graphs are being processed in a non-deterministic order, and as the relevant top-level module symbols are merged together into a unified set of symbols that include the snippets, the top-level module gets arbitrarily picked from those, rather than "if any are non-virtual", prefer that.
Since each additional snippet makes it's own additional symbol-graph (each with a module that is defined as isVirtual=true), that would imply that the chance of getting an "isVirtual=true" for the main module goes up with more examples. I tried a few quick checks on the swift-markdown repo, but it consistently displays the preview correctly (and has quite a few snippets within it) - so I may be off base with this theory.

Following up with how SymbolGraph operates internally, there's a private function that provides an indicator of if the symbolgraph in question is the "main" one or not, that used the logic:
let isMainSymbolGraph = !url.lastPathComponent.contains("@")

This doesn't account for a snippets module graph, which also appears to be main. However, updating the private function in question (private static func moduleNameFor(_ symbolGraph: SymbolGraph, at url: URL) -> (String, Bool) ) to do a bit more exclusion didn't resolve the issue.
Turns out there's almost identical logic in SymbolKit's GraphCollector, which likewise doesn't account for the possibility of snippet modules.
The function public static func moduleNameFor(_ graph: SymbolGraph, at url: URL) -> (String, Bool)
An instance of GraphCollector is maintained in the SymbolGraphLoader, and this same logic is hit when calling it's
public func mergeSymbolGraph(_ inputGraph: SymbolGraph, at url: URL, forceLoading: Bool = false) function. It then uses that "Does an @ symbol exist in the module name" to determine extension (@ symbol exists) or primary - and because there's multiple primaries, (and it grabs the first one it finds), the value looked up gets indeterministic.
I think the ultimate resolution here would be to extend the logic in SymbolKit's GraphCollector.moduleNameFor() needs some tweaking to account for a 3rd kind of collection of symbols - the snippets - and record that as an extension kind rather than a primary kind. Just looking for "snippets" in the name of the URL is a potential solution, but suboptimal if any module name actually contains the string "snippets", at which point it's a false positive. That said, the SymbolGraph itself has metadata (the generator) that can be used to also identify where the symbolGraph came from that would be a good double-check on that logic.

Since this digging extends down into SymbolKit, I opened https://github.com/swiftlang/swift-docc-symbolkit/issues/88 with an explanation or what was incorrect there. In addition to the upstream logic fix, which seems needed to resolve this issue, the replicated logic in SymbolGraphLoader should likely be removed, and the logic from SymbolKit (when fixed) used in it's place in order to localize the knowledge and not have to solve this in two places.
The local logic in swift-dock's SymbolGraphLoader doesn't appear to be causing an issue, but it is a bit incorrect.


Polish Kotlin DSL plugin accessor generation

@bot-gradle test QFL please.

OK, I've already triggered QuickFeedbackLinux build for you.


boost-build[core] build failure

Host Environment

OS: macOS 10.15.3
Compiler: Xcode 11.3.1

To Reproduce
Steps to reproduce the behavior:
export CC=/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/cc
export CXX=/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/c++
./vcpkg install boost-build[core]
Failure logs
$ ./vcpkg install boost-build[core]
Your feedback is important to improve Vcpkg! Please take 3 minutes to complete our survey by running: vcpkg contact --survey
Computing installation plan...
The following packages will be built and installed:
    boost-build[core]:x64-osx
Starting package 1/1: boost-build:x64-osx
Building package boost-build[core]:x64-osx...
-- Using cached /Users/christophe.calmejane/dev/vcpkg/downloads/boostorg-build-boost-1.72.0.tar.gz
-- Using source at /Users/christophe.calmejane/dev/vcpkg/buildtrees/boost-build/src/ost-1.72.0-fa8b817276
-- Using cached /Users/christophe.calmejane/dev/vcpkg/downloads/boost_LICENSE_1_0.txt
-- Using cached /Users/christophe.calmejane/dev/vcpkg/downloads/boost-1.72.0-boostcpp.jam
-- Installing: /Users/christophe.calmejane/dev/vcpkg/packages/boost-build_x64-osx/share/boost-build/copyright
-- Installing: /Users/christophe.calmejane/dev/vcpkg/packages/boost-build_x64-osx/tools/boost-build/boostcpp.jam
-- Bootstrapping...
CMake Error at scripts/cmake/vcpkg_execute_required_process.cmake:72 (message):
    Command failed: /Users/christophe.calmejane/dev/vcpkg/packages/boost-build_x64-osx/tools/boost-build/bootstrap.sh
    Working Directory: /Users/christophe.calmejane/dev/vcpkg/packages/boost-build_x64-osx/tools/boost-build
    Error code: 1
    See logs for more information:
      /Users/christophe.calmejane/dev/vcpkg/buildtrees/boost-build/bootstrap-x64-osx-out.log

$ cat /Users/christophe.calmejane/dev/vcpkg/buildtrees/boost-build/bootstrap-x64-osx-out.log
Bootstrapping the build engine with toolset clang...

Failed to bootstrap the build engine
Consult 'bootstrap.log' for more details

$ cat ./packages/boost-build_x64-osx/tools/boost-build/bootstrap.log
###
###
### Using 'clang' toolset.
###
###
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/c++ --version
Apple clang version 11.0.0 (clang-1<IP_ADDRESS>)
Target: x86_64-apple-darwin19.3.0
Thread model: posix
InstalledDir: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin
###
###
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/c++ -x c++ -O3 -std=c++11 -O3 -s -DNDEBUG builtins.cpp class.cpp command.cpp compile.cpp constants.cpp cwd.cpp debug.cpp debugger.cpp execcmd.cpp filesys.cpp frames.cpp function.cpp glob.cpp hash.cpp hcache.cpp hdrmacro.cpp headers.cpp jam.cpp jambase.cpp jamgram.cpp lists.cpp make.cpp make1.cpp md5.cpp mem.cpp modules.cpp native.cpp object.cpp option.cpp output.cpp parse.cpp pathsys.cpp regexp.cpp rules.cpp scan.cpp search.cpp strings.cpp subst.cpp sysinfo.cpp timestamp.cpp variable.cpp w32_getreg.cpp modules/order.cpp modules/path.cpp modules/property-set.cpp modules/regex.cpp modules/sequence.cpp modules/set.cpp execunix.cpp fileunix.cpp pathunix.cpp -o b2
In file included from builtins.cpp:7:
./jam.h:336:10: fatal error: 'sys/types.h' file not found
#include <sys/types.h>
         ^~~~~~~~~~~~~
1 error generated.

Additional context
For some reason, I need to have CC/CXX set (here I manually set them before invoking vcpkg just for showcasing the issue).
I tracked down the issue in packages/boost-build/tools/boost-build/src/engine/build.sh where the script is setting CXX like this: CXX=${CXX:=clang++}
If CXX is not set before invoking vcpkg then clang++ is chosen and everything compiles correctly.
Is there a clean way for vcpkg to unset critical environment variables for ports that might behave differently if set (for any reason)? I don't think outside environment should impact how boost (or any other package) is compiled, except for any options passed to vcpkg command line.
Just FYI, my actual use case is because a project is calling vcpkg install from a CMake script that is executed at configure time. Depending on the chosen compiler (by CMake), boost either succeed or fails to compile. For instance if I use Xcode generator then everything is fine (because CXX is set to clang++ by CMake), but if I use Ninja or Makefiles then it fails.

@christophe-calmejane, boost currently upgrade to 1.73.0, could you get latest source and see if this issue still occur?
I can't repro this issue locally.
./vcpkg install boost-build
Computing installation plan...
The following packages will be built and installed:
boost-build[core]:x64-osx
Detecting compiler hash for triplet x64-osx...
Starting package 1/1: boost-build:x64-osx
Building package boost-build[core]:x64-osx...
Could not locate cached archive: /Users/vcpkg/.cache/vcpkg/archives/62/62bc95a660c9a6fa4ecc0fb0cba0536921dff742.zip
-- Downloading https://github.com/boostorg/build/archive/boost-1.73.0.tar.gz...
-- Extracting source /Users/vcpkg/phoebe/vcpkg/downloads/boostorg-build-boost-1.73.0.tar.gz
-- Using source at /Users/vcpkg/phoebe/vcpkg/buildtrees/boost-build/src/ost-1.73.0-018fb008dd.clean
-- Downloading https://raw.githubusercontent.com/boostorg/boost/boost-1.73.0/LICENSE_1_0.txt...
-- Downloading https://raw.githubusercontent.com/boostorg/boost/boost-1.73.0/boostcpp.jam...
-- Installing: /Users/vcpkg/phoebe/vcpkg/packages/boost-build_x64-osx/share/boost-build/copyright
-- Installing: /Users/vcpkg/phoebe/vcpkg/packages/boost-build_x64-osx/tools/boost-build/boostcpp.jam
-- Bootstrapping...
-- Performing post-build validation
-- Performing post-build validation done
Stored binary cache: /Users/vcpkg/.cache/vcpkg/archives/62/62bc95a660c9a6fa4ecc0fb0cba0536921dff742.zip
Building package boost-build[core]:x64-osx... done
Installing package boost-build[core]:x64-osx...
Installing package boost-build[core]:x64-osx... done
Elapsed time for package boost-build:x64-osx: 7.719 s
Total elapsed time: 9.298 s

Have you manually defined CC and CXX env variables before running vcpkg install?

I didn't define any CC and CXX env variable.

BTW, you can reference https://github.com/microsoft/vcpkg/blob/master/scripts/azure-pipelines/osx/azure-pipelines.yml#L19 for VM setup on OSX.

Well, defining the env vars was the whole point of the ticket. Boost was (and is still) compiling fine, as long as it's not disturbed by an external element.
My ticket's point was that vcpkg should not (in general, not just Boost which merely served as an example) be affected in any way be the environement. It's a complete build toolchain, if something has to impact the compilation it should be defined in ports file and/or passed as parameters (via CMAKE TOOLCHAIN file for example).
Here with boost, we have a compilation failure if CC and CXX are defined (to valid values, as I used the exact same values that Ninja generator sets CC/CXX to).
So it's not a specific port bug, but more something that vcpkg should take care of internally like undefining (backuping) some env vars before calling cmake).

@christophe-calmejane, Sorry for my late response.
This is mostly like a Upstream issue, vcpkg only execute bootstrap.sh, see https://github.com/microsoft/vcpkg/blob/master/ports/boost-build/portfile.cmake#L63, without setting any additional flags on osx, could you report an issue to boost build instead?

@christophe-calmejane Thanks for your issue. This issue should be a upstream issue, did you report this issue on upstaream?

I might have missed Phoebe's answer (along with forgetting this ticket), so I didn't report to boost project. Not sure I will have the time to do so for now, neither have I checked with a more recent boost version.

Waiting upstream fix this issue, we will sync upstream's change to VCPKG.

Please reopen this issue when it is fixed upstream.


Use F# as in TC for operations, bug fixes

Need updated syntax as well, otherwise golden. Will merge next instead, closing this one.

Don't close the pull request. It can be updated with the patch.

Aight, open!

@philip-karlsson have a look now!

Looks good, merging!


[SPARK-41469][CORE] Avoid unnecessary task rerun on decommissioned executor lost if shuffle data migrated

What changes were proposed in this pull request?

This PR proposes to avoid rerunning the finished shuffle map task in TaskSetManager.executorLost() if the executor lost is caused by decommission and the shuffle data has been successfully migrated.
Why are the changes needed?

To avoid unnecessary task recomputation.
Does this PR introduce any user-facing change?

No.
How was this patch tested?

Added UT

cc @warrenzhu25 too

Mark as WIP first regarding the compilation error and missing ut. Any feedback is still welcome.

cc @warrenzhu25 too

It's really the change I want. Great work.

The failed test seems to be flaky:
- decommission workers ensure that shuffle output is regenerated even with shuffle service *** FAILED *** (18 seconds, 479 milliseconds)
[info]   5 did not equal 4 Expected 4 tasks but got List(0:0:0:0-SUCCESS, 0:0:0:0-SUCCESS, 0:0:1:0-SUCCESS, 0:0:0:1-SUCCESS, 1:0:0:0-SUCCESS) (DecommissionWorkerSuite.scala:191)
[info]   org.scalatest.exceptions.TestFailedException:
[info]   at org.scalatest.Assertions.newAssertionFailedException(Assertions.scala:472)
[info]   at org.scalatest.Assertions.newAssertionFailedException$(Assertions.scala:471)
[info]   at org.scalatest.Assertions$.newAssertionFailedException(Assertions.scala:1231)
[info]   at org.scalatest.Assertions$AssertionsHelper.macroAssert(Assertions.scala:1295)
[info]   at org.apache.spark.deploy.DecommissionWorkerSuite.$anonfun$new$6(DecommissionWorkerSuite.scala:191)
....

Could you take a look at the failure? It looks like relevant.

The failure is not reproducible every time. I suspect it is still a flaky test. I will keep an eye on it.

Got it. If then, it's okay. Thank you for checking and confirming that.

The failure is indicating two task end events for the same task ? I dont see how that can happen due to this PR - but wondering how that could have happened in general ... any thoughts @Ngone51 ?

@mridulm Thanks for the help. Let me take another look. (Sorry for the delay was unhealthy last week...

Merged to master.
Thanks for working on this @Ngone51 !
Thanks for review @dongjoon-hyun :-)

Thanks @mridulm @dongjoon-hyun

#(&£€&445₩)*khakqganHynosql sharsing
ShahrzadMahro
در تاریخ یکشنبه ۲۱ آوریل ۲۰۲۴، ۲۲:۳۶ Parth Shyara @.***>
نوشت:

@.**** commented on this pull request.
In core/src/main/scala/org/apache/spark/scheduler/TaskSetManager.scala
https://github.com/apache/spark/pull/39011#discussion_r1573887387:

val maybeShuffleMapOutputLoss = isShuffleMapTasks &&

 (reason.isInstanceOf[ExecutorDecommission] || !env.blockManager.externalShuffleServiceEnabled)

@Ngone51 https://github.com/Ngone51 @mridulm
https://github.com/mridulm Is the above issue being tracked elsewhere?
—
Reply to this email directly, view it on GitHub
https://github.com/apache/spark/pull/39011#discussion_r1573887387, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ANEZZRHCBDW5SHLP2PE25W3Y6QE45AVCNFSM6AAAAAASZOZVDSVHI2DSMVQWIX3LMV43YUDVNRWFEZLROVSXG5CSMV3GSZLXHMZDAMJTGUYDCMBYHA
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>


resolved issue #28

have made appropriate changes, do check and let me know.

Great Work

thanks man