v21.1.2 refactor tests: GameInitiationRequestValidator

[Current coverage][cc-pull] is 100%

Merging [#523][cc-pull] into [master][cc-base-branch] will not change coverage

@@           master   #523   diff @@
====================================
  Files          28     28
  Lines         429    429
  Methods       108    108
  Messages        0      0
  Branches        0      0
====================================
  Hits          429    429
  Misses          0      0
  Partials        0      0

Powered by Codecov. Last updated by [c06b8e4...2ec13f8][cc-compare]
[cc-base-branch]: https://codecov.io/gh/eugene-matvejev/battleship-game-api/branch/master?src=pr
[cc-compare]: https://codecov.io/gh/eugene-matvejev/battleship-game-api/compare/c06b8e47a54a1785ebbc558c8f30315e5c926ca1...2ec13f8008d96933055d2c0409145efd4c580943
[cc-pull]: https://codecov.io/gh/eugene-matvejev/battleship-game-api/pull/523?src=pr


Watermark displays over text or not at all when images or urls are on a PDF page.

I used stamptk and pdktk to add watermarks to PDFs.  They display correctly in desktop based PDF viewers.
The watermark appears over the text when images are included in the page.
The watermark doesn't appear at all if urls are included on the PDF page.

When reporting an issue, please make sure that you read https://github.com/mozilla/pdf.js/blob/master/CONTRIBUTING.md, paying special attention to the first paragraph. I'm also quoting the relevant section:

[...] and provide more details about the issue: link to the PDF, location in the PDF, screenshot, browser version, operating system, PDF.js version and JavaScript console warning/error messages.

At the very least, you must provide a link to a PDF file that can be used to reproduce this issue.
If the PDF file isn't available online, please upload it to a file sharing service (e.g. Dropbox, Google Drive, Microsoft OneDrive or similar), and paste a link to the file here.

Closing as incomplete until the information requested above is provided. We need at least a PDF file to reproduce the issue.


[bug] Invoke function takes unusually long time to return a large Vec image data.

Describe the bug
I tracked all time of executions. The image was processed at rust end in a reasonable time but there exists an unusual delay between sending and receiving on the display built using React.
Reproduction
No response
Expected behavior
Fast Send.
Full tauri info output
[✔] Environment
    - OS: Ubuntu 20.04 X64
    ✔ webkit2gtk-4.0: 2.38.6
    ✔ rsvg2: 2.48.9
    ✔ rustc: 1.77.1 (7cf61ebde 2024-03-27)
    ✔ Cargo: 1.77.1 (e52e36006 2024-03-26)
    ✔ rustup: 1.27.0 (bbb9276d2 2024-03-08)
    ✔ Rust toolchain: stable-x86_64-unknown-linux-gnu (default)
    - node: 20.9.0
    - npm: 10.1.0

[-] Packages
    - tauri [RUST]: 1.6.1
    - tauri-build [RUST]: 1.5.1
    - wry [RUST]: 0.24.7
    - tao [RUST]: 0.16.8
    - tauri-cli [RUST]: not installed!
    - @tauri-apps/api [NPM]: 1.5.0 (outdated, latest: 1.5.4)
    - @tauri-apps/cli [NPM]: 1.5.1 (outdated, latest: 1.5.12)

[-] App
    - build-type: bundle
    - CSP: unset
    - distDir: ../build
    - devPath: http://localhost:3001/
    - framework: React

Stack trace
No response
Additional context
No response

This is not something we can fix in v1, but one of the main things we worked on for v2. It's still not perfect, see https://github.com/tauri-apps/tauri/issues/9190

Not sure if it's related, but currently I'm having the same trouble in Tauri v1, but with a regular text data - it takes insane amount of time to display.
Now, the good thing is that I figured out that it happens when the window is not focused. The second I click on it again, it instantly shows.
Obviously not saying this is the cause, but perhaps you have this type of problem as well, you should try refocusing the window again.
As for this problem, I will make a new issue tomorrow morning to describe it.

@FutureExcited I have similar experience. I have an app that runs in bg and window listens to events. Memory explodes out of proportions and I thought it was angular that was leaking out.
Any temp fix you got for this?

@anuradhawick  Unfortunately not. I'd recommend to try your luck in their discord


Large scale configuration example

The documentation should give an example on how to do a large scale load test across multiple jMeter workers  Guidance should be included as to how many virtual users can be handled per worker (ACI).

Thanks @mhackermsft! We'll be creating an example section soon.

Hello,
I have put together a sample implementation for larger infrastructures. I am unable to push any changes to this repo. Please could you let me know how to assign this issue to myself and also be able to raise a PR.
Thanks,
Hepsiba Reddy

Hi @fernandoBRS, any updates on this?
When I try to deploy this sample with many workers (for example, JMETER_WORKERS_COUNT = 80), the terraform provisioning almost always fails. Some container groups get stuck in 'Creating' state, and appear to be unable create a service association link with the vnet. I witness this behavior occasionally even with small number of workers (JMETER_WORKERS_COUNT < 10).
I am wondering if there are some established configurations or practices to handle large scale deployments with many workers? Glad to open a new issue if needed.
Thank you!


Rename --routes-location

Is your feature request related to a problem? Please describe.
Config file no longer called routes.json. We should call this something else.
Describe the solution you'd like
Maybe --config-location? Is it confusing if we have a CLI config too #20?

Naming is hard! What about?

--cli-config-location: for the CLI config
--swa-config-location: for staticwebapp.config.json

Ok. I think that works. It's unclear if one day we'll need to specify the CLI config too (probably). If that's the case, swa-config-location works. 😅


tour: [REPLACE WITH SHORT DESCRIPTION]

Context: https://go.dev/tour/welcome/1
Change the title above to describe your issue and add your feedback here, including code if necessary

https://instagram.com/erbayyuksell?igshid=YmMyMTA2M2Y=cansu

YmMyMTA2M2Y=cansu

YmMyMTA2M2Y=cansu


Add corner as dependency

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

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

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
1265

Relevant Lines:
1523

💛  - Coveralls

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Warning: This coverage report may be inaccurate.
This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

For more information on this, see Tracking coverage changes with pull request builds.
To avoid this issue with future PRs, see these Recommended CI Configurations.
For a quick fix, rebase this PR at GitHub. Your next report should be accurate.

Details

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

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
1265

Relevant Lines:
1523

💛  - Coveralls


Release a new version

Hello. I see some nice features in the master branch, however the last release is pretty old. Are you going to release a new version soon?

Hi! I'll agree it's time for a new release. I couldn't install version 2.1 cause of version collision with php-console-highlighter: I have 0.4, but release 2.1 is demanding 0.3.2

@povils  Any update?

Hey, thanks for pushing it. I will try this do this Monday))
On Fri, Aug 2, 2019, 17:01 Mark<EMAIL_ADDRESS>wrote:

@povils https://github.com/povils Any update?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/povils/phpmnd/issues/95?email_source=notifications&email_token=ACYAG4K7U6FSCQVT2DVLHB3QCRD23A5CNFSM4HNPSZE2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD3N722Y#issuecomment-517733739,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACYAG4JPX5S7GF2IXLSEIV3QCRD23ANCNFSM4HNPSZEQ
.

Did this release happen?

No release since january

New release not happening @povils ?

Hey, sorry for waiting! 2.2.0 release is here :)


add state to snapshot list

fixes #366

@moliware @lmenezes how does this look to you? can we merge this? thx in advance!

@moliware @lmenezes how does this look to you? can we merge this? thx in advance!

Code looks good! I'm merging, thank you!

nice, thanks!


fix orders of yaml for access-authn-authz/*

The order of kind and data were inconsistent, and that made the doc unreadable.
This fixes the orders in consistent way in reference/access-authn-authz/*
ref: #13862

/lgtm

/assign @Rajakavitha1 could you review and approve?

/approve


Typos in Page

A:
Note
Activity alerts are being deprecated. We recommend that you start using alert policies in the security and compliance center instead of creating new activity alerts. Alert policies provide addition functionality such as the ability to create an alert policy that triggers an alert when any user performs a specified activity, and displaying alerts on the View alerts page in the security and compliance center. For more information, see Alert policies.
Should be:
Note
Activity alerts are being deprecated. We recommend that you start using alert policies in the security and compliance center instead of creating new activity alerts. Alert policies provide additional functionality, such as the ability to create an alert policy that triggers an alert when any user performs a specified activity and displaying alerts on the View alerts page in the security and compliance center. For more information, see Alert policies.
B:
Tip
You might want to create an activity alert for just one activity that's performed by any user. Or you might want to create an activity alert that track multiple activities performed by one or mores users.
Should be:
Tip
You might want to create an activity alert for just one activity that's performed by any user. Or you might want to create an activity alert that track multiple activities performed by one or more users.

Hello @theokou! Can you please tell us to which article(s) your feedback applies? I suspect it's in our compliance content, but to be sure, and to route it to the correct writer, it would help to know which article we need to address. Thanks!

Hello @theokou! Can you please tell us to which article(s) your feedback applies? I suspect it's in our compliance content, but to be sure, and to route it to the correct writer, it would help to know which article we need to address. Thanks!

Hi Denise,
I am referring to article "Create activity alerts",  https://docs.microsoft.com/en-us/microsoft-365/compliance/create-activity-alerts?view=o365-worldwide

@leicham Thanks for submitting PR with fixes for these issues. I merged that PR.


How to use custom_css option in Ag-Grid ?

Hello,
I need to change the default 'blue' color of Ag-Grid in the Streamlit app to 'red' color
I didn't find any solution to add custom css to change the color of ag-grid table
So I tried the following 2 ways to change the color, but it didn't work.
Can any suggest the correct to do so ?
gb = GridOptionsBuilder.from_dataframe(df)
grid_options = gb.build()
grid_return = AgGrid(df,
theme='blue',
custom_css= {'background-color': '#ff0000'}
)
st.markdown('', unsafe_allow_html=True)

custom_css={".ag-row-hover": {"background-color": "red !important"},".ag-header-cell-label": {"background-color": "orange !important"}})


Feat/contextmenu

common ui

Context Menu

feature

[x] ContextMenuProvider
[x] ContextMenu
[x] ContextMenuItem

Codecov Report
Attention: Patch coverage is 63.00578% with 64 lines in your changes missing coverage. Please review.

Project coverage is 82.99%. Comparing base (6bf2595) to head (f2f1b54).

Files with missing lines
Patch %
Lines

src/components/ContextMenu/ContextMenuItem.tsx
52.63%
27 Missing :warning:

src/components/ContextMenu/ContextMenuProvider.tsx
50.00%
27 Missing :warning:

src/components/ContextMenu/ContextMenu.tsx
76.92%
6 Missing :warning:

src/components/Portal/PortalContent.tsx
72.72%
3 Missing :warning:

src/components/Portal/usePortal.ts
90.00%
1 Missing :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##             main      #27      +/-   ##
==========================================
- Coverage   83.99%   82.99%   -1.00%
==========================================
  Files          78       82       +4
  Lines        3511     3676     +165
  Branches      238      239       +1
==========================================
+ Hits         2949     3051     +102
- Misses        562      625      +63

Flag
Coverage Δ

82.99% <63.00%> (?)

Flags with carried forward coverage won't be shown. Click here to find out more.

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Incorrect Expected Answer for Quiz: Experience a Screen Reader

In Quiz: Experience a Screen Reader, the screen reader clearly states the role of the form element as "Edit text, email entry".  However this is marked incorrect, as the expected answer is "Edit text".

ah sorry if this is not more clear. Screen readers typically read both the role and the name together. So the role is Edit text and the name is email entry.


[image_picker] warning: Don't import implementation files from another package.

On trying the example of image_picker, there is a warning in IntelliJ that

Don't import implementation files from another package.

It refers to the two lines here
import 'package:flutter/src/widgets/basic.dart';
import 'package:flutter/src/widgets/container.dart';

The code seems to work fine after removing them.
Should I create a PR to remove those two lines?

Hi @asashour
These are unused imports, it won't throw affect the flutter run or flutter build, for some reason, these don't show any warning when running image_picker/example from clone flutter/plugin repo. This warning is thrown by the analyzer when copying the code sample into a regular Flutter project
We can totally remove these lines, feel free to create PR to remove these.
Thank you


Update dependencies and workflows

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 100.00%. Comparing base (7829cb2) to head (f993c07).

Additional details and impacted files
@@            Coverage Diff            @@
##              main      #102   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files           38        38
  Lines          817       817
  Branches        57        57
=========================================
  Hits           817       817

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


⚠ ClamAV has degraded performance

In 9cdd856, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 202 ms

Resolved: ClamAV performance has improved in 62dba94.


generalized followers

currently server/centralized.go expects act as either a leader with a single follower, or as a follower.
We should at least generalize to support n followers for single leader.

Right now it's set up for chaining.
e.g. leader -> follower1 -> follower2 -> etc. any server can choose to terminate the chain.
Is that not sufficient?

it seems like conceptually it only needs to be
leader -> follower1
leader -> follower2
...
that makes addition / replacement of followers easier since only one other node needs to change accounting (though it adds load to the leader, i suppose)

Sure, conceptually it's essentially a frontend gateway (that can coexist with any one of the servers).
So the leader = follower + frontendGateway


Fix signals problem on sentry.io

Defensively get the name
This fixes the problem that Tony reported.

please describe the problem that Tony reported in the PR description


Emacs mode C-c C-x doesn't handle spaces in paths

Steps to reproduce
Create a folder with a space in the name
Create a file test.lean inside that folder
Open Emacs, try out C-c C-x, you'll get a "cannot open file" error, because the space is not quoted.

Is it possible that this fix broke it for me? Any time I try to compile with C-c C-x now, I get an error like this:
-*- mode: compilation; default-directory: "~/projects/lean/hott/types/" -*-
Compilation started at Thu Apr 16 19:10:34

\~/projects/lean/bin/lean -Dpp.width=120  /home/floris/projects/lean/hott/types/square.hlean
/bin/bash: ~/projects/lean/bin/lean: No such file or directory

Compilation exited abnormally with code 127 at Thu Apr 16 19:10:34

@fpvandoorn, possibly. I'll double check it on a Linux machine. Can you confirm that you do have a file at ~/projects/lean/bin/lean?

@fpvandoorn I also had this problem. I'm not sure exactly what fixed it, but the problem was gone after I: deleted the build directory and rebuilt from scratch, and restarted emacs.
@soonhokong I had ~/projects/lean/bin/lean when I experienced the problem.

Hmm... the only change was to use the function shell-quote-argument to escape any special characters in a pathname (i.e. space).
@fpvandoorn, can you exit emacs and reopen it and check whether you can reproduce the problem?

OK. I can reproduce it on my linux machine... I'll investigate it.

@fpvandoorn, please try the latest version.

Wow, that was fixed quickly. Thanks!
I can't check right now whether it works, but I'll try it tomorrow.


Deploy Checklist: New Expensify 2023-10-09

Release Version: 1.3.80-3
Compare Changes: https://github.com/Expensify/App/compare/production...staging
This release contains changes from the following pull requests:

[x] https://github.com/Expensify/App/pull/25543
[x] https://github.com/Expensify/App/pull/26200
[x] https://github.com/Expensify/App/pull/26358
[x] https://github.com/Expensify/App/pull/27385
[x] https://github.com/Expensify/App/pull/27936
[x] https://github.com/Expensify/App/pull/28146
[x] https://github.com/Expensify/App/pull/28175
[x] https://github.com/Expensify/App/pull/28277
[x] https://github.com/Expensify/App/pull/28348
[x] https://github.com/Expensify/App/pull/28357
[x] https://github.com/Expensify/App/pull/28377
[x] https://github.com/Expensify/App/pull/28387
[x] https://github.com/Expensify/App/pull/28397
[x] https://github.com/Expensify/App/pull/28443
[x] https://github.com/Expensify/App/pull/28486
[x] https://github.com/Expensify/App/pull/28511
[x] https://github.com/Expensify/App/pull/28567
[x] https://github.com/Expensify/App/pull/28615
[x] https://github.com/Expensify/App/pull/28628
[x] https://github.com/Expensify/App/pull/28645
[x] https://github.com/Expensify/App/pull/28679
[x] https://github.com/Expensify/App/pull/28728
[x] https://github.com/Expensify/App/pull/28746
[x] https://github.com/Expensify/App/pull/28785
[x] https://github.com/Expensify/App/pull/28796
[x] https://github.com/Expensify/App/pull/28810
[x] https://github.com/Expensify/App/pull/28842
[x] https://github.com/Expensify/App/pull/28850
[x] https://github.com/Expensify/App/pull/28880
[x] https://github.com/Expensify/App/pull/28882
[x] https://github.com/Expensify/App/pull/28903
[x] https://github.com/Expensify/App/pull/28905
[x] https://github.com/Expensify/App/pull/28906
[x] https://github.com/Expensify/App/pull/28918
[x] https://github.com/Expensify/App/pull/28920
[x] https://github.com/Expensify/App/pull/28947
[x] https://github.com/Expensify/App/pull/28948
[x] https://github.com/Expensify/App/pull/28953
[x] https://github.com/Expensify/App/pull/28957
[x] https://github.com/Expensify/App/pull/28972
[x] https://github.com/Expensify/App/pull/28975
[x] https://github.com/Expensify/App/pull/28978
[x] https://github.com/Expensify/App/pull/28980
[x] https://github.com/Expensify/App/pull/28981
[x] https://github.com/Expensify/App/pull/28985
[x] https://github.com/Expensify/App/pull/28987
[x] https://github.com/Expensify/App/pull/28992
[x] https://github.com/Expensify/App/pull/28993
[x] https://github.com/Expensify/App/pull/29185
[x] https://github.com/Expensify/App/pull/29189
[x] https://github.com/Expensify/App/pull/29251

Deploy Blockers:

[x] https://github.com/Expensify/App/issues/29159
[x] https://github.com/Expensify/App/issues/29160
[x] https://github.com/Expensify/App/issues/29162
[x] https://github.com/Expensify/App/issues/29163
[x] https://github.com/Expensify/App/issues/29170
[x] https://github.com/Expensify/App/issues/29172
[x] https://github.com/Expensify/App/issues/29183
[x] https://github.com/Expensify/App/issues/29184
[x] https://github.com/Expensify/App/issues/29186
[x] https://github.com/Expensify/App/issues/29221

Deployer verifications:

[x] I checked the App Timing Dashboard and verified this release does not cause a noticeable performance regression.
[x] I checked Firebase Crashlytics and verified that this release does not introduce any new crashes. More detailed instructions on this verification can be found here.
[x] I checked GitHub Status and verified there is no reported incident with Actions.

cc @Expensify/applauseleads

:rocket: All staging deploys are complete, @Expensify/applauseleads please begin QA on version https://github.com/Expensify/App/releases/tag/1.3.80-0 :rocket:

@jasperhuangg Regression TR is 81% progress. We are still validating couple PRs.
#25543 failing with #29163 (blocker)
Need help with these 2 PRs (not sure if our QA team can validate) https://github.com/Expensify/App/pull/28377#issuecomment-1754046541 and https://github.com/Expensify/App/pull/28920#issuecomment-1754057246

@jasperhuangg Regression TR is just1% left.
#25543 failing with #29163 (blocker)
#28628 failing with #29178
We have open blockers  #29159, #29160, #29162, #29163, #29170, #29172, #29183, #29184 and #29186

@jasperhuangg
Regression is completed.
Open Blockers:
https://github.com/Expensify/App/issues/29159
https://github.com/Expensify/App/issues/29160
https://github.com/Expensify/App/issues/29162
https://github.com/Expensify/App/issues/29163
https://github.com/Expensify/App/issues/29170
https://github.com/Expensify/App/issues/29172
https://github.com/Expensify/App/issues/29183
https://github.com/Expensify/App/issues/29184
https://github.com/Expensify/App/issues/29186
Unchecked PRs:
#25543 failing with #29163 (blocker)
#28628 failing with #29178
Can you pls tag us if there are any CPs needed to re-test

@mvtglobally https://github.com/Expensify/App/pull/29189 CP'd, should fix https://github.com/Expensify/App/issues/29160, please retest, thanks!

https://github.com/Expensify/App/issues/29162 is a known follow-up issue, so checking it off

https://github.com/Expensify/App/issues/29160 was fixed by https://github.com/Expensify/App/pull/29189, checking it off

Checking off https://github.com/Expensify/App/issues/29172 not a blocker

Closed https://github.com/Expensify/App/issues/29184

Closed https://github.com/Expensify/App/issues/29186

Checking off https://github.com/Expensify/App/issues/29221, doesn't need to be a blocker

https://github.com/Expensify/App/issues/29183 is reproducible on prod, checking it off

Checking off https://github.com/Expensify/App/pull/28628 since the failing QA is also reproducible on production

Checking off https://github.com/Expensify/App/issues/29159 CP'd https://github.com/Expensify/App/pull/29251 to fix it

:shipit:


Stop supporting unsupported versions of NodeJS, older than v18.

Question

Judging by https://github.com/nodejs/release#release-schedule, it's safe to use NodeJs no older 18, evrething else is unsupported and potentially dangerous to use. Maybe we shouldn't encourage the use of potentianally dangerous version? After all, the package gains access to authorization tokens and other sensitive data.
I suggest not cheching the performance of the package on NodeJS older that 18 and raising the level of supported NodeJS to version 18. Anyone who wants to put themselves and their users at risk will be able to use previous versions of the package.

Support old versions is not a real problem, you can use any node version that you want. But yep, for future release when we refactor the code we need to drop support for some node versions, because if we use native libs that is part of some node versions, in old versions the library dont works.


Git Clone throws NoSuchMethodError: ‘java.nio.file.Path io.kestra.core.runners.RunContext.tempDir()’

Git clone is broken, not sure whether Git or WorkingDirectory task is the issue?
This is a blocker as it breaks tutorial flows + Git tasks are critical for many deployments of our users
error:
Clone_repository
2024-08-02 12:48:00.439tutorialdwh_and_analyticsclone_repository6k2Fces1qn6i863RudaHlv‘java.nio.file.Path io.kestra.core.runners.RunContext.tempDir()’
Clone_repository
2024-08-02 12:48:00.439[tutorial](http://localhost:28080/ui/flows?namespace=tutorial)dwh_and_analyticsclone_repository6k2Fces1qn6i863RudaHlvjava.lang.NoSuchMethodError: ‘java.nio.file.Path io.kestra.core.runners.RunContext.tempDir()’
 at io.kestra.plugin.git.Clone.run(Clone.java:103)
 at io.kestra.plugin.git.Clone.run(Clone.java:19)
 at io.kestra.core.runners.WorkerTaskThread.doRun(WorkerTaskThread.java:76)
 at io.kestra.core.runners.AbstractWorkerThread.run(AbstractWorkerThread.java:57)

reproducer:
id: dwh_and_analytics
namespace: tutorial
description: Data Warehouse and Analytics

tasks:
  - id: dbt
    type: io.kestra.plugin.core.flow.WorkingDirectory
    tasks:
    - id: clone_repository
      type: io.kestra.plugin.git.Clone
      url: https://github.com/kestra-io/dbt-demo
      branch: main

    - id: dbt_build
      type: io.kestra.plugin.dbt.cli.DbtCLI
      taskRunner:
        type: io.kestra.plugin.scripts.runner.docker.Docker
      containerImage: ghcr.io/kestra-io/dbt-duckdb:latest
      commands:
        - dbt deps
        - dbt build
      profiles: |
        jaffle_shop:
          outputs:
            dev:
              type: duckdb
              path: dbt.duckdb
              extensions:
                - parquet
              fixed_retries: 1
              threads: 16
              timeout_seconds: 300
          target: dev

    - id: python
      type: io.kestra.plugin.scripts.python.Script
      outputFiles:
        - "*.csv"
      taskRunner:
        type: io.kestra.plugin.scripts.runner.docker.Docker
      containerImage: ghcr.io/kestra-io/duckdb:latest
      script: |
        import duckdb
        import pandas as pd

        conn = duckdb.connect(database='dbt.duckdb', read_only=False)

        tables_query = "SELECT table_name FROM information_schema.tables WHERE table_schema = 'main';"
        tables = conn.execute(tables_query).fetchall()

        # Export each table to CSV, excluding tables that start with 'raw' or 'stg'
        for table_name in tables:
            table_name = table_name[0]
            # Skip tables with names starting with 'raw' or 'stg'
            if not table_name.startswith('raw') and not table_name.startswith('stg'):
                query = f"SELECT * FROM {table_name}"
                df = conn.execute(query).fetchdf()
                df.to_csv(f"{table_name}.csv", index=False)

        conn.close()

Seems to be an old version of the plugin in the classpath

@anna-geller  can you try again now that our Docker images has been deployed with new version of plugins?

yup, works!


File Sharing in the iOS App

Please add support for File Sharing to the iOS application. It would be useful when importing an existing key to be able to use iTunes for the file transfer.

theoretically yes, but i'm not sure about this one, because:

to upload the key to your phone, you need itunes
itunes runs on your desktop
so you might just as well set up whiteout on your desktop...

but i see where this is coming from. i'll leave the ticket open to see if there are more people in favor.

I thought about setting up the desktop version, but I also thought the "new user" experience on an iPhone would be useful feedback for you. If there's a better place for feedback let me know.
For a new user looking to import a key the experience is a little weird. Here are my initial thoughts:

I'm not sure why I have the option to enter my name when logging in. Maybe its just because I haven't fully setup the app yet. I'm curious if I have to provide this each login.
The import from file system is not very iOS-like. Most users won't necessarily know what a file system on an iPhone means. Plus, it opens to the camera roll -- I'm not sure how to use that to import a private key.
The format for the copy/paste option is not clear. I'm assuming from reading a few issus here that I need to include both my private key and public key and then the password.
I also had a problem importing my private subkey + public key. There's a separate issue tracking this.

It's great that I can use an existing key; I really like having that option. I'm hoping that experience can be improved, and I think enabling File Sharing support would help accomplish this.
I know that setting up the desktop is an option for getting private keys synced everywhere, but the key sync makes me nervous. I just don't want my private key out on the internet in any form. Plus, I'm worried that people will stop where I did and never finish the setup. I don't think that pausing the mobile experience to setup the desktop version in order to complete the mobile setup is the workflow you're going for.

+1 I had a hard time getting my private key into Whiteout on iOS. Import file does not work and opening the fotos instead is very confusing for the average user.
Honestly, I don't know what a comfortable solution would be. But maybe an instruction would help.

well, a comfy solution would be to either generate a new key, or set it up
on the desktop and sync the key.
On May 20, 2015 11:41, "majnu-campact"<EMAIL_ADDRESS>wrote:

+1 I had a hard time getting my private key into Whiteout on iOS. Import
file does not work and opening the fotos instead is very confusing for the
average user.
Honestly, I don't know what a comfortable solution would be. But maybe an
instruction would help.
—
Reply to this email directly or view it on GitHub
https://github.com/whiteout-io/mail-html5/issues/343#issuecomment-103825957
.

Setting it up on the desktop and syncing it would be fine, but there wasn't a clue about that possibility on the screen. A link to instructions would have saved me quite some time fiddling around with copying the key manually ;)
I did come up with an idea for those (like me) who prefer not to send their private key over the wire: Apps can receice files via iTunes (Dateifreigabe). If Whiteout could offer that option then the users could just drag their keyfile into iTunes. That would be comfy as well.

I don't want a new key. I have to use a new one for now, temporarily, just to use your app. I'm currently unable to import my key even on the desktop. I have a separate ticket issue opened for that.

What I did is I exported my key to a file, renamed the extension to .txt and loaded it via iTunes into an App that can display files, like Filer Lite. I then opened it from there and copied the content into the clipboard and then into Whiteout.

How many UIDs do you have in your key, @majnu-campact ?

@kevin559er: I have one primary key and one sub key. Is that what you meant?


Allow variable api primary key

Closes #1428

Coverage remained the same at 82.987% when pulling 63e6236c5d9d92fc181b72506fa50b57f0edf961 on eatonphil:allow-variable-api-primary-key into bb968f749f48027376e9680989199b3b083ab572 on linode:master.

Closed #1388


Protected code?IT IS IN MY GMAIL NOW.

THE proteced code notif has now shown up in my GMAIL account now

What code? Could you please attach screen shot?


Break apart showcase for dev legibility

The showcase app started sprawl pretty darn hard, this PR breaks it up. If we like we can break it up inside of the examples page so that people dont have to scroll as hard

I also centralized the styling of the buttons in the examples


Enhancement: show the list of commits again when reset mode selection is canceled.

Enhancement: show the list of commits again when reset mode selection is canceled.

Thanks


Random lfs_dir_fetchmatch() failure

In NOR flash ,W25Q512NW the file mount , file write , file close operations are done successfully but at times when We start to execute the code with file system mount it get hits with lfs_dir_fetchmatch () failure. Later only format resolves this.
This lfs_dir_fetchmatch () failure is seen randomly. Could you please help me to understand what might be the the causes of failure and how can we identify that.

This is unfortunately not very much information to go on. On common issue I've seen is misconfigured block devices causing the wrong block to be written or erased during use.
Have you ran tests that verify the block device can read and write various blocks on disk?

lfs_dir_fetchmatch is where the CRCs on the device are verified, so this likely means that the writes are not being stored on disk correctly.
It could also be that there are caches in the block device or block device driver that need to be flushed as a part of the sync callback.

Sorry for the short issue description.
Scenario where Issue  faced:
Case1:
LittleFS  mounted , file open , file write, file close and unmount was done.
Later another code was flashed in XIP mode and debug of that code was done.
Now the board is handed over for LittleFS test run.
This time the mount operation was failing with below error.
corrupted dir pair{0x0,0x1}
bad block at 0x0
super block 0x0 has become unwritable.
Case2:
Binary got written to flash area by mistake and mass erase was done.
After the mass erase operation the litleFS mount was not happening.
The format was done by flashing another littlefs sample code later which the issue resolved.
why was it happening what should we do in order to avoid such 'format' or such 'LFS unable to mount ' scenario.
#define LITTLEFS_START_ADDR 0x400000
#define LITTLEFS_READ_SIZE 16
/* Maximum block program size definition /
#define LITTLEFS_PROG_SIZE 256
/ Erasable block size definition /
#define LITTLEFS_BLOCK_SIZE 4096
/ Minimum block cache size definition /
#define LITTLEFS_CACHE_SIZE 256
/ Minimum lookahead buffer size definition */
#define LITTLEFS_LOOKAHEAD_SIZE 16
.read = lfs_mflash_read,
.prog = lfs_mflash_prog,
.erase = lfs_mflash_erase,
.sync = lfs_mflash_sync,
.read_size = LITTLEFS_READ_SIZE,
.prog_size = LITTLEFS_PROG_SIZE,
.block_size = LITTLEFS_BLOCK_SIZE,
.block_count = 1024,
.block_cycles = 100,
.cache_size = LITTLEFS_CACHE_SIZE,
.lookahead_size = LITTLEFS_LOOKAHEAD_SIZE
#define LITTLEFS_START_ADDR 0x400000 : Does this mean that LittleFS area starts after 4MB. Does it make sense to change the start address to higher value so that to avoid unintended write operation.


RWA-1895 Junit 5 upgrade

JIRA link (if applicable)
https://tools.hmcts.net/jira/browse/RWA-1895
Change description
Does this PR introduce a breaking change? (check one with "x")
[ ] Yes
[ ] No

duplicate


Update to Java 11 as minimum required version

Version 6.0 of HAPI (in prerelease as of the time of this writing) requires Java 11. The cql-translator uses some HAPI APIs to generate data-requirements for CQL files. In order to update to the latest HAPI releases, the cql-translator will need to be updated to 11 as a minimum as well.
https://hapifhir.io/hapi-fhir/docs/introduction/changelog.html#hapi-fhir-600-prerelease
To do the upgrade we need to change gradle build to the correct Java version, ensure the CI pipeline is updated to use the correct version, and gather feedback from the community on the timing of the change from 8 to 11.

See also #582 and #512

I did a quick migration to Java11 and everything seems to work fine.
We should add: targetCompatibility = JavaVersion.VERSION_11 to build.gradle to imply minimum version of Java 11.
Since Java11 removes JAXB, the upgrade requires migrating JAXB commons from 0.12.0 to 1.11.1 and the JAXB runtime dependency below to the xds-to-modelInfo model:

    implementation group: 'org.jvnet.jaxb2_commons', name: 'jaxb2-basics-runtime', version: '1.11.1'

Related to #582 and #512, I also tested migrating to Gradle from 5.6.2 to 7.4.2, which requires us to:

Rework the deprecated maven publishing configuration to use the new plugin
Update a these scopes:

compile to implementation
testCompile to testImplementation
runtime to runtimeOnly


FIX path oauth/token erreur 404 url not found

In API DOC : https://docs.mangopay.com/guide/authentification
POST: https://api.mangopay.com/v2.01/oauth/token/ (change the subdomain to api.sandbox... to use the sandbox environment)
Authorization: Basic czZCaGRSa3F0MzpnWDFmQmF0M2JW
Content-Type: application/x-www-form-urlencoded
Form data: grant_type=client_credentials

Hi @rachedbelhadj
Could you rebase your PR to master, we've made some changes to the testing and release process
Hence this PR won't pass unless it is up to date with current master
thanks


Parallel result stream collector

The ResultCollector currently only supplies single-threaded collectors.

The Java Collector interface does not support terminating the stream early. The only way is to use takeWhile or to make a custom stream implementation (like StreamEx).


Application-specific Defaults

Make it easy to have application-specific defaults for limits such as the maximum length value list.

Changes merged to dev.


Numba support

Allowing parallel computation of huge datasets using numba.

Any progress?

Hi. Sorry to keep you waiting for so long. I haven't gotten a chance to fix the unit tests yet. But I am hoping to get on it this weekend and finalize it.

No worries, take your time :). I prefer a job well done!

Hi @MaxHalford, I was checking the warning messages on travis. Apparently, numba does not support class definitions. Check it out here.    That is why the test cases failed. I will think of some other way to parallelize the operations and let you know if I come up with a solution.

Okay, I didn't know about that but it makes sense. Take your time!

I'm closing this, but feel free to make another pull request if so inclined.


[Feature Request]: Before Extract PDF auto remove password

Feature Description
I want these two functions(remove password, extract pages) to be combined.
Here’s the situation:
When I have a protected PDF (not the password to open the file) and I want to extract a few pages,

I currently need to first remove the password using "Remove Password" and then extract the pages using "Extract Pages."
Why is this feature valuable?
This can let this PDF webpage more connivence.
Suggested Implementation
No response
Additional Information
No response
No Duplicate of the Feature

[X] I have verified that there are no existing features requests similar to my request.

This was added in 0.36.2!
It's already live

This was added in 0.36.2! It's already live

But I'm already 0.36.2, and error occur when I extract pdf.

Can you try test it out in a new browser or something
See if it's a cache issue

Can you try test it out in a new browser or something See if it's a cache issue

Sorry for replying so late.
It still doesn't work in 'extract-page,'(in Private mode, in another PC, browser, Wi-Fi) but I can use this function normally in 'multi-tool.'
I'm happy that I can use it in 'Stirling PDF.'
Thanks for your reply.


Add cashmere wallet to the projects

Context: https://twitter.com/CashmereWallet

Im closing this to keep the list of open PRs managable but feel free to reopen it once youre open source


chore(package): update dependency-check to version 2.8.0

Closes #31
https://greenkeeper.io/

Codecov Report

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

@@          Coverage Diff          @@
##           master    #44   +/-   ##
=====================================
  Coverage     100%   100%
=====================================
  Files           7      7
  Lines          92     92
  Branches        7      7
=====================================
  Hits           92     92

Continue to review full report at Codecov.

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


[Feature Request] Support String[] and hashtable as Metadata name-value pair "value" types

It is very common to have an array of strings as a metadata type such as individual tags, and a hashtable/dictionary of string values such as name-value pair tags.
The hashtable can have the values cast to [string] to avoid object issues, and nested hashtables would not be supported
While both of these can be implemented with string (delimited values for string[] and json for hashtable), they represent a burden to the user to have to do their own data transformation after-the-fact.

Thanks @JustinGrote we do not restrict types for metadata so you could include support for String[] on a individual vault implementation or you can use PowerShell serialization toString as a workaround

@SydneyhSmith Looking at the code it looks like you are correct, let me go back to my implementation and see if it was something on my side.

Further testing and I can't reproduce the issue it seems, I've tried string arrays, pscredential objects, etc. and they all seem to come out fine. Must have been me, apologies!


Mismatch between Datasets path and metadata

There are tens of datasets with metadata different from their path. Dataset's URI is computed from metadata as [channel]/[namespace]/[version]/[short_name]. Path could theoretically determine all these fields in metadata, but we don't enforce it and if users don't set it explicitly there's gonna be a mismatch. This is annoying because lots of our tools depend on dataset URIs (datadiff or compare) and we use either metadata or path assuming they match.
Here are some problematic datasets I found
URI `garden/hmd/2022-12-07/hmd` does not match dataset path `garden/hmd/2022-12-07/life_tables`
URI `garden/homicide/None/homicide_long_run_omm` does not match dataset path `garden/homicide/2023-01-03/homicide_long_run_omm`
URI `garden/irena/2022-10-20/renewable_electricity_capacity_and_generation` does not match dataset path `garden/irena/2022-10-20/renewable_electricity_capacity`
URI `garden/irena/2023-01-04/renewable_electricity_capacity_and_generation` does not match dataset path `garden/irena/2023-01-04/renewable_electricity_capacity`
URI `garden/malnutrion/2022-10-18/malnutrition` does not match dataset path `garden/malnutrition/2022-10-18/malnutrition`
URI `garden/met_office_hadley_centre/2023-01-02/near_surface_temperature_global` does not match dataset path `garden/met_office_hadley_centre/2023-01-02/near_surface_temperature`
URI `garden/owid/2023-01-23/covid19` does not match dataset path `garden/owid/latest/covid`
URI `garden/rff/2022-09-14/emissions_weighted_carbon_price__economy` does not match dataset path `garden/rff/2022-09-14/emissions_weighted_carbon_price`
URI `garden/rff/2022-10-11/emissions_weighted_carbon_price__economy` does not match dataset path `garden/rff/2022-10-11/emissions_weighted_carbon_price`
URI `garden/wpp/2019/standard_projections` does not match dataset path `garden/un/2019/un_wpp`
URI `meadow/andrew/2019-12-03/co2_mitigation_curves_2celsius` does not match dataset path `meadow/andrew/2019-12-03/co2_mitigation_curves`
URI `meadow/aviation_safety_network/2022-10-12/aviation_statistics_by_period` does not match dataset path `meadow/aviation_safety_network/2022-10-12/aviation_statistics`
URI `meadow/gcp/2022-09-29/global_carbon_budget_global` does not match dataset path `meadow/gcp/2022-09-29/global_carbon_budget_additional`
URI `meadow/hmd/2022-12-07/hmd` does not match dataset path `meadow/hmd/2022-12-07/life_tables`
URI `meadow/met_office_hadley_centre/2023-01-02/near_surface_temperature_global` does not match dataset path `meadow/met_office_hadley_centre/2023-01-02/near_surface_temperature`
URI `meadow/papers/2016-04-01/farmer_lafond_2016` does not match dataset path `meadow/papers/2023-01-04/farmer_lafond_2016`
URI `meadow/papers/2009-03-01/nemet_2009` does not match dataset path `meadow/papers/2023-01-04/nemet_2009`
URI `meadow/wpp/2019/standard_projections` does not match dataset path `meadow/un/2019/un_wpp`
URI `grapher/cait/2022-08-10/greenhouse_gas_emissions_by_sector` does not match dataset path `grapher/cait/2022-08-10/all_ghg_emissions`
URI `grapher/cait/2022-08-10/methane_emissions_by_sector` does not match dataset path `grapher/cait/2022-08-10/ch4_emissions`
URI `grapher/cait/2022-08-10/carbon_dioxide_emissions_by_sector` does not match dataset path `grapher/cait/2022-08-10/co2_emissions`
URI `grapher/cait/2022-08-10/nitrous_oxide_emissions_by_sector` does not match dataset path `grapher/cait/2022-08-10/n2o_emissions`
URI `grapher/gcp/2022-09-29/global_carbon_budget_global` does not match dataset path `grapher/gcp/2022-09-29/global_carbon_budget_additional`
URI `grapher/homicide/None/homicide_long_run_omm` does not match dataset path `grapher/homicide/2023-01-03/homicide_long_run_omm`
URI `grapher/malnutrion/2022-10-18/malnutrition` does not match dataset path `grapher/malnutrition/2022-10-18/malnutrition`
URI `grapher/met_office_hadley_centre/2023-01-02/near_surface_temperature_global` does not match dataset path `grapher/met_office_hadley_centre/2023-01-02/near_surface_temperature`
URI `grapher/rff/2022-09-14/emissions_weighted_carbon_price__economy` does not match dataset path `grapher/rff/2022-09-14/emissions_weighted_carbon_price`
URI `grapher/rff/2022-09-14/world_carbon_pricing` does not match dataset path `grapher/rff/2022-09-14/world_carbon_pricing_any_sector`
URI `grapher/rff/2022-10-11/emissions_weighted_carbon_price__economy` does not match dataset path `grapher/rff/2022-10-11/emissions_weighted_carbon_price`
URI `grapher/rff/2022-10-11/world_carbon_pricing` does not match dataset path `grapher/rff/2022-10-11/world_carbon_pricing_any_sector`
URI `explorers/emdat/2022-11-24/natural_disasters` does not match dataset path `explorers/emdat/2022-12-07/natural_disasters`
URI `explorers/owid/2022-05-17/food_explorer` does not match dataset path `explorers/owid/latest/food_explorer`
URI `explorers/un/2022-07-11/un_wpp` does not match dataset path `explorers/un/2022/un_wpp`

The typical step looks like this
ds_garden = Dataset.create_empty(dest_dir, metadata=ds_meadow.metadata)
...
ds_garden.save()

The most common error happens when meadow has a different short name or version and we don't update it with ds_garden.metadata.version = xxx (e.g. we're combining two meadow datasets, one has name renewable_electricity_capacity_and_generation and the output is renewable_electricity_capacity, but we don't change it).
We can set those attributes either in code with ds_garden.metadata.version or in the YAML file.
Here are a couple of ways we could fix this:

Set metadata from dest_dir when creating a dataset with Dataset.create_empty(dest_dir)
Set metadata from dest_dir when saving a dataset with ds_garden.save()
Keep it explicit, but raise an error or at least a warning in ds_garden.save() if they don't match

Dataset is currently a pretty general class that allows saving datasets to any path. We could either be strict and enforce [channel]/[namespace]/[version]/[short_name] structure or be a bit more benevolent and set metadata only when the path matches the structure.
cc @larsyencken @pabloarosado

Good find! I had been aware of this but had forgotten. In some sense it was inevitable since we weren't enforcing it in any way.
I had thought, we can just catch it in CI, but actually you can't see it until you've run every step, so it has to be caught at  run time as in your suggestions.
I think the main question is how much we want to couple owid-catalog to the etl.

If we want to couple them, we would modify Dataset.save() to solve this problem (raise error).

We would probably prefer in time to move them into the same repo as well

If we want them decoupled, we would modify DataStep.run() to do the check immediately after running a step and raise an error there.

Originally I'd been thinking that the could be quite different, and that we might end up writing other scripts that manipulate datasets outside the ETL. 1y+ on and it seems that's not a use case we care about.
I'm now in favour of (3) coupling them more and raising an error in Dataset.save().

Thanks for looking into this @Marigold. I'm thinking of an alternative, which would keep owid-catalog and etl decoupled. We could have a function in etl.helpers, which could be used like, e.g.,
ds_garden = create_dataset(path=dest_dir, tables=[tb_garden], default_metadata=ds_meadow.metadata)

and would:

Create an empty Dataset on dest_dir, loading a "default metadata" (as fallback metadata).
Get channel, namespace, version and short name from dest_dir, and add it to the metadata.
If there is a metadata file adjacent to the step, load it and overwrite existing fields in metadata.

Would any of this make sense? If so, it could reduce significantly the redundant code in the steps.

I'm now in favour of (3) coupling them more and raising an error in Dataset.save(). Basically we'd be saying: you may read from a catalog in any number of places, but it's got to have this particular folder structure behind it.

@larsyencken The annoying thing about having to explicitly set them is that you end up with a boilerplate code like this pretty much everywhere
from etl.helpers import Names

# way to extract metadata from module path
N = Names(__file__)

ds_garden = Dataset.create_empty(dest_dir, metadata=ds_meadow.metadata)
ds_garden.metadata.version = N.version
ds_garden.metadata.short_name = N.short_name
ds_garden.metadata.namespace = N.namespace
ds_garden.save()

You can check out this PR with manual fixes for the problems above. Almost all of it would be unnecessary if we set it implicitly (and we could get rid of much more code).

ds_garden = create_dataset(path=dest_dir, tables=[tb_garden], default_metadata=ds_meadow.metadata)

@pabloarosado This looks very neat, it's nice to have only a single function for everything. The only disadvantage is when your Tables don't fit all in memory and you want to add them one by one with ds_garden.add(table). We could always go low level or pass iterator though, so it's not a real disadvantage.
My idea was to add regex pattern to Dataset that would be extracting metadata from paths. I.e.
@dataclass
class Dataset:
    path: str
    metadata: "DatasetMeta"
    structure: str = r"(?P<channel>\w+)\/(?P<namespace>\w+)\/(?P<version>\w+)\/(?P<short_name>\w+)$"

    def __init__(self, path: Union[str, Path], structure: str = None) -> None:
       ...

    def create_empty(cls, path):
       groups = re.search(path, self.structure)
       meta.namespace = groups.namespace
       ....

If you wanted a general Dataset you would just use empty structure. One advantage is that it would be applied to all existing steps and wouldn't add yet another helper function. I'm not married to this though.


[mesheryctl] (child) mesheryctl system unit testing

See mesheryctl Command Tracker for current status of commands.
check Epic here #3016
Current Behavior
Currently, we don't have any unit tests setup to test mesheryctl system commands and functions
Desired Behavior
Required to enable unit testing support for mesheryctl system commands and functions, to ensure the accuracy and robustness of each mesheryctl release.
mesheryctl Unit Testing

Mark all possible situations for each mesheryctl system commands and functions.
Write tests using Golang’s standard library.
A combination of CodeCov and GitHub Actions are to be used as mainstays in the approach to unit testing - https://github.com/codecov/codecov-action.

Subcommands to cover

[x] mesheryctl system start
[x] mesheryctl system stop
[ ] mesheryctl system channel
[ ] mesheryctl system token
[ ] mesheryctl system logs
[ ] mesheryctl system reset
[ ] mesheryctl system restart
[ ] mesheryctl system status
[ ] mesheryctl system update
[ ] mesheryctl system config

Contributor Resources

mesheryctl Contributing Guide
Beginner's guide to contributing to Meshery and mesheryctl
mesheryctl Command Tracker
Meshery CLI Commands and Documentation
Layer5 Community Slack

This issue can be split-up further for sub-commands under mesheryctl system subcommands and can be picked up by multiple devs for each file/command.

Hey @piyushsingariya can I take unit-test for system reset and restart please ?

Hey @piyushsingariya can I take the system start one?

Yeah sure @chetak123, go ahead!
@sayantan1413 start and stop have been already covered.

@piyushsingariya  You can assign me for system token and system context.

I have raised a PR for mesheryctl system status

@sayantan1413 @chetak123 any updates?

Actually @piyushsingariya can I get some more time in it as my sem. exams are starting and I am little busy right now😅

@piyushsingariya can i take mesheryctl system update

@Shreyas220 update is being handled by @sayantan1413. I think you can give a try to restart maybe.

okay @piyushsingariya
but I think @chetak123 was assigned restart, can I take this from you chetak?

Yeah sure 🙌 , guess I have to only work on system reset then.

Yeah sure 🙌 , guess I have to only work on system reset then.

thank you  😊

@Shreyas220 @chetak123 any update?

Hey @piyushsingariya can you please update which all commands are completed ?

Updated!

Thanks @piyushsingariya 😃

@Shreyas220 @chetak123 any update?

got held up with some things, will make a PR soon

@Shreyas220 @chetak123 any update?

I was caught up with my exams and I am pretty new to golang 😅, will be making a pr soon.


Total assertion count expectations are inaccurate (with async expects)

🐛 Bug Report
expect.hasAssertions() and expect.assertions() incorrectly count assertions as part of a test when they should not be.
To Reproduce
The most basic example I could create to demonstrate
test('hasAssertions should fail expects in promises', () => {
  expect.hasAssertions();
  // Note that the expect below does not "count" as a failed assertion for this
  // test, but hasAssertions() also does not fail as it should!
  Promise.resolve().then(() => expect(true).toBe(false));
});

Expected behavior
The test above should fail, the async assertion should be ignored towards the assertion count. The promise chain, where the expect is executing is not part of the test. We can tell that because the test is not marked as failing even with a blatantly broken assertion. When the expect runs the test is "complete" and should not be counted as part of assertionCount in Jest.
Link to repl or repo (highly encouraged)
I forked the repo and wrote an integration test to demonstrate the problem. Branch
Permalink to the spec itself
https://repl.it/repls/DramaticCuteAssignments
Run npx envinfo --preset jest
❯ npx envinfo --preset jest

  System:
    OS: macOS High Sierra 10.13.6
    CPU: (4) x64 Intel(R) Core(TM) i5-5257U CPU @ 2.70GHz
  Binaries:
    Node: 8.11.1 - ~/.nvm/versions/node/v8.11.1/bin/node
    Yarn: 1.15.0 - /usr/local/bin/yarn
    npm: 5.6.0 - ~/.nvm/versions/node/v8.11.1/bin/npm

Notes
I do realize that the test is bad, it's not very well written. But tests like these do happen IRL and assertion count matchers is what you would want to use to catch them. Currently they do not work for this scenario.
This was pretty interesting and I dug into it a bunch, trying to see if there is an easy fix. But I was unable to locate an obvious mistake. It seems like the assertionCount logic (expect) is separate from the logic marking tests as failures (jest-jasmine2?) so there isn't a simple way to marry the two.

This also has a negative effect on consecutive tests which use things like setTimeout to enqueue assertions in macrotasks. Leading to assertions being "leaked" across tests:
Example:
test.only('assertions after done() callback - 1', done => {
  setTimeout(() => {
    done();
    setTimeout(() => {
      expect(1 + 2).toBe(2);
    });
  });
});

test.only('assertions after done() callback - 2', done => {
  expect.hasAssertions();
  setTimeout(() => {
    done();
  });
});

This test setup leads to these results after tests complete:
 FAIL  src/__tests__/index.js
  ✓ assertions after done() callback - 1 (31ms)
  ✕ assertions after done() callback - 2 (6ms)

  ● assertions after done() callback - 2

    expect(received).toBe(expected) // Object.is equality

    Expected: 2
    Received: 3

      28 |     done();
      29 |     setTimeout(() => {
    > 30 |       expect(1 + 2).toBe(2);
         |                     ^
      31 |     });
      32 |   });
      33 | });

      at Timeout.toBe [as _onTimeout] (src/__tests__/index.js:30:21)

Note that the second spec did not fail due to missing assertions, but instead due to a broken assertion enqueued from spec #1. I get what's going on and I get that it's due to the global nature of the expect library, but this is pretty surprising to see.

Can reproduce this. IIRC at least for jest-circus at least one tick passes after the test until the result is evaluated because of internal awaits.
Not sure if this is easily fixable - you should at least see the unhandled rejection warning though to tell you there's something wrong with your test.
Note that the example from your comment is currently pretty much impossible to detect. I have experimented with using things like zone.js to implement some sort of strict async or debug mode for Jest that could detect this mistake, but nothing really concrete yet.

Ooh, the zone.js library is very cool.
How I stumbled upon this is trying to write a "plugin" for jest which would catch these type of runtime issues. I have incorporated zone.js library into it as a PoC, and it seems to be working rather well. I'm going to throw this at a few thousand tests I have available and report back. Thanks!

I have simillar issue.
My test:
test('should work', () => {
        expect.assertions(1);

        return getCoinInfo()
            .then((coinInfo) => {
                expect(coinInfo.id).toBeGreaterThan(0);
            })
            .catch((error) => {
                logError(error);
            });
    });

It should fail but it doesn't

Running into this as well.

I've just stumbled across this issue due to my own misunderstanding of the behaviour of expect.hasAssertions and expect.assertions()
AFAICT, jest signals expectation failure by throwing, so when I run the initial example in my own code base, it fails, but the following test passes:
test('expect.assertions(2) should pass when caught', () => {
    expect.assertions(2)
    Promise.resolve()
      .then(() => {
        // jest signals expectation failure by thowing, and the intial example has no .catch
        expect(true).toBe(false)
      })
      .catch((e) => {
        expect(true).toBe(true)
      })
  })

(ack. it's highly likely things have changed since the issue was raised)
I'm unclear on why this works at all without returning or awaiting the promise 😄

You can chain as many Promises as you like and call expect at any time, as long as you return a Promise at the end.

https://jestjs.io/docs/tutorial-async (emphasis mine)

Essentially same underlying issue here the solution I suggest in https://github.com/facebook/jest/issues/9881#issuecomment-1050671577 - expect is not bound to a single test, and maintains a global state. So async will confuse it. We need some way of binding an "instance" of expect to a single test, so we can reliably count assertions made in that specific test

@SimenB Thanks for the response and I agree 100% RE: the problem of global expect not being bound to a single test.
It's probably a bit too late in the lifecycle of Jest to expand/change it's API in such a way but I for one would love to see an addition to the test(string, fn) API with something like test.strict that would directly provide the expect Fn as a variable instead of relying on the global. Similar ideas have worked for other test runners (ava comes to mind).
Ex:
test.strict('this test will fail assertions post test completion', (expect) => {
   setTimeout(() => expect(true).toBe(true), 10000);
});

Yeah, I wanna add that type of API. Unfortunate we used the test name as just an alias for it instead of breaking teh API 😅
FWIW I'd me 100% open to a PR adding support for test.strict, test.bound, test.isolated or some such thing which binds/isolates expect. The name isn't the hard part, just need to figure out how to make expect not rely on global state (but still keep it to not break back compat)

@EllaMolnar-FOX
You are correct in that there are ways to write good tests which do not leak assertions. The examples provided in this issue are intentionally stripped down to reproducible example of the behavior. They are not intended as an example of a "good" test that still breaks.
As a side-note, the example above is perfectly valid with just async test functions without the done callback. Async functions return a promise by default (even if they resolve to an undefined value). Jest will wait for these to resolve, so the done is superfluous.

Unfortunately @EllaMolnar-FOX 's fix won't work for me because I'm using TypeScript for my tests.  I can't use both async and done in the same test.
 error TS2345: Argument of type '(done: DoneCallback) => Promise<void>' is not assignable to parameter of type 'ProvidesCallback | undefined'.
      Type '(done: DoneCallback) => Promise<void>' is not assignable to type '(cb: DoneCallback) => void | undefined'.
        Type 'Promise<void>' is not assignable to type 'void'.


[DRAFT] experimental new release process: lerna/npm

It modifies the Lerna configuration to publish independent packages (without nx) using conventional commits.  This will create/update CHANGELOGs and create GitHub Releases for each workspace upon publish.
This is what Appium does, and I believe the goals for our release process are nearly identical.  Please look at the releases/tags in that repo for what you get.
To publish, just run npm run release.  Note that we may want to add a preversion lifecycle script which runs a clean/build.

This removes all yarn config, caches, and lockfiles, and changes all scripts to use npm run instead of yarn.  It means lerna bootstrapis no longer needed, andlernais not needed (but can still be used) to run scripts across workspaces.  There should only be _one_ lockfile: the rootpackage-lock.json`.
Note that this change impacts what would be done in https://github.com/LavaMoat/LavaMoat/issues/625.  Test fixtures, when installed, should no longer create lockfiles.
A note on "resolutions": these become overrides and everything can be done in the monorepo root.

Updated CI config
cc @legobeat

Pinned the dep of keccak in packages/node/test/projects/2 to avoid patch failure, lockfile updates, and ultimately policy file updates.  Don't know if this is desirable.

I'm unsure about the failures here.  Could it be due to transitive deps that have changed?

Current dependencies on/for this PR:

boneskull/npm

PR #626   👈

This comment was auto-generated by Graphite.


Fix link

This seems to fix it.
Fixes https://github.com/eclipse/kuksa.val/issues/757
(The staging fix is not really related, and possibly we should remove boschglobal staging settings later anyway?)

hmm so in the past we had some alternate CI on boschglobal were the website was build for staging and testing. It was a bit ugly but completely removing staging website build is not the solution either. For this PR it is fine if we just merge but bigger ones might pose an issue


Add configuration class and test framework

Fixes #5
Also adds the initial framework for tests, along with good coverage for the config functions.
Adds GitHub workflows.

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@b722da0). Click here to learn what that means.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master       #6   +/-   ##
=========================================
  Coverage          ?   39.58%
=========================================
  Files             ?        6
  Lines             ?      432
  Branches          ?       76
=========================================
  Hits              ?      171
  Misses            ?      251
  Partials          ?       10

Continue to review full report at Codecov.

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


Registrations should require confirmation

Registration should be a two-step process:

The user enters their email address in the Android app. The app calls the backend and either the user is logged in (account existed) or a new account is created and the user is logged in (account did not exist). When a new account is created, it is flagged as unconfirmed. Also, account creation causes a welcome email to be sent.
The welcome email contains a confirmation link that is valid for 24 hours. Unless the user clicks the link within that time, the account expires and is deleted. However, the user can still use the app normally with an unconfirmed account (until it expires). When the user clicks the link, they are shown a web page that tells them their account is now activated. If the page loads successfully, the account is flagged as confirmed.

We'll know if this works at October 15th, 14:40

Seems to be working properly as of #85


feat: Contract classes and instances

WIP to get the CI to run stuff for me

Benchmark results
No metrics with a significant change found.

Detailed results
All benchmarks are run on txs on the Benchmarking contract on the repository. Each tx consists of a batch call  to create_note and increment_balance, which guarantees that each tx has a private call, a nested private call, a public call, and a nested public call, as well as an emitted private note, an unencrypted log, and public storage read and write.
This benchmark source data is available in JSON format on S3 here.
Values are compared against data from master at commit 6dac6504 and shown if the difference exceeds 1%.
L2 block published to L1
Each column represents the number of txs on an L2 block published to L1.

Metric
8 txs
32 txs
128 txs

l1_rollup_calldata_size_in_bytes
45,412
179,524
716,068

l1_rollup_calldata_gas
221,704
866,836
3,446,896

l1_rollup_execution_gas
314,123
984,508
3,666,485

l2_block_processing_time_in_ms
1,424 (+2%)
5,283 (-2%)
20,784

note_successful_decrypting_time_in_ms
290
865 (-2%)
3,161 (-2%)

note_trial_decrypting_time_in_ms
104 (+4%)
92.4 (-17%)
136 (-8%)

l2_block_building_time_in_ms
16,403 (+1%)
64,164
256,566

l2_block_rollup_simulation_time_in_ms
11,992 (+1%)
46,785
187,550

l2_block_public_tx_process_time_in_ms
4,374 (+1%)
17,274
68,723

L2 chain processing
Each column represents the number of blocks on the L2 chain where each block has 16 txs.

Metric
5 blocks
10 blocks

node_history_sync_time_in_ms
15,790 (-8%)
30,383 (-2%)

note_history_successful_decrypting_time_in_ms
1,938 (-4%)
3,838 (-1%)

note_history_trial_decrypting_time_in_ms
118 (-31%)
228 (-3%)

node_database_size_in_bytes
3,588,353 (+2%)
3,624,810 (+2%)

pxe_database_size_in_bytes
29,923
59,478

Circuits stats
Stats on running time and I/O sizes collected for every circuit run across all benchmarks.

Circuit
circuit_simulation_time_in_ms
circuit_input_size_in_bytes
circuit_output_size_in_bytes

private-kernel-init
214
44,681
25,561

private-kernel-ordering
166
43,753
14,809

base-rollup
1,202
128,338
881

root-rollup
79.2
4,088
677

private-kernel-inner
292
71,208
25,561

public-kernel-private-input
205
31,863
25,561

public-kernel-non-first-iteration
203
31,905
25,561

merge-rollup
7.64
2,608
881

Tree insertion stats
The duration to insert a fixed batch of leaves into each tree type.

Metric
1 leaves
2 leaves
8 leaves
16 leaves
32 leaves
128 leaves
64 leaves
512 leaves
1024 leaves
2048 leaves
8192 leaves

batch_insert_into_append_only_tree_16_depth_ms
12.1
17.6 (-13%)
15.4 (+14%)
19.3 (-2%)
25.3
66.0 (+1%)
N/A
N/A
N/A
N/A
N/A

batch_insert_into_append_only_tree_16_depth_hash_count
16.9
17.5
23.0
31.6
47.0
143
N/A
N/A
N/A
N/A
N/A

batch_insert_into_append_only_tree_16_depth_hash_ms
0.625
0.627 (-9%)
0.615 (+13%)
0.543 (-1%)
0.485
0.444 (+1%)
N/A
N/A
N/A
N/A
N/A

batch_insert_into_append_only_tree_32_depth_ms
N/A
N/A
N/A
N/A
N/A
82.9 (-4%)
51.8 (+1%)
252 (-1%)
480 (-1%)
906 (-2%)
3,565

batch_insert_into_append_only_tree_32_depth_hash_count
N/A
N/A
N/A
N/A
N/A
159
96.0
543
1,055
2,079
8,223

batch_insert_into_append_only_tree_32_depth_hash_ms
N/A
N/A
N/A
N/A
N/A
0.475 (-3%)
0.500 (+1%)
0.439 (-2%)
0.439
0.427 (-1%)
0.427

batch_insert_into_indexed_tree_20_depth_ms
N/A
N/A
N/A
N/A
N/A
120 (+1%)
62.0 (-1%)
385 (+3%)
762 (-5%)
1,421 (-4%)
5,610

batch_insert_into_indexed_tree_20_depth_hash_count
N/A
N/A
N/A
N/A
N/A
197
104
691
1,363
2,707
10,771

batch_insert_into_indexed_tree_20_depth_hash_ms
N/A
N/A
N/A
N/A
N/A
0.514 (+1%)
0.504
0.486
0.484 (-4%)
0.474 (-2%)
0.471

batch_insert_into_indexed_tree_40_depth_ms
N/A
N/A
N/A
67.3 (-1%)
N/A
N/A
N/A
N/A
N/A
N/A
N/A

batch_insert_into_indexed_tree_40_depth_hash_count
N/A
N/A
N/A
94.1
N/A
N/A
N/A
N/A
N/A
N/A
N/A

batch_insert_into_indexed_tree_40_depth_hash_ms
N/A
N/A
N/A
0.596 (-1%)
N/A
N/A
N/A
N/A
N/A
N/A
N/A

Miscellaneous
Transaction sizes based on how many contracts are deployed in the tx.

Metric
0 deployed contracts
1 deployed contracts

tx_size_in_bytes
15,455
32,223

Transaction processing duration by data writes.

Metric
0 new commitments
1 new commitments

tx_pxe_processing_time_ms
376 (+1%)
1,085

Metric
1 public data writes

tx_sequencer_processing_time_ms
534


[Feature request] Fixture data classes

The problem:
transaction.php fixture file
<?php

return [
	[
		'id' => 1,
		'currency_id' => 1,
		'type_id' => 2,
		'state_enum' => 'success',
	],
]

What is id 1 in currency field? id2? In project that contains many relations and many tests that hardcored ids make trouble work with fixtures. And heavy troubles when need refactor tests. In refactoring I will replace all sucess strings and remember what means 1 and 2.
Look at this TransactionFixtureData.php
<?php

class TransactionFixtureData extends BaseActiveFixtureData
{
    public function getData()
    {
		$rubCurrency = Currency::findByName(Currency::RUB);
		$refundType = TransactionType::findByName(TransactionType::REFUND);
		$successState = TransactionState::findByName(TransactionState::IS_SUCCESS);

        return [
            [
				'id' => 1,
				'currency_id' => $rubCurrency->id,
				'type_id' => $refundType->id,
				'state_enum' => $successState->name,
            ]
		];
	}
}

Problems:

It's class, not static file
Class makes requests to database (need right depends)
Impossible use templates

Benefit: it's readable.
Yii communities need it?

Feature makes no sense.
The obvious solution for the described usecase will be creating own fixture class, overriding its getData() method. The code will be the same without extra base class involved.
class TransactionFixture extends \yii\test\ActiveFixture
{
    protected function getData()
    {
       //return array;
    }
}


Added command schemaExtension list resolving #12

Added command schemaExtension list resolving #12
Closes #12

Coverage remained the same at 100.0% when pulling 01a87c0471abbb6a06097fa132e1312e37f516e3 on rabwill:issue-12 into b847249a22c3ae32a480a00db4a800503204cd96 on pnp:dev.

Hey folks, my first take on this command. I am waiting for some comments from you after review :) cheers

Thanks @rabwill 👍🏻

Hey guys, I do not currently have time to review this PR. Leaving it open for review to be picked up by someone else.

Hey guys, I do not currently have time to review this PR. Leaving it open for review to be picked up by someone else.

No problem, @appieschot and I will go through it in the next few days

Hey @appieschot I have resolved all comments, was a little hopeless with the commits. soz.
Please let me know if there is something else.

 Nothing that we can't fix though! 🙂
@appieschot, @garrytrinder, @VelinGeorgiev, if you happen to pick up this PR and all is working as expected, please double check that we correctly merge it with master.

I suspected it and did not want to make it worse 😭 so I thought I ll push it in anyway. Thank you, my last resort was to create a fresh branch.

Ill try and carve out some time this weekend to go through it, first step is to check whether all is working properly ;) then getting the correct bits to a commit.

Cheers 🥳 Velin !


[Ready for Review] Backport Adminrouter DNS entry TTL override of 5 seconds to 1.9 OSS

This PR is a backport from 1.10/1.11/master.
It aims to reduce the upper bound of Adminrouter Mesos state cache refresh to 25 + 5 seconds.
Before the TTL was 60 seconds (explicit) for agents and 60 seconds (implicit) for masters.
The resolver used here then caches DNS entries for at most 5 seconds.
Corresponding DC/OS tickets (obligatory)

DCOS-2388 Adminrouter DNS entry TTL override of 5 seconds OSS.

Checklist for all PRs

[x] Read the DC/OS contributing guidelines

@mesosphere-mergebot label  ready for review

@orsenthil I tried to make teamcity/dcos/test/upgrade-from-previous-major pass 5 times already, I think that test is broken. Could you assist me in debugging this please?

Hey @timaa2k  - Sorry for that!. Looking into this one.  Marathon returning Waiting for Marathon, resp code is: 502 is  new (The 502 was new, we had seen 500 earlier).
The last success on the branch was around 6 days ago - https://teamcity.mesosphere.io/viewLog.html?buildId=1036984&tab=buildResultsDiv&buildTypeId=DcOs_Open_Test_UpgradeTest_FromStableMajorVersion
But the base branch of 1.9 itself is hitting this issue now, which means, the problem is unrelated to your PR.
https://teamcity.mesosphere.io/viewLog.html?buildId=1044976&buildTypeId=DcOs_Open_Test_UpgradeTest_FromStableMajorVersion&tab=buildLog

Could you override that test?

@orsenthil  Are we ok with overriding failing CI (teamcity/dcos/test/upgrade-from-previous-major)?

@mesosphere-mergebot bump-ee

@mesosphere-mergebot bump-ee

@mesosphere-mergebot bump-ee

@mesosphere-mergebot bump-ee

@mentioning senthil we have a problem with mergebot here, as you can see Pawel issued a bump several times that went unanswered.

@timaa2k  - That was interesting. See above.

Mergebot has not been updated/deployed since 3 weeks. So nothing changed.
I looked at the logs for the recent events and didn't find anything suspicious.
Checked github to see if it was given correct information

$ git rev-parse dcos/pull/2772
3b2f7724fe12c295901230a19895d2df44bffc8c

It did, and then I tried bump-ee again, to see if this fails, I can look at the logs. But instead, it was succesful.

The rev-parse trick from the pr branch of github is good one to see if github is giving correct information and that could help save some surprises.

@mesosphere-mergebot override-status teamcity/dcos/test/upgrade-from-previous-major https://jira.mesosphere.com/browse/DCOS_OSS-2394

@vespian  - Could you please approve this again. After the last change https://github.com/dcos/dcos/pull/2772/commits/3b2f7724fe12c295901230a19895d2df44bffc8c it has only one approval.


Apostrophe characters in the search query will lead to an error 500

Description
Whenever the user searches for any content that has an apostrophe in its name, Jellyseerr will output an error code 500.
Version
1.6.0
Steps to Reproduce

Open Jellyseer web ui
Type any string character containing an apostrophe (') Alt+0027
Observe

Screenshots
No response
Logs
That error does not show up in logs

Platform
desktop
Device
Any
Operating System
Debian Bookworm
Browser
Chrome
Additional Context
No response
Code of Conduct

[X] I agree to follow Overseerr's Code of Conduct

Did you say you're on 1.6.0? Latest version is 1.7.0

Can you try development branch? Because thats what I'm on. I think thats why

Still the same issue unfortunately. This is very weird because backtick, backslashes, quotes in the search query don't generate any error.

Still the same issue unfortunately. This is very weird because backtick, backslashes, quotes in the search query don't generate any error; where semicolon, exclamation mark do.

I'm on development branch. I have just tested it on several devices even after installing new on test devices. It works. So probably your instance is having issues with tmdb or sth can you share logs?

Here's the redacted log
overseerr-2023-11-08-redacted.log

Nothing out of the ordinary. How did you install jellyseerr?
Can you provide me the chrome devtools console log when the error occurs and also in network tab look for an error.
And if docker is it possible to whip up a new fresh test container with the tag :develop with the block
dns:
    - <IP_ADDRESS>
    - <IP_ADDRESS>

added.
See if you face the same issue on that new container.  I am also running it like that on the latest commit.

I was indeed a few commits behind but still no luck :(

Could you try git cloning to another directory and yarn install and build and start so it's a fresh instance just to see if that works? I'm still unable to reproduce this at all

Node version was the culprit :|
I had 20.x installed, downgraded it to 18 instead and the issue is now gone. Thanks for the support!


Revise throughout to be compatible with Predictive

So far, when we have wanted to track a "generated quantity" (a quantity which is not sampled directly, but is depends on quantities that are sampled), we have littered numpyro.Deterministic throughout the model code. This can be confusing because the name supplied in numpyro.Deterministic may not correspond to the variable with that name in other parts of the code. E.g. there may be a numpyro site called Rt but later in the model the variable Rt is padded. This padded Rt will not be present in the posterior samples, even though it would be easier to use in post processing than the unpadded Rt.
Perhapes @dylanhmorris can fill us in if there is a more "correct" way to achieve this, but I propose adding a generated_quantities flag to the model arguments, collecting all of the numpyro.Deterministic random variables at the end of the model, and only calling numpyro.Deterministic if generated_quantities = True.
Ex:
import numpy as np
import jax.numpy as jnp
import jax
import numpyro
import numpyro.distributions as dist
from numpyro.infer import MCMC, NUTS, Predictive
import matplotlib.pyplot as plt

# Define the model
def linear_regression(X, y=None, gq=False):
    # Priors for unknown parameters
    alpha = numpyro.sample('alpha', dist.Normal(0, 10))
    beta = numpyro.sample('beta', dist.Normal(0, 10))
    sigma = numpyro.sample('sigma', dist.Exponential(1))

    # Linear model
    mean = alpha + beta * X

    # Likelihood (sampling distribution) of observations
    with numpyro.plate('data', X.shape[0]):
        obs = numpyro.sample('obs', dist.Normal(mean, sigma), obs=y)
    if gq:
        numpyro.deterministic('mean', mean)
    return mean

# Generate synthetic data
np.random.seed(0)
N = 100
X = np.random.randn(N)
y = 1.0 + 2.0 * X + np.random.normal(0, 1.0, size=N)

# Define the MCMC model
nuts_kernel = NUTS(linear_regression)
mcmc = MCMC(nuts_kernel, num_warmup=500, num_samples=1000)
mcmc.run(jax.random.PRNGKey(0), X, y)
posterior_samples = mcmc.get_samples()
posterior_samples.keys()
# Posterior predictive sampling
predictions = predictive(jax.random.PRNGKey(1), X, gq=True)

This ensures that the MCMC objects remain lean and useful for diagnostics, while allowing us to produce generated_quantites in a centralized location.

Actually, after playing around with NumPyro for a while, I'm not sure this is possible. This is how things work in Turing, so I would hope there is similar functionality in NumPyro.

After discussion with @dylanhmorris, we think it would be better for now to continue tracking deterministic random variables as we do now.


Build Fails

I tried to install via cargo install below the build failed :(
The same failure is reproduced when we try to checkout the code and build again.
Error:
mfrw@u18 ~/r/below (master)> cargo build --release
warning: /home/mfrw/rutils/below/below/store/Cargo.toml: version requirement `=0.8.0+zstd.1.4.9` for dependency `zstd` includes semver metadata which will be ignored, removing the metadata is recommended to avoid confusion
   Compiling below_derive v0.2.0 (/home/mfrw/rutils/below/below/below_derive)
   Compiling fb_procfs v0.2.0 (/home/mfrw/rutils/below/below/procfs)
   Compiling cgroupfs v0.2.0 (/home/mfrw/rutils/below/below/cgroupfs)
   Compiling below-common v0.2.0 (/home/mfrw/rutils/below/below/common)
   Compiling below v0.2.0 (/home/mfrw/rutils/below/below)
error: failed to run custom build command for `below v0.2.0 (/home/mfrw/rutils/below/below)`

Caused by:
  process didn't exit successfully: `/home/mfrw/rutils/below/target/release/build/below-47df527852d71c27/build-script-build` (exit status: 101)
  --- stderr
  thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: Build("No such file or directory (os error 2)")', below/build.rs:19:47
  note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
warning: build failed, waiting for other jobs to finish...
error: build failed

Am I missing anything trivial ?

I think you're missing clang. I've improved the error message in libbpf-rs ( https://github.com/libbpf/libbpf-rs/commit/e072eb9117d47e96b1a4810f4df6d802d7197a01 ) but I didn't tag the release yet

I think you're missing clang. I've improved the error message in libbpf-rs ( libbpf/libbpf-rs@e072eb9 ) but I didn't tag the release yet

Thank you very much :)


Cow: Watch petir.io

Cow requests the watch of the watch_keyword petir\.io. See the MS search here and the Stack Exchange search in text, in URLs, and in code.

petir\.io has been seen in 1 true positive, 0 false positives, and 0 NAAs.

Approved by VLAZ in Charcoal HQ


Sandcastle/Gist interop

Please close if this is a duplicate.
A while back, @shunter mentioned the idea of being able to save a Sandcastle example as a giant url.  Sounds cool.  Taking it to the next level, it is possible to do nice interop with GitHub gists so Sandcastle examples could be backed by a gist?

Added in #3795.


Checkin Fails with 'The service endpoint [ProjectCollectionName] was not found'

As of 9/5/2018, the Checkin task started to fail on me with an error stating that "The service endpoint EAS was not found" (note that EAS is the name of my Team Collection and also the root folder of the VSTSVC tree attached to the build).  These builds worked fine last Friday, but were not used on Monday (holiday) or Tuesday (VSTS outage).  I have attached the build log output to this issue - note that the failed checkin happens in step 10.  I am happy to provide any additional information that would be helpful - please let me know.
logs_14123.zip
Thanks!
Sean

My test builds are succeeding and are returning no issues. I haven't recently pushed a new version.
Can you run a build with the following variables set:
system.debug = true
agent.diagnostic = true

Things that come to mind that may have caused this:

Did the agent auto-update?
Have you tried restarting the agent?

Thanks for such a quick reply!
I did try restarting the agent services, but it didn't help.  I'm not positive on how to go about checking if the agent auto-updated, but I don't think so - I am using a service running out of bin.2.138.4 folder (which is dated 8/13/18), so that upgrade should have happened a couple of weeks ago.
I ran another build with the build variable above, and it looks like the failure is happening somewhere in  Get-SourceProvider - I've attached the full log below.
Let me know if there's anything else I can try
logs_with_debug_enabled.zip

I don't see anything that stands out. Could you run a smbatch script task
that outputs cmd /c set
On Thu, 6 Sep 2018, 01:05 seanmobrien<EMAIL_ADDRESS>wrote:

As of 9/5/2018, the Checkin task started to fail on me with an error
stating that "The service endpoint EAS was not found" (note that EAS is the
name of my Team Collection and also the root folder of the VSTSVC tree
attached to the build). These builds worked fine last Friday, but were not
used on Monday (holiday) r Tuesday (VSTS outage). I have attached the build
log output to this issue - note that the failed checkin happens in step 10.
I am happy to provide any additional information that would be helpful -
please let me know.
logs_14123.zip
https://github.com/jessehouwing/vsts-tfvc-tasks/files/2354829/logs_14123.zip
Thanks!
Sean
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/jessehouwing/vsts-tfvc-tasks/issues/68, or mute the
thread
https://github.com/notifications/unsubscribe-auth/AD-uS87jTgDv-n8reZsc_EptissHVA-Qks5uYFjDgaJpZM4Wb1bO
.

Sure thing - I have a meeting I need to run to but will do it right when I get back.  One thing that I did notice is it appears from the output that the error could be occurring around line 107 of vsts-tfvc-shared.psm1 -
  $serviceEndpoint = Get-ServiceEndpoint -Context $distributedTaskContext -Name $env:BUILD_REPOSITORY_NAME
However, if I retrieve
GET https://xxxxxx.visualstudio.com/EAS/_apis/serviceendpoint/endpoints?api-version=4.1-preview.1&endpointNames=EAS
I receive
{"count":0,"value":[]}.
Here is what I get back for a full list of service endpoints:
{"count":2,"value":[{"data":{},"id":"f578d64a-40d3-4b20-befe-815c56a97e0c","name":"WebTeam Nuget Feed","type":"externalnugetfeed","url":"http://nuget.xxxxx.org/nuget/WebTeam/","createdBy":{"displayName":"Xxxx Xxxxx","id":"2ddf8d7e-8c94-4cd7-8c16-280a6f1cab66","uniqueName":"xxxxx@xxxx.ORG"},"authorization":{"scheme":"None"},"isReady":true},{"data":{},"id":"e20292f0-d1d5-4c40-aace-3a739125630f","name":"Veracode (xxxxxx@xxxx.org)","type":"VeracodeAnalysisCenterEndpoint","url":"https://analysiscenter.veracode.com/","createdBy":{"displayName":"Xxxx Xxxxxxxx","id":"c02b39d5-b378-4eb1-b33b-b150575f6359","uniqueName":"xxxxxx@xxxx.ORG"},"authorization":{"scheme":"Token"},"isReady":true}]}
Is it possible I've lost some endpoint setup somewhere along the way?  I don't see any similar endpoints configured in other projects, but that doesn't mean I just don't know where to look.

The task is requesting the System Endpoint directly from the server. These
are predefined endpoints. They should just "be there".
On Thu, Sep 6, 2018 at 8:27 PM seanmobrien<EMAIL_ADDRESS>wrote:

Sure thing - I have a meeting I need to run to but will do it right when I
get back. One thing that I did notice is it appears from the output that
the error could be occurring around line 107 of vsts-tfvc-shared.psm1 -
$serviceEndpoint = Get-ServiceEndpoint -Context $distributedTaskContext
-Name $env:BUILD_REPOSITORY_NAME
However, if I retrieve
GET
https://xxxxxx.visualstudio.com/EAS/_apis/serviceendpoint/endpoints?api-version=4.1-preview.1&endpointNames=EAS
I receive
{"count":0,"value":[]}.
Here is what I get back for a full list of service endpoints:
{"count":2,"value":[{"data":{},"id":"f578d64a-40d3-4b20-befe-815c56a97e0c","name":"WebTeam
Nuget Feed","type":"externalnugetfeed","url":"
http://nuget.xxxxx.org/nuget/WebTeam/","createdBy":{"displayName":"Xxxx
Xxxxx","id":"2ddf8d7e-8c94-4cd7-8c16-280a6f1cab66","uniqueName":"xxxxx@xxxx.ORG"},"authorization":{"scheme":"None"},"isReady":true},{"data":{},"id":"e20292f0-d1d5-4c40-aace-3a739125630f","name":"Veracode
(xxxxxx@xxxx.org)","type":"VeracodeAnalysisCenterEndpoint","url":"
https://analysiscenter.veracode.com/","createdBy":{"displayName":"Xxxx
<EMAIL_ADDRESS>"},"authorization":{"scheme":"Token"},"isReady":true}]}
Is it possible I've lost some endpoint setup somewhere along the way? I
don't see any similar endpoints configured in other projects, but that
doesn't mean I just don't know where to look.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/jessehouwing/vsts-tfvc-tasks/issues/68#issuecomment-419195333,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AD-uS5KHwQ1h8330mQTp9dJ9TfvS6EfRks5uYWj_gaJpZM4Wb1bO
.

Hi there! I just wanted to chime in that we've been seeing the same thing on our builds since the VSTS outage on Tues (04Sep). To clarify our last build that went through was Tues morning (0224 E/T). As Sean said, according to the logs it's not finding the endpoint which is the team project path. I ran the build using the 2 debugs mentioned. The agent_diag log shows that endpoint (aka server path) is correct & found. In fact the GetSources task would fail if the endpoint wasn't found. Is there a way to verify the method the task uses to grab the endpoint hasn't been broken by the fix that was implemented to get the VSTS servers back up on Tues night?

I ran a test on the hosted pools and my local agent without issues.
A rewrite using the new api has been in the books for a long time, but I
haven't had the time to do that.
Can you check whether the build has a collection scope or project scope
security token?
On Sat, 8 Sep 2018, 00:44 grizz0blaw<EMAIL_ADDRESS>wrote:

Hi there! I just wanted to chime in that we've been seeing the same thing
on our builds since the VSTS outage on Tues (04Sep). To clarify our last
build that went through was Tues morning (0224 E/T). As Sean said,
according to the logs it's not finding the endpoint which is the team
project path. I ran the build using the 2 debugs mentioned. The agent_diag
log shows that endpoint (aka server path) is correct & found. In fact the
GetSources task would fail if the endpoint wasn't found. Is there a way to
verify the method the task uses to grab the endpoint hasn't been broken by
the fix that was implemented to get the VSTS servers back up on Tues night?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/jessehouwing/vsts-tfvc-tasks/issues/68#issuecomment-419585601,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AD-uSyzhCbRlRh21c4UI3PWSCDHrzDw7ks5uYvbUgaJpZM4Wb1bO
.

I won't be able to get in touch with the people who have access to that information until Monday, but I will check and let you know.   Thanks again!
Get Outlook for Androidhttps://aka.ms/ghei36

From: Jesse Houwing<EMAIL_ADDRESS>Sent: Saturday, September 8, 2018 12:54:28 AM
To: jessehouwing/vsts-tfvc-tasks
Cc: seanmobrien; Author
Subject: Re: [jessehouwing/vsts-tfvc-tasks] Checkin Fails with 'The service endpoint [ProjectCollectionName] was not found' (#68)
I ran a test on the hosted pools and my local agent without issues.
A rewrite using the new api has been in the books for a long time, but I
haven't had the time to do that.
Can you check whether the build has a collection scope or project scope
security token?
On Sat, 8 Sep 2018, 00:44 grizz0blaw<EMAIL_ADDRESS>wrote:

Hi there! I just wanted to chime in that we've been seeing the same thing
on our builds since the VSTS outage on Tues (04Sep). To clarify our last
build that went through was Tues morning (0224 E/T). As Sean said,
according to the logs it's not finding the endpoint which is the team
project path. I ran the build using the 2 debugs mentioned. The agent_diag
log shows that endpoint (aka server path) is correct & found. In fact the
GetSources task would fail if the endpoint wasn't found. Is there a way to
verify the method the task uses to grab the endpoint hasn't been broken by
the fix that was implemented to get the VSTS servers back up on Tues night?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/jessehouwing/vsts-tfvc-tasks/issues/68#issuecomment-419585601,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AD-uSyzhCbRlRh21c4UI3PWSCDHrzDw7ks5uYvbUgaJpZM4Wb1bO
.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/jessehouwing/vsts-tfvc-tasks/issues/68#issuecomment-419615849, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AIVsAw54MGrPhhwyHz9Bnno7Ps-9znrOks5uY1uUgaJpZM4Wb1bO.

Can you guys force an agent update to get to 2.140?
From the folks that build the agent:

make sure they are on latest version agent. there was a bug in the agent cause the legacy endpoint not populate correctly.

—

Same Problem here. Updating our build agent to 2.140 fixed the issue.

Looks like that was my problem as well - thanks again for all your help getting this figured out!

I can also confirm that everything is back up & running. Thank you Jesse!


Fixing the Alignment of Image in this page.

I am Praful Nigam. Under GSSOC'24, I would like to work on this issue. Pls assign me this!!

@prafulnigam  i think this is a background effect not a mistake plzz confirm @ashutoshgithubs so that we can consider  this as a mistake or a effect

@ashutoshgithubs : I believe this isn't looking really good. Even if it is a effect. It needs to be worked on.

@prafulnigam how do you want to make it better. I have created a grid in the background and shifted its alignment. But if you can make it even more better, work on.  If your work will appear more appealing, your PR will be confirmed. Are you ready?

Thanks ! On it.

Hello @ashutoshgithubs
I would like to fix or change the position of the image and add some hover effect on the image so that it looks more beautiful
So can you please assign this issue to me


formatter:format changes in database module

No issue.
Changes to make the linter happy. It looks like the latest security patch made it through CI without linting?
@wetneb any idea how that happened?

@wetneb I automerged this since it was trivial and it'll allow me to rebase my other PR on a clean master branch, but I'm still curious how this slipped through. Something about the setup of our temporary security repos?

Yes indeed the CI does not run on security repos, so I should have thought about running linting on my side… sorry about that and thanks for taking care of it!


Possible extension: ignore accents

Request to extend the current project to not only ignore cases, but also accents in the text. Especially useful when learning stressed languagedssuch as slavic languaes.
Text of the field with which needs to be compared can be easily modified by the following snippet:
	 ru_raw = ru_stress.normalize("NFD").replace(/[\u0300-\u036f]/g, '');
EDIT: if not interesting to the general public that uses this add on, I will fork and adapt accordingly myself (when permitted).

Good idea! I might add this as an optional feature since accents in some languages are important to learn as well.
You can always fork the project and modify it to your liking. No problem.

This would be helpful!

After nearly 2 years, I have finally got around to updating the addon to include this (as well as the option to ignore punctuations).
If you're still interested, you can test use the updated version, or you can keep using your own forked version if you want 😉.


Typos corrected in workflow description

Description
Small typos corrected in variable name and step name.
Related issue(s)

/retest


Allow to share indexheader.ReaderPool metrics

[ ] I added CHANGELOG entry for this change.
[x] Change is not relevant to the end user.

Changes
I'm working on some improvements to reduce the Cortex store-gateway memory allocations on clusters with large number of tenants.
Long story short, we have a known issue caused by metrics collection (https://github.com/cortexproject/cortex/issues/3697) and, as a first step, I would like to be able to share the metrics passed to indexheader.ReaderPool.
Verification
Existing tests.

Thanks Ben! ❤


request like post and like comment post, also comment

Is your feature request related to a problem? Please describe.
like post and like comment post, also comment

Hello @yekayee !
I don't understand your issue. Can you be more specific, please?

i mean request fiture like post like commentar and comment on post

I'm sorry but t you need to give more context to the issue.

Im closing this issue since it was not a cleary question


Replace log2(n) by local functions

This also adds support for environments without a log2 function (Android).
Signed-off-by: Stefan Weil<EMAIL_ADDRESS>

The implementation in lstm/lstm.cpp is much faster according to results of a small test program which calls it for all unsigned values: 37 s (old algorithm with log2), 39 s (non gnu code), 0.7 s (gnu code). I expect that the non gnu code is faster for typical integer values which require less loop iterations.

What happened to the AppVeyor CI build? It does not look related to my modifications.

Windows/cppan build is broken (actually not tesseract directly but dependency: error C2065: 'FRIBIDI_TYPE_PDF_LRI': undeclared identifier ).
@egorpugin : can you fix it?

For MSVC you can use:
_BitScanReverse
https://msdn.microsoft.com/en-us/library/fbxyd7zd.aspx
OR
__lzcnt
https://msdn.microsoft.com/en-us/library/bb384809.aspx

@egorpugin : can you fix it?

I'm debugging. Looks like bad codegen from MSVC.

Build is fixed, but 64 has compiler issue.
https://developercommunity.visualstudio.com/content/problem/206985/clexec-bad-codegen-on-x64.html

@stweil, did you see my comment?

Yes, I did, but needed to find time for coding and test. See PR #1369. It reduces the time for MS C code from 39 s to 0.7 s (same value as for gcc).


[bazel] FusoSoC sometimes appears to corrupt the cache and requires a bazel clean to get unstuck

It looks like this sequence may reveal the symptoms:

Build verilator with a commit where usbuart still existed
Check out a commit after that horizon, and try to build again

bazel-out/ will still show many references to the usbuart IP, but the repo source has none.

It would be interesting to know if the error could be reproduced by invoking fusesoc manually while moving across the usbuart deletion horizon.
Unfortunately, the bazel fusesoc_build rule is not hermetic and, IMHO, isn't as strict about its deps as it ought to be, but for the time being, I don't think that problem is worth solving in bazel.

@cfrantz @a-will @timothytrippel anything left to do here?

Likely fixed by #19466, which causes fusesoc builds to happen in a sandbox.

I'll close it, since I'm not aware of any remaining issues. Please re-open (or open a new issue) if this comes up again.