feat(rbac): allow editing permission policies

Resolves:
https://github.com/janus-idp/backstage-plugins/issues/993
GIF:
https://github.com/janus-idp/backstage-plugins/assets/22490998/8c1d2a53-ded6-455c-b7aa-4fdaea3431e4
https://github.com/janus-idp/backstage-plugins/assets/22490998/6c3bfe18-7693-4d4a-8e41-2eeb2f7316a4

https://github.com/janus-idp/backstage-plugins/assets/20724543/3e1c8b1a-a1e8-4954-bfbd-72036c3f8af6

@debsmita1 as you can see in above rec/image that before the permissions are loaded the component is being rendered and hence it shows an error. IMO when the permissions are loading lets show a progress component and if there is any error once after the loading is completed then show the error.
Also on clicking cancel IMO the user should be redirected to the previous page it came from. For ex in above case on clicking cancel it should navigate back to role overview page.
cc: @parvathyvr

@debsmita1 I am also seeing an issue wherein sometimes the navigation is not working properly. For ex I saw an issue when clicked on save button on edit role form and it navigated to rbac page but the list was not rendered. This doesnt happen always.

Screen.Recording.2024-01-05.at.3.37.38.PM.mov

@debsmita1 as you can see in above rec/image that before the permissions are loaded the error component is being rendered since the permissions are undefined and the above error is shown. IMO when the permissions are loading lets show a progress component and if there is any error/permissions are undefined once after the loading is completed then show the error.
Also on clicking cancel IMO the user should be redirected to the previous page it came from. For ex in above case on clicking cancel it should navigate back to role overview page.
cc: @parvathyvr

Done. PTAL
https://github.com/janus-idp/backstage-plugins/assets/22490998/fd74c844-1463-4a76-8935-6cc2837a34ec

@debsmita1 I am also seeing an issue wherein sometimes the navigation is not working properly. For ex I saw an issue when clicked on save button on edit role form and it navigated to rbac page but the list was not rendered and after some time is gets rendered. This doesnt happen always.

Couldn't reproduce this. If you see this again could you record the network logs ?

@debsmita1 I am also seeing an issue wherein sometimes the navigation is not working properly. For ex I saw an issue when clicked on save button on edit role form and it navigated to rbac page but the list was not rendered and after some time is gets rendered. This doesnt happen always.

Couldn't reproduce this. If you see this again could you record the network logs ?

@debsmita1 the issues seems to be with rendering the whole page. If the data is not available then the table should be shown with empty state but here the entire page is not rendering. I will check the network logs but in case of data failure also the whole page UI should not break. I will keep an eye on this issue.

@debsmita1 On going to the edit form with active step as Edit permission policies I dont see a error now but I dont see a progress bar either. When the policies are loading nothing is displayed and then suddenly the table is shown.
https://github.com/janus-idp/backstage-plugins/assets/20724543/29738a11-6d4e-495c-91bf-feb3f5b0ecd2

@debsmita1 On adding a policy row and adding values to the fields a warning saying MUI: The value provided to Autocomplete is invalid is being shown. Please fix it.
https://github.com/janus-idp/backstage-plugins/assets/20724543/594979d0-6393-4cf3-bd61-4c7e7cd0634d

@debsmita1 On adding a policy row and adding values to the fields a warning saying MUI: The value provided to Autocomplete is invalid is being shown. Please fix it.
Screen.Recording.2024-01-09.at.11.56.04.AM.mov

Fixed it

@debsmita1 The PR looks good and works as expected but I see two minor issues:
https://github.com/janus-idp/backstage-plugins/assets/20724543/ce3604f5-615a-44cd-8271-7078eccb6d3e

Now I see a warning for members dropdown
On adding new policy row, permission and plugin dropdown's bg color is changed to blue

@debsmita1 The PR looks good and works as expected but I see two minor issues:
Screen.Recording.2024-01-10.at.3.08.11.PM.mov

Now I see a warning for members dropdown
On adding new policy row, permission and plugin dropdown's bg color is changed to blue

@divyanshiGupta  I couldn't find a warning for the members dropdown, but there appears to be an issue with the autocomplete components. The solution mentioned in the warning doesn't seem to be working. I found an open issue on github https://github.com/mui/material-ui/issues/29727. However, I did fix the background color of the plugin dropdown


New API Proposal from Chenosis : IMEI Fraud Check API

GSMA Drop 2
This API enables the API Consumer to determine whether fraud has been reported for the connected device. It will use the MSISDN or/ IMEI to check if the associated device has been reported as lost, suspended, stolen, blacklisted.
Use case – account takeover, online registration

This is Chunghwa Telecom. We would like to express our support for this API.


Added new line in generate menu

Hello,
I added this for a better visibility

Thank you for the contribution @BenjaminBorlet!  Two things

You put your \n in single quotes.  Did you commit the wrong file?

I'm not sure that putting things on multiple lines improves the readability for me, and I'm not sure I'd want this to be the default option. (since it seems like a hard things to get right for everyone)

I'd be open to adding a formatting option flag -- something like --list-format that would let a user chose different ways to have those lists displayed -- maybe with a configuration file in ~/.pestle to allows users to pick a format.

Hello,
First of all it was my first contribution on github, so sorry if I had a bad approach ^^
I had this idea because when you have like 10 choice, it's really hard to read it in first place.
(yes i wanted to commit double quote sorry again)
But I understand some people could prefer this view, so i'm totally okay with some flag or config file, but I think it's a bit over my competence for now ^^


Compilation error when building examples

In file included from CustomMatPlot/source/cmp_trace.cpp:8:
CustomMatPlot/include/include_internal/cmp_trace.h: In member function ‘constexpr bool cmp::TracePoint<ValueType>::operator<=>(const cmp::TracePoint<ValueType>&)’:
CustomMatPlot/include/include_internal/cmp_trace.h:43:32: error: no match for ‘operator<=>’ (operand types are ‘juce::Point<int>’ and ‘juce::Point<int>’)
   43 |     return this->getPosition() <=> rhs.getPosition();
      |            ~~~~~~~~~~~~~~~~~~~ ^~~ ~~~~~~~~~~~~~~~~~
      |                             |                     |
      |                             Point<[...]>          Point<[...]>

and
CustomMatPlot/source/cmp_lookandfeel.cpp: In function ‘constexpr std::pair<float, float> getFirstEndFromPreviousTicks(const std::vector<float>&, cmp::Lim_f)’:
CustomMatPlot/source/cmp_lookandfeel.cpp:48:35: error: call to non-‘constexpr’ function ‘std::vector<_Tp, _Alloc>::const_iterator std::vector<_Tp, _Alloc>::begin() const [with _Tp = float; _Alloc = std::allocator<float>; std::vector<_Tp, _Alloc>::const_iterator = std::vector<float>::const_iterator]’
   48 |     auto it = previous_ticks.begin();
      |               ~~~~~~~~~~~~~~~~~~~~^~

my environment

Ubuntu 22.04 (WSL)
g++ (Ubuntu 11.2.0-19ubuntu1) 11.2.0
$ git submodule - 98c19f752fcdf9c2dc80ba2deb227f4ce26a5c70 ../externals/JUCE (5.4.5-659-g98c19f752)

After minor changes, got the compilation working though.
diff --git a/include/include/cmp_datamodels.h b/include/include/cmp_datamodels.h
index bf9b647..8fa6b9c 100644
--- a/include/include/cmp_datamodels.h
+++ b/include/include/cmp_datamodels.h
@@ -21,7 +21,7 @@
 #if (__cpp_impl_three_way_comparison >= 201907L)
 #include <compare>

-#define THREE_WAY_COMP true
+#define THREE_WAY_COMP false
 #else
 #define THREE_WAY_COMP false
 #endif
diff --git a/source/cmp_lookandfeel.cpp b/source/cmp_lookandfeel.cpp
index cf0d24b..5c4701b 100644
--- a/source/cmp_lookandfeel.cpp
+++ b/source/cmp_lookandfeel.cpp
@@ -41,7 +41,7 @@ static std::vector<float> getLinearTicks(
   return ticks;
 };

-static constexpr std::pair<float, float> getFirstEndFromPreviousTicks(
+static const std::pair<float, float> getFirstEndFromPreviousTicks(
     const std::vector<float>& previous_ticks, const cmp::Lim_f lim) {
   auto start_value = 0.0f;
   {
@@ -1101,4 +1101,4 @@ template class PlotLookAndFeelDefault<Scaling::linear, Scaling::logarithmic>;

Thanks! I removed the three_way_comp since it's not used and removed the constexpr. Let me know if you found more issues on Linux and how to solve them. I tried it out on Ubuntu once a few months ago, and the library looked quite bad compared to Windows and Mac. But I don't remember the exact environment I used then.


Switch New York Times case study to use youtube shortcode

This is a clean up request

What would you like to be added
Update the case study for the New York Times to use the youtube shortcode that is built in to Hugo.
Why is this needed
Using HTML and iframes directly is not as easy to maintain as Hugo shortcodes, which are explicitly designed to afford code reuse.
Comments
/kind cleanup
/help
/language en
If you make this change, preview the site locally and check that the videos still render.
Related to https://github.com/kubernetes/website/issues/23660

/assign

Thanks @habibrosyad


Remove shard allocation restriction from the table shrink flow

Summary of the changes / Why this improves CrateDB
Checklist

[] User relevant changes are recorded in CHANGES.txt
[x] Touched code is covered by tests
[x] Documentation has been updated if necessary
[x] CLA is signed

@joemoe FYI


python310Packages.fe25519: 1.4.0 -> 1.4.2, python310Packages.ge25519: 1.4.0 -> 1.4.3

Description of changes

Things done

Built on platform(s)

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

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

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

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

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

[ ] Fits CONTRIBUTING.md.

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

8 packages built:

python310Packages.fe25519
python310Packages.fe25519.dist
python310Packages.ge25519
python310Packages.ge25519.dist
python311Packages.fe25519
python311Packages.fe25519.dist
python311Packages.ge25519
python311Packages.ge25519.dist


DS-1924 Include current locale in calculating cache key

This ensures that the value of the 'current locale' page meta element reflects locale switches made by the user.

+1, tested


"Ignoring remote @import of " message during build

⚠ IMPORTANT ⚠ Please check the following list before proceeding. If you ignore this issue template, your issue will be directly closed.

[x] Read the docs.
[x] Use Vite >=2.0. (1.x is no longer supported)
[x] If the issue is related to 1.x -> 2.0 upgrade, read the Migration Guide first.

Describe the bug
The dependency we use to import company styles does a @import of a google font url:
@import url("https://fonts.googleapis.com/css?family=Open+Sans:200,200i,400,400i,500,500i,600,600i,700,700i,900,900i&display=swap");

During the build step, the following warning appears:
warnings when minifying css:
Ignoring remote @import of "https://fonts.googleapis.com/css?family=Open+Sans:200,200i,400,400i,500,500i,600,600i,700,700i,900,900i&display=swap" as no callback given and after other content.

And indeed, the font is not imported in the dist build, resulting in a visual difference between the npm run serve and the build.
Reproduction
https://github.com/scambier/test-vite-app/tree/8ff2fd4783aa3b025fbfce283236f927071f22c1
The @import is in App.vue

clone
npm install
npm run dev => The font is Open Sans
npm run build => The warning appears
start a local server in ./dist => Open Sans is not loaded, the font is serif

System Info

vite version: 2.0.0-beta.61
Operating System: Windows 10
Node version: 14.15.4
Package manager (npm/yarn/pnpm) and version: npm 6.14.10

Logs (Optional if provided reproduction)

Run vite or vite build with the --debug flag.
Provide the error log here.

  vite:config no config file found. +0ms
  vite:config using resolved config: {
  vite:config   root: 'C:/Users/[user]/Dev/test-vite-app/dist',
  vite:config   base: '/',
  vite:config   mode: 'production',
  vite:config   configFile: undefined,
  vite:config   logLevel: undefined,
  vite:config   clearScreen: undefined,
  vite:config   build: {
  vite:config     target: [ 'es2019', 'edge16', 'firefox60', 'chrome61', 'safari11' ],
  vite:config     polyfillDynamicImport: true,
  vite:config     outDir: 'dist',
  vite:config     assetsDir: 'assets',
  vite:config     assetsInlineLimit: 4096,
  vite:config     cssCodeSplit: true,
  vite:config     sourcemap: false,
  vite:config     rollupOptions: {},
  vite:config     commonjsOptions: { include: [Array], extensions: [Array] },
  vite:config     minify: 'terser',
  vite:config     terserOptions: {},
  vite:config     cleanCssOptions: {},
  vite:config     write: true,
  vite:config     emptyOutDir: null,
  vite:config     manifest: false,
  vite:config     lib: false,
  vite:config     ssr: false,
  vite:config     ssrManifest: false
  vite:config   },
  vite:config   inlineConfig: {
  vite:config     root: undefined,
  vite:config     base: undefined,
  vite:config     mode: undefined,
  vite:config     configFile: undefined,
  vite:config     logLevel: undefined,
  vite:config     clearScreen: undefined,
  vite:config     build: {}
  vite:config   },
  vite:config   publicDir: 'C:\\Users\\[user]\\Dev\\test-vite-app\\dist\\public',
  vite:config   command: 'build',
  vite:config   isProduction: true,
  vite:config   optimizeCacheDir: 'C:\\Users\\[user]\\Dev\\test-vite-app\\node_modules\\.vite',
  vite:config   alias: [ { find: /^\/@vite\//, replacement: [Function: replacement] } ],
  vite:config   plugins: [
  vite:config     'alias',
  vite:config     'vite:dynamic-import-polyfill',
  vite:config     'vite:resolve',
  vite:config     'vite:html',
  vite:config     'vite:css',
  vite:config     'vite:esbuild',
  vite:config     'vite:json',
  vite:config     'vite:wasm',
  vite:config     'vite:worker',
  vite:config     'vite:asset',
  vite:config     'vite:css-post',
  vite:config     'vite:build-html',
  vite:config     'commonjs',
  vite:config     'vite:data-uri',
  vite:config     'vite:define',
  vite:config     'rollup-plugin-dynamic-import-variables',
  vite:config     'vite:import-analysis',
  vite:config     'vite:esbuild-transpile',
  vite:config     'vite:terser',
  vite:config     'vite:size'
  vite:config   ],
  vite:config   server: {},
  vite:config   env: { BASE_URL: '/', MODE: 'production', DEV: false, PROD: true },
  vite:config   assetsInclude: [Function: assetsInclude],
  vite:config   logger: {
  vite:config     hasWarned: false,
  vite:config     info: [Function: info],
  vite:config     warn: [Function: warn],
  vite:config     error: [Function: error],
  vite:config     clearScreen: [Function: clearScreen]
  vite:config   },
  vite:config   createResolver: [Function: createResolver]
  vite:config } +7ms
building for production...
dist/assets/favicon.f749aae1.ico          4.19kb
dist/assets/vendor.4ead770d.f8b50b9a.js   42.32kb
dist/assets/index.a066a697.js             44.72kb / brotli: 16.01kb
dist/assets/index.60c5379a.css            0.18kb / brotli: 0.12kb
dist/index.html                           0.49kb

@yyx990803 I updated to beta 62, the warning message is gone (per your commit), but the core problem is still there: the font is not loaded.


add more mouse button support and Toggle() function style with KeyTog…

Please provide Issues links to:

Issues: #

Provide test code:

Description
...

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


Use KernelAbstractions backend

This is a big step towards closing #32.
What else is needed:

Remove CUDA/Adapt extension/dependency
Add other backend tests?
Improve the performance
Fix #34

Right now, at least on the CPU, the KA kernels are more than 5x slower. cc @avik-pal @vchuravy

Thanks for looking into this so quickly. I generally tend not to use KA for CPU (in favor of just the @simd loop), but I think it uses threading for CPU, which might not be ideal for smaller broadcasting problems.

Thanks for looking into this so quickly. I generally tend not to use KA for CPU (in favor of just the @simd loop), but I think it uses threading for CPU, which might not be ideal for smaller broadcasting problems.

Yeah, I thought I'd give it a try, it's kind of a nice solution, to be honest. The only reason CUDA is still needed in the extension is for Adapt. I think that this branch should mostly support other backends, but if Adapt is needed for other backends, then I think you'd need to add it. I don't have experience adapting AMD gpus, but I imagine the pattern is very similar.
Feel free to try things on this branch. I probably won't merge this in until we add tests (to close #34), and perhaps fix the cpu perf, or just revert things to how we previously had it.


AWS lambda runtime integration

Take this repository:
https://github.com/umccr/s3-rust-noodles-bam
And:

Set it up, deploy, run as-is.
Add a sub-crate hooks to the same API endpoints as the HTTP one.
Benchmark.

Watch out for https://github.com/awslabs/aws-lambda-rust-runtime/pull/332, which TL;DR means that one cannot test the lambda locally (yet), some headers need to change in the runtime to allow sam local invoke et al to work.
Until then, sam deploy is required for every test, which is quite time consuming due to (slow) AWS SAM tooling.

PR merged yesterday! I'll give it a spin tomorrow to see if it works fine locally, it'll simplify development greatly.

Current local blocker: https://github.com/aws/aws-sam-cli/issues/3132


unit: remove explicitly prefixed constants

Please take a look.
Closes #90.

PTAL

I'll wait.

That's such an obvious solution to the Kg problem ... can't believe I didn't think of that.

Which part, the extra constant or the 1e-3?

Setting the gram to be 1e-3.

When you remove all the constants, that's what was left. It seemed obvious.

I agree, it does seem obvious


Deployment via uvicorn fails: TypeError: call() missing 2 required positional arguments: 'receive' and 'send'

I'm trying to run the First Steps example from the documentation and get the following error:

$ uvicorn main:app --host <IP_ADDRESS> --port 5000
INFO: Started server process [3712]
INFO: Uvicorn running on http://<IP_ADDRESS>:5000 (Press CTRL+C to quit)
ERROR: Exception in ASGI application
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/uvicorn/protocols/http/httptools_impl.py", line 388, in > run_asgi
asgi = app(self.scope)
TypeError: call() missing 2 required positional arguments: 'receive' and 'send'
INFO: ('<IP_ADDRESS>', 1092) - "GET / HTTP/1.1" 500

fastapi          0.45.0
Any suggestions?

Hypercorn seems to run just fine, any info on this anyways?

It might be a uvicorn version issue -- could you let us know what versiosn of uvicorn you are using?
If it isn't a version issue, a minimal reproducible example would also make it a lot easier to verify/work on the problem.

I didn't even know that was available as a Debian package :joy: :man_shrugging:
Yeah, what they said. Install with pip. And create an environment first.

File "/root/FastApiTest/lib/python3.6/site-packages/hypercorn/asgi/h11.py", line 107, in handle_asgi_app
asgi_instance = self.app(self.scope)
TypeError: call() missing 2 required positional arguments: 'receive' and 'send'
i dont know what to do, is this some sort of bug or what? the API calls returns empty page with 500 error

@AlinaSec that seems pretty much like your server (Hypercorn) is trying to use version 2.0 of the ASGI specification, instead of the current latest, version 3.0.
You should be able to upgrade Hypercorn to a more recent version. Or you could alternatively use a recent version of Uvicorn or Daphne too.
Anyway, if you still have problems, please create a new issue following the template.


titleTemplate bug should fix it immediately

Version
v2.4.5
Reproduction link
https://github.com/nuxt/nuxt.js/issues/5051
Steps to reproduce
this issue is fixed and merged
What is expected ?
we use SSR for SEO, titleTemplate is very useful and important.
This bug has been around for a long time, but it has not been fixed.
I think we should pay more attention to the impact of this bug and release a fix version as soon as possible.
What is actually happening?
titleTemplate can't work

This bug report is available on Nuxt community (#c8799)

Why do u create a new issue for already opened one? Im closing this one  unless u can provide how its different from the one you linked
PS and you can use titleTemplate with explicit return as described in issue you linked


chore(deps): update helm release base to v1.16.1

This PR contains the following updates:

Package
Update
Change

base
minor
1.15.1 -> 1.16.1

Release Notes

istio/istio
v1.16.1: Istio 1.16.1
Compare Source
Artifacts
Release Notes
v1.16.0: Istio 1.16.0
Compare Source
Artifacts
Release Notes
v1.15.4: Istio 1.15.4
Compare Source
Artifacts
Release Notes
v1.15.3: Istio 1.15.3
Compare Source
Artifacts
Release Notes
v1.15.2: Istio 1.15.2
Compare Source
Artifacts
Release Notes

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

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

This PR has been generated by Renovate Bot.

:tada: This PR is included in version 1.0.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


feat(config):  include additional config files

Background

I will add the sesh config file to my GitHub repository dotfiles, but I don't want to commit some sensitive information to the public GitHub repository. For example:

I have the following sesh startup_scripts config, but I don't want to add the sensitive info (company name) ~/code/my_compay to my Github repository[[startup_scripts]]
session_path = "~/code/my_compay/third_session"
script_path = "~/.config/sesh/scripts/third_script"

The solution is to allow the sesh config to include additional config files, and then I could exclude the additional config files from the git commit history.

Usage

The custom sesh config

# ~/.config/sesh/sesh.toml

default_startup_script = "default"

[[startup_scripts]]
session_path = "~/dev/first_session"
script_path = "~/.config/sesh/scripts/first_script"

[[startup_scripts]]
session_path = "~/dev/second_session"
script_path = "~/.config/sesh/scripts/second_script"

[[extended_configs]]
path = "~/.config/sesh/local/sesh.toml"

The following config is an additional config that will be included in the custom sesh config

# ~/.config/sesh/local/sesh.toml
[[startup_scripts]]
session_path = "~/dev/third_session"
script_path = "~/.config/sesh/scripts/third_script"

Test Cases

All of the test cases are passed.

Hi @joshmedeski Do you know why the bench tests keep failing? Do you think it is a GitHub action resource issue?

It appears to be working now. Thanks for creating the tests, I mostly just wanted some awareness for where this feature drops off in performance, and we now have that answer.
I'll look over the code again and do some manual testing then I can merge and ship it, thanks!

I've got some more work to do this week, so I probably will do a release on Friday. Nice work!

@0xRichardH did you play around with the built-in import feature from toml?
import = ["~/code/my_compay/sesh.toml"]

It didn't work on my first try, but this seems more simple and more inline with how toml works rather than us trying to create a brand new pattern.
We could even convert what we did to an array instead of grouping by [[extended_configs]].
What do you think? I want this to be as simple as possible before documenting and shipping it.

https://github.com/toml-lang/toml/issues/397

@0xRichardH did you play around with the built-in import feature from toml?
import = ["~/code/my_compay/sesh.toml"]

It didn't work on my first try, but this seems more simple and more inline with how toml works rather than us trying to create a brand new pattern.
We could even convert what we did to an array instead of grouping by [[extended_configs]].
What do you think? I want this to be as simple as possible before documenting and shipping it.

The toml itself doesn't support import feature https://github.com/toml-lang/toml/issues/397 . but it will be more elegant to use import to replace extended_configs. I will create a new PR to make a change.
import = ["~/code/my_compay/sesh.toml"]

Thanks! I'll look it over.


Nullable!T doesn't wrap

eg
skipping Nullable!(TDLine!(PriceBar!(PriceBarType(cast(PriceBarFlags)32u), -1, "Daily")))
skipping Nullable!(TDLine!(PriceBar!(PriceBarType(cast(PriceBarFlags)96u), -1, "Intraday")))
skipping Nullable!(KPDate!(cast(KPDateType)2, "Europe/London"))

The current version no longer skips Nullable at least when I tried it with Nullable!int. It does, however, crash, but that's a pyd bug.


Webapp: Import error on 'appservice' commandlet

This is autogenerated. Please review and update as needed.
Describe the bug
Command Name
az appservice
Errors:
cannot import name 'DefaultErrorResponseException' from 'azure.mgmt.web.models' (/usr/lib/python3/dist-packages/azure/mgmt/web/models.py)
Traceback (most recent call last):
python3/dist-packages/knack/cli.py, ln 233, in invoke
    cmd_result = self.invocation.execute(args)
cli/core/commands/__init__.py, ln 584, in execute
    parsed_args = self.parser.parse_args(args)
python3/dist-packages/knack/parser.py, ln 262, in parse_args
    return super(CLICommandParser, self).parse_args(args)
...
cli/command_modules/appservice/custom.py, ln 39, in <module>
    from azure.mgmt.web.models import KeyInfo, DefaultErrorResponseException
ImportError: cannot import name 'DefaultErrorResponseException' from 'azure.mgmt.web.models' (/usr/lib/python3/dist-packages/azure/mgmt/web/models.py)

To Reproduce:
Steps to reproduce the behavior. Note that argument values have been redacted, as they may contain sensitive information.

Put any pre-requisite steps here...
az appservice --help

Expected Behavior
Environment Summary
Linux-5.10.0-0.bpo.8-amd64-x86_64-with-debian-buster-sid
Python 3.7.2rc1
Installer: DEB

azure-cli 2.18.0 *

Extensions:
azure-devops 0.18.0

Additional Context

route to service team

closing due to lack of response. Please file a new issue if this is still a problem.


Fix zoom out when wheel event.deltaY is zero

Don't apply zoom in or zoom out when deltaY is zero on wheel events. Should fix https://github.com/openseadragon/openseadragon/issues/947 and not make OpenSeadragon zoom out when scrolling horizontally on a touchpad.

Oups, sorry I didn't intend to add these in the PR! I'll clean that, I just wanted the small fix here.

Should be good now, I reverted the second commit that introduced these changes.

Ugh! Artificial scroll events from trackpads...another well known pain point for web events ;)
This fix is good, thanks @cavenel !


Move more iface tests to test ipv6

I used cfg to use IPv6 if IPv6 is available and IPv4 otherwise. We could instead test both, with a test_ipv4 test module and test_ipv6 test module. Would that be preferred?

@m-labs-homu r+

:pushpin: Commit 9a56b3d has been approved by whitequark

:hourglass: Testing commit 9a56b3d4e9df9b706347431087934becfe0211f8 with merge 43a049382b12a4c9131637b753f58b53a87d29ad...

:broken_heart: Test failed - status-travis

@m-labs-homu retry

:sunny: Test successful - status-travis
Approved by: whitequark
Pushing 94d7338aed6d4b5157d328915b5ac94236fc6427 to master...


[Translation: ID] quests

hey, i want submit my translation quest for indonesian version,
must i edit n upload developers.json file here too? to include my personal link?

hi, do you currently have a fork, or is this manual?
We do have translators working on Indonesian version, but it seems they haven't submitted the quests.json yet. I'd like to tag them here and get their response, so we can all be up-to speed on how to move forward.
@hufuhufu @freezebear
You can upload the file here if you want, so they may check on it later. Once approved, we will merge/push your work on the master branch. I will add you to developers.json myself after this, just post up to 5 desired links for the about page.

i do this manualy
just add my facebook link
https://www.facebook.com/bayuuyab.fu

n where should i upload quests.json
sorry im new in github

probably pastebin, or puush

allright here's the file link
http://pastebin.com/JaYHv1Ck

ah thanks for this. I looked also at both of their forks and seems they don't have any quests.json on any of their branches. I will push this to master in a while.
Also if you're interested, we added around five new quests just earlier, highlighted here:
https://github.com/dragonjet/KC3Kai/commit/19921a000f36e6e2ae80aeab009ae5f754260ab7

okay i'll learn how to forks and add that quest too

@vrarara i think the translation need better proofreader. I'm indonesian myself and the translation are bad from my point.

@McDohl i will fix it, if u want can u give FB link for more chat :)

oh good thin i havent pushed this, you guys can discuss it and upload via @McDohl's fork

I'm actually just started translating quests.json.
@vrarara I've sent friend request so we could discuss this.

okay


React Tutorial

I create a new repository and work on a new branch (use Gitflow).
I open a pull request with all my changes.
Add some styles and JSX.

@lilskyex0x Thank you 🙌


DOC: add a skeleton and workflow for docs building

This is the first iteration of the docs for the repo. We can do improvements via separate PRs as we go.

I changed the sphinx theme to https://cloud-sptheme.readthedocs.io/en/latest/ (similar to https://github.com/NSLS-II/sirepo-bluesky/pull/80). The built docs will look like:

@JunAishima, @gwbischof, ready for your review. The built docs are available in https://github.com/nsls2-conda-envs/conda-pack-template/actions/runs/3085767320 if you'd like to check the rendered version.

OK, I am going to merge it given one review (that I dismissed to solve the CI/STY issues.)

The docs are live now: https://nsls2-conda-envs.github.io/conda-pack-template (implemented via https://github.com/nsls2-conda-envs/conda-pack-template/commit/1ae01fa34c1a666e089e539ed92ba8f8e0184b28 and the repo settings).
The https://github.com/nsls2-conda-envs/conda-pack-template/commit/0ff2ad364ad85d2b96ebea6cf2c8b6eb286b75e3 commit updates the README.md file.
The next step is to rename the repo and apply the changes to all env-repos.


The type initializer for 'Confluent.Kafka.Impl.LibRdKafka' threw an exception

Hello,
I am using the liberary in my Windows Service VS2015 solution, and its work fine on my devlopement environment under Windows 7 Entreprise .
However, when I install the service ( InstallUtil.exe -i myService.exe, with the same binaries) on my testing server (Windows Server 2008 R2, Framework .net 4.5.2),  I get the following error when trying:" The type initializer for 'Confluent.Kafka.Impl.LibRdKafka' threw an exception"
Thank you in advance for any suggestions?

What Confluent.Kafka version are you using?
We pushed new NuGet packages for Confluent.Kafka and librdkafka.redist yesterday which shouldve fixed a number of linking problems people were seeing.

I used <IP_ADDRESS>
I am now using the 0.9.4-preview8, I got same probleme.

I'm not sure how you package up and deploy your application for target install, but make sure that librdkafka.dll, zlib.dll, etc, are installed along with your application.

Please file an issue on https://github.com/confluentinc/confluent-kafka-dotnet and close this one.

I do have these dlls in folders x86 & x64...
It must be a missing components on my test environment, as the same package is working well on my development machine..

@MSDRIOUICH did you find the root cause of the problem?

@edenhill When I package my application for deployment through Octopus Deploy, the librdkafka.redist.0.9.4 NuGet package outputs to folders x86 and x64 rather than the application root folder, so the application does not find the required librdkafka DLLs. I assume that this is controlled by the file librdkafka.redist.props. It runs fine in Visual Studio and seems to find the DLLs, but once deployed it can no longer find them in the subfolders. If I copy the files from the x86 folder to my application root it works ok. What is the way best way to handle this?

...I have forced the correct files to the root folder using a nuspec file when generating my deployment NuGet package


Android app crashes after updating RN to 0.45

I updated RN 0.45.0 and after that the app crashes as soon as I try to open any file. I found that If I change my targetSdkVersion to 23 (instead of 25) it doesn't crash, but instead tells me that "Media not found".
Any solution?

i dont have tested it on 0.45. i will test it and give you a feedback

Okay. Figured it out.
At the moment you are saving files to apps cache, but other apps cannot access those files. This is an Android this. They are pushing for devs to use content :// instead of file://. I run into this because I'm using Android 7.1.2. I made some modifications to your library and made it work. But because I defined FileProvider in the manifest file of your library it breaks another library that uses FileProvider when merging manifest files. Not sure how to get around it yet. I can do a pull request with my solution.

At the moment I have no time to fix these things on android. Sure you can send me a pull request. Thank you for your help.


[Source Engine] Translucent sprites rendering issue

Hard edges on translucent sprites env_sprite with World Space Glow render mode (9) in Source engine games, also affects to env_lensflare in Black Mesa
Software information
Tested on Half-Life 2 Deathmatch, Black Mesa
System information\Tested on

GPU: NVIDIA GeForce RTX 3060 Ti \ NVIDIA GeForce GTX 1660 Ti
OS: Windows 10 / 11
Driver: NVIDIA 552.22.0
DXVK version: 32bit since 1.3.9 (earlier versions have not been tested) to 2.3.1

Apitrace file(s)
hl_trace
Log files
hl2_d3d9.log
Screenshots
Black Mesa sreenshots:

Half-Life 2 Deathmatch sreenshots:

Just checking out the apitrace it looks fine on my RX 7900xtx with both radv and amdvlk

Internal note:
It's blending a texture that gets uploaded via a simple Lock,Copy,Unlock onto the render target. The blending is a simple add and output alpha of the fragment shader is 1.0 across the board.
The only thing that might be interesting is that both the RT as well as the texture are reinterpreted as SRGB.

I looked into the problem a little. I added alpha channel to the texture, cuz it was with no alpha DXT1 and created a new material then I tried different shader parameters
--Shader used: UnlitGeneric
--Shader parameters tested: $translucent 1 $additive 1
--Texture format: DXT5 Compressed texture

So... this looks like a problem with $additive 1 only, and maybe Nvidia drivers

This indeed is looking like a Nvidia driver bug. We've confirmed that it looks fine on AMD with the radv and amdvlk driver. On Intel it looks good with the Linux driver and on Nvidia it also looks fine on the NVK Linux driver while Nvidia own have the issue.

No. A bug report needs to be made to Nvidia, which we haven't gotten to yet (I've volunteered now)

Forgot to update here that this have been reported to Nvidia and is being tracked as bug number 4762602


Support of drawing image/icon in centre instead of text.

Example use case is SMS/Messages App: If message is from a known contact their initials are drawn else a default icon like this.

+1 this would be very useful.

+1 I need this !

+1 I need this

+1

Yep, I wanted this for some time!


unable to delete a folder which is not empty

hi,
I am unable to delete a folder which is not empty and getting the following error.
{"RemoteException":{"exception":"PathIsNotEmptyDirectoryException","javaClassName":"org.apache.hadoop.fs.PathIsNotEmptyDirectoryException","message":"`/aakash is non empty': Directory is not empty"}}

In order to delete a directory that has content you need to pass the recursive option as well as a callback for handling errors like so:
import WebHDFS from 'webhdfs';

const client = WebHDFS.createClient({
  host: 'example.dev.company.com',
  port: 8080,
  path: '/',
});

const deleteDirectoryWithContent = (directoryPath) =>
  client.unlink(directoryPath, true, (error) => {
    if (error) throw error;
  });


Need help in updating the public doc for Azure Bastian Subnet usage

[Feedback:
The doc that needs to be updated is
https://learn.microsoft.com/en-us/azure/bastion/bastion-nsg#apply
In this doc, the AllowBastianHostCommunication tag for Outbound rule shows that protocol should be set as "Any".
But there are few customer companies for security reasons do not permit to use "ANY" under the protocol section. We worked internally with the Product group from Bastian product and the engineer confirmed that we do not need "ANY" under the protocol section, instead allowing only "TCP" under the protocol section would be suffice for the Bastian service to work effectively. The customer is looking for adding this on the public doc as note for awareness that they can communicate to their internal security teams. Hence please do the necessary modification on the above public doc. ]

Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

ID: cc46ceac-e45e-6f29-dd5b-6453c614d9b2
Version Independent ID: b8b3bb83-5204-1f8b-787f-eb3da444e22e
Content: Working with VMs and NSGs in Azure Bastion
Content Source: articles/bastion/bastion-nsg.md
Service: bastion
GitHub Login: @cherylmc
Microsoft Alias: cherylmc

@sruthik2105 , thank you for your feedback. We have assigned this to the content owner/author for review.
@cherylmc , for your review.

#reassign:isamorris

Hello Team, any update ?

Hello Team, is this task being reviewed ? @cherylmc @isamorris

Hi! I'm looking into updating this page. Can you tell me, is it the "AllowBastionCommunication" field for Egress? The reason I ask is that the "AllowBastionHostCommuncation" field (mentioned in the GitHub issue) is the field for Ingress (the name is slightly different) I want to be sure to update the proper field.

#please-close


put-bucket-acl doesn't seem to do anything

Environment info

NooBaa Version: noobaa-core-5.15.0-20231114.el8.x86_64
Platform:  other: noobaa standalone

Actual behavior

Setting bucket ACL using "aws s3api put-bucket-acl" returns success, but doesn't seem to do anything.

Expected behavior

Expect bucket ACL to be applied, or command to fail.

Steps to reproduce
# aws --profile user1 --endpoint http://localhost:6001/ s3 mb s3://bucketname2
# aws s3api put-bucket-acl --bucket bucketname2 --grant-full-control name=backupuser --endpoint http://localhost:6001/ --profile user1
# aws s3api get-bucket-acl --bucket bucketname2  --endpoint http://localhost:6001/ --profile user1

An error occurred (NoSuchBucketPolicy) when calling the GetBucketPolicy operation: The specified bucket does not have a bucket policy.

More information - Screenshots / Logs / Other output
Logs during put-bucket-acl:
Nov 16 12:51:57 scale-test-os-1.oslo.forum.ibm.com node[523830]: [nsfs/523830]    [L0] core.sdk.bucketspace_fs:: BucketSpaceFS.read_bucket_sdk_info: bucket_config_path /ibm/cesSharedRoot/noobaa/buckets/bucketname2.json
Nov 16 12:51:57 scale-test-os-1.oslo.forum.ibm.com node[523830]: Nov-16 12:51:57.812 [nsfs/523830]    [L0] core.sdk.bucketspace_fs:: BucketSpaceFS.read_bucket_sdk_info: bucket_config_path /ibm/cesSharedRoot/noobaa/buckets/bucketname2.json
Nov 16 12:51:57 scale-test-os-1.oslo.forum.ibm.com node[523830]: [nsfs/523830]    [L0] core.sdk.bucketspace_fs:: BucketSpaceFS.read_bucket_sdk_info: bucket_config_path /ibm/cesSharedRoot/noobaa/buckets/bucketname2.json
Nov 16 12:51:57 scale-test-os-1.oslo.forum.ibm.com node[523830]: Nov-16 12:51:57.814 [nsfs/523830]    [L0] core.sdk.bucketspace_fs:: BucketSpaceFS.read_bucket_sdk_info: bucket_config_path /ibm/cesSharedRoot/noobaa/buckets/bucketname2.json
Nov 16 12:51:57 scale-test-os-1.oslo.forum.ibm.com node[523830]: [nsfs/523830]    [L0] core.sdk.bucketspace_fs:: BucketSpaceFS.read_bucket_sdk_info: bucket_config_path /ibm/cesSharedRoot/noobaa/buckets/bucketname2.json
Nov 16 12:51:57 scale-test-os-1.oslo.forum.ibm.com node[523830]: Nov-16 12:51:57.817 [nsfs/523830]    [L0] core.sdk.bucketspace_fs:: BucketSpaceFS.read_bucket_sdk_info: bucket_config_path /ibm/cesSharedRoot/noobaa/buckets/bucketname2.json

But no changes are made to the bucketname2.json:
# cat /ibm/cesSharedRoot/noobaa/buckets/bucketname2.json
{"name":"bucketname2","tag":"","system_owner":"noobaa@noobaa.io","bucket_owner":"noobaa@noobaa.io","versioning":"DISABLED","creation_date":"2023-11-16T07:59:02.789Z","path":"/ibm/fs1/buckets/bucketname2","should_create_underlying_storage":true}

And no changes are done on the directory of the bucket... so it seems it's just a silent failure during put-bucket-acl.

ACLs are not supported in NooBaa and/or NS FS. Please use bucket policies


Support freedesktop.secrets (e.g., GNOME Keyring)

I'm using GNOME Keyring to store my GitHub credentials. When I run git pull for a private GitHub repository, git uses the credentials from the keyring. I have the following configuration in ~/.gitconfig to make git use freedesktop.secrets:
[credential]
        helper = /run/current-system/sw/bin/git-credential-libsecret

However, when I run something hub-specific like hub pr list for the same private repository, my username and password are asked on the command-line. If needed, they should be asked by my keyring app and re-used from there. Why is hub working differently than git in this matter?

Hub authentication is for GitHub API and sometimes uses different credentials (especially if you have 2FA enabled on your account) than git credentials, so the two are kept separate, for now. https://github.com/github/hub/issues/1644#issuecomment-359002547 https://github.com/github/hub/issues/1217
I realize that this is poor user experience, sorry about that! 🙇

@mislav Thanks for the quick response! However, a few comments:

Keeping two credentials separate doesn't make my request of supporting freedesktop.secrets (e.g., GNOME Keyring) obsolete. So I don't see a reason to close this issue. Or did I miss something?

How can I change which tool is used to ask for the credentials? Is there any integration to any such tools? Quite often, one can set things like SSH_ASKPASS or SSH_AUTH_SOCK or add some configuration options to choose which tool is used to ask for username and password.

Or what kind of secure credential management Hub supports?

So I don't see a reason to close this issue. Or did I miss something?

I've referenced an existing open issue #1217 which proposes a feature that hub implements storing of credentials using a git credential helper. I've closed this one as duplicate.

Or what kind of secure credential management Hub supports?

Unfortunately, hub doesn't support any secure credential management. It asks you for your GitHub username & password, immediately uses those to exchange them for a Personal Access Token, then stores that token in ~/.config/hub.
Alternatively, you may provide GITHUB_TOKEN via environment variable. You can populate that variable by reading from some secure credential store.

Ok, thanks!


Proposal: how to enable long-term caching of assets.

I'd like to write down a proposal I'm thinking of to implement far future caching in react-server-cli to get feedback before diving in. I have some worries about it, and I'd rather have some discussion before jumping in.
For background, read this excellent article on how to implement long-term caching in webpack; basically my proposal is just to implement everything in that article when in production mode (or when long-term caching's turned on by a flag).
Mostly this is fairly straightforward, but there is one wrinkle that I want to run by all of you. It's the case where you compile the client code ahead of time and upload the assets to a CDN or static server. Then you launch react-server-cli with jsUrl: http://mycdn.com/my/precompiled/assets/, and r-s-c launches just the HTML server, pointing all JS and CSS URLs at something like http://mycdn.com/my/precompiled/assets/main.js.
The problem in this case is that the HTML server needs to know about the output of the client webpack build in order to get the hashed names of both the entrypoint script files and the chunks that are loaded later. I can see two ways to do this:

Decoupled: Don't change the current compile codepath. When firing up a server with jsUrl set, run the compile codepath again just to get the file hashes (and throw away the actual assets).
Manifest File: When compiling the client code, output a manifest.json in the root directory that has all of the file hashes present. When firing up a server with jsUrl set, do NOT compile the client. Instead pull down the manifest file via HTTP(S) and use that to determine the file names.

I'm leaning towards a manifest file. If for whatever reason the client compilation was performed on a different version of the app codebase than what the server is attempting to run, we could detect that case using the manifest file and warn or refuse to start up at all. I'm sure that client/server version mismatches would create wildly hard to find bugs.
I also have some worries about the manifest file, particularly that requiring there to be a network path from the HTML server to the static file server might trip some folks up. Thoughts?

We actually implemented something like this internally that sounds similar to option 2. We have a roughly five line webpack plugin that outputs a file called assetsByChunkName.json that we use to tell the server about the entrypoints. For lazy-loaded JS bundles, webpack keeps its own mappings internally, and just knows what files to load. AFAIK, we don't use the assetsByChunkName.json file on the client at all. (cc @bartkusa, who worked on this originally)

Thanks, @roblg!

For lazy-loaded JS bundles, webpack keeps its own mappings internally, and just knows what files to load.

FYI, the Medium article I linked to above explains that this is not enough to keep the hashes constant from build to build; any change to any module changes all the hashes of all entry chunks, even if the entry chunk doesn't include that module. You have to use ChunkManifestPlugin as well; see the section on "Deterministic Hashes".
Any thoughts on using HTTP(S) to download a manifest when the client build is being served up by another server?

Interesting. We definitely expected to have issues w/ non-deterministic behavior, and looked for it, and didn't find it. Although I think we were worried about hashes changing for no reasons. Maybe they all change if any file changes? I don't recall if we checked for that (but @bartkusa may remember).
There's a comment from sokra on the issue linked in the blog post saying that occurrence order is the default. (And then some comments from people after that saying they're still experiencing the issue, though maybe in very particular circumstances.) So maybe it's fixed, maybe not? If we can get away with not adding a dependency on YAWP (Yet Another Webpack Plugin), that would be my preference. IME, the more plugins you have in the build, the more bugs you find in plugins in the build. :)
In any event, to answer your actual question: I don't think see a problem with downloading the file from the static content server at startup.
Alternatively, what's preventing us from just outputting the file in the frontend build, and then having that file copied into the server deploy tar or whatever as a step outside r-s-c? Just convenience?

Although I think we were worried about hashes changing for no reasons. Maybe they all change if any file changes?

Yeah, this issue is not about non-determinism from one build to the next when the code doesn't change. It's about a small code change changing all hashes for all chunks, including completely unrelated ones. To quote the article:

The problem with this is the same as before: whenever we change any part of the code, it will, even if the rest of its contents wasn’t altered, update our entry chunk to include the new manifest.

The problem is that every entry chunk keeps a map of all chunk names, which of course includes the chunk hashes in the chunk names. So, when any chunk changes, its hash changes, which means that the chunk name map changes, which changes the text of the entry chunk, which changes the entry chunk's hash. Yay.

There's a comment from sokra on the issue linked in the blog post saying that occurrence order is the default. (And then some comments from people after that saying they're still experiencing the issue, though maybe in very particular circumstances.) So maybe it's fixed, maybe not?

Occurrence order is a different problem, which can cause hashes to change between different builds of the same codebase. You also need the OccurrenceOrderPlugin (which also is in the linked article).
In that thread, sokra says it's on by default in the next major version (i.e. webpack 2), which is confirmed in this webpack 2 feature list.

what's preventing us from just outputting the file in the frontend build, and then having that file copied into the server deploy tar or whatever as a step outside r-s-c?

I'm trying to decide what to do when react-server-cli is used to build the client code separately from starting up the HTML server, as described here in the docs. I suppose those instructions could be changed to say something like "step 2.5: Copy manifest.json to your server somewhere" and then "step 3: when you start up the HTML server, pass the manifest file in at the command line using --manifest=location/of/manifest.json along with jsUrl". Is that what you mean?

re: determinism - Le sigh. I suppose we probably have a bug to fix now internally as well.

I suppose those instructions could be changed to say something like "step 2.5: Copy manifest.json to your server somewhere" and then "step 3: when you start up the HTML server, pass the manifest file in at the command line using --manifest=location/of/manifest.json along with jsUrl".

Yep, that's what I was thinking. That's basically what we do today internally. I'm assuming that there should be another step somewhere in there that's like "copy your server code to " as well, right? I would think it would go along with that.

YAWP

😆 ... 😂 ... 😢

@aickin - Was this covered by #96, or is there more you'd like to see done here?

Sorry, yeah, I think this is covered. Closing!

Thanks!


[Suggestion]: code style improvement

Hi there!
I've recently delved into the codebase, and I've observed that there is room for style improvements. Currently, there is a considerable inconsistency in style both within individual files and between them.
Here's what I'm proposing:
(1) Review: I'll thoroughly review the codebase file by file and pinpoint areas where code style can be enhanced.
(2) Pull Requests (PRs): For each file that requires changes, I'll initiate a separate PR. This approach allows for a systematic review and discussion about the proposed changes.

totes.
i'd suggest starting with the internal agents code because its desparate for love, and theres little activity there to coord around

Yeah, we need review guidelines!  @us was really good at reviews, so maybe he can suggest a guideline we can use?

I'm not the biggest fan of style guides though this early.

I want to fix this issue. Is anyone working on this?

This issue is currently on hold and will be addressed by the core team in future


Barrier assertion error + hang

After ~1M iterations, my code hits the following assertion error:
/nobackupp2/kbando/Softwares/legion/runtime/realm/runtime_impl.cc:2361: Realm::BarrierImpl* Realm::RuntimeImpl::get_barrier_impl(Realm::Event): Assertion `id.is_barrier()' failed.

A backtrace can be found at /home/bandokihiro/Public/DebugBarrier/barrier_assertion_bt.
Changing MAX_PHASES to MAX_PHASES/2 in legion_trace.cc did not solve the issue and the code fails after approximately the same number of iterations. Further changing to MAX_PHASES/4 led to a hang. Backtraces can be found at /home/bandokihiro/Public/DebugBarrier/vortex/hang_pleaides.
I tried to reproduce on sapling with MAX_PHASES/2 and it hanged. Bactraces can be found at /home/bandokihiro/Public/DebugBarrier/vortex/hang_sapling. In order to run it, just execute /home/bandokihiro/Public/DebugBarrier/vortex/run.sh.

@streichler I don't think I can assign you

Some updates (with help from both @bandokihiro and @lightsighter ):

The problem seems to be related to the barrier regeneration that happens here: https://gitlab.com/StanfordLegion/legion/-/blob/control_replication/runtime/legion/legion_trace.cc#L4845
Different ranks are stopping to wait at different points, which leads to deadlock.
Running with -lg:inorder seems to allow reliable barrier regeneration, although probably at a performance cost.
Disabling the use of tracing ought to avoid the issue, also probably at a performance cost.
@lightsighter will be able to look at this in more detail on Monday.

thanks, did we figure out only the source of the hang or also the assertion error?

Just the hang so far.  It's possible that the assertion error is related, but it's also possible it's a separate off-by-one issue.

Pull the control_replication branch and try again.

I was able to hit the assertion error on sapling so the hang looks fixed

Pull and try again.

it did not hit the assertion error but hanged instead at about the same number of iterations. backtraces can be found at /home/bandokihiro/Public/DebugBarrier/vortex/hang_0908

I need frozen processes to look at for tonight.

The changes I made
bandokihiro@sapling:~/Public/DebugBarrier/legion$ git diff
diff --git a/runtime/realm/runtime_impl.cc b/runtime/realm/runtime_impl.cc
index c2575fc..0a3c8a1 100644
--- a/runtime/realm/runtime_impl.cc
+++ b/runtime/realm/runtime_impl.cc
@@ -2358,6 +2358,31 @@ namespace Realm {
     BarrierImpl *RuntimeImpl::get_barrier_impl(Event e)
     {
       ID id(e);
+      if (!id.is_barrier()) {
+        printf("Reached assertion failure. Abort and freeze.\n");
+        std::cout << "ID = " << id << std::endl;
+
+
+        int process_id = getpid();
+        char hostname[128];
+        gethostname(hostname, 127);
+        // fprintf(stderr,"Legion process received signal %d: %s\n",
+        //                 signal, strsignal(signal));
+        fprintf(stderr,"Process %d on node %s is frozen!\n",
+                        process_id, hostname);
+        fflush(stderr);
+
+        // // now that we've stopped, don't catch any further SIGINTs
+        // struct sigaction action;
+        // action.sa_handler = SIG_DFL;
+        // sigemptyset(&action.sa_mask);
+        // action.sa_flags = 0;
+
+        // CHECK_LIBC( sigaction(SIGINT, &action, 0) );
+
+        while (true)
+          sleep(1);
+      }
       assert(id.is_barrier());

       Node *n = &nodes[id.barrier_creator_node()];

was not hit this time. The code is hanging on sapling on all 4 nodes.

This is the off by one error we were looking for earlier. Pull and try again.

it went further but eventually hit my snippet above at about 2M iterations

Where are the backtraces?

/home/bandokihiro/Public/DebugBarrier/vortex/assert_0909

Try running with this patch and report back what happens:
diff --git a/runtime/legion/legion_trace.cc b/runtime/legion/legion_trace.cc
index c167f942a..697a160f7 100644
--- a/runtime/legion/legion_trace.cc
+++ b/runtime/legion/legion_trace.cc
@@ -6939,7 +6939,7 @@ namespace Legion {

     //--------------------------------------------------------------------------
     Instruction::Instruction(PhysicalTemplate& tpl, const TraceLocalID &o)
-      : operations(tpl.operations), events(tpl.events),
+      : tmpl(tpl), operations(tpl.operations), events(tpl.events),
         user_events(tpl.user_events), owner(o)
     //--------------------------------------------------------------------------
     {
@@ -7575,9 +7575,14 @@ namespace Legion {
       assert(rhs < events.size());
       assert(lhs < events.size());
 #endif
+      const ShardedPhysicalTemplate *shard_template =
+        static_cast<const ShardedPhysicalTemplate*>(&tmpl);
+      assert(shard_template->total_replays <= Realm::Barrier::MAX_PHASES);
       Runtime::phase_barrier_arrive(barrier, 1/*count*/, events[rhs]);
       events[lhs] = barrier;
       Runtime::advance_barrier(barrier);
+      if (!barrier.exists())
+        assert(shard_template->total_replays == Realm::Barrier::MAX_PHASES);
     }

     //--------------------------------------------------------------------------
diff --git a/runtime/legion/legion_trace.h b/runtime/legion/legion_trace.h
index 8d3171b6c..9cf720eb0 100644
--- a/runtime/legion/legion_trace.h
+++ b/runtime/legion/legion_trace.h
@@ -1168,10 +1168,11 @@ namespace Legion {
       std::map<unsigned/*Trace Local ID*/,ShardID> owner_shards;
       std::map<unsigned/*Trace Local ID*/,IndexSpace> local_spaces;
       std::map<unsigned/*Trace Local ID*/,ShardingFunction*> sharding_functions;
-    protected:
+    public:
       // Count how many times we've been replayed so we know when we're going
       // to run out of phase barrier generations
       size_t total_replays;
+    protected:
       // Count how many advance instructions we've seen updated for when
       // we need to reset the phase barriers for a new round of generations
       size_t updated_advances;
@@ -1257,6 +1258,7 @@ namespace Legion {
       virtual GPUReduction* as_gpu_reduction(void) { return NULL; }
 #endif
     protected:
+      const PhysicalTemplate &tmpl;
       std::map<TraceLocalID, Memoizable*> &operations;
       std::vector<ApEvent> &events;
       std::map<unsigned,ApUserEvent> &user_events;

after about 2M iterations it hit this
solver: /home/bandokihiro/Public/DebugBarrier/legion/runtime/legion/legion_trace.cc:7585: virtual void Legion::Internal::BarrierArrival::execute(): Assertion `shard_template->total_replays == Realm::Barrier::MAX_PHASES' failed.

without properly freezing despite the following command line
mpirun -n 4 -H n0000,n0001,n0002,n0003 -npernode 1 -bind-to none -x LEGION_FREEZE_ON_ERROR ../DG-Legion/build/exec/solver -logfile logs/log_%.log -hdf5:forcerw -dm:memoize -ll:cpu 1 -ll:util 2 -ll:dma 2 -ll:ocpu 1 -ll:othr 1 -ll:csize 2000 -ll:force_kthreads

1048574

Pull and try again.

Looks fixed, thanks.


Allow to use TypeDoc 0.25.x

The current peer dependency version prevents upgrading to the latest version of TypeDoc 0.25.0
>  npm i

npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving<EMAIL_ADDRESS>npm ERR! Found<EMAIL_ADDRESS>npm ERR! node_modules/typedoc
npm ERR!   dev<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR! node_modules/typedoc-plugin-merge-modules
npm ERR!   dev<EMAIL_ADDRESS>from the root project```

While it's still possible to use the current plugin version with npm i --force or npm i --legacy-peer-deps, it's not that convenient - this PR extends the allowed versions of TypeDoc.

Thanks for your help.
I created a separate branch for this as I also had to fix several unit tests because of changes in the HTML output of TypeDoc in version 0.25.0
Released in 5.1.0 🎉


Allow DocService to inject user-specified scripts into the client and…

… provide an extension point to provide custom HTTP headers.
Many services require authentication using short-lived access tokens. It is not practical to set these using the http header field in the debug form. This change allows users to register custom JavaScript to run and allows them to register a customizer of HTTP headers. For example, a firebase auth user would just add this injected script to have debug requests automatically authenticated with a valid access token
armeria.registerHeaderProvider(function() {
  return firebase.auth().currentUser.getIdToken().then(token => { authorization: 'Bearer ' + token });
});

Thanks, @anuraaga !


DllReferencePlugin cannot consume exposed index.js correctly

Bug report

What is the current behavior?
In ES6, having an index.js file in a folder lets you perform an import from the folder implicitly without specifying the index.js.
DllPlugin correctly adds such files to manifest.json, but when you try to import such module consumed by DllReferencePlugin - it fails with error Cannot find module. You have to append /index.js to the import statement explicitly to workaround this.
If the current behavior is a bug, please provide the steps to reproduce.

Create simple Dll project, having a folder with some module in it, and  index.js within this folder, which should basically reexport the module

// example structure
//--MyModule
//  |_ MyModule.js
//  |_ index.js

// index.js
export { default } from './MyModule';

Next, create another DllReference project, and try to consume the Dll from the step above

// some Dll consumer code
import MyModule from 'Dll/MyModule'; // FAILS

import MyModule from 'Dll/MyModule/index'; // WORKS

What is the expected behavior?
DllReferencePlugin should be able to import such modules correctly if they exist in manifest.json

Other relevant information:
webpack version:  4.28.4
Node.js version: 11.6.0
Operating System: Windows 10

@sokra would you accept the PR created by @mc-zone please?

bump

Still valid

@vankop Should we keep issues for dll? I think we can improve docs and mark it is legacy with recommendations to migrate on module federation

yeah. please migrate to module federatio. thanks.


Add descriptions for queries H-Q

Relates to https://github.com/elastic/elasticsearch-specification/issues/964
Adds Query DSL descriptions for queries H through Q. Descriptions were sourced from https://www.elastic.co/guide/en/elasticsearch/reference/current/query-dsl.html and subpages.

Thanks for the thorough review @jrodewig . I've pushed a change that applies your suggestions.


Unable to compile RTC_INT undefined

There are a lot of mentions of RTC_INT in the code, but it's not defined anywhere. Which gpio is it?
exit status 1
'RTC_INT' was not declared in this scope

  attachInterrupt(RTC_INT, [] {
      rtcIrq = 1;
      BaseType_t xHigherPriorityTaskWoken = pdFALSE;
      EventBits_t  bits = xEventGroupGetBitsFromISR(isr_group);
      if (bits & WATCH_FLAG_SLEEP_MODE)
      {
	  //! For quick wake up, use the group flag
	  xEventGroupSetBitsFromISR(isr_group, WATCH_FLAG_SLEEP_EXIT | WATCH_FLAG_AXP_IRQ, &xHigherPriorityTaskWoken);
      } else
      {
	  uint8_t data = Q_EVENT_AXP_INT;
	  xQueueSendFromISR(g_event_queue_handle, &data, &xHigherPriorityTaskWoken);
      }
      if (xHigherPriorityTaskWoken)
      {
	  portYIELD_FROM_ISR ();
      }
  }, FALLING);```

It's defined in libraries/TTGO_TWatch_Library-master/src/board/twatch2020_v1.h as pin 37.
You must always include "config.h".  That pulls in LilyGoWatch.h.  That pulls in the above file that defines RTC_INT.
A suggestion: if you develop on Linux or Mac, learn to use this command:
find ~/Arduino -type f -print0 | xargs -0 grep RTC_INT
So you can find where something is defined.  I spent hours
with that command trying to figure out how to wake the watch
using the rtc alarm function.


July Release Prep - Confidential Ledger

Contributing to the Azure SDK
Please see our CONTRIBUTING.md if you are not familiar with contributing to this repository or have questions.
For specific information about pull request etiquette and best practices, see this section.

API change check
API changes are not detected in this pull request.


Providing BM25 top-100 for all datasets

First of all, thanks for this amazing benchmark. I'd like to evaluate a re-ranking model on several datasets. If I got I correctly, I will have to download and index all datasets independently to get the top-100 BM25 rank lists. Could you please provide those for each dataset for easier evaluation?
Thanks a lot!

I would echo this request since I cannot reproduce the BM25 (Elasticsearch, default setting) results on certain datasets, particularly the ones with fewer docs like NFCorpus and SciFact.
Besides, I found that the scores may change a bit in different runs. Is there any randomness inside Elasticsearch? Maybe @thakur-nandan can provide some insights? Thanks!


Fix stack overflow with large number of item includes for the same item list

Use loops and explicit stacks to traverse the linked list of previous operations instead of recursion.

I continue to find this implementation confusing, but this is an improvement over the old version. :shipit:

:shipit:

@dotnet-bot test Windows_NT Build for CoreCLR please

:shipit:

Thanks!


Expired link to saved_models

Hello,
I want to reproduce your results but the link under saved_models is expired. Is it still available in any other ways?
Thank you!

Hi,
Do you mean this link? I just tried it and it still works.


Remove crio-status binary

What type of PR is this?
/kind deprecation
What this PR does / why we need it:
The binary is already deprecated so we do not have to ship it in v1.28 and beyond.
Which issue(s) this PR fixes:

None
Special notes for your reviewer:
Refers also to https://github.com/cri-o/cri-o/pull/7440
Does this PR introduce a user-facing change?

Removed `crio-status` binary in favor of the `crio status` subcommand.

/lgtm


Change Merged entry icon

Describe your suggested feature
Please add a better icon for the Merged library entries
Other details
No response
Acknowledgements

[X] I have searched the existing issues and this is a new ticket, NOT a duplicate or related to another open or closed issue.
[X] I have written a short but informative title.
[X] If this is an issue with an official extension, I should be opening an issue in the extensions repository.
[X] I have updated the app to version 1.11.2.
[X] I will fill out all of the requested information in this form.

Can you propose some design? This issue is arguable and ambigue

Can you propose some design? This issue is arguable and ambigue

I can't propose any design, but I don't want something extravagant or anything like that
I just don't really like the hand drawn M with the strange line in the middle

I saw that someone had some ideas about the icon and they were pretty cool (half of each icon or an animation that goes between the icon of both sources)

I saw that someone had some ideas about the icon and they were pretty cool (half of each icon or an animation that goes between the icon of both sources)

those were my ideas lmao
I have another one: why not use the little merge icon that appears in the manga entries?


For the Inline payload format, changing the Media Type does not update the placeholder in the payload field.

Description:
In Payload Factory mediator when the Payload Format is set to Inline, users can enter the payload directly. By default, the placeholder in the payload field displays a sample JSON object. However, when the Media Type is changed, the placeholder should update to reflect the appropriate format for the selected media type. Currently, the placeholder does not change accordingly.
Steps to reproduce:
Affected Versions:
v1.0.3
OS, DB, other environment details and versions:
Related Issues (optional):

Suggested Labels (optional):

Suggested Assignees (optional):

The latest release v1.0.5 has resolved the issue. Please reopen if the problem persists.


Add Markdown linting GHA, fix errors

Add markdownlint GitHub Action.
Remove old docs that are out of date and better covered in the main
website docs.
Fix errors flagged in remaining docs.
Signed-off-by: Daniel Farrell<EMAIL_ADDRESS>

This was merged as a part of submariner-io/submariner-operator#617 (by accident from my side). It works out well though, good to have the fixes in and a test keeping new errors out while we wait on the other repos to get fixed and #272 to add MD linting to the normal verify job. Once that's done, we can remove the GHA here.


Create Rachit.py

Problem
-On hover Box-Item grows in size now
Solution
-transform property added to box-item on hover
Changes proposed in this Pull Request :

1.transform property added to box-item on hover
2.on hover color of the contributors name changes to navy
..

Other changes

Hello Am rachit this is a little program and
i hope its help for kids to do it.'''


regenerateDeviceId is not importable

Expected Behavior

regenerateDeviceId should be importable, as it needs to be called on user sign-out event
Current Behavior

regenerateDeviceId is not importable, it is declared in AmplitudeBrowser class
https://github.com/amplitude/Amplitude-TypeScript/blob/d335f6231d6a0bd487824f0ba1dbb92b50793c94/packages/analytics-browser/src/browser-client.ts#L95-L98
but not being exported in index.ts
https://github.com/amplitude/Amplitude-TypeScript/blob/d335f6231d6a0bd487824f0ba1dbb92b50793c94/packages/analytics-browser/src/index.ts#L1-L20

So right now I don't have a way to sign users out :(
Possible Solution

Add regenerateDeviceId to exported members of index.ts
Steps to Reproduce

Environment

JS SDK Version:
Installation Method:
Browser and Version:

Hi @kykungz,
We are improving the experience of regenerating the deviceId.  We will have another method called reset, which will reset the userId and deviceId. It's in progress, and will come soon.
We will let you know when that comes out.
Thanks.

@yuhao900914 Thanks, do you have any other solution that I can use when reset is not yet available? Or should I revert back to amplitude-js instead.

@yuhao900914 @liuyang1520 Just saw that https://github.com/amplitude/Amplitude-TypeScript/pull/157 was just merged and released an hour ago, that's fast! Thanks a lot!


Missing ifdefs for UserConsentedAll?

Library/PackageCache/com.binouze.googleusermessagingplatform@3367dccb33/Runtime/GoogleUserMessagingPlatform.cs(386,22): error CS0103: The name '_GetConsentForExternal' does not exist in the current context

It seems project won't compile for non-iOS target.

sorry just updated it, it should work now


ADBDEV-6593: Fix vacuum_progress isolation tests

Fix vacuum_progress isolation tests
Isolation tests vacuum_progress_column and vacuum_progress_row would
previously fail sometimes because vacuum_worker_changed fault injector was
never reached. This happened because vacuum execution and FTS version upgrade
are not synchronized: after FTS disables syncrep according to the test, it
should bump FTS version, which should be detected by the dispatcher on the
next StartTransaction call, and then the segment backends will be restarted
(making vacuum_worker_changed fault accessible). However, if FTS is too slow
(or dispatcher too fast), it might skip StartTransaction calls before FTS
version is bumped, and the segment restart will happen after vacuum is
complete, without triggering vacuum_worker_changed. This is an acceptable
behavior for the code since the restart still happens milliseconds after
disabling syncrep, but the test doesn't expect it.
This patch fixes the test by making the dispatcher wait on
vacuum_rel_finished_one_relation fault until waits until mirror down is
detected by FTS, ensuring FTS version bump happens before dispatcher proceeds.
Note that the patch also changes expected output: it seems like previously
restart happened on the last StartTransaction, making all the collected
stats to be zero. However, post-cleanup vacuum phase (which is executed after
vacuum_worker_changed) is also responsible for vacuuming the indexes, so the
correct output should include those too. Note that num_dead_tuples value is
still zero, indicating that vacrelstats was indeed reset correctly.

Could you elaborate a bit more on " This is an acceptable
behavior for the code since the restart still happens milliseconds after
disabling syncrep, but the test doesn't expect it." ?
Why is it acceptable in production and what exactly will happen with DB in prod in this case?

Could you also explain some more in " it might skip StartTransaction calls before FTS
version is bumped" ? Who exactly might skip StartTransaction? What will be consequences?

Why is it acceptable in production and what exactly will happen with DB in prod in this case?

As far as I know, nothing. Syncrep is disabled when it is detected that mirror is down, so the segment's backend can proceed for a bit before it is restarted, with syncrep turned off. Since mirror being down shouldn't affect the behavior of the segment, if it manages to complete any transactions in that time they should still be correct, so it's acceptable for the restart to happen a bit later.

Who exactly might skip StartTransaction? What will be consequences?

The dispatcher checks whether the segments should be restarted inside StartTransaction calls. If the dispatcher proceeds through StartTransaction before FTS version is bumped, it will only detect the bump on the next StartTransaction. I think there won't be any consequences since the mirror could have been turned off during that next transaction as well, with the same observable behavior for the dispatcher. Lack of synchronization only changes the moment when mirror becomes down as observed by the dispatcher, so it shouldn't affect the resulting behavior.

A new flaky test?

Seems so, created a ticket for it


Isonet support NVIDIA A100

Dear Author，
First thanks a lot for this powerful software !
I have a question: Is IsoNet support CUDA 11.2 and NVIDIA A100 with tensorflow-gpu_2.7?
I install isonet with conda python3.9 and tensorflow-gpu_2.7+cuda11.2+NVIDIA A100 get this error:
(py39) [root@Isonet]$ isonet.py refine subtomo.star --gpuID 0,1,2,3 --iterations 30 --noise_start_iter 10,15,20,25 --noise_level 0.05,0.1,0.15,0.2
04-16 22:14:09, INFO
######Isonet starts refining######
04-16 22:14:27, INFO     Note: detected 128 virtual cores but NumExpr set to maximum of 64, check "NUMEXPR_MAX_THREADS" environment variable.
04-16 22:14:27, INFO     Note: NumExpr detected 128 cores but "NUMEXPR_MAX_THREADS" not set, so enforcing safe limit of 8.
04-16 22:14:27, INFO     NumExpr defaulting to 8 threads.
04-16 22:14:30, WARNING  The results folder already exists before the 1st iteration
The old results folder will be renamed (to results~)
04-16 22:14:50, INFO     Done preperation for the first iteration!
04-16 22:14:50, INFO     Start Iteration1!
/data1/apps/miniconda3/envs/py39/lib/python3.9/site-packages/keras/optimizer_v2/adam.py:105: UserWarning: The lr argument is deprecated, use learning_rate instead.
super(Adam, self).init(name, **kwargs)
/data1/apps/miniconda3/envs/py39/lib/python3.9/site-packages/keras/engine/functional.py:1410: CustomMaskWarning: Custom mask layers require a config and must override get_config. When loading, the custom mask layer must be passed to the custom_objects argument.
layer_config = serialize_layer_fn(layer)
04-16 22:14:54, INFO     Noise Level:0.0
2022-04-16 22:15:06.826516: F tensorflow/stream_executor/cuda/cuda_driver.cc:153] Failed setting context: CUDA_ERROR_NOT_INITIALIZED: initialization error
Thanks a lot!

Hi,
We only tested tensorflow2.5. and python3.6 on A100 GPUs. IsoNet works fine with A100.
Could you run the command with parameter: "--log_level debug" and see what is the error message?

Hi,
We only tested tensorflow2.5. and python3.6 on A100 GPUs. IsoNet works fine with A100.
Could you run the command with parameter: "--log_level debug" and see what is the error message?

Dear procyontao,
Thanks a lot!
And could you tell me which cuda version and which NVIDIA A100 driver did you use?

I sloved the problem.
Thanks procyontao!
I use python 3.8 with miniconda
and install:
pip install imageio==2.10.5 numpy==1.19.2
then install
pip install tensorflow-gpu==2.5.0
pip install -r requirements.txt
And Isonet run successfully.

Hi all,
I also required TensorFlow v2.6.0 to run IsoNet properly on A100 GPUs.
I figured it would be nice to provide some GPU benchmarks for the tutorial dataset
I used TF2.6.0 Cuda11.6 IsoNet0.1 on the three tutorial tomograms
System  Time/step  speedup
2x 2070S 950ms  1
4x2080TI 700ms ~1.4
4x1080TI 900ms ~1
1xRTX8000 1000ms ~1
2xRTX8000 700ms ~1.3
4xA100 480ms ~2
Cheers

Hi proteincommandr,
Thank you for providing the GPU benchmarks. We do not even afford that many types of GPU for a speed test.
One question, did you consider the differences in batch_size (i.e. number of subtomograms processed in one step)?
the default relation between number of GPUs and default batch_size is listed below:
nGPUs batch_size
1 4
2 4
3 6
4 8
5 10
6 12
7 14
8 16
If you do not specify the batch size in your command, your list should be:
System Time/step speedup batch_size speedup_persubtomo
2x 2070S 950ms 1 4 0.5
4x2080TI 700ms ~1.4 8 1.4
4x1080TI 900ms ~1 8 1
1xRTX8000 1000ms ~1 4 0.5
2xRTX8000 700ms ~1.3 4 0.65
4xA100 270ms ~3.5 8 3.5


Create a  page with video slides  per topic

Now that we are getting more and more video slides, it would be nice to have a page per topics showing all the videos, instead of a single huge page.
Also added a TOC for because some topics (such as admin) have a lot of video slides

ping @hexylena

Not so many change for ecology ;) But really nice feature !!

yeahh, sorry for the spam, I had to touch every topic for this :P

Not so many change for ecology ;) But really nice feature !!

yeahh, sorry for the spam, I had to touch every topic for this :P


Is it possible to send article link in notification?

Hi, I'm using newsboat to monitor a (filtered) feed and I receive a notification on Telegram when the feed contains a certain keyword.
Is it possible to include a direct link to the article in the notification? Now I just include a text containing the address of the website.
Thanks!

Hi! Newsboat notifications report aggregate values like total number of new articles — guess it's not obvious if you only have a single, rarely updated feed, so each notification effectively corresponds to a single article. I understand this is a pretty limited interface; perhaps https://github.com/newsboat/newsboat/issues/1155 could extend it sufficiently that your use-case becomes possible.
Overall, I get a feeling that Newsboat is not the right tool for the job: Newsboat is geared towards being used by a person rather than being a part of some automated process. If I were you, I'd use rsstail or wrote a Python script with feedparser library.
I don't think there's anything to do about this issue for us, so I'm closing this.

Hi! Newsboat notifications report aggregate values like total number of new articles — guess it's not obvious if you only have a single, rarely updated feed, so each notification effectively corresponds to a single article. I understand this is a pretty limited interface; perhaps https://github.com/newsboat/newsboat/issues/1155 could extend it sufficiently that your use-case becomes possible.
Overall, I get a feeling that Newsboat is not the right tool for the job: Newsboat is geared towards being used by a person rather than being a part of some automated process. If I were you, I'd use rsstail or wrote a Python script with feedparser library.
I don't think there's anything to do about this issue for us, so I'm closing this.


[BUG]? Installer fails, fresh installation on latest PI that has not had allsky previously.

Environment

Camera:  ZWO  or  RPi - include the model ZWO 178MC
OS:  Bullseye
Allsky version: v2023.05.01_03

The newest software includes a file called  ~/allsky/version
If it does not exist, run:       grep Software /var/log/allsky.log

Pi model and amount of memory: Rpi 4B 8GB

Bug Description
Fresh git clone today (v2023.05.01_03) on a Pi that previously did not have allsky installed.
This is my backup PI I use for testing with the latest Bullseye installed.
The installer fails at saving the camera settings.

Log / configuration files

allsky.log

@Jonk2   Jon,
Long time no talk.  Hope you're doing well!
Would you please attach ~/allsky/config/installation_logs/install.sh.log ?  It will give me a better idea of why it couldn't save the capabilities.
Did you install the raspistill package, or did it come on Bullseye?
Also, would you please rename "allsky" to "allsky-SAVED", then do another git, then in the new allsky/install.sh, remove the echo on lines 375 and 376, and try the installation again?  The two white lines in the screenshot near the top should have been executed but I forgot to remove the "echo" so they were displayed instead.  It's possible that's what caused the problem.

@Jonk2, Jon,
Just remove the word echo from the lines so the commands are executed.  echo simply outputs whatever else is on the command line.  It doesn't execute anything.  I'm pretty sure I had it like that for testing and forgot to fix it.
Thanks.

@EricClaeys
Raspistill in the /usr/bin folder has a date of 22/03/23 which is when I installed a fresh OS, so it wasn't me manually.
The installation log from the attempt yesterday is attached which will tell you where the issue is.
You will also notice that lighttpd installation failed - I have a weird issue with this PI, upon booting it up, sometimes it grinds to a halt after a couple of minutes, then sorts itself out. I moved the PI back outside, booted it and started a fresh allsky clone - this is probably why it failed, just bad timing.
It worked on the 2nd attempt though. I think I tried to install allsky 2 or 3 more times last night before posting here, just to make sure.
Using analyze-blame, I can sometimes see up to 3 minutes have elapsed sometimes after a reboot, I have no idea why (possible DNS checking issue I've read) but I digress...
I've re-cloned into a fresh folder and removed echo from the 2 lines mentioned above:

Upon running the new install script...

The same error appears in the new installation log as the one aattached, i.e.
Unable to create '/home/pi/allsky/config/options.json' and '/home/pi/allsky/config/settings.json' files. , RET=255: Fatal error: Uncaught Error: Call to undefined function json_decode() in /home/pi/allsky/html/includes/functions.php:56 Stack trace: #0 /home/pi/allsky/html/includes/createAllskyOptions.php(291): get_decoded_json_file('/home/pi/allsky...', true, 'ERROR: Unable t...') #1 {main}   thrown in /home/pi/allsky/html/includes/functions.php on line 56
Let me know what you want me to try next and I'll get on it.
install.sh.log

Would you please attach /home/pi/allsky/config/installation_logs/lighttpd.install.log ?  It should say why lighttpd installation failed.  I'm pretty sure that's why you are getting the undefined function json_decode() error - that function wasn't installed because lighttpd installation failed.

Did you exit the first installation while lighttpd was being installed?  Another installation started after the first "Installing the web server" message, and that's where the lighttpd installation failed.
* STARTING INSTALLATON AT Wed 13 Sep 20:59:51 BST 2023.

* No prior Allsky found.
* ZWO camera found.
* Using the 'master' branch.
* Displaying notification image 'InstallationInProgress.jpg'
* CURRENT_LOCALE=en_GB.UTF-8, TEMP_LOCALE=[[LANG=en_GB.UTF-8 ]]
* Using ZWO camera.
* Using current hostname of 'RORPI'.
* RAM_SIZE=8192, SUGGESTED_SWAP_SIZE=0.
* Size of current swap (2048 MB) is sufficient; no change needed.
* /home/pi/allsky/tmp is now in memory.
* Installing the web server.
* STARTING INSTALLATON AT Wed 13 Sep 21:17:50 BST 2023.

* No prior Allsky found.
* ZWO camera found.
...
* Installing the web server.
*** ERROR:
**********
lighttpd installation failed
**********

* The full log file is in /home/pi/allsky/config/installation_logs/lighttpd.install.log
The end of the file is:
* Displaying notification image 'InstallationFailed.jpg'

* ENDING INSTALLATON AT Wed 13 Sep 21:18:00 BST 2023.

Did you exit the first installation while lighttpd was being installed? Another installation started after the first "Installing the web server" message, and that's where the lighttpd installation failed.

No, I restarted or rather retried install.sh straight after it failed, that was it. It did work the 2nd or 3rd time (so it says in the install log? )....I mention the PI booting delay above which may or may not be the issue.
When I reboot it, sometimes even an ftp transfer fails after 20s or so, I have to wait a few minutes for it to work so that's another reason to suspect that. That isn't an allsky issue, I guess I just have to wait a few minutes after a reboot before I do anything manually.
The lighttpd install log is attached. It appears to confirm it is installed correctly.
lighttpd.install.log

Ok, canceling the installation during lighttpd installation explains why the second installation started.  Unfortunately because you tried again and it successfully installed lighttpd, the log file only shows the successfull attempt so I don't know why it failed the 2nd time.
I should change the installation so it APPENDS to the log files instead of truncating them.
I have never had to wait after a reboot, but I can understand why that could happen.  Luckily you shouldn't need to reboot often.
Is everything working now?

I've deleted the previous allsky folder and re-cloned.
Ran the installation script, and the same error occurs:

install.sh.log

I suspect that the initial install of lighttpd failed and was never fully fixed in subsequent installs, so let's try to uninstall it and start over.
Would you please run the following:
sudo systemctl stop hostapd
sudo systemctl stop lighttpd
sudo apt-get --assume-yes purge lighttpd php-cgi php-gd hostapd dnsmasq avahi-daemon
cd ~/allsky
mv  config  config-SAVED
./install.sh

This will remove the web-related packages and then run the installation again.  If you previously spent time updating your settings, you can simply copy the config-SAVED/setting.json to config after the installation completes.
If there are any problems, please attach ~/allsky/config/installation_logs/install.sh.log and any log files for packages that fail (the log file name will be in the error message).  Do not re-run the installation or do anything else.
Thanks - Eric

@EricClaeys followed your instructions, unfortunately with the same result.
Here's a copy n paste of the console, the log is attached. It looks to be the same error.
**Linux RORPI 6.1.21-v8+ #1642 SMP PREEMPT Mon Apr  3 17:24:16 BST 2023 aarch64
The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.
Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
Last login: Sun Sep 17 21:39:15 2023 from <IP_ADDRESS>
Wi-Fi is currently blocked by rfkill.
Use raspi-config to set the country before use.
pi@RORPI:~ $ sudo systemctl stop hostapd
pi@RORPI:~ $ sudo systemctl stop lighttpd
pi@RORPI:~ $ sudo apt-get --assume-yes purge lighttpd php-cgi php-gd hostapd dnsmasq avahi-daemon
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following packages were automatically installed and are no longer required:
bind9-host bind9-libs libavahi-core7 libdaemon0 libfstrm0 libmaxminddb0 libprotobuf-c1
libuv1 php-common php7.4-cgi php7.4-cli php7.4-common php7.4-gd php7.4-json
php7.4-opcache php7.4-readline spawn-fcgi
Use 'sudo apt autoremove' to remove them.
The following packages will be REMOVED:
avahi-daemon* dnsmasq* hostapd* ipp-usb* libnss-mdns* lighttpd* lighttpd-mod-deflate*
lighttpd-mod-openssl* php-cgi* php-gd*
0 upgraded, 0 newly installed, 10 to remove and 0 not upgraded.
After this operation, 8,167 kB disk space will be freed.
(Reading database ... 111826 files and directories currently installed.)
Removing libnss-mdns:armhf (0.14.1-2) ...
Removing ipp-usb (0.9.17-3) ...
Removing avahi-daemon (0.8-5+deb11u2) ...
Created symlink /run/systemd/system/avahi-daemon.service → /dev/null.
Removed /run/systemd/system/avahi-daemon.service.
Removing dnsmasq (2.85-1) ...
Removing hostapd (2:2.9.0-21) ...
Removing lighttpd-mod-openssl (1.4.59-1+deb11u2) ...
Removing lighttpd-mod-deflate (1.4.59-1+deb11u2) ...
Removing lighttpd (1.4.59-1+deb11u2) ...
Removing php-cgi (2:7.4+76) ...
update-alternatives: using /usr/bin/php-cgi7.4 to provide /usr/bin/php-cgi (php-cgi) in auto mode
update-alternatives: using /usr/lib/cgi-bin/php7.4 to provide /usr/lib/cgi-bin/php (php-cgi-bin) in auto mode
Removing php-gd (2:7.4+76) ...
Processing triggers for man-db (2.9.4-2) ...
Processing triggers for dbus (1.12.24-0+deb11u1) ...
Processing triggers for libc-bin (2.31-13+rpt2+rpi1+deb11u5) ...
(Reading database ... 111646 files and directories currently installed.)
Purging configuration files for lighttpd (1.4.59-1+deb11u2) ...
removing dangling symlink /etc/lighttpd/conf-enabled/10-fastcgi.conf ...
removing dangling symlink /etc/lighttpd/conf-enabled/15-fastcgi-php.conf ...
dpkg: warning: while removing lighttpd, directory '/etc/lighttpd/conf-enabled' not empty so not removed
Purging configuration files for ipp-usb (0.9.17-3) ...
Purging configuration files for lighttpd-mod-openssl (1.4.59-1+deb11u2) ...
Purging configuration files for dnsmasq (2.85-1) ...
dpkg: warning: while removing dnsmasq, directory '/usr/lib/resolvconf' not empty so not removed
Purging configuration files for hostapd (2:2.9.0-21) ...
Removed /etc/systemd/system/hostapd.service.
Purging configuration files for avahi-daemon (0.8-5+deb11u2) ...
rmdir: failed to remove '/run/avahi-daemon': Directory not empty
Purging configuration files for libnss-mdns:armhf (0.14.1-2) ...
libnss-mdns.postrm: Checking NSS setup...
libnss-mdns.postrm: Removing mdns from NSS setup
Purging configuration files for lighttpd-mod-deflate (1.4.59-1+deb11u2) ...
Processing triggers for dbus (1.12.24-0+deb11u1) ...
pi@RORPI:~ $ cd ~/allsky
pi@RORPI:~/allsky $ mv  config  config-SAVED
pi@RORPI:~/allsky $ ./install.sh

*** Welcome to the Allsky Installer! ***

ZWO camera found.
Using ZWO camera.
Size of current swap (2048 MB) is sufficient; no change needed.
/home/pi/allsky/tmp is currently a memory filesystem; no change needed.

*** NOTICE:

The following steps can take up to an hour depending on the speed of your Pi
and how many of the necessary dependencies are already installed.
You will see progress messages throughout the process.
At the end you will be prompted again for additional steps.

Installing the web server.
Installing dependencies.
Preparing Allsky commands.
Modifying locations for WebUI.
Setting up WebUI options and default settings for ZWO cameras.
Making new settings file '/home/pi/allsky/config/settings.json'.

*** ERROR:

Unable to save camera capabilities.

pi@RORPI:~/allsky $**
install.sh.log

@EricClaeys
Short of a full os reinstall (which doesn't help anyone figure this out) is there anything else you can suggest I try?
This PI is running in cli mode only and only running 1 python script reading and recording an i2c sensor. Nothing else.

@Alex-developer, do you have any ideas?  The error message is:
Fatal error: Uncaught Error: Call to undefined function json_decode() in /home/pi/allsky/html/includes/functions.php:56

@Jonk2 interrupted the initial installation as it was installing the web server (which includes php), so I'm assuming php wasn't completely installed, but says it is.  Hence php scripts can't find json_decode().
Jon said he executed what I suggested:
sudo apt-get --assume-yes purge lighttpd php-cgi php-gd hostapd dnsmasq avahi-daemon

but it didn't help.

@EricClaeys @Alex-developer
Gents, I appreciate this is maybe a specific issue to me, rather than Allsky, but is there anything else to try before I wipe this PI and start again? Wiping isn't really an issue, but if there is a bug somewhere with the installer, perhaps I should wait to see if it can be found?

atal error: Uncaught Error: Call to undefined function json_decode()

Sorry missed this. Sounds like the php-json package is missing. You could try installing that.
apt install -y php-json

@Jonk2, if what @Alex-developer suggested doesn't work and you decide to re-image, please save the config/installation_logs directory first in case we need to refer to it.  I still think it's likely that something related to php or json didn't get fully installed when you aborted the installation the first time, but it's reporting as installed.

@EricClaeys The installer failed the first time with no previous allsky installed on a fairly fresh os (March this year I think). I tried again, same result which is why I raised it here.
@Alex-developer I followed your suggestion with the following result:

However the allsky installation script still fails with the same error message, even after a reboot.
So, I’ve saved the config/installation_logs folder in case anyone needs it and will write a fresh os using the pi installer as usual.
Then, hopefully it’ll work!

Hi the above issue of installation error with "Unable to save camera capabilities" seems to be still occurring.  I have new Raspberry PI 5 (Operating System: Debian GNU/Linux 12 (bookworm); Kernel: Linux 6.6.31+rpt-rpi-2712; Architecture: arm64) and Arducam Imx519 and Arducam Owlsight pi cameras and encountered similar issue.  my log file below

STARTING INSTALLATON AT Fri Aug 16 11:25:44 PM PDT 2024.

No prior Allsky found.

RPi camera found.

Using the 'master' branch.

Displaying notification image 'InstallationInProgress.jpg'

CURRENT_LOCALE=en_US.UTF-8, TEMP_LOCALE=[[LANG=en_US.UTF-8 LANGUAGE=en_US.UTF-8 LC_ALL=en_US.UTF-8 ]]

Using RPi camera.

Using current hostname of 'gsnballskycam'.

RAM_SIZE=8192, SUGGESTED_SWAP_SIZE=0.

Size of current swap (200 MB) is sufficient; no change needed.

/home/sreegsnb/allsky/tmp is currently a memory filesystem; no change needed.

/home/sreegsnb/allsky/tmp already mounted.

Installing the web server.

Installing dependencies.

Preparing Allsky commands.

Modifying locations for WebUI.

Setting up WebUI options and default settings for RPi cameras.

Making new settings file '/home/sreegsnb/allsky/config/settings.json'.

Executing makeChanges.sh --force --cameraTypeOnly   'cameraType' 'Camera Type' '' 'RPi'

ERROR: Segmentation fault in capture_RPi -cmd libcamera-still
*** ERROR:

Unable to save camera capabilities.

Displaying notification image 'InstallationFailed.jpg'

ENDING INSTALLATON AT Fri Aug 16 11:26:12 PM PDT 2024.

Please advise

Just FYI.. issue resolved.  Arducam Owlsight camera was the issue, removed the camera and reinstalled all worked fine on Raspberry Pi 5.
Note for anyone trying to use RPi HQ camera or Arducam cameras with Raspberry Pi 5, please invest in new CSI cables (22pin to 15pin) or new 15pin cable, the stock cables that come with camera are not reliable and can cause "no camera available" errors.
Thanks


Deconstruct/construct command?

Worth trying to  deconstruct/construct  command?
The implementation will use build/unbuild enigma mixins

wrong repo


PP-1500 ePDQ - notification parsing and sha signature verification

WHAT
ePDQ - notification parsing and sha signature verification
Still to do:

implement StatusMapper logic
create notification resource
manual testing on actual notifications

with @alexbishop1
with @ckalista

General comment before I review code: I think it would be good to explain your approach in more detail in the commit message and PR. For example I know from having discussed with you that you had to make decisions about how to make the payload available for verification of the signature, and I think it would be good to explain that to posterity.

Hi Dom,
that's a good comment.
Sorry I did not do it - probably I thought this was a "temporary" PR, just
for an initial review, and planning to finalise it once the StatusMapper
bit was added.
However, as you are hinting, I think it is better to finalise this one and
open another PR for the StatusMapper.
I am going to add the PR description now.
Thanks,
Daniele
On 5 June 2017 at 10:26, Dominic Jones<EMAIL_ADDRESS>wrote:

General comment before I review code: I think it would be good to explain
your approach in more detail in the commit message and PR. For example I
know from having discussed with you that you had to make decisions about
how to make the payload available for verification of the signature, and I
think it would be good to explain that to posterity.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/alphagov/pay-connector/pull/395#issuecomment-306143958,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AVx5Q14bJiUHwrUhy2s_37SheywbkPg2ks5sA8nTgaJpZM4NufPf
.

--
Daniele Occhipinti
Developer
Government Digital Services - GOV.UK Pay
E<EMAIL_ADDRESS>T: 07767 272 950

Cool, no worries

Dom, description has been added. Thanks.
On 5 June 2017 at 10:39, Dominic Jones<EMAIL_ADDRESS>wrote:

Cool, no worries
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/alphagov/pay-connector/pull/395#issuecomment-306146365,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AVx5Q6kYuYA9bjT9hTDv4hnsYDKyzyCNks5sA8zCgaJpZM4NufPf
.

--
Daniele Occhipinti
Developer
Government Digital Services - GOV.UK Pay
E<EMAIL_ADDRESS>T: 07767 272 950

Let me know if you're gonna make any of the more disputable changes above, and I'll go over again and approve (probably)