Are you done with qpp conversion tool 2023 updates?

          Are you done with qpp conversion tool 2023 updates?

If not then when you will be finished it with?
Originally posted by @abhisheka1993 in https://github.com/CMSgov/qpp-conversion-tool/issues/1364#issuecomment-1787057931

did you get a chance to check it?

Hi @abhisheka1993,
We have majority of the work complete but are waiting on a requirements update for PCF program submissions. I estimate this will be finished within the next week. 2023 MIPS should be completed. Feel free to open back up another issue if anything else comes up.

Thanks saquino0827, I am just waiting for the updates for 2023.


version 1.9.0: what has changed?

Hi Kevin, could you tell us what has changed with this version, please?

I fixed issues #29 and #23 and #13

Thank you.


Minor corrections to docblocks / comments

Cascading comments have been maintained 😄

This unfortunately breaks the uniform styling of these commend blocks.

@driesvints: I made sure not to break the uniformity though... have you viewed the diff? Many times it's the same number of letters that's changed so with a monospaced font there is no change to the styling.

@driesvints: what happens when this is not possible? For example, some of the corrections involve adding or removing a single character (a array → an array, an user → an user).
Does comment styling take precedent?

Does styling take precedence over having a comment that uses the correct grammar? 😕

Yes but we're open to improve grammar as long as the styling is preserved.

Yes but we're open to improve grammar as long as the styling is preserved.

How do you suggest this is achieved?
Do you mean the whole comment must be rewritten to: 1) correct the grammar (most of the time a single character) and 2) comply with "three spaces for the second line and two for the third line"?
The commas can be removed if you would prefer to omit them.

A handful of examples (to me, the styling is intact):
- // Now we are ready to execute the query to see if we have an user matching
+ // Now we are ready to execute the query to see if we have a user matching
  // the given credentials. If not, we will just return nulls and indicate
  // that there are no matching users for these given credential arrays.

- // Here we'll check if the given subset of where clauses contains any "or"
+ // Here we'll check if the given subset of where clauses contain any "or"
  // booleans and in this case create a nested where expression. That way
  // we don't add any unnecessary nesting thus keeping the query clean.

- // If the values implements the Arrayable interface we can just call this
+ // If the values implement the Arrayable interface we can just call this
  // toArray method on the instances which will convert both models and
  // collections to their proper array form and we'll set the values.

  // of the relation so that we will easily and quickly match them to their
- // parents without having a possibly slow inner loops for every models.
+ // parents without having a possibly slow inner loop for every model.


Restart HA will random cause one camera fail to establish

Logger: custom_components.dahua
Source: custom_components/dahua/client.py:612
Integration: Dahua (documentation, issues)
First occurred: 24:34:36 (11 occurrences)
Last logged: 24:46:16
Failed to sync device state
Traceback (most recent call last):
File "/config/custom_components/dahua/client.py", line 606, in get_bytes
response = await auth.request("GET", self._base + url)
File "/config/custom_components/dahua/digest.py", line 50, in request
return await self._handle_401(response)
File "/config/custom_components/dahua/digest.py", line 151, in _handle_401
return await self.request(
File "/config/custom_components/dahua/digest.py", line 46, in request
response = await self.session.request(method, url, headers=headers, **kwargs)
File "/usr/local/lib/python3.9/site-packages/aiohttp/client.py", line 544, in _request
await resp.start(conn)
File "/usr/local/lib/python3.9/site-packages/aiohttp/client_reqrep.py", line 890, in start
message, payload = await self._protocol.read()  # type: ignore
File "/usr/local/lib/python3.9/site-packages/aiohttp/streams.py", line 604, in read
await self._waiter
asyncio.exceptions.CancelledError
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/config/custom_components/dahua/init.py", line 171, in _async_update_data
await self.client.async_get_snapshot(0)
File "/config/custom_components/dahua/client.py", line 67, in async_get_snapshot
return await self.get_bytes(url)
File "/config/custom_components/dahua/client.py", line 612, in get_bytes
response.close()
File "/usr/local/lib/python3.9/site-packages/async_timeout/init.py", line 55, in aexit
self._do_exit(exc_type)
File "/usr/local/lib/python3.9/site-packages/async_timeout/init.py", line 92, in _do_exit
raise asyncio.TimeoutError
asyncio.exceptions.TimeoutError

Unlikely this is anything to do with the integration but something one off with your setup or camera. Not a lot I can do here.


WIP: android: avoid revocation check missing OCSP URI exceptions.

This is a draft for now, as there are some trade-offs to discuss here. Apologies for the length of this PR description. I did a lot of digging around to come up with this approach and I wanted to provide as much context as I could (both for my future self and for other maintainers).
Description
Revocation checking on Android has a few peculiarities that must be accounted for in order to maximize the value of the revocation checking that rustls-platform-verifier does given the platform constraints. See https://github.com/rustls/rustls-platform-verifier/issues/13 for more information.
Most importantly, when we check a certificate chain preferring OCSP (default behaviour), Android's revocation checker implementation will throw a fatal exception if any certificates within the considered chain depth are missing an OCSP staple (which is true for all intermediates, only end-entity certs can have stapled OCSP) or are missing an authority information access extension with an OCSP access method and URI location (which is common for real-world intermediates like Let's Encrypt's R3 intermediate certificate).
In essence we have two decisions to make for any given validated certificate chain when it comes time to check revocation status:

Should we check for the entire chain (minus root trust anchor) or, just check the end entity status.
Should we check preferring OCSP and falling back to CRLs, or should we check CRLs only.

We want our decisions to:

Prefer OCSP when possible
Maximize the revocation checking we perform
Avoid exceptions/errors for real-world certificate chains that are unrevoked

Unfortunately the existing APIs and PKI practices mean we have to make some compromises. Read on for more.
End entity vs Full Chain
Prior to this branch we made the determination of revocation checking depth exclusively by determining if the certificate chain was issued by a known system root trust anchor. If it was, we checked the whole certificate path (minus root trust anchor, since these can not be revoked by traditional means). If it wasn't, we checked only the end entity certificate:
https://github.com/rustls/rustls-platform-verifier/blob/ce16ccce58744b8973e3ecf5011a1fdf3bdef011/android/rustls-platform-verifier/src/main/java/org/rustls/platformverifier/CertificateVerifier.kt#L300-L307
In this branch we adjust this logic so that:

As before, if the trust anchor isn't a known system trust anchor we default to checking only the end entity certificate
If the trust anchor is known, but we only have OCSP revocation information for the end-entity certificate, we check only the end entity certificate
In all other cases we check the entire chain.

Checking only the end entity certificate when we lack OCSP revocation information for the rest of the chain is a trade-off: we can't specify OCSP vs CRL preferences per-certificate, just per-chain, so if we have a chain that has an OCSP URI or stapled OCSP response for the end-entity certificate, we prefer to check only the end-entity certificate revocation status rather than checking the whole chain when we know the chain is missing OCSP revocation information for an intermediate. The alternatives are to proceed with full chain verification, at which point an exception will be thrown from the missing OCSP information (current behaviour), or to prefer CRL validation for the full chain (which would ignore that we have enough information to check OCSP for the end-entity).
Prefer OCSP vs CRL only
Prior to this branch we always preferred OCSP (the default setting). In theory the Android revocation checker should fall back to checking CRLs if it encounters an error checking OCSP, but in practice this doesn't seem to work (TODO: Can we get a better answer for why?). Instead the first certificate that the revocation checker encounters without an OCSP staple or a suitable AIA OCSP URL results in a fatal exception of the form "certificate was revoked: java.security.cert.CertPathValidatorException: Certificate does not specify OCSP responder".
To try to meet our goals this branch changes the revocation logic so that:

If we're checking only the end-entity certificate, we prefer OCSP only when we have either an OCSP staple or know the end-entity certificate contains a suitable AIA extension.
If we're checking the entire chain, we prefer OCSP only when the entire chain has OCSP information available (e.g. the end-entity cert has a stapled OCSP response or suitable AIA extension, and each intermediate in the chain has a suitable AIA extension).
In all other cases we prefer CRLs and don't try to fall back to OCSP since we know it will fail.

"Does this cert have an AIA OCSP URL?"
As part of our new logic we need to make the determination about whether a certificate has an Authority Information Access extension that specifies an OCSP URI. Unfortunately Android/Java make this difficult :-(
The system provider's own OCSP implementation used by the revocation checker has all of the logic required to parse an AIA extension to find an OCSP URI, but it's locked away in platform internal only classes under the sun.security.provider.* namespace that we can not import. None of the X509Certificate and Certificate classes, or the X509Extension interface provide access to the AIA extension.
However X509Certificate implements X509Extension, which offers a method for getting a raw DER encoded extension value by OID. We can use this to access the raw DER encoding of the AIA extension.
Our next challenge is doing something useful with the raw DER extension value. Unfortunately again the tools required for DER parsing are present, but locked away in internal-only classes that we can't use. Frequently folks will take a dependency on BouncyCastle to parse DER but this is an extremely heavy-weight cryptography library (and one I find particularly gross to work with...).
As a last resort we take a more extreme, but lightweight, approach: we have the DER encoding of the overall extension value, and we know the DER encoding of the OID that specifies a OCSP access method within that extension (id-ad-ocsp) so we can simply try to find the matching byte sequence for that OID in the raw DER extension. This is sufficient for our purposes as a heuristic for whether or not OCSP checking will fail from a missing OCSP URI. A maliciously crafted certificate could include an AIA extension designed to fool our heuristic into thinking there is an OCSP URI when there isn't, but this will only result in a revocation rejection when the provider OCSP checking code fails to find a real OCSP URI. It would also have to be a certificate issued by a known trust anchor since we do all of this work after verifying the chain signatures up to a trust anchor.
If this approach is too gross I think the best alternative is to have Rust code do this parsing and provide the extension URI (if present) along with each certificate. Note that webpki and rustls don't have existing code to parse/expose the AIA extension either, so this will require implementing that code somewhere, or taking a dependency on a large crate like x509-parser.
Let's Encrypt testcase
So far this branch includes one additional real world verification test, bundling a Let's Encrypt certificate chain of the form EE (AIA OCSP present) -> R3 intermediate (no AIA OCSP) -> ISRG Root X1 (no AIA OCSP) -> trust anchor.
Before the changes in this branch revocation checking would always fail for this chain, producing the "certificate was revoked: java.security.cert.CertPathValidatorException: Certificate does not specify OCSP responder" result observed in #13 due to the two intermediate certificates missing AIA OCSP URLs.
With the changes in this branch revocation checking succeeds:

When deciding whether to check the full chain or just the end entity cert we find the root is known but we only have OCSP checking information for the end entity certificate (it has an AIA OCSP URL, but the intermediates do not). So we decide to check only the end entity certificate.
When deciding whether to prefer OCSP or use CRL w/o fallback, we find that we're only checking the end entity and we do have sufficient OCSP information, so we prefer OCSP.

Ultimately this translates into using the revocation checker options [ONLY_END_ENTITY, SOFT_FAIL], and a positive "not revoked" determination.
Other approaches
Unfortunately there's precious little information or example code in the wild for Android revocation checking. What I did find tended to either:
a) Ignore this problem, presumably encountering the exception we see when checking full chains when some certificates are missing OCSP information (e.g. this gist)
b) Tried to ignore this exception in particular, by matching the error message.
Neither approach seemed viable to me.
Todo

[ ] Vet overall idea is reasonable
[ ] Implement additional test coverage - the test coverage in-branch isn't sufficient, but I wanted to vet the approach first.

Android does not provide any way only to attempt to validate revocation from cached
data like the other platforms do

Literally unplayable. How bad would it be to only check stapled OCSP responses? Does this caveat also apply to CRLs? Is android going to go and download a 30MB CRL every time?
(Thanks for correcting the OSCPs in this file!)

How bad would it be to only check stapled OCSP responses?

I think to do this we'd have to forgo checking beyond end entity depth. It looks like this is what Conscrypt is doing.

Does this caveat also apply to CRLs? Is android going to go and download a 30MB CRL every time?

Yup, that's my understanding :dizzy_face: Looking at Conscrypt again they explicitly added a no-fallback flag when checking revocation up to end entity depth preferring OCSP because:

if the OCSP check fails (e.g. because the date on the device is wrong) then the Sun PKIXRevocationChecker will fall back to downloading a CRL and checking that. On Android 8.0/8.1 this causes large latency and possible OOM.

If we had Rust code to do CRLite, would we be able to plug that in here somehow?

A simpler alternative to consider: https://github.com/rustls/rustls-platform-verifier/pull/40

Closing in favour of #40. Thanks for the input folks!


Allow setting clipping parameters (only _r1 if unpaired) - Issue 944

Fix for https://github.com/nf-core/rnaseq/issues/944:
Setting clipping parameters did not work in 3.10.
PR checklist

[ X] This comment contains a description of changes (with reason).
[ ] If you've fixed a bug or added code that should be tested, add tests!
[X ] Make sure your code lints (nf-core lint).
[ X] Ensure the test suite passes (nextflow run . -profile test,docker --outdir <OUTDIR>).
[ X] CHANGELOG.md is updated.

Thanks! I tested on the test dataset which has both single and paired end samples. Seemed to work fine as far as I can see.


Error at harvesting reflexive strategies.

Looking at the logs I see that the harvester is always failing at this strategies:
0x1435c96785B64D4d9452812645C3cD423C1F73ca - PngSporePngLp
0x14519ABf2f04a632Ee65D84D9A37d9Eec02955F3 - JoeAvaxGbLp
0x20B6c71D1724A8D8510FB3D2486e4cCF2A8D91AD - PngAvaxGbLp
0x5547e1aaD9c6557C625Da99a0Da1aEcdA1cE2992 - PngAvaxAvmeLp (This one is not reflexive tho, it was made with the wrong base?)
0x7e4196Fe4A9C661B1BbD27B54214E669351Bdf23 - PngAvaxShibxLp
With the error: cannot estimate gas; transaction may fail;
Please review harvest() on these.

Are these deprecated too? @jomarip

I think this still fail. Worth keeping on here as a reminder. It actually was important to remember today


VSCode failing to update

This morning, I used the gear menu -> Restart to update to update my Code installation. After attempting to install the update, I see the following error:

I'm using VSCode Insiders on Windows 10, and I updated yesterday.
The aforementioned log file is here:
vscode-inno-updater.log

VSCode Version:

OS Version:

Steps to Reproduce:

Click the Gear (1) in the bottom left
Click "Restart to update..."
Wait for the error to appear
On dismissing the error, VSCode restarts without any issues besides the failure to update.

Alternatively:

Open VSCode
Close VSCode
Wait for the error to appear
On dismissing the error, VSCode exits.

Does this issue occur when all extensions are disabled?: I can't figure out how to launch the user version of Code Insiders from the run dialogue; code-insiders --disable-extensions doesn't work.

After restarting Windows, I was able to successfully update. I'd close this issue but I don't know if there's an underlying problem or not.

Thanks, we already have a couple other issues following this problem.


Unable to generate code when using SQLite with LEFT JOIN

Version
Other
What happened?
sqlc generate failed when using the described schema and query. The version used is v1.16.0.
Relevant log output
column reference "id" not found

Database schema
CREATE TABLE IF NOT EXISTS links (
    id TEXT PRIMARY KEY,
    destination TEXT NOT NULL,
    created_at INTEGER NOT NULL,
    updated_at INTEGER NOT NULL
);

CREATE TABLE IF NOT EXISTS visits (
    id TEXT PRIMARY KEY,
    link_id TEXT NOT NULL,
    created_at INTEGER NOT NULL,
    FOREIGN KEY (link_id) REFERENCES links(id)
);

SQL queries
-- name: GetLinks :many
SELECT
    links.id,
    links.destination,
    links.created_at,
    links.updated_at,
    COUNT(visits.id) AS visits
FROM links LEFT JOIN visits ON links.id = visits.link_id
GROUP BY links.id;

Configuration
version: 2
sql:
  - engine: sqlite
    schema: internal/sqlite/schema.sql
    queries: internal/sqlite/queries.sql
    gen:
      go:
        package: sqlite
        out: internal/sqlite

Playground URL
https://play.sqlc.dev/p/c8d3c10a1bb40e4c91484e3334f3ae33e7764a7f5e4ba6742c6842c4c13c5933
What operating system are you using?
macOS
What database engines are you using?
No response
What type of code are you generating?
Go

+1

it's worked for me
https://play.sqlc.dev/p/d9035f55cc5e09c0b18e9e798423c4b7e2969b7036ce25d680a553f7d18addf9

@zasdaym
Your query is worked now, You just have to work with placeholders instead of table names.
SELECT
- links.id
+    l.id,
-    links.destination,
+    l.destination,
-    COUNT(visits.id) AS visit_count
+    COUNT(v.id) AS visit_count
-FROM links LEFT JOIN visits ON links.id = visits.link_id
+FROM links l LEFT JOIN visits v ON l.id = v.link_id
-GROUP BY links.id;
+GROUP BY l.id;

https://play.sqlc.dev/p/253ad0cdf535a53bfe0be3235fa7324d9b10e3b03cfd952bfa57d52404d5dd13

Thanks for the solution @zakaria-chahboun, but the same exact query is working when using the postgresql engine.

Duplicate of #2271, I think.


Re-apply the same Walrus file without modification triggered resource patch

Describe the bug
Re-apply the same Walrus file without modification triggered resource patch
Steps to reproduce

Start a walrus server with single docker installation
Download walrus cli, generate token and config the cli.
Save the wordpress walrus file from walrus file hub as app.yaml. The content is as below:

resources:
  - name: wordpress-db
    type: mysql
    attributes: {}
  - name: wordpress
    type: containerservice
    attributes:
      containers:
        - image: wordpress
          profile: run
          ports:
            - internal: 80
              external: 80
          envs:
            - name: WORDPRESS_DB_HOST
              value: ${res.wordpress-db.address}
            - name: WORDPRESS_DB_PASSWORD
              value: ${res.wordpress-db.password}
            - name: WORDPRESS_DB_USER
              value: ${res.wordpress-db.username}
            - name: WORDPRESS_DB_NAME
              value: ${res.wordpress-db.database}

Run "walrus apply -f app.yaml", wait for the deployment to complete.
Run "walrus apply -f app.yaml" again without any modification. It will return:
resource default/dev/wordpress unchanged
resource default/dev/wordpress-db patched
Re-run "walrus apply -f app.yaml" again without any modification. It will return:
resource default/dev/wordpress unchanged
resource default/dev/wordpress-db patched
Check the wordpress-db resource through Walrus UI, it has revisions triggered in 2nd and 3rd apply although the walrus file is the same.
Check change history, the 2nd change showed a resource id was added and the 3rd change showed "no modification"

Environment

Walrus version: v0.5.0-rc4

Update: remove the " attributes: {} " part from mysql resource will resolve this issue.

Environment

Walrus version: main ee79b53f2325cd7cbf5be5e36bdfc7084c21d054
UI version: dev-a712ac5

Test Result: pass


Error("missing field length"} in Timestamp in TUF repository after latest update

Description

After latest update on TUF repository, the SigstoreTrustRoot::new function in sigstore-rs is failing. The error is:
failed to construct SigstoreTrustRoot: TufError(ParseMetadata { role: Timestamp, source: Error("missing field `length`", line: 14, column: 4)

After looking at: timestamp.json, the length field under "snapshot.json" is indeed missing. The repository was updated recently Generated 2024-09-05T19:21+00:00

I'll close this as a duplicate of #1251.

the change was intentional, and is TUF specification compliant
unfortunately the awslabs/tough, tuf implementation that sigstore-rs uses, did not implement this correctly until a few weeks ago (and an unrelated dependency issue is preventing sigstore-rs from upgrading at the moment)


docs($http): Recommend unique XSRF cookie names for shared domains

Adding a recommendation as a followup to https://github.com/angular/angular.js/issues/11999

Just switched my Github account's public e-mail over to
<EMAIL_ADDRESS>CLA shouldn't be needed.
On Thu, Jun 4, 2015 at 10:59 AM googlebot<EMAIL_ADDRESS>wrote:

Thanks for your pull request. It looks like this may be your first
contribution to a Google open source project, in which case you'll need to
sign a Contributor License Agreement (CLA).
[image: :memo:] Please visit https://cla.developers.google.com/
https://cla.developers.google.com/ to sign.
Once you've signed, please reply here (e.g. I signed it!) and we'll
verify. Thanks.

If you've already signed a CLA, it's possible we don't have your
GitHub username or you're using a different email address. Check your
existing CLA data https://cla.developers.google.com/clas and verify
that your email is set on your git commits
https://help.github.com/articles/setting-your-email-in-git/.
If you signed the CLA as a corporation, please let us know the
company's name.

—
Reply to this email directly or view it on GitHub
https://github.com/angular/angular.js/pull/12028#issuecomment-108991741.

thanks for the PR! I've reworded it a bit and landed the change as 2c3cd8126cad932bad807f6573f4e4d7a5f41121


Trigger Slack notification for review response

Automated Message: Variable changes to be included in this PR

https://medium.com/m/callback/email?token=182aa671a935&operation=login&state=medium&source=email-2e6fd972d713-1645512171378-auth.login------0-------------------d4e62134_22ea_4060_840a_793090a10ff8


remove GlyphsInfo submodule but keep the .xml files

I haven't been able to get gh actions to package a release that includes the .xml files in the Lib/gftools/util/GlyphsInfo submodule. What's strange is that the files are getting pulled into the repo:

To save my sanity, I've removed the submodule and I'll just update the files whenever they are updated. glyphsLib also uses this approach.
@alerque I've spent half a day on this so I'm opting for the easy route here.

if you use setuptools_git_ls_files setuptools plugin to have git include all files tracked by submodules in the sdist manifest.
You just need to add "setuptools_git_ls_files" to the setup_requires keyword of your setup.py script, e.g. like we do in cffsubr here.

Thanks Cosimo. After adding your plugin to setup.py, the package which is generated using setup.py sdist will include the .xml files.
tar -ztvf dist/gftools-0.5.0.tar.gz
...
-rw-r--r-- runner/docker 4102534 2020-11-16 15:11 gftools-0.5.0/Lib/gftools/util/GlyphsInfo/GlyphData.xml
-rw-r--r-- runner/docker 2264108 2020-11-16 15:11 gftools-0.5.0/Lib/gftools/util/GlyphsInfo/GlyphData_Ideographs.xml

However, the xml files are still missing from the release zip. I'll dig a bit more.

Oh damn. The Github release api doesn't support sub modules, https://github.community/t/create-release-that-contains-submodule/1329

the xml files are still missing from the release zip.

you should not use github release zip, only the sdist is the canonical source distribution.
auto-generated tar.gz files from GH do not include submodules.

that's not a problem, pip will only use the sdist package that you upload to PyPI, the GH archives are irrelevant and should not be discouraged. Either one clones (recursively) or downloads the sdist from PyPI.

Yes to what Cosimo said. Use the Python generated sdist, that's the one that should be released. Besides submodules there are other things the Github "release" (which is just a git archive generated tarball of sources) will not include, such as preparing sources for use with setuptools (as opposed to setuptools_scm or other custom modules).

Ok cool. Thanks for clarifying this. I'll close this and fix up #270 instead.


Offset blocking UI actions

Applying offset as margin to AlertComponent blocks actions (clicks) to any underlying buttons/UI.

As I said in #95, I want to keep the package as simple as possible, and I think that adding two different offset/margin option can confuse people. Also, I don't think that an alert blocking the content bellow it is a big deal.
So I am closing this as a wontfix.


Setup Anaconda

Setup an Anaconda environment for UnderstandingLanguage. The initial environment will contain the following packages:

Python
Sphinx
Sphinx_Rtd_Theme
Pylint

The Anaconda environment is now working with Eclipse.


[Windows] Can't parse file path for 'amplify/data/resource.ts'

Environment information
System:
    OS: Windows 11 10.0.23612
    CPU: (16) x64 AMD Ryzen 9 5900HX with Radeon Graphics
    Memory: 9.31 GB / 23.91 GB
  Binaries:
    Node: 20.10.0 - C:\Program Files\nodejs\node.EXE
    Yarn: 1.22.21 - C:\Program Files\nodejs\yarn.CMD
    npm: 10.2.5 - C:\Program Files\nodejs\npm.CMD
    pnpm: 8.14.1 - C:\Program Files\nodejs\pnpm.CMD
    bun: Not Found
    Watchman: Not Found
  npmPackages:
    @aws-amplify/backend: 0.10.0
    @aws-amplify/backend-cli: 0.9.5
    aws-amplify: 6.0.11
    aws-cdk: Not Found
    aws-cdk-lib: Not Found
    typescript: 5.3.3

Description
When running amplify sandbox, I'm getting an error:
File name or path for backend definition are incorrect
Caused By: Amplify Data must be defined in amplify/data/resource.ts

The thing is: the file is there.
File path got from defineData is c:\\code\\github\\Javascript ou Typescript\\babybloom\\monorepo\\apps\\mobile-app\\amplify\\data\\resource.ts.

This error showed because I had created an enum with one of the options having a - (dash), changing it to _ (underline) fixed the issue.
Still think this error should be clearer.


Trigger full set of tests of Events after a deploy

Description
As a part of the release pipeline for Events we want to run the full set of tests to verify Events after deploy. There needs to be a delay to ensure that the new version is the active version of the application.
Additional Information
No response
Tasks

[ ] Extend release pipeline to trigger the Events tests in correct environment.

[ ] This requires a github access token so that DevOps can run a github workflow.

[ ] The release pipeline should fail if the tests fail.
[ ] The workflow should send a message to slack alert-info
[ ] Remove outdated tests from altinn.studio repository
[ ] Remove outdated k6-test pipeline dependencies to Events.

Acceptance Criterias

[ ] Tests are triggered shortly after deploy.

duplicate created in #473. Closing this as the other one is in progress


Add missing methods to Rect2i

Replace inline with _FORCE_INLINE_ in short methods.
Remove unused and redundant method no_area() as we already have has_no_area().
Add grow_individual() grow_margin() and expand() to Rect2i.

if anyone needs them, guess it's fine

Thanks!


{Network} az network lb address-pool: refine error message

Description

Fix #14342
Testing Guide

History Notes

[Component Name 1] BREAKING CHANGE: az command a: Make some customer-facing breaking change.
[Component Name 2] az command b: Add some customer-facing feature.

This checklist is used to make sure that common guidelines for a pull request are followed.

[ ] The PR title and description has followed the guideline in Submitting Pull Requests.

[ ] I adhere to the Command Guidelines.

/azp run Azure.azure-cli


Fix issue #2319 (crash on import of candid class)

This PR does not affect the produced WebAssembly code.

@chenyan-dfinity PTAL
BTW, do you know if we actually type-check (i.e. kind-check) the imported candid file before or during import? There might be a an unlikely, but possible, security hole if we don't.


Upgrade poetry2nix

https://github.com/fluidattacks/makes/blob/cf2105dee74e005b0c302d39d58c869c011802dd/src/args/make-python-poetry-environment/default.nix#L6

Upgrade to latest commit
Validate that all makes jobs that use it work properly
upgrade makes version on universe.

Closing in favor of #1378


How to show this on page?

Sorry new here,
where should I add the code to show the report?

Sorry new here,
where should I add the code to show the report?

composer require laravel-admin-ext/chartjs
php artisan vendor:publish --tag=laravel-admin-chartjs
config/admin.php
'extensions' => [
'chartjs' => [
// Set to false if you want to disable this extension
'enable' => true,
]
]
例子resources/views/admin/chartjs.blade.php

In yr controller
return $content
        ->header('Chartjs')
        ->body(new Box('Bar chart', view('admin.chartjs')));

I did all these steps, but I get not thing

return $content
->header('Chartjs')
->body(view('charts.test'));

In the terminal, go to the project directory and run:
composer require laravel-admin-ext/chartjs
php artisan vendor:publish --tag=laravel-admin-chartjs

Open config/admin.php, add configurations that belong to this extension at extensions section:
`
'extensions' => [
 'chartjs' => [

     // Set to `false` if you want to disable this extension
     'enable' => true,
 ]

]
`

Create a view in views directory like resources/views/admin/chartjs.blade.php, and add following codes:
`

4. In the terminal, run the command: php artisan make:controller ../../Admin/Controllers/ChartjsController 5. Go to app/Admin/Controllers/ChartjsController.php, clear it and write the code:<?php
namespace App\Admin\Controllers;
use App\Http\Controllers\Controller;
use Illuminate\Http\Request;
use Encore\Admin\Layout\Content;
use Encore\Admin\Widgets\Box;
class ChartjsController extends Controller
{
public function index(Content $content)
{
return $content
->header('Chartjs')
->body(new Box('Bar chart', view('admin.chartjs')));
}
}`


Extent log message about conflicted shards

Description
In my installation, in CouchDB logs messages I can see messages like
1 conflicted shard in cluster

I have tried to delete old databases and in the server logs can see
[critical] 2024-03-26T17:28:24.081510Z<EMAIL_ADDRESS><0.16743.70> -------- 1 conflicted shard in cluster
[critical] 2024-03-26T17:28:29.187245Z<EMAIL_ADDRESS><0.18085.70> -------- 1 conflicted shard in cluster
[critical] 2024-03-26T17:28:34.311446Z<EMAIL_ADDRESS><0.21253.69> -------- 1 conflicted shard in cluster
[critical] 2024-03-26T17:28:39.541320Z<EMAIL_ADDRESS><0.31584.67> -------- 1 conflicted shard in cluster
[critical] 2024-03-26T17:28:44.649152Z<EMAIL_ADDRESS><0.20660.67> -------- 1 conflicted shard in cluster
[critical] 2024-03-26T17:28:49.717562Z<EMAIL_ADDRESS><0.23910.70> -------- 1 conflicted shard in cluster
[critical] 2024-03-26T17:28:54.921189Z<EMAIL_ADDRESS><0.9403.70> -------- 1 conflicted shard in cluster
[critical] 2024-03-26T17:29:00.033066Z<EMAIL_ADDRESS><0.19084.68> -------- 1 conflicted shard in cluster
[critical] 2024-03-26T17:29:05.174271Z<EMAIL_ADDRESS><0.25777.70> -------- 1 conflicted shard in cluster
[critical] 2024-03-26T17:29:10.262848Z<EMAIL_ADDRESS><0.30249.69> -------- 1 conflicted shard in cluster
[critical] 2024-03-26T17:29:15.402787Z<EMAIL_ADDRESS><0.27844.70> -------- 1 conflicted shard in cluster
[critical] 2024-03-26T17:29:20.721704Z<EMAIL_ADDRESS><0.20999.70> -------- 1 conflicted shard in cluster
[critical] 2024-03-26T17:29:25.680320Z<EMAIL_ADDRESS><0.100.70> -------- 1 conflicted shard in cluster
[critical] 2024-03-26T17:29:30.777084Z<EMAIL_ADDRESS><0.243.71> -------- 1 conflicted shard in cluster
[critical] 2024-03-26T17:29:35.905120Z<EMAIL_ADDRESS><0.23983.70> -------- 1 conflicted shard in cluster
[critical] 2024-03-26T17:29:41.078100Z<EMAIL_ADDRESS><0.4260.71> -------- 1 conflicted shard in cluster
[critical] 2024-03-26T17:29:46.252992Z<EMAIL_ADDRESS><0.5119.71> -------- 1 conflicted shard in cluster
[critical] 2024-03-26T17:29:51.305345Z<EMAIL_ADDRESS><0.6351.71> -------- 1 conflicted shard in cluster
[critical] 2024-03-26T17:29:56.444482Z<EMAIL_ADDRESS><0.6549.71> -------- 1 conflicted shard in cluster
[critical] 2024-03-26T17:30:01.605705Z<EMAIL_ADDRESS><0.5639.61> -------- 1 conflicted shard in cluster
[critical] 2024-03-26T17:30:06.766324Z<EMAIL_ADDRESS><0.9687.69> -------- 1 conflicted shard in cluster

These log messages do not provide information about:

database with conflicts;
shard file;
conflicted revision id.

Could you extent logs message?
Steps to Reproduce
I do not know
Expected Behaviour
Log messages should allow identifying conflicted database, shard, and revision id.
Your Environment

CouchDB version used:

{
  "couchdb": "Welcome",
  "version": "3.3.3",
  "git_sha": "40afbcfc7",
  "uuid": "385419103339-esrp",
  "features": [
    "access-ready",
    "partitioned",
    "pluggable-storage-engines",
    "reshard",
    "scheduler"
  ],
  "vendor": {
    "name": "The Apache Software Foundation"
  }
}

Browser name and version:
Not used

Operating system and version:

NAME="CentOS Stream"
VERSION="8"
ID="centos"
ID_LIKE="rhel fedora"
VERSION_ID="8"
PLATFORM_ID="platform:el8"
PRETTY_NAME="CentOS Stream 8"
ANSI_COLOR="0;31"
CPE_NAME="cpe:/o:centos:centos:8"
HOME_URL="https://centos.org/"
BUG_REPORT_URL="https://bugzilla.redhat.com/"
REDHAT_SUPPORT_PRODUCT="Red Hat Enterprise Linux 8"
REDHAT_SUPPORT_PRODUCT_VERSION="CentOS Stream"

Additional Context

Conflicted shards means that the database metadata doc in the _dbs has a conflicts. That database is replicated in a circle (n1->n2->n3->n1) and since any node can receive database creation requests it's possible to get conflicts in those documents. We only use the winning (latest) version of the db but warn the user via custodian (a helper background watcher service) if there are conflicts present. I believe you can delete the conflicted revision one of the nodes (via /_node/_local/_dbs/$dbname) and then custodian will stop reporting it.
The code that detects is somewhere here: https://github.com/apache/couchdb/blob/main/src/custodian/src/custodian_util.erl#L206-L208

Could you update the log message to
1 conflicted shard in the cluster, please check "_dbs" REST endpoint for all cluster nodes

I think it may work as a documentation string better as opposed a longer log message. Maybe a paragraph in the docs indicating what the error means, with a few examples, so it's easy to search, and how to react to it.


Show current price

I wanted to see the current price without having to show the entire past 24hours, I think changing the date comparison to -30 minutes should do it? it seemed to work on my end but feel free to ignore this PR if this is the wrong way to go about it or if you don't want this feature.
Love the card thanks for your work!

Not sure If I've even done this PR correctly, accidentally made it on my own fork first of all 🤦

Thanks so much for this! Makes way more sense. I made some other changes so I incorporated this in my latest release which is now available (v0.1.3)


checkbox inside a tag not clickable

When I click the checkbox the list item is selected, but not the checkbox. And I can not clear it.
BOWER:  "dependencies": {
    "angular": "~1.4.7",
    "angular-animate": "~1.4.7",
    "angular-cookies": "~1.4.7",
    "angular-resource": "~1.4.7",
    "angular-route": "~1.4.7",
    "angular-sanitize": "~1.4.7",
    "angular-touch": "~1.4.7",
    "angular-bootstrap": "~0.14.3",
    "bootstrap": "~3.3.6",
    "angular-oauth2": "~3.0.1",
    "angular-spring-data-rest": "~0.4.3",
    "ng-duallist": "~0.0.9"
}

I changed the tag for the div and it worked.

    {{data.name}}
    <input ng-model="data.selected" class="pull-right" type="checkbox">

@danbit thanks for reporting bug,
New version released


Changed volume for preprocessor

What's done:

changed volume for preprocessor from hostPath to emptyDir

It closes #2119

Tested locally:


C3s mapping

Overview
This PR resolves the issue of having hard coded the project as c3s-cmip6, it also includes a use_inventory option in roocs.ini
It will only work with an updated inventory with CMIP6 replaced with c3s-cmip6 and the base_dir and paths edited - see https://github.com/cp4cds/c3s_34g_manifests/pull/6
Issues https://github.com/roocs/34e-mngmt/issues/75 and https://github.com/roocs/rook/issues/85

@ellesmith88 can this be merged (after conflict resolution) or should we wait?

@ellesmith88 can this be merged (after conflict resolution) or should we wait?

@ellesmith88 can this be merged (after conflict resolution) or should we wait?

Yes could be merged but won't work properly until the inventory is updated - which can only be done when the production system is updated otherwise things will break for James. I'm going to do a pull request to this branch so maybe after that?

@ellesmith88 can this be merged (after conflict resolution) or should we wait?

Yes could be merged but won't work properly until the inventory is updated - which can only be done when the production system is updated otherwise things will break for James. I'm going to do a pull request to this branch so maybe after that?

@ellesmith88 can this be merged (after conflict resolution) or should we wait?

Yes could be merged but won't work properly until the inventory is updated - which can only be done when the production system is updated otherwise things will break for James. I'm going to do a pull request to this branch so maybe after that?

Ok. Feel free to merge when ready.

@ellesmith88 can this be merged (after conflict resolution) or should we wait?

Yes could be merged but won't work properly until the inventory is updated - which can only be done when the production system is updated otherwise things will break for James. I'm going to do a pull request to this branch so maybe after that?

Ok. Feel free to merge when ready.


in Mobile/tablet the Carbon Design System home button does not work

FYI @jeanservaas @alisonjoseph

Actually might be a Gatsby issue since Gatsby demo site does not work either

It looks like it's due to bx--header__global being placed over a.Header, changing the z-index resolves the issue but should be fixed in the theme 👍


Text captilization

Description
MA-2310
Add a description of your changes here.
Notes
How to test this PR
Reviewers
If you've been tagged for review, please check your corresponding box once you've given the :+1:.

[x] Code review: @BenjiLee
[x] Code review: @danialzahid94

👍

👍


WIP Fix travis

Still not working, in the repo, in this specific branch (fix_travis) you can do:
conda create -n test python=3.6 notebook
source activate test

then
conda install -c conda-forge nb_conda_kernels
conda install --file requirements.txt
npm install
pip install -e .
jupyter nbextension install nb_anacondacloud --py --sys-prefix
jupyter nbextension enable nb_anacondacloud --py --sys-prefix
jupyter serverextension enable nb_anacondacloud --py --sys-prefix

then
jupyter notebook

and try using the nb_anacondacloud extensions triggers:
[W 07:00:58.436 NotebookApp] 403 POST /anaconda-cloud/publish (<IP_ADDRESS>): '_xsrf' argument missing from POST
[W 07:00:58.440 NotebookApp] 403 POST /anaconda-cloud/publish (<IP_ADDRESS>) 5.25ms referer=http://localhost:8888/notebooks/Untitled.ipynb

@minrk, can you try to reproduce? I am pretty sure I don't have stale js around...

Coverage increased (+1.3%) to 49.3% when pulling 8f06e36e3b7b56a96de0401f8827a3c26dea4913 on fix_travis into c1f50f3f99043b2d35fe5bc6e78f7ddc11459d13 on master.

This is ready now. Merging.


cell editor load text box on load of grid

Dear Team,
Thank you for the extensive table features?
I have 2 quick questions which i did not found any documentation (at least what i see)

Loading grid with default controls on cells like loading grid with textbox or dropdown. I see editor but this has only 2 events like click and dbclick. is there any onload event ?

Is table is accessible ?

This is not an issue but checking if there is a help on these 2 items ?
Thanks

@rajaveernapu sorry for lately reply, about your two questions, i think I'm still not very clear:

Not very clear about first question
I think no, but what kind of accessible you want?

@AllenFang I am sorry , i didnt get any notification on this .
I have a requirement of load text box when loading grid as editable column. It is like want to show a textbox in one of the column.
JAWS and KEROS accessible tools are not reading this table headers. How can we add aria labels to headers ?
I have one css file , is there anyway to completely override my css with css default coming from package ?
Thanks Again for your help.

JAWS and KEROS accessible tools are not reading this table headers. How can we add aria labels to headers ?

Would you please point me where should I add the aria label on headers?  I can help to add :)

I have one css file , is there anyway to completely override my css with css default coming from package ?

I think you can overwrite the css anytime.

I have a requirement of load text box when loading grid as editable column. It is like want to show a textbox in one of the column.

so far we don't have this feature

Thank you. We should have aria controls on our header columns and rows too dynamically.
Any plan to add onload editable textbox/dropdown/textarea ??

@rajaveernapu sorry for lately reply, too busy lol .  I think i can implement it but no schedule so far. so any PR is welcome, thanks

Sure Allen , any references for it where i can go and add an event would be appreciated. I tried add a formatter with textbox but it is some how killing pagination and not sure what is relation with it.
Can you suggest me to a right place where i can add onload textbox and dropdowns to my grid.


[Ubuntu,Windows] add Android NDK 27 version to images

Description
This PR consists of below changes

Add Android NDK 27 version to images.
makes default version to NDK 27.

Related issue:
10314
Check list

[x] Related issue / work item is attached
[ ] Tests are written (if applicable)
[ ] Documentation is updated (if applicable)
[ ] Changes are tested and related VM images are successfully generated

May I ask why macos was excluded from this update?

d'accord

what about macos?


Splashdown documents

Likely the final ticket to have the label "Orbital".

[x] Poster
[ ] Video

@VietAnh1010 Once again could you do the video?
PDF: splashdown-slides-v1.pdf
Figma: prototype this one is slightly better because navigation is kinda smoother with some animation (I hope I have removed all non-free fonts, now it should render on all operating systems)
Contact me asap if you want to have any changes.

Is the video done? I initially planned to do it this afternoon.

Done, submitted. Although you could redo it and submit again, but I guess no need to. (I won’t be free this afternoon anyway.) Now all we need to do is to sit back and relax, because everything is done.


Add expect_column_stdev_to_be_greater_than test

This PR adds a new test to assert whether the stdev of a column is greater than a defined value.

I think code-wise this looks good (except that one extra distinct), but we'll need to add an integration test to the test project's schema.yml here.
If there is not a column already suitable for this, we'll need to add either a test model (I've been avoiding/putting off doing seeds for each test and instead have been generating test data in select statements) or a new column to an existing model so I can test this across platforms. Does that make sense?

Got it. Will work on that tomorrow :)

@MartinGuindon I just pushed the 0.3.4 release which includes support for the type of test you're doing here. I think these new options should take of what you needed in this PR, so I'll go ahead and mark it closed. Feel free to open this again though if you think we still need it.
dbt_expectations.expect_column_stdev_to_be_between:
    min_value: 0
    strictly: True

That's awesome and should work nicely! Thank you!


integration test flake: delegate_and_undelegate

The change in #1519 reducing the epoch duration for the smoke test also increases the probability that the integration test delegate_and_undelegate will fail if the epoch transition occurs during the test, e.g. see build here:
---- delegate_and_undelegate stdout ----
thread 'main' panicked at 'Unexpected failure.
error: test failed, to rerun pass '-p pcli --test network_integration'
code-1
stderr=```"Error: Error submitting transaction: code 1, log: undelegation was prepared for next epoch 9 but the next epoch is 10\n"```
command=`"/home/ubuntu/actions-runner/_work/penumbra/penumbra/target/debug/pcli" "--data-path" "/tmp/.tmp13d6kT" "tx" "undelegate" "0.99delegation_penumbravalid1rfedd9y9w5dc8gf7q6hmumkexxswxkgeklk724cet8v7t7g00yzsvqg7rw"`
code=1
stdout="Scanning blocks from last sync height 84 to latest height 88\npre-checking transaction...\nbroadcasting transaction...\nconfirming transaction  ...\ntransaction confirmed and detected\npre-checking transaction...\nbroadcasting transaction...\n"
stderr="Error: Error submitting transaction: code 1, log: undelegation was prepared for next epoch 9 but the next epoch is 10\n"
', /rustc/a55dd71d5fb0ec5a6a3a9e8c27b2127ba491ce52/library/core/src/ops/function.rs:248:5
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

Options:

Increase epoch duration (not really a fix, just reduces the probability it occurs, and it increases the length of the test)
Try the delegate and undelegate tasks n times and fail the test if they fail n times, probably n=3 is good

Got hit by this just now :( https://github.com/penumbra-zone/penumbra/pull/1526


Define types for document id and database name

Define DocumentId and DatabaseName types. These types would replace the &str type currently used for identifying documents and databases, thereby making our crate's API more type-safe.

This can be conveniently done using traits.
In the example below, our crate defines the DatabaseName trait and the DatabaseLiteral type, and the application defines the Db type to implement DatabaseName.
Doing it this way allows applications to specify a plain string literal (using the DatabaseLiteral type), while also allowing applications to implement custom database name types of unlimited complexity.
trait DatabaseName {
    fn database_name(&self) -> &str;
}

struct DatabaseLiteral<'a>(&'a str);

impl<'a> DatabaseName for DatabaseLiteral<'a> {
    fn database_name(&self) -> &str {
        let DatabaseLiteral(s) = *self;
        s
    }
}

enum Db {
    Alpha,
    Bravo(String),
}

impl DatabaseName for Db {
    fn database_name(&self) -> &str {
        match *self {
            Db::Alpha => "alpha",
            Db::Bravo(ref s) => s,
        }
    }
}

fn head_database<D>(name: D) -> () where D: DatabaseName {
    println!("{}", name.database_name());
}

head_database(Db::Alpha);
head_database(Db::Bravo("hello".to_string()));
head_database(DatabaseLiteral("foo"));

Resolved in this commit: 9ec3eed70efbdad9aa6e2f464b3b8db9173967f6.


Investigate multiple dashboards workflow

We are planning to rotate multiple dashboards - one per project and a couple of global leaderboards. It's emergent to investigate how this feature works, because it may affect jobs implementation.

I found this one some weeks ago. I believe, it couldn't affect jobs.
https://github.com/vrish88/sinatra_cyclist

@mogol thanks, I'll have a look! The question is - if we have the same kind of widget on multiple dashboards (e.g. an average rating widget), how should a job be constructed? Can it send data to widgets on hidden dashboards as well?

We have to try. But according to Dashing docs, Yes, it send data to all widgets

I have this implementation now:
project_manager.obtain_all_projects.each do |project|
    reviews = service.obtain_reviews_for_app_id(project.appstore_id)
    widget_name = "appstore_rate_#{project.appstore_id}"
    send_event(widget_name, {
                              'title' => rating.round(2).to_s
                          }
    )
  end

This one was really an easy task.

I've implemented cycling, currently between two dashboards. It can be triggered by using URL: dashboard_url/_cycle?duration=30s.
Dashing updates all widgets, even on hidden dashboards.


Move swarm quickstart the separate repo

Its very slow and downloads a lot of stuff, that makes the build take too long. For example doing PRs to forge takes 15 min due it checks all archetypes and the swarm is dead slow.
There is a new git repo at, where it can live
https://github.com/fabric8-quickstarts

+1
the release now takes 20 mins longer too

The example has been moved here
https://github.com/fabric8-quickstarts/swarm-camel


Love this app, being using it for over a year. But...

Seems to have stopped working recently. Though all my custom stylesheets are enabled, they are not being loaded. And I can no longer edit them in the stylebot options. Clicking the edit button doesn't seem to do anything.

Thanks @Matterful, can you add your OS version and Chrome browser version here. Thanks

I think I'm getting a similar issue here: I newly installed Stylebot, but the "Open Stylebot" and right click "Style Elements" options don't do anything at all.
Running Chrome 43.0.2357.130 m on Windows 7.

Sorry about that, I should've been more specific. I'm on OS X Yosemite version 10.10.3, runnning Chrome 43.0.2357.130 (64-bit).

Hopefully this helps a bit more. Here is the error messaging from my console, when on the stylebot options page.
Uncaught TypeError: Cannot read property '_enabled' of null      -----  @ace.js:101
Missing module:
Reactlookup @ ace.js:101
window.require @ ace.js:83(
anonymous function) @ VM146:49
(anonymous function) @ VM146:256
InjectedScript._evaluateOn @ VM143:895
InjectedScript._evaluateAndWrap @ VM143:828
InjectedScript.evaluate @ VM143:694
Missing module: react   --- @ace.js:101

I can confirm Matterful, having the same issue. Everything was working fine yesterday but today it doesn't want to play ball.
"Uncaught TypeError: Cannot read property '_enabled' of null"


AVRO-3985: Add trusted packages support in SpecificData

What is the purpose of the change
This change introduces the org.apache.avro.SERIALIZABLE_PACKAGES system property to enforce the security aspect of using java-class in a schema.
Verifying this change
This change is already covered by existing tests, using the default trusted packages. I can add an additional test specifically for non trusted packages.
Documentation

Does this pull request introduce a new feature? yes
If yes, how is the feature documented? The error message already explains how to use org.apache.avro.SERIALIZABLE_PACKAGES system property. Happy to add additional documentation if needed.

@Fokko @martin-g @KalleOlaviNiemitalo I updated the PR. Can you guys please take a look ? Thanks !

Moving this forward, thanks @jbonofre for fixing this 🙌  and thanks @martin-g and @KalleOlaviNiemitalo for the reviews!


Proposed changes for 1.3 schema

Proposed schema changes for 1.3 that add manifest support for the following issues. This is only a proposal so all changes appear in the 1.2 installer manifest. Once approved, I will work to create the 1.3 schema and add the changes to all relevant manifests.
Parent Issue: #1997
Related to:

#2183
#2097
#2041
#1885
#1665

I have gone through each issue listed in the 1.3 manifest schema thread and selected the ones that I believe we can reasonably target for the 1.4 client. This is in addition to the fields needed for support zip installation.


auth

Dont find possible ways to protect swagger
doesnt work
  .guard(app =>
    app
    .use(isAuthenticated)
    .get("/swagger/json", redirect("/swagger/json"))
    .get("/swagger", redirect("/swagger"))
  )
  .use(swagger())

isAuthenticated here is plugin with checking auth credentials.
What can be done ? =>
The fastest way to impement mannual auth
.use(swagger({
   authToken: "token_1234"
})

The user must manually enter a token in the browser, which will be used in the request headers

I have the same problem, I want the endpoints in swagger to appear as protected but I can't do it. The documentation does not show examples

Unfortunately the security configuration didn't work for me.
swagger 1.2.0


journalist: init at 1.0.0-unstable-2024-05-28

Description of changes
Closes #317832

Things done

Built on platform(s)

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

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

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

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

[ ] Fits CONTRIBUTING.md.

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

Tested this one with https://github.com/NixOS/nixpkgs/pull/318317 since it depends on this one. I haven't encountered any problems.


after_script not working on custom CRUD views

Bug report
What I did:
Create a custom CREATE view using $this->crud->setCreateView('your-view');,

Then I added after scripts:
@section('after_scripts')
    <script type="text/javascript">
        alert('hahahah');
    </script>
@endsection

What I expected to happen:
Alert shows "hahahah"
What happened:
Nothing happened. After scripts not loaded into the page
What I've already tried to fix it:
Everything
Backpack, Laravel, PHP, DB version:
Backpack: 3.2.19
Laravel: 5.5.13
PHP: 7

Thanks @lloy0076, you might be right. I also tried @push also didn't work.

@yingliangzhang - Backpack\Base 0.9.0 (to be launched in a few days) will allow you to use @push inside any custom view. It has both sections and stacks. Register on backpackforlaravel.com and you'll receive the newsletter as soon as it's launched. You'll then be able to upgrade your project to the latest version and use this feature.
Cheers!

Until then, you can modify your layout.blade.php with this change: under  @section('after_scripts') insert a line @stack('after_scripts').

@tabacitu Nice. Thank you😀

This problem still persists. I am trying to add some custom scripts in custom create file but nothing is happening.

@sdebarun you should be able to use both @push and @section in your custom blade files that extend the default layout:
@push('after_scripts)
  <script>alert('got here');</script>
@endpush

@section('after_scripts)
  <script>alert('got here');</script>
@endsection

Double-check for typos when writing after_scripts.


Toggle off/on Health Estimate on per token

Is your feature request related to a problem? Please describe.
Hi! Love the module! My problem is that I'd like the ability to show Health Estimate at certain times or on certain tokens, rather than only to all tokens or no tokens.
Describe the solution you'd like
I'd love it if I can show my players the enemy's health estimates on a per-token basis as a quick setting on the npc's character sheet, as an action HUD element, or on the combat tracker. In a session, I want to be able to make my players roll checks to see health estimates of their enemy in cases where it might not be readily apparent, such as when fighting strange/inscrutable creatures, BBEGs, or just things they haven't come across. That way, when they pass the check, I can enable the estimate on that enemy so they can better strategize.
Is this specific to system or is it system agnostic?
D&D 5e, but this could see use in many systems I suppose
Additional context
Nothing else comes to mind!

Check the actor's Prototype Token configs or a token's config for the Estimates tab. Also check the Configure Controls for the Health Estimate tab if you want to set an on-demand shortcut.

Closing as wontfix since this feature already exists.


Remove unnecessary resource functions

Closes: RHOAIENG-6359
Description
This PR removes unnecessary resourceDisplayName and resourceDescription functions. Places where those functions were used are now replace with the generic getDisplayNameFromK8sResource.
How Has This Been Tested?
npm run test
Test Impact
No new tests were added as this was to clean up the code and remove unnecessary functions.
Request review criteria:

Self checklist (all need to be checked):

[x] The developer has manually tested the changes and verified that the changes work
[x] Commits have been squashed into descriptive, self-contained units of work (e.g. 'WIP' and 'Implements feedback' style messages have been removed)
[x] Testing instructions have been added in the PR body (for PRs involving changes that are not immediately obvious).
[ ] The developer has added tests or explained why testing cannot be added (unit or cypress tests for related changes)

If you have UI changes:

[ ] Included any necessary screenshots or gifs if it was a UI change.
[ ] Included tags to the UX team if it was a UI/UX change (find relevant UX in the SMEs section).

After the PR is posted & before it merges:

[ ] The developer has tested their solution on a cluster by using the image produced by the PR to main

/lgtm
/approve
did some ad hoc testing running through various parts of the UI


Replace mockito with mockito-kotlin

mockito-kotlin covers the use cases of mockito so there is no need to depend on mockito any more.

I don't know, shouldn't we just use whatever version that mockito-kotlin is currently using? I'm okay with it, but I wonder why it's important to control mockito version ourselves.(For my future reference)

Using a newer minor version is usually OK, as there should be no API changes - there might be some bug fixes or performance improvements, so that's definitely good. The latest kotlin-mockito seems to be using slightly outdated Mockito version. But yeah, this is such a minor dependency that we could go either way.
Thanks for the contribution.


[Bug]: [Go SDK] periodic.impulse increases Dataflow Backlog time

What happened?
We have a slowly updating object that we'd like to use as a SideInput.
We've decided to utilize periodic.Impulse to periodically update the SideInput. We set the startTime to be "now" and the endTime to be "10 years later", with the intention of producing output endlessly.
However, we observed an extreme increase in the Backlog time, ballooning to around 600 weeks. We suspect that this is because we've set the endTime to be 10 years later.
Image below, Reaching to around 500 weeks = 10 years as I set as endTime.

It appears that Dataflow estimates the end of the job as "10 years later = 500 weeks", causing horizontal scaling of workers and resulting in the use of 100 workers.
Below is our simplified sample code, which closely follows this reference.
[Refrence] https://github.com/apache/beam/blob/dc1cfe54bfa0d3a22034f3fea463f0284cb2ba83/sdks/go/examples/slowly_updating_side_input/slowly_updating_side_input.go
func main() {
	flag.Parse()
	beam.Init()
	ctx := context.Background()

	checkFlags(ctx)

	project := gcpopts.GetProject(ctx)
	p, s := beam.NewPipelineWithRoot()
	pubsubCol := pubsubio.Read(s, project, *topicId, &pubsubio.ReadOptions{
		Subscription: *subscription,
	})

	timeInterval := 1 * time.Minute

	windowedPubsubCol := beam.WindowInto(s, window.NewFixedWindows(timeInterval), pubsubCol)

	periodicImp := periodic.Impulse(s, time.Now(), time.Now().AddDate(10, 0, 0), timeInterval, false)
	updatedSideInput := beam.ParDo(s, SideInputGeneratorDoFn, periodicImp)
	windowedSideInput := beam.WindowInto(s, window.NewFixedWindows(timeInterval),
		updatedSideInput,
		beam.Trigger(trigger.Repeat(trigger.Always())),
		beam.PanesDiscard(),
	)

	col2 := beam.ParDo(s, &DoFn1{}, windowedPubsubCol, beam.SideInput{Input: windowedSideInput})
	col3 := beam.ParDo(s, &DoFn2{}, col2)
	pubsubio.Write(s, *wProject, *wProjectId, col3)

	if err := beamx.Run(ctx, p); err != nil {
		log.Exitf(ctx, "Failed to execute job: %v", err)
	}
}

Issue Priority
Priority: 2 (default / most bugs should be filed as P2)
Issue Components

[ ] Component: Python SDK
[ ] Component: Java SDK
[X] Component: Go SDK
[ ] Component: Typescript SDK
[ ] Component: IO connector
[ ] Component: Beam examples
[ ] Component: Beam playground
[ ] Component: Beam katas
[ ] Component: Website
[ ] Component: Spark Runner
[ ] Component: Flink Runner
[ ] Component: Samza Runner
[ ] Component: Twister2 Runner
[ ] Component: Hazelcast Jet Runner
[X] Component: Google Cloud Dataflow Runner

just note Java PeriodicImpulse having the same issue. Its more likely a Dataflow issue of metrics

@Abacn
Thank you for your reply.
Then, is there a way to implement the slowly updating side input pattern with the Go SDK?
We have come up with some workaround ideas:

Use another PubSub to simulate the impulse.
Use windowing with beam.Trigger(trigger.Repeat(trigger.AfterProcessingTime().PlusDelay(timeInterval))) and beam.Combine to mimic the impulse.
Store data on local file so that each DoFns can access to it.

However, we would like to avoid complex implementations.

If I understood correctly this is just an artifact of Dataflow UI. Does it affect the functionality of PeriodicImpulse?

Same issue here with Python but without having explicitly specified an End Time. Once Dataflow scales up, it will not scale down. As you can see, it has many many weeks in backlog even though Data freshness is already 0 because everything is already being processed at a good pace after catching up with the real backlog

I believe this has to do with the fact that PeriodicImpulse uses ImpulseSeqGenDoFn which has a restriction_tracker behind the scenes. Similarly to a SplittableDoFn, it is indeed telling Dataflow that there is a huge backlog yet to process.
What would be the suitable alternative then for slowly-changing side inputs?

@kemkemG0 In case you did not manage to solve the issue, the whole problem is in the class ImpulseSeqGenRestrictionProvider in the method restriction_size which is the one that tells Dataflow how much backlog there is to be processed, and hence, it tells Dataflow not to downscale because there is too much to process yet.
In can be solved "easily" by replacing this method in a subclass for:
def restriction_size(self, unused_element, restriction):
        """
        This removes the backlog issue by specifying the size to be processed is 0
        """
        return 0

And then subclass ImpulseSeqGenDoFn so that it uses this RestrictionProvider and, finally subclass PeriodicImpulse so that it uses your ImpulseSeqGenDoFn

closed by https://github.com/apache/beam/issues/32506


Add configurable background tint for SegmentedProgressIndicator, for the segment in progress

Where a segment is in progress, in a SegmentedProgressIndicator, a useful option could be to have the background track painted in a different color, or the same color as the progress section but with an alpha applied.
This makes it easier for the user to see which segment is in progress, in cases where segments represent a particular task to be done.

Fixed in #547


Bad error location with flatten tagged enum

Hi! I attempted to deserialize a structure with a flattened tagged enum. However, when providing incorrect input data, the error's location is not properly indicated.
Code sample:
use serde::{Deserialize, Serialize};

#[derive(Debug, Serialize, Deserialize)]
struct Task {
    id: String,
    #[serde(flatten)]
    task_type: TaskType,
}

#[derive(Debug, Serialize, Deserialize)]
#[serde(tag = "type", content = "params", rename_all = "snake_case")]
enum TaskType {
    Complex(ComplexTaskParams),
}

#[derive(Debug, Serialize, Deserialize)]
struct ComplexTaskParams {
    param_one: String,
    param_two: String,
}

fn main() {
    let yaml = r#"
        id: 1
        type: complex
        params:
            param_one: value_one
            param_two: 123
    "#;

    let task: Task = serde_yaml::from_str(yaml).unwrap();
    print!("{:?}", task);
}

Expected error location of param_two - line: 5, but it's locate start position of Task:
thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value:
Error("invalid type: integer `123`, expected a string", line: 2, column: 9)', src/main.rs:31:49

This is a duplicate of #1183. With flatten the data gets deserialized into an intermediate buffer, advancing the location in the yaml file, but then fails to deserialize the buffer data into the struct.


List of possible features to implement

https://github.com/ets-labs/python-dependency-injector/pull/765

Maybe some configuration provider https://python-dependency-injector.ets-labs.org/providers/configuration.html
Object provider https://python-dependency-injector.ets-labs.org/providers/object.html
Dict provider https://python-dependency-injector.ets-labs.org/providers/dict.html
Selector provider https://python-dependency-injector.ets-labs.org/providers/selector.html
Allow dynamic attributes assignment in container https://python-dependency-injector.ets-labs.org/containers/dynamic.html

Is there're a way for adding those in a way that wouldn't break type checking and require typing.cast() usage?

Injecting a factory–I use that a lot. I like the way pdi fills in args for you when it gives you a Factory in a caller.
The way pdi does configuration isn't great. I use pydantic-settings v2 and to get it into a Configuration object in pdi I had to hack it + you lose type safety. Seems hard but would be so great to solve!
I use Selector a lot, it's a great feature.

I'm stoked to see this project coming along! If any of these sound like good starter tasks I'd be interested in trying one out. I'm using pdi in production at my job and need a path forward!

Thank you, Jason! Great to hear, that this project can became useful not only for my projects.
I will split this issue into parts and will write ideas, how they can be implemented, so anyone can contribute.

Injecting factory itself moved to https://github.com/modern-python/that-depends/issues/27

Object provider moved to https://github.com/modern-python/that-depends/issues/28 and looks like good starter's task

Dict provider moved to https://github.com/modern-python/that-depends/issues/29 and looks like good starter's task also


Possible to get example of use

I have the following, as shown in the readme:
.use(metadata({
templatedata: 'templatedata.yaml'
}))
and
templatedata.yaml in the 'src' directory (containing varname: value)
But varname when used in a template is not recognised
I think I just need to do more, but I can not see an example of use (and that is something that can help others too).
EDIT: tried also with .json and json data form, same result. No global metadata (at least not available to templates)

In your template, it should be presented as templatedata.varname.


Fix type detection with null

This tries to address #26
The PR contains:

Fixes simple type detection when format is applied to multiple types
Breaks the guesser chain when a DateTime guesser guesses a type (should be expanded to a more general solution, possibly object guessers should break the chain)
If a MultipleType is a nullable object type, then typehint is correctly set to the object with the optional null value as usual.

Close in favor of #31, Thanks :)


Expected @ at record start.

I am getting the following error:
faster -t 20240327-54345-2B1-LAB5262-L144596.bam_dcc.fastq.gz > faster_results.tsv
thread 'main' panicked at src/main.rs:404:14:
Failed to parse fastq record!: Custom { kind: Other, error: "Expected @ at record start." }
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

So it seems as if the fastq file is corrupt? However, other programs had no problem with this file (e.g. assembled with hifiasm without hitch). Any ideas?
Thank you

Okay I just checked, and the fastq file does start with @:
gunzip -c 20240327-54345-2B1-LAB5262-L144596.bam_dcc.fastq.gz > uncompressed.fastq
head uncompressed.fastq
@m54345U_240329_012903/73926044/ccs
TACAAACATGACAAGGGGAAGGAAAAGCCTTTCAATAGAACCTGA

So why this error?

Hi,
can you try faster2 (it's faster and I maintain it more now)?
https://github.com/angelovangel/faster2
It takes similar parameters like faster.
If this doesn't work may be try seqkit stats to get similar metrics...

Oh great, I hadn't realised that there is a new version! Faster2 works without problem on my file (and probably faster). Thank you so much for this amazing tool!


Fixes #93: Logical Switch refresh conflict

Description
Changed the name of method to refresh_data_state! and the conflict was fixed.
Issues Resolved
Fixes #93
Check List

[ ] New functionality includes testing.

[x] All tests pass ($ rake test).

[ ] New functionality has been documented in the README if applicable.

[ ] New functionality has been thoroughly documented in the examples (please include helpful comments).

[x] Changes are documented in the CHANGELOG.

The method is not referenced in the examples. But I'll put it in there.

The changes was done.


udp_tunneling: add udp tunneling

Additional Description: Last bit of #29277. This PR uses the previous PR classes (#29733) to support raw UDP tunneling over HTTP stream, either with connect-udp upgrade or POST request.
Risk Level: low, guarded by config
Testing: unit tests, integration tests
Docs Changes: API, docs, config examples
Release Notes: none
Platform Specific Features: none

/assign @DavidSchinazi
Thanks again for sticking with the reviews - this is the last PR for UDP tunneling. It adds the API config and uses the classes from previous PR to establish the tunnel, adds docs and integration testing.
Will appreciate your review, thanks

@mattklein123 would you have time to review the API changes alone? I assume Ryan may do a second pass afterwards, as he reviewed the previous PR

Yes I will do the API review tomorrow.

/retest

Thanks for your review @DavidSchinazi.
/assign @RyanTheOptimist
Since you reviewed the previous PR, I'll appreciate if you could review this one as well, as they are tightly related. Thanks. I assumed you'd be the right person to review this, but if it doesn't work for you or you don't currently have time to review, please assign someone else.
@mattklein123 not sure it's mandatory now, but I made a small rephrase in the API due to David's comment, can you please stamp it again?

/retesr

/retest

@RyanTheOptimist I made a small refactor, can you take a look again please? Thanks.


fix: update standalone to 1.88.25

Closed as Beth advised not to merge this version of the standalone


Question about wallpapers location

Hello, I have just spotted this project and would like to fork it. Can you tell me where have the wallpapers been put?

I don't even remember making this repository. Do as you wish with it.


Spotify Playlist Generator

Generate multiple playlists of a given size from a large Spotify playlist.

This script will generate multiple smaller spotify playlist from a large spotify playlist and shuffle them and add them to your spotify account
Type of issue

NOTE: These boxes can be checked using [X]

[X] Feature (New Script)

[ ] Bug

[ ] Documentation

Checklist:

[X] I have read the project guidelines.
[X] I have checked all the existing projects, before submitting a new project issue.
[X] I have checked previous issues to avoid duplicates.
[X] This issue will be meaningful for the project.

cool @sandyjswl  go for it, add your script under Miscellaneous

Sure thanks.


docs: Detail the setup process

I think the setup process needs to be a bit more detailed and reformatted for readability.

Poor readability at the moment. The docs just seem like a wall of text. I can submit a PR for this if required. +1 for inline code as well.

A link to the FAQ and more directions for troubleshooting would be great too. Using an external Postgres database, creating firewall rules to whitelist gunicorn, and so on. (DigitalOcean and Vultr have firewalls enabled in images it seems)

Point out what's stored in these:
  /opt/vespene
  /etc/vespene
  /var/log/vespene
  /var/spool/vespene
  /tmp/vespene/

I mean sure, I know Vespene's using these but what for? Where are the builds stored? Where can I keep project files? Is a .vespene file created when I create a project? Where is it?

GUNICORN_OPTS="--bind <IP_ADDRESS>:8000" was changed to GUNICORN_OPTS="--bind <IP_ADDRESS>:8000" and back to GUNICORN_OPTS="--bind <IP_ADDRESS>:8000". I was following the setup guide on docs.vespene.io so I didn't catch this and figured it was still using <IP_ADDRESS>.
This should go into the docs since we're asking people to run the scripts and not giving specific instructions on installing Vespene.

Since hostnames are used for referring to build workers, one way would be to refer to the master host using it's hostname as well to avoid the <IP_ADDRESS> and <IP_ADDRESS> issue.

Edit: TIL there's also http://docs.vespene.io/development_setup.html ;_;

Hi,
This is really a lot of different things.
If you would like to discuss them I would suggest commenting on the docs topic on talk.vespene.io and I can go into detail on each. The forum is for feedback and this queue is for bugs.
Regardless, some comments now:
The hostname is not public because without a SSL configuration it would be an insecure default. This can be provided through gunicorn or NGINX/Apache. That could possibly be added to the security guide.
I think most poeple know what those paths mean but I’m open to some clarification and thoughts from multiple readers are welcome. Vespene projects live in the database and .vespene files live in the source git repos.
Anyway if you can stop by the forum docs feedback thread that would be great!
I would not spend time on rewriting my docs - I’m very opinionated there and these took weeks to write - and there is a chance edits may lose some detail.


Webjars

@JothiShobana Please sign the Contributor License Agreement!
Click here to manually synchronize the status of this Pull Request.
See the FAQ for frequently asked questions.

@JothiShobana If you would update this branch to match the latest version of the guide and sign the CLA, we can definitely fold your PR in!

Someone needs to patch the pom.xml as well.

I didn't realize how old this branch is. The edits to README are to its old markdown version. Need to overhaul the whole thing and edit the asciidoctor version, as well as both "initial" and "complete" maven/gradle builds.

I'm closing this PR as being too old to salvage.


keylime_agent invalid TOML value

Starting the agent results in:
Error: Config(invalid TOML value, did you mean to use a quoted string? at line 2 column 16 in ../etc/keylime/agent.conf.d/bz2114485.conf)

[agent]
tpm_hash_alg = sha256

And also:
Error: Config(invalid TOML value, did you mean to use a quoted string? at line 2 column 10 in ../etc/keylime/agent.conf.d/run_as.conf)

[agent]
run_as = keylime:keylime

--> all must be in quotes

@mpeters can you have a look at it?
It seems like that the migration still is in place for the old Python agent and overrides the rust agent config.

Yeah, it definitely seems like a bad interaction with the old agent install stuff. I'll take a look at it. Maybe our python installer needs to not install the python agent (by default).

With the new agent and  when quoting the values all works smoothly. I had the impression that the new rust agent is already used. What I do rigth now to patch it with my config is:
vagrant ssh -c "sudo -u keylime rm -f /etc/keylime/agent.conf.d/*"
vagrant scp ../keylime-emulator-config/agent.conf /tmp
vagrant ssh -c "sudo mv /tmp/agent.conf /etc/keylime/agent.conf.d/"
vagrant ssh -c "sudo chown -R keylime:keylime /etc/keylime/agent.conf.d/"

I have to do it anyway, since I have to use an external registrar_ip for my tests.

Yes, the latest updates to the vagrant env are using the rust agent. I think there's some interaction with the old python agent install code that updates configs that's messing with the rust agent's configs. I'll dig into it


Support provenance metadata

The documentation of provenance metadata is an important and growing need of data publishers. Consider supporting provenance at the dataset level of an EML record for internal (to PASTA) and external data sources.

I just received a request for this feature from some folks at IEP and recently processed a dataset my self, via ezEML, in which I had to manually construct the provenance. Would be great to have this feature built in to this awesome metadata editor!

Enhanced in release 2021.07.07. The group decided that the way to handle this was to modify Method Step to add an optional "Data Sources" field. In the generated metadata, a section is appended to the Method Step description. If the Data Sources entry is "My data source... 2021", for example, the following is appended to the Method Step description:
                <para></para>
                <para>==================== Data Sources =========================</para>
                <para>My data source... 2021</para>
                <para>===========================================================</para>

It will be up to the data curator to modify the EML appropriately.


Adds concurrency and lock to team selection voting to avoid breaking

There are two fixes in here.
The simple one is to fix the issue where the .li command breaks the bot when there is no lobby info.
More complex is avoiding the bot breaking when users spam voting. As I worked on it, I realized what we really need is debouncing (so that we don't process reactions until the user stops spamming them). However, what I wrote here should definitely help. Added some concurrency on removing duplicate reactions in combination with a lock so that we don't get rate limited. This improves the processing speed of handling reactions by avoiding excessive communication with Discord. Currently, the bot:

fetches message
for each reaction, fetches users
for each reaction that's a duplicate by the user that we're currently processing, removes that reaction

This change eliminates the need for #1 and #2, just jumping straight to removing any duplicate reactions.
This could probably be a lot cleaner tho, like I mentioned above I think debouncing is probably the way to go, but just wanted to put this out for feedback at this point.

You probably shouldn't use # before your numbers unless intentional, I believe that links to old PRs lol. But this is some great information. For context, this is a little sloppy because the initial bot was not responding to reactions and we didn't know why. So there's some sloppy code we wrote trying to chase down something that worked.


Ensure all our lambda are concurrency safe

Describe the bug
Ensure all our lambda are concurrency safe
To Reproduce
Steps to reproduce the behavior:

Examine any lambda that takes more time to finish that the cron rate
See that another lambda can start concurrently before the previous run is done

Additional context
This was noticed to be the case on LH Prover Pub, and the fix to use a app based mutex worked.
For other lambdas (that are not idempotent), a mutex is needed to avoid overlapping lambda invocations

This was fixed by @wanglonghong


avoid Scalar::is_null_ptr, it is going away

Comparing pointers should be done more carefully than that

@bors r+

:pushpin: Commit 698b311a596b5d141b0c42f1b5400adc1f11150f has been approved by RalfJung

:hourglass: Testing commit 698b311a596b5d141b0c42f1b5400adc1f11150f with merge 16d791bf88760d62d9925efb387beadd93de64f0...

:sunny: Test successful - checks-travis, status-appveyor
Approved by: RalfJung
Pushing 16d791bf88760d62d9925efb387beadd93de64f0 to master...


Fix machine ref matching

Signed-off-by: Chuck Ha<EMAIL_ADDRESS>What this PR does / why we need it:
This PR allows the controller to match Refs with  machines properly.
Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #80
Special notes for your reviewer:
Release note:
NONE

/retest

/lgtm


feat(helm): added values README via helm-docs cli

What does this PR do?

Added README file to possess all values that traefik's helm chart reads
there are still improvements that will be done, like giving descriptions from the yaml's comments and optional values... but one PR at a time
Motivation

I checked the full value path I needed to write and reading from the yaml is difficult, for example ports is a long tree.
More

[x] Yes, I updated the tests accordingly
[x] Yes, I ran make test and all the tests passed

Hello @justmike1,
Thanks for your interests in Traefik and for this PR !
This can definitely help when using this chart.
I have some comments:

Wdyt about adding a Makefile target to re-generate this file?
There are a lot of parameters, so maybe we should keep this doc inside a specific file (like VALUES.md), in order to keep readability
README.md is copied to traefik/ in order to be displayed in artifacthub page. See here.

@mloiseleur

Added the Makefile target
You can't change the name of the file the helm-docs output. so I added renaming via Makefile
Changing to VALUES.md mitigates the issue, though in the future, when we will add also proper descriptions and default values via helm-docs supported comments and have a descriptive file, we will need to think a way to merge them sensibly and not just one on top of the other.

I use traefik for a year already and I don't see it change any time soon, so I will improve it with time.

I also added a test step in order for the file to stay updated upon PRs

That's better. I tried it by adding the needed -- into values.yaml for two first section and it looks good.
I guess we'll need to find how to properly display examples provided directly into values.yaml.

@mloiseleur anything more required to push this PR? I don't like big PRs, so I would suggest steps:

merging this PR
PR for refactoring values.yaml comments to helm-docs
PR for main README to have those values as well with keeping it's structure, like injecting them before contributions header, in order to be seen also in artifacthub

I don't have a strong opinion of PR size.
I do have a strong opinion that we should not merge an empty VALUES.md.
I agree with you that it could be merged within the README.
=> For this PR, I think it's missing two things:

Add the needed -- in values.yaml, to have a base on VALUES.md
In Guidelines, non critical features are commented. How could those features be documented with this system ?

@mloiseleur Sorry for repeating commits, VALUES.md is full now, pending your next review.
Currently, I don't see a way in helm-docs to document commented out parameters, maybe in future versions, so I believe keeping it as is, and maybe we can layer the documentation, and then make a full one that will be structured from the files in CD flow.

I should be able to review it on next friday. I'll keep you informed.

Thank you guys! @darkweaver87 @mloiseleur


hierarchical binding for vcml::tlm_target_socket: "(E126) sc_export instance already bound"

Hi,
I have a question wrt to hierarchical binding of vcml::tlm_target_socket.
The situation I have is:
I have a child module ("stream") with a vcml::tlm_target_socket ("stream_child_socket") and a parent module ("dma") with a vcml::tlm_target_socket.
If I bind now the parent-target-socket to the child-target-socket
        parent_socket.bind(stream.stream_child_socket);
I get the following error during elaboraton:
C++ exception with description "Error: (E126) sc_export instance already bound: tb.dma.stream.stream_child_socket
In file: /build/3rdparty/systemc/install/include/sysc/communication/sc_export.h:188" thrown in the test body.

What is the best approach to deal with this?
The SystemC language reference seems to indicate this behaviour is intentional for simple_target_sockets in table "Table 60—Permitted socket bindings". If I read this correctly.
But then I am wondering what the purpose of this template specialisation is:
https://github.com/machineware-gmbh/vcml/blame/8b21479538a35c7549dfe278e6dc71465619e46e/include/vcml/protocols/tlm_sockets.h#L372

To do a hierarchical TLM binding between the dma parent module and stream submodule, you need to use tlm::tlm_target_socket<> in the parent module (instead of a vcml::tlm_target_socket).
Then simply bind your stream.stream_child_socket to this new target socket.

Ok, but then I loose the vcml convenience functions like stub() and maybe trace()?

Correct. But you can still manually stub the socket using a vcml::tlm_initiator_stub.

How about having another specialization that adds an adapter if vcml::tlm_target_socket is connected to another vcml::tlm_target_socket even if they have the same width?

I think the correct way to handle this would be to move the desired functionality (stub, trace, ...) into a tlm_base_target_socket. We already do it like this for the other protocols (gpio, clk, ...) to allow stubbing of hierarchically bounds ports. In this context, "base" sockets support stubbing and adapters, but they can only forward transactions, not receive them.
We did not use this approach for normal TLM sockets, because we felt having the convenience sockets (e.g. simple_target_socket) would be more useful than building our own base sockets and then derive from them.
Having an adapter would surely work, but it introduces a lot of overhead (one extra sc_module) that could be avoided by using a hierarchical binding like it is intended by the standard.

Tracing should still work for the child socket.


cppcheck -  Strncpy-fills May Not Be Null Terminated

This ticket will is addressing the following cppcheck warnings:
E-JA/cfe/fsw/cfe-core/src/es/cfe_es_apps.c:502: warning: The buffer 'RamDiskPath' may not be null-terminated after the call to strncpy().
/home/bamboo-remote-agent/bamboo-agent-home/xml-data/build-dir/CFS-CFSCFE-JA/cfe/fsw/cfe-core/src/es/cfe_es_apps.c:807: warning: The buffer 'RamDiskPath' may not be null-terminated after the call to strncpy().
/home/bamboo-remote-agent/bamboo-agent-home/xml-data/build-dir/CFS-CFSCFE-JA/cfe/fsw/cfe-core/src/es/cfe_es_shell.c:122: warning: The buffer 'Cmd' may not be null-terminated after the call to strncpy().
/home/bamboo-remote-agent/bamboo-agent-home/xml-data/build-dir/CFS-CFSCFE-JA/cfe/fsw/cfe-core/src/es/cfe_es_shell.c:96: warning: The buffer 'OutputFilename' may not be null-terminated after the call to strncpy().
4-8-16 - CCB meeting discussed solution to replace strncpy call with CFE_SB_MessageStringGet

Imported from trac issue 151.  Created by sstrege on 2016-04-11T17:38:44, last modified: 2019-03-05T14:57:55

Trac comment by sstrege on 2016-04-11 18:19:53:
commit [changeset:9598030] ready for CCB review

Trac comment by sstrege on 2016-04-12 15:34:55:
CCB 4-12-16 - Updated to make returns void and replace destination string lenght macros with sizeof call.  Commit [changeset:fabd325] is ready for merge.

Trac comment by glimes on 2016-04-12 17:00:34:
Will do!

Trac comment by glimes on 2016-04-13 12:57:13:
Commits [changeset:9598030] and [changeset:fabd325] are now part of ic-2016-04-12.

Trac comment by jhageman on 2019-03-05 14:57:55:
Milestone renamed


Is there a way to make this work in Drawing mode?

This isn't an issue, more like a question.
I installed this thinking it would be great to use to update version number and date on drawing sheets, sadly missing in Fusion.
After reading the documentation fully and looking at sketches on the drawing sheets I can't see an obvious way to make this work. I can make it work in the Design mode, extrude the text and add that to a drawing but not simple on multipage drawings.
Am I missing something or is the limited sketch environment in the drawing sheets limiting this clever add-in?

Hi,
Fusion 360 currently provides very limited control of the Drawing mode from add-ins. It is simply not possible to change the texts in a Drawing from an add-in.
(For someone desperate writing add-ins who found this issue: There might be "Text Commands", but they are basically undocumented, often needs to drive UI dialogs (slow, disturbing) and are not guaranteed to work in future versions.)

Thanks for responding, I thought that may be the case. I'll carry on with the manually updating.


K8SPXC-835: Fix pxc-monit crash on replica cluster

This is for tests, real changes in https://github.com/percona/percona-docker/pull/484

Test name
Status

recreate
passed

upgrade-haproxy
passed

scaling
passed

haproxy
passed

restore-to-encrypted-cluster
passed

scaling-proxysql
passed

upgrade-proxysql
passed

security-context
passed

init-deploy
passed

demand-backup
passed

smart-update
passed

limits
passed

monitoring-2-0
passed

affinity
passed

one-pod
passed

pitr
passed

auto-tuning
passed

proxysql-sidecar-res-limits
passed

upgrade-consistency
passed

users
passed

demand-backup-encrypted-with-tls
passed

tls-issue-self
passed

tls-issue-cert-manager
failed

commit: https://github.com/percona/percona-xtradb-cluster-operator/pull/980/commits/e657398c6fc15e988be1850ca587632248f1649d
image: perconalab/percona-xtradb-cluster-operator:PR-980-e657398c

Test name
Status

upgrade-haproxy
passed

scaling
passed

scheduled-backup
passed

scaling-proxysql
passed

security-context
passed

big-data
passed

haproxy
passed

init-deploy
passed

limits
passed

monitoring-2-0
passed

affinity
passed

one-pod
passed

auto-tuning
passed

proxysql-sidecar-res-limits
passed

users
passed

tls-issue-self
passed

tls-issue-cert-manager
passed

storage
passed

tls-issue-cert-manager-ref
passed

upgrade-proxysql
passed

self-healing
passed

validation-hook
passed

smart-update
passed

upgrade-consistency
passed

self-healing-chaos
passed

self-healing-advanced
passed

self-healing-advanced-chaos
passed

operator-self-healing
failed

operator-self-healing-chaos
failed

commit: https://github.com/percona/percona-xtradb-cluster-operator/pull/980/commits/e657398c6fc15e988be1850ca587632248f1649d
image: perconalab/percona-xtradb-cluster-operator:PR-980-e657398c

Test name
Status

scheduled-backup
passed

storage
passed

self-healing
passed

self-healing-chaos
passed

self-healing-advanced
passed

self-healing-advanced-chaos
passed

operator-self-healing
passed

big-data
passed

scaling
passed

scaling-proxysql
passed

security-context
passed

upgrade-haproxy
passed

haproxy
passed

recreate
passed

init-deploy
passed

restore-to-encrypted-cluster
passed

limits
passed

demand-backup
passed

monitoring-2-0
passed

pitr
passed

affinity
passed

demand-backup-encrypted-with-tls
passed

one-pod
passed

auto-tuning
passed

proxysql-sidecar-res-limits
passed

users
passed

tls-issue-self
passed

tls-issue-cert-manager
passed

tls-issue-cert-manager-ref
passed

validation-hook
passed

upgrade-proxysql
passed

operator-self-healing-chaos
passed

smart-update
passed

upgrade-consistency
passed

commit: https://github.com/percona/percona-xtradb-cluster-operator/pull/980/commits/e657398c6fc15e988be1850ca587632248f1649d
image: perconalab/percona-xtradb-cluster-operator:PR-980-e657398c


[Feature request]: Support vim keybindings

This is more of a nice to have addition.

Support for moving around with the hjkl keys, and other ways of moving between the tree and main window.

This would be quite intuitive for new users who are used to using vim keybindings. (The first thing I tried was to move up and down with j and k :smiling_face_with_tear:)

@juftin Maybe have a similar setup for key bindings as you have for the themes? You could toggle the key bindings with V. What do you think?

:tada: This issue has been resolved in version 1.12.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


TCP-AO

Is routinator planning to support TCP-AO for RTR connections ?

TCP-AO needs to be implemented by the TCP stack, so this it not something that Routinator can implement on its own. If the underlying socket library supports TCP-AO, then we are not opposed to supporting it as well. However, I am a bit wary that each OS uses a different mechanism to enable and configure it and this will become a bit of a portability nightmare.
That all said, I am not entirely convinced that TCP-AO is the right choice for RTR connections. These connections should only exist within the management network which should be secured against the kind of interference TCP-AO protects against. Inter-site connections, meanwhile, need to be properly secured which would require the use of TLS or SSH. Am I missing something?

I'm happy to report an initiative has started to (finally) get this work done. The scope of work has been defined (BSD and Linux implementation) and the next step is to secure funding including applying with the RIPE NCC Community Projects Fund.
The team behind this initiative include, Max Stucchi (ISOC), Greg Hankins (Nokia), Stefan Wahl (Megaport), Philip Paeps (Alternative Enterprises), Ron Bonica (Juniper Networks) and Melchior Aelmans (Juniper Networks).

@partim As part of the work I'm proposing together with @maelmans et al, I intend to keep the socket layer as common as possible between platforms (Linux, BSD).  My proposal specifically includes support for BSD and Linux precisely to avoid portability nightmares.
Having said that, if our proposal is accepted, you can expect a patch from me to add support to routinator. :)

This is great news @maelmans, I hope the RIPE NCC Community Projects Fund request works out. Once this work is done we look forward to reviewing and including the patch by @ppaeps. Open source community work at its finest!


A way for search and get Country Code without any manual action.

I needed that find a CountryCode befor user select anythings by a default number.
then I add this function in fl_country_code_picker.dart
Future<CountryCode?> getByCode(String CodeNumber) async{
final allCountryCodes = codes.map(CountryCode.fromMap).toList();
for (var element in allCountryCodes) {
 if (element.dialCode == CodeNumber) {
   return element;
 }

}
return null; // Return null if the code is not found/ Return null if the code is not found
}
it works well for me .
I used it in my code like this
CountryCode? code =await countryPicker.getByCode(firstDigit);

Hello @MojtabaMohammadzadeh 👋
The CountryCode model already have that functionality, added at v1.0.7.
Example:
final phCountryCode = CountryCode.fromCode('PH');
if (phCountryCode == null) print("Ph country code not found!");

You also have the other convenient methods such as;
fromName, fromDialCode

Thank you very much. It realy helped me .
You are fantastic.

Cool, I'm glad to hear that! :)


Where is show.year?!

While watching a TV show, I'm not finding the year in User('[user]').watching.year nor in watching.episode and watching.show . Where's it hiding?

It may not be getting pulled back by PyTrakt--need to look into this.


Error

Description
[Insert description of issue here]
Detailed Information
Is available here

I think this means you have 2 schema-version lines in your database.  Keep the line which is "shcema-version: 1" and delete the other.