fix network_mode is incompatible with port_bindings Error

Solved bug #243 by removing port: 5000:5000 because it create conflict with network_mode:host in docker-compose-host.yml file.
Reference: https://forums.docker.com/t/docker-errors-invalidargument-host-network-mode-is-incompatible-with-port-bindings/103492

@itsdivyanshjain I get what you mean.
@Ali-Razmjoo @dhirensr Do we need to have version numbers there? If it is not necessary, then the list file can be just the list of required packages without the version number.

Yes, even I am thinking of to get rid of version number in requirements-apt-get.txt

@Ali-Razmjoo
we can do that also, but I think we can just remove the version number from requirements-apt-get file because whenever we/user need to add any apt package we can just edit requirements-apt-get file. Due to that it doesn't going to affect our code quality too.

I am not sure if we remove the version we are going to face another issue once they get updated to latest... for now I'd like to fix the version to pass the CI and solve that issue in another PR/decision making process.

and thank you guys for contributions, tests and reports.


CF - Allow multiple cfn-lint API versions

Fixes #3411

Coverage decreased (-0.3%) to 94.171% when pulling b3ae6a0f12ba86fe40d5d5dae0d75d01e126db39 on bblommers:bugfix/3411 into 14980371d796ef849b1ea401ce2c028911b537d1 on spulec:master.

Thanks for fixing this!


Question: run-android error, Unable to resolve module ./index

After rm -rf node_modules && npm i, the problem remains the same:
Looking for JS files in
D:\Projects\Temp\TestApp\node_modules\react-native\scripts
Loading dependency graph, done.
Error: Unable to resolve module ./index from D:\Projects\Temp\TestApp\node_mo dules\react-native\scripts/.: The module ./index could not be found from D:\ Projects\Temp\TestApp\node_modules\react-native\scripts/.. Indeed, none of thes
e files exist:

D:\Projects\Temp\TestApp\node_modules\react-native\scripts\index(.native||. android.js|.native.js|.js|.android.json|.native.json|.json|.android.ts|.native.t s|.ts|.android.tsx|.native.tsx|.tsx)
D:\Projects\Temp\TestApp\node_modules\react-native\scripts\index\index(.nat ive||.android.js|.native.js|.js|.android.json|.native.json|.json|.android.ts|.na tive.ts|.ts|.android.tsx|.native.tsx|.tsx)
at ModuleResolver.resolveDependency (D:\Projects\Temp\TestApp\node_modules\m
etro\src\node-haste\DependencyGraph\ModuleResolution.js:163:15)
at ResolutionRequest.resolveDependency (D:\Projects\Temp\TestApp\node_module
s\metro\src\node-haste\DependencyGraph\ResolutionRequest.js:52:18)
at DependencyGraph.resolveDependency (D:\Projects\Temp\TestApp\node_modules
metro\src\node-haste\DependencyGraph.js:283:16)
at D:\Projects\Temp\TestApp\node_modules\metro\src\lib\transformHelpers.js:2
61:42
at Server. (D:\Projects\Temp\TestApp\node_modules\metro\src\Serve
r.js:1038:41)
at Generator.next ()
at asyncGeneratorStep (D:\Projects\Temp\TestApp\node_modules\metro\src\Serve
r.js:99:24)
at _next (D:\Projects\Temp\TestApp\node_modules\metro\src\Server.js:119:9)
::ffff:<IP_ADDRESS> - - [23/Mar/2019:15:19:02 +0000] "GET /index.delta?platform=and
roid&dev=true&minify=false HTTP/1.1" 500 - "-" "okhttp/3.12.1"

package.json:
{
"name": "TestApp",
"version": "0.0.1",
"private": true,
"scripts": {
"start": "node node_modules/react-native/local-cli/cli.js start",
"test": "jest",
"lint": "eslint ."
},
"dependencies": {
"react": "16.8.3",
"react-native": "0.59.1"
},
"devDependencies": {
"@babel/core": "^7.4.0",
"@babel/runtime": "^7.4.2",
"@react-native-community/eslint-config": "^0.0.3",
"babel-jest": "^24.5.0",
"eslint": "^5.15.3",
"jest": "^24.5.0",
"metro-react-native-babel-preset": "^0.53.1",
"react-test-renderer": "16.8.3"
},
"jest": {
"preset": "react-native"
}
}

I'm getting this same error for react-native run-ios on a Mac.  It's a brand new, empty project, just created with the latest react-native cli (i.e. not expo).
But the index.js file is there in the root of the project, right where it should be.
I don't know why the react-native-bot has closed this as "a question".  It's quite obviously an error report.


Hotwords runtime is slow

Hi, thanks for the project!
I'm decoding on top of NeMo model with and without variable amount of hotwords and get the following runtime:

No hotwords: 2 sec
100 hotwords: 23 sec
200 hotwords: 45 sec

Is there a plan on improve this amazing feature run-time using trie or any other solution?

Are you using LM as well during decoding? @nirraviv

@yashjogi yes


added -> operator to unique_wdf_object_reference

I'm not quite sure I see the utility of adding this. Overloading -> makes sense when what is returned is itself a pointer, so that you can apply indirection on it to access its fields/methods. But in this case, what is returned is a WDF object type like WDFREQUEST, which doesn't have any fields/methods. Can you please exemplify the use-case with some sample code?
Note that this is also the reason why unique_any also does not have an overloaded ->. unique_any is meant for "handle" types, not pointer types.

this is what I'd like to do:
wil::unique_wdf_object_reference<PDRIVER_OBJECT> device;
IoGetDeviceObjectPointer(&name, FILE_WRITE_DATA, &file_object, &device);
irp = IoAllocateIrp(device->StackSize, FALSE);

oops, sorry I screwed up.


Doesn't beacon a BITS Telemetry Formatter

Aprx periodically beacons PARM, UNIT, and EQNS Telemetry Report Formatters such that traffic telemetry may be rendered correctly. The BITS formatter sets the "Project Name" for the telemetry, and should possibly be included in the beacon rotation.

Corrected in commit 047e44510762c375aa1fea83ffcdf4ac0bf43a84
Project name is now used to transmit the full version string.


Additional Reporting Data Page: Regulated Operations and Reporting-only Operations

Description:
As a Regulated Operation, I want to add additional data so that I can fill out my emissions and compliance report
As a Reporting Operation, I want to add additional data so that I can fill out my emissions report, and need to ensure that "electricity generated" is an optional field only.
This page is required for all Regulated Operations (including Opt-ins and New Entrants) & Reporting Operations.
It does NOT apply for EIOs or Simple Reports.
The emissions and compliance reports are done at the facility level, but there are a couple of data fields that we need to ask users for at the operation level.
For SFOs this won't make a difference, and will just be an additional page after emissions and compliance data.
For LFOs they would see this page after they have completed all the facility level emissions and compliance forms.
Wireframe
Acceptance Criteria:
Given that I am a Regulated operation
When I've completed all the facility-level reports (emissions and production)
Then I need a form to fill in additional information
Given that I am a Reporting Operation
When I've completed all the facility-level reports (emissions only)
Then I need a form to fill in additional information,
Development Checklist:

[x] Add a model report_additional_data to store the additional fields required for Regulated and Reporting Operations. This will track the extra data added at the operation level.
[x] Add an additional reporting data  page at /reports/{version}/additional-reporting-data
[x] Additional reporting data is saved to the report_additional_data table on continue/save
[x] Form for capturing emission should be rendered only if user clicks on yes for Did you capture emissions?
[x] Electricity generated field should only be visible if operation's regisration purpose is Reporting Operation only.
[ ] Meets the DOD

Definition of Ready (Note: If any of these points are not applicable, mark N/A)

[ ] User story is included
[ ] User role and type are identified
[ ] Acceptance criteria are included
[ ] Wireframes are included (if required)
[ ] Design / Solution is accepted by Product Owner
[ ] Dependencies are identified (technical, business, regulatory/policy)
[ ] Story has been estimated (under 13 pts)

Definition of Done (Note: If any of these points are not applicable, mark N/A)

[ ] Acceptance criteria are tested by the CI pipeline
[ ] UI meets accessibility requirements
[ ] Configuration changes are documented, documentation and designs are updated
[ ] Passes code peer-review
[ ] Passes QA of Acceptance Criteria with verification in Dev and Test
[ ] Ticket is ready to be merged to main branch
[ ] Can be demoed in Sprint Review
[ ] Bugs or future work cards are identified and created
[ ] Reviewed and approved by Product Owner

Notes:

We have separate tickets for the "Additional Data" forms specific to a) New Entrants b) Regulated Partial Year

I took a stab at refining this but need to discuss at next week's refinement with everyone/

@ayeshmcg to write dev checklist

Hey @ayeshmcg I'm getting an error trying to get through Operation 17's workflow to this page. May need some assistance to review this.

@patriciarussellCAS
Can we schedule a call to check this together?

Follow-up notes:

I will confirm with BA whether regulated operations should see "electricity generation"
Need a design/tech debt ticket to move electricity generation into it's own field below under "Additional Data" that matches the wireframe.

@patriciarussellCAS
Created this tech debt card - https://github.com/bcgov/cas-reporting/issues/372

Confirmed that Regulated Operations see electricity generated, and Reporting Operations do NOT. I've added this to the tech debt card as well.


Reimplement css styling logic

Replace current hardcoded variant with a responsive/settings-driven one.

Done.


Cleaned up demo notebooks

Removed titles from demo notebooks so sphinx can index them correctly. Also cleared a couple notebooks which still had embedded output and renamed two notebooks.

Looks good. Happy to merge.

I'll merge right away as this stuff is not tested at the moment.


⚠ Bofrost.at has degraded performance

In c7a9549, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 1510 ms

Resolved: Bofrost.at performance has improved in 4af0587.


turbo: 1.7.0 -> 1.8.1

Description of changes
Updates to latest release.
Also fixes https://github.com/NixOS/nixpkgs/pull/200788#issuecomment-1438069262
Thanks for the package @dlip and reviewers !
Things done

Built on platform(s)

[x] 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
[x] 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

[x] Fits CONTRIBUTING.md.

Hmm some dependency still seems to be missing here...  it crashes when I run turbo run build on a project:
thread 'main' panicked at 'Failed to execute turbo.: Os { code: 2, kind: NotFound, message: "No such file or directory" }', crates/turborepo/src/main.rs:50:10
stack backtrace:
   0:           0x9cf900 - std::backtrace_rs::backtrace::libunwind::trace::h4a7f1a9dbfd0050f
                               at /rustc/215e3cd218b83b8a3152d84d92f17109253c25e1/library/std/src/../../backtrace/src/backtrace/libunwind.rs:93:5
   1:           0x9cf900 - std::backtrace_rs::backtrace::trace_unsynchronized::h5b828858f541f66d
                               at /rustc/215e3cd218b83b8a3152d84d92f17109253c25e1/library/std/src/../../backtrace/src/backtrace/mod.rs:66:5
   2:           0x9cf900 - std::sys_common::backtrace::_print_fmt::ha0d7f7fa2424466f
                               at /rustc/215e3cd218b83b8a3152d84d92f17109253c25e1/library/std/src/sys_common/backtrace.rs:65:5
   3:           0x9cf900 - <std::sys_common::backtrace::_print::DisplayBacktrace as core::fmt::Display>::fmt::he50c5143f1ab75d4
                               at /rustc/215e3cd218b83b8a3152d84d92f17109253c25e1/library/std/src/sys_common/backtrace.rs:44:22
   4:           0xa11c5e - core::fmt::write::hc787a3d04103fa2b
                               at /rustc/215e3cd218b83b8a3152d84d92f17109253c25e1/library/core/src/fmt/mod.rs:1209:17
   5:           0x9c9095 - std::io::Write::write_fmt::h675091bbbcb60bb9
                               at /rustc/215e3cd218b83b8a3152d84d92f17109253c25e1/library/std/src/io/mod.rs:1682:15
   6:           0x9cf6c5 - std::sys_common::backtrace::_print::h652b6c4ccf8840dc
                               at /rustc/215e3cd218b83b8a3152d84d92f17109253c25e1/library/std/src/sys_common/backtrace.rs:47:5
   7:           0x9cf6c5 - std::sys_common::backtrace::print::hed6a8016a9dd162e
                               at /rustc/215e3cd218b83b8a3152d84d92f17109253c25e1/library/std/src/sys_common/backtrace.rs:34:9
   8:           0x9d10ff - std::panicking::default_hook::{{closure}}::hf463edb68a4f4015
                               at /rustc/215e3cd218b83b8a3152d84d92f17109253c25e1/library/std/src/panicking.rs:267:22
   9:           0x9d0e3a - std::panicking::default_hook::h82bd8191dd7139df
                               at /rustc/215e3cd218b83b8a3152d84d92f17109253c25e1/library/std/src/panicking.rs:286:9
  10:           0x9d17fc - std::panicking::rust_panic_with_hook::he0a74a42970414b0
                               at /rustc/215e3cd218b83b8a3152d84d92f17109253c25e1/library/std/src/panicking.rs:688:13
  11:           0x9d1597 - std::panicking::begin_panic_handler::{{closure}}::h7940a88ccdfc66ac
                               at /rustc/215e3cd218b83b8a3152d84d92f17109253c25e1/library/std/src/panicking.rs:579:13
  12:           0x9cfdac - std::sys_common::backtrace::__rust_end_short_backtrace::h11489a9243f86fef
                               at /rustc/215e3cd218b83b8a3152d84d92f17109253c25e1/library/std/src/sys_common/backtrace.rs:137:18
  13:           0x9d12b2 - rust_begin_unwind
                               at /rustc/215e3cd218b83b8a3152d84d92f17109253c25e1/library/std/src/panicking.rs:575:5
  14:           0x426733 - core::panicking::panic_fmt::ha40ac504f27f693b
                               at /rustc/215e3cd218b83b8a3152d84d92f17109253c25e1/library/core/src/panicking.rs:65:14
  15:           0x4269f3 - core::result::unwrap_failed::h688862f4f03a9f36
                               at /rustc/215e3cd218b83b8a3152d84d92f17109253c25e1/library/core/src/result.rs:1791:5
  16:           0x4299ba - turbo::main::h06ba96bf1592f8b5
  17:           0x428753 - std::sys_common::backtrace::__rust_begin_short_backtrace::hdf39de5105f0d646
  18:           0x42806d - std::rt::lang_start::{{closure}}::h341c3aa093144fbe
  19:           0x9c16fe - core::ops::function::impls::<impl core::ops::function::FnOnce<A> for &F>::call_once::h7b5bc0122283ecc9
                               at /rustc/215e3cd218b83b8a3152d84d92f17109253c25e1/library/core/src/ops/function.rs:286:13
  20:           0x9c16fe - std::panicking::try::do_call::h5bd05eda45150b51
                               at /rustc/215e3cd218b83b8a3152d84d92f17109253c25e1/library/std/src/panicking.rs:483:40
  21:           0x9c16fe - std::panicking::try::h14eef84f9d16b8c4
                               at /rustc/215e3cd218b83b8a3152d84d92f17109253c25e1/library/std/src/panicking.rs:447:19
  22:           0x9c16fe - std::panic::catch_unwind::h2f8f5a68220e39dc
                               at /rustc/215e3cd218b83b8a3152d84d92f17109253c25e1/library/std/src/panic.rs:137:14
  23:           0x9c16fe - std::rt::lang_start_internal::{{closure}}::h4315d35388392089
                               at /rustc/215e3cd218b83b8a3152d84d92f17109253c25e1/library/std/src/rt.rs:148:48
  24:           0x9c16fe - std::panicking::try::do_call::h502afca58aff5254
                               at /rustc/215e3cd218b83b8a3152d84d92f17109253c25e1/library/std/src/panicking.rs:483:40
  25:           0x9c16fe - std::panicking::try::h60864fc3302cc007
                               at /rustc/215e3cd218b83b8a3152d84d92f17109253c25e1/library/std/src/panicking.rs:447:19
  26:           0x9c16fe - std::panic::catch_unwind::h39ab24ef2eb872b2
                               at /rustc/215e3cd218b83b8a3152d84d92f17109253c25e1/library/std/src/panic.rs:137:14
  27:           0x9c16fe - std::rt::lang_start_internal::h9a3de212315a782d
                               at /rustc/215e3cd218b83b8a3152d84d92f17109253c25e1/library/std/src/rt.rs:148:20
  28:           0x429b05 - main

Can anyone check if you get the same error?

ld: framework not found CoreServices

No idea what this means.
If Darwin doesn't work for whatever reason I could just flag this as Linux-only?
I don't have a Mac so there's not much I can do here really.

Tests are failing
--- FAIL: TestWaitForCookie (0.59s)
    cookie_test.go:25: assertion failed: error is not nil: timed out waiting for initial fsevents cookie: filewatching failed to start: Start
--- FAIL: TestWaitForCookieAfterClose (0.54s)
    cookie_test.go:46: assertion failed: error is not nil: timed out waiting for initial fsevents cookie: filewatching failed to start: Start
--- FAIL: TestWaitForCookieTimeout (0.56s)
    cookie_test.go:69: assertion failed: error is not nil: timed out waiting for initial fsevents cookie: filewatching failed to start: Start
--- FAIL: TestWaitForCookieWithError (0.73s)
    cookie_test.go:90: assertion failed: error is not nil: timed out waiting for initial fsevents cookie: filewatching failed to start: Start
--- FAIL: TestFileWatching (1.48s)
    filewatcher_test.go:108: assertion failed: error is not nil: timed out waiting for initial fsevents cookie: filewatching failed to start: fw.Start
FAIL
FAIL    github.com/vercel/turbo/cli/internal/filewatcher        4.166s
FAIL
error: builder for '/nix/store/90ajh0xmsi0s4hkqvr7z52facinqhms4-go-turbo-1.8.1.drv' failed with exit code 1;

@SuperSandro2000 Can you send me a link to that?
As far as I can see all checks are currently green except for the Darwin ones.

Hi! I tried your pull request in a custom flake.nix file to install turbo in a devShell. It builds and works as expected, until I try to run turbo dev on a default project created with pnpx create-turbo@latest.
> turbo run dev

thread ‘main’ panicked at ‘Failed to execute turbo.: Os { code: 2, kind: NotFound, message: “No such file or directory” }’ crates/turborepo/src/main.rs:50:10

Do you have any clue and why this could be happening?

@iivvaannxx yeah you're likely running turbo from node_modules instead of the one from nix.
Run which turbo to confirm.
Here's the shellHook I use:
        shellHook = ''
          npm i # for some reason yarn crashes without this (?)
          yarn
          rm -rf node_modules/.bin/turbo # use the one from nix
        '';

Rather than removing the binary, you can set the environment variable:
TURBO_BINARY_PATH="${pkgs.turbo}/bin/turbo"

Thank you both @dlip @mausch! I ended up exporting the environment variable and it worked. However, and I don't know why, if i run which turbo and echo $TURBO_BINARY_PATH they show exactly the same output, so it seems it wasn't actually using the node_modules binary. Even though, exporting the environment variable worked. Now the dev servers can start.
But, I get this rare warning:
failed to contact turbod. Continuing in standalone mode: connection to turbo daemon process failed. Please ensure the following:
        - the process identified by the pid in the file at /tmp/nix-shell.uhUxl2/turbod/d85cf2e7a4fada2b/turbod.pid is not running, and remove /tmp/nix-shell.uhUxl2/turbod/d85cf2e7a4fada2b/turbod.pid
        - check the logs at /home/ivan/.local/share/turborepo/logs/d85cf2e7a4fada2b-Portfolio.log
        - the unix domain socket at /tmp/nix-shell.uhUxl2/turbod/d85cf2e7a4fada2b/turbod.sock has been removed
        You can also run without the daemon process by passing --no-daemon

Which i am not sure what it means (I'm quite new using turborepo). And a little below, on the workspaces logs I get:
docs:dev: ready - started server on <IP_ADDRESS>:3001, url: http://localhost:3001
web:dev: ready - started server on <IP_ADDRESS>:3000, url: http://localhost:3000
web:dev: npm ERR! code ENOWORKSPACES
web:dev: npm ERR! This command does not support workspaces.
web:dev:
web:dev: npm ERR!  This command does not support workspaces.
docs:dev:
docs:dev: npm ERR! A complete log of this run can be found in:
docs:dev: npm ERR!     /home/ivan/.npm/_logs/2023-03-11T17_42_53_326Z-debug-0.log

So it seems that something is not going as it should be. If I can't fix this I can workaround it using Docker to run the development environment but I would like to use my system. Also, if this shouldn't be here, tell me where I should ask it and I will do it straight away.

Closing this, superseded by https://github.com/NixOS/nixpkgs/pull/220631
I don't know why I bother wasting my time sending update PRs to nixpkgs, this has happened to me several times already...


High intensity ANSI color codes render the same as normal in the Debug Console

The normal-intensity ANSI color codes (30-37, 40-47) render the same color as the high-intensity ones (90-97, 100-107).
This seems like a duplicate of #21423, but that one is closed and this is still an issue. It is noted in the code (https://github.com/Microsoft/vscode/blob/1f64c126721a66f30a7dcc3ac9e605e8115bcca7/src/vs/workbench/contrib/debug/browser/media/repl.css#L130), so I hesitate to call it a bug, but it seems like something someone put off and forgot about.

I can submit a PR for this tomorrow, just wanted to open an issue before I start working on it.

Dupe of #63986 (didn't see it before).


What's the purpose of these field?

In the picture, there is a field——active, in script like this:

But it does not have any script references!! And the Script itself doesn't make any Laser Pointer shows up, please check that, Thank you!

As already replied here: https://answers.unity.com/questions/1455089/vive-laser-pointer-turn-off.html by mesadigitaldesign, this has an easy fix:

 if(active != isActive)
 {
     isActive = active;
     pointer?.SetActive(isActive);
 }
 if(!isActive)
     return;

Fixed in next release


UseOpenApiRule is not special

Refactored Result to reference strings of interest rather than instances of RuleSet or Rule
Avoid creating RuleSet and Rule instances in tests just to build Result instances
RuleValidator no longer references a RuleSet or Rule when parsing fails
Documented a new InternalRuleSet

Closes #851

Codecov Report

Merging #972 into master will increase coverage by 0.03%.
The diff coverage is 90.47%.

@@             Coverage Diff              @@
##             master     #972      +/-   ##
============================================
+ Coverage     86.23%   86.27%   +0.03%
- Complexity      958      959       +1
============================================
  Files           174      174
  Lines          2696     2703       +7
  Branches        425      424       -1
============================================
+ Hits           2325     2332       +7
  Misses          162      162
  Partials        209      209

Impacted Files
Coverage Δ
Complexity Δ

...va/de/zalando/zally/rule/zalando/UseOpenApiRule.kt
82.5% <ø> (ø)
12 <0> (ø)
:arrow_down:

...rver/src/main/java/de/zalando/zally/rule/Result.kt
100% <100%> (ø)
8 <3> (+1)
:arrow_up:

...n/java/de/zalando/zally/apireview/RuleViolation.kt
83.33% <100%> (ø)
10 <2> (ø)
:arrow_down:

.../main/java/de/zalando/zally/rule/RulesValidator.kt
91.07% <86.66%> (+1.07%)
19 <0> (ø)
:arrow_down:

Continue to review full report at Codecov.

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

:+1:

:+1:


Taking Long to Save

Does this issue occur when all extensions are disabled?: Yes/No

VS Code Version:
OS Version:

Steps to Reproduce:

after closing vscode

/needsMoreInfo including platform, version, and whether the problem also happens if you run VS Code with all extensions temporarily disabled.

Thanks for creating this issue! We figured it's missing some basic information or in some other way doesn't follow our issue reporting guidelines. Please take the time to review these and update the issue.
Happy Coding!

This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines.
Happy Coding!


Generating types breaks with Tailwind CSS  v3.3

Hi,
thank you for this fantastic tool :heart:
In the version 3.3 of Tailwind CSS, they added a support for ESM and TypeScript config.
I've changed my config to ESM, and rename it to tailwind.config.ts.
I am trying to generate the types with the following command:
pnpm typewind generate

then I get the following error:
$ pnpm typewind generate
/home/xeho91/<redacted>/tailwind.config.ts:1
import pluginAspectRatio from "@tailwindcss/aspect-ratio";
^^^^^^

SyntaxError: Cannot use import statement outside a module
    at internalCompileFunction (node:internal/vm:73:18)
    at wrapSafe (node:internal/modules/cjs/loader:1176:20)
    at Module._compile (node:internal/modules/cjs/loader:1218:27)
    at Module._extensions..js (node:internal/modules/cjs/loader:1308:10)
    at Module.load (node:internal/modules/cjs/loader:1117:32)
    at Module._load (node:internal/modules/cjs/loader:958:12)
    at Module.require (node:internal/modules/cjs/loader:1141:19)
    at require (node:internal/modules/cjs/helpers:110:18)
    at createTypewindContext (/home/xeho91/<redacted>/node_modules/typewind/dist/cli.js:72:56)
    at generateTypes (/home/xeho91/<redacted>/node_modules/typewind/dist/cli.js:155:15)

Additional information
My project has type set to module in package.json file.
// package.json
{
  ...
  "type": "module",
  ...
}

Hi, thanks for opening this. Typewind currently directly imports the tailwind config, so it being in ts causes an error. Should be an easy fix, will look into it

Converting the Tailwind configuration file name to tailwind.config.cjs and adapting the code to common JS:
/** @type {import('tailwindcss').Config} */
// eslint-disable-next-line no-undef
module.exports = {
  content: ["./src/**/*.{html,js}"],
  theme: {
    extend: {},
  },
  plugins: [],
};

fixes it

Hey there, I'm looking into using typewind and I also have a .ts tailwind config file, am I correct to assume this is still an issue since there have been no further updates on here?

Sorry, yeah this is still a problem. I'll try getting to it this weekend!

any update on this or any ideas on how to fix it locally?

Hey @itsjavi, do you happen to be using the swc plugin? Custom theme tokens won't work with SWC because of its limitations (it can't access the file system to parse the tailwind config). They should be working with the babel plugin though

Just pushed a commit that should enable tailwind.config.ts! Will trigger an NPM deploy once it's live


Typo in README

I am assuming from the context that this is a typo

Hi @runette, thank you for your contribution and your interest in the project!
-   // Triangle is not considered bad if its area is smaller than MinimumArea.
+   // Triangle is considered bad if its area is smaller than MinimumArea.

It seems there might be a misunderstanding. The refinement process aims to eliminate all triangles in the mesh that are considered "bad" based on their area and/or angles.
Before version v2.4 (the upcoming release at main branch), there were two parameters: MinimumArea and MaximumArea.

MinimumArea acted as the lower bound, preventing segment splitting or triangle splitting if a triangle's area was smaller than the specified value (or any triangle shared by the segment).
MaximumArea served as the upper bound, classifying triangles as "bad" if their area exceeded the specified value.

However, with the changes in the v2.4+ refinement algorithm, there is now a single parameter called RefinementThresholds.Area. This parameter classifies a triangle as "bad" if its area is greater than the specified threshold.
I am aware that the previous pair of parameters, MinimumArea/MaximumArea, may have introduced confusion. I hope that the introduction of the single parameter RefinementThresholds.Area resolves any potential confusion in the future."
Please note that v2.4 is still under development, and I haven't updated the README.md after the recent commit 9d71e0aaf706ab4725d8aabc76ab6a508671fcd0. I appreciate your understanding and will make sure to address this in the documentation soon.

Thanks for the response. The current text is indeed very confusing.

@runette, in commit 9d71e0a, I introduced a summary for the new parameter RefinementThresholds.Area, which should now be clear:
            /// <summary>
            /// Specifies the maximum area constraint for triangles in the resulting mesh refinement.
            /// Ensures that no triangle in the mesh has an area larger than the specified value.
            /// </summary>

Similar text will be added in README file.
I have also marked Minimum/MaximumArea as obsolete.
The README.md should be updated in the next week, since with a few large recent update I wanted to postpone it.


deleting

[ ] bills
[ ] payments
[ ] payment sources

not needed in the nearby future releases. closing this for now.


PWA: IDB support.

With this change the PWA will start showing cached emotlies in the home
with limited or absent connectivity.

LGTM.

I've rebased this, just to be totally sure.
Thanks for your review @tizianasellitto. Let me know if there's something else to address before landing this.:)

It's ok. Go on.


Increased Openstack timeouts from 5 minute to 10 minutes.

For Openstack clusters that runs on VMs, the provisioning / image uploading is slow.
To cover such clusters, i increased all the openstack timeouts from 5 to 10 min.
@mbhinder @tw4dl

LGTM


Add feature flag to simulate EoC cancellation behaviour

Context
Make it easier to manually test https://github.com/DFE-Digital/apply-for-teacher-training/pull/2788

Changes proposed in this pull request
For a specific time window towards the end of the cycle, we cancel any
applications to unavailable course options before they can be sent to
the provider.
When this feature flag is active, the time-related checks for whether or
not we apply that behaviour are stubbed. This makes manual testing
easier when outside of the time window.

Guidance to review

Link to Trello card

https://trello.com/c/tGI5SMcV
Things to check

[x] This code does not rely on migrations in the same Pull Request
[x] If this code includes a migration adding or changing columns, it also backfills existing records for consistency
[x] API release notes have been updated if necessary
[x] New environment variables have been added to the Azure config

Think we're also starting to form a new category of feature flags around simulat_x and we could revisit how to break up / organise them.


Fix generation to docs and consistency

Spelling error Blocktack > Blockstack
Consistency in the generated view and the line switching " to '

@jcnelson Fixed my npm and tested locally.

 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.Mary Anthony seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.

 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.Mary Anthony seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


Scoop broke: no output after command interrupt

Hello,
So I accidentally ran a command I use to update my bucket:
cd "E:\scoop-buckets\private" `
&& git add --all `
&& git commit `
&& scoop update `
&& scoop status

... and so I quickly pressed Ctrl+C. I'm not sure if I managed to interrupt the command or not, but there were no changes to be commited anyway (I've closed the console window now).
Immediately after that, the command I use to check for updates, E:\scoop-buckets\private\bin\checkver.ps1 -app * && scoop update && scoop status, returns:
Split-Path: E:\scoop-buckets\private\bin\checkver.ps1:1
Line |
   1 |  … P_HOME = resolve-path (split-path (split-path (scoop which scoop))) }
     |                                                  ~~~~~~~~~~~~~~~~~~~
     | Cannot bind argument to parameter 'Path' because it is null.

&: The term '/bin/checkver.ps1' is not recognized as a name of a cmdlet, function, script file, or executable program.
Check the spelling of the name, or if a path was included, verify that the path is correct and try again.

Somehow Scoop broke and I'm not sure what's changed. Scoop was working perfectly immediately before the accidental command, and stopped working immediately after it.
My user environment variables show a SCOOP pointed to Scoop's location ("D:\scoop"). No SCOOP_HOME is present (not sure if there should be).
Running scoop returns no output.
"D:\scoop\apps\scoop\current" contains files (~12 MB).
Restarting the system didn't resolve the issue.
Thanks.
Windows Terminal v1.8.1521.0
PowerShell v7.1.3

Edit: Apparently, these three files with "scoop" in their file path were modified 40 minutes - 2 hours before the time of the issue:
"D:\scoop\shims\scoop.ps1":
if (!(Test-Path Variable:PSScriptRoot)) { $PSScriptRoot = Split-Path $MyInvocation.MyCommand.Path -Parent }

"D:\scoop\shims\scoop":
#!/bin/sh
powershell.exe -noprofile -ex unrestricted "D:\scoop\apps\scoop\current\bin\scoop.ps1"  "$@"

"D:\scoop\shims\scoop.cmd":
@echo off
setlocal enabledelayedexpansion
set args=%*
:: replace problem characters in arguments
set args=%args:"='%
set args=%args:(=`(%
set args=%args:)=`)%
set invalid="='
if !args! == !invalid! ( set args= )
powershell -noprofile -ex unrestricted "& 'D:\scoop\apps\scoop\current\bin\scoop.ps1'  %args%;exit $lastexitcode"

Are they as they should be?
Where else could the problem lie? I don't understand how Scoop could break like this, so it is difficult for me to fix. What should I check for? Which values should be set in my environment?

Solved: The fix was to run "D:\scoop\apps\scoop\current\bin\scoop.ps1" directly and check for an update:
D:\scoop\apps\scoop\current\bin\scoop.ps1 update
Updating Scoop...
WARN  Overwriting shim to scoop.ps1 installed from
Updating 'extras' bucket...
[...]
Scoop was updated successfully!

And scoop now produces output again:
scoop
Usage: scoop <command> [<args>]

Some useful commands are:
[...]


Extension issue

Issue Type: Bug
Extension Name: html-language-features
Extension Version: 1.0.0
OS Version: Windows_NT ia32 6.1.7601
VS Code version: 1.68.1

:warning: We have written the needed data into your clipboard. Please paste! :warning:

Thanks for creating this issue! It looks like you may be using an old version of VS Code, the latest stable release is 1.91.1. Please try upgrading to the latest version and checking whether this issue remains.
Happy Coding!


Feature/jsonapi (part 1)

Closes #27
Should support all the basic stuff for JSON API
Thanks @Landsi @stanislavstavrev and @joanromano for the help during DONI
Was quite easy to solve the empty array issue:
Element.self is JSONAPISerializable.Type // we just forgot .Type

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

Merging [#54][cc-pull] into [master][cc-base-branch] will increase coverage by +0.09%

@@             master        #54   diff @@
==========================================
  Files             5          6     +1
  Lines           314        385    +71
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
+ Hits            312        383    +71
  Misses            2          2
  Partials          0          0

Powered by Codecov. Last updated by [d66ea2b...8b463dc][cc-compare]
[cc-base-branch]: https://codecov.io/gh/devlucky/Kakapo/branch/master?src=pr
[cc-compare]: https://codecov.io/gh/devlucky/Kakapo/compare/d66ea2beee203a7405b6807dddbe67b7cb8507df...8b463dccc656b506aa7846e04f9af299a102748c
[cc-pull]: https://codecov.io/gh/devlucky/Kakapo/pull/54?src=pr

👍


Unresolved P/Invoke method 'winmm.dll!midiOutGetNumDevs' in UWP app

Copied from the comment:

I noticed OutputDevice.GetByName("Microsoft GS Wavetable Synth"); in UWP apps in debug mode works, but release mode fails with "'Unresolved P/Invoke method 'winmm.dll!midiOutGetNumDevs' from this method. Please look for this method in build warnings for more details. '" as UWP has a dedicated abstraction to be used https://docs.microsoft.com/en-us/windows/uwp/audio-video-camera/midi
A means to use existing cross-platform libraries would be great, or a way to add support for other platforms by app developers.

I've fixed the issue. Changes are not released yet. You can either build the library from sources from develop branch, or take DLL from here: DryWetMIDI.5.2.0-bin-net45.zip.
I did some testing and results are pretty interesting.
First of all, I have these devices in my system (all are virtual ones):
Microsoft GS Wavetable Synth
LoopBe Internal MIDI
Game Controller 1
01. Internal MIDI
02. Internal MIDI
MIDI A
MIDI B
MIDI C
Keyboard

If I use DryWetMIDI in .NET framework or .NET Core app, I see all these devices with exact names. But if I use DryWetMIDI in UWP app (after fix) I see:
Microsoft GS Wavetable Synth

So it looks like all non-standard virtual devices are not listed.
But much more interesting is what UWP native API (from link you've provided) shows:
MIDI
MIDI
02. Internal MIDI [1]
Программный синтезатор звуковой таблицы Microsoft
MIDI
01. Internal MIDI [1]
MIDI
MIDI
LoopBe Internal MIDI [1]

Hmm, that's not what I expect... Программный синтезатор звуковой таблицы Microsoft is Microsoft GS Wavetable Synth in Russian. I don't know why Microsoft decided to localize it in UWP API. Also all remaining devices have wrong names. So I definitely won't use UWP API in DryWetMIDI.
Anyway, the problem is fixed now :) Thanks for the issue!

Thank you very much for fixing this issue.


Limit processing in flatten

Abandon flattening past a certain depth.
Abandon flattening past an element index number across all lists. This is useful for very large lists. For example we can set max_list_elements=100 and only the top 100 elements in all lists are processed.

As mentioned in https://github.com/amirziai/flatten/issues/11, including a subset of fields or excluding fields would also limit processing (ie. 1 and 2 in https://github.com/amirziai/flatten/issues/9). As a user of the library, my use case is I have in mind that I want to process certain fields and ignore others. To me it is more intuitive to be able to specify that to the library than post processing the output of the library.

@mcarans let's say we have this dictionary (feel free to come up with a better example but I want us to nail down the requirements):
d = {
'a': [1,2,3],
'b': {'a': [1,2,3], 'b': [4,5,6]},
'c': 'c',
'd': {'a': 5}
}
What would you want to pass to `flatten` and what do you want to see in return?

I would want to pass in some way 'a' and get back from flatten 'b', 'c' and 'd' flattened. The 'a' : [1,2,3] would not be output at all. The other 'a' under 'b' and 'd' would be output ie. we only apply this at the root level.

If it's root-level and the argument you pass is the set to be filtered I think I've addressed it in #11 . Here's the documentation I wrote:
https://github.com/amirziai/flatten/tree/flatten-ignore-keys%239#ignore-root-keys
Am I missing something?

@amirziai I see that you have implemented the above which is what I would have called 1/2 from my list ie. inclusion/exclusion of fields. For 3 and 4, I meant that all fields would be included, but that these options would enable or disable flattening of those fields ie. with your example above if we disabled flattening for 'b', then our output would have a column entitled 'b' with contents 'b': {'a': [1,2,3], 'b': [4,5,6]}

@mcarans I think I understand now. The point of flatten to me is that the resulting object has no structure (no iterables other than strings are present as values of the flat dictionary). This way you can easily pass the dictionary to Pandas. I see the use case though but I think that it should live outside of flatten. Feel free to open a new issue for it.


Add local Visual Studio Code just like other included software

Include VSCode in the installer (may be an option).
Add the "data" folder to VSCode so that the extensions will also be installed locally.
And provide a "portable" version of pico-setup in .zip format without any installation.

Visual Studio Code is updated very frequently, and adding a copy of it to our installer would mean that for most of the lifetime of the installer, users would get an outdated version.

The VS Code licensing terms also don't allow redistribution anyway. More info in https://github.com/microsoft/vscode/issues/60205#issuecomment-1018985581

@ndabas If VSCode isn't included in the pico-setup-windows installer, why is it listed in https://github.com/raspberrypi/pico-setup-windows/blob/master/README.md#included-software ?

Ahh, looking at https://github.com/raspberrypi/pico-setup-windows/blob/master/packages/pico-setup-windows/VSCodeUtils.nsh it seems that pico-setup-windows automatically downloads and installs the latest VSCode installer during setup.

Yes, it is downloaded and installed when the setup is run, but is not 'included' in the sense of the binary being a part of the installer.
I assumed from the phrasing of the issue that the poster was talking about an offline version, because the installer does 'include' VS Code in terms of what it installs.

Yes, why not download and unzip VS Code inside SDK.

Yes, why not download and unzip VS Code inside SDK.

That's already been answered in this thread.


MakerDAO Extended Schema QA

Description
Value

Subgraph Reviewed
https://subgraphs.messari.io/subgraph?endpoint=https://api.thegraph.com/subgraphs/name/tnkrxyz/makerdao-ext&tab=protocol

Date Reviewed
October 12 2022

Schema Version
2.0.1

Subgraph Version
2.0.0

Methodology Version
1.1.0

Issues

cumulativeUniqueUsers - It looks like the the old schema is tracking 49,082 and the 2.0.1 schema is tracking 31,515

I see for this account that there is two closed positions. It looks like there is a lending position and then a borrowing position. How come there is only repay though? For the lending side shouldn't there be a deposit and the borrow side there should be a repay and a borrow? This might be weird though because it looks like an early makerDAO transaction since its in SAI, but figure I’d double check. Query - https://api.thegraph.com/subgraphs/name/tnkrxyz/makerdao-ext/graphql?query=%7B%0A++ac[…]estampOpened%0A++++++timestampClosed%0A++++%7D%0A++%7D%0A%7D

This liquidation looks correct, but I am not sure about the profitUSD. IIRC this should be the penalty fee correct ? Looks like this is $8.47K on maker risk (https://maker.blockanalitica.com/liquidations/per-date/2022-09-19/) but only $638 on the subgraphs. Maybe, I am interpreting wrong and this account did not provide the full liquidation so it only received $638 for their share? Query - https://api.thegraph.com/subgraphs/name/tnkrxyz/makerdao-ext/graphql?query={
++account+(id%3A+"0x045bf24164b9dd5949bcd780f679fb60effe7637")+{
++++openPositionCount
++++closedPositionCount
++++depositCount
++++liquidateCount
++++liquidates+(orderBy%3A+timestamp%2C+orderDirection%3A+desc%2C+first%3A+1)+{
++++++market+{
++++++++id
++++++}
++++++hash
++++++amount
++++++col
++++++amountUSD
++++++profitUSD
++++++asset+{
++++++++name
++++++++id
++++++}
++++}
++}
}

Thx! Will take a look of them soon.

1. `cumulativeUniqueUsers` - It looks like the the old schema is tracking 49,082 and the 2.0.1 schema is tracking 31,515

This is due to a bug in the new implementation not taking into account urns owned by DSProxy owned by a user. I fixed it and redeployed the subgraph. The new subgraph also handles transfers of CDP (urn) positions, while not in the old implementation (1.1.3). The fix should bring the two number closer, but may not be exactly equal.

2. I see for this account that there is two closed positions. It looks like there is a lending position and then a borrowing position. How come there is only repay though? For the lending side shouldn't there be a deposit and the borrow side there should be a repay and a borrow? This might be weird though because it looks like an early makerDAO transaction since its in SAI, but figure I’d double check. Query - [https://api.thegraph.com/subgraphs/name/tnkrxyz/makerdao-ext/graphql?query=%7B%0A++ac[…]estampOpened%0A++++++timestampClosed%0A++++%7D%0A++%7D%0A%7D](https://api.thegraph.com/subgraphs/name/tnkrxyz/makerdao-ext/graphql?query=%7B%0A++ac%5B%E2%80%A6%5DestampOpened%0A++++++timestampClosed%0A++++%7D%0A++%7D%0A%7D)

Can you post the complete link again - the one above was truncated.

3. This liquidation looks correct, but I am not sure about the profitUSD.

For tx 0x60d9aa1de054884827dc5e7ae032dbe8e09e5da09f3145138d6d4cdf7c18367c, the debt was $65156, and maker imposes a 13% penalty on liquidations (that goes to the protocol), the liquidation auction was set for and won at $73626, but market value of the seized ETH was $74264, netting a profit of $638 to the liquidator.

@tnkrxyz Sounds good for 1 and 3. Sorry about that here is the full query - https://api.thegraph.com/subgraphs/name/tnkrxyz/makerdao-ext/graphql?query={
++account+(id%3A+"0x41e335ef0d3f9c7fec0eb86d3fbe81d062d66133")+{
++++openPositionCount
++++closedPositionCount
++++depositCount
++++liquidateCount
++++borrowCount
++++repayCount
++++positions+{
++++++isCollateral
++++++borrows+{
++++++++id
++++++}
++++++repays+{
++++++++id
++++++++amountUSD
++++++}
++++++deposits+{
++++++++id
++++++}
++++++side
++++++id
++++++timestampOpened
++++++timestampClosed
++++}
++}
}

A quick update that I'm still working on 1. I found a bug in subgraph version 1.1.3 (the account.id all missing the proper 0x prefix), so 49k unique users is certainly incorrect. I believe it only affects user count metrics, position and transaction entity.  I fixed the bug and re-deployed to my own account to see if it matches with ext subgraph number.
I have a hypothesis for 2; will write up once I confirm it.

@bye43 Sorry for the delay in getting back to this - redeployed makerdao-ext subgraphs took a long time to sync & I had to do it a few times before I got it right.
For unique user count, there were a bug in the makerdao-ext subgraph AND a separate bug in the makerdao subgraph, so neither unique user count was correct. After fixing both bugs, the ext subgraph has a cumulative unique user count of 22,334 as of 2022-11-12, while the number for the fixed makerdao subgraph is 21,877. I believe the difference is due to whether cdp ownership change is included. I think the current implement in makerdao-ext is better.
In terms of the positions/repaycount for address 0x41e335ef0d3f9c7fec0eb86d3fbe81d062d66133, the discrepancy was indeed because of account migration from old SAI to MCD contract. I implemented a fix for it and the repaycount is now correct using this query.
Note that: 1). the deposit count & borrow count is still off (both=0) because they happened in the old contract; 2). You have to use "0xe617cb6f95ee083b18287e86be729f87c172f949" as the account id, because 0x41e335ef0d3f9c7fec0eb86d3fbe81d062d66133 is a proxy owned by 0xe617cb6f95ee083b18287e86be729f87c172f949. With the bug fixed, the Account entity only includes owner aadresss of urns/proxies. You can see this in the above query

@tnkrxyz Trust your judgement for cumulativeUniqueUsersand looks good for positions/repaycount for address 0x41e335ef0d3f9c7fec0eb86d3fbe81d062d66133. Thanks and will close issue! @jaimehgb should this be deployed to the messari hosted service?

@bye43 thanks!
I forgot to tag #696 where the bug fix was pushed.


Add links to download a video

Purpose
We want to add links to download a video when we are viewing it. We should be allowed to download it in 480p, 720p and 1080p.
An instructor should also decide if a video is downloadable or not.
Proposal
We have to add is_downloadable property to a video object. This property is by default True and can be changed by an instructor from the video dashboard.
If a video is downloadable then we display links to download it in 480p, 720p and 1080p just below the video player

[x] add is_downloadable field to video model and expose it in the API.
[x] Add a component to manage is_downloadable state in the video dashboard
[x] display links above the video player if the video is downloadable.

Should we find another wording than is_downloadable because anyway IT IS downloadable ^^
show_download?

Can you add screenshots? e.g. a sliding switch button would be nice to trigger this flag.

Can you add screenshots? e.g. a sliding switch button would be nice to trigger this flag.

Screenshots added

Should we find another wording than is_downloadable because anyway IT IS downloadable ^^
show_download?

Indeed they are downloadable but I think there no misunderstanding calling it is_downloadable. show_download can also be a solution.

@jmaupetit you can do a last review please.

@jmaupetit @sampaccoud there is a new commit adding a new function in AWS update-state lambda ;-)


Add support for catching handlers that panic

closing this as the project is no longer being used by crates.io


HealthMonitor generates scan and fix tasks which do not get fixed

BOSH version 265.1.0
During a deployment the director waits for all agents to start. If at this point a timeout happens the deployment fails. For such a deployment HM will generate resurrection alerts (see here). The resurrector creates scan and fix jobs for these alerts. The scan and fix jobs can't the issue because at this line expects_vm? returns false and all VMs are filtered out. It returns false because the lifecycle of the job is nil.
Is there a reason why the analyze_agent doesn't check the expects_vm? state like analyze_instance does?

Is there a reason why the analyze_agent doesn't check the expects_vm? state like analyze_instance does?

if that information is available i dont see a reason why not.

Closing/re-opening to make a github story. @voelzmo is this something you all are interested in owning?

Hi @beyhan,
Is this still an issue on the latest version of the BOSH director? If so, could you give us some specific steps to reproduce this issue?
We've tried recreating this on initial deploys, upgrade deploys, etc and still haven't been able to see the HM create a large number of alerts.
Let us know if you have any other questions.
Best,
@jfmyers9 && @jaresty, CF BOSH

We'll close this for now. Please let us know if you want to re-open it.
Best,
@pivotal-mp && @dpb587-pivotal

Hi @jfmyers9,
Sorry, I couldn't get back to this issue. It's OK to close it and will reopen it if needed. I still think that the issue exists but didn't observed it for a while.


Pipe broken error when turning on notification island

Hi Again,
I was experimenting and came across a weird error where it says that the pipe is broken for stdout

another thing i found is that whenever resuming music, the r always gets cut off. is there a way to change where it is displayed. ive tried but had no luck

that the pipe is broken for stdout

Although this is an unexpected output, it shouldn't affect the core functionality of this project.

the r always gets cut off.

You may have to tweak some of the settings. The default settings are for MBP 14 inch 2021 (there's also an option for MBP 16 inch 2021). You can tweak the settings by modifying userconfig.sh (see readme for more details). I understand most values require tedious process to determine, it is normal to go through trial and error.


Feature: Publish OCI Annotations

Metadata in the form of annotations can be associated to OCI based images. Helm also supports defining annotations on the Chart.yaml file. When publishing charts to OCI based registries, annotations should also be published to the image manifest.
Annotations would be associated with the following:

Known/Predefined keys
User defined annotations

The following table defines how OCI annotations are mapped including applicable fields from the Chart.yaml file.

OCI Annotation
Description
Chart.yaml field

org.opencontainers.image.created
RFC 3339 date the chart was published to the registry

org.opencontainers.image.authors
Comma separated list of maintainers in the form Maintainer Name 1 (email), Maintainer Name2 (email)
maintainers

org.opencontainers.image.url
URL of the project
home

org.opencontainers.image.source
First item from the sources property
sources

org.opencontainers.image.version
Chart Version
version

org.opencontainers.image.title
Chart name
name

org.opencontainers.image.description
Chart description
description

<User Defined Annotations>
Additional annotations to include
annotations

Additional annotations as designated in the annotations field within the Chart.yaml file.
Certain user defined annotations cannot override the generated value:

org.opencontainers.image.created
org.opencontainers.image.title
org.opencontainers.image.version

Related to #11059

My only question is whether the oci artifact digest would change if annotations were added, or if it's only calculated on the content. Asking because currently, helm push is idempotent. Can not look into it right now, but discussed with @sabre1041 and one of us will check on this

While we are waiting for the PR to get merged here is a workaround:

create annotations.json{
  "$manifest": {
    "annotation1": "foo",
    "annotation2": "bar"
  }
}

create either empty config.json or convert Chart.yaml to JSON and save it as config.json
push the chart with oras (version 0.15.0 was used)aws ecr get-login-password | oras push -u AWS --password-stdin \
  $(ECR_REGISTRY)/$(IMAGE_NAME):$(IMAGE_TAG) \
  --config config.json:application/vnd.cncf.helm.config.v1+json \
  --annotation-file annotations.json \
  $(IMAGE_NAME)-$(IMAGE_TAG).tgz:application/vnd.cncf.helm.chart.content.v1.tar+gzip

aws ecr batch-get-image could be used to pull information about the image{
    "schemaVersion":2,
    "mediaType":"application/vnd.oci.image.manifest.v1+json",
    "config":{
	    "mediaType":"application/vnd.cncf.helm.config.v1+json",
	    "digest":"sha256:ca3d163bab055381827226140568f3bef7eaac187cebd76878e0b63e9e442356",
	    "size":3
    },
    "layers":[
	    {
		    "mediaType":"application/vnd.cncf.helm.chart.content.v1.tar+gzip",
		    "digest":"sha256:4daf63839a7c00eb96b332da4002509059bd6c2082c32b3a269681c7e3a379b9",
		    "size":3833,
		    "annotations":{
			    "org.opencontainers.image.title":"..."
		    }
	    }
    ],
    "annotations":{
            "annotation1": "foo",
            "annotation2": "bar"
        }
}

Example of a Makefile:
ECR_REGISTRY = ???
IMAGE_NAME = ???
IMAGE_TAG = ???

annotations.json:
	echo '{"$$manifest": {"annotation1": "foo","annotation2": "bar"}}' > annotations.json

config.json:
	echo '{}' > config.json

.PHONY: oras-publish
oras-publish: annotations.json config.json
	aws ecr get-login-password | oras push -u AWS --password-stdin \
		$(ECR_REGISTRY)/$(IMAGE_NAME):$(IMAGE_TAG) \
		--config config.json:application/vnd.cncf.helm.config.v1+json \
		--annotation-file annotations.json \
		$(IMAGE_NAME)-$(IMAGE_TAG).tgz:application/vnd.cncf.helm.chart.content.v1.tar+gzip

.PHONY: get-annotations
get-annotations:
	aws ecr batch-get-image \
		--repository-name $(IMAGE_NAME) \
		--image-id imageTag=$(IMAGE_TAG) \
		--output json | jq -r '.images[].imageManifest'

Hope that will help someone in the meantime.


fix broken html due to invalid truncate

in view_eng.html we use the django built-in filter truncatechars. However currently on dev this outputs something like this:

              Commit Hash
              <em class="t…

              Branch/Tag
              develop

              Orchestration

                    Not Specified

which breaks the html because it opens a  tag and never closes it.
using django built-in filter `truncatchars_html" must be used

I see you've put the milestone there, something you wanna see merged into the RC?

Yes, but didn't want to cause more work as it's not high prio. How would this work. You (or me) just cherry picking this commit into the RC branch? Or create another PR? Don't like PR handling, so might as well wait for 1.6.1 or 1.7.0.

Yes, but didn't want to cause more work as it's not high prio. How would this work. You (or me) just cherry picking this commit into the RC branch? Or create another PR? Don't like PR handling, so might as well wait for 1.6.1 or 1.7.0.

I was gonna go for cherry-picking. That's what we documented as well, also introducing a new tag for now I guess to make sure the PR is frozen (ready-for-backport).


No E-Mail-Notification via GitHub

This is only possible with assignee = me in .upptimerc.yaml 👍🏻

This is only possible with assignee = me in .upptimerc.yaml 👍🏻

And with Include your own updates in https://github.com/settings/notifications

Or when assigning issues to an account different from the one that opens the issues 🤔 So that this other account will get notified when new issues are opened (and closed?)…!?


Send raid lobbies to webhook

This sends all raid lobbies directly to webhook and skips persisting to DB. Adds a new webhook type raid_lobby. Fixes #107.
Depends on #123. Untested but comments welcome.

I have only looked briefly so this could be inaccurate.  This probably generates webhooks even with no change in the lobby value which is probably excessive.
If I am right (and have not missed the logic), then it would be easy enough to store the current value in the gym record in any case - just we wouldn't load or save it to the db.  It would then also be available to be returned by any in-memory query later.

A new webhook of this type (without broader gym details) would not be one poracle could notify on - it would need to be an extension to the one of the standard ones (or, at least have complete enough information to build a notification).
If it is not relevant to poracle to consume this then you can ignore this comment

if you're making this a complete raid webhook type, i think it should also be sent based on GMO data, with the lobby count being 0

Yes in that case those two fields would simply be missing from the webhook object. By the way, feel free to push directly to this PR. :)

This is looking really good. We just need a source of the data to be able to test, but will be merged when we can show it working correctly.

Merge when? 😃

Merge when? 😃

Not until it’s been possible to test with real data to see that it works as we would wish - and to give opportunity to evaluate that the format and sequence of data is useful to any possible downstream users

It sounds some people are now feeding this with data, please can you post a webhook sequence generated so we can see how lobbies evolve from egg onwards (eg null/vs 0/repeat entries) so we can consider if the format is correct for downstream implementers.

Could you add GetRaidLobbyCounterOutProto to the list of supported protos in protos.md please?

Hmm. Maybe this should be gated behind a config for webhook?

If we aren't sending it by webhook, perhaps we shouldn't be processing it at all (since that's our only use case; maps can't get it yet because it is held in memory only).  If there is an option it should probably just not process it (and therefore not generate the webhook).
Should this be added to 'scan context'?  This is our generalised way of controlling what is processed, but this is location and scan mode related and I'm not sure either of these apply.
if later we manage to make a subscription based channel for changes to map inside a specific window (which would be possible with our geographic data structure and grpc support) we can consider whether the changes are pushed this way and optionally not by webhook - but we don't have that for now.
I have to say when you start to multiply up the number of data items and frequency of change (every 5-10 seconds for every active raid on a big map) it starts to look quite large quite quickly.  As in discord, I fear for the way poracle does matches - but we won't really know until someone experiments with it.

Just wondering. Is it more reasonable to put this switch here, or put it in the controller? If the controller does not send the queries then Golbat wouldn't process either.

Most mitm won’t allow selectivity. It will come regardless from eg atlas

This is scan context, but as I say this is a per location / scan type config. This should probably just be a global setting to begin with.

This is conflicting with main now... But I would say sending raid lobbies to webhooks is getting more useless than before. with actual changes a lobby closes immediately if 20 players are in there, even 3-5 players are leaving again, nobody can join anymore.
So I would prefer to have some stats on it, rather than webhook notifications :)

If you're at a place with constant 20-player lobbies, this PR is useless either way anyways?

We should keep this open until a consumer exists or clear use arises as all of the content is valid just without a user yet

Hi I'm a user. I like to help out my rural strangers with legendary raids. 🫡

That's what I meant? The use case is to track gyms near you that you could join immediately if a lobby starts.

That's what I meant? The use case is to track gyms near you that you could join immediately if a lobby starts.

Indeed; but given the time remaining we have seen on real life hooks, processing & notification delay and no tooling yet to actually deliver this - combined with now 'ready to raid' shortening lobbies - I remain skeptical that a useful implementation will appear.  However, simply because it's possible that it may I am suggesting we keep this open rather than close it unmerged.

I feel like the norm for rural raiding is to keep going into lobbies and jump out until a critical mass of players are in the lobby. Whatever data you gathered at large cities will never be relevant since this feature is completely useless there to begin with.

So maybe in order to decrease load, maybe downstream could instead use a grpc to let golbat know what gyms they're interested in raiding, and golbat will skip all other gym lobbies. The hook would also expire once the raid finishes or downstream unsubscribes. This way it should solve the issue of overloading poracle?

Rural areas tend to have less frequent 'drive bys' by MITM scanners so actually catching a lobby is going to be less likely.  As I said, I'm happy to leave this as a PR until others prototype solutions - my work on this subject (including sending the protos to golbat across my entire area) has lead me to believe that a useful & practical solution is unlikely to be forthcoming.
Should one exist then we will be able to evaluate load across the system in production and whether the webhook contains the right information etc.
You are right that an entirely different communication mechanism could modifies some of the timeliness (but that's only 1 second of the delay probably), or could provide a different subscription model than exists for current webhooks.  It's unlikely to be poracle that would subscribe because that's a fundamentally different architecture.
I have seen an alternative prototype which receives the raws directly (no golbat needed); posts to discord for specific gyms and even that shows that given scan rates and discord push notification delays it's not quick enough to be useful.
Perhaps some dedicated application using android or apple push could get there fast enough if you increased scanning density.


Check for ext property on Android gradle module

I did some tests and realize that the previous commit (#163) introduced a wrong behavior that was maintained in #231
What happens is that, when we use a statement (project.ext.reactNative) in our .gradle file, we are saying that we want to use the ExtraPropertiesExtension and get a property from this called reactNative, but if the property doesn't exist an error will be thrown.
The case where it works well is when we change the project.ext by rootProject.ext and start to check if any ext's property exists before using it.

Blog worthy!

Just leaving this shameless link to my tweet as a reference for all those who complain on open source software: https://twitter.com/designorant/status/927509929195384832
Thanks guys!


Good summaries were ignored

Hi @hwchase17 ,
I'm using RetrievalQA to do question answering on vector store, below are the config I used
llm=ChatOpenAI chatgpt 3.5 model
embeddings = OpenAIEmbeddings
retriever=Pinecone
This is one of the messages
Given the following extracted parts of a long document and a question, create a final answer.\nIf you don't know the answer, just say that you don't know. Don't try to make up an answer.\n______________________\n
I set the results from Pinecone to k=4, it did summarize for documents and put into the final prompt messages. The strange thing is that the first summary is good and the rest of the summaries all said 'here is no information provided in the given portion of the document something like this. But the expected answer should use the first summary.
And then the final answer I got is like there is no information about xxxx. This happened since last Friday after 4~5pm, and I can get the correct answer before.
Do you know if something changed on openai chat completion API?

Hi @hwchase17,
Thank you for bringing this issue to my attention. It appears that the summarization tool is not providing the expected output.
I suggest trying the following steps to troubleshoot the issue:

Check the configuration of the summarization tool to ensure that the correct parameters are being used.
Check the input documents to ensure that they are correctly formatted and contain the necessary information.
Try using a different summarization tool to see if the issue persists.

If the issue persists, please provide more information about the input documents and the configuration of the summarization tool.
I hope this helps.
Best,
Langchain


lean CI: automatic labeling of PRs

I was curious about your Lean rewrite of the autolabel script, so I took a look already. I hope you don't mind! (Let me know if you prefer to just hack on it instead.)
Your new script looks really shiny and elaborate. In my mind, I was thinking of something much simpler (basically, a direct port as much as possible), hence I wonder if all this complexity is necessary. (It is really fun to write this, I agree --- but as code is read more often, I care about future readers more...) As far as I can see, the drivers of that complexity are
(1) adding exclusions (to handle Tactic.Lint getting labelled as t-linter, but Tactic.Simp as t-meta)
(2) ensuring "Algebra/File.lean" does not get labelled "t-algebraic-geometry"
(Can you handle this by using the Name API more? I presume it has all the logic with prefixes already...)
(3) allowing for multi-level inclusions in a general way
(4) separating the core logic and the mapping, which implies an environment extension, macros to manipulate this list etc.
The shell script dealt with these by

performing one preprocessing step to handle "Tactic/Linter", and
doing a simple matching of root directory to label name
disallowing multi-part directories, other than that
defining both the mapping and the logic in the same script.

I wonder if the new script's complexity is already necessary. (That said, reading this in detail will be a good way for me to learn more about Lean programming.)
I do like the self-tests, these are great. Another thought I had was validating the script's configuration. Because it's all in Lean, you can check for typos (e.g. "." vs "/"), warn if the label rules and the root directories on disk do not match (on both directions), etc. this is much nicer than in shell, and definitely useful.

This PR contains both the shell script and the lean one: I am closing this, since there are two separate PRs now, one with the lean script (#15938) and one with the shell script (#15848, probably closed in favour of the Lean one).


OS X - Use 64-bit inode stat and dirent functions

This updates the stat and dirent family of types and functions (dirent.h and sys/stat.h) to use the newer 64-bit inode versions.  These functions are the default for C compiled code on OS X > 10.5 and provide extra fields and longer filenames.
This also removes the 32-bit inode versions as I believe they are intended for compatibility with binaries build pre 64-bit inode OS X.  I would think all new code should use 64-bit inode versions.
But just in case that isn't preferred, I do have two other versions of this PR that allows:

selection of 64-bit or 32-bit, configurable at compile time, or
both 64-bit and 32-bit coexist, where 32-bit is selected by import core.sys.osx.sys.stat_ino32

Ah, didn't think OS X 32-bit would have a problem because iOS 32-bit uses 64-bit inodes.

32-bit functions need addition mangling to use modern OS X __DARWIN_UNIX03 functions.  Should pass 32-bit testers now (fingers crossed).

But just in case that isn't preferred, I do have two other versions of this PR that allows:
selection of 64-bit or 32-bit, configurable at compile time, or

Just select the 64-bit versions as we do on every other platform.

Ah, didn't think OS X 32-bit would have a problem because iOS 32-bit uses 64-bit inodes.

It shouldn't, please try to fix this. I'd guess that you need to replace c_longs with longs.

@MartinNowak - the current commit is correct for both -m64 and -m32 and matches output of clang.  The original 32-bit issue was that I missed the __DARWIN_ALIAS macro on some of the prototypes in the C header.  For -m32 code, this appends "$UNIX2003" to function symbols.
BTW I notice while looking through the MacOSX SDK header files that many function prototypes have __DARWIN_ALIAS macro. Has anybody thought to review D OS X prototypes so that the modern API is used?  As-is, could lead to subtle difference between D and C code.  @jacob-carlborg are you aware of this?

@smolt no. But I looked up the __DARWIN_ALIAS macro to see what it actually does and found this in the documentation [1].
"Because the _LP64_ environment only supports UNIX03 semantics it causes __DARWIN_UNIX03 to be defined, but causes __DARWIN_ALIAS to do no symbol mangling"
The test below shows as well that the mangling only occurs when building for 32bit.
$ cat main.c
#include <time.h>

int main (int c, char** v)
{
    long a = timezone;
    return 0;
}
$ clang main.c -o main && nm main
0000000100000000 T __mh_execute_header
0000000100000f70 T _main
                 U _timezone
                 U dyld_stub_binder
$ clang main.c -o main -m32 && nm main
00001000 T __mh_execute_header
00001f80 T _main
         U _timezone$UNIX2003
         U dyld_stub_binder

[1] http://www.opensource.apple.com/source/xnu/xnu-1456.1.26/bsd/sys/cdefs.h

Yup, man 5 compat has good info too.
There is a lot of stuff going on in cdefs.h.  It appears to me 64-bit functions are mostly without special mangling, although select and pselect also get a "$1050" suffix due to __DARWIN_1050 macro.  Here though we might want to make the unlimited select version with "$DARWIN_EXTSN" suffix the default.
$ man 2 select
...
COMPATIBILITY
     select() now returns with errno set to EINVAL when nfds is greater
     than FD_SETSIZE.  Use a smaller value for nfds or compile with
     -D_DARWIN_UNLIMITED_SELECT.

Seems like a review of OS X declarations would be good.  I'll catch what I can as I poke around.  I just noticed last night that core.stdc.time CLOCKS_PER_SEC should be 1_000_000 instead of 100 as of OS X 10.5.

ping

Auto-merge toggled on


add instructions on using the git icon

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


Search broken links, images and videos in repositories

[ ] Developer Guidelines - eoscostarica.io
[ ] DevOps- https://github.com/edenia/openstack-docs
[ ] DevOps - https://github.com/edenia/openstack-docs/blob/master/Kubernetes.md
[ ] DevOps - What is a Container?
[ ] Open Source Projects - https://eos-foundation.eosio.cr - WARNING
[ ] Open Source Projects - https://notarize.eosio.cr/dashboard/notary
[ ] Backend Boilerplate - hasura
[ ] Node installation -  Example
[ ] Block Explorers - https://eospark.com/
[ ] Block Explorers - https://glass.cypherglass.com/map/main/top50
[ ] Block Explorers - https://monitor.telosfoundation.io/
[ ] EOS Podcast - EOS Radio
[ ] EOS Podcast - EOS Dublin
[ ] EOS Podcast - EOS Dapp Stars

@AngeloCG97 I hope you are going well. In this issue description I wrote all the links that I found broken or with some error in the opening or referring moment, so, I would appreciate if you can instruct me to to know how to get the correct links or well if you can tell me who can I ask for that information.

@AngeloCG97 I hope you are going well. In this issue description I wrote all the links that I found broken or with some error in the opening or referring moment, so, I would appreciate if you can instruct me to to know how to get the correct links or well if you can tell me who can I ask for that information.


MC-9891 Update subscribed catalogue UI due to breaking core changes

Note: this depends on MauroDataMapper/mdm-resources#71

Update admin setup forms to use Angular reactive forms
Add new connection type field to add/edit subscribed catalogue
Display connection type of each subscribed catalogue in the list view
Handle case where published model type is not known
Display published data model dates
Update Subscribe Data Model dialog to use Angular reactive forms
Send additional properties during subscribed model creation - content link and/or importer

Screenshots
Admin screen of subscribed catalogues with subscribed catalogue types:

Inclusion of dates from published data models:

Updates to subscribe dialog:

I've noticed the backend error text isn't very user friendly when selecting an incompatible model content type and importer to subscribe to, I'll try to update this.

Also looking at the published models ordering on the backend as that seems out of order.


Instagram reels not working

Everything working fine except reels in instagram, tab goes unresponsive everytime.

Sometimes it come back after 3-4 reels it stops responding.

Having somewhat same problem. It lags while browsing videos on youtube or facebook. Felt like it had some issues with gpu drivers (not sure) I'm using AMD & using the latest AVX2 mini installer

Having somewhat same problem. It lags while browsing videos on youtube or facebook. Felt like it had some issues with gpu drivers (not sure) I'm using AMD & using the latest AVX2 mini installer

I have a intel laptop with nvidia mobile gpu. I have tried brave and opera but same issue. Maybe it's a hardwere issue then.

Having somewhat same problem. It lags while browsing videos on youtube or facebook. Felt like it had some issues with gpu drivers (not sure) I'm using AMD & using the latest AVX2 mini installer

I have a intel laptop with nvidia mobile gpu. I have tried brave and opera but same issue. Maybe it's a hardwere issue then.

yeah might be a driver issue


Building an iso does not work (mismatched rpm error)

This can be reproduced by running the following command:
podman run \
    --rm \
    -it \
    --privileged \
    --pull=newer \
    --security-opt label=type:unconfined_t \
    -v $(pwd)/output:/output \
    -v /var/lib/containers/storage:/var/lib/containers/storage \
    quay.io/centos-bootc/bootc-image-builder:latest \
    --type iso --target-arch arm64 \
    --local \
    quay.io/bootc-extension/httpd:latest

Which uses the "quay.io/bootc-extension/httpd:latest" test image which is simply the httpd example from https://gitlab.com/bootc-org/examples
podman run \
    --rm \
    -it \
    --privileged \
    --pull=newer \
    --security-opt label=type:unconfined_t \
    -v $(pwd)/output:/output \
    -v /var/lib/containers/storage:/var/lib/containers/storage \
    quay.io/centos-bootc/bootc-image-builder:latest \
    --type iso --target-arch arm64 \
    --local \
    quay.io/bootc-extension/httpd:latest
Trying to pull quay.io/centos-bootc/bootc-image-builder:latest...
Getting image source signatures
Copying blob sha256:d2d335e3ff36eb2c14653641ee5af2db67eaa148b21142946b4c7f2221bf9bf7
Copying blob sha256:1ff5b3d378b54a54652cc50bee9ff5bac849d28efe63a2f8ab0d0f1853110e57
Copying blob sha256:d1d88850a0e9b4b8d8f3608b8ea75570f678c421aea4235f5da2d980a0c8079a
Copying config sha256:7e40d33bb69963f79d289b9a93822dac304f12c8c557dbb9db901b04fd2e0ab3
Writing manifest to image destination
Generating manifest manifest-iso.json
ERRO[0000] Unable to write container event: write unixgram @f58c0->/run/systemd/journal/socket: sendmsg: no such file or directory
ERRO[0009] Unable to write exec died event: "write unixgram @f58c0->/run/systemd/journal/socket: sendmsg: no such file or directory"
ERRO[0000] Unable to write container event: write unixgram @29261->/run/systemd/journal/socket: sendmsg: no such file or directory
ERRO[0000] Unable to write exec died event: "write unixgram @29261->/run/systemd/journal/socket: sendmsg: no such file or directory"
DONE
Building manifest-iso.json
starting -Pipeline source org.osbuild.containers-storage: 391c942482ae423508b29ec3953f4afaa45a1f1cf1775d323e9eaf6a27fb39ae
Build
  root: <host>
Pipeline source org.osbuild.curl: f19ff56226796b748d2499a94f439cdf794329e7f5cc3fcea5d0f1638ca5f335
Build
  root: <host>
Traceback (most recent call last):
  File "/usr/bin/osbuild", line 33, in <module>
    sys.exit(load_entry_point('osbuild==118', 'console_scripts', 'osbuild')())
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3.12/site-packages/osbuild/main_cli.py", line 179, in osbuild_cli
    manifest.download(object_store, monitor, args.libdir)
  File "/usr/lib/python3.12/site-packages/osbuild/pipeline.py", line 418, in download
    source.download(mgr, store, libdir)
  File "/usr/lib/python3.12/site-packages/osbuild/sources.py", line 44, in download
    reply = client.call_with_fds("download", args, fds)
            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3.12/site-packages/osbuild/host.py", line 384, in call_with_fds
    raise error
osbuild.host.RemoteError: RuntimeError: checksum mismatch: sha256:0053d63a5eb0bc399e2e56a2599a1a09dca20c5bcac36f713a56fec46abac391 https://mirror.cpsc.ucalgary.ca/mirror/centos-stream/9-stream/AppStream/aarch64/os/Packages/perl-Getopt-Long-2.52-4.el9.noarch.rpm
   File "/usr/lib/python3.12/site-packages/osbuild/host.py", line 268, in serve
    reply, reply_fds = self._handle_message(msg, fds)
                       ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3.12/site-packages/osbuild/host.py", line 301, in _handle_message
    ret, fds = self.dispatch(name, args, fds)
               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3.12/site-packages/osbuild/sources.py", line 123, in dispatch
    self.fetch_all(SourceService.load_items(fds))
  File "/usr/lib/osbuild/sources/org.osbuild.curl", line 142, in fetch_all
    for _ in executor.map(self.fetch_one, *zip(*amended)):
  File "/usr/lib64/python3.12/concurrent/futures/_base.py", line 619, in result_iterator
    yield _result_or_cancel(fs.pop())
          ^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib64/python3.12/concurrent/futures/_base.py", line 317, in _result_or_cancel
    return fut.result(timeout)
           ^^^^^^^^^^^^^^^^^^^
  File "/usr/lib64/python3.12/concurrent/futures/_base.py", line 456, in result
    return self.__get_result()
           ^^^^^^^^^^^^^^^^^^^
  File "/usr/lib64/python3.12/concurrent/futures/_base.py", line 401, in __get_result
    raise self._exception
  File "/usr/lib64/python3.12/concurrent/futures/thread.py", line 58, in run
    result = self.fn(*self.args, **self.kwargs)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/osbuild/sources/org.osbuild.curl", line 190, in fetch_one
    raise RuntimeError(f"checksum mismatch: {checksum} {url}")

Error: cannot run osbuild: running osbuild failed: exit status 1
2024/04/29 13:25:13 error: cannot run osbuild: running osbuild failed: exit status 1

The ISO build inspects the base bootable container to use the rpm repositories to build the ISO from the same content sources that the image itself uses.  It looks like the build selected an out of sync rpm mirror where the file https://mirror.cpsc.ucalgary.ca/mirror/centos-stream/9-stream/AppStream/aarch64/os/Packages/perl-Getopt-Long-2.52-4.el9.noarch.rpm is empty and it's failing the checksum validation.

@achilleas-k
Ah, so from my understanding, is that I have to re-build the image which would pull the correct mirrors, in order to build with bootc-image-builder?

@achilleas-k
Ah, so from my understanding, is that I have to re-build the image which would pull the correct mirrors, in order to build with bootc-image-builder?

Maybe.  It might select the same mirror during depsolve (through libdnf) or it might not.

@achilleas-k
Ah, so from my understanding, is that I have to re-build the image which would pull the correct mirrors, in order to build with bootc-image-builder?

Maybe. It might select the same mirror during depsolve (through libdnf) or it might not.

I've rebuilt the example image using --no-cache and it built successfully again, but encountered the same issue unfortunately.
Is there any way to have it check other mirrors for the perl package?

Is there any way to have it check other mirrors for the perl package?

You could modify the base container and set a baseurl for the Appstream repo config to a known good mirror as a workaround.  Not really a long-term solution but should work around the issue for now.

OK, we investigated more, and found out that the mirror denylists curl that we use for downloading RPMs. I came up with a workaround: https://github.com/osbuild/osbuild/pull/1765

https://github.com/osbuild/osbuild/pull/1766 is now pulled into the latest bootc-image-builder. It will help with this particular repository problem. :)


Add support for running inside a VM with vfio-noiommu

This PR is required for https://github.com/openshift/sriov-network-operator/pull/369.
This PR enables the mapping of a no-iommu vfio device into a container.
Associated system configuration enables no-iommu for the vfio-pci driver.
This PR is required to allow Kubernetes to run in a virtual environment that does not provide a virtualized iommu.  The initial target environment is OpenStack.  OpenStack Nova does not currently provide a virtualized iommu. Support for vfio-noiommu was added to linux a few years ago with the caveats outlined below...
`There is really no way to safely give a user full access to a DMA
capable device without an IOMMU to protect the host system.  There is
also no way to provide DMA translation, for use cases such as device
assignment to virtual machines.  However, there are still those users
that want userspace drivers even under those conditions.  The UIO
driver exists for this use case, but does not provide the degree of
device access and programming that VFIO has.  In an effort to avoid
code duplication, this introduces a No-IOMMU mode for VFIO.
This mode requires building VFIO with CONFIG_VFIO_NOIOMMU and enabling
the "enable_unsafe_noiommu_mode" option on the vfio driver.  This
should make it very clear that this mode is not safe.  Additionally,
CAP_SYS_RAWIO privileges are necessary to work with groups and
containers using this mode.  Groups making use of this support are
named /dev/vfio/noiommu-$GROUP and can only make use of the special
VFIO_NOIOMMU_IOMMU for the container.  Use of this mode, specifically
binding a device without a native IOMMU group to a VFIO bus driver
will taint the kernel and should therefore not be considered
supported.  This patch includes no-iommu support for the vfio-pci bus
driver only.`
In the future, the current QEMU machine type in use for OpenStack is i440fx.  The
machine type should be switched to Q35 in the future.  The Q35 machine provides
a virtualized iommu implementation and will obsolete this patch.
In summary, the use of noiommu introduces security concerns, but the performance
boost provided by vfio-pci can be justified in many cases.

/lgtm

/cc @ahalim-intel @adrianchiris @martinkennelly @moshe010 PTAL

Second the three points made by @moshe010 especially emphasizing the addition of documentation. PR looks good. I am currently testing it locally. Thank you for this.

@moshe010 @martinkennelly Docs pushed

LGTM overall besides nits / CNI Question.

@martinkennelly Aplogies, forgot to document the SR-IOV CNI situation. I will include an example that I have been using for testing.  Basically, just remove the annotations...
  annotations:
    k8s.v1.cni.cncf.io/networks: sriov-net1

and keep the resources...
    resources:
      requests:
        intel.com/intel_sriov_netdevice: '1'
      limits:
        intel.com/intel_sriov_netdevice: '1'
```
unchanged.

@adrianchiris could you take a look at the new doc update?


Please also generate documentation for generic type

Hello Keisuke,
See here, it requires that every generic type parameter have its own doc string.
/// <summary>
    /// A sample generic class.
    /// </summary>
    /// <typeparam name="S">The first generic type parameter.</typeparam>
    /// <typeparam name="T">The second generic type parameter.</typeparam>
    public class Class1<S, T>
    {
    }

Thanks

@MZhoume I just released, please check v0.1.0

@haolly @Lucidiot I added generic type to vscode-docomment v0.1.0, please check it


Bug: sometime test failed

Describe the bug
Sometime test failed:
https://github.com/8xFF/atm0s-sdn/actions/runs/9996545528/job/27631167978?pr=168

[ ] enable logs for tests
[ ] fix error

After we retry test, it success.
https://github.com/8xFF/atm0s-sdn/actions/runs/10001982292

It related to multi-interfaces


New package: HJSON v1.0.0

Registering package: HJSON
Repository: https://github.com/fmatesa/HJSON.jl
Created by: @fmatesa
Version: v1.0.0
Commit: da3f6a6dd03332a8bbab8c9957ee515108c43b08
Git reference: HEAD

@goerz Ok now it should be fine. Sorry for the mess.

Sorry for the mess.

That's okay, but next time, try to carefully read the guidelines and messages from the bot and plan ahead, so that it doesn't take quite as many attempts.
In any case, the three-day waiting period still applies for this registration. After it ends, you will have to go to the #pgk-registration channel on Slack and ask for a manual merge.


[DOC-3983]

Harness Developer Pull Request
Thanks for helping us make the Developer Hub better. The PR will be looked at
by the CODEOWNERS.
What Type of PR is This?

[ ] Issue
[X] Feature
[ ] Maintenance/Chore

If tied to an Issue, list the Issue(s) here:

Issue(s)

House Keeping
Some items to keep track of. Screen shots of changes are optional but would help the maintainers review quicker.

[ ] Tested Locally
[ ] Optional Screenshot.

 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.

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step behind the Harness VPN and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app. Current Draft URL is: https://65d4e563379ed7049bb70cbc--harness-developer.netlify.app

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step behind the Harness VPN and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app. Current Draft URL is: https://66317878d551ba3f5c166d5f--harness-developer.netlify.app


files with file: <my-relative-file-path> always returns exception

Describe the bug
I'm trying copy of some files from repo running GitLabForm job:
config_version: 3

gitlab:
  url: https://<own-ce-gitlab>

projects_and_groups:
  "*":
    files:
      "LICENSE.md":
        file:
          - "LICENSE.md"
        branches:
          - "main"
        commit_message: "chore(license): add LICENSE.md according to with SISL 1.4"
        overwrite: false

facing exception:
Processing section 'files'
Processing file 'LICENSE.md' in branch 'main'
Warning: Error occurred while processing project reusable-ci/templates/fork-me, exception:
[Errno 2] No such file or directory: "['LICENSE.md']"

GitLabForm version
3.3.1
GitLab version
15.6.0

ah sorry just realized the issue, i've used array 🤭 now it works, great extension 👍
config_version: 3

gitlab:
  url: https://<own-ce-gitlab>

projects_and_groups:
  "*":
    files:
      "LICENSE.md":
        file: "assets/LICENSE.md"
        branches:
          - "main"
        commit_message: "chore(license): add LICENSE.md according to with SISL 1.4"
        overwrite: false


Need more samples

Crunching down 6 days (~18GB) of reports only yielded:
Analyzing Navigational Status: 100%|██████████| 1124/1124 [00:01<00:00, 931.42it/s]
Distribution of Navigational Status: {'Under way using engine': 971, 'Restricted maneuverability': 72, 'Under way sailing': 12, 'Engaged in fishing': 55, 'Moored': 14}

Added 3 more days in summer:
Analyzing Navigational Status: 100%|██████████| 4947/4947 [00:08<00:00, 607.00it/s]
Distribution of Navigational Status: {'Under way using engine': 2873, 'At anchor': 1, 'Engaged in fishing': 1591, 'Moored': 36, 'Under way sailing': 44, 'Reserved for future amendment [HSC]': 110, 'Restricted maneuverability': 292}
(Weird: The number of vessels doubled with each added 3 days that doesn't add up (6 days: 1124, 9 days: 2038, 12 days: 4947)), investigationg...

Added 3 more days in summer:
Analyzing Navigational Status: 100%|██████████| 3029/3029 [00:04<00:00, 611.22it/s]
Distribution of Navigational Status: {'Under way using engine': 1428, 'Engaged in fishing': 1516, 'Moored': 4, 'Reserved for future amendment [HSC]': 42, 'Restricted maneuverability': 30, 'Under way sailing': 9}

Added 3 more days in summer:
Analyzing Navigational Status: 100%|██████████| 10298/10298 [00:54<00:00, 188.44it/s]Distribution of Navigational Status: {'Under way using engine': 5645, 'At anchor': 1, 'Engaged in fishing': 4029, 'Moored': 59, 'Under way sailing': 54, 'Reserved for future amendment [HSC]': 163, 'Restricted maneuverability': 347}


Having a stack with id = * results in ERROR: no compatible stacks among provided buildpacks

What happened?
Trying to pack build with this buildpack, v0.4.0
Try to run integration tests here: https://github.com/paketo-buildpacks/go/pull/558/commits/09aa607690e4cbb62dcf8756c4a7bc5913c90ac6
What was the actual behavior?
results in ERROR: no compatible stacks among provided buildpacks
Thoughts
Could be related to the stacks change here: https://github.com/paketo-buildpacks/git/compare/v0.3.0...v0.4.0#diff-5f54cb49d0e28117084fad482c0daf89502d4ecb329230071fcf78e56dc939b3
This seems like a bigger issue?

This seems like a bug in pack builder create since * is an allowed wildcard stack ID: https://github.com/buildpacks/spec/blob/main/buildpack.md#buildpack-implementations.

Is this observable in the latest pack version? (0.24)


Rails/SaveBang is issuing warning regardless of the actual type on the receiver

Hi there!
Expected behavior
This is obviously not an ActiveRecord instance, the update is fine as it is.
$ cat save.rb
h = {a: 1}
h.update(b: 1, c: 2)

Actual behavior
$ bundle exec rubocop save.rb
Inspecting 1 file
C

Offenses:

save.rb:1:1: C: [Correctable] Style/FrozenStringLiteralComment: Missing frozen string literal comment.
h = {a: 1}
^
save.rb:2:3: C: [Correctable] Rails/SaveBang: Use update! instead of update if the return value is not checked.
h.update(b: 1, c: 2)
  ^^^^^^

1 file inspected, 2 offenses detected, 2 offenses autocorrectable

Steps to reproduce the problem
See above.
RuboCop version
$ bundle exec rubocop -V
1.56.3 (using Parser <IP_ADDRESS>, rubocop-ast 1.29.0, running on ruby 3.2.2) [arm64-darwin22]
  - rubocop-rails 2.21.2

I'm facing probably similar issue when using Stripe gem, which uses methods like .create, e.g.:
Stripe.api_key = 'sk_test_51I4UMLE5DzVbS13sj7QTJMi8skvfRaObABhbHvM0IDYUEPBOlCWz1gHsSy50kwZCUUhEiPNsYZh3Zxmrv1TGFcfv00YS4ob3e9'

Stripe::Customer.create({
  name: 'Jenny Rosen',
  email<EMAIL_ADDRESS>})


minor bug fix for paypal flow

merging this to keep moving on paypal preapproval flow. fyi @xdamman

Fyi, tests passed https://circleci.com/gh/OpenCollective/opencollective-website/3379 (for some reason, github isn't updated circleci links)


"Florieni" is listed in the drop-down menu

Description:
"Florieni" is listed in the drop-down menu alongside its corresponding county and commune, according to the law
Precondition:
The website is up an running.

Step 1
Type "Florieni" in the search bar.

Expected results
The location is listed in the drop-down menu as "Florieni, Argeș (Albeștii de Argeș)".


notarget No matching version found for<EMAIL_ADDRESS>

IMPORTANT: Pl

ease use the following link to create a new issue:
https://new-issue.vuejs.org/?repo=vuejs/vue-cli
If your issue was not created using the app above, it will be closed immediately.
中文用户请注意：
请使用上面的链接来创建新的 issue。如果不是用上述工具创建的 issue 会被自动关闭。

See https://github.com/vuejs/vue-cli/issues/2494.


Adapt configure-admission.sh for new extension releases with changed value names for Helm charts.

How to categorize this PR?

/area control-plane
/area dev-productivity
/kind enhancement
What this PR does / why we need it:
The newly introduced extension controller of the gardener-operator expects Helm charts for extension admission controllers to have values without the global section. The configure-admission.sh script has been extended to recognise if the latest extension release already has been migrated to be used this way and to provide suitable values.
Additionally the extension controller always sets the value .gardener.virtualCluster.enabled=true to allow deployments like here in the local gardener-extensions without virtual Garden cluster to override the default.
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Release note:

Adapt `configure-admission.sh` for new extension releases with changed value names for Helm charts.

/cc @kon-angelo

/retest

Thanks 🙂
/approve

/lgtm


Improve ockam tcp-outlet create --help text (clap command)

Current behavior
When a user runs ockam tcp-outlet create --help they are presented with the following help information.

Desired behavior
Instead, the help text should instead show the following: Create a TCP Outlet
Implementation details
You can change the Rust doc comment for the CreateCommand struct in this file to make this change.

Some tips for newcomers:

Create a new branch for the issue you are working on (don't push directly to your fork's develop branch)
In the PR description, include the issue that's being solved
Run cargo fmt. You can configure the editor to run it automatically every time a file is saved
Run cargo clippy to make sure the code compiles + follows rust standards/best practices
You don't need to keep your branch updated with develop until there is a merge conflict. If you still want to update it, use git rebase develop instead of git merge develop

We love helping new contributors! ❤
If you have questions or need help as you explore, please join us on Discord. If you're looking for other issues to contribute to, please checkout our good first issues.

I'd like to contribute, please assign me this issue

@ShatilKhan That's awesome, this is all yours. Please let us know if you have any questions as you explore. You can also ask questions on the contributors discord https://discord.gg/RAbjRr3kds
Also, please associate your PR and issue using this technique: https://docs.github.com/en/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue


WIP: Support for mhcflurry - Take #2

Re-based @timodonnell's #45 onto the latest code to revive the integration possibility.
TODO:

[ ] cut a mhcflurry release to be distributed on PyPI (so that we can rely on some stable CLI/APIs)
[ ] add mhcflurry training procedure to the Travis job (otherwise tests fail)

This change is

This may be easier once my refactor of MHCflurry is done. This will include pre-trained models and a pip release. I'm hoping to have that merged by end of this week but it will depend on how our cloud infra experiments go

thanks, @timodonnell! I will keep an eye on your refactoring for a few days, then. If you get busy with other stuff, I might go ahead and get something going just to get the biokepi stage ready for mhcflurry and save some time :+1:

Going to close this and the other MHCflurry PR until Tim and I finish rearranging MHCflurry over the next few weeks.


Zl/ingestion fixes

Fixing some issues that the job consolidation in PR #279 caused.
Main issue was that each subgraph consumed from the same consumer group, which caused issues for jobs involving more than 1 feature set.
To remedy this, in this fix, we only have a single read from source node, and fan out from there.