Fix broken links

What changes to the docs does this PR provide?

Just fixes some broken links (Found while investigating #340)
PR Checklist
Please check if your PR fulfills the following requirements:

[x] Correctly picked the right branch to base the change off (master for new features, live for typos/improvements)
[ ] For new pages, used the provided template
[ ] For new features, added an entry in the Table of Contents
[x] Ran against a spell and grammar checker
[x] Contains NO breaking changes

Other information

Docs Build status updates of commit e2bac80:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

:x:Error

Details

Line 136: [Error] Restore nuget package W:\2ff2-s\.optemp\dependentPackages\Microsoft.DocAsCode.ECMA2Yaml\packages.config in folder:W:\2ff2-s\.optemp\packages failed, possibly due to transient errors from nuget servers. Please retry building your content. If the issue still happens, open a ticket in https://SiteHelp and include the build report and the following error message for our team to troubleshoot: Errors in packages.config projects     Unable to find version '1.0.728' of package 'Microsoft.DocAsCode.ECMA2Yaml'.       C:\Users\ContainerAdministrator\.nuget\packages\: Package 'Microsoft.DocAsCode.ECMA2Yaml.1.0.728' is not found on source 'C:\Users\ContainerAdministrator\.nuget\packages\'.       https://docfx.pkgs.visualstudio.com/docfx/_packaging/docs-build-v2-prod/nuget/v2: Package 'Microsoft.DocAsCode.ECMA2Yaml.1.0.728' is not found on source 'https://docfx.pkgs.visualstudio.com/docfx/_packaging/docs-build-v2-prod/nuget/v2'.
Line 136: [Error] Restore nuget package W:\2ff2-s\.optemp\dependentPackages\Microsoft.OpenPublishing.CommonPlugins\packages.config in folder:W:\2ff2-s\.optemp\packages failed, possibly due to transient errors from nuget servers. Please retry building your content. If the issue still happens, open a ticket in https://SiteHelp and include the build report and the following error message for our team to troubleshoot: Errors in packages.config projects     Unable to find version '1.0.224' of package 'Microsoft.OpenPublishing.CommonPlugins'.       C:\Users\ContainerAdministrator\.nuget\packages\: Package 'Microsoft.OpenPublishing.CommonPlugins.1.0.224' is not found on source 'C:\Users\ContainerAdministrator\.nuget\packages\'.       https://docfx.pkgs.visualstudio.com/docfx/_packaging/docs-build-v2-prod/nuget/v2: Package 'Microsoft.OpenPublishing.CommonPlugins.1.0.224' is not found on source 'https://docfx.pkgs.visualstudio.com/docfx/_packaging/docs-build-v2-prod/nuget/v2'.

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

@mrlacey can you please try updating the master branch into your own branch?

Docs Build status updates of commit db353ca:
:warning: Validation status: warnings

File
Status
Preview URL
Details

docs/platform-specific/PlatformSpecificDifferencesGenerator.md
:warning:Warning
View
Details

docs/helpers/Colors.md
:white_check_mark:Succeeded
View

docs/helpers/StorageFiles.md
:white_check_mark:Succeeded
View

docs/helpers/Streams.md
:white_check_mark:Succeeded
View

docs/helpers/ThemeListener.md
:white_check_mark:Succeeded
View

docs/helpers/WeakEventListener.md
:white_check_mark:Succeeded
View

docs/services/Linkedin.md
:white_check_mark:Succeeded
View

docs/services/MicrosoftTranslator.md
:white_check_mark:Succeeded
View

docs/platform-specific/PlatformSpecificDifferencesGenerator.md

Line 49: [Warning-InvalidFileLink] Invalid file link:(~/platform-specific/platformspecificanalyzer).

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
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.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit f324cc8:
:warning: Validation status: warnings

File
Status
Preview URL
Details

docs/platform-specific/PlatformSpecificDifferencesGenerator.md
:warning:Warning
View
Details

docs/helpers/Colors.md
:white_check_mark:Succeeded
View

docs/helpers/StorageFiles.md
:white_check_mark:Succeeded
View

docs/helpers/Streams.md
:white_check_mark:Succeeded
View

docs/helpers/ThemeListener.md
:white_check_mark:Succeeded
View

docs/helpers/WeakEventListener.md
:white_check_mark:Succeeded
View

docs/services/Linkedin.md
:white_check_mark:Succeeded
View

docs/services/MicrosoftTranslator.md
:white_check_mark:Succeeded
View

docs/platform-specific/PlatformSpecificDifferencesGenerator.md

Line 49: [Warning-InvalidFileLink] Invalid file link:(~/platform-specific/platformspecificanalyzer).

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
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.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Triggering another doc check pass to make sure validation went away.

Docs Build status updates of commit f324cc8:
:warning: Validation status: warnings

File
Status
Preview URL
Details

docs/platform-specific/PlatformSpecificDifferencesGenerator.md
:warning:Warning
View
Details

docs/helpers/Colors.md
:white_check_mark:Succeeded
View

docs/helpers/StorageFiles.md
:white_check_mark:Succeeded
View

docs/helpers/Streams.md
:white_check_mark:Succeeded
View

docs/helpers/ThemeListener.md
:white_check_mark:Succeeded
View

docs/helpers/WeakEventListener.md
:white_check_mark:Succeeded
View

docs/services/Linkedin.md
:white_check_mark:Succeeded
View

docs/services/MicrosoftTranslator.md
:white_check_mark:Succeeded
View

docs/platform-specific/PlatformSpecificDifferencesGenerator.md

Line 49: [Warning-InvalidFileLink] Invalid file link:(~/platform-specific/platformspecificanalyzer).

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
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.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit 14870af:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/helpers/Colors.md
:white_check_mark:Succeeded
View

docs/helpers/StorageFiles.md
:white_check_mark:Succeeded
View

docs/helpers/Streams.md
:white_check_mark:Succeeded
View

docs/helpers/ThemeListener.md
:white_check_mark:Succeeded
View

docs/helpers/WeakEventListener.md
:white_check_mark:Succeeded
View

docs/platform-specific/PlatformSpecificDifferencesGenerator.md
:white_check_mark:Succeeded
View

docs/services/Linkedin.md
:white_check_mark:Succeeded
View

docs/services/MicrosoftTranslator.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 in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel


SqlPool schema jsons

MSFT employees can try out our new experience at OpenAPI Hub  - one location for using our validation tools and finding your workflow.

Contribution checklist:

[ ] I commit to follow the Breaking Change Policy of “no breaking changes
[ ] I have reviewed the documentation for the workflow.
[ ] Validation tools were run on swagger spec(s) and errors have all been fixed in this PR. How to fix?

If any further question about AME onboarding or validation tools, please view the FAQ.
ARM API Review Checklist

[ ] Ensure to check this box if one of the following scenarios meet updates in the PR, so that label “WaitForARMFeedback” will be added automatically to involve ARM API Review. Failure to comply may result in delays for manifest application. Note this does not apply to data plane APIs, all “removals” and “adding a new property” no more require ARM API review.

Adding new API(s)
Adding a new API version
Adding a new service

[ ] If you are blocked on ARM review and want to get the PR merged with urgency, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.

Breaking Change Review Checklist
If there are following updates in the PR, ensure to request an approval from API Review Board as defined in the Breaking Change Policy.

[ ] Removing API(s) in stable version
[ ] Removing properties in stable version
[ ] Removing API version(s) in stable version
[ ] Updating API in stable version with Breaking Change Validation errors
[ ] Updating API(s) in preview over 1 year

Please follow the link to find more details on PR review process.

/azp run automation - sdk

Hi @tunafish88 please let me know when this is ready for review

Hi @tunafish88 it seems that this draft PR is not receiving any changes for like a month, I will first close this. Please feel free to reopen when you come back on this PR.


[BEAM-2244] Cherry-pick #3053 to release-2.0.0

[BEAM-2244] Move details of Metrics to Runners Core
Largeish changes this required were:

splitting the MetricsContainer into an interface in Java Core with
an implementation in Runners Core
modifying the various *Cell classes to have a name
cleaning up dependency cross-fire.

R: @bjchambers confirm this is a valid CP. Also, note there was one merge conflict fixup in SourceRdd -- check that one out.

Looks valid to me.

Changes Unknown when pulling e2f331e517804cc3ed0262fe8cc0772a4629d310 on dhalperi:cp-3053 into ** on apache:release-2.0.0**.


✨ Start drafting v3 API

Summary
This PR proposes a v3 of the edge.kubestellar.io Kubernetes API group.
This is just a statement of what a nicer API might look like. I do not yet have a position on coexistence with v2 vs. jump from v2 to v3.
Related issue(s)
Fixes #

We went with a smaller change, in #1202


Fix the bugs in snake game

Stop the snake just when it hits the wall (it can not penetrate the wall).
Fix the canvas size to exactly fit with the grid (make the canvas smaller to accommodate other UI elements).
Draw the boundary.

optional
3. Add levels
4. Change the food(make it a frog).
5. Make the snake look like a snake.

except 3 all are fixed
levels will be added later.


failing to respond to cache pressure client_id xx

go-ceph version: v0.8.0
there is a ceph-service pod running in k8s, which use go-ceph to operate cephfs, like(create/delete dir, create/delete dir), but mds report
mds.sh-bs-b1-303-j14-ceph-133-2(mds.0): Client xdl-ceph-client-d6795749-z988c:xdl failing to respond to cache pressure client_id: 6704

I retart  ceph-service , mds is ok,  is it a bug in go-ceph?

The pleasant coincidence of a ceph mailing list post indicating that nfs-ganesha once encountered similar problems and a bit more searching shows that there is now api hooks intended for managing client cache pressure:

https://tracker.ceph.com/issues/12334
https://github.com/ceph/ceph/pull/34596

I also see that there is a newer version: ceph_ll_register_callbacks2
What I'm not clear about is how the low-level api and the high level apis are meant to interact with regards to the cache and these callbacks.
@jtlayton if I may bother you for a moment, since you added the original set of callbacks: is it correct to say that using (only) the high level API doesn't automatically handle the cache pressure requests? Assuming we were to add support for the callbacks how would existing code that uses the high-level api make use of the callbacks?  What, if any, additional low-level API functions would be needed to make it useful to someone who has a use-case like @qiankunli's?
Thanks for your time!

Yeah -- we probably need to add some documentation comments to struct ceph_client_callback_args. If you wouldn't mind opening a bug at tracker.ceph.com, we can add some comments in the near future.

Thanks for the suggestion. Done at https://tracker.ceph.com/issues/53004

For now though, you unfortunately have to look at the userland client code and suss out how each gets called.

OK, thanks for the heads up.  I've already looked over the test C file and that helped somewhat. I'll take a look at some other examples too.

For this problem, you're probably mostly interested in .dentry_cb and .ino_release_cb. These get called when the MDS wants to trim the client's record of a Dentry or an Inode (usually to reduce its own memory consumption).
Ganesha keeps an cache of Inode references, and it registers an .ino_release_cb that tries to release the corresponding NFS filehandle when a request to trim that Inode comes in. It's not guaranteed to work if the FH is in use, but these usually come in sets and eventually some get released.

OK, thanks!

->dentry_cb works in a similar fashion for Dentry objects. Ganesha's FSAL_CEPH doesn't use that one, but ceph-fuse does. The rest are somewhat specific to the ceph-fuse use-case.

Sure. I can look into how both systems use the callback APIs down the road, to help serve as examples.

Probably, you want to expose most or all of these via go-ceph. It's been a while since I did any Go work though, so I won't presume how you should go about it.

Yeah, we currently have only bindings for a (good, but incomplete) set of the high-level api functions. I have suspected for a while we'd eventually want to cover more of the low level APIs too.  On the plus side we've done some callback support for the rbd packge so we have some experience with callbacks between the C and Go layers.

So, to be clear:

@jtlayton if I may bother you for a moment, since you added the original set of callbacks: is it correct to say that using (only) the high level API doesn't automatically handle the cache pressure requests?

Correct. This is really an application-level problem with the ll_* API. The application is generally holding references to Dentry and Inode objects, and usually needs to do something application-specific to release them in response to a request from the MDS to trim them.

Thanks, that's probably the cause of @qiankunli issues then. One thing I'm still not clear on (but perhaps I just need to review the code closer)  how do the high-level and low-level APIs interact. Is there something like a (private) cache the high level calls use that we need to be aware of?


Ready for production use?

What's the project status? It's ready for production?

Yeap! Ready to go! All of our servers are completely migrated and only running the new Golang version.


dispose

Can u check dispose again

WillPopScope(
    child: NeedAddStepWidget(xxx),
    onWillPop: () async {
        intro.dispose();
        return true;
    }
)

Is there any problem with writing like this

Correct. I have tested and worked like that. So I think its worth renaming dispose with popScope or something else. Its a bit confusing like this. Again thanks for this great package.


Liked Projects Tab

Currently "Liked" projects are not displaying in the Liked tab.  Is it possible to implement that now, or do we have to wait until we get OP's information.  If we can do it now, let's do.

The shuffle button in the Liked tab doesn't seem to have any effect (Although it's tough to test with just two).  Let's implement a list shuffling like in the projects page.

i'll work on this

Fixed in #119


How to integrate Elasticsearch with NextJS 6?

If you have any link to an example integration that would be great!

You should use getInitialProps call an API (in your case elasticsearch), but just doing a HTTP request to it.


KCARE-1152 Secure Boot detection

Also updated copyright due to KCARE-1200

Signed-off-by: Rinat Sabitov<EMAIL_ADDRESS>

@aborilov Could you please make a review?


Update README.md

Codecov Report

Merging #87 (a1e46f5) into master (5c882fe) will not change coverage.
The diff coverage is n/a.

 Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


feat: add support for brotli

and feat: make Accept, Accept-Encoding, Content-Type, Content-Encoding checking optional

@packruler When I came up with this PR, I thought I might need to create unit tests, but since I haven't had a lot of time to spare, I just created the PR as a draft, and I'd be happy if you would be willing to refine it ;)


Ensure CI is set up correctly

Also, see if we can get shipshape running on shipshape in the CI

Is the idea here to get Travis fixed, or to move off Travis and onto Jenkins?

Whatever leaves us with a working CI. We don't currently have travis running shipshape on shipshape, but this might fix that problem.
http://blog.travis-ci.com/2015-08-19-using-docker-on-travis-ci/

We don't currently have Travis running at all. :-(


SPIKE explore ideas around Terragrunt support

Community users have been asking for Terragrunt support for quite some time. We might need to explore some ideas around supporting Terragrunt alongside vanilla Terraform in the controller.
User Story
As a Terraform Controller user,
I'd like to have Terragrunt support integrated into the controller,
so that I can manage my Terragrunt-based infrastructure alongside my existing Terraform infrastructure.
Acceptance Criteria

[ ] Support Terragrunt configuration files in addition to vanilla Terraform files within the controller
[ ] Properly manage Terragrunt dependencies and modules
[ ] Support popular Terragrunt features such as remote state management
[ ] Provide clear documentation on using Terragrunt with the Terraform Controller
[ ] Ensure existing Terraform functionality is not impacted by the addition of Terragrunt support

Rationale

The issue is related to exploring ideas for a potential feature, which fits into the RFC area.
The issue is about extending support to another popular tool (Terragrunt) in the Terraform ecosystem.
Supporting Terragrunt will require proper performance handling of dependencies and modules.
This issue is a proposal for a new feature.
Considering that Terragrunt support has been requested by the community for some time, it holds moderate priority.
Adding Terragrunt support affects both the usability and appeal of the controller. However, it does not currently impact the existing controller functionality.

Roadmap change
To track progress toward Terragrunt support, we can add it to a future quarter, ideally after current priorities have been addressed. For example:
Q2 2024

Explore and integrate Terragrunt support in the Terraform Controller

Closing in light of recent developments.

@LappleApple hello, what do you mean by "recent developments" please?


[spec2x] dracut: add 99emergency-timeout

See commit message. Adapted from #85, with the following diff:
--- a/dracut/99emergency-timeout/timeout.sh
+++ b/dracut/99emergency-timeout/timeout.sh
@@ -29,7 +29,7 @@ _prompt_for_timeout() {
     if [[ -e /.emergency-shell-confirmed ]]; then
         return
     fi
-    ignition_units="ignition-disks.service ignition-files.service ignition-mount.service"
+    ignition_units="ignition-disks.service ignition-files.service"
     if systemctl show $ignition_units | grep -q "^ActiveState=failed$"; then
         # Ignition has failed, suppress kernel logs so that Ignition logs stay
         # on the screen
@@ -43,7 +43,7 @@ _prompt_for_timeout() {
         cat <<EOF
 -------------------------------------------------------------------------------
 Ignition has failed. Please ensure your config is valid. Note that only Ignition spec
-v3.0.0+ configs are accepted.
+v2.x.x configs are accepted.
 A CLI validation tool to check this called ignition-validate can be downloaded from GitHub:
     https://github.com/coreos/ignition/releases
 Here are the Ignition logs:

Not tested in RHCOS yet - will do this shortly.

Now tested in RHCOS (4.2) - gives the following error message as expected in a config that tries to make /etc/issue a directory without specifying "overwrite": true (with the full logs and printed config omitted):
Ignition has failed. Please ensure your config is valid. Note that only Ignition spec
v2.x.x configs are accepted.
A CLI validation tool to check this called ignition-validate can be downloaded from GitHub:
    https://github.com/coreos/ignition/releases
Here are the Ignition logs:

...

}CRITICAL : Ignition failed: failed to create files: failed to create files: failed to create directory "/etc/issue": mkdir /sysroot/etc/issue: not a directory
Press Enter for emergency shell or wait 4 minutes 30 seconds for reboot.


Bug report with minions

When attempting to give other's minions, the "other" gains mouse control of ALL minions.
Others can control someone else's minions With E, R, T.

@Agarian I am aware of the first one, it has been noted in #7 and in projects. And I'll look into the second one, thanks for letting me know =D

Ok thanks lol

I'm also on Discord

Legend said agarian was never gone

Legend says the original Ogar-Unlimited may soon be reborn...

That legend is correct :D
I tested it already :)

Wow and it isn't even finished xD

XD


Version Issue for BetterTransformer. Please provide exact package dependencies and Python, Torch version you used

It is giving me:
ValueError: Transformers now supports natively BetterTransformer optimizations (torch.nn.functional.scaled_dot_product_attention) for the model type llama. Please upgrade to transformers>=4.36 and torch>=2.1.1 to use it. Details: https://huggingface.co/docs/transformers/perf_infer_gpu_one#flashattention-and-memory-efficient-attention-through-pytorchs-scaleddotproductattention
Traceback (most recent call last):

I installed from requirements.txt.
I am using python 3.10.13 , torch==2.2.0  and transformers==4.37.2 on 4xA10 on Sagemaker.

+1 for this. Exact versions would be helpful.


Can flutter_tools terse-ify stack traces on failures?

The stack_trace package has an option to remove/fold repetitive Dart SDK frames, which on the stack trace like listed on #13190, would make much more understandable. This looks like a big scary system crash when in reality it was just an NPE in the tooling, for example.
Steps to Reproduce
See https://github.com/flutter/flutter/issues/13190.

See also #4021.
I'd rather we avoided stack_trace. It generates stack traces that are less readable overall than the VM's default stack traces (because of doing weird things to the paths, etc). This messes with tooling that tries to process the stacks, for example.

It's not required to use stack_trace to rewrite - it has some decent folding infrastructure that is completely separate from how the traces are parsed and displayed for example.

What about creating issues to get bad behavior fixed?

Closing in favour of #4021 which will cover this.


Number of "Threads" makes "messages from" inaccessible from search

If you try to search for messages from a certain contact in the search bar, you briefly see a list of potential matches but this is almost immediately occluded by the list of matching email threads. It's then impossible to scroll down to find the contacts list.
What operating system are you using?
Mac OSX 10.11.6
What version of Nylas Mail are you using?
2.0.28
--
Bug?
no
Is the issue related to a specific email provider (Gmail, Exchange, etc.)?
no
Is the issue reproducible with a particular attachment, message, signature, etc?

...
--
Feature Request?
Does this feature exist in another mail client or tool you use?
...

It also occurs at openSUSE Leap 42.2 and Nylas Mail version 2.0.31.


Fix workflow service to handle coordinator and database errors

Add a separate retry decorator to handle coordinator and database connection errors different than the retry decorator for database write conflicts. Include the retry decorator at appropriate locations. The exception is raised again when retries are exhausted and the workflow engine process method catches the exception and fails the workflow execution. Add unit tests to test recovery from connection errors and when retries are exhausted. If the environmental errors persist and the workflow engine is unable to record the failed status for the workflow, add a garbage collection routine to cleanup these cases. Fixes #4704 and #4705.

Identified in internal st2cicd e2e tests infra.
With this newly introduced feature and default like:
# Max seconds to allow workflow execution be idled before it is identified as orphaned and cancelled by the garbage collector.
gc_max_idle_sec = 900

we're now marking long running orchestra workflows as canceled and stopping their execution.
This is pretty much a serious regression in just released v3.1 that will break existing workflow runs :disappointed_relieved: We'll likely need a patch release for this next week asap.

Addressed via https://github.com/StackStorm/st2/pull/4733


A way to customize the default "src"

So firstly, as a sidenote, I think the default cwd (where ultra looks for the app.jsx/app.tsx file) shouldn't even be "src" because the whole philosophy around ultra is that there is no "source", no "build", no transpiling stuf. It should just be called "website" or "root" or "public" in my opinion, or even better, it should just be the current directory the server file is in.
Secondly, and more important, I suggest that this should be customizable. I know, ultra seems to be one of those "zero-config" projects, and I really love that it is, but I believe that the cwd is such a fundamental part that there should just be a simple "cwd" or "root" setting when calling ultra, like so:
import ultra from<EMAIL_ADDRESS>
await ultra({
	importmap: await Deno.readTextFile("importmap.json"),
	cwd: "./"
});

If you (as in you, the maintainers of ultra) agree, I'll gladly add a pull request for this. I assume it wouldn't be that difficult to introduce this setting, but let's see.

After opening this issue I discovered https://github.com/exhibitionist-digital/ultra/pull/7, and I find the reasoning in there strange, because what is more common is not necessarily better. Even "source" instead of "src" would be better in my opinion, but whatever. As I said, this shouldn't really be the point of the issue, as there should just be away to customize the app folder name.

@nnmrts Thanks, we did go back and forth between what a default directory should be, but I agree that making it customisable would be nice. I think due to needing a bit of config for either the oak server, or vercel/deno deployments, the project code would be easier managed living in a specific directory for the time being.


⚠ Bofrost.at has degraded performance

In 0f26a37, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 1173 ms

Resolved: Bofrost.at performance has improved in 0088857.


S3 User Uploads Bucket created by amplify does not accept large files

Describe the bug
Can't upload large files to the user uploads bucket that amplify generates without modifying CORS configuration. To fix, the CORSConfiguration of the S3 bucket needs to include     <ExposeHeader>ETag</ExposeHeader>. See https://github.com/aws/aws-sdk-js/issues/191
To Reproduce

amplify add storage
go through instructions to create user uploads s3 bucket
Use appsync to upload the files

Expected behavior

Any file uploaded successfully regardless of size (file I was uploading was 9mb)

Screenshots
With the default CORS configuration, GraphQL will fail with error of 'No access to ETag property on response. Check CORS configuration to expose ETag header.'
Desktop (please complete the following information):

OS: OSX
Browser Chrome

That issue was fixed with PR #579


[Bug]: regularly (often once a day) i get several warnings

Contact Details
No response
What happened?
most often during the night between 02:00 - 05:00 i get some warnings but there will be no script running and also no restart of the instance is configured.
no clue why this happens

chromecast.0
2023-01-03 04:57:43.177
warn
Wohnzimmer - Client error: Error: read ECONNRESET at TLSWrap.onStreamRead (node:internal/stream_base_commons:217:20)

chromecast.0
2023-01-03 04:57:42.167
warn
Wohnzimmer - Client error: Error: read ECONNRESET at TLSWrap.onStreamRead (node:internal/stream_base_commons:217:20)

chromecast.0
2023-01-03 04:57:42.162
warn
Wohnzimmer - Client error: Error: read ECONNRESET at TLSWrap.onStreamRead (node:internal/stream_base_commons:217:20)

chromecast.0
2023-01-03 04:57:35.615
warn
Wohnzimmer - Client error: Error: connect ECONNREFUSED <IP_ADDRESS>:8009 at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1278:16)

chromecast.0
2023-01-03 04:57:35.612
warn
Wohnzimmer - Client error: Error: connect ECONNREFUSED <IP_ADDRESS>:8009 at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1278:16)

chromecast.0
2023-01-03 04:57:33.609
warn
Wohnzimmer - Client error: Error: connect ECONNREFUSED <IP_ADDRESS>:8009 at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1278:16)

chromecast.0
2023-01-03 04:57:33.605
warn
Wohnzimmer - Client error: Error: connect ECONNREFUSED <IP_ADDRESS>:8009 at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1278:16)

chromecast.0
2023-01-03 04:57:32.601
warn
Wohnzimmer - Client error: Error: connect ECONNREFUSED <IP_ADDRESS>:8009 at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1278:16)

chromecast.0
2023-01-03 04:57:32.598
warn
Wohnzimmer - Client error: Error: connect ECONNREFUSED <IP_ADDRESS>:8009 at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1278:16)

chromecast.0
2023-01-03 04:57:31.514
warn
Wohnzimmer - Client error: Error: Device timeout at fn.ontimeout (/opt/iobroker/node_modules/castv2-client/lib/senders/platform.js:56:26) at Object.onceWrapper (node:events:627:28) at fn.emit (node:events:513:28) at fn.emit (node:domain:489:12) at Timeout.ontimeout [as _onTimeout] (/opt/iobroker/node_modules/castv2-client/lib/controllers/heartbeat.js:44:10) at listOnTimeout (node:internal/timers:559:17) at processTimers (node:internal/timers:502:7)

chromecast.0
2023-01-03 04:57:31.510
warn
Wohnzimmer - Client error: Error: Device timeout at fn.ontimeout (/opt/iobroker/node_modules/castv2-client/lib/senders/platform.js:56:26) at Object.onceWrapper (node:events:627:28) at fn.emit (node:events:513:28) at fn.emit (node:domain:489:12) at Timeout.ontimeout [as _onTimeout] (/opt/iobroker/node_modules/castv2-client/lib/controllers/heartbeat.js:44:10) at listOnTimeout (node:internal/timers:559:17) at processTimers (node:internal/timers:502:7)

chromecast.0
2023-01-03 04:17:46.880
warn
Gäste WC - Client error: Error: read ECONNRESET at TLSWrap.onStreamRead (node:internal/stream_base_commons:217:20)

chromecast.0
2023-01-03 04:17:45.866
warn
Gäste WC - Client error: Error: read ECONNRESET at TLSWrap.onStreamRead (node:internal/stream_base_commons:217:20)

chromecast.0
2023-01-03 04:17:33.705
warn
Gäste WC - Client error: Error: Device timeout at fn.ontimeout (/opt/iobroker/node_modules/castv2-client/lib/senders/platform.js:56:26) at Object.onceWrapper (node:events:627:28) at fn.emit (node:events:513:28) at fn.emit (node:domain:489:12) at Timeout.ontimeout [as _onTimeout] (/opt/iobroker/node_modules/castv2-client/lib/controllers/heartbeat.js:44:10) at listOnTimeout (node:internal/timers:559:17) at processTimers (node:internal/timers:502:7)

chromecast.0
2023-01-03 03:23:57.661
warn
Wintergarten - Client error: Error: read ECONNRESET at TLSWrap.onStreamRead (node:internal/stream_base_commons:217:20)

chromecast.0
2023-01-03 03:23:57.645
warn
Wintergarten - Client error: Error: read ECONNRESET at TLSWrap.onStreamRead (node:internal/stream_base_commons:217:20)

chromecast.0
2023-01-03 03:23:51.891
warn
Wintergarten - Client error: Error: connect ECONNREFUSED <IP_ADDRESS>:8009 at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1278:16)

chromecast.0
2023-01-03 03:23:50.574
warn
Wintergarten - Client error: Error: connect ECONNREFUSED <IP_ADDRESS>:8009 at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1278:16)

chromecast.0
2023-01-03 03:23:49.683
warn
Wintergarten - Client error: Error: connect ECONNREFUSED <IP_ADDRESS>:8009 at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1278:16)

chromecast.0
2023-01-03 03:23:48.678
warn
Wintergarten - Client error: Error: connect ECONNREFUSED <IP_ADDRESS>:8009 at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1278:16)

chromecast.0
2023-01-03 03:23:48.565
warn
Wintergarten - Client error: Error: connect ECONNREFUSED <IP_ADDRESS>:8009 at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1278:16)

chromecast.0
2023-01-03 03:23:47.559
warn
Wintergarten - Client error: Error: connect ECONNREFUSED <IP_ADDRESS>:8009 at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1278:16)

chromecast.0
2023-01-03 03:23:46.539
warn
Wintergarten - Client error: Error: Device timeout at fn.ontimeout (/opt/iobroker/node_modules/castv2-client/lib/senders/platform.js:56:26) at Object.onceWrapper (node:events:627:28) at fn.emit (node:events:513:28) at fn.emit (node:domain:489:12) at Timeout.ontimeout [as _onTimeout] (/opt/iobroker/node_modules/castv2-client/lib/controllers/heartbeat.js:44:10) at listOnTimeout (node:internal/timers:559:17) at processTimers (node:internal/timers:502:7)

chromecast.0
2023-01-03 03:23:45.552
warn
Wintergarten - Client error: Error: Device timeout at fn.ontimeout (/opt/iobroker/node_modules/castv2-client/lib/senders/platform.js:56:26) at Object.onceWrapper (node:events:627:28) at fn.emit (node:events:513:28) at fn.emit (node:domain:489:12) at Timeout.ontimeout [as _onTimeout] (/opt/iobroker/node_modules/castv2-client/lib/controllers/heartbeat.js:44:10) at listOnTimeout (node:internal/timers:559:17) at processTimers (node:internal/timers:502:7)

chromecast.0
2023-01-03 02:02:37.176
warn
Büro - Client error: Error: read ECONNRESET at TLSWrap.onStreamRead (node:internal/stream_base_commons:217:20)

chromecast.0
2023-01-03 02:02:36.167
warn
Büro - Client error: Error: read ECONNRESET at TLSWrap.onStreamRead (node:internal/stream_base_commons:217:20)

chromecast.0
2023-01-03 02:02:36.162
warn
Büro - Client error: Error: read ECONNRESET at TLSWrap.onStreamRead (node:internal/stream_base_commons:217:20)

chromecast.0
2023-01-03 02:02:29.714
warn
Büro - Client error: Error: connect ECONNREFUSED <IP_ADDRESS>:8009 at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1278:16)

chromecast.0
2023-01-03 02:02:29.527
warn
Büro - Client error: Error: connect ECONNREFUSED <IP_ADDRESS>:8009 at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1278:16)

chromecast.0
2023-01-03 02:02:27.710
warn
Büro - Client error: Error: connect ECONNREFUSED <IP_ADDRESS>:8009 at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1278:16)

chromecast.0
2023-01-03 02:02:27.523
warn
Büro - Client error: Error: connect ECONNREFUSED <IP_ADDRESS>:8009 at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1278:16)

chromecast.0
2023-01-03 02:02:26.704
warn
Büro - Client error: Error: connect ECONNREFUSED <IP_ADDRESS>:8009 at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1278:16)

chromecast.0
2023-01-03 02:02:26.698
warn
Büro - Client error: Error: Device timeout at fn.ontimeout (/opt/iobroker/node_modules/castv2-client/lib/senders/platform.js:56:26) at Object.onceWrapper (node:events:627:28) at fn.emit (node:events:513:28) at fn.emit (node:domain:489:12) at Timeout.ontimeout [as _onTimeout] (/opt/iobroker/node_modules/castv2-client/lib/controllers/heartbeat.js:44:10) at listOnTimeout (node:internal/timers:559:17) at processTimers (node:internal/timers:502:7)

chromecast.0
2023-01-03 02:02:26.518
warn
Büro - Client error: Error: connect ECONNREFUSED <IP_ADDRESS>:8009 at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1278:16)

chromecast.0
2023-01-03 02:02:23.341
warn
Büro - Client error: Error: Device timeout at fn.ontimeout (/opt/iobroker/node_modules/castv2-client/lib/senders/platform.js:56:26) at Object.onceWrapper (node:events:627:28) at fn.emit (node:events:513:28) at fn.emit (node:domain:489:12) at Timeout.ontimeout [as _onTimeout] (/opt/iobroker/node_modules/castv2-client/lib/controllers/heartbeat.js:44:10) at listOnTimeout (node:internal/timers:559:17) at processTimers (node:internal/timers:502:7)

Adapter Version
3.1.0
JS-Controller Version
4.0.23
Node JS Version
16.18.1
NPM Version
8.19.2
Operating System
Debian
Relevant log output
No response
Anything else?
No response

Similar warnings reularly between 03:00 am and 05:00 am here as well.

Duplicate of #162


Lagging in redirecting to homepage after signing in

It takes 4-5 clicks on the "Let's Begin" button after signing up or log in to redirect to the quiz.htnl and homepage.htm respectively.

Sir can I work on this?


HDDS-9513. Let quantiles in GrpcMetrics work normally

What changes were proposed in this pull request?
Fix some bugs about quantiles in GrpcMetrics.
What is the link to the Apache JIRA
https://issues.apache.org/jira/browse/HDDS-9513
How was this patch tested?
Test locally.
When config is like:
<property>
  <name>ozone.grpc.metrics.percentiles.intervals</name>
  <value>57</value>
</property

The result will be:

It was adding to the processing time quantiles twice and skipping the queue time quantiles.
Thanks @YuanbenWang for the fix. Changes LGTM!

Thank you for the review~!


Czech translation for v1.5

1.6 ?

I know I'm late but this is translation for v1.5 strings. For v1.6 I'll make another PR after conventional Google Groups request...

Thanks @dvorapa .
1.6 strings could be another PR i guess, that would avoid rework and delays in string translations.
Merging :+1:


Fix errors ignoring

Errors are ignored in various places

Real errors were igonred at:

https://github.com/voedger/voedger/blob/872556225d3504a3651ea63e8097e7d1381a7da1/pkg/istructsmem/contname-types.go#L176
https://github.com/untillpro/airs-bp3/blob/06a90076054e14e19b38a16a5b54d086d1f643ce/packages/air/it/impl_workspace_test.go#L129

Fixed by https://github.com/voedger/voedger/commit/4e20ccc9d937904e4f8306e5bb67ced3e4790979 and https://github.com/untillpro/airs-bp3/commit/9b5ba2c430b8d00f6672aeafb63c8375f49dcb9d


Add automated test for pg_upgrade

Describe the problem
We should make sure new changes to pg_tle do not break when they go through pg_upgrade.
Describe the proposal
We can potentially do this with a TAP test, but our tests are currently set up to run on a single version of Postgres. Will need to do more investigating

FYI you can find an example of how to do this at https://github.com/theory/pgtap/blob/main/test/test_MVU.sh


Unexpected token when parsing stateless component with flow annotated return type

I'm not sure if this is the right place for this issue, but only eslint complains about the following code, both babel and flow compile without errors / warnings.
export const PageList = ({ pages, width, height }: Props): ReactElement => {
  ...
}

results in:
20:61  error  Parsing error: Unexpected token

It seems you're using the ESLint default parser Espree, but Espree does not support flow annotations (https://github.com/eslint/espree/issues/189).
You'll need to use babel-eslint for this.

I'm actually using "babel-eslint": "^4.1.6" already.

I've also tried "parser": "babel-eslint" in .eslintrc.

Any other ideas on what could be causing the error?

I cannot reproduce the error with<EMAIL_ADDRESS>and<EMAIL_ADDRESS>I'm pretty sure this is not related to eslint-plugin-react at all since the parse error come from ESLint.
But if you can provide me more information (eslint/babel-eslint versions, .eslintrc file and the full source file) maybe I could find the problem.

<EMAIL_ADDRESS>+<EMAIL_ADDRESS>.eslintrc:
{
  "parser": "babel-eslint",
  "extends": "rackt",
  "env": {
    "mocha": true
  },
  "rules": {
    "strict": 0,
    "new-cap": 0,
    "comma-dangle": [1, "always-multiline"],
    "react/jsx-uses-react": 1,
    "react/wrap-multilines": 2,
    "flow-vars/define-flow-type": 1,
    "flow-vars/use-flow-type": 1
  },
  "plugins": [
    "react",
    "flow-vars"
  ]
}

MyComponent.js:
// @flow

import React from 'react'
import { Page } from '../models/Page'

type Props = {
  page: Page,
  width: number,
  height: number
}

export const MyComponent = (props: Props): ReactElement => {
  ...

  return (
    <img key={ref} src={imageUrl} style={style} />
  )
}

@meleyal I can reproduce this issue without eslint-plugin-react I think we need to raise this in ESLint or babel-eslint
This is the simplest version that throws the Parsing error: Unexpected token error
const add = (a: number, b: number): number => a + b;

Upgrading to<EMAIL_ADDRESS>fixes the issue: https://github.com/babel/babel-eslint/issues/237


Update Syncthing to 0.12.1

Thank you for the contribution. It was merged directly as b5accb74ecb145b7bf0b51a287cab0ace0f289ae to keep commit history cleaner. Your contribution is still credited to you.


Bring back the old templates 🙏

The old templates has some advantages that I miss in the current one:

The code is split in modules that makes it easy to work with especially when the application code is growing.
Having control on the app: terminal settings and the drawing loop.

It's worth reading through https://github.com/ratatui/templates/pull/74 to get an understanding of why the changes were made. There's a lot of discussion. There were a lot of problematic bits about the previous simple template that have been ironed out, but I can see how if you were used to those idiosyncrasies, you might miss them.
In particular regarding the modules approach, it's easier to go from no modules to modules as rust-analyzer has an extract module refactoring built-in. It doesn't however have easy move-code-to-module refactorings (yet). I previously wrote:

I have a strong (evidence based) opinion against pre-emptively organizing a project into horizontal layers. Having worked on many projects small and large, horizontal segmentation leads to poorer long term maintainability for a variety of reasons. Doing this would be pre-emptive. Put another way, if I was using the simple template personally, having the extra file would be an annoyance that I'd always want to revert. Reverting would be annoying. Refactoring in the other direction is fairly simple though - highlight code, extract to module, done.

There's definitely room for different templates to be added here. I'd suggest building it up from practices you're using in your apps, perhaps as a pythops/ratatui-template or something.

Having control on the app: terminal settings and the drawing loop.

Can you expand on this?


SQL populate: Raise standard room rates 5% and holiday reservation rates by and additional 5%

Since more and more people are traveling, the room rates have gone up by 5%. Additionally, if the customer makes reservation for a holiday stay (Fourth of July, Christmas Eve, New Years Eve) the increased rate is another 5%.

Update current costs by 5%
write if statement for reservation date

This was a pain in the A$$ :)


Decide on a logging approach

There currently are a few places where "log messages" are printed - using console.log. In some cases, this is already "funneled" into a single, internal log function (similar to the logCallback in the previous version). But there should be something that offers more fine-grained control over what is logged, and where the log output goes.
Of course, one could just go to https://github.com/topics/logging-library?l=typescript and pick the first result. But maybe there are reasons to put more thought into that, and maybe even reasons to pick one specific library.

Obvious places where this should come in handy:
When upgrading a tileset, it currently prints something like this:
Upgrading asset version number
  Upgrading asset version from 1.0 to 1.1
Upgrading refine to be in uppercase
Upgrading content.url to content.uri
  Renaming 'url' property for content parent.b3dm to 'uri'
  Renaming 'url' property for content ll.b3dm to 'uri'
  Renaming 'url' property for content lr.b3dm to 'uri'
  Renaming 'url' property for content ur.b3dm to 'uri'
  Renaming 'url' property for content ul.b3dm to 'uri'
Upgrading extension declarations
  Upgrading GLB in ll.b3dm
  Upgrading GLB in lr.b3dm
  Upgrading GLB in parent.b3dm
  Upgrading GLB in ul.b3dm
  Upgrading GLB in ur.b3dm

So it prints

what it is upgrading on a "task level"
what it is upgrading on an "instance level"

These could just be different log level (as in INFO and FINE, or FINE and FINER).

When executing a "pipeline", things become ... nested:
Executing pipeline
  Executing tilesetStage 0 of 6: upgrade
  Executing tilesetStage : upgrade
    currentInput:  ./specs/data/TilesetOfTilesets
    currentOutput: C:\<temp>\tilesetStage-0-upgrade

<The output from `upgrade`, as above>

  Executing tilesetStage 1 of 6: combine
  Executing tilesetStage : combine
    currentInput:  C:\<temp>tilesetStage-0-upgrade
    currentOutput: C:\<temp>tilesetStage-1-combine
  Executing tilesetStage 2 of 6: _b3dmToGlb
  Executing tilesetStage : _b3dmToGlb
    currentInput:  C:\<temp>tilesetStage-1-combine
    currentOutput: C:\<temp>tilesetStage-2-_b3dmToGlb
    Executing contentStage 0 of 1: b3dmToGlb
Processing source: parent.b3dm with type CONTENT_TYPE_B3DM
        to target: parent.glb
Processing source: tileset3/ll.b3dm with type CONTENT_TYPE_B3DM
        to target: tileset3/ll.glb
Processing source: lr.b3dm with type CONTENT_TYPE_B3DM
        to target: lr.glb
Processing source: ur.b3dm with type CONTENT_TYPE_B3DM
        to target: ur.glb
Processing source: ul.b3dm with type CONTENT_TYPE_B3DM
        to target: ul.glb
Processing source: tileset.json with type CONTENT_TYPE_TILESET
        to target: tileset.json
  Executing tilesetStage 3 of 6: _optimizeGlb
  Executing tilesetStage : _optimizeGlb
    currentInput:  C:\<temp>tilesetStage-2-_b3dmToGlb
    currentOutput: C:\<temp>tilesetStage-3-_optimizeGlb
    Executing contentStage 0 of 1: optimizeGlb
Processing source: parent.glb with type CONTENT_TYPE_GLB
        to target: parent.glb
Processing source: tileset3/ll.glb with type CONTENT_TYPE_GLB
        to target: tileset3/ll.glb
Processing source: lr.glb with type CONTENT_TYPE_GLB
        to target: lr.glb
Processing source: ur.glb with type CONTENT_TYPE_GLB
        to target: ur.glb
Processing source: ul.glb with type CONTENT_TYPE_GLB
        to target: ul.glb
Processing source: tileset.json with type CONTENT_TYPE_TILESET
        to target: tileset.json
  Executing tilesetStage 4 of 6: _separateGltf
  Executing tilesetStage : _separateGltf
    currentInput:  C:\<temp>tilesetStage-3-_optimizeGlb
    currentOutput: C:\<temp>tilesetStage-4-_separateGltf
    Executing contentStage 0 of 1: separateGltf
Processing source: parent.glb with type CONTENT_TYPE_GLB
        to target: parent.gltf
Processing source: tileset3/ll.glb with type CONTENT_TYPE_GLB
        to target: tileset3/ll.gltf
Processing source: lr.glb with type CONTENT_TYPE_GLB
        to target: lr.gltf
Processing source: ur.glb with type CONTENT_TYPE_GLB
        to target: ur.gltf
Processing source: ul.glb with type CONTENT_TYPE_GLB
        to target: ul.gltf
Processing source: tileset.json with type CONTENT_TYPE_TILESET
        to target: tileset.json
  Executing tilesetStage 5 of 6: gzip
  Executing tilesetStage : gzip
    currentInput:  C:\<temp>tilesetStage-4-_separateGltf
    currentOutput: ./output/result

Whether or not log libraries offer a functionality to keep track of indentation levels has to be investigated. (Maybe the indentation has to be tracked manually - right now, the indentation for the pipeline itself here is just "fixed", but this hits some limits when a certain stage creates own log messages...)

The basic integration of a logging library was completed in https://github.com/CesiumGS/3d-tiles-tools/pull/61
There will always be considerations for what is supposed to be logged and how (for example, referring to the "nested logging" during pipeline execution), but this will be part of the respective PRs.


Applied eslint from main .eslintrc to examples

Changed eslintrc to be JSON file (Most projects use JSON version)
Added .eslintignore to ingore node_modules from subdirectories such as examples
Ran eslint --fix examples to fix all examples
Added npm script for running eslint against examples
Added npm script for running eslint against generated out code
Hooked npm scripts into travis ci to prevent examples from becoming inconsistent with future PR's

Thanks!


bech32 nodeid QR

Shouldn't QR code with a bech32 encoded nodeid work?
It seems only the hex version works.
Would be much smaller QR codes.

Please provide qr (or qr value) example, to help dev team reproduce this issue. :)

Thanks! It's not a priority now, but if the new format proposed in the mailing list gains traction, eclair will certainly support it.


RX2 downlink handling in case RX1 frame was detected but not intended for the end-device

Handle following edge-case:

Listen for RX1 downlink and start receiving frame...
Hook into HeaderReceived (or any other possible mechanism) and validate MIC and check whether packet is intended for current end-device...
...if not, handle RX2 window if timing still allows it.

I think it is well handled. The mac layer returns NoUpdate unless it's successful basically.
Does this not satisfy the case your detailing?

Sorry, I should make an effort to rephrase:

We will proceed to RX2 as long as fn rx_listen returns None: https://github.com/lora-rs/lora-rs/blob/258ce4bbcb2e71075e52db91f4600f43641059b3/lorawan-device/src/async_device/mod.rs#L371
After processing a frame, the fn rx_listen returns None if the mac layer responds with: NoUpdate: https://github.com/lora-rs/lora-rs/blob/258ce4bbcb2e71075e52db91f4600f43641059b3/lorawan-device/src/async_device/mod.rs#L403
The mac layer responds with NoUpdate when it fails to parse the frame: https://github.com/lora-rs/lora-rs/blob/main/lorawan-device/src/mac/session.rs#L162

Sorry, I should make an effort to rephrase:
1. We will proceed to RX2 as long as `fn rx_listen` returns `None`: https://github.com/lora-rs/lora-rs/blob/258ce4bbcb2e71075e52db91f4600f43641059b3/lorawan-device/src/async_device/mod.rs#L371

2. After processing a frame, the `fn rx_listen` returns `None` if the mac layer responds with: `NoUpdate`: https://github.com/lora-rs/lora-rs/blob/258ce4bbcb2e71075e52db91f4600f43641059b3/lorawan-device/src/async_device/mod.rs#L403

3. The mac layer responds with `NoUpdate` when it fails to parse the frame:
   https://github.com/lora-rs/lora-rs/blob/main/lorawan-device/src/mac/session.rs#L162

Ok, I'll take your word ont it.. :+1:


Error 500 on last release

I caught error 500 on /laravel-filemanager route since last release.
No more information, sorry.
Investigate on last PR ;)

Not sure is a package issue.

Ref #15

I just merged #15.
Please let me know whether it solves your issue.

It works, but only with dev-master#5a8e244 on my composer.json
May be we have to tag a minot release (bugfix) 1.0.1?

@welcoMattic
Thanks! Bump to 1.1.0

Perfect timing for my last preprod deploy of the week!
Thanks :wink:

You are welcome, have a nice weekend!


Image: support transparency

Add an Alpha = 1.0 property to the Image plot type.

https://scottplot.net/cookbook/4.1/#image

This may also allow overlaying a semitransparent image above a heatmap which may help @bukkideme in #2277

duplicate, will address in #2285


Homebrew install fails

Hi, when doing brew install samuelmeuli/tap/tmignore I get this error:
xcodebuild: error: Could not resolve package dependencies:
  sandbox-exec: sandbox_apply_container: Operation not permitted

make: *** [build] Error 74

I'm running as standard user (no admin) if that matters. Make log is attached.
01.make.txt

Any luck with v1.2.1? I'm afraid I haven't been able to reproduce the error yet.

nope, fails too
==> make build
Last 15 lines from /Users/mario/Library/Logs/Homebrew/tmignore/01.make:

Fetching https://github.com/IBM-Swift/HeliumLogger

Fetching https://github.com/SwiftyJSON/SwiftyJSON

Fetching https://github.com/apple/swift-log

Fetching https://github.com/jakeheis/SwiftCLI

Fetching https://github.com/samuelmeuli/swift-exec

xcodebuild: error: Could not resolve package dependencies:
  sandbox-exec: sandbox_apply_container: Operation not permitted

make: *** [build] Error 74

Also having the same error.

I've tested the install on two machines and haven't encountered any issues:

macOS 10.15.4 and 10.15.5
Xcode 11.5
Homebrew 2.3.0-21-g7db771b

Prebuilt binaries are available on the Releases page.

Thanks for the prebuilts, they work great
But +1 to this bug on Mojave 10.14.6
Homebrew 2.3.0 (git revision 467e0; last commit 2020-06-05)
Xcode 11.3.1

After upgrading to Catalina and updating Xcode it works for me now :)
@onlinelaser try updating xcode?

Same here: after upgrading to macOS Catalina, brew upgrade was successful.

Tried all the methods here and I'm also getting the same error. My system is, as of this moment, up-to-date:
Mac OS 10.15.6 (19G2021)
XCode 12.0 (12A7209)
Homebrew 2.5.1
Any ideas?

I'm also getting the "sandbox-exec: sandbox_apply: Operation not permitted" error. I'm on macOS 10.15.17 and XCode 12.0.1.
BTW, I had to download the full XCode, command line tools were not enough. (Unfortunately, I didn't copy the error message.)
@samuelmeuli With the pre-built binaries, future upgrades won't work, right? Also, brew services start tmignore also won't be available I guess?!

Hi, I have similar issue not related to this repository but the symptoms look very similar so maybe suffer from the same issue: https://community.sonarsource.com/t/xcodebuild-can-not-resolve-package-dependencies-using-build-wrapper-macosx-x86/32959/17

I'm also getting the sandbox-exec: sandbox_apply: Operation not permitted error as well.
macOS: 10.15.7 (19H15)
XCode: 12.1 (12A7403)
Homebrew: 2.5.8
Here the terminal output:
brew install samuelmeuli/tap/tmignore
Updating Homebrew...
==> Auto-updated Homebrew!
Updated 2 taps (homebrew/core and homebrew/cask).
==> New Formulae
condure
==> Updated Formulae
Updated 1 formula.
==> Updated Casks
vagrant                                  vagrant-vmware-utility

==> Installing tmignore from samuelmeuli/tap
==> Downloading https://github.com/samuelmeuli/tmignore/archive/v1.2.2.tar.gz
Already downloaded: /Users/stefan/Library/Caches/Homebrew/downloads/694e9e2acfa7fc1d36e4be32543d766098b853eaf69a98ec5ec66fbc803d0abd--tmignore-1.2.2.tar.gz
==> make build
Last 15 lines from /Users/stefan/Library/Logs/Homebrew/tmignore/01.make:

Fetching https://github.com/jakeheis/SwiftCLI

Fetching https://github.com/samuelmeuli/swift-exec

Fetching https://github.com/apple/swift-log

Fetching https://github.com/SwiftyJSON/SwiftyJSON

Fetching https://github.com/IBM-Swift/HeliumLogger

xcodebuild: error: Could not resolve package dependencies:
  sandbox-exec: sandbox_apply: Operation not permitted

make: *** [build] Error 74

If reporting this issue please do so at (not Homebrew/brew or Homebrew/core):
  https://github.com/samuelmeuli/homebrew-tap/issues

I tried the prebuilt binaries and it works.
To fix the macOS Catalina error
“tmignore” cannot be opened because the developer cannot be verified.
macOS cannot verify that this app is free from malware.

You have to run the following command (make sure you use the right path):
xattr -d com.apple.quarantine /usr/local/bin/tmignore
Question now is how to get the scheduler running?

Homebrew install in Big Sur also does not work unfortunately.

I was so glad to discover this repo but then felt said in just two minutes after hitting this issue too. This reminded me of a famous monologue by Luis CK with this part on the airplaine wifi:

I was on an airplane and there was high-speed Internet on the airplane. That's the newest thing that I know exists.
And it's fast, and I'm watching YouTube clips. It's amaz--I'm on an airplane! And then it breaks down. And they apologize, the Internet's not working. And the guy next to me goes, 'This is b___s___.' I mean, how quickly does the world owe him something that he knew existed only 10 seconds ago?

😂
Hope that this problem can be solved at some point. Great app idea @samuelmeuli regardless!
Meanwhile, if anyone knows of any easy-to-apply workarounds, please share 🙌

Workaround: Download and use the precompiled binary from the Releases page: https://github.com/samuelmeuli/tmignore/releases

Just added a PR which works around the install problem: https://github.com/samuelmeuli/homebrew-tap/pull/3

@samuelmeuli any chance you could please push in #18 and then release a new version so installation via Homebrew works again?

Any updates on this?

same error here, any news or info how to resolve?

Bruh


Scaling referenced () inlined SVGs with CSS by using height/width along with auto

According to this guide on the root svg element the width/height or the viewbox needs to be set, so the svg can properly scaled via CSS, when either height or width is set to auto.
The generated sprite from svg-sprite I embed like this:
<svg version="2.0">
  <use href="sprite.svg#logo" />
</svg>

I think it would be a great feature for svg-sprite to export a JSON file with some meta information about the sprites like width, height and viewBox, which then can dynamically added.

@openscript hello!
All the data (except viewbox) can be found here in the shape field. You can easily calculate the viewBox like 0 0 ${shape.width.inner} ${shape.height.inner}


uploading projects

hi, its my frist hours here and i want to  upload my project and i gett this message:
Uploads are disabled.
File uploads require push access to this repository.
so what should i do

solved


Unable to pull the Docker image

I'm getting this error when trying to pull the Docker image according to the description:
docker run --rm -v $(pwd):/out -e BATON_INSTANCE_URL=acme.my.salesforce.com -e BATON_USER_USERNAME_FOR_EMAIL=false ghcr.io/conductorone/baton-salesforce:latest -f "/out/sync.c1z"
Unable to find image 'ghcr.io/conductorone/baton-salesforce:latest' locally
docker: Error response from daemon: Head "https://ghcr.io/v2/conductorone/baton-salesforce/manifests/latest": unauthorized.

This should be fixed for you now. Sorry about that!


Added api_v2_errors

I've added api_v2_errors macro which implements Apiv2Errors trait for selected struct - it can be then (afer implementing also ResponseError) used in handler return type (example added in tests) to document errors in swagger.
Additional implementation of OperationModifier on Result<T, E> where
T is OperationModifier and E is OprationErrorsModifier
allows to automatically add defined errocodes to swagger handler response.
I'll test it in my project if it will work smooth in following days, but meanwhile you could maybe take a look if this approach is good enough (it's not the best for sure :-))

It's not very convenient to define struct and impl Display and ResponseError for it to just add errorcodes to swagger, but it worked for me well. There is a handy lib enum-display-derive which makes it more compact. I've added an example to the book.

Thank you very much for your work! I'll look into this in detail tonight. I have a few suggestions based on how I'd planned for this.

I don't think #62 can't be closed after this PR. You still won't be able to have 201 in swagger instead of 200 as 200 is inserted always.

#[api_v2_errors(
    description="foo",
    code=403, description="bar",
    code=-10,
    code="100", description="spam", description="eggs",
    code=50,
    code=469,
    code=1500,
    code=1000000000,
)]

Will generate bunch of errors and warnings:
  --> src/handlers/posts.rs:12:5
   |
12 |     description="adsfadsf",
   |     ^^^^^^^^^^^^^^^^^^^^^^

error: Invalid u16 in code argument
  --> src/handlers/posts.rs:14:5
   |
14 |     code=-10,
   |     ^^^^^^^^

error: Invalid macro attribute. Should be 'code = int' or 'description = str'
  --> src/handlers/posts.rs:15:5
   |
15 |     code="100", description="blablabla", description="datata",
   |     ^^^^^^^^^^

warning: This attribute overwrites previous description
  --> src/handlers/posts.rs:15:42
   |
15 |     code="100", description="blablabla", description="datata",
   |                                          ^^^^^^^^^^^^^^^^^^^^

error: Invalid u16 in code argument
  --> src/handlers/posts.rs:19:5
   |
19 |     code=1000000000,
   |     ^^^^^^^^^^^^^^^

warning: Invalid status code 50
  --> src/handlers/posts.rs:16:5
   |
16 |     code=50,
   |     ^^^^^^^

warning: Status code 469 doesn't have a canonical name
  --> src/handlers/posts.rs:17:5
   |
17 |     code=469,
   |     ^^^^^^^^

warning: Invalid status code 1500
  --> src/handlers/posts.rs:18:5
   |
18 |     code=1500,
   |     ^^^^^^^^^

error: aborting due to 4 previous errors

Let me know is you want maybe some of warnings be changed to errors, for invalid codes for example.

I don't think #62 can be closed after this PR.

 Should probably just leave it as a link rather than link it through Github.

 Nice work! Thanks!

Thank you very much for working on this!

Boohoo, you've overwritten my authorship :stuck_out_tongue:
Next, I'd try to add tags in operation macro attribute :-)

I've no idea how it happened! I merged it the same way as your previous PR! But anyway, I've done a rebase, changed the commit author and force pushed! Your authorship has been restored!
Looking forward to your work! :smile:


Custom metrics demo

I would like to inquire about monitoring the Bluetooth connection status and how to create a custom Metric for this purpose. Could you please provide me with a demo or example on how to achieve this?

@ftc300 I hope you figured this out.
We will add an example that will showcase a use case with the usage of custom metrics real soon.

@ftc300 I hope you figured this out.
We will add an example that will showcase a use case with the usage of custom metrics real soon.

@vikramdattu please kindly spend time showing us how to add custom metrics and variables as well. Thank you in advanced!

Hi @dolphin22 adding a custom metric/veriable has two parts:

Register a metrics/veriable // one time at the start after initialising insights
Send the data // this can be multiple times as per requirement

#include <esp_diagnostics_metric.h>`
#define TAG "heap"
#define KEY "free"
#define LABEL "amount of free heap"
#define PATH "Heap.Free"

Register a metric:
esp_diag_metrics_register(TAG, KEY, LABEL, PATH ESP_DIAG_DATA_TYPE_UINT); // API ref
Send the data: (this can be done multiple times)
uint32_t free_heap = <code to get free heap>
esp_diag_metrics_add_uint(KEY,  free heap);

API ref
Hope this helps!

Hi @dolphin22 adding a custom metric/veriable has two parts:

Register a metrics/veriable // one time at the start after initialising insights
Send the data // this can be multiple times as per requirement

#include <esp_diagnostics_metric.h>`
#define TAG "heap"
#define KEY "free"
#define LABEL "amount of free heap"
#define PATH "Heap.Free"

Register a metric: esp_diag_metrics_register(TAG, KEY, LABEL, PATH ESP_DIAG_DATA_TYPE_UINT); // API ref
Send the data: (this can be done multiple times)
uint32_t free_heap = <code to get free heap>
esp_diag_metrics_add_uint(KEY,  free heap);

API ref
I have shown the example to add metrics, you can extend this similarly for variables. Hope this helps!

It works, thanks!


Batch update of alt text and title attributes across documentation

(Actions ran in https://github.com/jonathanalgar/langchain/pull/3. Links to LangSmith traces for runs from each commit can be found from here).
Description: Batch update of alt text and title attributes for images across repo using alttexter/alttexter-ghclient (built using LangChain/LangSmith).
I added to PR all files with markdown formatted text containing images found across the repo (*ex ./README.md).
I checked all of the generated alt texts and titles and didn't find any technical inaccuracies.
Some files didn't update:
Already have good alt texts so didn't add files to PR:

https://github.com/langchain-ai/langchain/blob/27dca2d92fbd9c956a1eac7cf885a0ed060ca9ff/docs/docs/integrations/providers/argilla.mdx#L3
https://github.com/langchain-ai/langchain/blob/27dca2d92fbd9c956a1eac7cf885a0ed060ca9ff/docs/docs/integrations/callbacks/argilla.ipynb?short_path=9e89cb5#L236
https://github.com/langchain-ai/langchain/blob/27dca2d92fbd9c956a1eac7cf885a0ed060ca9ff/docs/docs/integrations/providers/apify.mdx#L11

Needs separate PR(s) on this repo to fix image definitions:

https://github.com/langchain-ai/langchain/blob/27dca2d92fbd9c956a1eac7cf885a0ed060ca9ff/docs/docs/integrations/tools/e2b_data_analysis.ipynb?short_path=e92e707#L207
https://github.com/langchain-ai/langchain/blob/27dca2d92fbd9c956a1eac7cf885a0ed060ca9ff/templates/rag-mongo/README.md?plain=1#L134

svg images not supported by gpt4-vision-preview:

https://github.com/langchain-ai/langchain/blob/27dca2d92fbd9c956a1eac7cf885a0ed060ca9ff/docs/docs/get_started/introduction.mdx#L17

alttexter-ghclient can't parse URL:

https://github.com/langchain-ai/langchain/blob/27dca2d92fbd9c956a1eac7cf885a0ed060ca9ff/cookbook/meta_prompt.ipynb?short_path=2339907#L14
(Added TODO)

alttexter-ghclient needs image filename in URL:

https://github.com/langchain-ai/langchain/blob/27dca2d92fbd9c956a1eac7cf885a0ed060ca9ff/templates/rag-gemini-multi-modal/README.md?plain=1#L12
https://github.com/langchain-ai/langchain/blob/27dca2d92fbd9c956a1eac7cf885a0ed060ca9ff/templates/rag-chroma-multi-modal/README.md?plain=1#L12
https://github.com/langchain-ai/langchain/blob/27dca2d92fbd9c956a1eac7cf885a0ed060ca9ff/templates/rag-multi-modal-local/README.md?plain=1#L14
https://github.com/langchain-ai/langchain/blob/27dca2d92fbd9c956a1eac7cf885a0ed060ca9ff/templates/rag-multi-modal-mv-local/README.md?plain=1#L14
https://github.com/langchain-ai/langchain/blob/27dca2d92fbd9c956a1eac7cf885a0ed060ca9ff/templates/rag-chroma-multi-modal-multi-vector/README.md?plain=1#L12
https://github.com/langchain-ai/langchain/blob/27dca2d92fbd9c956a1eac7cf885a0ed060ca9ff/docs/docs/modules/data_connection/retrievers/self_query.ipynb?short_path=44acd54#L18
https://github.com/langchain-ai/langchain/blob/27dca2d92fbd9c956a1eac7cf885a0ed060ca9ff/docs/docs/modules/data_connection/retrievers/contextual_compression.ipynb?short_path=f9abef1#L20
(Added TODO)

alttexter-ghclient can't use ipynb attachment:

https://github.com/langchain-ai/langchain/blob/27dca2d92fbd9c956a1eac7cf885a0ed060ca9ff/cookbook/Semi_Structured_RAG.ipynb?short_path=91820b6#L30
https://github.com/langchain-ai/langchain/blob/27dca2d92fbd9c956a1eac7cf885a0ed060ca9ff/docs/docs/integrations/retrievers/Activeloop DeepMemory%2BLangChain.ipynb?short_path=367491e#L249
(Added TODO)

@efriis I'm not sure why the changes in the ipynb alt texts are breaking the build 🤔 for example:
SyntaxError: /home/ja/langchain-2/_dist/docs/modules/chains/document/map_reduce.md: Unterminated string constant. (16:13)
  14 | them to an LLM). This compression step is performed recursively if
  15 | necessary.`}

> 16 |

  19 |
{`Recreating with LCEL`}

SyntaxError: /home/ja/langchain-2/_dist/docs/modules/chains/document/refine.md: Unterminated string constant. (21:13)
  19 | when documents frequently cross-reference one another or when a task
  20 | requires detailed information from many documents.`}

> 21 |

  23 |
{`Recreating with LCEL`}

  24 |
{`With `}{`LangChain Expression Language`}{` we can

the md syntax is identical as before

@efriis I'm not sure why the changes in the ipynb alt texts are breaking the build 🤔 for example:
SyntaxError: /home/ja/langchain-2/_dist/docs/modules/chains/document/map_reduce.md: Unterminated string constant. (16:13)
  14 | them to an LLM). This compression step is performed recursively if
  15 | necessary.`}

> 16 |

  19 |
{`Recreating with LCEL`}

SyntaxError: /home/ja/langchain-2/_dist/docs/modules/chains/document/refine.md: Unterminated string constant. (21:13)
  19 | when documents frequently cross-reference one another or when a task
  20 | requires detailed information from many documents.`}

> 21 |

  23 |
{`Recreating with LCEL`}

  24 |
{`With `}{`LangChain Expression Language`}{` we can

the md syntax is identical as before

identified issue, working on a fix later this evening!

Removed ipynb files from PR—there is an issue with the alt text getting wrapped in the markdown cells (default filters of the stable version of Quarto). This is handled by Docusaurus v3+ but not the Docusaurus that the build uses (2.4.3). Full discussion: https://github.com/quarto-dev/quarto-cli/discussions/8131
tl;dr: I'll open a new PR with the alt texts for the ipynb files once Docusaurus is bumped to v3+.


Active listeners for Feedback Dataset

Is your feature request related to a problem? Please describe.
For feedback datasets, which carry the ability to carry complex labeling tasks, manual interactions to trigger training/evaluation can be a bottleneck for high frequency models.
Describe the solution you'd like
Active listeners for datasets in Argilla to trigger functions on submit, maybe an ability to ex. trigger on submitted 50/60 examples or 60/60 examples etc.

I also just encountered this problem and found it very surprising to find out that listeners only work with pre-built template datasets.
From what I could discover it's because /api/datasets endpoint only returns these pre-built template datasets and deep down listeners only check that endpoint.

Reopening, as we might still want to tackle this one.


🚧 (project) add rich library for a user friendly CLI

Purpose
ralph can be used as a CLI and integrating the rich library makes the tool more user friendly and easy to read.
Proposal
The provided handler from rich replaces the custom made stream handler.
:warning: The logging configuration, as initially set, does not support rich logging handler coloration. We need to instantiate the handler to have access to a console instance, and here configure the color system.
:test_tube: logger tests are failing, as for now, I have not updated them with the new handler. The rich integration enforces message wrapping. It is not yet possible to run correctly the test

Seen and discussed with @wilbrdt, we should consider configure the logger in a other way. To get the coloration with the RichHandler, a console should be configured.
Will configure the logger with a direct instantiation of the handler

@jmaupetit what do you think of this configuration for rich ?


Possible memory fault in emit_token()

In some files while emitting token using the "tokenizer" approach instead of "gradual scanner", the memory boundary goes between two separate segments resulting in huge memory segment length as the argument to calloc.
It seems that the problem is with lexer have-shift mechanism

Problem was with inforrect shift of the buffer content and its pointers in lexer. Commit 85dcb4035485fcbd59181eb103b4250b15025497 addresses this issue.
Closing issue.


ABC iView 401 Authentication Error

Checklist

[X] I'm reporting a broken site support
[X] I've verified that I'm running youtube-dl version 2021.12.17
[X] I've checked that all provided URLs are alive and playable in a browser
[X] I've checked that all URLs and arguments with special characters are properly quoted or escaped
[X] I've searched the bugtracker for similar issues including closed ones

Verbose log
[debug] System config: []
[debug] User config: []
[debug] Custom config: []
[debug] Command-line args: ['-v', '-u', 'PRIVATE', 'https://iview.abc.net.au/video/CH1911H022S00']
Type account password and press [Return]:
[debug] Encodings: locale cp1252, fs mbcs, out cp437, pref cp1252
[debug] youtube-dl version 2021.12.17
[debug] Python version 3.4.4 (CPython) - Windows-10-10.0.22610
[debug] exe versions: ffmpeg 2022-05-02-git-40f2ea971f-full_build-www.gyan.dev, ffprobe 2022-05-02-git-40f2ea971f-full_build-www.gyan.dev
[debug] Proxy map: {}
[debug] Using fake IP <IP_ADDRESS> (AU) as X-Forwarded-For.
[abc.net.au:iview] CH1911H022S00: Downloading JSON metadata
[abc.net.au:iview] CH1911H022S00: Downloading webpage
ERROR: Unable to download webpage: HTTP Error 401: Unauthorized (caused by HTTPError()); please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; type  youtube-dl -U  to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
File "C:\Users\dst\AppData\Roaming\Build archive\youtube-dl\ytdl-org\tmpupik7c6w\build\youtube_dl\extractor\common.py", line 634, in _request_webpage
File "C:\Users\dst\AppData\Roaming\Build archive\youtube-dl\ytdl-org\tmpupik7c6w\build\youtube_dl\YoutubeDL.py", line 2288, in urlopen
File "C:\Python\Python34\lib\urllib\request.py", line 470, in open
File "C:\Python\Python34\lib\urllib\request.py", line 580, in http_response
File "C:\Python\Python34\lib\urllib\request.py", line 508, in error
File "C:\Python\Python34\lib\urllib\request.py", line 442, in _call_chain
File "C:\Python\Python34\lib\urllib\request.py", line 588, in http_error_default
Description

WRITE DESCRIPTION HERE
ABC iView exhibits a HTTP 401 error. I have tried other systems and different accounts. All yield the same result.

The ABC iView extractor doesn't know how to log in. If that should be needed, use --cookies ... with cookies saved from your logged-in browser session (see Readme/manual for more).

@gamer191 I am using a VPN. My provider has not been blocked and I can access the video just fine with my account through Firefox. I have had extractor errors when using my cookie so I will need to look into that.


umremovable (recent played server)

this issue led me not able to use other mods as I always ended up clicking that button instead of doing other stuff.

This mod is abandoned so I encourage you to use 5zig reborn: https://github.com/5zig-reborn/The-5zig-Mod
You will get more support there and maybe your issue got patched.


Add tool for upgrading from v7 to v8

Description
Tool to ease the process of upgrading existing v7 application to v8.
Marking as draft until workflow for creating releases with binaries are in place
Related Issue(s)
Fixes #275
Verification

[ ] Your code builds clean without any errors or warnings
[ ] Manual testing done (required)
[ ] Relevant automated test added (if you find this hard, leave it and we'll help out)
[ ] All tests run green

Documentation

[ ] User documentation is updated with a separate linked PR in altinn-studio-docs. (if applicable)

No solution file?

No solution file or changes to existing?

Didn't add the project file to the app solution file. If we add it to the solution I think it will trigger a build and release of the upgrade tool when we release a new version of the app nugets


Please document the XEE attacks when using DOMHandle so that custoemrs avoid this vulnerability

So we can address your issue, please include the following:
Version of MarkLogic Java Client API
4.2.0
Version of MarkLogic Server
9.0-9.1
The java api is vulnerable to very easy to exploit XEE attacks. In particular the usage of a DOMHandle is vulnerable.
See the following code snippet for a working exploit.
import com.marklogic.client.DatabaseClient;
import com.marklogic.client.DatabaseClientFactory;
import com.marklogic.client.document.XMLDocumentManager;
import com.marklogic.client.io.DOMHandle;
import com.marklogic.client.io.StringHandle;

import java.nio.charset.Charset;

class Scratch {
   public static void main(String[] args) {
       final DatabaseClient client = DatabaseClientFactory.newClient("localhost", 8000, new DatabaseClientFactory.DigestAuthContext("admin", "admin"));
       final String xml = "" +
           "" +
           "]>" +
           "&xxe;";

       final XMLDocumentManager docMngr = client.newXMLDocumentManager();

       final DOMHandle handle = new DOMHandle();
       handle.fromBuffer(xml.getBytes(Charset.forName("UTF-8")));

       docMngr.write("test.xml", handle);

       System.out.println(docMngr.read("test.xml", new StringHandle()).get());
   }
}

This codesnippets save the content of /etc/passwd to "test.xml" in marklogic and prints its content.
As soon as a DOMHandle is used the injection of system resources (of the host the application is running on) is possible.
See DOMHandle's makeDocumentBuilderFactory method which creates a insecure DocumentBuilderFactory instance.
Please document this scenario so that customers don't run into this issue.
The issue was originally reported by Michale Wagner from SiteFusion.de via MarkLogic support.

My point with this support issue was that I think its more safe to not allow external entities by default so customers do not get affected by xee attacks so easily.
I can understand if you do not want to introduce a possible breaking change for customers currently relying on the functionality though. It should of course be properly documented in the DOMHandle API then :)

Given that we're introducing other backward incompatibilities, it seems okay to introduce this one.
I applied the OWASP recommendations to the SAX, StAX, and other defaulted parsers as well.
Of course, the parsers provided by the handles are only defaults.  The application is free to configure their own parsers in all cases.
Shouldn't cause any regressions.

Ran the snippet on develop branch. The code throws exception.
Fixed.
12:32:14,770 |-INFO in ch.qos.logback.classic.LoggerContext[default] - Found resource [logback-test.xml] at [file:/C:/space/HEAD/java-client-api/marklogic-client-api-functionaltests/bin/test/logback-test.xml]
12:32:14,771 |-WARN in ch.qos.logback.classic.LoggerContext[default] - Resource [logback-test.xml] occurs multiple times on the classpath.
12:32:14,771 |-WARN in ch.qos.logback.classic.LoggerContext[default] - Resource [logback-test.xml] occurs at [file:/C:/space/HEAD/java-client-api/marklogic-client-api/bin/test/logback-test.xml]
12:32:14,771 |-WARN in ch.qos.logback.classic.LoggerContext[default] - Resource [logback-test.xml] occurs at [file:/C:/space/HEAD/java-client-api/marklogic-client-api-functionaltests/bin/test/logback-test.xml]
12:32:14,856 |-INFO in ch.qos.logback.classic.joran.action.ConfigurationAction - debug attribute not set
12:32:14,856 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - About to instantiate appender of type [ch.qos.logback.core.ConsoleAppender]
12:32:14,864 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - Naming appender as [STDOUT]
12:32:14,871 |-INFO in ch.qos.logback.core.joran.action.NestedComplexPropertyIA - Assuming default type [ch.qos.logback.classic.encoder.PatternLayoutEncoder] for [encoder] property
12:32:14,924 |-INFO in ch.qos.logback.classic.joran.action.RootLoggerAction - Setting level of ROOT logger to INFO
12:32:14,924 |-INFO in ch.qos.logback.core.joran.action.AppenderRefAction - Attaching appender named [STDOUT] to Logger[ROOT]
12:32:14,925 |-INFO in ch.qos.logback.classic.joran.action.ConfigurationAction - End of configuration.
12:32:14,927 |-INFO in ch.qos.logback.classic.joran.JoranConfigurator@449b2d27 - Registering current configuration as safe fallback point

[Fatal Error] :1:1: Content is not allowed in prolog.
Exception in thread "main" org.w3c.dom.ls.LSException: Content is not allowed in prolog.
	at com.sun.org.apache.xerces.internal.parsers.DOMParserImpl.parse(DOMParserImpl.java:1015)
	at com.marklogic.client.io.DOMHandle.receiveContent(DOMHandle.java:423)
	at com.marklogic.client.io.DOMHandle.fromBuffer(DOMHandle.java:182)
	at com.marklogic.client.functionaltest.Scratch.main(Scratch.java:22)
Caused by: ::::1:1:3:Content is not allowed in prolog.
	at com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:376)
	at com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:327)
	at com.sun.org.apache.xerces.internal.impl.XMLScanner.reportFatalError(XMLScanner.java:1472)
	at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl$PrologDriver.next(XMLDocumentScannerImpl.java:994)
	at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next(XMLDocumentScannerImpl.java:602)
	at com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.next(XMLNSDocumentScannerImpl.java:112)
	at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:505)
	at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:842)
	at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:771)
	at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:141)
	at com.sun.org.apache.xerces.internal.parsers.DOMParserImpl.parse(DOMParserImpl.java:985)
	... 3 more


more one group of variants ?

are possible use oscar for variants when need more by one group of variants?
for example, T_shirts:
colors: black, white, red
sizes: M, L, XL
and different price for every variant ? any plans ?

It's not clear what you are asking here - can you provide a more detailed explanation of what you are trying to achieve? Oscar already allows you to add any number of variants to a product, which different pricing for each. If you need more flexibility you can also calculate the price dynamically in your pricing strategy.

Closing due to lack of feedback - feel free to reopen if you can provide more details.


Said crashed

Siad has exited unexpectedly. Please submit a bug report including the error log
Loading...
(0/6) Loading siad...
(1/6) Loading gateway...
(2/6) Loading consensus...
(3/6) Loading transaction pool...
(4/6) Loading wallet...
(5/6) Loading host...
(6/6) Loading renter...
Finished loading in 2.817313564 seconds
Wallet: scanned to height 34547...

Checking /var/log/messages this looks like oom-killer nuked it overnight.


How Privacy Computation Engine Works

High-level explainer on how Privacy Computation Egine and Privacy Compiler work.
Covers configuration and what to expect from those components. Also specifies all the fields necessary to configure the PCE (including RoPA)
Close blindnet-io/devrel-management/issues/52
Close blindnet-io/devrel-management/issues/51
Close blindnet-io/product-management/issues/829

I wrote basic black-box-view documentaiton on how Privacy Computation Engine and Privacy Compiler work.
I used the "How to configure..." part do define the settings kind of input the PCE takes. @m4rk055 please review this ASAP and see if it is in sync with what you are doing. Feel free to make changes if not, but let us itterate this week to have a stable definition of what are the settings that go in.
My idea is to have the Systems define a table of records that can be easily derived from typical privacy policies. See for example this one "7 - Treatment details". The whole setting should be easily defined by reading the privacy policy. Also, it should be as easy, given the settings, to generate a Ptivacy policy.
p.s. Also I don't let the System specify their own human-readable lables for PRIV categories and other terms here. I assume, Systems can have a configuration file where they handle localized labels for PRIV terms, and then they can here, in configuration, only provide the PRIV Term.

The PR has been approved by @m4rk055, but https://github.com/blindnet-io/blindnet.dev/pull/27/commits/c1554a54c9e9e21b15714c5a458197e85add1c8c introduced several changes afterwards. I'm therefore asking for a new approval before merging it.


BuildRenderTree does not get called in Preview 4

Describe the bug
I've added a simple component which overrides BuildRenderTree and attempts to wrap ChildContent in a simple <div>.  I've more complex logic in a real-world usage, but this simple test demonstrates the issue.
I'm wondering if this is related to the ix for #8192
To Reproduce
See reproducible demo here:
https://github.com/DerekChasse/BuildRenderTree
Index.razor has a <p> tag which should, as part of rendering the TestComponent, be wrapped in a <div> and that <div> should have a GUID identifier as a simple test of AddAttribute.
Expected behavior
I would expect that, as in preview 0.9.0 calls to the overridden BuildRenderTree be honored.
Screenshots

Additional context
There is also simple logging with Console.Writeline in the BaseIndex baseclass which was previously honored in and is no longer being called.
Visual Studio 16.1.0 Preview 2.0
dotnet 3.0.100-preview4-011223

As I mentioned on Gitter @DerekChasse. This is an issue with your code, you've overridden BuildRenderTree in a base class, TestComponentBase.cs, which is inherited by TestComponent.razor but you've also specified markup in TestComponent.razor file. This is overriding your code in BuildRenderTree.

The explanation from @chrissainty is correct. Generated Razor code will replace override  BuildRenderTree() and will not call call base.BuildRenderTree(). This is the intended behavior, we want to make it possible to subclass a component and totally replace its markup.


createPlatformPaymentMethod iOS error

Describe the bug
Calling createPlatformPaymentMethod produces the following error on iOS:
Attempt to present <PKPaymentAuthorizationViewController: 0x7fdfec8d4d60> on <RCTModalHostViewController: 0x7fdfce953b10> (from <RCTModalHostViewController: 0x7fdfce953b10>) whose view is not in the window hierarchy

Checked the deprecated presentApplePay and it works with no problems.
To Reproduce
createPlatformPayPaymentMethod({
  applePay: {
    cartItems: [
      {
        amount: "20",
        paymentType: 'Immediate',
        label: 'Total',
        isPending: false,
      },
    ],
    merchantCountryCode: 'GB',
    currencyCode: 'GBP',
  },
})

Expected behavior
Apple pay sheet to open
Smartphone (please complete the following information):

Device: iPhone 14 Pro Max
OS: 16.4

Additional context

RN 0.71.7
RN-Stripe 0.26.0
Pod Stripe 23.5.1

Upgrading from stripe 0.4.0 to latest. Our flow doesn't allow us to use paymentSheet so we were using presentApplePay that has been marked as depecrated.

RCTModalHostViewController

Looks like you're calling this while a Modal component is presented. I tried this and it's still working for me, so could you provide a reproducible demo?

Hi @charliecruzan-stripe, thanks for looking into it. I'll try to get a reproducible demo.
 I cannot reproduce it anymore. No idea what it was then, maybe some dodgy depedencies or a bad install... closing


usql: 0.13.3 -> 0.13.4

Description of changes
https://github.com/xo/usql/compare/v0.13.3...v0.13.4
Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[ ] Fits CONTRIBUTING.md.

$ ./result/bin/usql sqlite://test
Connected with driver sqlite3 (SQLite3 3.39.4)
Type "help" for help.

sq:test=> select cos(pi());
 cos(pi())
-----------
        -1
(1 row)

Result of nixpkgs-review pr 207143 run on x86_64-linux 1

2 packages built:

darwin.builder
usql


chore: fix the missing example.toml in README-CN

The example.toml is missing in the docs folder, the minimal.toml is valid.
Rationale
example.toml was renamed into minimal.toml
Detailed Changes
change the README-CN's  content
Test Plan

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

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

Thank you very much for your contribution.

If it's convenient for you, please sign the CLA for PR merging.

If it's convenient for you, please sign the CLA for PR merging.

Done

@zuston Merged in, thanks again for your contribution and welcome to the ceresdb community.


Function libxml_disable_entity_loader() is deprecated

PHP 8 deprecated the libxml_disable_entity_loader() function.

Sorry for the late reply, anyway, now version 1.2.1 is compatible with PHP 8.
composer update will resolve the issue.


Support bloom filters

It should be possible to query many addresses at once using bloom filters. This would require further development of the insight db to make this possible. In a nutshell you would need an index on every bit of the bloom filter to be able to quickly query the addresses in the filter.

This may be possible for new mempool transactions, but the indexes would likely need to be updated to support this at the database level to be able to query the history.


Transcription output

Hi,
Good paper! I'm trying to run your trained model and want to get some transcriptions. However, I find it difficult to save the transcriptions to a file so that I can do some research. Could you please help me with that?
Many thanks,
Zhaofeng

Hi,
Thanks for your interest in the paper.
Are you trying to transcribe a list of audio files?
This should be easy to do by adding a "transcribe" function to "AudioEfficientConformerInterCTC", "VisualEfficientConformerInterCTC" and "AudioVisualEfficientConformerInterCTC" in models_zoo.py similar to what is done in the NeMo toolkit.
The function could take the list of audio file paths as argument, return a list of transcriptions.
You could then use this function to transcribe your data and then save them to a text file.

Hi,
Thanks a lot for your suggestion. I will try that!
Many thanks


connection-pool-<IP_ADDRESS> doesn't compile

Citing from http://hydra.cryp.to/build/1183547/nixlog/3/raw:
src/Data/ConnectionPool/Internal/Streaming.hs:126:29:
    Constructor ‘ClientSettings’ should have 4 arguments, but has been given 3
    In the pattern: ClientSettings port host addrFamily
    In an equation for ‘acquireTcpClientConnection’:
        acquireTcpClientConnection (ClientSettings port host addrFamily)
          = getSocketFamilyTCP host port addrFamily

Package streaming-commons changed some of its data types and code of this library had to be updated accordingly, but those new fields aren't used. Plan is to include that functionality in to future release.
Release with this fix is available on Hackage: http://hackage.haskell.org/package/connection-pool-<IP_ADDRESS>


RP2040 PIO?

This is library support programmable IO on the RP 2040? I am looking for a library that specifically supports this so that I don't have to have a lot of CPU dedicated to driving LEDs.
It's unclear whether the micro python core library for neopixel, supports PIO
https://github.com/micropython/micropython-lib/blob/master/micropython/drivers/led/neopixel/neopixel.py
Thanks!

This library uses PIO as the main way to send data out to leds, but some code is still executed on the cpu (like pixel assignment and operations on pixels).

Thanks! Can you point to where the PIO stuff is in the code? I'm just curious to learn more about it.

These lines include the PIO program used to generate bitstream for LEDs. Here the state machine is initialized. Finally, this is the code used to send data from python to PIO. In PR #20 there was also some work done to rewrite the PIO program so we don't need sleep function inside the python, but it's not completely verified.

Thank you for that clarification! Really helpful to see where in the code this happens.


Date Range not working on mobile screens in web

Describe the bug
When range is set for the component (it works fine on desktop web), and is open on mobile screen then the range doesn't work and it returns same date for start and end date.
Expected behavior
Different ranges should be allowed to select even for mobile screen,
Desktop & mobile (please complete the following information):

Browser: chrome (mobile version)
Library version 9.0.1

Caused by the same issue reported in #948


exchange-request-policy saves last access time, not last time of network request

urql version & exchanges:
"urql": "^2.0.3"
"@urql/core": "^2.1.1"
"@urql/exchange-request-policy": "^0.1.2"
Steps to reproduce
Switch between two pages faster than the TTL
Expected behavior
Queries don't trigger shouldUpgrade (and subsequently a network request)
Actual behavior
Queries should trigger shouldUpgrade after TTL has been expired based on last network request, not after last access of cached data
Reproduction
https://codesandbox.io/s/vibrant-bird-5pi8t?file=/src/index.js
Open the console and use the toggle button faster than every two seconds and "shouldUpgrade" won't show in the console. Wait for two seconds and then toggle, then you will see "shouldUpgrade".
It will still not make a network request, but that is handled in this issue: https://github.com/FormidableLabs/urql/issues/1334

I wouldn't quite classify this as a bug, but rather as a change request maybe 🤔 I do think this kind of fits nicely into our bigger thoughts around merging the requestPolicyExchange with the refocusExchange and making a larger more featureful replacement for both that handle more of these edge cases.
I think in some cases it's very desireable actually, to have it use the last accessed time rather than last received time, but I think this will need more thought put into it rather than just switching it over potentially.

With the current default TTL of 5 minutes, some queries might never reload.
I can't actually come up with a use case where last accessed time for upgrading to a network request is the preferred behavior.
With the current setting while actively using the software, data will stay stale. Only when becoming inactive and active again, data will be refreshed.
I can only see a benefit when having very low TTLs. But since we can only define a global TTL and not per query, I think TTLs will probably be higher.


Annotate unused exports

Resolves https://github.com/Codex-/knip-reporter/issues/8
@Codex- feel free to edit the pull request if needed, can be squashed also to one commit.
Version number comes from my fork, can be different. I waited for knip v3 support and rebased my previous implementation on top of today's main branch.

Thanks for this! I'll take a look when I can :)


git-bug: change upstream source to git-bug/git-bug

Description of changes
git-bug has moved into the git-bug organization. This change updates the fetchFromGitHub call to fetch directly from git-bug/git-bug instead of relying on what is now a 301 redirection (that lives only at GitHub's discretion).
Things done

Built on platform(s)

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

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

[ ] sandbox = relaxed
[ ] sandbox = true

[x] Tested, as applicable:

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

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

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

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

verified redirect and ran nom-build . -A git-bug.src --check