text:
Support Oci 1.0

Issue #, if available:
closes #339
Description of changes:
Support OCI 1.0
SOCI relies on being able to associate an index with an image. This
capability was introduced in OCI distribution and image specs version
1.1 as Artifacts and the Referrers API respectively.

In order to drive adoption, an OCI 1.0 compatible fallback was added
that encodes artifacts as Image Manifests and stores the Referrers API
content in an Image Index.

This PR adds the ability to serialize and deserialize SOCI indices as
either OCI Artifacts or OCI Images. There is no automatic OCI 1.0
fallback when creating images. The user of the CLI/library must
explicitly request an OCI 1.0 compatible Image Manifest. The snapshotter
will be able to automatically load a SOCI index in either serialized
form.

Testing performed:
make check && make test && make integration
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

This is probably ready for review, but it needs to be rebased after https://github.com/awslabs/soci-snapshotter/pull/350

Just want to confirm that I understand what this PR does.  Currently soci supports and relies oci 1.1 artifact types, this PR adds support for both CREATING and READING oci 1.0 image types.
The meat of the pr is in the changes to soci_index.go.  Where as the creating and reading the index used happen directly with JSON package, there are now abstractions that allow us to inject support for different manifest types.  Adds the following functions

func DecodeIndex(r io.Reader, index *Index) error: for reading from an io.Reader
func UnmarshalIndex(b []byte, index *Index) error : for reading from a byte array
func (i *Index) Marshal() ([]byte, error): for creating the file from an index object

Within these functions the logic splits out between 1.0 and 1.1 For reading it checks whether the media type is an artifact (1.1) or an image (1.0).  If it is type 1.0 it calls a helper function to add fields to make it feel and act like a 1.1 artifact.  For building it relies on a new flag called legacy-registry.  If this is present is builds a 1.0 style soci index.  This flag has been plumbed through.
I haven't had a chance to go through all the tests.  What do they do?
Anything choices that were tricky while making this PR?  Or full steam confidence all the way?

On the testing side looks like you test both cases for marshall in TestMarshalIndex in soci_index_test.go and for creation you added TestLegacyOCI in push_test.go.  All the other test updates were to use the new abstractions.  Correct?

@Kern-- I merged #363 which changes to use defaultMinLayerSize instead of 0 in buildIndex. Just FYI in case you use it and rely on the previously default 0 minLayerSize.

Just want to confirm that I understand what this PR does.

Yes. I don't want to quote your whole explanation, but it is correct.

I haven't had a chance to go through all the tests. What do they do?

Your later comment implies you did check this, but just to confirm,
TestMarshalIndex verifies that we can marshal both OCI Artifacts and OCI Image Manifests. The most important piece here is that we remember which type was serialized - if we serialized as a Manifest and read it back as an Artifact, then a subsequent marshalling as an Artifact would change the digest and likely break a bunch of stuff. (e.g. in the snapshotter where we re-serialize the manifest to store on disk for later container launches).

Anything choices that were tricky while making this PR? Or full steam confidence all the way?

I think the choice of "legacy-registry" as the CLI flag is the most contentious. There's still discussion on the OCI Image spec about whether they should require OCI 1.0 Manifest compatible artifacts by default or if 1.1 Artifacts will go away entirely. I think we can still change this flag later, but we should be thinking about versioning soon and what sort of backwards compatibility we will provide.

authors: Kern-- djdongjin sbuckfelder

repo: awslabs/soci-snapshotter


text:
lr_scheduler seems to be reset if training is resumed

Hi,
if training is resumed the learning rate scheduler seems to be reset.
This seems to be the case because the class OptimizerConfig contains the learning rate scheduler both directly in lr_scheduler and also in the dict params, and the module.init_optimizer function relies on the dict OptimizerConfig.params but not on OptimizerConfig.lr_scheduler.
But here:
https://github.com/awslabs/sockeye/blob/da518f1c6e90e08e2a1f8d2888608121f75b3d67/sockeye/training.py#L989-L993
only the lr_scheduler is updated but not the params dict.
A quick fix might be adding
self.optimizer_config.params['lr_scheduler'] = self.optimizer_config.lr_scheduler
before
https://github.com/awslabs/sockeye/blob/da518f1c6e90e08e2a1f8d2888608121f75b3d67/sockeye/training.py#L993
But overall it looks dangerous to have the learning rate scheduler both in lr_scheduler and in the dict params within the class OptimizerConfig.

Hi @julian90, thanks for submitting this issue! This is clearly a bug and I agree about the double reference to the scheduler instance in OptimizerConfig.
Does this change fixes the problem for you?

source: gharchive/issue

repo: awslabs/sockeye

license_type: permissive

license_source: bigquery


text:
Invalid parameter passed error for ReceiveMessageRequest when testing with elasticmq - SQS 3.0.0-M2

Type: Bug
Component: SQS

Describe the bug
When using @SqsListener and elasticmq for testing with standard queue, the listener doesn't fetch messages and throws an error, "Value  for parameter ReceiveRequestAttemptId is invalid. The request include parameter that is not valid for this queue type...".
CreateRequest() method in SqsMessageSource.java sets this property for both FIFO and standard queues but this field only applies to FIFO queues.
From the docs:
--receive-request-attempt-id (string)

This parameter applies only to FIFO (first-in-first-out) queues.

Just to clarify this a bit, both AWS and LocalStack APIs do not complain about this parameter, so it was left for standard queues as well to reduce overall complexity.
Also, the docs state it doesn’t apply, not that it’s prohibited and should throw an error.
But since the elastic mq API does complain, I think that’s reason enough to change this and remove the parameter for standard queues.

@magna25 feel free to submit a PR. Since we work in tests with Localstack this is not a high priority for us.

Fixed in #586

authors: maciejwalkowiak magna25 tomazfernandes

repo: awspring/spring-cloud-aws

license_source: github-api


text:
AWS Spring cloud map support (with AWS SDK v2)

Support for integrating with AWS Cloudmap
:loudspeaker: Type of change

[ ] Bugfix
[x] New feature
[ ] Enhancement
[ ] Refactoring

:scroll: Description

This pull request adds support for integrating spring boot application with AWS cloudmap. Here is an example of how an simple properties file integration looks like for both cloudmap registration and discovery
spring.cloud.aws.cloudmap.region=us-east-1
spring.cloud.aws.cloudmap.enabled=true
spring.application.name=cloudmap-namespace-here

# Discover existing cloudmap instances
spring.cloud.aws.cloudmap.discovery.failFast=false
spring.cloud.aws.cloudmap.discovery.discoveryList[0].service=TestService
spring.cloud.aws.cloudmap.discovery.discoveryList[0].nameSpace=ECS-CloudMap

# Register new instance
spring.cloud.aws.cloudmap.registry.description=Namespace for sample cloudmap registry service
spring.cloud.aws.cloudmap.registry.port=80
spring.cloud.aws.cloudmap.registry.service=a-service
spring.cloud.aws.cloudmap.registry.nameSpace=a-namespace

The property file is optional, any application can easily register themselves to cloudmap by adding spring-cloud-starter-aws-cloudmap dependency to pom or gradle files, here is a example:
<dependency>
  <groupId>io.awspring.cloud</groupId>
  <artifactId>spring-cloud-starter-aws-cloudmap</artifactId>
</dependency>

:bulb: Motivation and Context

Adds support for cloudmap integration with spring boot applications for both service registry and discovery #5
:green_heart: How did you test it?
I executed the following tests:

Ran unit test cases and made sure nothing failed
Deployed the sample spring boot app checked in part of this pull request in ECS, EKS fargate instances. The application could successfully discover and register the application to AWS cloudmap.

:pencil: Checklist

[x] I reviewed submitted code
[x] I added tests to verify changes
[x] I updated reference documentation to reflect the change
[x] All tests passing
[x] No breaking changes

:crystal_ball: Next steps
Code review and merging code to 3.x branch

Thanks @hariohmprasath. I'll do some polishing and very likely come back to you with some questions. In meantime, there are 3 things missing:

reference documentation
infrastructure for running a sample - or an instruction how to run the sample (I guess it's not possible to run it with Localstack)
nullability annotations & package-info.java.

There are quite a few unused fields that I am not sure if just should be deleted or some parts of implementation is still missing.
Missing integration tests stopped me from doing further refactoring. If we can't test against Localstack, we should mock AWS API and perhaps use Wiremock to stub EC2/ECS endpoints.
I feel like the CloudMapUtils class is the center of this implementation and ideally we would refactor it to avoid having so much logic in the util class - but this can or even has to wait until we have integration tests so that we can refactor safely.
@hariohmprasath would you be willing to address these issues? In case I am missing something, your opinion is appreciated.

Thanks for reviewing the code @maciejwalkowiak, let me start addressing some of the comments and we can sync up based on the changes

Reference documentation added, package-info with nullability annotation added, no infrastructure required if cloudmap namespace or service doesnt exist the cloudmap connector module will automatically create them

There are quite a few unused fields that I am not sure if just should be deleted or some parts of implementation is still missing.
Missing integration tests stopped me from doing further refactoring. If we can't test against Localstack, we should mock AWS API and perhaps use Wiremock to stub EC2/ECS endpoints.
I feel like the CloudMapUtils class is the center of this implementation and ideally we would refactor it to avoid having so much logic in the util class - but this can or even has to wait until we have integration tests so that we can refactor safely.
@hariohmprasath would you be willing to address these issues? In case I am missing something, your opinion is appreciated.

Thanks for reviewing the code @maciejwalkowiak, let me start addressing some of the comments and we can sync up based on the changes

@maciejwalkowiak, The last commit that I pushed in has code changes to mock the required HTTP responses. So we can use these tests as a reference for further refactoring. Since CloudMap is not supported in CloudMap you may need to connect with AWS using credentials to run this sample.
It just requires the following environment variables to be set before running the sample application:
AWS_ACCESS_KEY_ID=<key>
AWS_REGION=us-east1
AWS_SECRET_ACCESS_KEY=<secret>
DEPLOYMENT_PLATFORM=ECS

Update CloudMapUtils.getEcsRegistrationAttributes(), comment out line between 536 to 547 and return hard-coded ipAddress and vpcId, this is all you need to pretty much to run this sample.

@hariohmprasath thanks for an update. We still need to have an integration test that checks everything all together. Something like ParameterStoreConfigDataLoaderIntegrationTests - does not need to use SpringApplication, can just use Spring testing framework capabilities, but it has to give us confidence that when details change, the integration still works.
Considering it's not possible to use Localstack for that, either we need to mock responses from AWS or run the test against real AWS and spin up resources with Cloudformation. I can imagine this is quite a bit of work but we just cannot merge the integration lacking solid test coverage.

@hariohmprasath thanks for an update. We still need to have an integration test that checks everything all together. Something like ParameterStoreConfigDataLoaderIntegrationTests - does not need to use SpringApplication, can just use Spring testing framework capabilities, but it has to give us confidence that when details change, the integration still works.
Considering it's not possible to use Localstack for that, either we need to mock responses from AWS or run the test against real AWS and spin up resources with Cloudformation. I can imagine this is quite a bit of work but we just cannot merge the integration lacking solid test coverage.

Hi @maciejwalkowiak,
Thanks for reaching out to localstack team regarding the support. I had a chance to catch up on their response and based on that I have submitted an enhancement (https://github.com/testcontainers/testcontainers-java/issues/5838) + PR (https://github.com/testcontainers/testcontainers-java/pull/5839) to support AWS CloudMap  for localstack module in testcontainers project.
Once the enhancement and PR gets approved I can use the same to add the required integration test cases. Hope this works for you, let me know your thoughts. Thanks

@hariohmprasath sounds like the way to go!

Hi @maciejwalkowiak,
I have added integration tests to test service discovery and registration for both the platforms (ECS and EKS).

EcsCloudMapIntegrationTest.java - Integration tests for ECS platform
EksCloudMapIntegrationTest.java - Integration tests for EKS platform

Note: Since CloudMap service is only enabled for pro version of LocalStack make sure to create an API Key (either using trial mode or buying a subscription), update the key in IntegrationTestUtil.LOCAL_STACK_API_KEY variable before running the integration tests.

Hopefully this should make things easier for testing, let me know if you want me to update anything. Thanks and appreciate your support for this PR.

Hi @maciejwalkowiak, Just checking to see whether you had a chance to review the changes, let me know if you have any questions/suggestions. Thanks

@hariohmprasath not yet unfortunately but it's still high in my priority list so don't worry - it won't be ignored :-)

Hi @maciejwalkowiak,
Hope you are doing great. Any tentative timeline when this support will be released? Thanks

@hariohmprasath apologies again, but we didn't find enough time to include it in 3.0.
3.0 will be released in April, CloudMap is planned for 3.1, so Q2/Q3 2023.

Sounds good, thanks for letting me know

Hi @maciejwalkowiak, Would love to get this merged by early 2024 :)

We are interested in using this integration as well. What needs to be done to get this reviewed and merged, and how could we help with that process?

Hi @maciejwalkowiak, The PR was created on Sep 4, 2022, probably 2 years back :) Any plans to merge it part of a mainline or release?

+1

Again apologies for postponing it for so long. I'll get some support and we will get it through.

source: gharchive/pull-request

authors: Vostan hariohmprasath maciejwalkowiak zampettim


text:
Potential application deadlock when handling EAGAIN?

If an application attempts to submit an sqe using io_uring_enter(), it's possible that EAGAIN may be returned:
EAGAIN
The kernel was unable to allocate memory for the request, or otherwise ran out of resources to handle it.
The application should wait for some completions and try again.

The application may then attempt to handle this EAGAIN as recommended by the man page by calling io_uring_enter() but this time with to_submit=0 and with min_complete=1 in an attempt to flush the cq ring.
However, what if this was the very first sqe submitted by the application, so that there are no cqes inflight or available to be flushed when calling io_uring_enter() with min_complete=1? Would this not result in an application deadlock?
What's the best way to handle EAGAIN?

Just to clarify the main point here:
EAGAIN could also be caused by another component of the system, outside of io_uring, so that the man page's advice of "wait for some completions and try again" could actually result in deadlock if there are no inflight requests in the io_uring instance.

Just to clarify the main point here:
EAGAIN could also be caused by another component of the system, outside of io_uring, so that the man page's advice of "wait for some completions and try again" could actually result in deadlock if there are no inflight requests in the io_uring instance.

That's certainly true, it could be outside of io_uring hands at that point. Generally io_uring tries to ensure that we can always make forward progress, at least in terms of requests. The man page is a bit outdated in that sense.
That said, if the system is driven way out of resources, most kernel APIs end up being unreliable in the sense that you can get spurious -ENOMEM. That's really not something specific to io_uring, and there's sadly not too much that can be done about it. In practice, the kernel tries very hard to allocate data for operations, so you'd only really run into this if the system is run into the ground anyway.

That's certainly true, it could be outside of io_uring hands at that point. Generally io_uring tries to ensure that we can always make forward progress, at least in terms of requests. The man page is a bit outdated in that sense.
That said, if the system is driven way out of resources, most kernel APIs end up being unreliable in the sense that you can get spurious -ENOMEM. That's really not something specific to io_uring, and there's sadly not too much that can be done about it. In practice, the kernel tries very hard to allocate data for operations, so you'd only really run into this if the system is run into the ground anyway.

Thanks @axboe!

Thanks @axboe!

authors: axboe jorangreef

repo: axboe/liburing

license: mit


text:
issue regarding latest changes

Hi @axelmohnen
getting a few errors upon updating to latest commit.

also this table does not exist, in class Z2UI5_CL_TOOL_APP_SHLP_GEN
DATA: lt_dd07v  TYPE dd07v_t,

maybe dd07v_tab is the same ?? dont really know..

as of latest pull from a2ui5, client is not passed anymore to factory methods, and need to be removed from caller.

in class:Z2UI5_CL_TOOL_APP_VH_GEN
lines: DATA(lr_popup) = z2ui5_cl_xml_view=>factory_popup( ir_client ).
as in other factory methods in this implementation.
im running on abap 7.50 on-prem, btw if thats relevant i suppose.

i can try PR wlth fixes if thats ok by you

Hi @choper725,
I will have a look.... and provide an update soon.
Thanks,
Axel

Hi @choper725,
I issues should be fixed now.
I added a new demo app "Z2UI5_CL_TOOL_APP_12" in order to demonstrate the new "IV_USE_DEEP_SHLP" parameter.
The "deep search" is fully functional. In case the DDIC searchhelp contains search fields where the corresponding data element has a DDIC SHLP maintained or the corresponding domain has some fix values maintained, than if the "IV_USE_DEEP_SHLP" parameter is flagged it will open another generic SHLP or generic value help.
Just give it a try :-)
Thanks,
Axel

thx @axelmohnen  ill check it ou!

hi @axelmohnen
still getting error on views creation methods, regarding latest a2ui5 version

Hi @choper725,
I removed all erroneous factory calls, due to the latest 2UI5 version, from the demo apps.
I don't have the latest 2UI5 version in our system yet. That's the reason why I don't have the error....
The demo12 is working, but it was probably not a good example.
Explanation:
Demo12 was using searchhelp "H_T002". This searchhelp has the field "SPRAS" with data element "SPRAS". Data element "SPRAS" has the searchhelp "H_T002" assigned. This is exactly the same searchhelp. This means, for you it looks that you have to click twice.
I added now the company code searchhelp "H_T001_ME" to demo12. This has the field "BUKRS" and the data element "BUKRS".
The data element "BUKRS" has the searchhelp "C_T001" assigned.

ohh i see, thats why double clicking..
great ill check those !!
btw even in older versions client is not mandatory to pass to the view functions

table T001 does not exist in NPL / A4H MiniSAP, pull fails

Hi @AndreaBorgia-Abo,
could you please retry. I replaced the table t001 in all demos.

Pull now works, super fast, thanks.

authors: AndreaBorgia-Abo axelmohnen choper725

license: MIT


text:
Improved Client and Adapter creation

This updates the package to use a single constructor for the Client and adapter/* types. Configuration is now retrieved from the environment if not specified otherwise. This rougly matches what the AWS SDK does. This reduces a lot of code duplication and confusion we had in place for supporting Axiom Cloud and Selfhost.

@tola: Please check if you need to update the documentation. Would also love if you could check the *.md files for spelling or stlye mistakes in this PR.

LGTM, but I'll move it onto @mhr3's plate for a proper review :)

authors: lukasmalkmus njpatel

repo: axiomhq/axiom-go


text:
XIVY-13138 establish inscription and ivyscript ws connection in node backend

WebSocketForwarder inspired by https://github.com/eclipse-glsp/glsp-theia-integration/blob/master/packages/theia-integration/src/node/websocket-connection-forwarder.ts

@martin-fleck-at, you might find time to check whether this WebSocket forwarding solution is sufficient for our case. Many thanks

Nice work! Is it now possible to debug this messages via this vscode extension? https://marketplace.visualstudio.com/items?itemName=typefox.vscode-messenger-devtools

I see the handlers in the debug view but not the events. I will check that ;)

repo: axonivy/vscode-extensions


text:
Obtain the graph create by process

Hi,
first of all thanks for the project. I would suggest to make possible for a user to have the graph back. For example, once you call set_output and subsequently process you can store the png generated by the libraries. I would like to not be forces to set the output and maybe just call get_graph and obtain the graph returned by the process function. Is it already possible?
Thanks

Hi! Wasn't sure which is your problem, so I have multiple answers:

If your problem is that the output of the plot_xxx functions in visualize.py are png files:

you can change that by specifying a format='dot', or format='raw' parameter, to produces layouted or raw dot files.

If you want to have access to the internal graph used by bingraphvis without plotting to a file:

You can access it multiple ways, the heart of the Vis object is the VisPipeLine which handles all the components of the library (source, annotators, content, transformers), except the Output.
So you can access the graph like this:
vis = AngrVisFactory().default_cfg_pipeline(cfg)
vis.add_transformer([...])
graph = vis.pipeline.process()

or you can setup the pipeline in a standalone way:
vp = VisPipeLine()
vp.set_source(AngrCFGSource())
vp.add_content(AngrCFGHead())
graph = vp.process()

Can you share me your usecase, why you need the internal graph?
I'm asking this, because I have plans to change this part of the code in the future, so if you base anything on the internal graph representation, probably you will need to refactor your code later. But if I know how you use it, I can take care when doing the changes, that I don't remove support for your usecase.

thanks @axt , very nice answer. I think I would go for the latter solution... In my case I need it because I would like to have an "interactive" graph maybe using d3.js or in general it would be useful to anyone that wants to store/use the graph in another way and not just "see" it.
Thanks again

Originally I planned the  Output component for this. It gets called with the result of the processing pipeline, and handles it any way it wants. So for example, one could create an InteractiveOutput class, what could be used instead of DotOutput, and would open a graphical display and render the graph into it. (I admit, that this desing has limitations, and for exampe its especially bad for interacting with 'd3.js')
Creating an interactive display is a challenging task. Most of the bingraphvis structure/API is created for the basic usecase of creating non-interactive graphs. If you manage to build something usable on top of bingraphvis I can adapt the API of it to support your needs.
I also advise you to check https://github.com/angr/angr-management, before writing you own interactive display, @ltfish added a lot of nice features to it (check this screenshot):

Thanks @axt , I'll have a look on the project you suggested.
Anyway, would not be better to have a different class for each output type you want to create? So a user would just need to call set_output(DisideredFormat()) and it would be done... Isn't possible?
Thanks

Just saw that you updated the previous comment. Yes its correct that way, but I would advice you to call preprocess on vis.pipeline instead of on vis. At the moment they do the same, but it can happen that the vis objects functionality changes in the future and that can introduce some incoherence if you call the prepocess of the outer object, and then the process of the inner.
vis = AngrVisFactory().default_cfg_pipeline(cfg)
vis.pipeline.preprocess(cfg.graph)
g = vis.pipeline.process()
g.nodes

Not sure I understand the question about the output. It works that way you described, you can create your own class, and then use `set_output(YourOutput())`.

All solved for now.
Thanks

repo: axt/angr-utils


text:
Error when open an empty file

Version confirmation

[X] Confirm

Following prerequisites

[X] Confirm

Neovim version
NVIM v0.9.0
Operating system/version
Win10 22H2 19045.2728
Terminal name/version
nvim-qt
$TERM environment variable
No response
Branch info
main (Default/Latest)
Fetch Preferences
SSH (use_ssh = true)
How to reproduce the issue
Open the file with nvim-qt.
Expected behavior
no error
Actual behavior

Additional information
When the file name contains "{", the error will occur.

what kind of devious ppl will put '{}' in their path name.

null-ls.nvim should be responsible for handling this, please open an issue in the upstream repo.

what kind of devious ppl will put '{}' in their filename.

I just kept my keepassxc password in the filename, and I tried to open the file with nvim-qt. That's why I found the error.

I just kept my keepassxc password in the filename, and I tried to open the file with nvim-qt. That's why I found the error.

never heard of keepassxc b4. looks interesting!

never heard of keepassxc b4. looks interesting!
That is a password management software that is open source and localized, worth a try.

close for it's about upstream

authors: CharlesChiuGit Jint-lzxy lentikr

repo: ayamir/nvimdots


text:
Create RELEASE.md

Created initial release file (#10)

Hi @Jaspreet099 Awesome start! 🚀

repo: ayoayco/astro-reactive-library


text:
fix: fixes runtime errors in non typescript-eslint projects

Description
Some runtime errors happen in projects that do not user typescript-eslint parser.
For example, decorators are not detected (and the decorators property will not exist on nodes, even though typescript-eslint types will say it necessarily exists).
This PR fixes them and adds for each rule some basic tests to ensure that the rule works fine in a non-typescript environment, using eslint's Rule Tester rather than typescript-eslint's Rule Tester.

[x] Bug fix

Awesome, thanks a lot!

repo: azat-io/eslint-plugin-perfectionist


text:
Investigate and fix if time: java.lang.UnsupportedOperationException: empty.reduceLeft

View details in Rollbar: https://rollbar.com/Azavea/RasterFoundry/items/927/
Traceback (most recent call last):
  File "LinearSeqOptimized.scala", line 137, in reduceLeft
  File "List.scala", line 84, in reduceLeft
  File "TraversableOnce.scala", line 208, in reduce
  File "Traversable.scala", line 104, in reduce
  File "Mosaic.scala", line 245, in apply
  File "Mosaic.scala", line 238, in apply
  File "Option.scala", line 146, in map
  File "OptionT.scala", line 29, in apply
  File "OptionT.scala", line 29, in apply
  File "Try.scala", line 237, in apply
  File "Try.scala", line 192, in apply
  File "Try.scala", line 237, in map
  File "Future.scala", line 237, in apply
  File "Future.scala", line 237, in apply
  File "Promise.scala", line 32, in run
  File "ExecutionContextImpl.scala", line 121, in exec
  File "ForkJoinTask.java", line 260, in doExec
  File "ForkJoinPool.java", line 1253, in pollAndExecAll
  File "ForkJoinPool.java", line 1346, in runTask
  File "ForkJoinPool.java", line 1979, in runWorker
  File "ForkJoinWorkerThread.java", line 107, in run
java.lang.UnsupportedOperationException: empty.reduceLeft

Likely caused when trying to run a tool on a project without any scenes

repo: azavea/raster-foundry


text:
Produce signed URLs for S3 interactions for vsicurl

Right now vsicurl interactions with S3 depend on direct HTTP (not HTTPS, and not via S3 protocol) access to scratch files. The requires the scratch space buckets for be world readable. In order to continue using vsicurl, these URLs need to be signed and the bucket made non-world readable.
This is somewhat tied to https://github.com/azavea/raster-foundry/pull/239. Ensure that the changes there are undone as part of resolving this issue.

We are unable to generate a signed URLs for private S3 resources using boto3 for both GET and HEAD requests which is needed by the vsicurl driver.
The solution is to set CPL_VSIL_CURL_USE_HEAD to NO when opening files in GDAL (See: http://gdal.org/python/osgeo.gdal-pysrc.html#SetConfigOption).

authors: hectcastro kdeloach


text:
Bug in parsing higher-order infix operators.

Environment

Millet version: 0.14.7-1 (from archlinux user repository)
Editor version: NVIM 0.10.2
OS version: Archlinux x86_64 Linux 6.11.8-zen1-2-zen

Steps to reproduce
Write something like:
fun println s =
  (print s; print "\n")

infix 0 |>
fun (a: 'a) |> (b: 'a -> 'b) = b a

val () = "hello" ^ " " ^ "world" |> println

Expected behavior
It passed type check of both SML/NJ and MLton:

Actual behavior
However, Millet reported an type error. This is likely a bug on parsing.

i cannot reproduce with your code example where |> and the usage of |> are in the same file. but i can reproduce if |> is in a different file and i import it. i think it's likely that |> is in scope, but the infix-ness of |> is not in scope.
you can do two things:

put:
[language]
fixity-across-files = true

in your millet.toml and restart millet. this will allow importing fixities but will also possibly make millet slower, since it has to do more work to correctly track all the fixity environments across files.

in each file you use the infix op, re-declare the fixity of it. in your example that would mean putting infix 0 |> (or the equivalent, shorter infix |>) at the top of each file you import |> into.

improve docs in b590b18e9637be9a63897f71eaa61029bba4b880 and c78f916db270e47951198e2f4e3fad10b8dee024

authors: MizurenNanako azdavis

repo: azdavis/millet


text:
feat(io-stream): add getStream() method to access underlying stream

Signed-off-by: azjezz azjezz@protonmail.com

Pull Request Test Coverage Report for Build 1457205528

0 of 2 (0.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.06%) to 99.938%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/Psl/File/Internal/AbstractHandleWrapper.php
0
2
0.0%

Totals

Change from base Build 1446232382:
-0.06%

Covered Lines:
3209

Relevant Lines:
3211

💛  - Coveralls

authors: azjezz coveralls

repo: azjezz/psl


text:
How to restart a work flow  with old timestamp? How work flow get the schedule time?

A  flow is scheduled with starting time  1:00 Am and repeated 1hour。
The flow is launched  at time  1:00  , 2:00 3:00  and it  can get the schedule time by start time.
If  a flow  failed  at 2:00  will be relaunched  manually at some times(eg.  5:00)， the flow get the start-time not 2:00 but 5:00 .
How work flow get the schedule time?

Hi @superwood , I can not understand what you mean by relaunched manully

@superwood ,i think @superwood will expect executions saved startTime.
eg,
The execution failed at 2:00,the execution relaunched at 5:00 will auto set start-time=2:00 but 5:00

authors: fsi206914 superwood wangqiaoshi

repo: azkaban/azkaban


text:
Add support for thin archives on web and executor server

Thin archives allow project zips to include a /app-meta/startup-dependencies.json file that specifies JAR dependencies that the project's flows need to be able to run. These dependencies no longer have to be bundled in the zip, significantly reducing its size.
These dependencies will be downloaded from a configurable origin during post-upload processing on the web server, then persisted to storage. When preparing a flow for execution, the dependencies specified in the project's startup-dependencies.json file will be downloaded from storage.
In addition, support has been added for ProjectValidatorCacheable, a new specification of a validator that can generate a cacheKey for a thin project. Files that have been deemed to be VALID or needing to be REMOVED can be indicated as such in a new validated_dependencies db table. Thus files that have already undergone validation do not need to be revalidated on future uploads.
See comment here for detailed description of thin archive processing on web server and how cache keys (validation keys) work: https://github.com/azkaban/azkaban/blob/fc5fd8d05007323d9fe14dd3a581cb60ee722f09/azkaban-common/src/main/java/azkaban/project/ArchiveUnthinner.java#L48-L80

Pull Request Test Coverage Report for Build 4872

560 of 683 (81.99%)  changed or added relevant lines in 36 files are covered.
2 unchanged lines in 1 file lost coverage.
Overall coverage increased (+0.9%) to 39.757%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

az-core/src/main/java/azkaban/utils/HashUtils.java
40
41
97.56%

azkaban-common/src/main/java/azkaban/utils/StorageUtils.java
4
5
80.0%

azkaban-exec-server/src/main/java/azkaban/execapp/FlowRunnerManager.java
7
8
87.5%

azkaban-spi/src/main/java/azkaban/spi/DependencyFile.java
12
13
92.31%

azkaban-spi/src/main/java/azkaban/spi/ProjectStorageMetadata.java
0
1
0.0%

azkaban-web-server/src/main/java/azkaban/webapp/servlet/ProjectManagerServlet.java
0
1
0.0%

azkaban-common/src/main/java/azkaban/metrics/CommonMetrics.java
2
4
50.0%

azkaban-common/src/main/java/azkaban/project/validator/ValidationReport.java
19
21
90.48%

azkaban-common/src/main/java/azkaban/utils/DependencyTransferException.java
4
6
66.67%

azkaban-common/src/main/java/azkaban/utils/FileIOUtils.java
1
3
33.33%

Files with Coverage Reduction
New Missed Lines
%

azkaban-common/src/main/java/azkaban/jobExecutor/AbstractProcessJob.java
2
55.81%

Totals

Change from base Build 4871:
0.9%

Covered Lines:
12590

Relevant Lines:
31667

💛  - Coveralls

authors: abagshaw coveralls


text:
Cloudflare blocking again

Hey! Setting this up, and it works great locally, even with headed. On GH action though, I'm running into a 403 Forbidden. Seems like Cloudflare may have updated their detection past checking for iframes? Any ideas?

hard to say, it's certainly possible that they're blocking github IPs... you could maybe pay for a vpn (or use a free one) then use a github action to connect to your vpn account before running the script?
if that works, I'd really appreciate a PR to update the README so that other users know to leverage that route.

repo: azoff/tockstalk


text:
🛑 Mining is down

In 27ba6b7, Mining (https://mining.uzumekiulee.repl.co) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Mining is back up in 4a26fb6 after 5 minutes.

repo: azrielbsi/monitor


text:
Create Backup Policy for SQLDatabase and SAPHanaDatabase

Issue-id
PR Checklist

[x] I have added example(s) inside the [./examples/] folder
[x] I have added the example(s) to the integration test list for normal (~30 minutes) or long runner >30 minutes
[ ] I have checked the coding conventions as per the wiki
[x] I have checked to ensure there aren't other open Pull Requests for the same update/change?

Description

Does this introduce a breaking change

[ ] YES
[x] NO

Testing
Tested inhouse

@iriahk89 Please help to review this PR.

It seems like we're dealing with an error from Terraform syntax for 'SAPHanaDatabase. I will make a ticket to ask support from Hashicorp. @iriahk89 @khaman-pet
protectionpolicies.ProtectionPoliciesClient#CreateOrUpdate: Failure responding to request: StatusCode=400 -- Original Error: autorest/azure: Service returned an error.
│ Status=400 Code="BMSUserErrorInvalidPolicyInput" Message="Input for create or update policy is not in proper format. Please check format of parameters like schedule time, schedule days, retention time and
│ retention days

thanks for the PR @leethanh2112 and thanks for the review @iriahk89!

repo: aztfmod/terraform-azurerm-caf


text:
Typo : August string : "Aud" => "Aug"

August typo :"Aud" => "Aug"
https://github.com/azure-rtos/netxduo/blob/72dcde94184b9996894c4be3b4a5cafb2b448100/addons/sntp/nxd_sntp_client.c#L4909

Hi @DoudFPV Much thanks for reporting this issue to us, we will fix it.

Fixed it in 6.2.0 https://github.com/azure-rtos/netxduo/releases/tag/v6.2.0_rel

authors: DoudFPV bo-ms

repo: azure-rtos/netxduo


text:
Validate container names

This should close #102
Validates container names with a regex.

@sedouard I killed the old PR and re-issued as the repo name change messed me up.  but this incorporates what @felixrieseberg requested and the message in the status.

Hey! Thanks so much - I apologize in advance, but I left you two more comments in the code. Those are the last ones from me, I promise :+1:

LGTM I think the modal is a better UX for this.

.vscode/settings.json was checked in - probably shouldn't be. but i overwrote as default VSCode is tabs and 4 as length.

@cicorias: That makes sense to me and is small enough that we can smuggle it in here :) I'll wait for the tests and will merge then!

had to fix the other spacing issue

@cicorias probably my fault. the vscode thing was my doing. we originally had the .settings but vs code moved it, so I just kept it in the repo

Wait though - tabSize should be 4. The settings file just changed, and so did the spacing here?

@felixrieseberg editorconfig has always been set to indent size = 2.

to confirm - 4 'spaces' - not tabs?  Not sure if there's a mix in play already.  i'll fix in the morning.

Whatever get's the job done - in the end, it should be four soaces to be consistent with the rest ;-)

@cicorias I think the vscode settings are consistent with whats in editorconfig (which is used by sublime). Our code mostly uses 4 space indents (which is 2 indents with the current settings), but sometimes there are 2 space indents hiding in there. I've opened https://github.com/azure-storage/deco/issues/344 to track the issue since I don't think you should have to worry about this neuance in this PR.

authors: cicorias felixrieseberg sedouard

repo: azure-storage/deco


text:
Support for Islamic Calendar

Have you thought about adding a Trait for the Islamic Holidays?

@TheAdnan Definitely thought about but not yet investigated. I'm not familiar with Islamic holidays how these could be added in a calculated way. Do you maybe have an idea or a good resource?
Cheers! Sacha

I did a bit of research, and I found these implementation for the Islamic (Hijri) calendar:

https://www.phpclasses.org/package/9435-PHP-Convert-and-manipulate-Hijri-dates.html

http://php.net/manual/en/ref.calendar.php#54234

Thanks! These are great resources. I'll have a look into that. I need to understand more about the Islamic calendars first :)

authors: TheAdnan stelgenhof

repo: azuyalabs/yasumi


text:
small improvements

Check the commits for details. tl;dr:

flake8 and black
python typing
multi stage docker build
Python 3.12

Not perfect, but good enough.

Thank you for the interest in the project. However, I do not believe this pull really improves the project.
There is no reason why replacing all single quotes with double quotes provide any benefit at all. Instead, it obfuscates the Git history, showing the name of the person doing formatting changes instead of the person who did the logic behind the code, making “git blame” less useful.
I recommend watching the “Beyond PEP 8 talk” by Raymond Hettinger: https://www.youtube.com/watch?v=wf-BqAjZb8M

Of course, this is your choice, still some things to consider:

The idea to replace these singled quotes with double ones, is not my choice, it's the choice of black, which is a Project of the Python Software Foundation. The talk you are referencing is 9 years old, black has been created 6 years ago and is the de-facto standard for code formatting in Python these days.
The docker image could not be build, as some packages (gcc / build-base) had been missing in the alpine Python image, adding these packages would grow the image to about 300MB, by switching to a multi stage build the image now is about 80MB.
I also did some type checks and introduced type hints, however: I know that some people don't like them.

:wave:

authors: encbladexp hprid


text:
docker build 出错

How is Anse deployed?
Docker
Describe the bug
使用 docker build . 创建镜像以后
使用 docker run --rm --name gemini_pro_chat -p 3030:3000 -e GEMINI_API_KEY="" -e HTTPS_PROXY="" gemini_pro_chat 命令进行 container 创建, 然后报错了
Starting service...
Running script...
node:internal/modules/esm/resolve:853
  throw new ERR_MODULE_NOT_FOUND(packageName, fileURLToPath(base), null);
        ^

Error [ERR_MODULE_NOT_FOUND]: Cannot find package 'send' imported from /usr/src/dist/server/entry.mjs
    at packageResolve (node:internal/modules/esm/resolve:853:9)
    at moduleResolve (node:internal/modules/esm/resolve:910:20)
    at defaultResolve (node:internal/modules/esm/resolve:1130:11)
    at ModuleLoader.defaultResolve (node:internal/modules/esm/loader:396:12)
    at ModuleLoader.resolve (node:internal/modules/esm/loader:365:25)
    at ModuleLoader.getModuleJob (node:internal/modules/esm/loader:240:38)
    at ModuleWrap.<anonymous> (node:internal/modules/esm/module_job:85:39)
    at link (node:internal/modules/esm/module_job:84:36) {
  code: 'ERR_MODULE_NOT_FOUND'
}

Node.js v21.4.0

Console Logs
No response
Participation

[ ] I am willing to submit a pull request for this issue.

运行这个 docker 也不行
docker run --rm --name gemini_pro_chat -p 3030:3000 -e GEMINI_API_KEY="" -e HTTPS_PROXY="" ghcr.io/babaohuang/geminiprochat:main

Starting service...
Running script...
node:internal/modules/esm/resolve:853
  throw new ERR_MODULE_NOT_FOUND(packageName, fileURLToPath(base), null);
        ^

Error [ERR_MODULE_NOT_FOUND]: Cannot find package 'send' imported from /usr/src/dist/server/entry.mjs
    at packageResolve (node:internal/modules/esm/resolve:853:9)
    at moduleResolve (node:internal/modules/esm/resolve:910:20)
    at defaultResolve (node:internal/modules/esm/resolve:1130:11)
    at ModuleLoader.defaultResolve (node:internal/modules/esm/loader:396:12)
    at ModuleLoader.resolve (node:internal/modules/esm/loader:365:25)
    at ModuleLoader.getModuleJob (node:internal/modules/esm/loader:240:38)
    at ModuleWrap.<anonymous> (node:internal/modules/esm/module_job:85:39)
    at link (node:internal/modules/esm/module_job:84:36) {
  code: 'ERR_MODULE_NOT_FOUND'
}

Node.js v21.4.0

现在的dockerfile应该可以了

repo: babaohuang/GeminiProChat


text:
Unnecessary extra tick

var foo = async () => {
  console.log(1);
  return (await 1) + 2;
}
foo();
console.log(2);

should transpile to:
var foo = function foo() {
  return new Promise(function (resolve) {
    console.log(1);
    resolve(1);
  }).then(function (_resp) {
    return _resp + 2;
  });
};
foo();
console.log(2);

which should log 1, then 2.
but instead transpiles to:
var foo = function foo() {
  return Promise.resolve().then(function () {
    console.log(1);
    return 1;
  }).then(function (_resp) {
    return _resp + 2;
  });
};
foo();
console.log(2);

This difference means the async function takes an extra tick - which results in logging 2, then 1.

Nice find, thanks for reporting.
There is the edge case of what to do with functions thrown before an await statement to take into account. It's some time ago I looked it up in the spec, but I think the correct behaviour is to make these too reject the promise instead of returning an error. That would make the total code required be something like this instead:
const PromiseChainStart = {
  then(func) {
    return new Promise(function (resolve, reject) {
      try {
        resolve(func());
      } catch (err) {
        reject(err);
      }
    });
  }
};

PromiseChainStart.then(function () {}
});

Doing it that way would also keep the code generation easier since there wouldn't be two return styles to handle (resolve/reject calls vs. return/throw).

@marten-de-vries it should reject the promise, and new Promise already has a try/catch, so no explicit one is needed.

I hadn't really thought of these semantics before, but curious: should 1 log before 2 if you aren't awaiting foo's call? I guess said another way, should there be a difference in logging the values if the code is:
foo();
console.log(2);

versus:
await foo();
console.log(2);

Apologies if this seems obvious, but I wanted to verify behavior.

Yes, the spec says that both examples should log 1 and then 2.

authors: eliperelman ljharb marten-de-vries

repo: babel/kneden

license: ISC


text:
Send env change token in tds when error abort transaction block

Description
Issues Resolved
[BABEL-4797]
Check List

[ ] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is under the terms of the Apache 2.0 and PostgreSQL licenses, and grant any person obtaining a copy of the contribution permission to relicense all or a portion of my contribution to the PostgreSQL License solely to contribute all or a portion of my contribution to the PostgreSQL open source project.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Pull Request Test Coverage Report for Build 8083666024
Details

0 of 6 (100.0%)  changed or added relevant lines in 2 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.003%) to 72.241%

Totals

Change from base Build 8046274338:
0.003%

Covered Lines:
40406

Relevant Lines:
55932

💛  - Coveralls


text:
skip fetch data from database

after search _id from documents are picked and a query is made to database that fill model for each record. is there way to prevent this? i only need data from elastic

before returning search result call "onlyDocuments" and data from elstic is returned and no query is executed towards database.

repo: babenkoivan/elastic-scout-driver-plus


text:
Migrate command fails

When I run php artisan elastic:migrate it imports everything then in console it returns:
All [App\Models\Product] records have been imported.
The products_index index was removed.

In Connection.php line 607:

  {"error":{"root_cause":[{"type":"index_not_found_exception","reason":"no such index","resource.type":"index_or_alias","resource.i
  d":"products_index","index_uuid":"_na_","index":"products_index"}],"type":"index_not_found_exception","reason":"no such index","r
  esource.type":"index_or_alias","resource.id":"products_index","index_uuid":"_na_","index":"products_index"},"status":404}

I have newest laravel version and use elasticsearch version 6.4.2

I am also stuck on this issue. I have followed the documentation and couldn't get the same result as you.

authors: berkayk muresanandrei

repo: babenkoivan/scout-elasticsearch-driver


text:
fetchby的编译报错消失了

版本0.8.86

知道了，没问题了

repo: babyfish-ct/jimmer


text:
🛑 SM Service is down

In f5c7895, SM Service (http://smservice.de) was down:

HTTP code: 0
Response time: 0 ms

Resolved: SM Service is back up in 521c405.

repo: bachmannschumacher/upptime


text:
🛑 SM Service is down

In e83c713, SM Service (http://smservice.de) was down:

HTTP code: 0
Response time: 0 ms

Resolved: SM Service is back up in c0cdfe6 after 12 minutes.


text:
Not able to fetch Shell script file containing ${#} | Reads as end of comment expected got end of file.

Expected Behavior
My contents directory contains a shell script file that has a line to calculate the length of the array as ${#Array[@]}.
My template directory tries to fetch it. It should be able to able to fetch this.
Actual Behavior
When it tries to fetch the content directory. It throws an error while trying to fetch the Shell Script from the content directory says, "Expected end of comment, got end of file"
Steps to Reproduce

Include a shell script file in the content directory that is calculating an array length using ${#Array[@]}
Try to fetch this content directory in the template.yaml
Run yarn dev and create component and then create repository. It throws error in fetch-base.
.

Context

Your Environment

Browser Information: Chrome Browser

Are you using the most recent version of the scaffolder and templating action? The templating syntax uses ${{ ... }} now to avoid this somewhat common collision.
It should also be possible to escape the substitution, use fetch:plain to avoid templating altogether, or use the copyWithoutTemplating option to avoid templating certain files.

authors: HorcruxAshu Rugvip

repo: backstage/backstage


text:
Enable APM trace with dd-trace which is not working in Backstage

Import the dd-trace, and invoke the trace.init() function to initialize with the required envs.
The APM metrics should showing up in datadog.
But actually it's not. I checked the envs and datadog-agent's status which should be fine.
Except the metrics did not show up,  what is also weird that no logs showing up though I customer the logger and set debug: true when init().
So for now there's no signs for diagnose.
By the way the dogstatsd sending metrics successfully which proves that the agent host connection should be OK.
Environment:
Deploy app in AWS -> ecs -> cluster -> ec2 , the agent task and the application task are in the same instance.
Backstage: 1.5.0
dd-trace: 3.2.0
opentracing: 0.14.7

We have this working, but haven't upgraded to to dd-trace -> v3.2.0. Will try next week. Was this working with v2.*?

@andrewthauer , how did you integrate it? Could you please show the sample code?
I just call the tracer.init() in packages/backend/indext.ts with the required envs. And I also set DD_TRACE_DEBUG: true and DD_TRACE_STARTUP_LOGS: true, still no logs show up.

Hey @SerenaIce, here's how I've set up basic Datadog tracing in our Backstage instance. I haven't gotten around to customising it or adding extra spans though which you might want to do.
This is using "dd-trace": "2.4.2" which is a bit old nowadays but I might try upgrading it tomorrow.
// package/backend/src/tracer.ts
import tracer from 'dd-trace';

tracer.init({
    service: "backstage.api",
    env: "production",
    hostname: "<snip>", // You likely don't need this
    sampleRate: 1,
    plugins: false, // There are a lot of plugins so we manually set them up
});
tracer.use('pg', { enabled: true, service: "backstage.db" })
tracer.use('express', { enabled: true, middleware: false, service: "backstage.api", blocklist: ['/healthcheck'] })
export default tracer;

// package/backend/src/index.ts
import './tracer' // The tracer should always be imported first!

The main thing here is just that the tracer is imported before everything else at the top of backend/src/index.ts. You might choose to inline it if you prefer instead of having it in a separate file.
I guess I'll note that the above is using Datadog all the way through rather than opentracing but I don't imagine it would affect very much

@marcus-crane , thanks and I will have a try. BTW, did you try to get the logs in your app service when enable the DD_TRACE_DEBUG: true? Which drove me crazy is that I couldn't see any logs which is hard for me to diagnose the issues.

We are pretty much doing the same as @marcus-crane. More specifically:
const datadogConfig = {
  service: env.DATADOG_APM_DEFAULT_SERVICE ?? env.APP_NAME ?? 'backstage',
  hostname: env.DATADOG_APM_HOST,
  port: Number(env.DATADOG_APM_PORT),
  tags: { env: env.APP_ENV },
  logInjection: true,
};

const enabled = Boolean(env.DATADOG_APM_ENABLED) ?? false;
if (enabled) {
  tracer.init(datadogConfig);
}

NOTE: The above code is called more or less at the very beginning of the plugins/backend/src/index.ts's main function. Hope this helps.

We finally find the root cause about this issue. It is because we had wrong value format in our GLOBAL_AGENT_NO_PROXY setting. The format like 'x.x.x.x/xx' should not be correct for the ip segment. It should be like 'x.x.x.*'.
So this is not a bug of backstage, I will close this one.

authors: SerenaIce andrewthauer marcus-crane


text:
Update authenticate-api-requests contrib page.

This comes with a few adjustments to newer versions of the dependency packages. Also some cleanup, and adding a server-to-server auth path.
Hey, I just made a Pull Request!

:heavy_check_mark: Checklist

[ ] A changeset describing the change and affected packages. (more info)
[X] Added or updated documentation
[ ] Tests for new functionality and regression tests for bug fixes
[ ] Screenshots attached (for UI changes)
[X] All your commits have a Signed-off-by line in the message. (more info)

Thank you for contributing during Hacktoberfest 🍂! You can claim the Backstage Hacktoberfest Holopin at https://bck.st/hacktoberfest-holopin 🙌🏻

authors: Pike suuus


text:
Add Worten to ADOPTERS.md.

Hey, I just made a Pull Request!
Add Worten (https://www.worten.pt) to the ADOPTERS.md file.
:heavy_check_mark: Checklist

[ ] A changeset describing the change and affected packages. (more info)
[ ] Added or updated documentation
[ ] Tests for new functionality and regression tests for bug fixes
[ ] Screenshots attached (for UI changes)
[x] All your commits have a Signed-off-by line in the message. (more info)

Hi! You were unlucky - i JUST now merged another adopter row at the bottom so there's a conflict. Feel free to reopen a new PR if that's easier than resolving the conflict, and we're happy to accept and merge after that.

authors: elisiariocouto freben


text:
feat(docs): Add documentation & example that AsyncApi 3 is supported

Hey, I just made a Pull Request!
Add documentation & example that AsyncApi 3 is supported.
The same way as it is done with OpenApi.
I also updated the example to the new version.
fixes #22534
:heavy_check_mark: Checklist

[x] A changeset describing the change and affected packages. (more info)
[x] Added or updated documentation
[ ] Tests for new functionality and regression tests for bug fixes
[ ] Screenshots attached (for UI changes)
[x] All your commits have a Signed-off-by line in the message. (more info)

Thanks again for this @Lazzaretti and looks like the demo site is now up to date too! 🚀 https://demo.backstage.io/catalog/default/api/streetlights/definition
Thanks for the review and merge @Rugvip 👍

authors: Lazzaretti awanlin


text:
Minor updates to testing documentation

Signed-off-by: Tavi Nolan Tavi.Nolan@fmr.com
Hey, I just made a Pull Request!
This PR updates the documentation in this page to fix the example showing how to run more than one suite of tests, and also removes a duplicated section 'Testing Utilities' which is already covered in the 'Examples' section of the same document.

:heavy_check_mark: Checklist

[ ] A changeset describing the change and affected packages. (more info)
[x] Added or updated documentation
[ ] Tests for new functionality and regression tests for bug fixes
[x] Screenshots attached (for UI changes)
[x] All your commits have a Signed-off-by line in the message. (more info)

resolves #25297

Thanks!

authors: benjdlambert rewixe


text:
scripts,workflows: add fossa wrapper script for config generation and retries

Fixes #4240 😅

Tugboat has finished building the preview for this pull request!
Link:

https://pr4723-7xwnrfpcuvr2xyuyn6pn3gtwsnwuznbf.tugboat.qa

Dashboard:

https://dashboard.tugboat.qa/603a461b65f8175d96fc9015

Tugboat has finished building the preview for this pull request!
Link:

https://pr4723-7xwnrfpcuvr2xyuyn6pn3gtwsnwuznbf.tugboat.qa

Dashboard:

https://dashboard.tugboat.qa/603a461b65f8175d96fc9015

Tugboat has finished building the preview for this pull request!
Link:

https://pr4723-7xwnrfpcuvr2xyuyn6pn3gtwsnwuznbf.tugboat.qa

Dashboard:

https://dashboard.tugboat.qa/603a461b65f8175d96fc9015

Tugboat has finished building the preview for this pull request!
Link:

https://pr4723-7xwnrfpcuvr2xyuyn6pn3gtwsnwuznbf.tugboat.qa

Dashboard:

https://dashboard.tugboat.qa/603a461b65f8175d96fc9015

authors: Rugvip backstage-service


text:
add refresh to deployments plugin

Hey, I just made a Pull Request!
Adds a refresh button + functionality to the GithubDeploymentsPlugin.
Screenshots

Issues
Issues: At the moment there seems to be a flakey test caused by the small time frame in which loading = true. Trying to figure out how to ensure this doesn't happen.
:heavy_check_mark: Checklist

[x] A changeset describing the change and affected packages. (more info)
[ ] Added or updated documentation
[x] Tests for new functionality and regression tests for bug fixes
[x] Screenshots attached (for UI changes)
[x] All your commits have a Signed-off-by line in the message. (more info)

Hey @freben - Just checking if this is good to merge now?


text:
Problems disabling/configuring a cop

I have a problem, disabling RSpec/MultipleExpectations. I some some funny behavior, when trying to configure/disable the cop via .rubocop.yml.
This:
RSpec/MultipleExpectations:
  Max: 5

works. I see fewer violations and the proper counters at the end of the lines in the report (e.g. RSpec/MultipleExpectations: Example has too many expectations [8/5].)
This:
RSpec/MultipleExpectations:
  Enabled: false

doesn't work, the cop is not disabled, violations are still reported.
However, this:
RSpec:
  MultipleExpectations:
    Enabled: false

works... with a twist:

$ rubocop -D --only RSpec/MultipleExpectations
Inspecting 100 files

0 files inspected, no offenses detected
key not found: "Enabled"
/Users/apopov/.rbenv/versions/2.4.1/lib/ruby/gems/2.4.0/gems/rubocop-0.49.1/lib/rubocop/config.rb:436:in `fetch'
/Users/apopov/.rbenv/versions/2.4.1/lib/ruby/gems/2.4.0/gems/rubocop-0.49.1/lib/rubocop/config.rb:436:in `enable_cop?'
/Users/apopov/.rbenv/versions/2.4.1/lib/ruby/gems/2.4.0/gems/rubocop-0.49.1/lib/rubocop/config.rb:118:in `block in initialize'
/Users/apopov/.rbenv/versions/2.4.1/lib/ruby/gems/2.4.0/gems/rubocop-0.49.1/lib/rubocop/config.rb:208:in `for_cop'
/Users/apopov/.rbenv/versions/2.4.1/lib/ruby/gems/2.4.0/gems/rubocop-0.49.1/lib/rubocop/cop/registry.rb:119:in `block in enabled'
/Users/apopov/.rbenv/versions/2.4.1/lib/ruby/gems/2.4.0/gems/rubocop-0.49.1/lib/rubocop/cop/registry.rb:138:in `select'
/Users/apopov/.rbenv/versions/2.4.1/lib/ruby/gems/2.4.0/gems/rubocop-0.49.1/lib/rubocop/cop/registry.rb:138:in `select'
/Users/apopov/.rbenv/versions/2.4.1/lib/ruby/gems/2.4.0/gems/rubocop-0.49.1/lib/rubocop/cop/registry.rb:118:in `enabled'
/Users/apopov/.rbenv/versions/2.4.1/lib/ruby/gems/2.4.0/gems/rubocop-0.49.1/lib/rubocop/cop/team.rb:47:in `cops'
/Users/apopov/.rbenv/versions/2.4.1/lib/ruby/gems/2.4.0/gems/rubocop-0.49.1/lib/rubocop/cop/team.rb:137:in `validate_config'
/Users/apopov/.rbenv/versions/2.4.1/lib/ruby/gems/2.4.0/gems/rubocop-0.49.1/lib/rubocop/cop/team.rb:25:in `initialize'
/Users/apopov/.rbenv/versions/2.4.1/lib/ruby/gems/2.4.0/gems/rubocop-0.49.1/lib/rubocop/runner.rb:257:in `new'
/Users/apopov/.rbenv/versions/2.4.1/lib/ruby/gems/2.4.0/gems/rubocop-0.49.1/lib/rubocop/runner.rb:257:in `inspect_file'
/Users/apopov/.rbenv/versions/2.4.1/lib/ruby/gems/2.4.0/gems/rubocop-0.49.1/lib/rubocop/runner.rb:205:in `block in do_inspection_loop'
/Users/apopov/.rbenv/versions/2.4.1/lib/ruby/gems/2.4.0/gems/rubocop-0.49.1/lib/rubocop/runner.rb:237:in `block in iterate_until_no_changes'
/Users/apopov/.rbenv/versions/2.4.1/lib/ruby/gems/2.4.0/gems/rubocop-0.49.1/lib/rubocop/runner.rb:230:in `loop'
/Users/apopov/.rbenv/versions/2.4.1/lib/ruby/gems/2.4.0/gems/rubocop-0.49.1/lib/rubocop/runner.rb:230:in `iterate_until_no_changes'
/Users/apopov/.rbenv/versions/2.4.1/lib/ruby/gems/2.4.0/gems/rubocop-0.49.1/lib/rubocop/runner.rb:201:in `do_inspection_loop'
/Users/apopov/.rbenv/versions/2.4.1/lib/ruby/gems/2.4.0/gems/rubocop-0.49.1/lib/rubocop/runner.rb:111:in `block in file_offenses'
/Users/apopov/.rbenv/versions/2.4.1/lib/ruby/gems/2.4.0/gems/rubocop-0.49.1/lib/rubocop/runner.rb:121:in `file_offense_cache'
/Users/apopov/.rbenv/versions/2.4.1/lib/ruby/gems/2.4.0/gems/rubocop-0.49.1/lib/rubocop/runner.rb:109:in `file_offenses'
/Users/apopov/.rbenv/versions/2.4.1/lib/ruby/gems/2.4.0/gems/rubocop-0.49.1/lib/rubocop/runner.rb:100:in `process_file'
/Users/apopov/.rbenv/versions/2.4.1/lib/ruby/gems/2.4.0/gems/rubocop-0.49.1/lib/rubocop/runner.rb:78:in `block in each_inspected_file'
/Users/apopov/.rbenv/versions/2.4.1/lib/ruby/gems/2.4.0/gems/rubocop-0.49.1/lib/rubocop/runner.rb:75:in `each'
/Users/apopov/.rbenv/versions/2.4.1/lib/ruby/gems/2.4.0/gems/rubocop-0.49.1/lib/rubocop/runner.rb:75:in `reduce'
/Users/apopov/.rbenv/versions/2.4.1/lib/ruby/gems/2.4.0/gems/rubocop-0.49.1/lib/rubocop/runner.rb:75:in `each_inspected_file'
/Users/apopov/.rbenv/versions/2.4.1/lib/ruby/gems/2.4.0/gems/rubocop-0.49.1/lib/rubocop/runner.rb:67:in `inspect_files'
/Users/apopov/.rbenv/versions/2.4.1/lib/ruby/gems/2.4.0/gems/rubocop-0.49.1/lib/rubocop/runner.rb:39:in `run'
/Users/apopov/.rbenv/versions/2.4.1/lib/ruby/gems/2.4.0/gems/rubocop-0.49.1/lib/rubocop/cli.rb:82:in `execute_runner'
/Users/apopov/.rbenv/versions/2.4.1/lib/ruby/gems/2.4.0/gems/rubocop-0.49.1/lib/rubocop/cli.rb:28:in `run'
/Users/apopov/.rbenv/versions/2.4.1/lib/ruby/gems/2.4.0/gems/rubocop-0.49.1/bin/rubocop:13:in `block in <top (required)>'
/Users/apopov/.rbenv/versions/2.4.1/lib/ruby/2.4.0/benchmark.rb:308:in `realtime'
/Users/apopov/.rbenv/versions/2.4.1/lib/ruby/gems/2.4.0/gems/rubocop-0.49.1/bin/rubocop:12:in `<top (required)>'
/Users/apopov/.rbenv/versions/2.4.1/bin/rubocop:22:in `load'
/Users/apopov/.rbenv/versions/2.4.1/bin/rubocop:22:in `<main>'

Sorry, the last configuration doesn't work, it just breaks rubocop, as the result is the same regardless of the options.

O.K., it seems there was an error in my setup, as I tried yet again and it worked, sorry for the confusion.

@AlexVPopov do you remember what the error in your setup was?
I started getting the behavior you're describing after upgrading to rubocop 0.49.0 from 0.47.1
TIA

@bobmazanec unfortunately I have totally forgotten what the error was, sorry 🤷♂

I had to try
Thanks & HNY 😃

authors: AlexVPopov bobmazanec

repo: backus/rubocop-rspec


text:
Array values that are buffered by .holdWhen() are released item per item

I guess this must be a bug.
Compare:
Bacon.interval(1000, [1,2]).
  take(3).log();

/* logs:
> [1, 2]
> [1, 2]
> [1, 2]
> <end>
*/

to
Bacon.interval(1000, [1,2]).
  holdWhen(Bacon.later(1000, false).startWith(true)).
  take(3).log();

/* logs:
> 1
> 2
> [1, 2]
> <end>
*/

I've tried to dig in the code but I'm having a hard time understanding what's going on there.

Nice find! There is a bug indeed in the holdWhen code here: https://github.com/baconjs/bacon.js/blob/master/src/holdwhen.coffee#L19
The problem lies with the usage of Array.prototype.concat here:
(xs,x) -> xs.concat(x)

The concat function treats arrays differently from other values. Would you like to try and fix it?

Released 0.7.44 with fix

authors: raimohanska timmolendijk


text:
Unexpected and inconsistent holdWhen() behavior

In the API docs .holdWhen() is said to:

pauses and buffers the event stream if last event in valve is truthy

When I tried to reproduce this behavior I couldn't, and on top of that I found v0.7.60 to behave very differently from v0.7.59.
My code sample is as follows:
Bacon.fromBinder(function (sink) {
  sink(new Bacon.Initial());
  sink(new Bacon.Error());
  sink(new Bacon.Next());
  sink(new Bacon.End());
  return function () {};
}).holdWhen(
  Bacon.later(2000, false).startWith(true)
).subscribe(function (event) {
  $('#log').append(event.constructor.name + "\n");
});

The output in #log that I had been expecting:
<2 sec delay>
Initial
Error
Next
End

Instead, what I ended up getting:
The result under v0.7.59 (demo):
Error
<2 sec delay>
End

The result under v0.7.60 (demo):
Initial
Error
Next
End
<no delays at any point in time>

I did look into the corresponding unit tests, as those are succeeding, but I had a hard time replicating them as they depend on some factory methods (expectStreamTimings() and series()) which are unfamiliar to me.
Two questions:

What is the expected behavior of holdWhen() in the case of my code sample?
What explains the difference between v0.7.59 and v0.7.60 (and possibly the expected behavior)?

I'd say the expected behavior would be
Error
<2 sec delay>
Initial
Next End
Because the Error events are always passed through directly.
This is once again an issue with synchronous sources. If you delay the source, it'll work.
The difference to 0.7.59 is that holdWhen has been completely re-implemented.
It would make sense to fix this, of course.

Ok, fixed in 0.7.61, with 2 more test cases. Will you pls chec if it works for you.

Works, except that the Initial has been transformed into a Next: demo

Thanks. Well, Initial is a corner case: EventStreams should never emit Initial events. It gets converted on the way... somewhere :)

Anyway, this seems to be fixed now. Please re-open if you disagree.

Yes, agree.
It does beg the question what to do with Initial events in general though, for which I opened a new issue.


text:
1.15 update

Not working on 1.15

#264


text:
PNG (raster) font does not have enough letter spacing

Are you experiencing an issue with...

[X] shields.io
[  ] My own instance
[  ] badge-maker NPM package

:beetle: Description

The numbers inside the raster.shields.io social badge (png version) have letter spacing that is too small, making the text not readable.
:link: Link to the badge

:bulb: Possible Solution
Increase letter spacing

Thanks for the report @boaz-codota! We're in the process of rewriting our rasterization proxy which produces the png badges, and while the pngs are always going to be less pixel-perfect than the svgs, I do think you can expect to see an improvement once we're done (which should be fairly soon).
Here's a screen grab of what your badge looks like with the new version (sorry for the blur, taken from my local):

Can't wait, we love the product in https://tabnine.com/ and use it to display social information in Jetbrains Marketplace and VSCode Marketplace

@boaz-codota Out of interest, what's your use-case for using raster badges in preference to SVG? We know we still serve a lot of PNGs but we don't really have a great handle on where and why they are used over SVG.

I'm glad you asked! We embed those badges in our Jetbrains plugin page.
While the web version renders the svgs perfectly: https://plugins.jetbrains.com/plugin/12798-tabnine-ai-autocomplete-javascript-c-java-python-ruby-rust-go-php--
The IDE cannot render SVGs at all (didn't save a pic of it, but trust me on that one). The PNG version on the other hand works perfectly:

authors: boaz-codota calebcartwright chris48s

repo: badges/shields


text:
Added Elegant Objects Logos

This will provide the following:

A space for "Other" logos to be uploaded to
A way for users that cannot use base64 and do not have their own hosting to use svg logos
Elegant Objects logos for the java community

This is probably the most typical form of open source contribution there is. I'm surprised that it was rejected last time. I'm hoping for a more "open" outcome this time around.

Messages

:book:

:sparkles: Thanks for your contribution to Shields, @ashtonhogan!

  Generated by :no_entry_sign: dangerJS

authors: ashtonhogan shields-ci


text:
fix [jsdelivr] service tests

https://app.circleci.com/pipelines/github/badges/daily-tests/495/workflows/4dcc5a2d-179a-40da-8956-0ffb7c3540fe/jobs/1393
Another batch of failing tests due to 0/week
Leveraging a similar approach as #5583 for this one vs the approach in #5618 as I've found the jsdelivr service to be trickier to find good test targets

Messages

:book:
:sparkles: Thanks for your contribution to Shields, @calebcartwright!

  Generated by :no_entry_sign: dangerJS against 3b84656898961b06c5ba126398cb71713e38871b

authors: calebcartwright shields-ci


text:
Remove rate limiting functionality

Our home grown rate limiting feature recently tripped us over in  #6511. When taking a closer look at the class, both @chris48s and I challenged its usefulness.
Its main intent is probably to guard against denial of service attacks, but it doesn't feel particularly robust. We still handle the requests on the same machine, so the rate-limiting itself could get easily overwhelmed if you simply sent a little more requests. Looking at our metrics for the past 30 days, outside the past week where I was experimenting with different numbers of servers, it only kicked in very occasionally to limit by ~5 to 15 requests/second. However, I'm not convinced it did any positive impact.
The rate limiting classes have no unit tests, is not easily configurable and still have comments referencing our old OVH servers. The rate limiting numbers had not been updated in many years, despite us servicing much more traffic on a very different underlying platform. I'm not sure what the intent of rate limiting per badge type is, and the hardcoded Camo IPs feels brittle. To me, this really is technical debt in our code server at this point.
I suggest we delete this functionality, slim down our server code and save a few CPU cycle per request. A CDN seems much better suited for these kind of tasks, and Cloudfare does allow one rule with our free plan. Let's discuss the details of that offline.

Warnings

:warning:
This PR modified the server but none of its tests. That's okay so long as it's refactoring existing code.

Messages

:book:
:sparkles: Thanks for your contribution to Shields, @PyvesB!

  Generated by :no_entry_sign: dangerJS against f300a196536ce4cea8f9a7daa315777137e4377d

authors: PyvesB shields-ci


text:
move all public production config into yaml

Refs https://github.com/badges/shields-ops/issues/16
Refs https://github.com/badges/shields-ops/pull/22

Messages

:book:
:sparkles: Thanks for your contribution to Shields, @chris48s!

  Generated by :no_entry_sign: dangerJS against a44a04ef457d63bb6679f9cf6ab07901c9d3b30d


text:
The supporting of windows

Currently this lib not work in windows, because:
1)
if (strtoupper(substr(PHP_OS, 0, 3)) === 'WIN') {
define('SOFTMOCKS_ROOT_PATH', '');
} else {
define('SOFTMOCKS_ROOT_PATH', '/');
}
2)
\QA\SoftMocks::doRewrite
$delimiter = (strtoupper(substr(PHP_OS, 0, 3)) === 'WIN' ? ';' : ':');
foreach (explode($delimiter, get_include_path()) as $dir) {
possible, there is more issues

@ZyManch would you like to volunteer for this?

authors: Sannis ZyManch

repo: badoo/soft-mocks


text:
Can't use setOnDateSelectedListener in kotlin

When I call setOnDateSelectedListener I get an error "Expresstion cannot be invoke as a function. The function invoke() is not found"
My code:
datePicker.onDateSelectedListener(object: DatePickerTimeline.OnDateSelectedListener{
override fun onDateSelected(year: Int, month: Int, day: Int, index: Int) {
calendar.set(year, month, day)
viewModel.getDiaryByPriority(calendar, "objective")
}
})

       datePicker.setOnDateSelectedListener{ year, month, day, index ->             var strDay = day.toString()             var strMonth = (month+1).toString()             if (strMonth.toInt()<10)                 strMonth = "0$strMonth"             if (day<10)                 strDay = "0$day"             textView.text =   strDay+"-"+strMonth+"-"+year.toString()             popupWindow.dismiss()         }

repo: badoualy/datepicker-timeline


text:
Showing profile image when customer login.

Issue Reference
#5464
Description
Showing customer profile picture if customer login and have uploaded a profile picture.
Fixed for default and velocity theme.
https://prnt.sc/oVwv235YWgj8

Resolve conflicts

@papnoisanjeev
not working properly, the customer name is not visible, Please find the screenshot Here
And please resolve the conflicts.

@papnoisanjeev
This is working fine only with the default theme. but getting issues with the velocity theme

@papnoisanjeev
The conflicts are still not resolved.

@Sanjaybhattwebkul
Conflicts has been resolved here.

@papnoisanjeev
The image option will only be for the velocity theme. the uploaded image should not be visible on the default theme.

And if the customer is updating the profile from the default theme, then the customer's image should not be removed.

@Sanjaybhattwebkul
Removed profile pic for default theme as discussed as only need for velocity theme.

@papnoisanjeev
The profile picture should not be updated if the customer is updating his profile from the default theme.

@papnoisanjeev The profile picture should not be updated if the customer is updating his profile from the default theme.

any update?

@Sanjaybhattwebkul
Fixed the issue (user profile remove) if anyone update profile using default theme.

@papnoisanjeev
Still not working the customer is not able to delete the profile picture,

@Sanjaybhattwebkul
Fixed.

repo: bagisto/bagisto


text:
Issue fixed #7161

#7161

Issue fixed for counting on wishlist and compare product

@amitwebkul
Not fixed, still counting is  not visible for the wishlist. please find the screenshot Here

@amitwebkul
This is working fine, Please find the screenshot Here

authors: Sanjaybhattwebkul amitwebkul


text:
Crash when gif from document directory.

i have download the list of gif from server into my document directory.
now when i m going to display it crash.
mycode:
let imageData = NSData(contentsOfURL: NSURL(fileURLWithPath: dataPath))
let advTimeGif = UIImage.gifWithData(imageData!)
Crash at here::
var delayObject: AnyObject = unsafeBitCast(
CFDictionaryGetValue(gifProperties,
unsafeAddressOf(kCGImagePropertyGIFUnclampedDelayTime)),
AnyObject.self)

Are you still having this issue?
If yes, can you try the new v1.6.1 version and check if the problem persists?
We removed the unsafeAddressOf call, so hopefully this bug is fixed. If not, feel free to re-open! 🍻

authors: AlbertSwift bahlo

repo: bahlo/SwiftGif


text:
null-safety in Executor

Executor's loop doesn't have any guards against null.  It should either:

reject null (possibly w/ a runtime exception).  This would mean that coding in Oj will be totally null-safe.
simply push null into PS

For now null is simply pushed into PS.
It'll be too complicated at this stage to go with approach 2.

repo: bahmanm/ojlang-core


text:
baichuan2-13b-base，模型加载内存超标

现象：
单进程单卡微调。
加载13b模型， 模型大小26G，加载到内存中最高占用62G左右，转到GPU上后，占显存27G，内存回落到2.2G。
影响：
多卡并行微调时，多进程下内存占用多倍 62*n，6卡并行直接把300G内存撑爆，机器干重启了。
问题：
为什么26G的模型加载，内存能到62G，中间是不是有问题？
模型加载  62G

load到GPU  30.5G

微调中的内存占用 2.2G

我这边deepspeed使用stage2的时候内存会爆，stage3就没问题了，不知道是什么bug

optimizer会占用大量的显存

authors: beginOfAll vcvcvnvcvcvn xyjigsaw


text:
issue=#437 tableschema-on-zk

#437
本次pr实现：
master把table的schema写到分布式协调服务上；建一个和ts、kick同级的table目录，一个表格在其下有一个子结点。
ts执行watch
（本次pr中ts收到watch通知只是打个日志，没有其它逻辑）。
为保证数据和meta表一致，master初始化时把table的schema统一写入分布式协调服务；
建表、更新schema时在写完meta表之后写zk；写失败打log.
删表时删除对应结点。
在zk和nexus上测试。

schema的变更由master通知ts.

repo: baidu/tera


text:
能别更新了吗

每次更新都出问题

老版本可以下载离线包 解压后手动安装

authors: baiy nujiakk

repo: baiy/Ctool


text:
🛑 Quill is down

In 9300ec3, Quill (https://quill.im) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Quill is back up in 7f197b4 after 11 minutes.

repo: baizhiheizi/upptime


text:
Update the ifconfig parsing to handle the new format introduced in Debian Stretch

As per issue #40 - I've also run into this on the latest Raspbian distro so have submitted this patch which handles the new format and adds tests for it.

Closing since it looks like this will never be merged :-(

repo: bakerface/wireless-tools


text:
chore(deps): update module golang.org/x/mod to v0.20.0

This PR contains the following updates:

Package
Type
Update
Change

golang.org/x/mod
require
minor
v0.19.0 -> v0.20.0

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

Pull Request Test Coverage Report for Build 10242353406
Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 62.872%

Totals

Change from base Build 10156958597:
0.0%

Covered Lines:
1226

Relevant Lines:
1950

💛  - Coveralls

authors: bakito coveralls

repo: bakito/adguardhome-sync


text:
add owners for v3 pools

v3 pools have different ownership concept, need to integrate this:
On a pool, natively there can be a:

SwapFeeManager - Can set swap fee
PauseManager - Can pause the pool
PoolCreator - Can set fee splits

How about amp?

if SwapFeeManager or PauseManager are not set, the fallback is that the authorizer controls permissions. The StablePool delegates permissions for amp updates to the authorizer as well

All 3 roles are set on pool creation. V2 owner is equivalent of V3 swapFeeManager.

authors: franzns gmbronco

repo: balancer/backend


text:
Receiving "Must contain an adapter key referencing the adapter to use." errors during Heroku deployment

I am in the process of deploying a basic SailsJS application to Heroku. I have done this a few times before without any hiccups; which leads me to believe this might be a documentation or deprecation issue.
When I deploy the application, this is the error that I am getting over and over:
Must contain an `adapter` key referencing the adapter to use.
In model (class), invalid connection :: mongoProd

I am currently using the following versions:
sails: 0.11.4
sails-mongo: 0.11.6

Now, I can confirm that have the sails-mongo adapter installed (duh). As far as my production.js is concerned, this is what I have:
environment: 'production',
  hookTimeout: 30000,

  // blueprint settings
  blueprints: {
    rest: false,
    shortcuts: false
  },

  session: {
    adapter: 'redis',
    host: //,
    port: 9592,
    user: //,
    pass: //,
  },
  models: {
    connection: 'mongoProd',
    migrate: 'alter'
  },
  port: process.env.PORT || 5000,

  log: {
    level: "silent"
  }

And finally, this is what my connections.js looks like:
mongoProd: {
    adapter: 'sails-mongo',
    url: process.env.MONGOLAB_URI
  },

I feel like Sails is not finding any of my environment configurations.

are you able to lift locally? if so, can you lift in console mode and do a console.log(sails.config.connections); and post the output?
also console.log(sails.config.connections); and post the output?

@japel great questions
@dniccum you might already know this, but please be very, very careful using migrate: alter in production!  Part 2 of this covers doing a deployment to Heroku and might be helpful here.

@japel I can lift in my local environment using sails lift, however when I use sails lift --prod, this is the error that I get:
error: Error: Failed to connect to MongoDB.  Are you sure your configured Mongo instance is running?
Error details:
{ [MongoError: connect ECONNREFUSED 127.0.0.1:27017]
  name: 'MongoError',
  message: 'connect ECONNREFUSED 127.0.0.1:27017' }
    at _createError (/Users/dougniccum/Sites/quiq-math-backend/node_modules/sails-mongo/lib/adapter.js:103:23)
    at /Users/dougniccum/Sites/quiq-math-backend/node_modules/sails-mongo/lib/adapter.js:106:13
    at /Users/dougniccum/Sites/quiq-math-backend/node_modules/sails-mongo/lib/connection.js:25:20
    at /Users/dougniccum/Sites/quiq-math-backend/node_modules/sails-mongo/node_modules/mongodb/lib/mongo_client.js:276:20
    at /Users/dougniccum/Sites/quiq-math-backend/node_modules/sails-mongo/node_modules/mongodb/lib/db.js:224:14
    at null.<anonymous> (/Users/dougniccum/Sites/quiq-math-backend/node_modules/sails-mongo/node_modules/mongodb/lib/server.js:234:9)
    at g (events.js:260:16)
    at emitTwo (events.js:87:13)
    at emit (events.js:172:7)
    at null.<anonymous> (/Users/dougniccum/Sites/quiq-math-backend/node_modules/sails-mongo/node_modules/mongodb/node_modules/mongodb-core/lib/topologies/server.js:269:68)
    at g (events.js:260:16)
    at emitTwo (events.js:87:13)
    at emit (events.js:172:7)
    at null.<anonymous> (/Users/dougniccum/Sites/quiq-math-backend/node_modules/sails-mongo/node_modules/mongodb/node_modules/mongodb-core/lib/connection/pool.js:81:12)
    at g (events.js:260:16)
    at emitTwo (events.js:87:13)

I am assuming this is normal since I am not running MongoDB locally. I am using my localDiskDB.db.
@mikermcneil noted!

@dniccum your local mongodb is running on the specified host and port? (127.0.0.1:27017)

@dniccum yeah, thats normal... try lifting locally in console mode with localDiskDB and do those console.log() I wrote, just to check if those are defined

@japel This is what is returned when I run the console.log(sails.config.connections) command:
{ localDiskDb: { adapter: 'sails-disk' },
  someMysqlServer:
   { adapter: 'sails-mysql',
     host: 'YOUR_MYSQL_SERVER_HOSTNAME_OR_IP_ADDRESS',
     user: 'YOUR_MYSQL_USER',
     password: 'YOUR_MYSQL_PASSWORD',
     database: 'YOUR_MYSQL_DB' },
  mongoProd: { adapter: 'sails-mongo', url: undefined },
  somePostgresqlServer:
   { adapter: 'sails-postgresql',
     host: 'YOUR_POSTGRES_SERVER_HOSTNAME_OR_IP_ADDRESS',
     user: 'YOUR_POSTGRES_USER',
     password: 'YOUR_POSTGRES_PASSWORD',
     database: 'YOUR_POSTGRES_DB' } }

Once again, I'm assuming that the reason why the url attribute is undefined is because the environment variable has not been defined. As for the console.log(sails.config.environment) command, this is what I get:
development

@dniccum how do things look if you start up your Sails app using:
NODE_ENV=production node app

@mikermcneil Nothing happens.

@dniccum which operating system are you using?

OSX El Capitan.

@dniccum and what do you mean with nothing happens?
what is the output of your terminal when doing
NODE_ENV=production node app.js
?

Yes when I enter this into my terminal, I receive no response or additional
messages.
On Mon, Jan 18, 2016 at 11:37 AM Jan Viktor Apel notifications@github.com
wrote:

@dniccum https://github.com/dniccum and what do you mean with nothing
happens?
what is the output of your terminal when doing
NODE_ENV=production node app.js
?
—
Reply to this email directly or view it on GitHub
https://github.com/balderdashy/sails/issues/3499#issuecomment-172601366.

--
Doug Niccum
Sent from my iPhone. Sorry if I have fat fingers.

@dniccum Would you mind setting up a repo that reproduces this in a new sails app real quick?  I think that'd be the easiest way to see what's going on.
e.g.:
sails new sails-issue-3499
cd sails-issue-3499
npm install sails-mongo@0.11.6 --save
# Now make whichever are the simplest/quickest changes which reproduce the issue,
# and when you for sure have the issue isolated, run:
git init
hub create  # or use the GitHub UI to create the repo and `git remote add` it manually
git add .
git commit -am 'Reproduces https://github.com/balderdashy/sails/issues/3499'
git push -u origin master
hub browse # or open the repo in your browser manually
# Then copy the URL of the new repo and paste it as a comment on this issue.
# We'll check it out, and since this way we'll be able to experience the problem
# ourselves, we should have no problem getting to the bottom of it.

Thanks man!

After some toying around, I have determined that the problem had to do with the version of redis-connect that I was using. Once I reduced it to lock in version 1.4.5, the application works just fine. Sorry for wasting your time.

@dniccum Not at all - sorry for the confusion with versions.  I tried my best w/ the error messages, but it's sort of an uphill battle with the peer dependencies.  Luckily, I think we've got session store dependency versioning more or less figured out for the upcoming v0.12 release, so getting the right version should get easier soon.

@mikermcneil thanks for letting me know and all of your help.

authors: dniccum japel mikermcneil

repo: balderdashy/sails


text:
sails 1.0 .create return the first record in creating model instead just created record in mysql adapter

Sails version: 1.0.0-32
Node version: 6.9.5
NPM version: 4.2.0
Operating system: Windows 10

sails-mysql: 1.0.0-15
module.exports.datastores = {
     adapter: require('sails-mysql'),
     url: 'mysql://........'
}

make request:
User.create({
        userName: "Jone",
        userPhone: "123"
      }).meta({
        fetch: true
      }).exec((error, result) => {
        console.log(result);
      });

and it return first record from database table User instead just created record.

@grey-ka I'm not able to reproduce this at all.  Doing .create() with .meta({fetch: true}) consistently returns the created record for me.  Can you update to the latest release of Sails 1.0 (and re-install your node modules), and then if the problem persists post a repo we can use to reproduce this issue?

@sgress454, thanks for the answer.
I found out what the problem was.
In my table there was no primary Key or any unique field and I specified in the model a random field with non-unique data.
As I understand that the request returns the correct data, I must specify a primaryKey field with unique data.

@grey-ka Yes, Waterline expects every table to have a primary key, and it's just good practice regardless.  You don't lose anything by having a unique identifier on every row.  I'm assuming you were using migrate: safe in your models config?  Otherwise Waterline should have created a primary key for you...


text:
Use 'www' folder if is available in production

I would like know the opinion about this.
Instead of define again a gunt task to copy the files in '.tmp/folder', use www/ folder with static assets compiled.
.cc @davidrivera

Yep, just running into a similar issue over at Sane Stack: https://github.com/artificialio/sane/issues/51
The grunt hook is disabled per default, because using docker, or nginx+pm2 (multi-process apps) it really is just causing issues, but I didn't think about the fact that the assets do not get lifted anymore on a simple sails lift.
This would certainly be an option, or how about having an option in the .sailsrc? Something like assets: assets or assets: www, etc? If it is empty it just defaults to .tmp/public. This makes it simple, new people don't get confused because nothing changes for them and others can customize it.
What are your thoughts?

@Globegitter agreed- so as you probably know, you can do this now by setting sails.config.paths.public- is the issue that it isn't being pulled from the sailsrc file in time to affect the static middleware? Or is it that the path isn't being resolved if it's relative?
ie. in your sailsrc file:
{
  "paths": {
    "public": "./www"
  }
}

Bumped~

What exactly does the "bumped" mean?

@randallmeeker et. al.
It means we are doing what we can to move through the backlog of PRs and get caught up~
bump (verb)
past tense: bumped; past participle: bumped
to push (something) jerkily in a specified direction.
Hopefully we won't do it jerkily but I can't make any promises ;)

@CWyrtzen wat? and what's ~ means?
seriously, bumped doesn't mean nothing, and at the end you says I can't make any promises, so basically you are saying nothing of nothing...
Chocolate~

I'm still confused. Does it mean your doing something with this issue
specifically?
I know what it means for a community member to "bump". They are promoting
an issue or request.
On Mar 17, 2015 9:34 AM, "Courtney Wyrtzen" notifications@github.com
wrote:

@randallmeeker https://github.com/randallmeeker et. al.
It means we are doing what we can to move through the backlog of PRs and
get caught up~
bump (verb)
past tense: bumped; past participle: bumped
to push (something) jerkily in a specified direction.
Hopefully we won't do it jerkily but I can't make any promises ;)
—
Reply to this email directly or view it on GitHub
https://github.com/balderdashy/sails/pull/2206#issuecomment-82386301.

Twas a bit of a joke about not making promises...the note simply means we sorting it through, moving it along intentionally, taking a second and third and fourth look...
All I can say is we are doing what we can to catch up and clean up and shine up so when you see BUMP it means it has been hand-carried on your behalf.
Perhaps my attempt at humor is misplaced but I think a little levity and good will are essential in times like these.
And @randallmeeker yes, promote, absolutely: further the progress of (something, especially a cause, venture, or aim); support or actively encourage. Indeed~
Cheers~

Alright, closing in favor of the solution documented here: https://github.com/balderdashy/sails/pull/2543#issuecomment-69277536

authors: CWyrtzen Globegitter Kikobeats mikermcneil randallmeeker


text:
Revise 3rd party integrations for new implementations

I have revised the 3rd party integrations pages based on new cloud IoT provisioning implementations, and also a balenaBlock (Cloud Relay) to use the provisioning and send data. Below is some background on the provisioning implementations, and how that changed the structure of the integration docs.
Provisioning implementation
The revised cloud IoT integrations are in these repositories: aws-iot-provision, azure-iot-provision, and gcp-iot-provision. They all now use the same approach to provisioning a device:

HTTP request to cloud
Run cloud function, which executes the steps below
Validate UUID
Generate public key pair / certificate
Register with IoT Core
Push credentials as env vars to balenaCloud

Cloud Relay block makes it easy to use the provisioning tools and send data. It automatically calls the HTTP endpoint on the cloud to provision the device. The block then expects data from a local MQTT broker, and relays it to the provisioned IoT service in the cloud.
Integration pages
Since the cloud provisioning implementations are similar and they provide detailed setup instructions, this PR condenses the documentation to a single dynamic page. The page describes how provisioning works and also mentions Cloud Relay block. It then directs the user to the implementation repository for generic cloud setup documentation and specific provisioning setup documentation.
This PR also includes a second commit to remove the original 3rd party integration pages.

Added commit with the link to the blog post, so removed draft label.

@vipulgupta2048 , I'd appreciate your review at least from the perspective of how to implement a dynamic page.

Thanks for the review @vipulgupta2048 ! I fixed the straightforward issues, but there are a couple worth discussing. I'll set up a meeting and loop in @mpous as well.

Thanks @kb2ma Will draft this so it doesn't get merged before the discussion

@vipulgupta2048 integrated the changes as discussed recently. Dictionary size per cloud reduced from 16 items to 9.  I also updated the text to accommodate the dictionary changes, and made a few other minor improvements.
Also, thanks for mentioning the continued presence of obsolete files. I confirmed this and removed in 69c7533.
Checks passed, so ready for hopefully final review.

@balena-ci rebase

@vipulgupta2048 thanks for the improvements. See inline comments. I did remove the separate 3rd party integrations page.

@kb2ma Thanks, please do make a note to resolve the comments when you are finished with them. You can only leave the ones pending discussions or a question you have. Much cleaner to re-review.

Thanks @vipulgupta2048  for the tip on resolving comments for re-review.

repo: balena-io/docs


text:
Update renovatebot/github-action action to 34.12.0

This PR contains the following updates:

Package
Type
Update
Change

renovatebot/github-action
action
minor
v34.10.0 -> v34.12.0

Release Notes

renovatebot/github-action
v34.12.0
Compare Source
See the the changelog for changes in all releases.
34.12.0 (2022-11-01)
Bug Fixes

deps: update renovate/renovate docker tag to v34.12.0 (d23b624)

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

@balena-ci I self-certify!

repo: balena-io/renovate-config


text:
balena-raspberrypi: Rename resin image types to balena

Rename resin image types to balena and replace RESIN_ env vars
Changelog-entry: Rename resin image types to balena
Signed-off-by: Kyle Harding kyle@balena.io

Can one of the admins verify this patch?

@balena-ci rebase

@balena-ci rebase

@balena-ci I self-certify!

authors: klutchell resin-jenkins

repo: balena-os/balena-raspberrypi


text:
bluez: Disable GATT 180A service provided by BlueZ for HNT

Author: Ryan Walmsley
Changelog-entry: bluez: Disable GATT 180A service provided by BlueZ for HNT
Signed-off-by: Alexandru Costache alexandru@balena.io

Awesome, thanks for merging @acostach .
I'm guessing likely next week this will be available to select on balena-cloud.com
Out of interest are the releases available slightly earlier on balena-staging?

@ryanteck yes, they are available a bit earlier there

authors: acostach ryanteck


text:
bblayers: Modify layer ordering

Yocto classes and conf files ignore layer priorities and are parsed
in order instead.
Changelog-entry: Modify layer ordering
Signed-off-by: Alex Gonzalez alexg@balena.io

@balena-ci rebase

@balena-ci I self-certify!


text:
worker: add runtimeConfiguration as parameter to setup()

Add Leviathan.RuntimeConfiguration as a parameter to setup(), allowing
reuse of this function to create and run Worker servers without a config
file.
Change-type: patch
Signed-off-by: Joseph Kogut joseph@balena.io

@balena-ci rebase

authors: jakogut klutchell

repo: balena-os/leviathan


text:
send image before flashing

addresses https://github.com/balena-os/leviathan-worker/issues/4
This fixes the problem, however it increases the flashing time. Short term fix as moving the core back on to the testbot would probably also solve this problem
Change-type: patch
Signed-off-by: Ryan Cooke ryan@balena.io

What issue is this PR addressing?

I would wait until https://github.com/balena-os/leviathan-worker/pull/6 is merged.

Superseded by https://github.com/balena-os/leviathan-worker/pull/9

authors: klutchell rcooke-warwick


text:
e2e: Run tests on qemu and testbots via github actions

Depends-on: https://github.com/balena-os/leviathan/pull/786

This PR is expecting BALENACLOUD_API_KEY to be a GH secret with the testbot API key.

Looks like we already have BALENA_TOKEN from the testbot user as a secret so I will use that.

@balena-ci rebase

Dang it, @klutchell My bad, I rebased using GitHub's button and it seems it does the rebase correctly but not as clean as versionbot. Trying test if your latest commit fixed this or not.

@balena-ci I self-certify!


text:
Issue in initializing variables in Ballerina

Description:
Please consider below code.
public type Client client object {

    //JMS connection related objects
    jms:Connection jmsConnection;
    jms:Session jmsSession;
    jms:QueueSender queueSender;

    public function __init(MessageStoreConfiguration storeConfig, boolean
        enableGuranteedDelivery = false, Client? failoverStore = ()) returns error? {
             self.storeConfig = storeConfig;
             check self.intializeMessageSender(storeConfig);
        }

    //init client
    function intializeMessageSender(MessageStoreConfiguration storeConfig) returns error? {

        string providerUrl = storeConfig.providerUrl;
        self.queueName = storeConfig.queueName;

        string? userName = storeConfig["userName"];
        string? password = storeConfig["password"];

        string acknowledgementMode = "AUTO_ACKNOWLEDGE";
        string initialContextFactory = getInitialContextFactory(storeConfig.messageBroker);

        // This initializes a JMS connection with the provider.
        self.jmsConnection = new({
                initialContextFactory: initialContextFactory,
                providerUrl: providerUrl
            });

        // This initializes a JMS session on top of the created connection.
        self.jmsSession = new(self.jmsConnection, {
                acknowledgementMode: acknowledgementMode
            });

        // This initializes a queue sender.
        self.queueSender = new(self.jmsSession, queueName = self.queueName);
    }

}

The variables
jms:Connection jmsConnection;
jms:Session jmsSession;
jms:QueueSender queueSender;

are not recognized as initialized. The user is confused why as he has actually initialized them. This is affecting the user experience because as a programmer, I have called intializeMessageSender function and I am expecting variables are initialized.
Steps to reproduce:
N/A
Affected Versions:
Ballerina version: 0.991.0

According to the spec; this is the expected behaviour. Hence, not a bug.

authors: abeykoon grainier

repo: ballerina-platform/ballerina-lang