text:
🐛 Bug Report:  Bitbucket Server Discovery cannot be configured as no plugin directory available

📜 Description
We are moving away from the default GitHub to our custom Bitbucket integration for loading catalog entities.
As per the document, it is required to run the below command --> https://backstage.io/docs/integrations/bitbucketServer/locations/
From your Backstage root directory
yarn --cwd packages/backend add @backstage/plugin-catalog-backend-module-bitbucket-server
And then add the entity provider to your catalog builder:
packages/backend/src/plugins/catalog.ts
import { BitbucketServerEntityProvider } from '@backstage/plugin-catalog-backend-module-bitbucket-server';
export default async function createPlugin(
env: PluginEnvironment,
): Promise {
const builder = await CatalogBuilder.create(env);
builder.addEntityProvider(
BitbucketServerEntityProvider.fromConfig(env.config, {
logger: env.logger,
scheduler: env.scheduler,
}),
);
// ..
}
however after running the server which is already configured with postgress DB the "plugins/catalog.ts" is not created and hence the integration is not working.
Kindly let me know if this is a bug
👍 Expected behavior
It should create the directory --> backstage/plugin-catalog-backend-module-bitbucket-server';
👎 Actual Behavior with Screenshots
The directory is not created and hence no configuration is possible.
backstage/plugin-catalog-backend-module-bitbucket-server';

👟 Reproduction steps
Install backstage version 1.24/1.25/1.26
once done, just follow your documentation; https://backstage.io/docs/integrations/bitbucketServer/
yarn --cwd packages/backend add @backstage/plugin-catalog-backend-module-bitbucket-server
in the packages/backend/src/plugins/catalog.ts is bot created and hence no configuration is possible
📃 Provide the context for the Bug.
Since we dont want to use github and we have our private bitbucket, this configuration is stopping us from from production
🖥 Your Environment
root@inmdlx100bs002:/data/backstage/backstage# yarn backstage-cli info
yarn run v1.22.22
$ /data/backstage/backstage/node_modules/.bin/backstage-cli info
OS:   Linux 5.15.0-119-generic - linux/x64
node: v18.20.4
yarn: 1.22.22
cli:  0.26.11 (installed)
backstage:  1.24.0
Dependencies:
@backstage/app-defaults                                          1.5.10
@backstage/backend-app-api                                       0.7.9, 0.9.3
@backstage/backend-common                                        0.21.7, 0.22.0, 0.23.3, 0.24.1
@backstage/backend-defaults                                      0.2.18, 0.4.4
@backstage/backend-dev-utils                                     0.1.5
@backstage/backend-openapi-utils                                 0.1.17
@backstage/backend-plugin-api                                    0.6.21, 0.7.0, 0.8.1
@backstage/backend-tasks                                         0.5.27
@backstage/catalog-client                                        1.6.6
@backstage/catalog-model                                         1.6.0
@backstage/cli-common                                            0.1.14
@backstage/cli-node                                              0.2.7
@backstage/cli                                                   0.26.11
@backstage/config-loader                                         1.9.0
@backstage/config                                                1.2.0
@backstage/core-app-api                                          1.14.2
@backstage/core-compat-api                                       0.2.8
@backstage/core-components                                       0.14.10
@backstage/core-plugin-api                                       1.9.3
@backstage/e2e-test-utils                                        0.1.1
@backstage/errors                                                1.2.4
@backstage/eslint-plugin                                         0.1.8
@backstage/frontend-plugin-api                                   0.6.7, 0.7.0
@backstage/integration-aws-node                                  0.1.12
@backstage/integration-react                                     1.1.30
@backstage/integration                                           1.14.0
@backstage/plugin-api-docs                                       0.11.8
@backstage/plugin-app-backend                                    0.3.73
@backstage/plugin-app-node                                       0.1.24
@backstage/plugin-auth-backend-module-atlassian-provider         0.2.5
@backstage/plugin-auth-backend-module-aws-alb-provider           0.1.17
@backstage/plugin-auth-backend-module-azure-easyauth-provider    0.1.7
@backstage/plugin-auth-backend-module-bitbucket-provider         0.1.7
@backstage/plugin-auth-backend-module-cloudflare-access-provider 0.2.1
@backstage/plugin-auth-backend-module-gcp-iap-provider           0.2.19
@backstage/plugin-auth-backend-module-github-provider            0.1.21
@backstage/plugin-auth-backend-module-gitlab-provider            0.1.21
@backstage/plugin-auth-backend-module-google-provider            0.1.21
@backstage/plugin-auth-backend-module-guest-provider             0.1.10
@backstage/plugin-auth-backend-module-microsoft-provider         0.1.19
@backstage/plugin-auth-backend-module-oauth2-provider            0.2.5
@backstage/plugin-auth-backend-module-oauth2-proxy-provider      0.1.17
@backstage/plugin-auth-backend-module-oidc-provider              0.2.6
@backstage/plugin-auth-backend-module-okta-provider              0.0.17
@backstage/plugin-auth-backend-module-onelogin-provider          0.1.5
@backstage/plugin-auth-backend                                   0.22.12
@backstage/plugin-auth-node                                      0.4.17, 0.5.1
@backstage/plugin-auth-react                                     0.1.5
@backstage/plugin-bitbucket-cloud-common                         0.2.22
@backstage/plugin-catalog-backend-module-bitbucket-server        0.2.1
@backstage/plugin-catalog-backend-module-scaffolder-entity-model 0.1.22
@backstage/plugin-catalog-backend                                1.25.2
@backstage/plugin-catalog-common                                 1.0.26
@backstage/plugin-catalog-graph                                  0.4.8
@backstage/plugin-catalog-import                                 0.10.10
@backstage/plugin-catalog-node                                   1.12.6
@backstage/plugin-catalog-react                                  1.12.3
@backstage/plugin-catalog                                        1.22.0
@backstage/plugin-events-node                                    0.3.10
@backstage/plugin-github-actions                                 0.6.16
@backstage/plugin-org                                            0.6.28
@backstage/plugin-permission-backend-module-allow-all-policy     0.1.21
@backstage/plugin-permission-backend                             0.5.48
@backstage/plugin-permission-common                              0.7.14, 0.8.1
@backstage/plugin-permission-node                                0.7.32, 0.8.2
@backstage/plugin-permission-react                               0.4.25
@backstage/plugin-proxy-backend                                  0.4.16
@backstage/plugin-scaffolder-backend-module-azure                0.1.16
@backstage/plugin-scaffolder-backend-module-bitbucket-cloud      0.1.14
@backstage/plugin-scaffolder-backend-module-bitbucket-server     0.1.14
@backstage/plugin-scaffolder-backend-module-bitbucket            0.2.14
@backstage/plugin-scaffolder-backend-module-gerrit               0.1.16
@backstage/plugin-scaffolder-backend-module-gitea                0.1.14
@backstage/plugin-scaffolder-backend-module-github               0.4.2
@backstage/plugin-scaffolder-backend-module-gitlab               0.4.6
@backstage/plugin-scaffolder-backend                             1.24.1
@backstage/plugin-scaffolder-common                              1.5.5
@backstage/plugin-scaffolder-node                                0.4.10
@backstage/plugin-scaffolder-react                               1.11.0
@backstage/plugin-scaffolder                                     1.24.0
@backstage/plugin-search-backend-module-catalog                  0.1.28, 0.2.1
@backstage/plugin-search-backend-module-techdocs                 0.1.27, 0.2.1
@backstage/plugin-search-backend-node                            1.3.1
@backstage/plugin-search-backend                                 1.5.16
@backstage/plugin-search-common                                  1.2.14
@backstage/plugin-search-react                                   1.7.14
@backstage/plugin-search                                         1.4.15
@backstage/plugin-signals-react                                  0.0.4
@backstage/plugin-tech-radar                                     0.7.4
@backstage/plugin-techdocs-backend                               1.10.12
@backstage/plugin-techdocs-common                                0.1.0
@backstage/plugin-techdocs-module-addons-contrib                 1.1.13
@backstage/plugin-techdocs-node                                  1.12.10
@backstage/plugin-techdocs-react                                 1.2.7
@backstage/plugin-techdocs                                       1.10.8
@backstage/plugin-user-settings-common                           0.0.1
@backstage/plugin-user-settings                                  0.8.11
@backstage/release-manifests                                     0.0.11
@backstage/test-utils                                            1.5.10
@backstage/theme                                                 0.5.6
@backstage/types                                                 1.1.1
@backstage/version-bridge                                        1.0.8
Done in 0.65s.
root@inmdlx100bs002:/data/backstage/backstage#
👀 Have you spent some time to check if this bug has been raised before?

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

🏢 Have you read the Code of Conduct?

[X] I have read the Code of Conduct

Are you willing to submit PR?
Yes I am willing to submit a PR!

I'm guessing that you are using the new backend system(there a bunch of backend.add(import ...) in your index.ts?
The docs for bitbucket server are referring to the old backend system. There's work in progress adding bitbucket server support here https://github.com/backstage/backstage/pull/26407 so I believe support for this module is going to land very soon.

authors: AnishAnil jhaals


text:
feat: (GitHub Issues Plugin) Dedicated plugin API to communicate with GitHub + correctly handle partial failures from GitHub API

Hey, I just made a Pull Request!
In this PR:

New plugin API - plugin.githubissues.service (all communication with GitHub API moved to the plugin API layer)
Thanks to the rewrite of the GitHub GrapQL API communication layer this PR introduces a local dev environment with test rendering data generated with @faker-js - making this plugin pacakge.json command yarn start work correctly
Fixes the error when GitHub GraphQL API returns partial failure (previously no issues were rendered) - the error from API is passed to the Backstage ErrorApi and the data returned by the API is rendered correctly here
Adds basic component test for correct rendering of the plugin - two scenarios - no data returned from API and single component successfully returned from API

Local DEV screenshot:

:heavy_check_mark: Checklist

[x] A changeset describing the change and affected packages. (more info)
[x] Added or updated documentation
[x] 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)

@jhaals all taken care off

Thanks for the help @jhaals! Was a bit bumpy but we made it 🙃 Cheers!

source: gharchive/pull-request

repo: backstage/backstage

license_type: permissive

license_source: github-api


text:
Update the SearchBar to make use of the useApp hook to retrieve the search icon specified in the createApp call

Hey, I just made a Pull Request!
The goal of this PR is to make use of the useApp hook in the SearchBar to retrieve the specified custom search icon provided to the Backstage createApp function. While implementing this change I noticed that all test cases of SearchBar as well as SearchAutocomplete were failing. This was due the test cases being wrapped by renderWithEffects instead of renderInTestApp. Finally, in order to test the implementation of the new search icon, I added the icons option to the renderInTestApp function. With this change I can verify that the custom search icon gets rendered when it is specified from createApp.
:heavy_check_mark: Checklist

[X] A changeset describing the change and affected packages. (more info)
[X] 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)

In the screenshot you're able to notice the Backstage icon now appearing in the search bar instead of the magnifying glass icon.

Awaiting review, so I wouldn't consider the PR to be stale. Please let me know if the PR is OK or if any changes are required. Thanks!

Thanks @awanlin for your comments, I've updated the PR with your suggestions.


text:
🚀 Copilot: Support for GitHub Organizations in addition to GitHub Enterprise.

Plugin Name
plugin-copilot & plugin-copilot-backend
🔖 Feature description
Support for fetching metrics for GitHub Organizations in addition to GitHub Enterprise.
🎤 Context
Currently, our implementation only supports GitHub Enterprise. However, many users and teams use GitHub Organizations for their repositories and projects and have no enterprise license. Adding support for GitHub Organizations would allow a broader range of users to benefit from the plugin.
✌ Possible Implementation
Some easy adjustments were made in this PR: https://github.com/dfl-aeb/community-plugins/pull/1/files
This would only allow to use either enterprise or orgs, which is totaly fine for my use case.
👀 Have you spent some time to check if this feature request has been raised before?

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

🏢 Have you read the Code of Conduct?

[X] I have read the Code of Conduct

Are you willing to submit PR?
Yes I am willing to submit a PR!

hey @dfl-aeb,
Thanks for your suggestion!
Currently there is a PR implementing that

I just found it too, sorry 🙈

source: gharchive/issue

authors: alissonfabiano dfl-aeb

repo: backstage/community-plugins


text:
README should mention how to integrate Slitter with existing project.

How does one use Slitter? Can one simply connect it to a project like Jemalloc? If not, can there be some example project showing Slitter's strenglths (maybe with a separate deliberately buggy example that demonstrates that Slitter crashes controllably more often compared to other allocactors)?

Hopefully https://github.com/backtrace-labs/slitter/blob/main/examples/demo.c is enough to get started and give you a taste.

authors: pkhuong vi

repo: backtrace-labs/slitter

license: MIT


text:
Detecting overriding same let in same rspec scope

Avoid copy-paste / grammar errors by detecting overriding same rspec let / let! / subject, e.g.
let(:a1) { 1 }
let(:a1) { 2 }

Expected behavior
This should create an offense:
let(:a1) { 1 }
let(:a1) { 2 }

Correct code could be:
let(:a1) { 1 }
let(:a2) { 2 }

Actual behavior
It doesn't create an offense
RuboCop version
0.47.1 (using Parser 2.3.3.1, running on ruby 2.3.3 x86_64-darwin16)

(mostly just a memo for myself to create this cop, originally filed there: https://github.com/bbatsov/rubocop/issues/4057)

I'd accept a cop for this. Also note that you can catch this in the meantime with by running rspec --warnings

@backus Oh thanks :) (--warnings produce 1420 lines in my case :) )
warning: method redefined; discarding old a1
warning: previous definition of a1 was here
warning: method redefined; discarding old a1
warning: previous definition of a1 was here

I would add detecting of let overwritting by a var in the example:
let(:a1) { 1 }

it 'is not used'
  a1 = 2
end

Not sure if it has to be the same cop

Correct code could be:
let(:a1) { 1 }
let(:a2) { 2 }

That would lead to a2 being an unused let. I’d say the correct code should be
let(:a1) { 2 }

authors: Darhazer Dorian backus bquorning

repo: backus/rubocop-rspec

license: mit

license_source: bigquery


text:
Depfu for Gitlab repos

:clipboard: Description
The Depfu service is using the /github/shields endpoint of Depfu, which means it can only query the status of Github repos. It would be nice to be able to query Gitlab repos.
:link: Data
Depfu also has a https://depfu.com/gitlab/shields/${userRepo} endpoint, which acts the same as the /github/shields endpoint, but for Gitlab repos.
:microphone: Motivation

While Depfu provides built-in badges, their style cannot be customized (e.g., ?style=flat-square), so it would be still useful to have this as a shields.io badge.

I think the way to do this will be to make new routes

/depfu/github/:userRepo+
/depfu/gitlab/:userRepo+

and then redirect /depfu/anything/else to /depfu/github/anything/else for backwards compatibility

Btw, I managed to find a workaround by using the underlying JSON endpoint directly, such as
https://img.shields.io/badge/dynamic/json?color=colorscheme&label=dependencies&query=text&url=https%3A%2F%2Fdepfu.com%2Fgitlab%2Fshields%2F{user}%2F{repo}&style=flat-square

But adding the routes would certainly be much nicer. I could try adding it myself, if I can manage to understand how redirectors and routes are set up. :slightly_smiling_face:

If you are interested in looking at it https://github.com/badges/shields/blob/c73072deed8eb6a5b9f51a06377f5f396ef21842/services/circleci/circleci.service.js is probably a good example to crib from

repo: badges/shields


text:
Why widget is not working for my server? widget disabled

I am testing this url and not working any ideas?
https://img.shields.io/discord/772774097734074388?label=Discord&logo=discord
my server : https://discord.com/servers/software-engineering-courses-secourses-772774097734074388

https://img.shields.io/discord/772774097734074388?label=Discord&logo=discord looks like it is working to me

Agreed, this seems live and functional so going to close. Feel free to follow up with any questions
https://img.shields.io/discord/772774097734074388?label=Discord&logo=discord

authors: FurkanGozukara calebcartwright chris48s


text:
Add kubernetes logo

Hi again,
Second proposal to add a logo: kubernetes!

Messages

:book:

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

:book:

:art: Thanks for submitting a logo. Please ensure your contribution follows our guidance for logo submissions.

  Generated by :no_entry_sign: dangerJS

I was thinking of using it as a kind of "kubernetes ready" badge.
Other people could use it to point to the namespace or the app name deployed like

or

Probably needs to be simplified as the docker logo :)

Usually we only accept logos which are directly related to a service badge. For example we've got several docker-related badges, so the logo you've submitted in your other PR #1750 is relevant to those service badges.
If you want to use other custom logos, you can do so by passing them as a base64 encoded string. For example, if I call
https://img.shields.io/badge/my%20namespace-my%20app-blue.svg?logo=data:image/svg%2bxml;base64,PHN2ZyB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciIHdpZHRoPSI3MjMiIGhlaWdodD0iNzAyIj48cGF0aCBkPSJNMzU5IDEwYTQ3IDQ2IDAgMCAwLTE4IDVMOTcgMTMxYTQ3IDQ2IDAgMCAwLTI1IDMyTDExIDQyNWE0NyA0NiAwIDAgMCA3IDM2IDQ3IDQ2IDAgMCAwIDIgM2wxNjkgMjExYTQ3IDQ2IDAgMCAwIDM3IDE3aDI3MWE0NyA0NiAwIDAgMCAzNy0xOGwxNjktMjEwYTQ3IDQ2IDAgMCAwIDktMzlsLTYxLTI2MmE0NyA0NiAwIDAgMC0yNS0zMkwzODIgMTVhNDcgNDYgMCAwIDAtMjMtNXoiIGZpbGw9IiMzMjZjZTUiLz48cGF0aCBkPSJNMzYxIDk5Yy04IDAtMTQgOC0xNCAxN3Y0bDIgMTRjMSAxMCAyIDE4IDEgMjZhMTYgMTYgMCAwIDEtNCA4bC0xIDZhMTg4IDE4OCAwIDAgMC0xMjIgNTlsLTUtNGMtMyAwLTUgMS05LTEtNi00LTEyLTExLTE5LTE4bC0xMC0xMC0zLTMtMTAtNGExNCAxNCAwIDAgMC0xMiA2Yy01IDYtMyAxNiA0IDIxbDMgMyAxMiA3IDIyIDE1IDMgOSA0IDRhMTg5IDE4OSAwIDAgMC0zMCAxMzJsLTYgMWMtMSAzLTQgNi02IDdsLTI2IDQtMTQgMS00IDFjLTkgMi0xNSAxMC0xMyAxOHMxMCAxMyAxOSAxMWgxbDMtMSAxMy01YzEwLTQgMTgtNyAyNi04IDMgMCA3IDIgOCAzbDctMWExOTAgMTkwIDAgMCAwIDg0IDEwNmwtMyA2IDIgOGExNDMgMTQzIDAgMCAxLTE0IDI0bC03IDEyLTIgNGMtNCA4LTEgMTcgNiAyMCA3IDQgMTYgMCAyMC04bDItNCA0LTEzYzQtMTAgNi0yMCAxMS0yNiAyLTIgNC0zIDctM2wzLTZhMTg5IDE4OSAwIDAgMCAxMzUgMGwzIDZjMyAwIDUgMSA4IDQgNCA3IDYgMTUgMTAgMjVsNCAxMyAyIDRjNCA4IDEzIDEyIDIwIDggNy0zIDEwLTEzIDYtMjFsLTItNC03LTExYTEzNyAxMzcgMCAwIDEtMTMtMjNjLTItNCAwLTcgMS05bC0zLTZjNDEtMjQgNzEtNjIgODUtMTA2bDYgMWMyLTEgNC0zIDgtMyA4IDEgMTYgNCAyNSA4bDE0IDVoNGM5IDIgMTctMiAxOS0xMHMtNC0xNi0xMy0xOGwtNC0xLTE0LTEtMjYtNC02LTctNi0xYTE4OSAxODkgMCAwIDAtMzEtMTMybDUtNWMxLTIgMC01IDMtOGwyMi0xNSAxMi03IDMtM2M3LTYgOS0xNSA0LTIyLTUtNi0xNS03LTIyLTFsLTMgMy0xMCAxMC0yMCAxOC04IDEtNiA0YTE5MiAxOTIgMCAwIDAtMTIxLTU5bC0xLTZjLTItMi00LTQtNS04bDItMjYgMi0xNHYtNGMwLTktNy0xNy0xNS0xN3ptLTE4IDExNGwtNCA3Ni0xIDFhMTMgMTMgMCAwIDEtMjAgMTBsLTYzLTQ1YTE1MSAxNTEgMCAwIDEgODgtNDJ6bTM3IDBhMTUyIDE1MiAwIDAgMSA4NyA0MmwtNjIgNDRhMTMgMTMgMCAwIDEtMjEtMTB6bS0xNDggNzFsNTggNTFoLTFhMTMgMTMgMCAwIDEtNSAyM2wtNzMgMjFhMTUxIDE1MSAwIDAgMSAyMS05NXptMjU4IDBhMTUzIDE1MyAwIDAgMSAyMiA5NWwtNzQtMjJhMTMgMTMgMCAwIDEtNS0yMmw1Ny01MXptLTE0MCA1NWgyM2wxNSAxOC01IDIzLTIxIDEwLTIyLTEwLTUtMjN6bTc1IDYzaDNsNzYgMTJhMTUxIDE1MSAwIDAgMS02MSA3N2wtMjktNzF2LTFhMTMgMTMgMCAwIDEgMTEtMTh6bS0xMjggMGExMyAxMyAwIDAgMSAxMiAxOGwtMjkgNzFhMTUxIDE1MSAwIDAgMS02MS03Nmw3Ni0xM2ExMyAxMyAwIDAgMSAyIDB6bTY0IDMxbDYgMWMzIDEgNSAzIDYgNmwzNyA2N2ExNTQgMTU0IDAgMCAxLTk3IDBsMzctNjdhMTMgMTMgMCAwIDEgMTEtN3oiIHN0eWxlPSJ0ZXh0LWluZGVudDowO3RleHQtYWxpZ246c3RhcnQ7bGluZS1oZWlnaHQ6bm9ybWFsO3RleHQtdHJhbnNmb3JtOm5vbmU7YmxvY2stcHJvZ3Jlc3Npb246dGI7bWFya2VyOm5vbmU7LWlua3NjYXBlLWZvbnQtc3BlY2lmaWNhdGlvbjpTYW5zIiBmb250LXdlaWdodD0iNDAwIiBjb2xvcj0iIzAwMCIgZmlsbD0iI2ZmZiIgb3ZlcmZsb3c9InZpc2libGUiIGZvbnQtZmFtaWx5PSJTYW5zIi8+PC9zdmc+

that will render.

Thanks for the PR, but i'm going to close this as there is currently no relevant badges.
Feel free to re-open this if you still think it should be merged.
Or if you want to add relevant badges we have a tutorial which should be helpful.


text:
A response size metric of an upstream service for dynamic badges like [dynamicyaml], (but not [jetbrains])

This PR adds a metric for response size of an upstream service for dynamic badges. I chose a histogram metric, mainly because in the histogram "Observations are very cheap as they only need to increment counters." (https://prometheus.io/docs/practices/histograms/). In histograms observations fall into buckets. Here we have buckets: 64kiB, 128kiB, ...,4MiB, 8MiB.
Dynamic badges fetch data from any source and for performance, reliability and security reasons fetch limit should be lower than 10MB (current limit). This metric should help us in determining the new limit.
How to test it?
METRICS_PROMETHEUS_ENABLED=true npm run start

# dynamic XML
curl "http://localhost:8080/badge/dynamic/xml.svg?color=red&label=label1&query=%2F%2Fname&url=https%3A%2F%2Fraw.githubusercontent.com%2Fhsz%2Fidea-gitignore%2Fmaster%2Fresources%2FMETA-INF%2Fplugin.xml"

# dynamic YAML
curl "http://localhost:8080/badge/dynamic/yaml.svg?color=red&label=label1&query=%24.trailingComma&url=https%3A%2F%2Fraw.githubusercontent.com%2Fbadges%2Fshields%2Fmaster%2F.prettierrc.yml"

# dynamic JSON
curl "http://localhost:8080/badge/dynamic/json.svg?color=red&label=label1&query=%24.name&url=https%3A%2F%2Fraw.githubusercontent.com%2Fbadges%2Fshields%2Fmaster%2Fpackage.json"

# results
curl "http://localhost:8080/metrics" -s | grep "service_response_bytes"

service_response_bytes_bucket{le="65536",category="dynamic",family="dynamic",service="dynamic_xml"} 1 ...
service_response_bytes_bucket{le="65536",category="dynamic",family="dynamic",service="dynamic_xml"} 1
service_response_bytes_bucket{le="131072",category="dynamic",family="dynamic",service="dynamic_xml"} 1
service_response_bytes_bucket{le="262144",category="dynamic",family="dynamic",service="dynamic_xml"} 1
service_response_bytes_bucket{le="524288",category="dynamic",family="dynamic",service="dynamic_xml"} 1
service_response_bytes_bucket{le="1048576",category="dynamic",family="dynamic",service="dynamic_xml"} 1
service_response_bytes_bucket{le="2097152",category="dynamic",family="dynamic",service="dynamic_xml"} 1
service_response_bytes_bucket{le="4194304",category="dynamic",family="dynamic",service="dynamic_xml"} 1
service_response_bytes_bucket{le="8388608",category="dynamic",family="dynamic",service="dynamic_xml"} 1
service_response_bytes_bucket{le="+Inf",category="dynamic",family="dynamic",service="dynamic_xml"} 1
service_response_bytes_sum{category="dynamic",family="dynamic",service="dynamic_xml"} 32529
service_response_bytes_count{category="dynamic",family="dynamic",service="dynamic_xml"} 1
service_response_bytes_bucket{le="65536",category="dynamic",family="dynamic",service="dynamic_yaml"} 1
service_response_bytes_bucket{le="131072",category="dynamic",family="dynamic",service="dynamic_yaml"} 1
service_response_bytes_bucket{le="262144",category="dynamic",family="dynamic",service="dynamic_yaml"} 1
service_response_bytes_bucket{le="524288",category="dynamic",family="dynamic",service="dynamic_yaml"} 1
service_response_bytes_bucket{le="1048576",category="dynamic",family="dynamic",service="dynamic_yaml"} 1
service_response_bytes_bucket{le="2097152",category="dynamic",family="dynamic",service="dynamic_yaml"} 1
service_response_bytes_bucket{le="4194304",category="dynamic",family="dynamic",service="dynamic_yaml"} 1
service_response_bytes_bucket{le="8388608",category="dynamic",family="dynamic",service="dynamic_yaml"} 1
service_response_bytes_bucket{le="+Inf",category="dynamic",family="dynamic",service="dynamic_yaml"} 1
service_response_bytes_sum{category="dynamic",family="dynamic",service="dynamic_yaml"} 84
service_response_bytes_count{category="dynamic",family="dynamic",service="dynamic_yaml"} 1
service_response_bytes_bucket{le="65536",category="dynamic",family="dynamic",service="dynamic_json"} 1
service_response_bytes_bucket{le="131072",category="dynamic",family="dynamic",service="dynamic_json"} 1
service_response_bytes_bucket{le="262144",category="dynamic",family="dynamic",service="dynamic_json"} 1
service_response_bytes_bucket{le="524288",category="dynamic",family="dynamic",service="dynamic_json"} 1
service_response_bytes_bucket{le="1048576",category="dynamic",family="dynamic",service="dynamic_json"} 1
service_response_bytes_bucket{le="2097152",category="dynamic",family="dynamic",service="dynamic_json"} 1
service_response_bytes_bucket{le="4194304",category="dynamic",family="dynamic",service="dynamic_json"} 1
service_response_bytes_bucket{le="8388608",category="dynamic",family="dynamic",service="dynamic_json"} 1
service_response_bytes_bucket{le="+Inf",category="dynamic",family="dynamic",service="dynamic_json"} 1
service_response_bytes_sum{category="dynamic",family="dynamic",service="dynamic_json"} 10959
service_response_bytes_count{category="dynamic",family="dynamic",service="dynamic_json"} 1

You may want to compare it with the previous approach https://github.com/badges/shields/pull/3662

Warnings

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

:warning:
This PR modified service code for dynamic but not its test code. That's okay so long as it's refactoring existing code.

:warning:

:books: Remember to ensure any changes to config.private in core/base-service/base.js are reflected in the server secrets documentation

Messages

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

  Generated by :no_entry_sign: dangerJS against 8717c1e59fa10b96ef01254289e7e62f9d67a48b

Thanks for the ping. I'll be travelling for a couple more days and still mostly AFK, but will follow up as soon as I can

Thank you @calebcartwright! Anyone else want to look at this or can I merge it?

authors: calebcartwright platan shields-ci


text:
Fix: forward slash -> backslash for ''

First of all, thank you for curl and the everything curl guide.
In two locations where the backslash (\) was used, there was "forward slash" mentioned. These two occurrences have been fixed.

Thanks!

authors: bagder steffenbusch

repo: bagder/everything-curl


text:
Add edit catalog image issue resolved

Description
On Add edit Catalog( product, category ) images placeholder adding issue is fixed

@akathuria289
Please resolve the conflicts

@akathuria289
Not working, the admin is not able to upload the product's image after merging this PR

@Sanjaybhattwebkul Please re-check

@akathuria289
Still not fixed, if we are uploading any image then there is a 404  error. Please find the screenshot Here

@akathuria289
Any update ?

@Sanjaybhattwebkul Please re-upload the screenshot URL

@abhishekkathuria
Not working, still getting 404 error, please find the screenshot Here

@abhishekkathuria
Any update?

@Sanjaybhattwebkul Resolved

@abhishekkathuria
Please resolve the conflicts

@abhishekkathuria
Please resolve the conflicts.

@abhishekkathuria
Any update?

@Sanjaybhattwebkul Resolved the conflict

Closing this PR as created new PR - https://github.com/bagisto/bagisto/pull/6649

repo: bagisto/bagisto


text:
imagenet_256_cc.yml runtime error

I'm trying to test the 256 ImageNet model on the deblurring task on the OOD data you provide in your adiacent repository. I'm getting this error:
ERROR - main.py - 2022-07-25 10:25:13,026 - Traceback (most recent call last):
  File "/Users/mbejan/Documents/diffusion/ddrm/main.py", line 164, in main
    runner.sample()
  File "/Users/mbejan/Documents/diffusion/ddrm/runners/diffusion.py", line 161, in sample
    self.sample_sequence(model, cls_fn)
  File "/Users/mbejan/Documents/diffusion/ddrm/runners/diffusion.py", line 249, in sample_sequence
    for x_orig, classes in pbar:
  File "/Users/mbejan/opt/anaconda3/envs/ddrm/lib/python3.10/site-packages/tqdm/std.py", line 1195, in __iter__
    for obj in iterable:
  File "/Users/mbejan/opt/anaconda3/envs/ddrm/lib/python3.10/site-packages/torch/utils/data/dataloader.py", line 438, in __iter__
    return self._get_iterator()
  File "/Users/mbejan/opt/anaconda3/envs/ddrm/lib/python3.10/site-packages/torch/utils/data/dataloader.py", line 384, in _get_iterator
    return _MultiProcessingDataLoaderIter(self)
  File "/Users/mbejan/opt/anaconda3/envs/ddrm/lib/python3.10/site-packages/torch/utils/data/dataloader.py", line 1048, in __init__
    w.start()
  File "/Users/mbejan/opt/anaconda3/envs/ddrm/lib/python3.10/multiprocessing/process.py", line 121, in start
    self._popen = self._Popen(self)
  File "/Users/mbejan/opt/anaconda3/envs/ddrm/lib/python3.10/multiprocessing/context.py", line 224, in _Popen
    return _default_context.get_context().Process._Popen(process_obj)
  File "/Users/mbejan/opt/anaconda3/envs/ddrm/lib/python3.10/multiprocessing/context.py", line 284, in _Popen
    return Popen(process_obj)
  File "/Users/mbejan/opt/anaconda3/envs/ddrm/lib/python3.10/multiprocessing/popen_spawn_posix.py", line 32, in __init__
    super().__init__(process_obj)
  File "/Users/mbejan/opt/anaconda3/envs/ddrm/lib/python3.10/multiprocessing/popen_fork.py", line 19, in __init__
    self._launch(process_obj)
  File "/Users/mbejan/opt/anaconda3/envs/ddrm/lib/python3.10/multiprocessing/popen_spawn_posix.py", line 47, in _launch
    reduction.dump(process_obj, fp)
  File "/Users/mbejan/opt/anaconda3/envs/ddrm/lib/python3.10/multiprocessing/reduction.py", line 60, in dump
    ForkingPickler(file, protocol).dump(obj)
AttributeError: Can't pickle local object 'Diffusion.sample_sequence.<locals>.seed_worker'

This is the script that creates the behaviour from above:
python main.py --ni \
  --config imagenet_256_cc.yml \
  --doc ood \
  --timesteps 20 \
  --eta 0.85 \
  --etaB 1 \
  --deg deblur_uni \
  --sigma_0 0.05 \

My imagenet_256_cc.yml is the same as the one your provide apart from the out_of _distribution argument, which is set to true.

#18 is related. I also have same error.

#18 is related. I also had the same error. Adding global seed_worker to Diffusion.sample_sequence in diffusion.py fails to resolve issue:
Traceback (most recent call last):
  File "<string>", line 1, in <module>
  File "C:\Users\shaw\Anaconda3\lib\multiprocessing\spawn.py", line 116, in spawn_main
    exitcode = _main(fd, parent_sentinel)
  File "C:\Users\shaw\Anaconda3\lib\multiprocessing\spawn.py", line 126, in _main
    self = reduction.pickle.load(from_parent)
AttributeError: Can't get attribute 'seed_worker' on <module 'runners.diffusion' from 'C:\\Users\\shaw\\Documents\\Year 2\\Diffusion Models\\ddrm\\runners\\diffusion.py'>

The reason (in my case) is that when running on Windows the multiprocessing module uses spawn and so one must (according to docs):

Wrap most of you main script’s code within if name == 'main': block, to make sure it doesn’t run again (most likely generating error) when each worker process is launched. You can place your dataset and DataLoader instance creation logic here, as it doesn’t need to be re-executed in workers.
Make sure that any custom collate_fn, worker_init_fn or dataset code is declared as top level definitions, outside of the main check. This ensures that they are available in worker processes. (this is needed since functions are pickled as references only, not bytecode.)

It is difficult to implement this advice since the seed_worker function needs access to the input args coming from the config file. Simplest "solution" was to just set the worker_init_fn argument to None as below (within Diffusion.sample_sequence):
val_loader = data.DataLoader(
            test_dataset,
            batch_size=config.sampling.batch_size,
            shuffle=True,
            num_workers=config.data.num_workers,
            worker_init_fn=None,
            generator=g,
        )

@lshaw8317  Hello, I have the same problem that occurs the error:
ForkingPickler(file, protocol).dump(obj)
AttributeError: Can't pickle local object 'Diffusion.sample_sequence.<locals>.seed_worker'

,and I tried to use your solution that I just set the worker_init_fn argument to None. However, after setting, the  tqdm bar (indicating sampling progress) freezes at 0% for a while, and eventually occurs a new error shown as below picture:

Did you encounter this new error? Did you know how to solve it?
Thanks a lot!

repo: bahjat-kawar/ddrm


text:
Flutter:  cache-sksl not working on iOS (TestFlight)

Sorry to disturb you, I saw your flutter issues
I used flutter build ios to generate .ipa
flutter build ios --release --bundle-sksl-path flutter_01.sksl.json

I can’t upload to TestFlight, he reported an error, I uploaded it directly using Xcode, and it succeeded
Error: code 1176 (App Store operation failed. Unable to process application at this time due to the following error: Invalid Provisioning Profile. The provisioning profile included in the bundle com.mhh.xxx [Payload/Runner.app] is invalid. [Missing code-signing certificate]. A Distribution Provisioning profile should be used when submitting apps to the App Store. For more information, visit the iOS Developer Portal..)

How did you upload it successfully?
thanks

Hi @paintingStyle ,
It seems a provisioning problem, which is related to your Apple Developer account, you need the correct provisioning profile to sign the bundle before you can upload it to Testflight/AppStore.
Maybe you don't have one or maybe you registered the wrong certificate/provisioning type.
The below stackoverflow issues may help:

https://stackoverflow.com/questions/19697237/invalid-provisioning-profile-missing-code-signing-certificate
https://stackoverflow.com/questions/34096279/which-certificate-type-and-provisioning-profile-type-should-i-use-for-test-fligh


text:
[Question] Validation Provider: Errors missing the field name

Sorry to bother you again, but
I am using the Validation Provider like this:
<ValidationProvider
        v-for="(field, index) in formFields"
        :key="index"
        v-slot="{ errors }"
        :rules="field.rules"
        mode="lazy"
      >
        <FormField
          v-model="form[field.name]"
          :error-messages="errors"
          :name="field.name"
          :label="field.label"
          :type="field.type"
          :title="field.title"
        />
      </ValidationProvider>

Now within my FormField component:
If I display
{{ errorMessages[0] }}
I will get something like this:
{field} must be a valid Email address.  (just translated from my localized German version).
Then thing is, that {field} is not the name of my field (in this case 'Email').
How can this be passed to the errorMessages array?
Your example here
<ValidationProvider vid="confirm" rules="required" v-slot="{ errors }">
  <VTextField v-model="passwordConfirm" type="password" :error-messages="errors" />
</ValidationProvider>

Seems to be doing the exact same thing, or am I missing something?
Thank you in advance.
Cheers

ValidationProvider can take a name prop which will replace the {field} placeholder.
<ValidationProvider
        v-for="(field, index) in formFields"
        :key="index"
        :name="field.name" <----- The field name
        v-slot="{ errors }"
        :rules="field.rules"
        mode="lazy"
      >
        <FormField
          v-model="form[field.name]"
          :error-messages="errors"
          :name="field.name"
          :label="field.label"
          :type="field.type"
          :title="field.title"
        />
      </ValidationProvider>

On point. thank you again. 👍🏼

authors: Jones-S logaretm

repo: baianat/vee-validate


text:
Add required_if rule

This adds the required_if rule. Fixes #41

Current coverage is 99.15% (diff: 75.00%)

Merging #81 into next will decrease coverage by 0.84%

@@           next        #81   diff @@
======================================
  Files        33         34     +1
  Lines       456        471    +15
  Methods     103        104     +1
  Messages      0          0
  Branches    129        135     +6
======================================
+ Hits        456        467    +11
- Misses        0          4     +4
  Partials      0          0

Powered by Codecov. Last update 70b30fc...3337337

@aXent Sorry it took that long, can you please rebase the branch to the latest changes so I can merge it?

Hi @logaretm, I'm working out some issues I've encountered using this rule in production. I'm closing this pull request and start a new one when these issues are solved. Thanks for looking into this! PR will be back soon.

@aXent Looking forward to it, thanks!

Any update on this PR?

@devonmather It is closed, rules are dynamic so you can simulate that with a dynamic expression to the directive instead of static one, like this example:
https://jsfiddle.net/logaretm/p0766ckj/

authors: aXent codecov-io devonmather logaretm


text:
sgx target_env

How the #[cfg(target_env = "sgx")] in libstd, libc etc. affects this SDK?
is this the dream of SGX being integrated into the SDK?
will this SDK someday leverage that to natively compile rust code into sgx?
i.e. https://github.com/rust-lang/rust/blob/f843ad60ef5a78d8b4da85c5007d3ecac229f1a8/src/libstd/sys/mod.rs#L44

I'm aware of that. Currently, Fortanix's solution occupies that.
I have several discussions with jethrob on github, where crates are merging commits to support their solutions. Currently the rust-lang/rust can checks target_env = "sgx" and target_vendor = "fortanix" at the same time to be compatible with our solutions.
Fortanix and my solution differ from the foundation -- whether or not use the Intel's codes, and, whether or not use the current design of libstd. The current design of libstd assumes that every target platform should provide time/net/env/thread/process/fs but sgx does not have that. So current targets in libstd only provide runtime panic. This happens when you write "std::fs::File::open" in the wasm target as well -- it panics but compiles. This is exactly what I'm trying to prevent. So Fortanix and I choose different ways for the tradeoff between usability and safety/security. Their codes are easy to use -- but hides too much info to become trustworthy. See my gif below until it ends.
https://dingelish.com/record.gif
The rustc compile, or the combination of "cargo + libstd" has to change to help embedded systems generating compile-time warning/faults instead of making unsupported APIs runtime panics. I proposed an pre-rfc for it at here. But I don't have time for it now.

Yes, I know about the different assumptions which is why we chose your sdk. For now I prefer it to be intel bindings than pure rust, at least as it's not a big well maintained well reviewed project.
I was just cirious if you could leverage their work to help prevent the need to fork dependencies some day.
Thanks for your work!

:-)
I do have the plan to reorg this and push this to the upstream, as long as I can generate compile-time warnings for unsupported functions!

authors: dingelish elichai

repo: baidu/rust-sgx-sdk


text:
#322 prop_tree: parse failed if input string is empty

#322

commit msg里加上issue号吧，git log的时候方便追查

authors: lylei xupeilin

repo: baidu/tera


text:
Fixes matches for Fedora / Kali-like ifconfig outputs

A few matches don't seem to work nicely on Kali linux, and also looking around the web fedora does the same output style with ifconfig.  This solves it as cleanly as I can for the two "ifconfig flavors" I've seem to come across..  on a side note, the kali / fedora way of doing it also has a ':' after the interface name.  Taking in this pull request would greatly simplify my program lol.  I will work on other aspects of your code as I continue writing my app and find any other inconsistencies... (iwconfig, for example?)

Not sure why this disrupted here. Any insights?

repo: bakerface/wireless-tools


text:
fix: sync minimum swap fee percentage in ConstantSumPool.sol with ConstantProductPool.sol

Updated value and comment for _MIN_SWAP_FEE_PERCENTAGE in ConstantSumPool.sol to 1e12 (0.0001%)
Updated comment for _MIN_SWAP_FEE_PERCENTAGE in ConstantProductPool.sol to reflect the true value of 0.0001%

cc @MattPereira
I hope this is the same person as matthu.eth on Discord, or this tag is going to seem really weird 😅


text:
Use "npm ci" instead of "npm install" to speed up CI

Read more: https://docs.npmjs.com/cli/ci

Resolved with PR #83 .

repo: balassy/aws-lambda-typescript


text:
batch delete with waterline?

is this possible? like sending an id array to Model.destroy();
Regards

destroy uses the same Waterline query language as the rest of the model methods.  If you want to batch delete models by ID, set the id criteria to an array:
Model.destroy({id: [array of ids]}).exec(...);

repo: balderdashy/sails


text:
Remove default socket on connect event message in browser or node js in production env

Sails version: 1.0.2
Node version: v8.11.3
NPM version: 6.2.0
DB adapter name: N/A
DB adapter version: N/A
Operating system: Ubuntu 16.04
Is that possible to remove default socket on connect event message in browser or node js in production env? Because currently i am using my own .connect & disconnect event. So that it will be clear.
But whenever client connect to socket server it showing both the default message along with my custom connect & disconnect.

Are you sending environment flag to set it to production mode?
It should not show this logs when data-environment=production is provided to sails.io.js
See https://sailsjs.com/documentation/reference/web-sockets/socket-client#?basic-configuration-using-html-attributes for details.

@umarfarook882 Happy to hear its working for you now!
@luizcarraro Thank you so much for helping a fellow Sails.js sailor!

authors: luizcarraro raqem umarfarook882


text:
Remove camelCase of table name for some database, ex: couchdb.

Here is the issue: https://github.com/balderdashy/waterline-adapter-tests/issues/21

I'm proposing in the couchdb adapter to simply work around this: https://github.com/tjwebb/sails-couchdb-orm/commit/39a34386ed5f00c8a43d0e70241370768d1b2bb4.
If a camelCase table name causes stuff to break, we need to know about it, so I think this test should remain.

Closing this as unresponsive, please reopen if you want to resume the issue/discussion. Thanks

authors: Powpow-Shen dmarcelino tjwebb

repo: balderdashy/waterline-adapter-tests


text:
Crash debugging UE4.26 shaders.

Description
RD tends to crash when debugging shaders with UE4.26. I switched back to RD1.18 and it's not crashing.

Steps to reproduce

Set UE4 cvars to turn off optimizeation and keep debug info. Enable RD plugin in UE4.
Launch RD from UE4.
Find a drawcall and a pixel and click Debug, and debug...
Sometimes it shows some assembly-ish code and crashes right away (Usually UE shaders, like AO). Sometimes it shows hlsl source and doesn't crash until a couple of step over/intos (Usually user created shaders, Base Pass).

Environment

RenderDoc version: 1.19
Operating System: Win10 21H2
Graphics API: DX11

I can confirm that this crash isn't specific to Unreal Engine. It's happening with my own renderer as well.
I've tracked it down to the function ShaderViewer::makeSourceVariableNode()
In that function, the debug variables are retrieved and stored in a variable
const ShaderVariable *reg = GetDebugVariable(r);
The code then adds RDTreeWidgetItem entries in the children list declared at line 4438. But it only inserts an entry into the list if reg->members is NOT empty.
If it is, then the children list remains empty.
Then at 4639 this code is run
  for(RDTreeWidgetItem *c : children)
    node->addChild(c);

This adds the children in the node's member variable m_children.
Again, this does not occur if children is empty.
The crash occurs at line 4652
    for(uint32_t i = 0; i < childCount; i++)
      node->child(i)->setText(1, getRegNames(node, ~0U, i));

This is because the algorithm does NOT check to see if the node has any children before trying to iterate through them, thus leading to a crash.
Here is the output in the console when this crash occurs

QTRD 026300: [17:58:24]            qvector.h( 427) - Fatal   - ASSERT failure in QVector::operator[]: "index out of range", file A:\Git\renderdoc\qrenderdoc\3rdparty\qt\include\QtCore\qvector.h, line 427
The thread 0x8844 has exited with code 0 (0x0).

This was an issue handling matrix source variables on D3D where each row/column of the matrix maps to a different register. That commit should fix the issue.

repo: baldurk/renderdoc


text:
Does not support index buffer with glVertexArrayElementBuffer

Specifying index buffer with OpenGL 4.5 function glVertexArrayElementBuffer doesn't work in RenderDoc(0.29 Win64).  If I replace the glVertexArrayElementBuffer with glBindVertexArray() followed by glBindBuffer(GL_ELEMENT_ARRAY_BUFFER, ...) then the index buffer is captured correctly in RenderDoc.

Do you have a repro sample showing the bug you can share? Eyeballing the code I don't see anything obviously standing out as wrong so I'll have to construct something to test it, and there's the chance I might not make my sample in the same way as yours and it won't repro the bug.

Hi thanks for the quick response.  I made a repo for you that shows this problem: https://github.com/finalpatch/rd278
Sorry for the language used being Pascal. You will need the Lazarus IDE if you want to build it. I have only tested this on Windows 10 x64.
In the file glhelpers.pas,  there is a line near the beginning "{$define RENDERDOC}".  If the RENDERDOC path is enabled, RenderDoc captures the index buffer. Otherwise RenderDoc is unable to capture the index buffer.  Either way, the rendering result in the window looks correct.

I think that should do the trick (ignore the commit listed twice). I was binding a buffer to the VAO without properly restoring the previous binding, so for this case where the bind is part of VAO state I was trashing it.
I also fixed an issue where buffers created via glCreate() and never going via glBindBuffer*() would be wrongly listed as 'uninitialised buffer' in the UI.
Let me know if that sorts it out for you.

Just tried the latest nightly, works flawlessly. Thanks a lot!

authors: baldurk finalpatch


text:
0.31 integrated in UE4 will prevent Swarm from running

Hello,
Using 0.31 in UE4 4.12 through the the plugin (https://github.com/Temaran/UE4RenderDocPlugin) will prevent Swarm from running.
It crashes with this callstack:

        UE4Editor-SwarmInterface-Win64-Debug.dll!NSwarm::FSwarmInterfaceImpl::InitSwarmInterfaceManaged(const wchar_t * SwarmInterfaceDLLPath) Line 560                C++

           UE4Editor-SwarmInterface-Win64-Debug.dll!NSwarm::FSwarmInterface::Initialize(const wchar_t * SwarmInterfacePath) Line 75     C++
           UE4Editor-UnrealEd-Win64-Debug.dll!FStaticLightingSystem::CreateLightmassProcessor() Line 1844       C++
           UE4Editor-UnrealEd-Win64-Debug.dll!FStaticLightingSystem::BeginLightmassProcess() Line 577 C++
           UE4Editor-UnrealEd-Win64-Debug.dll!FStaticLightingManager::CreateStaticLightingSystem(const FLightingBuildOptions & Options) Line 223            C++
           UE4Editor-UnrealEd-Win64-Debug.dll!UEditorEngine::BuildLighting(const FLightingBuildOptions & Options) Line 2310             C++
           UE4Editor-UnrealEd-Win64-Debug.dll!FEditorBuildUtils::EditorBuild(UWorld * InWorld, FName Id, const bool bAllowLightingDialog) Line 339   C++
           UE4Editor-LevelEditor-Win64-Debug.dll!FLevelEditorActionCallbacks::BuildLightingOnly_Execute() Line 568                C++
           UE4Editor-LevelEditor-Win64-Debug.dll!TBaseStaticDelegateInstance<TTypeWrapper<void> __cdecl(void)>::Execute() Line 953          C++
           UE4Editor-LevelEditor-Win64-Debug.dll!TBaseStaticDelegateInstance<void __cdecl(void)>::ExecuteIfSafe() Line 1021             C++
           UE4Editor-Slate-Win64-Debug.dll!TBaseDelegate<void>::ExecuteIfBound() Line 608       C++
           UE4Editor-Slate-Win64-Debug.dll!FUICommandList::ExecuteAction(const TSharedRef<FUICommandInfo const ,0> InUICommandInfo) Line 88      C++
           UE4Editor-Slate-Win64-Debug.dll!SMenuEntryBlock::OnClicked(bool bCheckBoxClicked) Line 1027          C++
           UE4Editor-Slate-Win64-Debug.dll!SMenuEntryBlock::OnMenuItemButtonClicked() Line 987        C++
           UE4Editor-Slate-Win64-Debug.dll!TMemberFunctionCaller<SMenuEntryBlock,FReply (__cdecl SMenuEntryBlock::*)(void) __ptr64>::operator()<>() Line 161   C++
           UE4Editor-Slate-Win64-Debug.dll!TTupleImpl<TIntegerSequence<unsigned int> >::ApplyAfter_ExplicitReturnType<FReply,TMemberFunctionCaller<SMenuEntryBlock,FReply (__cdecl SMenuEntryBlock::*)(void) __ptr64> >(TMemberFunctionCaller<SMenuEntryBlock,FReply (__cdecl SMenuEntryBlock::*)(void)> && Func) Line 128 C++
           UE4Editor-Slate-Win64-Debug.dll!TBaseSPMethodDelegateInstance<0,SMenuEntryBlock,0,FReply __cdecl(void)>::Execute() Line 321          C++
           UE4Editor-Slate-Win64-Debug.dll!TBaseDelegate<FReply>::Execute() Line 521  C++
           UE4Editor-Slate-Win64-Debug.dll!SButton::OnMouseButtonUp(const FGeometry & MyGeometry, const FPointerEvent & MouseEvent) Line 275 C++
           UE4Editor-Slate-Win64-Debug.dll!SMenuEntryButton::OnMouseButtonUp(const FGeometry & MyGeometry, const FPointerEvent & MouseEvent) Line 382       C++
           UE4Editor-Slate-Win64-Debug.dll!FSlateApplication::RoutePointerUpEvent::__l8::<lambda>(const FArrangedWidget & TargetWidget, const FPointerEvent & Event) Line 4618         C++
           UE4Editor-Slate-Win64-Debug.dll!FEventRouter::Route<FReply,FEventRouter::FToLeafmostPolicy,FPointerEvent,FReply <lambda>(const FArrangedWidget &, const FPointerEvent &) >(FSlateApplication * ThisApplication, FEventRouter::FToLeafmostPolicy RoutingPolicy, FPointerEvent EventCopy, const FSlateApplication::RoutePointerUpEvent::__l8::FReply <lambda>(const FArrangedWidget &, const FPointerEvent &) & Lambda) Line 215         C++
           UE4Editor-Slate-Win64-Debug.dll!FSlateApplication::RoutePointerUpEvent(FWidgetPath & WidgetsUnderPointer, FPointerEvent & PointerEvent) Line 4607               C++
           UE4Editor-Slate-Win64-Debug.dll!FSlateApplication::ProcessMouseButtonUpEvent(FPointerEvent & MouseEvent) Line 5061 C++
           UE4Editor-Slate-Win64-Debug.dll!FSlateApplication::OnMouseUp(const EMouseButtons::Type Button, const FVector2D CursorPos) Line 5041                C++
           UE4Editor-Core-Win64-Debug.dll!FWindowsApplication::ProcessDeferredMessage(const FDeferredWindowsMessage & DeferredMessage) Line 1510      C++
           UE4Editor-Core-Win64-Debug.dll!FWindowsApplication::DeferMessage(TSharedPtr<FWindowsWindow,0> & NativeWindow, HWND__ * InHWnd, unsigned int InMessage, unsigned __int64 InWParam, __int64 InLParam, int MouseX, int MouseY, unsigned int RawInputFlags) Line 1850      C++
           UE4Editor-Core-Win64-Debug.dll!FWindowsApplication::ProcessMessage(HWND__ * hwnd, unsigned int msg, unsigned __int64 wParam, __int64 lParam) Line 802             C++
           UE4Editor-Core-Win64-Debug.dll!FWindowsApplication::AppWndProc(HWND__ * hwnd, unsigned int msg, unsigned __int64 wParam, __int64 lParam) Line

Using 0.30 will not give this error.

Looking at the code on UE4's side, it seems like this initialises CLR and so it is quite possible that it runs into  this bug.
Can you try the latest nightly build and see if it works for you?

Thanks for the answer! I'll wait for the next release, as I can't allocate more time in the upgrade now :(
Cheers!
Alex

I forgot to comment on this when I released it, but v0.32 came out last week. If this isn't fixed there then let me know.

Thanks very much! I'll let you know as soon as I can try another update :)

authors: baldurk monops


text:
Update contracts digest to f32bce9

This PR contains the following updates:

Package
Update
Change

contracts
digest
93ba80c -> f32bce9

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ 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.

Can one of the admins verify this patch?

authors: balena-ci resin-jenkins

repo: balena-os/balena-odroid


text:
worker: install edk2 firmware for aarch64

Change-type: patch
Signed-off-by: Joseph Kogut joseph@balena.io

@jakogut with this change there seems to be no OVMF/AAVMF files in the image.

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

authors: jakogut klutchell

repo: balena-os/leviathan


text:
Invalid syntax highlighting when defaultable array parameter in a function

Description:
When a ballerina function have a nullable and dafaultable array as a parameter, the next parameter is highlighted incorrectly. See below image:

Same behaviour is observed when the first parameter is a string[]? and have a default value of ().
Steps to reproduce:
Try below code:
public function sample(int[]? sampleArray = (), int sampleValue = 0) {

}

If you remove the default value from the function parameter, this works as expected:
public function sample(int[]? sampleArray, int sampleValue = 0) {

}

Affected Versions:
VSCode plugin 1.2.4
Ballerina 1.2.4

This issue is associated with the VSCode plugin. Since a separate issue has been created, closing this issue

authors: ThisaruGuruge nadeeshaan

repo: ballerina-platform/ballerina-lang


text:
Testarina code coverage report is skipping lines

Description:
We were waiting for the test coverage in resource functions and happy to see that since alpha versions but we noticed that in the report some lines are skipping and we want to know that is affecting the code coverage.
Steps to reproduce:

Affected Versions:
Ballerina swan lake alpha 5

I was able to reproduce the above behavior in a simple Ballerina project.
https://github.com/Dilhasha/service-test-repo

We were able to reproduce the issue for above case 1 in a simple function and it seems to be an issue with the bal to java conversion because it's showing some coverage even when we generate test report using JaCoCo directly.
Created https://github.com/ballerina-platform/ballerina-lang/issues/31061

Closing since this will be tracked by #31061

authors: Dilhasha LakshanKarunathilake azinneera


text:
Unable to stop compilation from compiler plugins

Description:

The dlog with Diagnostic.Kind.ERROR should stop the compilation.
dlog.logDiagnostic(Diagnostic.Kind.ERROR, endpointNode.getPosition(), e.getMessage());

This is not working at the moment. Even though the kind is set as an error from the plugin, the compiler prints the error and continues.

There should be a logDiagnostic method that doesn't require position as a parameter as well.

Steps to reproduce:

Create a compiler plugin and dlog an error.

Affected Versions:
0.970.0-alpha0
OS, DB, other environment details and versions:
Mac OS
Suggested Labels (optional):
Bug, L1/L2 for May
Suggested Assignees (optional):
SameeraJ

Fixed in https://github.com/ballerina-platform/ballerina-lang/commit/e51fa1b3bfee0ba9238a79c4781b8e618e85ed4e.


text:
Improvements to provide proper error messages for invalid streaming window types

Purpose

To add fix for https://github.com/ballerina-platform/ballerina-lang/issues/12747..

Codecov Report

:exclamation: No coverage uploaded for pull request base (release-0.990.0@4e1ac35). Click here to learn what that means.
The diff coverage is 87.5%.

@@                Coverage Diff                 @@
##             release-0.990.0   #12793   +/-   ##
==================================================
  Coverage                   ?   59.86%
  Complexity                 ?      659
==================================================
  Files                      ?     2067
  Lines                      ?   101570
  Branches                   ?    12929
==================================================
  Hits                       ?    60803
  Misses                     ?    35584
  Partials                   ?     5183

Impacted Files
Coverage Δ
Complexity Δ

...inalang/compiler/desugar/StreamingCodeDesugar.java
97.5% <87.5%> (ø)
0 <0> (?)

Continue to review full report at Codecov.

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

authors: codecov-io mohanvive


text:
Add suggested improvements to thread based strand scheduler

Purpose

Address code review suggestions in PR https://github.com/ballerina-platform/ballerina-lang/pull/20115
Fixes #

Approach

Describe how you are implementing the solutions along with the design details.

Samples

Provide high-level details about the samples related to this feature.

Remarks

List any other known issues, related PRs, TODO items, or any other notes related to the PR.

Check List

[ ] Read the Contributing Guide
[ ] Required Balo version update
[ ] Updated Change Log
[ ] Checked Tooling Support (#)
[ ] Added necessary tests

[ ] Unit Tests
[ ] Spec Conformance Tests
[ ] Integration Tests
[ ] Ballerina By Example Tests

[ ] Increased Test Coverage
[ ] Added necessary documentation

[ ] API documentation
[ ] Module documentation in Module.md files
[ ] Ballerina By Examples

Codecov Report

Merging #20176 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master   #20176   +/-   ##
=======================================
  Coverage    19.9%    19.9%
=======================================
  Files          55       55
  Lines        1437     1437
  Branches      218      218
=======================================
  Hits          286      286
  Misses       1138     1138
  Partials       13       13

Continue to review full report at Codecov.

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


text:
Unable to retrieve binary payload from large file response

Description:
Unable to retrieve binary payload from ~5MB file response using getBinaryPayload.  This is an intermittent error.
Error log
error("Error occured while accessing binary content from the http response",error GenericClientError
("Error occurred while retrieving the binary payload from the response", error ParserError ("Error occurred while
extracting content from message : Idle timeout triggered while reading inbound response entity body")))

Identified following records in the Wireshark.

Steps to reproduce:

Upload a large file(>5MB) in an AWS S3 bucket and call getObject() method
This getObject() method internally uses getBinaryPayload to retrieve the payload from the response.

import ballerina/log;
import ballerina/lang.'string as strings;
import ballerinax/aws.s3;

string accessKeyId = "";
string secretAccessKey = "";
string region = "";
string bucketName = "";

s3:ClientConfiguration amazonS3Config = {
    accessKeyId: accessKeyId,
    secretAccessKey: secretAccessKey,
    region: region
};

s3:Client amazonS3Client = check new (amazonS3Config);

public function main() returns error? {
    var getObjectResponse = amazonS3Client->getObject(bucketName, "large.csv");
    if (getObjectResponse is s3:S3Object) {
        log:printInfo(getObjectResponse.toString());
        byte[]? byteArray = getObjectResponse["content"];
        if (byteArray is byte[]) {
            string content = check strings:fromBytes(byteArray);
            log:printInfo("Object content: " + content);
        }
    } else {
        log:printError("Error: " + getObjectResponse.toString());
    }
}

Affected Versions:
SL Beta2
Related Issues (optional):
https://github.com/wso2-enterprise/choreo/issues/7935

@Chuhaa Thanks for the info. By any chance can we get a complete wireshark record from Client SYN?

Please find the complete Wireshark record here


text:
GraalVM image generation failed due to quartz scheduler

Description:
Accoring to [1] Quartz use RMI's ObjID with run-time initialization. Due to that Quartz couldn't be used in applications where is required native image compilation by GraalVM. One workeround would be to use https://quarkus.io/guides/scheduler
more info on [2] [3] . [4] has complete stacktrace
[1] https://github.com/oracle/graal/issues/1125
[2] https://stackoverflow.com/questions/60258087/java-scheduler-that-works-with-native-image-compilation-by-graalvm
[3] https://quarkus.io/guides/scheduler
[4]
Caused by: com.oracle.graal.pointsto.constraints.UnsupportedFeatureException: No instances of sun.security.provider.NativePRNG are allowed in the image heap as this class should be initialized at image runtime. Object has been initialized without the native-image initialization instrumentation and the stack trace can't be tracked.
Detailed message:
Trace: Object was reached by
reading field java.security.SecureRandom.secureRandomSpi of
constant java.security.SecureRandom@26041238 reached by
scanning method java.rmi.server.ObjID.(ObjID.java:119)
Call path from entry point to java.rmi.server.ObjID.():
at java.rmi.server.ObjID.(ObjID.java:111)
at sun.rmi.transport.LiveRef.(LiveRef.java:74)
at sun.rmi.server.UnicastServerRef.(UnicastServerRef.java:168)
at java.rmi.server.UnicastRemoteObject.exportObject(UnicastRemoteObject.java:320)
at org.quartz.core.QuartzScheduler.bind(QuartzScheduler.java:372)
at org.quartz.core.QuartzScheduler.initialize(QuartzScheduler.java:235)
at org.quartz.impl.StdSchedulerFactory.instantiate(StdSchedulerFactory.java:1360)
at org.quartz.impl.StdSchedulerFactory.getScheduler(StdSchedulerFactory.java:1559)
at org.ballerinalang.stdlib.task.objects.TaskManager.getScheduler(TaskManager.java:56)
at org.ballerinalang.stdlib.task.objects.AbstractTask.resume(AbstractTask.java:153)
at org.ballerinalang.stdlib.task.actions.TaskActions.resume(TaskActions.java:59)
at ballerina.task.1_1_0.listener.resumeExternal(listener.bal:132)
at ballerina.task.1_1_0.$value$Scheduler.resume(scheduler.bal:92)
at ballerina.task.1_1_0.$value$Scheduler.call(scheduler.bal)
at ballerina.system.0_6_0.$value$Process.$doPipe$lambda$0$(process.bal)
at ballerina.system.0_6_0.$value$Process$$Lambda$94/1179751225.apply(Unknown Source)
at org.ballerinalang.stdlib.log.AbstractLogFunction$1.get(AbstractLogFunction.java:74)
at org.ballerinalang.stdlib.log.AbstractLogFunction$1.get(AbstractLogFunction.java:65)
at com.oracle.svm.core.jdk.SystemPropertiesSupport.initializeLazyValue(SystemPropertiesSupport.java:190)
at com.oracle.svm.core.jdk.SystemPropertiesSupport.getProperty(SystemPropertiesSupport.java:143)
at com.oracle.svm.core.jdk.Target_java_lang_System.getProperty(JavaLangSubstitutions.java:345)
at com.oracle.svm.jni.JNIJavaCallWrappers.jniInvoke_VARARGS:Ljava_lang_System_2_0002egetProperty_00028Ljava_lang_String_2_00029Ljava_lang_String_2(generated:0)
at com.oracle.graal.pointsto.constraints.UnsupportedFeatures.report(UnsupportedFeatures.java:126)
at com.oracle.svm.hosted.NativeImageGenerator.runPointsToAnalysis(NativeImageGenerator.java:750)
... 7 more

I think we can also this as we are no longer actively working on this direction.

authors: shafreenAnfar warunalakshitha


text:
Add build failure notification

Description
Sends build failure message to notification chat
Fixes # (issue)
Related Pull Requests (remove if not relevant)

Pull request 1
Pull request 2

One line release note:

One line describing the feature/improvement/fix made by this PR

Type of change
Please delete options that are not relevant.

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

[ ] Test A
[ ] Test B

Test Configuration:

Ballerina Version:
Operating System:
Java SDK:

Checklist:
Security checks

[ ] Followed secure coding standards in http://wso2.com/technical-reports/wso2-secure-engineering-guidelines?
[ ] Confirmed that this PR doesn't commit any keys, passwords, tokens, usernames, or other secrets?

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.Charuka Tharindu seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


text:
Intermittent errors in loading packages in tools distribution

Not related to core. Hence moving the issue to composer

repo: ballerinalang/ballerina


text:
Device tracker for o2box

This PR adds support for the O2Box, similar to the one shown here:
https://hilfe.o2online.de/docs/DOC-1332

Addressed the comments, updated to dev

Can you add your file to .coveragerc and it seems that CI reported some style violations: https://travis-ci.org/balloob/home-assistant/jobs/102450052#L187-L214

This is an automated response to help you succeed in getting this PR merged.

Whenever CI fails, the reason for failing will be at the bottom of the log. Each Python version performs different tests so it can be that only Python 3.5 fails. Your PR cannot be merged unless CI is green!
Always make sure your fork is up to date before you create a new branch. No "merge upstream" or "merge dev" commits. Also rebase on the dev branch before creating a PR.
Squash your commits when the PR is ready to be merged.

If your code communicates with devices:

Use a 3rd party library for communication. Add dependencies via REQUIREMENTS variable (example).
Only import your 3rd party dependencies inside functions that use it (example).
Run script/gen_requirements_all.py to update requirements_all.txt.
Add your new files to .coveragerc

If your code does not depend on external devices:

Write tests to verify your code works

Closing this PR as it has gone stale.

authors: balloob chrido

repo: balloob/home-assistant


text:
Feat/add favicons

Closes #
{{short description}}
Acceptance Criteria

[ ] Design Review by @Gagne87, @clastzoo
[ ] Technical Review by @hirsch88, @mladenplaninicic, @nobilo
[ ] Style Guide Review @hirsch88, @mladenplaninicic, @nobilo
[ ] Visual test done by @hirsch88, @nobilo, @mladenplaninicic, @Gagne87, @clastzoo
[ ] Functional test done by @hirsch88, @nobilo, @mladenplaninicic
Browser Testing by @hirsch88, @nobilo, @mladenplaninicic, @Gagne87, @clastzoo

Desktop

[ ] Chrome
[ ] Edge
[ ] Safari
[ ] Firefox

Tablet

[ ] iPad (Landscape / Portrait)

Mobile

[ ] Safari iOS
[ ] Chrome Preview

I guess we should also add in documentation instructions with post-install copy  job as we have for icons :)

authors: mladenplaninicic nobilo

repo: baloise-incubator/design-system


text:
virtueller Baloise Open Day - Beitrag: Open-Source - 24.08

Wir sind Versicherung und Bank in einem und das mit über 150 Jahren Tradition. Mindestens ähnlich alt ist die Idee des Gemeinguts, oder Allmende.
Im Zeitalter der Digitalisierung ergeben sich für diese altbewährten Konzepte neue Chancen. Denn die sogenannte Wissensallmende, also digitalisierte Ideen und Informationen, hat einen entscheiden Vorteil: im Unterschied zu Acker- oder Weideland verlieren Informationen durch intensive Nutzung nicht an Wert. Im Gegenteil: die gemeinsame Nutzung und Pflege solcher Güter lohnt sich heute mehr denn je - Stichwort Open-Source!
Wie wir das bei der Basler leben und was wir in den letzten Jahren schon erreicht haben, wollen wir euch sehr gerne zeigen!

Agenda

Was ist Wissensallmende / Open-Source

(sehr) bekannte Beispiele: Wikipedia, Android von Google, OpenStreetMaps

Welche Arten der Nutzung / Interaktion gibt es: DENY, USE, CONTRIBUTE, CHAMPION
Wo sind wir wie aktiv (gewesen)
Highlights: https://parcandi.ch, Open-Source Community, Mitwirken bei CH Open, Open-Insurance, CXO Appreciation

Wie viel Geld haben wir gespart? : Oloh - SCA : Hochrechnung

https://gitpitch.com/baloise/open-source/master?p=docs/slides/baloise-open-day

Recording added via e9df2fdce4a6fd61cae0ba483b76a9a05b748d14

repo: baloise/open-source


text:
Add a collection to the index

Collection name
a
Maintainer name
b
Maintainer contact link (i.e. repo issues link, email)
c
Repository URL
d
OCI Reference
aaaaaaa
I acknowledge that this collection provides new functionality, distinct from the existing dev container collections part of this index

[x] Confirm

#sign-off


text:
怎么刷新TZPhotoPickerController？

TZImagePickerController的selectedModels增加或移除元素后怎么刷新TZPhotoPickerController？

直接 [_collectionView reloadData]; 不可以吗？

TZPhotoPickerController类的对象并没有声明出来，怎么取其collectionView？

TZPhotoPickerController控制器都没创建，那为何要去刷新它？
TZPhotoPickerController控制器创建的时候，会走initSubviews方法，里面会调用checkSelectedModels方法，已经会根据TZImagePickerController中selectedModels的值来绘制界面。

我弄了个TZPhotoPickerController的全局变量，每次present的都是同一个对象，所以才需要刷新。

实在不行就把源码改一下，把属性拿到头文件里。

authors: DeTong banchichen vmei123

repo: banchichen/TZImagePickerController


text:
真机上,第一次授权,选择是,显示空白

真机上,第一次授权,选择是,显示空白,得第二次进入,才能正常显示,不知道是什么原因,能解决下嘛,谢谢

ios版本是ios9.1

我自己土方法修复了一下,希望坛主官方修复下

你好，这个是很久之前的一个问题的，请更新到新版本试试~新版本不会有这个问题的~


text:
UI - Swap

Tabs design  - tabs should be connected
Please remove separation line
Please fix input box design
Please change arrow/swap icons
Please change inactive button color/style

[ ]     Tabs design - tabs should be connected
[ ]     Please remove separation line
[ ]     Please fix input box design
[ ]     Please change arrow/swap icons
[ ]     Please change inactive button color/style

@pingustar Looks great

@pingustar i am checking staging and dont see any of these changes.

What do you see?

[ ] add recipient @Velua  to provide logic

[ ] USD value @pingustar

@Ran73Cohen only task left here is:

[ ] add USD value

@Ran73Cohen only task left here is:

[ ] add USD value

authors: ashachaf katyarozenfeld pingustar

repo: bancorprotocol/webapp


text:
Single token removal - text change

"Stake" should be "Initial Stake" - it's currently a bit confusing - not clear to users why the stake is different than the output -

updated text. deploying on staging now.

authors: pingustar yudilevi


text:
Enhancement - IOS: Entitlement.plist

New Command Example: "NET MAUI - Archive : IOS - Add Entitlement.plist"
I have recently moved over to VSCode from VS for MAC and searched for some support in adding the keychain access for the MAUI SecureStorage. in VS For MAC you can easily select Entitlement under the IOS Bundle Signing section. Had to do some research to get this done manually in VSCode. Because it falls together with Publishing, I thought I'd log this enhancement as it will fit nicely with the existing commands.
Action 1:
Create a new Entitlement.plist XML file with Secure Storage example:

Location & Filename:
Create  Entitlement.plist in /Platforms/iOS folder.
File Example to create

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
    <dict>
        <!-- Allow Debug Secure Storage access, replace {csprojfile.ApplicationId} from your project file and uncomment this section -->
        <!-- <key>keychain-access-groups</key>
        <array>
            <string>$(AppIdentifierPrefix){csprojfile.ApplicationId}</string>
         </array> -->
    </dict>
</plist>

Warnings: If the file exist do not take action.

Action 2:
Add the Entitlement section to the project file if it does not exist

Location & Filename:
Open the .csproj file and add a  before the  close tag.
Tag Example

<PropertyGroup Condition="$(TargetFramework.Contains('-ios'))">
   <CodesignEntitlements>Platforms\iOS\Entitlements.plist</CodesignEntitlements>
</PropertyGroup>

Warnings: Tag already exist

Thanks for the great plugin, using it extensively with all my projects - Hope this can enhance it and does not take too much effort with the samples provided.

Hey @EntityBox
Thanks for your idea.
Unfortunately I'm not planning to implement this functionality in this extension. However, I've got a good practice for you to use custom entitlements in your .NET MAUI app. Check out the end of this blogpost:
https://www.banditoth.net/2024/10/04/using-different-entitlements-for-debug-and-release-modes-in-net-maui-ios/

authors: EntityBox banditoth

repo: banditoth/maui-archiver-vscode


text:
dealloc 调用会延迟... 能优化成立即释放吗?

2015-07-29 11:39:07.175 licaishi[12659:60b] [WebViewController  viewDidLoad  130]:
2015-07-29 11:39:08.085 licaishi[12659:60b] [WebViewController  viewDidLoad  130]:
2015-07-29 11:39:11.402 licaishi[12659:60b] [WebViewController  viewDidLoad  130]:
2015-07-29 11:39:12.305 licaishi[12659:60b] [WebViewController  viewDidLoad  130]:
2015-07-29 11:39:13.067 licaishi[12659:60b] [WebViewController  viewDidLoad  130]:
2015-07-29 11:39:15.535 licaishi[12659:60b] [WebViewController  viewDidLoad  130]:
2015-07-29 11:39:16.305 licaishi[12659:60b] [WebViewController  viewDidLoad  130]:
2015-07-29 11:39:17.117 licaishi[12659:60b] [WebViewController  viewDidLoad  130]:
2015-07-29 11:39:19.718 licaishi[12659:60b] [WebViewController  viewDidLoad  130]:
2015-07-29 11:39:20.507 licaishi[12659:60b] [WebViewController  viewDidLoad  130]:
2015-07-29 11:39:22.051 licaishi[12659:60b] [WebViewController  viewDidLoad  130]:
2015-07-29 11:39:23.167 licaishi[12659:60b] [WebViewController  viewDidLoad  130]:
2015-07-29 11:39:23.968 licaishi[12659:60b] [WebViewController  viewDidLoad  130]:
2015-07-29 11:39:25.534 licaishi[12659:60b] [WebViewController  viewDidLoad  130]:
2015-07-29 11:39:27.151 licaishi[12659:60b] [WebViewController  viewDidLoad  130]:
2015-07-29 11:39:28.518 licaishi[12659:60b] [WebViewController  viewDidLoad  130]:
2015-07-29 11:39:29.151 licaishi[12659:60b] [WebViewController  viewDidLoad  130]:
2015-07-29 11:39:30.717 licaishi[12659:60b] [WebViewController  viewDidLoad  130]:
2015-07-29 11:39:31.917 licaishi[12659:60b] [WebViewController  viewDidLoad  130]:
停止操作, 静态2分钟左右, 系统自动会调用 dealloc
2015-07-29 11:41:20.993 licaishi[12659:60b] [WebViewController  dealloc  135]:
2015-07-29 11:41:20.995 licaishi[12659:60b] [WebViewJavascriptBridge  dealloc  94]:
2015-07-29 11:41:20.997 licaishi[12659:60b] [WebViewController  dealloc  135]:
2015-07-29 11:41:20.998 licaishi[12659:60b] [WebViewJavascriptBridge  dealloc  94]:
2015-07-29 11:41:20.999 licaishi[12659:60b] [WebViewController  dealloc  135]:
2015-07-29 11:41:20.999 licaishi[12659:60b] [WebViewJavascriptBridge  dealloc  94]:
2015-07-29 11:41:21.000 licaishi[12659:60b] [WebViewController  dealloc  135]:
2015-07-29 11:41:21.001 licaishi[12659:60b] [WebViewJavascriptBridge  dealloc  94]:
2015-07-29 11:41:21.002 licaishi[12659:60b] [WebViewController  dealloc  135]:
2015-07-29 11:41:21.002 licaishi[12659:60b] [WebViewJavascriptBridge  dealloc  94]:
2015-07-29 11:41:21.003 licaishi[12659:60b] [WebViewController  dealloc  135]:
问题是 如果操作不停止, 就会一直创建新的控制器, 导致内存警告
能优化成立即释放吗? 比如 navigationController  pop 对应控制器的时候.

JS会在垃圾回收时释放，目前找到手动回收的方法。

公司内发现一个很有才的方法强制进行垃圾回收：
(function(){
  var x = {};
  for(var i = 0;i<10000;i++){
    xxx[i]=[];
  };
  xxx=null;
})();

In this article, the author mentioned a way to force GC:
for(i=0; i<4100; i++){
  a = .5;
}

Never tried myself, but may be helpful.

能不能在JPForwardInvocation函数中，将参数slf封装成JPBoxing对象传过去？
[argList addObject:[JPBoxing boxWeakObj:slf]];  （JPEngine line:437）

@bang590  navigationController pop 时为什么要在js垃圾回收时进行释放，这个不是oc层面的问题么？有些不解？

@bang590 ，“JS会在垃圾回收时释放，目前找到手动回收的方法。”；请问，如何手动回收？

@fanghongjia   你说你找到了手动回收的方法，请问怎么回收呢？

如何立即手动回收？

强制垃圾回收这个方法， 好像在频繁push pop 的时候有时会让应用卡死

到底这个问题怎么解决呢？这里好像没给出具体的解决办法吧？ @bang590

如何立即回收内存？ @joliylee @Zhangyanshen @bang590

authors: Zhangyanshen bang590 bingbingBang chengjiaming fanghongjia honghewang joliylee leafduo lungfei sanshanchuns


text:
upgrading version of vault in existing cluster not behaving as expected

Describe the bug
I have an existing bankvault cluster. I'm running Vault version 0.10.4. If I update the cr-etc-ha.yaml file to have a newer version of Vault (0.11.0) and deploy it, my pods are not updated to the new version. I have to manually delete my pods and when they are recreated they have the new version of Vault.
To Reproduce
Steps to reproduce the behavior:

update https://github.com/banzaicloud/bank-vaults/blob/master/operator/deploy/cr-etcd-ha.yaml#L7 to have a different version of Vault than you already have deployed.
kubectl apply -f cr_etcd_ha.yaml
kubectl -n  describe pod vault-0  ( or vault-1)
See Image is not the version of Vault specified in the update cr-etcd-ha.yaml file:

Containers:
  vault:
    Container ID:  docker://xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
    Image:         vault:0.10.4

running:  kubectl -n  delete pod vault-0 will cause the pod to get recreated and it will have the correct/expect Image version
Expected behavior
If I update the cr-etcd-ha.yaml file with a new version of Vault and deploy it, my pods perform a rolling update to the new version.

Hi @eisjcormier, which Kubernetes version are you using? I can't reproduce this on my version 1.10 cluster.

this is how my StatefulSet looks like after the update from 0.11.0 to 0.11.1 Vault:
Name:               vault
Namespace:          default
CreationTimestamp:  Wed, 12 Sep 2018 20:05:59 +0200
Selector:           app=vault,vault_cr=vault
Labels:             <none>
Annotations:        <none>
Replicas:           1 desired | 1 total
Update Strategy:    RollingUpdate
Pods Status:        1 Running / 0 Waiting / 0 Succeeded / 0 Failed
Pod Template:
  Labels:       app=vault
                vault_cr=vault
  Annotations:  prometheus.io/path=/metrics
                prometheus.io/port=9102
                prometheus.io/scrape=true
  Containers:
   vault:
    Image:       vault:0.11.1
    Ports:       8200/TCP, 8201/TCP
    Host Ports:  0/TCP, 0/TCP

Hi. Thanks for looking into my issue.
I am running on AWS EKS. K8S version:
Client Version: version.Info{Major:"1", Minor:"10", GitVersion:"v1.10.3", GitCommit:"2bba0127d85d5a46ab4b778548be28623b32d0b0", GitTreeState:"clean", BuildDate:"2018-05-28T20:16:17Z", GoVersion:"go1.9.3", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"10", GitVersion:"v1.10.3", GitCommit:"2bba0127d85d5a46ab4b778548be28623b32d0b0", GitTreeState:"clean", BuildDate:"2018-05-28T20:13:43Z", GoVersion:"go1.9.3", Compiler:"gc", Platform:"linux/amd64"}
kubectl describe sts vault
Name:               vault
Namespace:          XXXXX
CreationTimestamp:  Thu, 06 Sep 2018 20:29:24 +0000
Selector:           app=vault,vault_cr=vault
Labels:
Annotations:
Replicas:           2 desired | 2 total
Pods Status:        2 Running / 0 Waiting / 0 Succeeded / 0 Failed
Pod Template:
Labels:       app=vault
vault_cr=vault
Annotations:  prometheus.io/path=/metrics
prometheus.io/port=9102
prometheus.io/scrape=true
Containers:
vault:
Image:       vault:0.11.0
Ports:       8200/TCP, 8201/TCP
Host Ports:  0/TCP, 0/TCP
but if you look at the pods, 0.10.4 is what is still running:
kubectl describe pod vault-0
Name:           vault-0
Namespace:      XXXXX
Node:           XXXXXXXXXXXXXXXXXXXXXXXXXX
Start Time:     Wed, 12 Sep 2018 19:10:39 +0000
Labels:         app=vault
controller-revision-hash=vault-69687f66bc
statefulset.kubernetes.io/pod-name=vault-0
vault_cr=vault
Annotations:    prometheus.io/path=/metrics
prometheus.io/port=9102
prometheus.io/scrape=true
Status:         Running
IP:             XXXXXXXXXXXXX
Controlled By:  StatefulSet/vault
Containers:
vault:
Container ID:  docker://e4e4fb266ab25078bc45493445b64cfd131c42c2973f3c2fd085fd80d1f92bef
Image:         vault:0.10.4
You'll notice my output of 'describe sts vault' doesn't have any Update Strategy specified. Where does that get defined? Is this not set by default?

Very interesting since the default Strategy is RollingUpgrade: https://kubernetes.io/docs/concepts/workloads/controllers/statefulset/#update-strategies
Probably this is an EKS thing, but specifying the strategy explicitly should't hurt, so I will push a fox for this.

thank you

This seems to be an issue with our current ReadinessProbe setup, which makes sure that only the active Vault instance gets traffic, and the pod is not in Ready state. I'm investigating how we could work around this.

Let me know if you want me to test anything

@eisjcormier I have pushed a fix in #157 for this issue.

@eisjcormier  Although the Kubernetes bug report attached referencing broken stage this actually applies to not ready pods as well. The rolling upgrade does upgrade all the pods in any other state than the ready one - and unluckily it leaves that out from the upgrade. The workaround is to let rolling upgrades all the not ready pods in the StatefulSet then switch to an upgraded one (ready moves to not ready) - the controller than kicks on to upgrade the old ready one as well.
Hope this was clear enough ...

Thanks guys. Appreciate the quick turnaround.

@eisjcormier You are welcome, let us know how it works out for you. Hopefully, the StatefulSet issue will be fixed in the forthcoming K8s version so this will work as it supposed to (without the fix). Thanks for reporting it.

The fix has been released in https://github.com/banzaicloud/bank-vaults/releases/tag/0.2.23.

authors: bonifaido eisjcormier matyix

repo: banzaicloud/bank-vaults


text:
Fluent-bit spec does not contain mountPath in the docs

Describe the bug:
The Fluent-bit Spec does not contain the mountPath field, even though it exists in the logging CRD.
Expected behaviour:
The mountPath field to appear in the documentation.
Steps to reproduce the bug:
Access the CRD section of the documentation site and navigate to the Fluent-bit Spec heading.
Additional context:

https://banzaicloud.com/docs/one-eye/logging-operator/configuration/crds/#fluent-bit-spec
https://github.com/banzaicloud/logging-operator/blob/master/pkg/sdk/api/v1beta1/logging_types.go#L377-L379

Environment details:

Kubernetes version (e.g. v1.15.2): n/a
Cloud-provider/provisioner (e.g. AKS, GKE, EKS, PKE etc): n/a
logging-operator version (e.g. 2.1.1): 3.8.2
Install method (e.g. helm or static manifests): helm
Logs from the misbehaving component (and any other relevant logs): n/a
Resource definition (possibly in YAML format) that caused the issue, without sensitive data: n/a

/kind bug

there's an outdated part of the docs that is not automatically generated, we will look into it

there's an outdated part of the docs that is not automatically generated, we will look into it

Thank you! @pepov

Thank you! @pepov

Now looks fine thanks for the report!

authors: ahma nickgerace pepov

repo: banzaicloud/logging-operator


text:
plus是否已经保存了当前数据库表格与实体映射信息

当前使用版本(必填,否则不予处理)
3.0.5
该问题是如何引起的？(确定最新版也有问题再提!!!)
我想在项目启动得时候获取一部分表的信息 比如字段 实体属性 备注 等信息进行保存,请问作者plus是否已经有这部分信息保存了,或者提供了相关api
重现步骤(如果有就写完整)
报错信息

表相关信息存放在类 com.baomidou.mybatisplus.core.metadata.TableInfoHelper 中自己处理

表相关信息存放在类 com.baomidou.mybatisplus.core.metadata.TableInfoHelper 中自己处理

表相关信息存放在类 com.baomidou.mybatisplus.core.metadata.TableInfoHelper 中自己处理

谢谢回答.好像这部分信息中没有注释

表相关信息存放在类 com.baomidou.mybatisplus.core.metadata.TableInfoHelper 中自己处理

谢谢回答.好像这部分信息中没有注释

表相关信息存放在类 com.baomidou.mybatisplus.core.metadata.TableInfoHelper 中自己处理

谢谢回答.好像这部分信息中没有注释

注释你可以考虑自定义注解获取，如果用了swagger 可以取 swagger 注解内容

表相关信息存放在类 com.baomidou.mybatisplus.core.metadata.TableInfoHelper 中自己处理

谢谢回答.好像这部分信息中没有注释

注释你可以考虑自定义注解获取，如果用了swagger 可以取 swagger 注解内容

repo: baomidou/mybatis-plus


text:
多数据源下配置dbConfig.setUpdateStrategy(FieldStrategy.IGNORED);不起作用

当前使用版本(必填,否则不予处理)
3.3.2
该问题是如何引起的？(确定最新版也有问题再提!!!)
多数据源下配置dbConfig.setUpdateStrategy(FieldStrategy.IGNORED); 使用updateById方法 为空的属性没有置空
重现步骤(如果有就写完整)
配置两个数据源：
@Configuration
@MapperScan(basePackages = {"com.jumper.cs.standard.mapper"} ,sqlSessionFactoryRef = "standardSqlSessionFactory",
sqlSessionTemplateRef="standardSqlSessionTemplate")
public class StandardDataSourceConfig {
@Bean(name = {"standardDataSource"})
@Primary
@ConfigurationProperties(prefix = "druid.standard")
public DruidDataSource dataSource() {
    return DruidDataSourceBuilder.create().build();
}
@Bean(name = {"standardGlobalConfig"})
public GlobalConfig globalConfig(){
    GlobalConfig globalConfig=new GlobalConfig();
    GlobalConfig.DbConfig dbConfig=new GlobalConfig.DbConfig();
    dbConfig.setUpdateStrategy(FieldStrategy.IGNORED);
    globalConfig.setDbConfig(dbConfig);
    return globalConfig;
}
@Bean(name = "standardMybatisConfiguration")
//@ConfigurationProperties(prefix = "mybatis-plus")
public MybatisConfiguration configuration(@Qualifier("standardGlobalConfig") GlobalConfig globalConfig){
    MybatisConfiguration conf = new MybatisConfiguration();
    conf.setLogImpl(StdOutImpl.class);
    conf.setGlobalConfig(globalConfig);
    return conf;
}
@Bean(name = "standardSqlSessionFactory")
@Primary
public SqlSessionFactory sqlSessionFactory(@Qualifier("standardDataSource") DataSource dataSource,
                                           @Qualifier("standardMybatisConfiguration") MybatisConfiguration conf) throws Exception {
    //final SqlSessionFactoryBean sessionFactory = new SqlSessionFactoryBean();
    MybatisSqlSessionFactoryBean sessionFactory = new MybatisSqlSessionFactoryBean();
    sessionFactory.setDataSource(dataSource);
    sessionFactory.setConfiguration(conf);
    // 设置mybatis的xml所在位置
    sessionFactory.setMapperLocations(
            new PathMatchingResourcePatternResolver().getResources("classpath*:mapper/standard/*Mapper.xml"));
    return sessionFactory.getObject();
}
@Bean(name = "standardTransactionManager")
@Primary
public DataSourceTransactionManager transactionManager() {
    return new DataSourceTransactionManager(this.dataSource());
}
@Bean("standardSqlSessionTemplate")
// 表示这个数据源是默认数据源
@Primary
public SqlSessionTemplate standardsqlsessiontemplate(
        @Qualifier("standardSqlSessionFactory") SqlSessionFactory sessionfactory) {
    return new SqlSessionTemplate(sessionfactory);
}

}
@Configuration
@MapperScan(basePackages = {"com.jumper.cs.standard.mapper"} ,sqlSessionFactoryRef = "standardSqlSessionFactory",
sqlSessionTemplateRef="standardSqlSessionTemplate")
public class StandardDataSourceConfig {
@Bean(name = {"standardDataSource"})
@Primary
@ConfigurationProperties(prefix = "druid.standard")
public DruidDataSource dataSource() {
    return DruidDataSourceBuilder.create().build();
}
@Bean(name = {"standardGlobalConfig"})
public GlobalConfig globalConfig(){
    GlobalConfig globalConfig=new GlobalConfig();
    GlobalConfig.DbConfig dbConfig=new GlobalConfig.DbConfig();
    dbConfig.setUpdateStrategy(FieldStrategy.IGNORED);
    globalConfig.setDbConfig(dbConfig);
    return globalConfig;
}
@Bean(name = "standardMybatisConfiguration")
//@ConfigurationProperties(prefix = "mybatis-plus")
public MybatisConfiguration configuration(@Qualifier("standardGlobalConfig") GlobalConfig globalConfig){
    MybatisConfiguration conf = new MybatisConfiguration();
    conf.setLogImpl(StdOutImpl.class);
    conf.setGlobalConfig(globalConfig);
    return conf;
}
@Bean(name = "standardSqlSessionFactory")
@Primary
public SqlSessionFactory sqlSessionFactory(@Qualifier("standardDataSource") DataSource dataSource,
                                           @Qualifier("standardMybatisConfiguration") MybatisConfiguration conf) throws Exception {
    //final SqlSessionFactoryBean sessionFactory = new SqlSessionFactoryBean();
    MybatisSqlSessionFactoryBean sessionFactory = new MybatisSqlSessionFactoryBean();
    sessionFactory.setDataSource(dataSource);
    sessionFactory.setConfiguration(conf);
    // 设置mybatis的xml所在位置
    sessionFactory.setMapperLocations(
            new PathMatchingResourcePatternResolver().getResources("classpath*:mapper/standard/*Mapper.xml"));
    return sessionFactory.getObject();
}
@Bean(name = "standardTransactionManager")
@Primary
public DataSourceTransactionManager transactionManager() {
    return new DataSourceTransactionManager(this.dataSource());
}
@Bean("standardSqlSessionTemplate")
// 表示这个数据源是默认数据源
@Primary
public SqlSessionTemplate standardsqlsessiontemplate(
        @Qualifier("standardSqlSessionFactory") SqlSessionFactory sessionfactory) {
    return new SqlSessionTemplate(sessionfactory);
}

}
使用updateByID方法空字段没有置空
但是加了@TableField(updateStrategy = FieldStrategy.IGNORED)的字段为空时可以置空
报错信息

需要把GlobalConfig 设置到MybatisSqlSessionFactoryBean中 而不是MybatisConfiguration中 可以解决问题
/**
* 全局自定义配置
*/
@Bean(name = "globalConfig")
@ConfigurationProperties(prefix = "mybatis-plus.global-config")
public GlobalConfig globalConfig() {
return new GlobalConfig();
}
/** 当使用myBatis-plus的时候需要使用 MybatisSqlSessionFactoryBean /
MybatisSqlSessionFactoryBean sessionFactory = new MybatisSqlSessionFactoryBean();
sessionFactory.setDataSource(dataSource);
sessionFactory.setConfiguration(configuration());
/* 设置全局配置 */
sessionFactory.setGlobalConfig(globalConfig());


text:
能否增加查询被逻辑删除的数据的方法？

版本号
3.5.2
该问题是如何引起的？
能否增加查询逻辑删除记录的方法？既然是逻辑删除，就说明还有使用的可能。但目前没有提供任何查询逻辑删除数据的方法

还要使用的不要用删除，自己加状态。

authors: huayanYu mynzdbx


text:
Highlighting specific row in zebkit grid view and row/ column span problem

Hi,
I am using zebkit grid to create a table in my project.

I need to highlight alternate row with specified color. example : Suppose I have 4 rows in grid then 2nd and 4th row should be highlighted with given color.
I tried to use " grid.defCellColor="red" ", but it sets the color to all cells in the grid.
I am not able to find the way for doing the same. Is there a way to achieve this ?
Also is there a way to add row and column span for grid view?
I have done through the documentation of zebkit but couldn't able to find a way to achieve the same.

Thanks!

To control grid cell colors (and other things) you should implement a custom grid view provider. For example, imagine you need to color to "red" every forth row in the grid. You can do it as follow:
// extend standard (DefViews) grid cell view provider
grid.setViewProvider(new zebkit.ui.grid.DefViews([
    function getCellColor(grid, row, col) {
         return row % 4 === 0 ? "red" : null;
    }
]));

Column and row span are not supported.

Thank!

Is there any way to achieve something like row span and column span for grid ?

Hi,

Column and row span are not supported.
If column and row span are not supported then is there any other way to achieve this behavior. Please comment.
Thanks!

There is actual no easy way to support column and row span. In any case it requires modifying grid cell painting to support the feature. May be it is even simpler to develop special grid layout that can place components inside taking in account row and column spans (if components approach fits your needs). May ready to use Java based grid layout (open source) exists, then it can be relatively easy converted into zebkit layout code.

I would love to implement the special grid layout which will have support for column and row span with resizing column and row support.
Could you please provide any help for moving forward in right direction for this?
Please provide some guidance on starting with this.
Thank you much!

any updates ?

authors: barmalei vasu-vvp

repo: barmalei/zebkit


text:
control block matching seems to find wrong block head or tail.

Notice the IF and ENDIF lines outlined.  The IF that is highlighted is not the if for the ENDIF highlighted.

Ctrl+Shift+\ matches the wrong ENDIF.
Ctrl+Shift+[ folds the correct control block.
If I comment out the exe sql code the block marking works

This fix did work for the sample I gave you but I found another version of code that its not working correctly for.

Ctrl+Shift+\ matches the wrong ENDIF.
Ctrl+Shift+[ folds the correct control block.
If I comment out the exe sql code the block marking works
One thing I noticed with this is that i have a CASE statement which has an END keyword.

repo: barrettotte/vscode-ibmi-languages


text:
Brak Kernel32 na Linuxie

https://github.com/bart-kosmala/fakers/blob/0f2371f9b565af0b6f24b5b39b4f6b642a693c04/generator/DisposableElement/Disposable.cs#L35

Generalnie przeglądając kod to nie widzę zastosowania do tej klasy, moglibyście po krótce opisać jaki jest jej cel?
Disposable się implementuje do używania z using ale zawsze można ręcznie po prostu zamknąć to co byłoby zamykane przez ten interfejs.

repo: bart-kosmala/fakers


text:
Support fsnotify 0.4

To allow building with recent ghc versions, the fsnotify dependency upper-bound needs to be updated.
The current bound is fsnotify >=0.3 && <0.4.
It would also allow language-puppet to be built with more recent ghc versions.

It's done, new version on hackage.

authors: PierreR bartavelle

repo: bartavelle/filecache


text:
Popup

Created a modal view with a popup for shot creation. The input is validated and when Create is clicked then the DirectorShot is added and the corresponding Camera timelines are updated which the accompanied shots.

Looks good to me, please take a look at the comments and then we can merge

LGTM

Good work! Merging


text:
Question: Does this library have the ability to get the PDF metadata?

I need to get the PDF metadata, such as Title, author, etc.  I didn't see a way to get it with this library, but just want to ask in case I missed it.
Thanks!
-Rick

Currently it's not possible to get metadata, but it's good idea to add such feature.

Ok, thanks for the response!

Support for metadata added in version 1.2.0.

Thanks @barteksc!  Great addition to your library.

authors: NightSkyDev barteksc

repo: barteksc/AndroidPdfViewer