Multi: add grace period before calling done! (default: 30s)

This uses the Multi object's already-allocated timer to set a timer when the number of in-progress downloads reaches zero, to clean up the curl multi-handle and associated resources when the timer goes off. If another download is started before then, then the timer is started again once the number of downloads reaches zero again. If a Multi object is garbage collected before its cleaup timer fires, it will be finalized earlier, so the cleanup occurs at the earlier of the two. If the grace period is zero, then done! is called immediately when the number of concurrent downloads reaches zero. If the grace period is larger than typemax(UInt64) ÷ 1000 then no timer is set and the cleanup only occurs when the Multi object is garbage collected.

Codecov Report

Merging #38 into master will decrease coverage by 5.25%.
The diff coverage is 65.21%.

@@            Coverage Diff             @@
##           master      #38      +/-   ##
==========================================
- Coverage   95.81%   90.56%   -5.26%
==========================================
  Files           5        5
  Lines         263      265       +2
==========================================
- Hits          252      240      -12
- Misses         11       25      +14

Impacted Files
Coverage Δ

src/Curl/Multi.jl
88.88% <63.63%> (-7.34%)
:arrow_down:

src/Downloads.jl
95.34% <100.00%> (ø)

src/Curl/utils.jl
78.12% <0.00%> (-18.75%)
:arrow_down:

Continue to review full report at Codecov.

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

@KristofferC & @aviks: feel free to look at the technical parts of this PR, but what I'm really interested in is feedback on the general concept of having a grace period before cleaning up a downloader's resources. We could make the default downloader behave the way it did before by making its grace period zero, but this seems like a pretty decent default since it's fairly common for people to write code that does more than one batch of downloads to the same server and this makes that noticeably faster since it can reuse already-open connections. It's still possible to use a locally scoped Downloader object to delimit the duration of libcurl resources since if a downloader is garbage collected before its grace period expires, the resources are finalized immediately. If, on the other hand, someone naively keeps a global reference to a Downloader object—in the future we might allow meaningful configuration of them that someone wants to apply—then this will still reclaim resources after some time.

Might also make sense to make the default grace period shorter: 60 seconds is an eternity in computer time. Apache's default Keep-Alive timeout is 15 seconds; not directly related, but it feels like the same kind of thing.

Update: changed the default grace period to 30 seconds.

I'm going ahead with this since the old behavior is just a special case of this one. If we decide we don't want the grace period by default, we can always make the default be a grace period of zero and retain this functionality for those who do want it.

Maybe 30 sec is still kinda long but I don't really know. 🤷♂

Yeah, who knows?! I figure that in most circumstances keeping some resources around on a client doesn't matter. On a server, you're likely to be serving lots of clients, but on the client that's not an issue.


[5.2] Removed routing filters

:+1:

:+1:

This yields a performance improvement for routing, and removes officially deprecated code (as of L5.1, but was undocumented since L5.0). People wanting to use deprecated features of laravel can just stay on our LTS release. This means we can cleanup our codebase in the minor release immediately following the LTS release.


[CENNSO-1030] Revert the new timer wheel implementation for now

It turned out to have a substantial memory leak, possibly with some timers not being cleaned up during session updates. Reverting for now to have more time for debugging and validation

I've state many times that the changed timer wheel had a good chance of having memory leaks. So, this is nothing new or surprising.
Instead of reverting the changes, finding and fixing the missing timer cleanups would be much more helpful.

@RoadRunnr That's the plan actually, to have the changes merged back as soon as we fix the issues. The revert is needed as a temporary measure due to release timings


feat: add node prefix import for Deno support

tests don't pass because of https://github.com/standard-things/esm/issues/904

Sorry, can you remove the eslint stuff

The next track of Polka is "next" -- it's not stable release yet. In fact, next is targeted to be the 1.0 release.
The master / stable branch is currently 0.5.x
This is also why you install polka via polka@next -- you're opting into the next release channel.
Apologies about the breaking change, but working on finding a working solution for modern and more legacy codebases. It'd help if you provided information in the issue, not here.

The next track of Polka is "next" -- it's not stable release yet. In fact, next is targeted to be the 1.0 release. The master / stable branch is currently 0.5.x
This is also why you install polka via polka@next -- you're opting into the next release channel.
Apologies about the breaking change, but working on finding a working solution for modern and more legacy codebases. It'd help if you provided information in the issue, not here.

Dependency:
<EMAIL_ADDRESS>-> sirv@^ 2.0.3 -> @polka/url^1.0.0-next.24

The question is: why does sirv depend on the next version of @polka/url, but the stable version?
And it seems that the sirv package is also maintained by you.

It'd help if you provided information in the issue, not here.


update documentation including classpath env var

Coverage remained the same at 43.202% when pulling 993009df4c438dcc12991bcb453a0d1b8de8f892 on update-classpath into 1f1f45a219ad3fcd6cb2457c89793bd2f7e1245a on master.

Coverage remained the same at 43.202% when pulling 993009df4c438dcc12991bcb453a0d1b8de8f892 on update-classpath into 1f1f45a219ad3fcd6cb2457c89793bd2f7e1245a on master.


Rearrange Directories

I found different types of files in your repo like .java .py .cpp .pdf etc. I will Rearrange them like "/Language/.." . It will clear your repo's main page

Yes sure


Assemblytics requires R(ggplot2) and X11 ?

Assemblytics requires R(ggplot2) and X11 ?
I got error on Linux server:
..........
4. Combine variants between and within alignments
Error in .External2(C_X11, paste("png::", filename, sep = ""), g$width,  :
unable to start device PNG
Calls: png
In addition: Warning message:
In png(paste(output_prefix, ".Assemblytics.size_distributions.",  :
unable to open connection to X11 display ''
Execution halted
Error in .External2(C_X11, paste("png::", filename, sep = ""), g$width,  :
unable to start device PNG
Calls: png
In addition: Warning message:
In png(file = paste(plot.output.filename, ".png", sep = ""), width = 1000,  :
unable to open connection to X11 display ''
Execution halted
Error in .External2(C_X11, paste("png::", filename, sep = ""), g$width,  :
unable to start device PNG
Calls: png
In addition: Warning message:
In png(file = paste(prefix, ".Assemblytics.Nchart.png", sep = ""),  :
unable to open connection to X11 display ''
Execution halted

You can use Assemblytics on the web at assemblytics.com, which requires no
installation.
On Wed, Jun 27, 2018 at 3:38 AM Fu-Hao Lu<EMAIL_ADDRESS>wrote:

Assemblytics requires R(ggplot2) and X11 ?
I got error on Linux server:
..........
4. Combine variants between and within alignments
Error in .External2(C_X11, paste("png::", filename, sep = ""), g$width, :
unable to start device PNG
Calls: png
In addition: Warning message:
In png(paste(output_prefix, ".Assemblytics.size_distributions.", :
unable to open connection to X11 display ''
Execution halted
Error in .External2(C_X11, paste("png::", filename, sep = ""), g$width, :
unable to start device PNG
Calls: png
In addition: Warning message:
In png(file = paste(plot.output.filename, ".png", sep = ""), width = 1000,
:
unable to open connection to X11 display ''
Execution halted
Error in .External2(C_X11, paste("png::", filename, sep = ""), g$width, :
unable to start device PNG
Calls: png
In addition: Warning message:
In png(file = paste(prefix, ".Assemblytics.Nchart.png", sep = ""), :
unable to open connection to X11 display ''
Execution halted
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/MariaNattestad/Assemblytics/issues/11, or mute the
thread
https://github.com/notifications/unsubscribe-auth/AHluPSydOIUzBQ8Tkp76D6rl52FamAeZks5uA2C2gaJpZM4U5eJd
.


Multiple LD_PRELOAD instances

Hello,
We have an application that currently uses LD_PRELOAD and when Dynatrace injects its own LD_PRELOAD it is causing application crashes. Is there currently any way to have Dynatrace add the LD_PRELOAD path to the existing LD_PRELOAD or some other type of workaround for this?
      - name: LD_PRELOAD                                                          # <------  app needs this
        value: /usr/lib64/libnss_wrapper.so
...
       - name: LD_PRELOAD                                                          # <------  Dynatrace injected this
       value: /opt/dynatrace/oneagent-paas/agent/lib64/liboneagentproc.so

I think we worked around this by modifying the image with a start script that takes any pre-defined value for LD_PRELOAD and appends the required path to it before invoking the actual executable.

Hi,
I wanted to follow up on this issue. Will this feature be added in any of the upcoming Operator versions? Or is it on the roadmap for the Operator?

Thank you for opening a Dynatrace Operator Issue. We've identified and tagged the issue as a "Feature request".
Dynatrace reviews feature requests in the Dynatrace community rather than Github. This helps our team consolidate, rank, and prioritize important input like yours.
Please search for similar requests, collaborate, and ask questions using the link above. Remember to add the labels "kubernetes" and "dynatrace-operator" to help get the attention you deserve.
Thanks for your help!


UX: Progress bar getting scrunched on phones

(Galaxy S6)

just like #35 #37 #31 , once screens have been updated with new components and layouts lets confirm these have been fixed. If these problems still persist even with new designs, please assign me and explain why so I can come up with a solution.

duplicate. closing.


[CI] GoRelease Docker

See: https://goreleaser.com/docker/

https://goreleaser.com/customization/docker/

If it ain't broke though...


Update deep-links.md

Changed "Generate a deep link to a chat" to "Generate a deep link to a call" for the last section

Docs Build status updates of commit 0511d14:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/concepts/build-and-test/deep-links.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


Brazilian Portuguese Translation

🇧🇷 Brazilian Portuguese Translation
This PR translates Sniffnet to brazilian portuguese.
Although european portuguese and brazilian portuguese are very similar, they differ in several ways and what "feels good" in one may not be the same in the other.

I thank you a lot for your contribution, but we already had a discussion about this topic as a PR for Brazilian Portuguese was submitted in #134 and one for European Portuguese was submitted in #136.
In particular, this was the response by @franciscoBSalgueiro who submitted the European version:

It's the same language, so any portuguese speaking person would be able to read both. That being said, you can definitely tell one was written by a Brazilian and another by a Portuguese. I've seen some apps have both a pt_PT and pt_BR translation, but if you only want to have one, I think any of them would work.

And from that I decided to only include the European version for reasons of easier maintainability.
What do you think?

Oh sorry, I haven't seen those PRs!
However as a Brazilian I do think they differ in relevant ways, one sure could read both translations, but there are several different words and habits between them! There are some Portuguese ways of speaking that although are 100% comprehensible, in Brazil they would be unusual or sometimes even wrong.
I saw that European Portuguese is not updated to translations_2.rs, and I don't feel able to complete it as I don't speak this variation of the language and as a consequence would be heavily biased.
In the other hand your decision is completely understandable for practicality and I should indeed have searched for PRs about this.

Don't worry!
Given your considerations, I think I'll include your translation as well.
Even if it will add the overhead of managing one more language, it can be a valuable addition for native Brazilians.

Hey @clr-cera I was about to merge the PR but I noticed that the changes with respect to the European variant are minimal.
At this point I think it's better to only keep one language.
Would you like to open a new PR just to update the original PT translation? (i.e., including only translations_2.rs from this PR)

Sure! I will close this PR and soon I'll send a new one, at the end there will be an European and Brazilian portuguese mix, which I don't think is inherently bad either.


Include document.scrollingElement

https://developer.mozilla.org/en-US/docs/Web/API/document/scrollingElement

+1

+1

+1

+1

+1

Github has reactions now. Please consider using them instead of a +1 comment to show your support, as they won't generate notifications (email and onsite).  Thanks!


SAM-2147 Do not allow instructors to edit or remove a published test aft...

...er any activity

Could you also update these properties in
config/configuration/bundles/src/bundle/org/sakaiproject/config/bundle/default.sakai.properties

Thanks, I've made these changes in https://github.com/sakaiproject/sakai/pull/119


Link to Azure Information Protection pricing is broken

[Enter feedback here]

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

ID: 233c91bd-3428-d866-aa90-56c18c750153
Version Independent ID: 5d5597ab-0b10-47b1-ac9c-fca9946a2eab
Content: Using Microsoft Cloud App Security controls in Power BI - Power BI
Content Source: powerbi-docs/admin/service-security-using-microsoft-cloud-app-security-controls.md
Service: powerbi
Sub-service: powerbi-eim
GitHub Login: @paulinbar
Microsoft Alias: painbar

@IrkenCR - Thank you for bringing this to our attention. It appears that the target page is no longer available and the link is also broken on the marketing page. I'm assigning this to the writer to follow up to see if a better destination is available.

Hi @IrkenCR , well I see the Azure Information protection pricing info still isn't available on the Azure Information Protection site. I have escalated the issue and will continue to monitor. Right now the link on our page just goes to the Azure Information Protection page (which is live). The problem now is that the Pricing info link on that page is broken. That is what has been escalated. So in the meantime I am closing this issue. Thanks!


How to install?

 pip install https://github.com/T-Dynamos/materialyoucolor-pyhton/archive/master.zip
OUPTUT:
ERROR: https://github.com/T-Dynamos/materialyoucolor-pyhton/archive/master.zip does not appear to be a Python project: neither 'setup.py' nor 'pyproject.toml' found.

@HeaTTheatR Currently I haven't packaged it. To use it, you may clone the repo and put your files inside it and run. See example.py

@T-Dynamos I am embedding this package in the KivyMD library. Therefore, I would like to be able to install this package.

Ok, I am on it!

@HeaTTheatR It's done! Now you can install with:
Always prefer master branch
pip3 install https://github.com/T-Dynamos/materialyoucolor-pyhton/archive/main.zip

or
pip3 install materialyoucolor


Update block_processing.exs - rename BlockStore and StateStore to Blo…

…ckDb and StateDb
rename BlockStore and StateStore to BlockDb and StateDb as stated from issue
Motivation

Description

Closes #686

Hi, this is only updating one file. We want to update the module everywhere where it's referenced.

Closing, feel free to reopen if you plan to keep working on this

noted, would reopen when it's done in the suitable way


[Discussion] Approach for supporting older versions of rustc

As it was recommended in #9629, I open the issue.
As we all know, distros (I mean Debian-based distros, such as Ubuntu and Debian itself) have problems with supplying the most recent versions of rust in time.
While it is possible to use the stuff like rustup and curl ... | sudo bash, it can have some issues and so it is strongly disrecommended.
So, an issue arises to allow outdated versions of rust to build rust-analyser.
There are some options:

introducing a policy of keeping the code compatible to the oldes version of rustc available in the latest versions of all major distros. Pro - rustc built by the distro itself can be used. Con - limiting oneself to old features only is not fun.

making an own update server for package managers and hosting it on GitHub Pages. Provide the prebuilt binary packages for the latest rust-nightly via it. Con - trust and security issues. Pro - latest Rust.

making an additional branch for each rust release significantly present in distros, that is meant to be rebased over master and gets a commit fixing the incompatibility when a commit not supporting needed versions of rust is landed into master.  An example of such a branch is https://github.com/KOLANICH-toosl/rust-analyzer/tree/ubuntu_21.04_compat . Con - additional work for ones maintaining this branch. Pro - developers get more fun playing with the fresh features. Comment - it'd be easier to maintain such a branch if the introduction of incompatible changes is documented. Also it may be possible to setup a GitHub action automatically rebasing the branch over master and detecting the incompatible commits.

CC https://github.com/rust-analyzer/rust-analyzer/pull/9550

Personally I don't think we should go out of our way to cater to distros that ship outdated Rust version. They can easily ship a just-as-outdated rust-analyzer if they insist.
In fact rust-lang/rust already has an experimental rust-analyzer submodule that should roughly match the Rust version, so that can be used as a starting point for finding a good release.

To put it differently, Debian could package rust-analyzer from the in-tree version, like it does with rustfmt or clippy (actually, these aren't even available in unstable, you need to enable the experimental repo).

Also, it's worth noting that it's not about "fun playing with fresh features". One issue is that we interact with rustc (e.g. running proc macros built by it), and supporting older versions as well as the current one would mean more effort and more code to maintain. The second issue is that we're working towards using libraries shared with rustc, and it's hard enough to argue for those libraries to build on current stable. Currently the rustc codebase uses lots of nightly-only features; there are many reasons for this other than developer fun, for example being able to dog-food and test new features.


Enum comparision tests

adds tests for enums

Codecov Report

Merging #220 (0c2fcb6) into main (3964784) will decrease coverage by 0.01%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##             main     #220      +/-   ##
==========================================
- Coverage   76.71%   76.71%   -0.01%
==========================================
  Files          80       80
  Lines        8754     8753       -1
==========================================
- Hits         6716     6715       -1
  Misses       2038     2038

Impacted Files
Coverage Δ

src/libfuncs/enum.rs
98.59% <100.00%> (-0.01%)
:arrow_down:

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


Fix license headers in integration/

jenkins, test this please

jenkins, test this please

jenkins, test this please

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-PR-Builder/11144/
Test PASSed.

alluxio-bot, merge this please


added pylint

started with code checking for #51

LMK when you have a ready-for-review version of this.

bumpity bump


fix: revert "load sourcemaps alongside modules (#11576)"

Description
Reverts https://github.com/vitejs/vite/pull/11576 as it's causing failures on the ecosystem CI: https://github.com/vitejs/vite/pull/11576#issuecomment-1398506016
Additional context
I'd love to get better source map support added, but source map support is pretty finicky in my experience and the PR being reverted didn't have any tests. We should probably make sure anything source map related has tests and is run against the ecosystem CI before merging on the next attempt. We reverted another attempt at source map support earlier for similar reasons

What is the purpose of this pull request?

[X] Bug fix
[ ] New Feature
[ ] Documentation update
[ ] Other

Before submitting the PR, please make sure you do the following

[X] Read the Contributing Guidelines.
[X] Read the Pull Request Guidelines and follow the PR Title Convention.
[X] Check that there isn't already a PR that solves the problem the same way to avoid creating a duplicate.
[X] Provide a description in this PR that addresses what the PR is solving, or reference the issue that it solves (e.g. fixes #123).
[ ] Ideally, include relevant tests that fail without this PR but pass with it.

Thanks Ben, I agree. @Vap0r1ze let's try again for 4.2, it was good at least to check how it worked in the wild and find out these issues. Thanks!

@patak-dev should we reopen #3288 then ?


Game crash while trying to place Radiant Resonator

crashlog: https://pastebin.com/D4fx8JPn

Tlauncher and other cracked launchers aren't supported, sorry.


[backport] Handles infinities of the same sign in logaddexp and logaddexp2

Backport of #6172 by @takagi

/test

run jenkins please


Continue playing videos after scrolling past them

Describe the problem
When playing a video then scrolling past it the videos stops once it is out of the view.
Describe the solution
It would be nice to have the video continuously play in the background

Closing as complete in https://github.com/j-fbriere/squawker/issues/111


Is there a way to change the cached image and write this back to disk?

My use case is one where I round profile images after they have loaded but doing so every time can be a bit performance intensive.  My ideal approach would be to do that work once and then save that (modified) asset to the cache for future reads.
Thanks in advance,
Andrew

Hey Andrew,
You should be able to achieve that by creating your own cache. MapleBacon comes with the Storage protocol that's passed a UIImage and is responsible for returning it again for matching URLs. The downloadImage sets the built in storage class as default parameter that you can override it with your own class: https://github.com/zalando/MapleBacon/blob/master/Library/MapleBacon/MapleBacon/ImageManager.swift#L18
Would that work?

Great!  That's exactly what I was looking for - I'll take a look at this and get back to you if I have any issues.


PL file selection for Perfect Chaos

The second part of Perfect Chaos loads PL_J1B.BIN in SA1. In the mod, PL_J0B.BIN is loaded for both parts. I think Perfect Chaos doesn't use the "normal" act numbers though, so it may be trickier to implement.

Looks like it stores the current phase at 0x03C69E28. It writes to it during the switch at 0x0056094D. I'm going to see about exploiting this to load the next palette file.

I've pushed a potential solution but I think it will need some more thorough testing before I consider this fixed.

Seems good enough!


Must use different node versions for installation and execution

Hi, the latest version of lamassu-bitgo presents a conundrum.  It fails to compile native code during installation with any version of node >= 0.12, due to changes in V8 from 0.10 to 0.12, but in order to execute, it requires a minimum node of 4.x due to the usage of 'const' and other similar keywords.

Hey @runderwo. Good observation. A recent update to some of the BitGo module's dependencies necessitated an upgrade of node and thus lamassu-server to 2.6.0.
It isn't required at this point, although we don't have a recommended upgrade path for existing servers, and thus for this version a new server should be used with the lamassu-install script.
This is less of an issue though, as we'll be migrating to our beta, which is about to go into field testing: https://support.lamassu.is/hc/en-us/categories/115000160112-Next-Gen-Beta-


[UI][Container] - Confusing drop down menu for private registry selection for "Select Image".

Version - V0.12.0
In "Add Container" page , drop down menu for private registry selection for "Select Image" shows the "address selected".But the dropdown has the name of the private registry which is confusing. Can we also include the "address selected" value along with the name of the private registry ?

Changed in rancherio/ui#104

Verified Fixed


support for Performance-Timeline & High-Resolution-Time

http://www.w3.org/TR/performance-timeline-2/
http://www.w3.org/TR/hr-time-2/

I can see now User Timing API 、Resource Timing API、Navigation Timing API supported.
ask for Performance-Timeline & High-Resolution-Time

https://webkit.org/status/#specification-performance-observer

+1

+1

+1

Available on various tables, including https://caniuse.com/#feat=mdn-api_performance & https://caniuse.com/#feat=high-resolution-time


Batch state blocks signatures verification

Very nice!  I'll take a look in a bit, if anyone else can too that'd be good.

This PR is exciting! I'm worried about messing with signature verification, as that's a very critical piece of code, but this looks good to me.
Does this speed up bootstrapping?

While it's increasing verification speed up to 40-50% for large amounts of state blocks (I forget to add old test --debug_verify_profile_batch, thx for reminder), currently only 14.4% of blocks are state. So it won't increase current bootstrap speed significantly

What about this process:

In addition to block_processor::blocks there is block_processor::state_blocks
block_processor::add puts state blocks in to the state block queue
block_processor::process_blocks first runs signature checks on everything in the state_blocks deque.  Anything that fails a signature check is dropped.  Anything that succeeds is put in to the blocks deque.  The blocks deque is then processed as normal
Signature checking in removed for state blocks in the ledger_processor
A test is added to prove that incorrectly signed state blocks are rejected.

Seems valid process

Still I think that signature verification shouldn't be removed from ledger processor by default because other functions can use it except block_processor::process_receive_many

MSVC conforms to C90 standards and does not support variable length arrays (C99) which is what is causing the appveyor failures

Have to disable batch signatures for MSVC builds

Other than that LGTM

Awesome work !


update to the latest dart sdk stable version

update to the latest dart sdk stable version
rev the pubspec version in prep for publishing

One of the newer lints doesn't like the underscore we use for the package name placeholder:
Use `lowercase_with_underscores` when specifying a library prefix. • bin/__projectName__.dart:1:58 • library_prefixes

One of the newer lints doesn't like the underscore we use for the package name placeholder:
Use `lowercase_with_underscores` when specifying a library prefix. • bin/__projectName__.dart:1:58 • library_prefixes

This lint has been fixed, I believe – CC @pq
https://github.com/dart-lang/linter/issues/2331

Do one of you mind publishing the latest?

This was fixed as of linter 0.1.124 which should be in dev?

Do one of you mind publishing the latest?

I can publish.

Published.


Edit the description of wheelMode in README.md

It seems like the method of use has changed, but it hasn't been updated.

Thanks @jeongnaehyeok


[Feature Request] OPDS catalog integration

Hi! Loving the app, but right now the biggest pain is having to redownload my ebooks every time I move to another device/browser.
I was wondering if it would be worth adding integration with ODPS catalogs. Calibre exposes an OPDS server by default, so this way I could just connect to my Calibre server (where I store all my ebooks) and grab any book I need.

This would also be a game changer for me. Something like this might be worth looking into https://github.com/NYPL-Simplified/opds-web-client

This would also be a game changer for me too, I'm starting to have too many books to manage effectively with ttsu, would be great if I can just connect to calibre.


State from other form

I'm on version 5.2.5.
I'm new to using this so this is probably a stupid question, but I'm not sure how to get part of a forms state to another forms props.
I have a generic component (address finder) that will be used system wide to provide data to many different forms, it performs an async action and stores the results of that action in its own state.
I have another form in which I want some part of the state from the generic component to populate some of the fields on this form.
What would be the best approach to this?

This is a usage question, and we encourage you to ask it on StackOverflow instead. We try to use the issue tracker for bug reports and feature requests, as well as some discussions, but this appears to be a very localized question.
This is the only way to ensure the same question doesn’t get asked many times in a row, and that folks who have the same question in the future will be able to find it.
I’m closing for these reasons.


Chapter 2 Page 36

I am not sure where it was mentioned that I should do something with the files that are missing after running node_modules. I never saw that I was told to make those files so should they have been generated. See I don't understand because I don't even get a simplest explanation sometimes of what these commands are doing.
packt-web:/var/www/html/web/themes/custom/alps_trips$ node_modules/.bin/webpack --config webpack.config.js --mode development
asset main.js 1.07 KiB [compared for emit] (name: main) 1 related asset
runtime modules 274 bytes 1 module
./js/main.js 30 bytes [built] [code generated]
ERROR in ./js/main.js 1:0-29
Module not found: Error: Can't resolve '../css/tailwind.css' in '/var/www/html/web/themes/custom/alps_trips/js'
resolve '../css/tailwind.css' in '/var/www/html/web/themes/custom/alps_trips/js'
using description file: /var/www/html/web/themes/custom/alps_trips/package.json (relative path: ./js)
Field 'browser' doesn't contain a valid alias configuration
using description file: /var/www/html/web/themes/custom/alps_trips/package.json (relative path: ./css/tailwind.css)
no extension
Field 'browser' doesn't contain a valid alias configuration
/var/www/html/web/themes/custom/alps_trips/css/tailwind.css doesn't exist
.js
Field 'browser' doesn't contain a valid alias configuration
/var/www/html/web/themes/custom/alps_trips/css/tailwind.css.js doesn't exist
.json
Field 'browser' doesn't contain a valid alias configuration
/var/www/html/web/themes/custom/alps_trips/css/tailwind.css.json doesn't exist
.wasm
Field 'browser' doesn't contain a valid alias configuration
/var/www/html/web/themes/custom/alps_trips/css/tailwind.css.wasm doesn't exist
as directory
/var/www/html/web/themes/custom/alps_trips/css/tailwind.css doesn't exist
webpack 5.89.0 compiled with 1 error in 46 ms

I am also getting this error on postcss-loader
error<EMAIL_ADDRESS>The engine "node" is incompatible with this module. Expected version ">= 18.12.0". Got "16.20.2"
error Found incompatible module.
info Visit https://yarnpkg.com/en/docs/cli/add for documentation about this command.

node_modules/.bin/webpack --config webpack.config.js --mode development
Should generate /build and the files main.js, main.js.map, styles.css, and styles.css.map but of course it does not I only get main.js and main.js.map because it appears tailwind.css, tailwind.css.js, tailwind.css.json, tailwind.css.wasm do not exist in /css and I have no clue where I am supposed to get them from. If none of these commands did anything to create them up till now and the files don’t already come with everything in git I am not sure what I am supposed to do.

Ok so clearly I discovered the error with tailwind.css and now I get the following keeping in mind I had to ignore the version issue on postcss-loader:
packt-web:/var/www/html/web/themes/custom/alps_trips$ node_modules/.bin/webpack --config webpack.config.js --mode development
asset main.js 9.35 KiB [emitted] (name: main) 1 related asset
runtime modules 937 bytes 4 modules
orphan modules 39 bytes [orphan] 1 module
cacheable modules 68 bytes
./js/main.js 29 bytes [built] [code generated]
./css/tailwind.css 39 bytes [built] [code generated] [1 error]
ERROR in ./css/tailwind.css (./css/tailwind.css.webpack[javascript/auto]!=!./node_modules/css-loader/dist/cjs.js!./node_modules/postcss-loader/dist/cjs.js!./css/tailwind.css)
Module build failed (from ./node_modules/postcss-loader/dist/cjs.js):
ReferenceError: tailwindcss is not defined
at Object. (/var/www/html/web/themes/custom/alps_trips/postcss.config.js:3:14)
at Module._compile (node:internal/modules/cjs/loader:1198:14)
at Object.Module._extensions..js (node:internal/modules/cjs/loader:1252:10)
at Module.load (node:internal/modules/cjs/loader:1076:32)
at Function.Module._load (node:internal/modules/cjs/loader:911:12)
at Module.require (node:internal/modules/cjs/loader:1100:19)
at module.exports (/var/www/html/web/themes/custom/alps_trips/node_modules/import-fresh/index.js:32:59)
at Object.loadJsSync (/var/www/html/web/themes/custom/alps_trips/node_modules/cosmiconfig/dist/loaders.js:17:12)
at .js (/var/www/html/web/themes/custom/alps_trips/node_modules/postcss-loader/dist/utils.js:61:56)
at Explorer.#loadConfiguration (/var/www/html/web/themes/custom/alps_trips/node_modules/cosmiconfig/dist/Explorer.js:116:42)
@ ./css/tailwind.css
@ ./js/main.js 1:0-29
ERROR in ./css/tailwind.css
Module build failed (from ./node_modules/mini-css-extract-plugin/dist/loader.js):
HookWebpackError: Module build failed (from ./node_modules/postcss-loader/dist/cjs.js):
ReferenceError: tailwindcss is not defined
at Object. (/var/www/html/web/themes/custom/alps_trips/postcss.config.js:3:14)
at Module._compile (node:internal/modules/cjs/loader:1198:14)
at Object.Module._extensions..js (node:internal/modules/cjs/loader:1252:10)
at Module.load (node:internal/modules/cjs/loader:1076:32)
at Function.Module._load (node:internal/modules/cjs/loader:911:12)
at Module.require (node:internal/modules/cjs/loader:1100:19)
at module.exports (/var/www/html/web/themes/custom/alps_trips/node_modules/import-fresh/index.js:32:59)
at Object.loadJsSync (/var/www/html/web/themes/custom/alps_trips/node_modules/cosmiconfig/dist/loaders.js:17:12)
at .js (/var/www/html/web/themes/custom/alps_trips/node_modules/postcss-loader/dist/utils.js:61:56)
at Explorer.#loadConfiguration (/var/www/html/web/themes/custom/alps_trips/node_modules/cosmiconfig/dist/Explorer.js:116:42)
at tryRunOrWebpackError (/var/www/html/web/themes/custom/alps_trips/node_modules/webpack/lib/HookWebpackError.js:88:9)
at webpack_require_module (/var/www/html/web/themes/custom/alps_trips/node_modules/webpack/lib/Compilation.js:5067:12)
at webpack_require (/var/www/html/web/themes/custom/alps_trips/node_modules/webpack/lib/Compilation.js:5024:18)
at /var/www/html/web/themes/custom/alps_trips/node_modules/webpack/lib/Compilation.js:5095:20
at symbolIterator (/var/www/html/web/themes/custom/alps_trips/node_modules/neo-async/async.js:3485:9)
at done (/var/www/html/web/themes/custom/alps_trips/node_modules/neo-async/async.js:3527:9)
at Hook.eval [as callAsync] (eval at create (/var/www/html/web/themes/custom/alps_trips/node_modules/tapable/lib/HookCodeFactory.js:33:10), :15:1)
at Hook.CALL_ASYNC_DELEGATE [as _callAsync] (/var/www/html/web/themes/custom/alps_trips/node_modules/tapable/lib/Hook.js:18:14)
at /var/www/html/web/themes/custom/alps_trips/node_modules/webpack/lib/Compilation.js:5002:43
at symbolIterator (/var/www/html/web/themes/custom/alps_trips/node_modules/neo-async/async.js:3482:9)
-- inner error --
Error: Module build failed (from ./node_modules/postcss-loader/dist/cjs.js):
ReferenceError: tailwindcss is not defined
at Object. (/var/www/html/web/themes/custom/alps_trips/postcss.config.js:3:14)
at Module._compile (node:internal/modules/cjs/loader:1198:14)
at Object.Module._extensions..js (node:internal/modules/cjs/loader:1252:10)
at Module.load (node:internal/modules/cjs/loader:1076:32)
at Function.Module._load (node:internal/modules/cjs/loader:911:12)
at Module.require (node:internal/modules/cjs/loader:1100:19)
at module.exports (/var/www/html/web/themes/custom/alps_trips/node_modules/import-fresh/index.js:32:59)
at Object.loadJsSync (/var/www/html/web/themes/custom/alps_trips/node_modules/cosmiconfig/dist/loaders.js:17:12)
at .js (/var/www/html/web/themes/custom/alps_trips/node_modules/postcss-loader/dist/utils.js:61:56)
at Explorer.#loadConfiguration (/var/www/html/web/themes/custom/alps_trips/node_modules/cosmiconfig/dist/Explorer.js:116:42)
at Object. (/var/www/html/web/themes/custom/alps_trips/node_modules/css-loader/dist/cjs.js!/var/www/html/web/themes/custom/alps_trips/node_modules/postcss-loader/dist/cjs.js!/var/www/html/web/themes/custom/alps_trips/css/tailwind.css:1:7)
at /var/www/html/web/themes/custom/alps_trips/node_modules/webpack/lib/javascript/JavascriptModulesPlugin.js:452:10
at Hook.eval [as call] (eval at create (/var/www/html/web/themes/custom/alps_trips/node_modules/tapable/lib/HookCodeFactory.js:19:10), :7:1)
at Hook.CALL_DELEGATE [as _call] (/var/www/html/web/themes/custom/alps_trips/node_modules/tapable/lib/Hook.js:14:14)
at /var/www/html/web/themes/custom/alps_trips/node_modules/webpack/lib/Compilation.js:5069:39
at tryRunOrWebpackError (/var/www/html/web/themes/custom/alps_trips/node_modules/webpack/lib/HookWebpackError.js:83:7)
at webpack_require_module (/var/www/html/web/themes/custom/alps_trips/node_modules/webpack/lib/Compilation.js:5067:12)
at webpack_require (/var/www/html/web/themes/custom/alps_trips/node_modules/webpack/lib/Compilation.js:5024:18)
at /var/www/html/web/themes/custom/alps_trips/node_modules/webpack/lib/Compilation.js:5095:20
at symbolIterator (/var/www/html/web/themes/custom/alps_trips/node_modules/neo-async/async.js:3485:9)
Generated code for /var/www/html/web/themes/custom/alps_trips/node_modules/css-loader/dist/cjs.js!/var/www/html/web/themes/custom/alps_trips/node_modules/postcss-loader/dist/cjs.js!/var/www/html/web/themes/custom/alps_trips/css/tailwind.css
1 | throw new Error("Module build failed (from ./node_modules/postcss-loader/dist/cjs.js):\nReferenceError: tailwindcss is not defined\n    at Object. (/var/www/html/web/themes/custom/alps_trips/postcss.config.js:3:14)\n    at Module._compile (node:internal/modules/cjs/loader:1198:14)\n    at Object.Module._extensions..js (node:internal/modules/cjs/loader:1252:10)\n    at Module.load (node:internal/modules/cjs/loader:1076:32)\n    at Function.Module._load (node:internal/modules/cjs/loader:911:12)\n    at Module.require (node:internal/modules/cjs/loader:1100:19)\n    at module.exports (/var/www/html/web/themes/custom/alps_trips/node_modules/import-fresh/index.js:32:59)\n    at Object.loadJsSync (/var/www/html/web/themes/custom/alps_trips/node_modules/cosmiconfig/dist/loaders.js:17:12)\n    at .js (/var/www/html/web/themes/custom/alps_trips/node_modules/postcss-loader/dist/utils.js:61:56)\n    at Explorer.#loadConfiguration (/var/www/html/web/themes/custom/alps_trips/node_modules/cosmiconfig/dist/Explorer.js:116:42)");
@ ./js/main.js 1:0-29
webpack 5.89.0 compiled with 2 errors in 235 ms
drew@packt-web:/var/www/html/web/themes/custom/alps_trips$ cd build/
drew@packt-web:/var/www/html/web/themes/custom/alps_trips/build$ ls
main.js  main.js.map

I'll look at this problem in the next few days; if you want to pass this point and go ahead, you can try to switch to the final branch, where everything is completed.

I had some similar issues,
For the "The engine "node" is incompatible" issure I had to install nvm and use that to update to a version of node above 18. Then after I restarted the console yarn stopped working I had to use npm install --global yarn and restart the console again
And as for the top issue, renaming "main.css" (as it is in the book) to "tailwind.css"  fixed that. I didn't get any other issues and this has been enough to get me up through yarn run build:dev on page 38 so far haha

Same issue, same solution as @BThvedt : in /web/themes/custom/alps_trips/js/main.js:
Instead of:
import "../css/tailwind.css";

Use:
import "../css/main.css";

I've updated the yarn command here: https://github.com/PacktPublishing/Modernizing-Drupal-10-Theme-Development/blob/main/ERRATA.md#chapter-2 to fix required versions:
yarn add -D webpack@5 webpack-cli@5 mini-css-extract-plugin@2 css-loader@6 postcss-loader@7


ifconfig: Add gateway property on RHEL/Debian based systems

This reimplements #6279 after our conversion of this resource to use properties. It also adds support for RHEL since that's documented here:
https://www.centos.org/docs/5/html/Deployment_Guide-en-US/s1-networkscripts-interfaces.html
Signed-off-by: Tim Smith<EMAIL_ADDRESS>

Looks like there's more to do for RHEL so I'm actually going to close this out in favor of the sep PR. So many PRs...

This is in fact the correct approach.


[6.0] Duplicate entry for primary key error when sending notifications to multiple users

Laravel Version: 6.0.0
PHP Version: 7.3.1
Database Driver & Version:

Description:
When i try sending notifications to multiple users, i get this error
SQLSTATE[23000]: Integrity constraint violation: 1062 Duplicate entry 'c6c5825a-ffdf-4721-9e3e-db1382000f57' for key 'PRIMARY' (SQL: insert into `notifications` (`id`, `type`, `data`, `read_at`, `notifiable_id`, `notifiable_type`, `updated_at`, `created_at`) values (c6c5825a-ffdf-4721-9e3e-db1382000f57, App\Notifications\BookedValuation, [], ?, 1, App\PartnerUser, 2019-09-10 07:05:05, 2019-09-10 07:05:05))

please note that the notification to the first user is completed before it fails
Steps To Reproduce:
send notification to multiple users e.g
use Illuminate\Support\Facades\Notification;
use App\User;
...

$users = User::all();
Notification::send($users, new BookedValuation($data1, $data2));

Hey there,
Can you first please try one of the support channels below? If you can actually identify this as a bug, feel free to report back and I'll gladly help you out and re-open this issue.

Laracasts Forums
Laravel.io Forums
StackOverflow
Discord
Larachat
IRC

Thanks!


Allow URIs for bundle and bundle sha

Bundles may be sourced externally so allow for a URI to be sourced instead of a local zip file.

create bundle_uri input
create bundle_sha input (optional?)

There doesn't seem to be much demand for this and really, it could get quite complicated so I'm closing this.  The original requester no longer needs it.


[api] Provide access to picture for services and service_requests

Extending the virtual attribute picture to:
/api/services
/api/service_templates
With this following is now doable:
GET /api/services?expand=resources&attributes=picture,picture.image_href
GET /api/service_requests?expand=resources&attributes=picture,picture.image_href
GET /api/service_templates?expand=resources&attributes=picture,picture.image_href
https://trello.com/c/Vpcpc5RJ

@imtayadeway @gtanzillo @dclarizio please review.  Thanks.

:+1: LGTM


OCM-13068 | fix: Add required flags to oprole creation for cluster manual mode

/cherry-pick release_1.2.49

/retest-required

/lgtm

/retest-required


Expose lua-resty-auto-ssl allow_domain functionality to end user (Let's Encrypt auto HTTPS)

See also:

https://github.com/GUI/lua-resty-auto-ssl/issues/38
https://github.com/GUI/lua-resty-auto-ssl/issues/26
https://github.com/GUI/lua-resty-auto-ssl/issues/170

The AP-ALB v0.4-beta still not expose to the user ways to customize the allow_domain, not even as function. This issue is for improve this.
This is our current rule that is hardcored (not able to not even customize with Ansible).
    # Initial setup tasks.
    init_by_lua_block {
      auto_ssl = (require "resty.auto-ssl").new()

      -- Define a function to determine which SNI domains to automatically handle
      -- and register new certificates for. Defaults to not allowing any domains,
      -- so this must be configured.
      auto_ssl:set("allow_domain", function(domain)
        return true
      end)

      auto_ssl:init()
    }

It's ok for testing (whitelist everything), and in fact was on the documentation of GUI/lua-resty-auto-ssl, but can hit Let's Encrypt limits fast for invalid domains pointing to IP of the server.

Implemented. Still allow end user implement raw lua code with alb_acme_rule_lua, but some common user cases are done using plain YAML.
This may specially useful for who did not want learn to debug the OpenResty full stack
Example from v0.8.6-alpha
### AP-ALB ACME ________________________________________________________________
# BY USING Let's Encrypt, even if automated for you, you AGREE with
# Let’s Encrypt Subscriber Agreement at https://letsencrypt.org/repository/

alb_acme_production: true

alb_acme_rule_ips_allowed: false # ACME (Let's Encript at least) will HTTPS for IPs, so don't even try

# Exact match
alb_acme_rule_whitelist: []
alb_acme_rule_whitelist_file: '' # not implemented... yet
alb_acme_rule_blacklist: []
alb_acme_rule_blacklist_file: '' # not implemented... yet

# Suffix match (e.g. for subdomains) and prefix match (e.g. if any full domain, if start with these values)
alb_acme_rule_whitelist_suffix: []
alb_acme_rule_whitelist_prefix: []
alb_acme_rule_blacklist_suffix: []
alb_acme_rule_blacklist_prefix: []

# alb_acme_rule_lua inject custom lua inside GUI/lua-resty-auto-ssl allow_domain function.
alb_acme_rule_lua: |
  -- FILE: /usr/local/openresty/nginx/conf/nginx.conf
  -- NGINX CONTEXT: http/init_by_lua_block/auto_ssl:set("allow_domain", function(domain)
  -- See https://github.com/GUI/lua-resty-auto-ssl
  -- Note 1: Inside lua blocks (like this one) "--" is used for start comments
  --       and not "#"
  -- Note 2: your custom code should 'return true' or 'return false'

# alb_acme_rule_last define your "default" behavior for what was not explicitly
# whitelisted/blacklisted
alb_acme_rule_last: true

# This value is infered from alb_acme_production. But you can customize yourself
alb_acme_url: "{{ 'https://acme-v02.api.letsencrypt.org/directory' if alb_acme_production else 'https://acme-staging-v02.api.letsencrypt.org/directory' }}"


Improve the error print of image inspect

I think we should return the err of GetImage(), so that user can get the reason why no such image.
Signed-off-by: Yanqiang Miao<EMAIL_ADDRESS>

This one is kind of interesting.  I couldn't get this error message to appear via the docker cli.  In my testing it appears that this error, while generated, is usually not printed to stderr and instead the cli will generate a new error message in it place.  So this would not benefit the cli user w/o more changes.  Which, btw, might be a good thing to do.
So, looking at the REST API:
$curl http://localhost:2375/v1.12/images/qweqweqw/json
No such image: qweqweqw, error: no such id: qweqweqw

$curl http://localhost:2375/v1.12/images/qweqi,weqw/json
No such image: qweqi,weqw, error: Error parsing reference: "qweqi,weqw" is not a valid repository/tag: invalid reference format

Here we do see the error with the extra error info - which is good. However, the total error message itself is kind of awkward. The 2nd one in particular makes us sound confused - is there a parsing error or can we not find the image by that name? Since the error is coming from a func called LookupImage it might be better to focus on what this func was doing - so, I think it might be better to change the error message to be:
Error looking for image: ?????, cause: no such id: ????
Error looking for image: ?????, cause: Error parsing reference: ...
Or something like that.

We need to be careful; IIRC, no such must remain in the response, for our error-code handling

First, sigh. :-(
Second, we may want to do more investigation then because if there's a parsing error I wouldn't expect a 404.

Yeah, it ain't pretty.
Wrt correct status code, perhaps a 400 or 422

Thanks @duglin @thaJeztah   I have updated, PTAL.

While I would prefer if we generated a better error, in order to do that its a much bigger piece of work. For example, this (really bad) pattern of a func returning an error when we can't find something instead of just "nil" for the object we're looking for, makes it really hard to detect when there's a real error (e.g. like the parsing error in this case) vs just a normal (non-error situation) of the object just not being there - which can easily be detected by the 'nil' for the object pointer. Meaning, a non-nil error would be reserved for real errors (non-404's) and we could then act accordingly.  But, this is much bigger than this issue and would require a pretty big change throughout the system.  A good change, IMO, but beyond the scope of this trivial PR.
@miaoyq thanks for the PR and patience.
so, LGTM.

@AkihiroSuda  All checks have passed, PTAL, Thanks

@vdemeester could you have a quick peek to check if https://github.com/docker/docker/blob/master/integration-cli/daemon/daemon.go#L764-L767 needs to be updated as well (this PR changes no such to be lowercase)

@thaJeztah @vdemeester  Updated!  PTAL  Thanks.


Feature Request: Auto-Pages + Page Markup Tag

This feature lets Webmasters type something like <page type="feed" theme="dark"> and have the page automatically load a per-defined browser theme, which includes the fully responsive CSS and built-in theme, with a single tag. Without any CSS, they then have a well-designed page that only requires them to assign content.
Advantages:

Webmasters can effortlessly create beautiful (and consistent) sites.
Webmasters don't have to build out full, responsive CSS. It's all done for them.
Standard CSS is already saved within the browser, saving on data exchange.
The browser can support mods so that users can choose how default themes are viewed.
Drastically reduced workload, much faster build time. Lets people focus more on what matters if CSS is not their primary concern.

I should also clarify that there are multiple page types. In this case feed was the example, where that would be like a social feed. You could have options like article where the content blocks are organized by text, media blocks, etc. You could have others like workspace, game, chatbox, etc.

I feel like this is a pretty niche feature so it's not currently planned


Impossible to load not well-formed GPX

I want to show on the map a GPX, which is being recorded right now. This GPX does not have closing tags, of course. So I have a "XML Parsing Error: no root element found".

I don't think handling this use case necessarily belongs at this layer. You should be feeding correct GPX data to leaflet-gpx, for example by concatenating the appropriate closing tags before passing the GPX content in:
var gpx = '...'; // assuming you're accumulating GPX data into this string
new L.GPX(gpx + '</trkseg></trk></gpx>', ...);


Selected tree icons hardly visible in light+ theme

With the (default) Light+ color theme, icons in selected tree items in the Git view are black on dark blue. They should probably be inverted.

VSCode Version: 1.32.1
OS: Linux x64 4.15.0-46-generic

Duplicate of #55857


Deep nested data validated wrong - nested rule values overwrite root rule values

Livewire at the moment seems to handle deep nested data and validation in a wrong way. The given example results in such wrong way of handling it.
// View
<input type="text" wire:model="items.{{ $loop->index }}.api_key" />
<input type="text" wire:model="items.{{ $loop->index }}.api_secret" />
<input type="text" wire:model="items.{{ $loop->index }}.from" />
<input type="text" wire:model="items.{{ $loop->index }}.to" />

// Component
public function persist(): void
{
    $data = this->validate([
        'items'              => ['required', 'array'],
        'items.*'            => ['array'],
        'items.*.api_key'    => ['required', 'string'],
        'items.*.api_secret' => ['required', 'string'],
        'items.*.from'       => ['required', 'numeric'],
        'items.*.to'         => ['required', 'numeric'],
    ]);

    $this->getModel()->settings()->set('notifications.nexmo', $data['items']);
}

This line changes the items property from being an associative array with nested items to simply become 'items' => 'items.*.to'.
I tested this with various different nested rules and it seems to always overwrite the root rule with the last nested rule. What I mean by this is that items is the root rule and items.*.to is the last nested rule and that last nested rule overwrites items with its value.

You're right, that line was clobbering the validation input.
I fixed this, and the fix will be available in the next release.


Is there a way to increase returned results past 200 entries?

It appears when running Get-AzSentinelIncident, it only returns the last 200 results, whether they are open or closed. We were not able to find a limit in the AzSentinel.psm1 code for the function.
It would be nice to increase or set a time frame in the script an increase results past 200 returned cases.

hi @jeffhoyo thanks for your reply, I will add a switch -all that you can use to pull all the incidents, I am also working to add some additional filter options like, only opened incident, closed, time range etc. in the feature  release. please let me know if you have some filter ideas.


18640 Amalgamating business table (initial)

Issue #: bcgov/entity#18640
Description of changes:

app version = 5.6.5
removed unnecessary re-export
added initial BusinessTable component
renamed property in amalg interface
updated filing save/restore
added global warning (orange) colour
added Business Status sub-component
added basic functionality to table
added Business Statuses enum
added businesses table to store (with default data for now only)
added initial validation code

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of the bcrs-entities-create-ui license (Apache 2.0).

Temporary Url for review: https://business-create-dev--pr-586-9detgijh.web.app

/gcbrun

Temporary Url for review: https://business-create-dev--pr-586-9detgijh.web.app

/gcbrun

Temporary Url for review: https://business-create-dev--pr-586-9detgijh.web.app


bug

Microsoft PowerToys version
<IP_ADDRESS>
Installation method
PowerToys auto-update
Running as admin
No
Area(s) with issue?
PowerToys Run
Steps to reproduce
Version: <IP_ADDRESS>
OS Version: Microsoft Windows NT 10.0.22621.0
IntPtr Length: 8
x64: True
Date: 1/19/2023 1:56:05 AM
Exception:
System.InvalidOperationException: Dispatcher processing has been suspended, but messages are still being processed.
at System.Windows.Threading.Dispatcher.WndProcHook(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
at MS.Win32.HwndWrapper.WndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
at MS.Win32.HwndSubclass.DispatcherCallbackOperation(Object o)
at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)
at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Int32 numArgs, Delegate catchHandler)
✔ Expected Behavior
No response
❌ Actual Behavior
No response
Other Software
No response

/dup https://github.com/microsoft/PowerToys/issues/18166

For any users that are able to replicate this consistently, can you please update to 0.68.1 and disable thumbnail generation to verify if it fixes the issue? Please let us know on #18166!


Pr coretag

Refactor for RackHD stuff and fixes for wait_for_vm.

All changes are in from our side for this pull request--let us know if you have questions or additional changes for us.


key binding of Markdown enter on macOS should command + enter instead of ctrl + enter

Thanks for the request @kgtkr! We'll discuss it in an upcoming meeting.

Thanks for the request @kgtkr! We'll discuss it in an upcoming meeting.

Closing as VS Code doesn't show that keybinding hint anymore.


Failing to log in to SkySpark with correct credentials

Tried testing with some simple code with skyspark with the code at the bottom of this issue. The result is posted below:
RESULT
False
<GetGridOperation failed>

CODE
from pyhaystack.client.skyspark import SkysparkHaystackSession
session = SkysparkHaystackSession(uri='http://url_to_server',
                                username='myusername',
                                password='secretpassword',
                                project = 'project')

if(__name__ == '__main__'):
    about = session.about()
    print(session.is_logged_in)
    print(about)

Thanks for reaching us.
I've tried your snippet using niagara client and it works. Unfortunately, I don't have actually an access to a Skyspark server.
Would you accept to share your login info in private ? I would then be able to look at it.
My email is in my Github profile

Hi,
I might be able to create an account on the demo project and hand you the details. I'll see if I can get permission to do this.

Hi Christian,
I have just created a temp account and sent you the details

Actively working on

Is there any publicly visible documentation for SkySpark?  I'll admit I ported the old needle sources to the new API blindly, I don't have access to a SkySpark server to test on.
I recall looking on their website for details but didn't see any.

beyon-d.net seems to be up to date

Ahh, that's why I didn't spot it, completely different site. :-)
https://www.beyon-d.net/doc/docSkySpark/Rest.html#auth would have been a big help.

@candronikos Please have a look to : https://github.com/ChristianTremblay/pyhaystack/tree/skyspark_login
I'm able to login, retrieve site, about... but I have some problems with find_entity. Seems to be related to hszinc... I'll give credentials to @sjlongland so he can make tests.

Forgot one detail : it works on Python 3.... we'll have a look to make it work with Python 2

Tested the code on my machine. Looks good so far! I removed the details of the response body for privacy but they're correct.
<GetGridOperation done: <Grid>
	Columns:
		productUri
		whoami
		serverBootTime
		projName
		tz
		moduleName
		serverName
		productName
		haystackVersion
		productVersion
		moduleVersion
		serverTime
		hostModel
	Row    0: ""DETAILS_HIDDEN""
</Grid>>

Troubles appears with :
sensors = session.find_entity(filter_expr='sensor').result
You can join gitter to share more details :
https://gitter.im/ChristianTremblay/pyhaystack

hszinc is tripping up on the grid that gets returned by SkySpark.  A simple read of site entities worked, but not equips, there's something there that the parser doesn't like.
I've grabbed a copy of the offending grid and I'll have a look when I get a chance.  In the meantime, you can force pyhaystack to use JSON serialisation by using the following:
import hszinc
from pyhaystack.client.skyspark import SkysparkHaystackSession
session = SkysparkHaystackSession(uri='http://xxx',
                         username='xxx, password='xxx, project='xxx', grid_format=hszinc.MODE_JSON)

This is not ideal, but it might get you going.

Remaining bug : Make Python 2 & 3 work
string encoding is giving me a hard time.

https://github.com/ChristianTremblay/pyhaystack/commit/578b2691638fa6ac1da20ce803dc3b7b951e8907
Solve the Python 2/3 compatibility

Hello. I need a Python 2.6 to Skyspark interface. I try long to make it runable. But i have the same Problem with   failed

I can't guaranty it'll work on 2.6 as we use a lot of features that are 2.7-3.
Can you be more precise about the bugs you meet ?
Also, be sure to make your tests with dev branch as some bugs have been noticed in Skyspark with master branch.

I would seriously not bother with Python 2.6.  Most platforms have moved on from that release, the only OSes I can think of that depend on that release are circa 2010 or earlier, which should be considered unsupported security liabilities.
Python 2.7 is still supported because Python 3.x support was in its infancy until very recently on most Linux distributions (IMO it's a mess in Debian even in Jessie), and really is on borrowed time: the upstream Python project wants to kill off the 2.x branch.
If you're starting from scratch, I'd seriously recommend going to Python 3.4 or later if possible, as this was the first of the 3.x series that was particularly well supported.  If backward compatibility with Python 2 modules is needed, then recent 2.7 is the best option.

Thanks, but the system i will connect runs under SLES 11 (python 2.6.5).
I had read something about "python" environments.. and the possibility to
run both Versions..
But the effort is too big for me...
I only will get a points-list from SkysPark and perhaps import points from
foreign system..
My idea is to minimize your pyhaystack (only communication to SyksPark).. I
don't need numpy or other numerical manipulations under python..
And if hszinc make trouble to run under this python Version, i'll change to
json...
Are my reflections OK ?
2016-10-30 3:19 GMT+01:00 Stuart Longland<EMAIL_ADDRESS>
I would seriously not bother with Python 2.6. Most platforms have moved on
from that release, the only OSes I can think of that depend on that release
are circa 2010 or earlier, which should be considered unsupported security
liabilities.
Python 2.7 is still supported because Python 3.x support was in its
infancy until very recently on most Linux distributions (IMO it's a mess in
Debian even in Jessie), and really is on borrowed time: the upstream Python
project wants to kill off the 2.x branch.
If you're starting from scratch, I'd seriously recommend going to Python
3.4 or later if possible, as this was the first of the 3.x series that was
particularly well supported. If backward compatibility with Python 2
modules is needed, then recent 2.7 is the best option.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/ChristianTremblay/pyhaystack/issues/14#issuecomment-257127854,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ATDM0RWdpFxoFpv01Zl6JzEXaDRv-kbFks5q4_7EgaJpZM4IqNzN
.

On 31/10/16 20:50, jjproe wrote:

And if hszinc make trouble to run under this python Version, i'll change to
json...

Won't make a sceric of difference.  hszinc is used in both modes, just
in ZINC mode it does its own serialisation/deserialisation, whereas in
JSON mode, the json module does the heavy lifting.
The same classes are used to represent values in both modes.
There's talk of a Python 2.7 binary as part of the OpenSuSE distribution:
https://forums.suse.com/showthread.php?5293-Python-2-7-for-SLES-11-SP3
SLES 11 is quite dated by the looks of things, so you likely won't see
anything official in terms of Python 2.7 or 3.x.  SLES 12 might be worth
investigating, the other option might be to look at Docker and running a
newer Python environment in a container.
Stuart Longland (aka Redhatter, VK4MSL)
I haven't lost my mind...
...it's backed up on a tape somewhere.

Locking the issue and linking here : https://github.com/ChristianTremblay/pyhaystack/issues/31


Document how to mock out helper methods with rack-test

I've been trying, searching, and then guessing, on how to mock out helper methods so I can test a controller. To no avail.
I have a helper
My::App.helpers do
  def current_user
    session[:uid]
  end
end

and a controller
My::App.controllers :api do
  get '/authenticate' do
    authenticate unless current_user
  end
end

and a test
describe 'AuthController' do
  it 'should not authenticate if already authenticated' do
    allow_any_instance_of(My::App).to receive(:current_user).and_return('123xyz')

   get '/api/authenticate'
  end
end

Naively I assumed that the allow_any_instance_of part via RSpec would be enough. However this code is not triggered.
Alternatively I tried
before do
  app(My::App) do
    set :current_user, '123xyz'
  end
end

No effect.
What is the preferred way in Padrino to support such behaviour?

Hi @cburgmer, great that you want to test your helpers. I've written about it under http://wikimatze.de/testing-helpers-in-padrino - please let me know if this helps you.

Thanks for the link, but in my case I don't want to test the helper, but rather mock the helper so I can test the controller.
In my case I've worked around the particular problem by treating the test case as an end-to-end test, and mocking out the session via rack.
RackTest is a nice thing, however it is not the right answer to when I want to test my controller via a unit test.

I did it with a mocking-class, which includes the helper and then mock the helper calls for this helper in the spec. E.g.:
describe SessionsHelper do
  before do
    class SessionsHelperKlass
      include SessionsHelper
    end

    @session_helper = SessionsHelperKlass.new
  end

  ...
  describe "#current_user?" do
    it "returns true if current user is logged in" do
      user = User.new
      expect(@session_helper).to receive(:current_user).and_return(user)
      expect(@session_helper.current_user?(user)).to be_truthy
    end

    it "returns false if user is not logged in" do
      user = User.new
      expect(@session_helper).to receive(:current_user).and_return(false)
      expect(@session_helper.current_user?(user)).to be_falsey
    end
  end
  ...
end

You then need to find a way to inject this helper in your controller test.

Closing as https://github.com/padrino/padrino-docs is the better place for documentation requests.


Question on serialising classes

Hi there. I noticed your documentation mentioning you need to annotate properties with @export. How would you achieve the following as Godot does not allow classes to be exported.
Example code:
class_name PlayerData
@export var inventory : Inventory
@export var skills : Skills

I'm currently using my own implementation of a JSON serialiser and stumbled upon your repo here. So I'm wondering if the above is possible. Thanks

Hi there. I noticed your documentation mentioning you need to annotate properties with @export. How would you achieve the following as Godot does not allow classes to be exported.
Example code:
class_name PlayerData
@export var inventory : Inventory
@export var skills : Skills

I'm currently using my own implementation of a JSON serialiser and stumbled upon your repo here. So I'm wondering if the above is possible. Thanks

Yes, it does. The latest commit adds support for nested resources, along with existing support for multi-nested objects.


Fix race condition in ExponentiallyDecayingReservoir's rescale method

Fixes issues #1005 and #793 - note that in #793 the longPeriodsOfInactivityShouldNotCorruptSamplingState test did not cover multiple concurrent requests after a long idle period.
The race condition currently occurs when two threads update the reservoir concurrently - after the first thread has successfully updated nextScaleTime (line 162) but before the write lock is obtained (line 163) a second thread updates the reservoir (line 95+).  With several threads pushing updates concurrently this presents a narrow window during which the second thread may obtain the lock before the first resulting in a corrupt reservoir state.  Note, however, that if a snapshot is requested just prior to the two concurrent updates the read lock will already be active when the two threads enter rescaleIfNeeded, resulting in a much larger window for this race condition.

Thank you very much for the fix and very detailed unit test!

I have an issue with this. The compareAndSet operation is atomic so it shouldn't allow more than one thread into that if block. Granted 'lockForRescale()' does effectively the same thing, however it is a more expensive operation than the compareAndSet.

The issue as I see it:

Thread 1 calls update
Thread 2 calls update
Thread 1 calls rescaleIfNeeded
Thread 2 calls rescaleIfNeeded
Thread 1 reads the CAS and updates it
Thread 1 gets swapped out
Thread 2 reads the updated CAS and exits
Thread 2 obtains the read lock and works with a new weight, but old (not scaled) values
Thread 1 gets swapped in and acquires a write lock, but it's too late

Basically, the CAS only guarantees that nextScaleTime gets updated atomically, but not other reservoir's state.

In case the fix the correct, I would like to cherry-pick this change to the 3.1.3-maintenance branch to provide users who affected by this bug an easy path to upgrade.

I didn't get more reasons opposing this fix, so I'm going to move this bugfix to the 3.1.3 branch. In the worst case, we have a performance regression, in the best we fix a concurrency bug.

@arteam, I think your comment:
"Thread 2 obtains a read lock and works with a new weight, but old (not scaled) values"
is incorrect.
The weight becomes new when startTime gets updated, but it gets updated only under the write lock by thread 1.
I still think this is a good change, as it simplifies reasoning about the code.


Only working for Melle weapons

Trying to add opacity because I want to completely fill my weapons with their respective combat colour, but it's only working for melle, It goes fully red but the other cb styles don't

Yeah this just randomly doesn't work for some equipment. Just now it stopped working for my magic set.

Could it also have issues with Tumeken/Sang? Equiping these items when set to mage, act as melee? Is this related?


Excluding a tag results in no tests being run

Summary
I invoke Cucumber like so:
node_modules/cucumber/bin/cucumber.js --tags '~@deprecated'

My features look like this:
homepage.feature:
Feature: homepage
  Scenario: visit homepage
    Given I am on "/"

homepage-old.feature:
@deprecated
Feature: homepage
  Scenario: visit homepage
    Given I am on "/home"

This results in exactly 0 tests being executed.
Expected Behavior
The one test without the @deprecated tag is run.
Current Behavior
No tests are run.
Possible Solution
??? (Fix the --tags CLI impl.)
Steps to Reproduce (for bugs)
See Summary.
Your Environment
cucumber: 2.0.0-rc.9
node: v7.9.0
OS: Debian GNU/Linux 8 (jessie)

Note the breaking changes in 2.0.0-rc.0 with respect to tags.


ARTEMIS-1495 No more Executor.flush!

I've added a test for the shutdownNode method in a separate PR on your repository: let me know if it mirrors your expectation of what the method is supposed to do :+1:
Re performance implications of this change: I've benchmarked it and the synchronized block makes a pure in-memory execution (i.e. no I/O involved) of the ProcessorBase about 7 time slower on my box when biased locking is disabled to mimic predicatable latencies and to avoid the JVM to trick us (-XX:-UseBiasedLocking is explained here).
I have to do benchmarking on the overall broker too, but I suppose it will impact latencies if not the thoughput too.
IMHO would be better to implement this using only (collaborative) lock-free algorithms that allow predicatable (and lower) latencies on hot paths: I've pushed another PR with an implementation of it for our use case (to review/discuss).
On the hot paths it cost just a volatile load (on x86 is just a load and compare).

@franz1981 I'm surprised the lock would be that much slower.. there is nothing competing for that long..
The advantage of the lock here is reentrancy. it's now possible to shutdown within the current executor. (even though I won't recommend that).
I've tried a lock free thing using the state.. but it seemed simpler...
I will try your PR.. just one thing.. you sent the PR to a wrong branch.. should be  clebertsuconic:artemis-1495

I have measured the lock version against the lock free and I don't see any difference.
The code is supposedly single threaded most of the time.. for that reason using the JVM lock didn't change much the perf.
I will take the lock free version  you made though.. as it's extending the same logic we have now.

I will close this as I am still working on this.

I am going to reopen this.. but will close it for now.

@franz1981 if you could take a look here please.. it's the last version I have...
I will reopen this same PR once I have the testsuite done completely tomorrow.

@clebertsuconic I've just pushed a PR to your version with very few changes (but sadly seems more using diff on the code) mostly perf dependent and to make the code a lil more documented: I'm happy with your changes and the added test too, very well done!!!!! :+1:
Let me know if the changes I've pushed seems good considering what are your expectations on the mechanics of the final version.
Just a note (if possible): now we have some sanity tests on the OrderedExecutor hence I will be super happy to see the missing ones for the other critical methods, if any (eg: flush, shutdown)..if is not possible we'll add them later.

I've merged this myself after extended review between me and @franz1981 , and extensive testings.
We can send extra commits to master later if anything is still needed to be done.

@clebertsuconic well done!!!!!!

@franz1981  you too :)


Invalid content /en/testnets/cardano/get-started/installing-and-running-the-cardano-node/

At the bottom of "https://developers.cardano.org/en/testnets/cardano/get-started/installing-and-running-the-cardano-node/"

These links leads to wrong path (missing "/testnets/)
For example:
"https://developers.cardano.org/en/cardano/get-started/installing-and-running-the-cardano-node/building-the-node-using-nix/"
should be changed to:
"https://developers.cardano.org/en/testnets/cardano/get-started/installing-and-running-the-cardano-node/building-the-node-using-nix/"
Each link listed on the page has this issue.

This issue is now fixed, thank you!

This issue is now fixed, thank you!


feat(cast): get create2 address

Motivation
Compute the address that would result from a CREATE2 operation with the given deployer, salt and either initCode or initCodeHash.
The following is a test script using ethers.js:

Solution
Add argument salt to create2 command.
cast create2 --deployer=0x8ba1f109551bD432803012645Ac136ddd64DBA72 --salt=0x7c5ea36004851c764c44143b1dcb59679b11c9a68e5f41497f6cf3d480715331 --init-code=0x6394198df16000526103ff60206004601c335afa6040516060f3
0x533ae9d683B10C02EbDb05471642F85230071FC3

cast create2 --deployer=0x8ba1f109551bD432803012645Ac136ddd64DBA72 --salt=0x7c5ea36004851c764c44143b1dcb59679b11c9a68e5f41497f6cf3d480715331 --init-code-hash=0x9fd9ed530ad2d3bac509a72be6fb4b53ff252bef5702e88e99a0718cf4433d02
0x533ae9d683B10C02EbDb05471642F85230071FC3

should note either in the salt docs or in the command docs that this is also an option separate from the default salt mining with filters

relevant documents for the salt options have been added.


Apply styles to a subset of the text being added?

when calling .drawText("some text to draw", { ...options }), is there a way to have text styles apply to only a subset of the text being added? Say, I want to change the font color of "some text" but leave "to draw" as is. Or just a way to add styles to text separately from the .drawText() call?

I doubt you can draw text with different styles with single drawText call, at least i didn't find a way to do it.
Instead I made a parser which splits text into array of strings. If string starts with   and ends with  i swap current font to bold and drawText.
I also used code for line wrapping made by raphaelvazuso in this issue

@MonteePoke is spot on!


Added tests for errors thrown in parsers.

Fixes #31.

@jaredweiss Please review.

:thumbsup: LGTM


Spelling mistake of an Object method in Intellisense for JavaScript

Does this issue occur when all extensions are disabled?: Yes

VS Code Version: 1.59
OS Version: Debian 10

Steps to Reproduce:

When we begin typing, it is suggested: Object.getOwnPropertyDescriptor() instead of the real Object.getOwnPropertyDescriptors() method
It raises an error: Uncaught TypeError: can't convert undefined to object

It's not a spelling mistake - Object.getOwnPropertyDescriptor (ES5) in an actual method that predates Object.getOwnPropertyDescriptors (ES2017) so suggestion is correct.
/needsMoreInfo
Do you have tsconfig.json or jsconfig.json in that workspace? If yes - make sure that libs has at least es2017 in list.
However, in case of folder without configuration and only test.js is shows both

Okay, so  thanks for the information.


Update WCAG 2.0 -> 2.1

https://content-guide-test-staging.apps.y.cld.gov.au/

Thanks @sirleech Suggest we hold off merge until we have the missing guidance. You were right :) but this is still useful even if we can't merge it just yet.

Doing some spring cleaning. Changes here may have been superseded by recent WCAG material published on the site.


Bumped sdk

see https://github.com/specklesystems/speckle-sharp-sdk/pull/66

closing in favour of https://github.com/specklesystems/speckle-sharp-connectors/pull/122
Idk why buy my ide is can't restore, I guess


Too many devices to manage

Hi, I have an account that is being used in a CI automation process with autoscaling instances. Those instances are "self registered" as devices to my Keybase account.
Since some weeks ago we started noticing some errors when new instances are trying to connect to keybase with "device name conflict" - That's not a problem on keybase side.
The problem that I want to report here is that after figuring out this condition, we tried to remove old devices from the authorized devices list, but we failed doing it, either via CLI or GUI.
The CLI error is "ERROR 413 Request Entity Too Large", while the GUI just fails without any information.
My bet here is that the client is trying to send the full list of authorized devices to the API/backend, and since we have more than 6k devices registered, it is just above the limit.
If this is the case, I guess the client should behave differently, by just sending the device to be removed (it doesn't even need to request the full list of devices).
Anyway, I'd love to get some help with alternatives to clean up our authorized devices list. Either 1 per "request" or by sending batches of device IDs to be removed.

I'm having the same problem... is anyone else having this issue?


Hold an Exit this Page team retro

What
Run a team retro to reflect on designing, building and publishing Exit this Page.
Why
So we can identify key learnings which will improve future components and patterns we build.
Who needs to work on this
Izabela
Who needs to review this
Kelly
Done when

[x] Scheduled date (Sep 2023)
[x] Asked team to note reflections whilst still fresh
[x] Planned format
[x] Run retro and agreed actions

This retro was run with the available team members on 13 September 2023. For anyone on the team looking for access to the retrospective Padlet board, feel free to ask Izabela.


[feat] Add support for sending apns-id

This will allow user to define the apns-id.

Thanks,

Thanks,

@kylebrowning after merging this please consider publish a version in order to fix vapor-apns.
Thanks,

@kylebrowning after merging this please consider publish a version in order to fix vapor-apns.
Thanks,


Add coord_system kwarg to get/apply_sun_pitch_yaw

Description
The current definition of yaw about the sun line matches ORviewer, but this does not match the engineering convention where +yaw is in the same sense as spacecraft body yaw.
The new default matches the engineering sense: it goes from 0 to 360, and has zero be defined as the ECI z-axis if the Sun is at exactly RA = Dec = 0.
This PR adds a keyword argument coord_system which can take the values "spacecraft" or "ORviewer".
Fixes #30
Interface impacts

Changes the sense of the yaw parameter. This is only used internally and should be OK.
Testing

Unit tests

[x] Mac (new unit tests)

(ska3) ➜  ska_sun git:(add-spacecraft-system) git rev-parse HEAD
3579ca1593a3fafb12d7cd67bec4c1de7cdbba42
(ska3) ➜  ska_sun git:(add-spacecraft-system) pytest
====================================================== test session starts ======================================================
platform darwin -- Python 3.10.8, pytest-7.2.1, pluggy-1.0.0
rootdir: /Users/aldcroft/git, configfile: pytest.ini
plugins: timeout-2.1.0, anyio-3.6.2
collected 19 items

ska_sun/tests/test_sun.py ...................                                                                             [100%]

====================================================== 19 passed in 4.62s =======================================================

Independent check of unit tests by [REVIEWER NAME]

[ ] [PLATFORM]:

Functional tests

Plotted the yaw value around the 2024:036 NSM yaw bias maneuver:

We still don't have much data to line up.  With regard to a "positive yaw bias of 0.025 deg/s for 30 minutes", I thought maybe a positive bias would move us in the negative yaw direction.  But I guess the sign convention could be the "bias that makes it go positive" is positive?

I think the language is now unambiguous and clear. There is no ambiguity in what a "positive" number is, and so the "positive yaw bias" refers to the value of +0.025 deg/s that is used as input when creating command loads from an RTS.
I specifically added this text to both of the docstrings to remind our future selves.

We still don't have much data to line up.

I'm not sure what that means, but with regards to confirming a sign convention you only need one case.

Regarding "with regards to confirming a sign convention you only need one case." sure, I just hadn't been looped in on this case.  It sounds like you have the convention from the RTS which is fine.  I also wasn't sure what you plotted for yaw to confirm it matches expectations -- I assume that is just derived using the code here.

We'll need an update to sparkles test_find_er_catalog to go with this.

I added a link to the notebook I used to make the plot in the description and here.

For reference, the yaw bias RTS is named A_TIMED_YAWBIAS.RTS. This appears in Slack in #anomaly_response_recovery along with "positive yaw bias of 0.025 deg for 30 mins".


fix: problems with paths with spaces

Earlier today, I encountered a problem when adding files with spaces in their name. Closing and reopening Neovim or even just opening the Tags Window would lose part of the file name and I could no longer open the correct file via Grapple.
Example: "this is a file.md" would become "file.md", everything up to the part after the last whitespace was dropped.
I figured this would be reasonably simple to fix and looked into it myself. My code is probably pretty bad, but it seems to work, and I included some comments and new tests.

Hi @derSicking, thanks for creating a PR! This is indeed something I felt might come up at some point. Taking a look here, I think this might be better solved with setting the name as an extmark. Contrary to the comment here, :h nvim_buf_set_extmark() does allow for setting the virtual text position to be inline. So the name could just be an inlined extmark before the path instead of an actual part of the display text.

This should be fixed in 7b53a86ba4e0cdb6a58ff38d9d0d2e9f802e1ff9. The name is now added as an extmark instead of a string when name_pos = "start" 🙂


manage.py script

@KudoS1410, great work! Kudos!
I would recommend you use better names for the dictionaries instead of dict1 etc.
Use function arguments instead of global variables, or try constructing a class to share variables all around.
Comments are not required on simple code lines. Like os.getcwd() is a direct function to get the current working directory, no need to explain that.


The debugger should not be disabled when you remove the last breakpoint

The Remove-PSBreakpoint command has logic that disables the debugger when the last breakpoint is removed. This logic does not make sense, and it gets in the way of automated debugger command testing. It has already been removed as part of the first set of automated tests that will be submitted via a PR soon. I'm simply creating this issue for tracking purposes.
Steps to reproduce
& {
    $bp = Set-PSBreakpoint -Command Remove-PSBreakpoint
    Remove-PSBreakpoint -Breakpoint $bp
}
1 + 1

Expected behavior
Regardless of whether you use stepInto, stepOver, or stepOut, you should be able to step to the 1 + 1 command.
Actual behavior
You cannot step to the 1 + 1 command.
Environment data
Name                           Value
----                           -----
PSVersion                      6.2.0
PSEdition                      Core
GitCommitId                    6.2.0
OS                             Microsoft Windows 10.0.17763
Platform                       Win32NT
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion      2.3
SerializationVersion           <IP_ADDRESS>
WSManStackVersion              3.0

When debugging is enabled, there is a significant impact to performance. It seems like a bad idea to degrade performance for the rest of the session if the debugger isn't actively needed.

@lzybkr I understand that and figured that was the reasoning behind this code; however, without this fixed, if I'm in a debug session, on the last breakpoint, and I remove that breakpoint and then step, the code runs to the end because the debugger is disabled. How can the debugger no longer be needed when I'm in the debugger stepping through code?
If we want this logic needs to be kept, then the condition needs to change so that the debugger is not disabled the last breakpoint is removed and if you are currently in the debugger. I'm not sure what flag/setting tells me that, but there must be one. I'll have a look to see.

Thanks for the comment @lzybkr. I put the disabling logic back, with added conditional checks to ensure that you are not currently stepping in the debugger. If you are, the debugger is not disabled.

That's better, but still not optimal. The debugger should also be disabled when you go (no more breakpoints could be hit) and when you've exited all scripts (empty callstack).

I don't disagree, but those two additional scenarios don't have anything to do with Remove-PSBreakpoint though, do they?


Tile Covered by Neighbour Tile by One Line

Hi, I have a site running on OSD viewer. When I zoom in, sometimes a tile is overlapped by one line by its neighbour tile. Here is an example:

The top strike of the first "8" is covered by the above tile.
I looked into this problem and displayed the position and size of the tiles. Obviously, the bottom of the above tile is over the below title by one line.
Tile1: y:-102.73317873859304 h:302.7454153239068 bottom:<PHONE_NUMBER>8531376
Tile2: y:199.01223658531373
I found if I comment out the line 22426 below, the problem will disappear.
22425     if ( !overlap ) {
22426         //sizeC = sizeC.plus( new $.Point( 1, 1 ) );
22427     }
Please contact me if you need more information.

This is actually kind of a thorny issue. You can see discussion of it here https://github.com/openseadragon/openseadragon/issues/1722 and here https://github.com/openseadragon/openseadragon/pull/2055. Let me know if you're interested in getting involved.
Do you have control over your tile creation? If so, the easiest fix for you is to add a tile overlap of 1, which bypasses the issue.

I think it would be reasonable to give a parameter to opt-out from this behaviour. I too had to patch this forced overlap, as the graphics we are using osd really suffered with annoying shifts appearing:

As we only have to support chromium based browsers it would be nice to have a solution without 'npx patch-package' approach.

Indeed... I suppose we could add https://github.com/openseadragon/openseadragon/pull/2055 with an option to turn it on. @themcoo Would you be interested in making a PR for that?


[🐞] Build fails with Prisma and Deno

Which component is affected?
Qwik Rollup / Vite plugin
Describe the bug
Added Prisma and Deno adapter to Starter App and tried to build with npm run build
Build Failed.
Output:
".prisma/client/index-browser" is imported by ".prisma/client/index-browser?commonjs-external", but could not be resolved – treating it as an external dependency.
error during build:
TypeError [PLUGIN_ERROR]: Invalid module ".prisma/client/index-browser" is not a valid package name imported from<EMAIL_ADDRESS>    at new NodeError (node:internal/errors:405:5)
    at parsePackageName (node:internal/modules/esm/resolve:709:11)
    at packageResolve (node:internal/modules/esm/resolve:731:5)
    at moduleResolve (node:internal/modules/esm/resolve:830:20)
    at defaultResolve (node:internal/modules/esm/resolve:1035:11)
    at DefaultModuleLoader.resolve (node:internal/modules/esm/loader:269:12)
    at DefaultModuleLoader.getModuleJob (node:internal/modules/esm/loader:153:32)
    at ModuleWrap.<anonymous> (node:internal/modules/esm/module_job:76:33)
    at link (node:internal/modules/esm/module_job:75:36)

Reproduction
https://stackblitz.com/edit/qwik-starter-2irmfx
Steps to reproduce
npm create qwik@latest
cd qwik-app
npm install
npm run qwik add prisma
npm run qwik add deno
npm run build
System Info
System:
    OS: Linux 6.3 Arch Linux
    CPU: (4) x64 Intel(R) Core(TM) i3-4005U CPU @ 1.70GHz
    Memory: 698.45 MB / 3.73 GB
    Container: Yes
    Shell: 5.1.16 - /bin/bash
  Binaries:
    Node: 20.3.0 - /usr/bin/node
    npm: 9.6.6 - /usr/bin/npm
    pnpm: 8.6.3 - /usr/bin/pnpm
  Browsers:
    Brave Browser: <IP_ADDRESS>
    Chromium: 114.0.5735.133

Additional Information
No response

It is enough to add deno to get a failing build (no need to add prisma).

However the error is different:
Error during SSG
getPlatform is not iterable (cannot read property Symbol(Symbol.iterator))
  Pathname: /
  Plugin: qwik-ssg
  File: /home/projects/qwik-starter-2irmfx/server/assets/@qwik-city-plan-00ac1429.js:9038:34
  9037|  const RouterOutlet = /* @__PURE__ */ componentQrl(/*#__PURE__*/ inlinedQrl(s_e0ssiDXoeAM, "s_e0ssiDXoeAM"));
  9038|  const QACTION_KEY = "qaction";
  9039|  const resolveHead = (endpoint, routeLocation, contentModules, locale)=>{
     |     ^
  9040|      const head = createDocumentHead();
  9041|      const getData = (loaderOrAction)=>{
      at shim (file:///home/projects/qwik-starter-2irmfx/server/assets/@qwik-city-plan-00ac1429.js:9038:34)
      at AsyncFunction.s_e0ssiDXoeAM (file:///home/projects/qwik-starter-2irmfx/server/assets/@qwik-city-plan-00ac1429.js:9053:24)
      at AsyncFunction.invoke (file:///home/projects/qwik-starter-2irmfx/server/assets/@qwik-city-plan-00ac1429.js:744:46)
      at eval (file:///home/projects/qwik-starter-2irmfx/server/assets/@qwik-city-plan-00ac1429.js:4644:28)
      at then (file:///home/projects/qwik-starter-2irmfx/server/assets/@qwik-city-plan-00ac1429.js:186:79)
      at eval (file:///home/projects/qwik-starter-2irmfx/server/assets/@qwik-city-plan-00ac1429.js:4634:20)
      at eval (file:///home/projects/qwik-starter-2irmfx/server/assets/@qwik-city-plan-00ac1429.js:1332:28)
      at safeCall (file:///home/projects/qwik-starter-2irmfx/server/assets/@qwik-city-plan-00ac1429.js:179:25)
      at executeComponent (file:///home/projects/qwik-starter-2irmfx/server/assets/@qwik-city-plan-00ac1429.js:1332:12)
      at renderSSRComponent (file:///home/projects/qwik-starter-2irmfx/server/assets/@qwik-city-plan-00ac1429.js:1591:6)

However the error is different:
Error during SSG
getPlatform is not iterable (cannot read property Symbol(Symbol.iterator))
  Pathname: /
  Plugin: qwik-ssg
  File: /home/projects/qwik-starter-2irmfx/server/assets/@qwik-city-plan-00ac1429.js:9038:34
  9037|  const RouterOutlet = /* @__PURE__ */ componentQrl(/*#__PURE__*/ inlinedQrl(s_e0ssiDXoeAM, "s_e0ssiDXoeAM"));
  9038|  const QACTION_KEY = "qaction";
  9039|  const resolveHead = (endpoint, routeLocation, contentModules, locale)=>{
     |     ^
  9040|      const head = createDocumentHead();
  9041|      const getData = (loaderOrAction)=>{
      at shim (file:///home/projects/qwik-starter-2irmfx/server/assets/@qwik-city-plan-00ac1429.js:9038:34)
      at AsyncFunction.s_e0ssiDXoeAM (file:///home/projects/qwik-starter-2irmfx/server/assets/@qwik-city-plan-00ac1429.js:9053:24)
      at AsyncFunction.invoke (file:///home/projects/qwik-starter-2irmfx/server/assets/@qwik-city-plan-00ac1429.js:744:46)
      at eval (file:///home/projects/qwik-starter-2irmfx/server/assets/@qwik-city-plan-00ac1429.js:4644:28)
      at then (file:///home/projects/qwik-starter-2irmfx/server/assets/@qwik-city-plan-00ac1429.js:186:79)
      at eval (file:///home/projects/qwik-starter-2irmfx/server/assets/@qwik-city-plan-00ac1429.js:4634:20)
      at eval (file:///home/projects/qwik-starter-2irmfx/server/assets/@qwik-city-plan-00ac1429.js:1332:28)
      at safeCall (file:///home/projects/qwik-starter-2irmfx/server/assets/@qwik-city-plan-00ac1429.js:179:25)
      at executeComponent (file:///home/projects/qwik-starter-2irmfx/server/assets/@qwik-city-plan-00ac1429.js:1332:12)
      at renderSSRComponent (file:///home/projects/qwik-starter-2irmfx/server/assets/@qwik-city-plan-00ac1429.js:1591:6)

This can be new issue in itself.

It is enough to add deno to get a failing build (no need to add prisma).

In my case the problem was with deno and prisma combined, build was failing when i add prisma.

This is happening with prisma and node as well

Adding an alias in vite.config.ts resolved this
    resolve: {
      alias: {
        ".prisma/client/index-browser": "./node_modules/.prisma/client/index-browser.js"
      }
    },

Disclaimer: I did not try this with Deno, yet, but I hope it will help.
Could you try that and let us know if that works for?
I found out that the "Invalid module" error could be solved with 2 aliases, see my repro here: https://github.com/Jolg42/prisma-repro-21094
This is what worked for me:
https://github.com/Jolg42/prisma-repro-21094/blob/main/adapters/vercel-edge/vite.config.ts
import { vercelEdgeAdapter } from<EMAIL_ADDRESS>import { extendConfig } from<EMAIL_ADDRESS>import baseConfig from "../../vite.config";

export default extendConfig(baseConfig, () => {
  return {
    build: {
      ssr: true,
      rollupOptions: {
        input: ["src/entry.vercel-edge.tsx", "@qwik-city-plan"],
      },
      outDir: ".vercel/output/functions/_qwik-city.func",
    },
    plugins: [vercelEdgeAdapter()],
    resolve: {
      alias: {
        ".prisma/client/default": "./node_modules/.prisma/client/default.js",
        "./query_engine_bg.wasm?module": "./node_modules/.prisma/client/query_engine_bg.wasm?init",
      },
    },
  };
});

I found out about this in Vite's docs here https://vitejs.dev/guide/features#webassembly

Pre-compiled .wasm files can be imported with ?init.

Originally posted by @Jolg42 in https://github.com/prisma/prisma/issues/21094#issuecomment-2142474474

@krishna-santosh Did you solve the problem?

Tried both solutions proposed by @sarat1669 and @Jolg42, but unfortunately they both didn't work.
vite v5.3.1 building SSR bundle for production...
".prisma/client/index-browser" is imported by ".prisma/client/index-browser?commonjs-external", but could not be resolved – treating it as an external dependency.
✓ 44 modules transformed.
server/build/q-C4YPi7sT.css    4.85 kB
server/entry.ssr.js            0.07 kB
<EMAIL_ADDRESS>   41.01 kB
server/entry.deno.js          51.10 kB
server/q-BulQp7W4.js          60.24 kB
server/q-BN1iqjfz.js         348.71 kB
✓ built in 5.39s
error during build:
TypeError [PLUGIN_ERROR]: Invalid module ".prisma/client/index-browser" is not a valid package name imported from<EMAIL_ADDRESS>    at parsePackageName (node:internal/modules/esm/resolve:768:11)
    at packageResolve (node:internal/modules/esm/resolve:792:5)
    at moduleResolve (node:internal/modules/esm/resolve:914:18)
    at defaultResolve (node:internal/modules/esm/resolve:1119:11)
    at ModuleLoader.defaultResolve (node:internal/modules/esm/loader:541:12)
    at ModuleLoader.resolve (node:internal/modules/esm/loader:510:25)
    at ModuleLoader.getModuleJob (node:internal/modules/esm/loader:240:38)
    at ModuleJob._link (node:internal/modules/esm/module_job:126:49)

undefined

Thanks @krishna-santosh
In the Prisma docs I found
previewFeatures = ["deno"]

Are you using this configuration?

I added it to schema.prisma and tried building the project again, but the result is still the same.

Related issue: https://github.com/prisma/prisma/issues/21094

have you tried running it using deno's --unstable-sloppy-imports ?

this would be fixed by using deno run's --unstable-sloppy-imports for the .js in the import path, but I am not sure if that can be added to vercel configs.


1.x Test and fix dynamic properties warnings

Related:

#2860

This pull request makes sure we run tests on 8.2 to test the fixes applied in #2890. See https://github.com/timber/timber/actions/runs/7652688123/job/20852977870 to confirm that there are no Deprecation Warnings in Timber for 8.2 anymore.
@nlemoine I would appreciate a quick review on #2860 and this pull request to confirm we can release the fix in 1.24.0.

Some failed tests but I think nothing related to the PR. I think we can merge this @gchtr ?

Were these pesky footer deprecations again. Merging :)


Fix oozie.sh - Debian 10 backports repo issue.

/gcbrun

/gcbrun

Tests are passing on 2.X and failing on 2.2 which are unrelated to this change.

/gcbrun

/gcbrun

/gcbrun

/gcbrun

2.1-debian11 fails with
Error from server (NotFound): pods "presubmit-2-1-debian11-32dbb602-ca42-47a1-aff2-cd66385a2c81" not found
This looks like an infrastructure failure in k8s...


README mentions "the shepherd" without introducing the concept

The README has this text:

While the RFC pull request is up, the shepherd may schedule meetings with the author and/or relevant stakeholders to discuss the issues in greater detail, and in some cases the topic may be discussed at a sub-team meeting. In either case a summary from the meeting will be posted back to the RFC pull request.

Ctrl-F finds no other instances of the word "shepherd" on the page. I'd update it myself but I'm not sure how much material is missing and should be added (just a word or half sentence somewhere, an entire section, etc.).

?

Closing as the shepherd is no longer mentioned.