tesseract 4.1.0 recognize the number 1 as lowercase letter l

Before you submit an issue, please review the guidelines for this repository.
Please report an issue only for a BUG, not for asking questions.
Note that it will be much easier for us to fix the issue if a test case that
reproduces the problem is provided. Ideally this test case should not have any
external dependencies. Provide a copy of the image or link to files for the test case.
Please delete this text and fill in the template below.

Environment
Mac OS
tesseract 4.1.0
leptonica-1.78.0
libgif 5.1.4 : libjpeg 9c : libpng 1.6.37 : libtiff 4.1.0 : zlib 1.2.11 : libwebp 1.0.3 : libopenjp2 2.3.1
Found AVX2
Found AVX
Found SSE
/usr/local/bin/tesseract /Users/xxx/Downloads/ocrtest2.jpeg /Users/xxxx/Downloads/ocrtest2 --oem 1 --psm 3 -l eng+chi_sim
Current Behavior:
recognize the number 1 as lowercase letter l
统一 社会 信用 代码 92331002MA2DTClp6l
Expected Behavior:
recognize the number 1 as 1
Suggested Fix:

try to use a larger model. it improved the results for me.


(FACT-2827) Reset ttls settings on OptionStore reset

Unit tests were failing when facter.conf contained ttls settings.

CLA signed by all contributors.


Register: unable to resolve relative import with oxc-resolver

Context
When updating @swc-node/register from version 1.10.0 to 1.10.2, relative typescript imports are no longer resolved.
When using a relative import, I get:
node:internal/modules/run_main:129
    triggerUncaughtException(
    ^
Error: Cannot find module './shared': ./shared cannot be resolved in file:///home/runner/work/rust-cdk-serverless/rust-cdk-serverless/iac/index.ts
    at resolve (file:///home/runner/work/rust-cdk-serverless/rust-cdk-serverless/node_modules/.pnpm/@swc-node+register@1.10.2_@swc+core@1.5.0_@swc+types@0.1.6_typescript@5.5.3/node_modules/@swc-node/register/esm/esm.mjs:208:15)
    at async nextResolve (node:internal/modules/esm/hooks:866:22)
    at async Hooks.resolve (node:internal/modules/esm/hooks:304:24)
    at async handleMessage (node:internal/modules/esm/worker:196:18)

errored PR: https://github.com/fargito/rust-cdk-serverless/pull/287
CI job: https://github.com/fargito/rust-cdk-serverless/actions/runs/9821902780/job/27118080233?pr=287

Investigation
The issue has probably been introduced by #798, more precisely here.
I'm a bit puzzled, because the call to resolver.async is done with the correct arguments according to the oxc-resolver docs:

directory must be an absolute path to a directory where the specifier is resolved against. For CommonJS modules, it is the __dirname variable that contains the absolute path to the folder containing current module. For ECMAScript modules, it is the value of import.meta.url. In my case, it gives the expected value, i.e. /home/runner/work/rust-cdk-serverless/rust-cdk-serverless/iac
identifier: in my case it is ./shared

This looks correct according to the oxc-resolver docs, but oxc-resolver cannot find it. Maybe the ts config is incorrectly passed to the resolver?
I will try and set up a minimal reproduction in the coming days.

Unfortunately, I can't use the latest version of register because oxc-resolver doesn't support Yarn PnP: https://github.com/oxc-project/oxc-resolver/issues/53 . Even a simple import in my setup e.g. import { $} from 'execa' will fail:
node:internal/modules/run_main:129
    triggerUncaughtException(
    ^
Error: Cannot find module 'execa': execa cannot be resolved in file:///Users/mitran/Projects/vite-storybook-boilerplate/bin/bootstrap.ts
    at resolve (file:///Users/mitran/Projects/vite-storybook-boilerplate/.yarn/unplugged/@swc-node-register-virtual-f17b414b8d/node_modules/@swc-node/register/esm/esm.mjs:208:15)
    at async nextResolve (node:internal/modules/esm/hooks:866:22)
    at async Hooks.resolve (node:internal/modules/esm/hooks:304:24)
    at async handleMessage (node:internal/modules/esm/worker:196:18)

Node.js v20.15.0

@psychobolt I'm using pnpm, so maybe it is a separate issue

I have set up a minimal reproduction: https://github.com/fargito/swc-node-relative-import-issue-repro

Thanks @Brooooooklyn! This fixed it for me.


Exception occurs while the 'Xpand.ExpressApp.Security.XpandSecurityModule' customizes TypesInfo: Sequence contains no matching element

Hello Tolis,
Since today i have the following error.
I haven't changed anything related to the security.
I just created an new class. Do you have any idea because i have no idea where to look.
I happens only on the win client on the start.

Type:       InvalidOperationException
Message:    Exception occurs while the 'Xpand.ExpressApp.Security.XpandSecurityModule' customizes TypesInfo: Sequence contains no matching element
Data:       0 entries
Stack trace:
at DevExpress.ExpressApp.ApplicationModulesManager.DoCustomizeTypesInfo(ITypesInfo typesInfo)
at DevExpress.ExpressApp.ApplicationModulesManager.Load(ITypesInfo typesInfo, Boolean loadTypesInfo)
at DevExpress.ExpressApp.XafApplication.Setup(String applicationName, IList`1 objectSpaceProviders, ApplicationModulesManager modulesManager, ISecurityStrategyBase security)
at DevExpress.ExpressApp.XafApplication.Setup()
at KBA_ADDON.Win.Program.Main() in C:\KBA-NotaSys\Devs\PROD\KBA_ADDON\KBA_ADDON.Win\Program.cs:line 75
----------------
InnerException:
		Type:       InvalidOperationException
		Message:    Sequence contains no matching element
		Data:       0 entries
		Stack trace:

at System.Linq.Enumerable.First[TSource](IEnumerable1 source, Func2 predicate)
at Xpand.Persistent.Base.General.XpandModuleBase.AssignSecurityEntities()
at Xpand.Persistent.Base.General.XpandModuleBase.CustomizeTypesInfo(ITypesInfo typesInfo)
at Xpand.ExpressApp.Security.XpandSecurityModule.CustomizeTypesInfo(ITypesInfo typesInfo)
at DevExpress.ExpressApp.ApplicationModulesManager.DoCustomizeTypesInfo(ITypesInfo typesInfo)
InnerException is null

I use the version : 18.2.301.8

Sorry ! Case solved. Is seems that my model is correpted somehow.
The UserType and RoleType were empty in the WinApplication.
BR
ISA


Study Group Planner

We are working on planning sessions for the remainder of this fall and for next spring. The agenda is still very much in draft form, so any input is very much appreciated.
Fall 2015

Week of
Date
Session

Nov. 16
Nov. 19
GitHub Pages and Jekyll

Nov. 23
N/A
Thanksgiving - No session

Nov. 30
Dec. 3
Lighting Talk Session

Dec. 7
TBD
End of Semester - Hacky Hour / Spring Planner

Dec. 14
N/A
Finals - No Session

Dec. 21
N/A
Winter Break - No Session

Dec. 28
N/A
Winter Break - No Session

Spring 2016 (draft - everything is tentative)

Week of
Date
Session

Jan. 4
N/A
Winter Break - No Session

Jan. 11
N/A
Winter Break - No Session

Jan. 18
TBD
Hacky Hour

Jan. 25
TBD
Intro to GitHub

Feb. 1
TBD
Using Jupyter

Feb. 8
TBD
Git Advanced

Feb. 15
TBD
GitHub Pages

Feb. 22
TBD
Using Jekyll for Publishing

Feb. 29
TBD
OPEN

Mar. 7
N/A
Spring Break - No Session

Mar. 14
TBD
OPEN

Mar. 21
TBD
OPEN

Mar. 28
TBD
OPEN

Apr. 4
TBD
OPEN

Apr. 11
TBD
OPEN

Apr. 18
TBD
OPEN

Apr. 25
TBD
Lighting Talk Session

May 1
TBD
Hacky Hour

The rest of this year looks well booked up (yay!) and I agree that we should repeat some of our content in the new year. Hoping we'll have some new faces joining the familiar ones.
As for additional content, I'd like to propose:

Work along for reveal.js HTML based slides

I quite like reveal.js since it makes it very quick to create a presentation that looks reasonably good. There isn't a lot of control on styling, which means you're pretty much forced into concise slides that favor images over text
You can write HTML to make the slides, but I'd also show how to write the slides in Markdown and then use pandoc to convert them to reveal.js HTML or other formats (Beamer, other HTML slide formats, etc.)

Work along for programatically building virtual machine (VM) images to encapsulate your software for distribution or testing using Vagrant

I've found it very useful to distribute VMs that contain some of my software with large lists of dependencies, especially for Windows users who don't have access to or know how to setup a compiler. I need to learn it anyway, so I might as well make a lesson on it

@ceholden great ideas! do you have a preference for dates? We could do the reveal.js session after the git advanced and the Vagrant after the break. Thoughts?

@tomhohenstein I don't have any plans for the dates scheduled right now, so put me where ever and I'll speak up if I need to reschedule? There's some possible work related travel currently up in the air for the spring...
I also want to add another proposed lesson -- Makefiles for data

semester is almost over and each session was added in a respective issues - closing issue


Ball movement looks laggy

The ball looks very laggy because refill the screen dark every time to remove its past trajectory. Need to find an alternative way to remove the trajectory.

I added double buffer and activate hardware surface in full screen. It looked much faster when before scaling to 15 in MBP. After scaling the game looks laggy again.

The game looks smoother again after I set the screen size to 1600x1000. The game still fills the full screen on 15 in MBP. The reason is unknown. But I will close this issue since the problem is solved.


Optimize the 128-bit vectorization of Poly1305 MAC for PowerPC

This issue offers two tips that boost the performance of vectorized code significantly on PowerPC architecture in addition to a little boost for other architectures like x86_64.
I've used Poly1305 MAC to observe the performance loss and spot the bottleneck at assembly level while keeping in mind that POWER8/POWER9 processors can pipeline down to 6 vector instructions simultaneously to achieve a reciprocal throughput of 0.5 for the used vector instructions. I've used son_ibm_ppc branch for testing.
Tip 1:
The latency of writing to memory buffers inside the loop that iterates message blocks of authentication algorithms like Poly1305 could cause overhead for the entire function, avoiding unnecessary writing operations could eliminate the overhead and increase the performance.
I'll demonstrate the changes on Hacl_Poly1305_128.c which can be generated from Hacl.Impl.Poly1305.fst using KreMLin tool.
The function Hacl_Poly1305_128_poly1305_update() read and write to the context buffer ctx of acc offset inside the main loop, the generated assembly code updates certain fields in ctx buffer for every block iteration.
To eliminate that overhead one needs to initiate acc values in local variables before the loop procedure begin and store those variables after loop end then use the local variable for the reciprocal values inside the loop.
Note The compiler is aware that the loaded values from pre buffer are same among blocks so the generated code load those values only once before the loop start.
By applying this tip, the performance of Hacl_Poly1305_128_poly1305_update() has been increased 8% on POWER9 processor and 5.5% for x86_64 architecture (Tested on Ice Lake arch)
The change isn't tested or tuned for 256-bit vector registers since PowerPC doesn't have any.
Tip 2:
Power ISA v3.00 has introduces several instructions like extended set of vector load/store operations and vector value extraction that can be taken advantage from many functions in HACL* which can be applied by appending -mpower9-vector flag in gcc-compatible/configure
The overall performance increase of Hacl_Poly1305_128_poly1305_update() by using Power ISA v3.00 is 47% on POWER9 processor.
Note the use of -mpower9-vector flag should be optional so the vectorized code would maintain the support of older CPUs.
Benchmark numbers of Hacl_Poly1305_128_poly1305_update() on POWER9 measured by cycles per byte (cpb)

Original
Patch (Tips applied)

3.90 cpb
2.47 cpb

In my opinion, this is the best performance we can get from using C intrinsic to optimize Poly1305. To get the optimal performance one needs to add support of PowerPC to Vale so functions like Poly1305 MAC can be implemented at assembly level with verification, in this way we can have more control over execution flow and achieve higher performance by saturating the execution units. I'll open another issue to describe a potential roadmap of adding PowerPC support to Vale.

Thanks Maamoun, that's really neat! To follow up on this:

can you attach a patch for the generated C code so that we can see precisely what needs to happen?
how to detect POWER9 in configure? should I call uname or something?

Thanks!

Thanks Maamoun, that's really neat! To follow up on this:

can you attach a patch for the generated C code so that we can see precisely what needs to happen?

It can be done as shown in this variant poly1305.txt (diff file)

how to detect POWER9 in configure? should I call uname or something?

I would recommend to add -mpower9-vector flag according to a user input for build configuration since the build machine's architecture and the target architecture may vary.

Thanks @mamonet that looks great. Just to clarify, do you plan on submitting PRs that implement these two changes or are you just filing bugs in the hope that someone picks them up?
Cheers,
Jonathan

Thanks @mamonet that looks great. Just to clarify, do you plan on submitting PRs that implement these two changes or are you just filing bugs in the hope that someone picks them up?

Submitting a PR for the first patch requires some sort of familiarity for many HACL* aspects like function assurance and pre/post condition asserts, I'm at a point where I can get a working patch for the Low* template but still have some difficulty keeping up with all the aspects which need some time to grasp. I don't want to end up with a patch that miss a persistent feature or not fully compatible with the other contexts.

Thanks. @polubelova wrote this code so she (might) be able to tell us whether it's an easy fix or a more complex one
I can take care of adding something to the configure script

Thank you. Any assistance or hints would be great. I'm able to upload my first try to modify Hacl.Impl.Poly1305.fst to reflect the change if that helps the code maintainer.

It seems a tuning flags has been added to the configure without me noticing. However, I've submitted a proper configure patch in PR #455 with slight performance boost on POWER9.


Bin script

Moved the bin script to cli.js
Updated package json
Fixed broken build badge

FYI: Cli.js invokes 'server.js' (this makes things easier to test)

Pull Request Test Coverage Report for Build 17

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

Totals

Change from base Build 14:
0.0%

Covered Lines:
46

Relevant Lines:
177

💛  - Coveralls


Getting Valid Response even though connected to MITM Proxy server and installed their root certificate.

I am using
https://mitmproxy.org/ to recreate the MITM attack.
I followed all the steps mentioned but this certificate transparency library always responds true. I can share the logid if required.

Do you have a sample project with the issue you're describing?


new page: add calculator page 🧮

So interesting trinkets those ade me think a lot about the over-engineering, and I just wrote a calculator page.
Wish your CR.  <3

You could probably save some bytes by removing whitespaces


BUG Deskulpt can't handle syntax error in widget js code

When there is a syntax error in the widget js code, Deskulpt will crash.  Below is a minimal example to reproduce this bug.
const React = window.__DESKULPT__.defaultDeps.React;

// Syntax error here, misspell "const" as "conts", will crash Deskulpt
conts bannerText = "My Simple Banner";

function Banner() {
  return (

{bannerText}

  );
}

export default {
  render: () => <Banner />,
};

And is the error message produced when Deskulpt crashes. It happens when I add this widget to the widgets folder and render. I run Deskulpt with  npm run tauri dev.
error: Expected ';', '}' or <eof>
 --> \\?\C:\Users\eiger\AppData\Roaming\com.tauri.deskulpt\widgets\ok-simple-banner\src\App.jsx:3:7
  |
3 | conts bannerText = "My Simple Banner";
  | ----- ^^^^^^^^^^
  | |
  | This is the expression part of an expression statement

thread 'main' panicked at src\bundler.rs:171:21:
FATAL: Failed to parse module
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
[0406/173441.713:ERROR:window_impl.cc(121)] Failed to unregister class Chrome_WidgetWin_0. Error = 0

@Charlie-XIAO @ROMEEZHOU You might want to check this out since we are writing tests for bundler this week

The error is currently emitted into the console, seems I forgot to change that. I need to figure out how to emit as a string though.


added page to ask username from user

Description
added OnBordingPage() for asking username from the user and updating username in store.dart.
Related Issue
Fixes #7

Hey @janvig!
could you please point out where should I fix a typo? Because I couldn't find any.

Hey @sanket143 @janvig
could you please look into this pr?

give @GajjarMiten 75 points


How to forbid parse sdk from saving info to the collection "Installastion"?

Hi, we do not want to upload the data like deviceToken, version to the collection 'Installation' by parse sdk. We are recording these info by our own ways.
How to stop it?

We don't currently have any way of disabling this information, other than simply forking the SDKs and removing the associated logic, which you are more than welcome to do.


Can't use @ConditionalOnBean with a feign client

Describe the bug
Hello, i would like to use @ConditionalOnBean(MyFeignClient.class) but this seems to be always evaluated to false. I am using spring boot 3.0.1 with spring cloud 2022.0.0
@SpringBootApplication
@EnableFeignClients
public class DemoApplication {

	public static void main(String[] args) {
		SpringApplication.run(DemoApplication.class, args);
	}

}

@FeignClient(name = "myFeign")
public interface MyClient {
}

@Configuration
@ConditionalOnBean(MyClient.class)
public class MyConfig {

  @Bean("hello")
  public String hello() {
    return "hello";
  }

}

@Service
public class MyService {

  private final String hello;

  public MyService(String hello) {
    this.hello = hello;
  }
}

On service startup i end up with :
***************************
APPLICATION FAILED TO START
***************************

Description:

Parameter 0 of constructor in com.example.demo.child.MyService required a bean of type 'java.lang.String' that could not be found.

if i remove @ConditionalOnBean(MyClient.class) the application runs fine
Please find the test app attached
demo.zip

This is due to the order in which beans are being created in the Spring Context. Your bean is instantiated from a user-provided configuration while the Feign clients bean are created using a factory bean in a phase that happens later, so you cannot use them in a condition in this way. Please note that Spring Boot docs indicate that:

You need to be very careful about the order in which bean definitions are added, as these conditions are evaluated based on what has been processed so far. For this reason, we recommend using only @ConditionalOnBean and @ConditionalOnMissingBean annotations on auto-configuration classes (since these are guaranteed to load after any user-defined bean definitions have been added).


Re-addition of react-fullstack-advanced to create boilerplate

react-fullstack-advanced was missing from the create boilerplate options. I've simply re-added it.

Any update on this issue?

Not that I have heard, unfortunately.

Currently we have new structure for GraphQL CLI and in the new alpha version 4.0.0-alpha.0 Checkout new instructions and we will be happy to hear your feedback. Feel free to contact us using our Discord channel;
https://discord.gg/xud7bH

We have just released a new structure for GraphQL CLI in new alpha versions 4.0.0-alpha.XXX.
We suggest to use the init command of GraphQL CLI which was completely rewritten!
Checkout the new instructions and the migration guide on the docs and let us know your feedback.
Feel free to contact us by opening an issue or using our Discord channel;
https://discord.gg/xud7bH

I've posted the wrong Discord link, this is the correct one: https://discord.gg/xud7bH9


Fixed path for bootstrap-sass.

This fixes the issue with running gulp dev on a fresh coreos-web repo.

LGTM. thanks!


HSEARCH-1031 Fix a couple of typos in the Boosting section of the docume...

...ntation

Thanks! merged


Prevent mousewheel events while dragging for orbit/pan/zoom

In some mouse control configurations (possibly only "Solidworks") users can incidentally move their mouse wheel (zoom) while middle-click-dragging (orbit). This leads to competing unreliable and reliable channel messages being sent to the engine to move the camera, resulting in sporadic behavior like this, where the camera jumps back to the position it was in when the mouse wheel moved:
https://github.com/KittyCAD/modeling-app/assets/23481541/33324464-a5ef-47a3-b67e-cec1e4ba534b
A better long term fix is to allow these competing commands to resolve nicely so that zooms, pans, and orbits can be done simultaneously. This will be especially important for space mouse users. But a fix for the current degraded experience for Solidworks mouse control users is to disallow mousewheel events while dragging.

For reference there was a previous issue with the Solidworks settings which we were unable to reproduce or get further feedback on: https://github.com/KittyCAD/modeling-app/issues/1911

Just want to add to this, I'm still having this issue even after switching to KittyCAD controls

A better long term fix is to allow these competing commands to resolve nicely so that zooms, pans, and orbits can be done simultaneously

Would that require engine updates, or is it all on our end still?

Would that require engine updates, or is it all on our end still?

My understanding is that would require an engine-side change, but I don't know if I'm ignorant of some way we could merge the camera movements client-side.

But a fix for the current degraded experience for Solidworks mouse control users is to disallow mousewheel events while dragging

I'm going to try to make this smaller fix, I can replicate it still. Apologies for the delay.


Support to specify the hostname of the route to be created from a service

Support to specify the hostname of the route to be created from a service instead of using the cluster's internal service name
spec:
  link:
    name: Route hostname to be injected as EnvVar using fruit-backend's Route
    targetcomponentname: fruit-client
    kind: Route
    ref: fruit-backend

Wont fix


Switch processing steps to rely on OSRM

Big changes!

A re-engineering of the processing steps to rely on OSRM's path inference stuff.
Swaps the local persistence to use PostgreSQL instead of SQLite.
Places the entry point into the clear_streets.py script with a few modes (slurp and write_cartodb being the two major processes and test_mode, recreate_tables being options and backup being a thing that dumps out the tables to CSV and saves them to S3)

Things that I know work:

Slurping parts
"Fake" slurping parts (that just consumes canned data for testing)
Getting traces from OSRM

Things that I have yet to run for reals:

Writing to CartoDB.
Slurping for more than a few minutes.

I left all of the stuff that adjusts the sampling interval intact (I think) but I'd love to have a second pair of eyes on that. Other than that, I think things should generally work as advertised.

Looks good. Lots of opportunity for factoring more stuff out, but a good improvement!


Builtin models

This PR has two commit. First commit is simplification of model repo access. Second commit is a new feature that adds builtin_models param to meta-model which serves similar purpose as builtins but is of ModelRepository type and enables adding a regular textX models as a fallback for all ImportURI based scoping providers.
I'm working on a language where I have two meta-models. One is intended for end-user while the other is internal meta-model used to specify types/object referenced from the user's models. I wanted to free users of having to import these provided specifications. Actually, those spec would be deployed by the language library so it would be hard for users to know their locations, thus it is nice to be able to pre-load those specs during main meta-model construction.
Code review checklist

[ ] Pull request represents a single change (i.e. not fixing disparate/unrelated things in a single PR)
[ ] Title summarizes what is changing
[ ] Commit messages are meaningful (see this for details)
[ ] Tests have been included and/or updated
[ ] Docstrings have been included and/or updated, as appropriate
[ ] Standalone docs have been updated accordingly
[ ] Changelog(s) has/have been updated, as needed (see CHANGELOG.md, no need
to update for typo fixes and such).

I like the builtin_models!
I am not sure if we have some double-functionality here: have a look at https://github.com/textX/textX/blob/master/tests/functional/test_metamodel/test_multi_metamodel_refs.py#L49. In this test we use the global_repository parameter of metamodel_from_*. This seems to have a similar effect. However, I prefer the way you propose it now. Maybe we can get rid of the global_repository and map it internally to the same thing? Or at least deprecate global_repository...

Ok for the simplification of the model repo access. Very good!

I think the new feature is a common fallback (lookup), where as the global repo is really global (shared and modified)...

In my understanding global_repository has different effect. It enables caching of all loaded models by the meta-model to ensure that all objects are unique no matter where they are loaded, as long as the same meta-model is used.  IIRC global repo style scope providers will store all loaded models to global repository all_models and if model is loaded again (even through importURI) the cached version will be used.
On the other hand builtin_models is meant to be a pre-loaded models for reference resolution and it affects all ImportURI inherited scope providers. These models are prepared during construction of the meta-model and are not updated by scope providers. So, in a way this is builtins functionality but with proper textX models loaded from str/file.


Using navigator.usb in the browser

Hi there!
With node-usb v2 now supporting the WebUSB API, would it maybe be possible to have the library use navigator.usb when available? I would love to be able to use the same code in Node.js, Electron and the browser, and at the moment I'm having to use what feels like a hacky workaround:
let isBrowser, usb = null;

if (typeof navigator !== 'undefined') {
  const userAgent = navigator.userAgent.toLowerCase();
  isBrowser = userAgent.indexOf(' electron/') === -1 && typeof window !== 'undefined';
} else {
  // Node.js process
  isBrowser = false;
}

if (!isBrowser) {
  // For Node.js and Electron
  const { webusb } = await import('usb');
  usb = webusb;
} else {
  usb = navigator.usb; // Yay, we're using WebUSB!
}

Instead, I would just like to do an import { webusb } from 'usb'; and have it use navigator.usb in the browser and node-usb in Node.js and Electron.

Hmm, interesting suggestion.
One drawback would be the user doesn't have control over which implementation is returned (but TBF, I can't think of an environment where both would be available).

Something like #467?

Yes, that looks like it will work just fine!


[WIP] [match] Only encrypt and commit files if they changed

This is work in progress, tests are failing still
Before: https://github.com/KrauseFx/certs/commit/d13691626cae6cb476c0aa41ef82cf9803d3feff
Now: https://github.com/KrauseFx/certs/commit/2edbbcd2ff9f55352898791bdd56bd2e4dfc2524
So much cleaner :)

Fixes https://github.com/fastlane/fastlane/issues/8917
Fixes https://github.com/fastlane/fastlane/issues/8793
Replaces, closes and fixes https://github.com/fastlane/fastlane/pull/8919

          1 Warning

:warning:
Pull Request is Work in Progress

  Generated by :no_entry_sign: Danger


gold market alert

the discord bot i mentioned you yesterday i changed a bit the py code and it does alert for gold on market and for attack.

i added you to my private repo of the gold market alarm see it yourself and if can make it to ts

Ah nice, I will take a look at it 👍🏼
I also did an other program which monitored the gold market, so I will just have to transfer that code to this project somehow :)

Can I ask on which server you're playing?

gr99

on my cmd it tells me that sh is not recognized as command

I think you have to add Bun to your PATH variable
add to ~/.zshrc
export BUN_INSTALL="$HOME/.bun"
export PATH="$BUN_INSTALL/bin:$PATH"

i type these one at a time on Git Bash?

Maybe the problem is that i am on windows

Hey stamas, i tried to get it running on windows and had some struggles my self since i had to install a vm first and so on...
I read somewhere that it should work if you install Bun in a wsl cli (Linux subsystem in windows). When you have Bun installed there you should be able to run the script.
Bun also allows to compiling this script to an executable .exe file which can be run on windows without the need to install bun. I will have to do some things to get this working but I will keep you updated :)


An option to configure request timeout for CLI / Runner.

Resolves #204

Codecov Report

Merging #221 into master will increase coverage by <.01%.
The diff coverage is 100%.

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


Fix default dimension of SPI parameters

Regards t_delay and nbrShiftGridCell

The parameter t_delay is assumed by the kernel to be an array with one element for each shard. The user is expected to initialise this parameter as (1) None, (2) a scalar or (3) an array of length rp.size. To make this work, the following is done:

None -- which sets t_delay to be a zero array of size rp.size
A scalar value -- which is sets t_delay to be an array of size rp.size with every element set to this provided scalar value.
An array of size rp.size -- which is what we want!

I added a check in verifySettings for the rare case where the user sets t_delay to an array with a different size than rp.size.


#16 finish route api/bidding/submit

Updates:

allow bid/submit route to add new Play naively
change names from Instance to Play, Customer to Host
Clean up and docs

Closes #16


MSAL Interceptor not adding bearer token to the API call after authenticated from AD

Core Library
MSAL.js v2 (@azure/msal-browser)
Core Library Version
2.21.0
Wrapper Library
MSAL Angular (@azure/msal-angular)
Wrapper Library Version
2.1.0
Description
We are upgrading from msal v1 to msal v2 and using redirect method of login. In AD app registered under SPA and did not select Implicit grant and hybrid flows checkboxs as we are using MSAL V2.
AD authentication is happening and I can see token request success and its redirecting to app. But after authentication , token is being added to api call automatically by Interceptor though all the necessary configuration is in place according to official documentation.
Note : when I run the sample app using our client and tenant details, its working perfectly for the graph api call - token is passing.
Error Message

Msal Logs
Navigated to https://localhost:4200/my-work/work-list
3DevTools failed to load source map: Could not load content for https://localhost:4200/sockjs.js.map: HTTP error: status code 404, net::ERR_HTTP_RESPONSE_CODE_FAILURE
VM11:452571 Msal Logging: [Tue, 25 Jan 2022 05:09:23 GMT]<EMAIL_ADDRESS>: Info - Emitting event: msal:loginStart
VM11:452583 [Tue, 25 Jan 2022 05:09:23 GMT]<EMAIL_ADDRESS>: Info - Emitting event: msal:loginStart
VM11:73415 Angular is running in development mode. Call enableProdMode() to enable production mode.
VM11:452571 Msal Logging: [Tue, 25 Jan 2022 05:09:23 GMT]<EMAIL_ADDRESS>: Info - Emitting event: msal:handleRedirectStart
VM11:452583 [Tue, 25 Jan 2022 05:09:23 GMT]<EMAIL_ADDRESS>: Info - Emitting event: msal:handleRedirectStart
VM11:452571 Msal Logging: [Tue, 25 Jan 2022 05:09:23 GMT] : [6a37a070-f9d7-4f1b-9f5f-5de7ab2badb6]<EMAIL_ADDRESS>: Info - handleRedirectPromise called but there is no interaction in progress, returning null.
VM11:452583 [Tue, 25 Jan 2022 05:09:23 GMT] : [6a37a070-f9d7-4f1b-9f5f-5de7ab2badb6]<EMAIL_ADDRESS>: Info - handleRedirectPromise called but there is no interaction in progress, returning null.
VM11:73415 Angular is running in development mode. Call enableProdMode() to enable production mode.
VM11:452571 Msal Logging: [Tue, 25 Jan 2022 05:09:23 GMT]<EMAIL_ADDRESS>: Info - Emitting event: msal:handleRedirectEnd
VM11:452583 [Tue, 25 Jan 2022 05:09:23 GMT]<EMAIL_ADDRESS>: Info - Emitting event: msal:handleRedirectEnd
VM11:604772 msal:in progress
VM11:452571 Msal Logging: [Tue, 25 Jan 2022 05:09:23 GMT]<EMAIL_ADDRESS>: Info - Emitting event: msal:loginStart
VM11:452583 [Tue, 25 Jan 2022 05:09:23 GMT]<EMAIL_ADDRESS>: Info - Emitting event: msal:loginStart
Navigated to https://login.microsoftonline.com/.../oauth2/v2.0/authorize?client_id=....&scope=user.read openid profile offline_access&redirect_uri=https%3A%2F%2Flocalhost%3A4200%2F&client-request-id=......
main.js:73 BSSO Telemetry: {"result":"Error","error":"NoExtension","type":"ChromeSsoTelemetry","data":{},"traces":["BrowserSSO Initialized","Creating ChromeBrowserCore provider","Sending message for method CreateProviderAsync","Received message for method CreateProviderAsync","Error: ChromeBrowserCore error NoExtension: Extension is not installed."]}
DevTools failed to load source map: Could not load content for https://login.microsoftonline.com/.../oauth2/v2.0/7941c8df4f140717a949.map: HTTP error: status code 404, net::ERR_HTTP_RESPONSE_CODE_FAILURE
favicon.ico:1 GET https://login.microsoftonline.com/favicon.ico 404 (Not Found)
Navigated to https://login.microsoftonline.com/.../oauth2/v2.0/authorize?client_id=...&scope=user.read openid profile offline_access&redirect_uri=https%3A%2F%2Flocalhost%3A4200%2F&client-request-id=....
VM16:13 [Violation] 'setTimeout' handler took 98ms
[Violation] Forced reflow while executing JavaScript took 73ms
Navigated to https://gfs2.glb.kworld.kpmg.com/adfs/ls/?client-request-id=....
chrome-error://chromewebdata/:1 Failed to load resource: the server responded with a status of 401 ()
Navigated to chrome-error://chromewebdata/
Navigated to https://gfs2.glb.kworld.kpmg.com/adfs/ls/wia?client-request-id=....
favicon.ico:1 GET https://gfs2.glb.kworld.kpmg.com/favicon.ico 404 (Not Found)
Navigated to https://login.microsoftonline.com/login.srf
Navigated to https://localhost:4200/
3DevTools failed to load source map: Could not load content for https://localhost:4200/sockjs.js.map: HTTP error: status code 404, net::ERR_HTTP_RESPONSE_CODE_FAILURE
main.js:452571 Msal Logging: [Tue, 25 Jan 2022 05:09:55 GMT]<EMAIL_ADDRESS>: Info - Emitting event: msal:loginStart
main.js:452583 [Tue, 25 Jan 2022 05:09:55 GMT]<EMAIL_ADDRESS>: Info - Emitting event: msal:loginStart
main.js:73415 Angular is running in development mode. Call enableProdMode() to enable production mode.
main.js:452571 Msal Logging: [Tue, 25 Jan 2022 05:09:55 GMT]<EMAIL_ADDRESS>: Info - Emitting event: msal:handleRedirectStart
main.js:452583 [Tue, 25 Jan 2022 05:09:55 GMT]<EMAIL_ADDRESS>: Info - Emitting event: msal:handleRedirectStart
main.js:73415 Angular is running in development mode. Call enableProdMode() to enable production mode.
main.js:452571 Msal Logging: [Tue, 25 Jan 2022 05:09:55 GMT]<EMAIL_ADDRESS>: Info - Emitting event: msal:loginFailure
main.js:452583 [Tue, 25 Jan 2022 05:09:55 GMT]<EMAIL_ADDRESS>: Info - Emitting event: msal:loginFailure
main.js:47887 ERROR Error: Uncaught (in promise): BrowserAuthError: interaction_in_progress: Interaction is currently in progress. Please ensure that this interaction has been completed before calling an interactive API.  For more visit: aka.ms/msaljs/browser-errors.
BrowserAuthError: interaction_in_progress: Interaction is currently in progress. Please ensure that this interaction has been completed before calling an interactive API.  For more visit: aka.ms/msaljs/browser-errors.
at BrowserAuthError.AuthError [as constructor] (main.js:162927:20)
at new BrowserAuthError (main.js:152364:24)
at Function.BrowserAuthError.createInteractionInProgressError (main.js:152452:12)
at RedirectClient. (main.js:155148:94)
at step (main.js:147797:17)
at Object.next (main.js:147728:14)
at main.js:147700:67
at new ZoneAwarePromise (polyfills.js:14512:23)
at __awaiter (main.js:147679:10)
at RedirectClient.StandardInteractionClient.preflightInteractiveRequest (main.js:155139:72)
at resolvePromise (polyfills.js:14412:21)
at polyfills.js:14307:11
at polyfills.js:14324:27
at ZoneDelegate.invoke (polyfills.js:13339:160)
at Object.onInvoke (main.js:74154:25)
at ZoneDelegate.invoke (polyfills.js:13339:48)
at Zone.run (polyfills.js:13065:37)
at polyfills.js:14485:28
at ZoneDelegate.invokeTask (polyfills.js:13372:173)
at Object.onInvokeTask (main.js:74142:25)
defaultErrorLogger @ main.js:47887
handleError @ main.js:47940
next @ main.js:74929
__tryOrUnsub @ main.js:407452
next @ main.js:407379
_next @ main.js:407315
next @ main.js:407285
next @ main.js:407023
emit @ main.js:70902
(anonymous) @ main.js:74180
ZoneDelegate.invoke @ polyfills.js:13339
Zone.run @ polyfills.js:13065
runOutsideAngular @ main.js:74045
onHandleError @ main.js:74180
ZoneDelegate.handleError @ polyfills.js:13343
Zone.runGuarded @ polyfills.js:13085
_loop_2 @ polyfills.js:14245
api.microtaskDrainDone @ polyfills.js:14258
drainMicroTaskQueue @ polyfills.js:13595
Promise.then (async)
scheduleMicroTask @ polyfills.js:13567
ZoneDelegate.scheduleTask @ polyfills.js:13362
Zone.scheduleTask @ polyfills.js:13170
Zone.scheduleMicroTask @ polyfills.js:13195
scheduleResolveOrReject @ polyfills.js:14473
ZoneAwarePromise.then @ polyfills.js:14674
bootstrapModule @ main.js:74974
965878 @ main.js:519400
webpack_require @ runtime.js:23
webpack_exec @ main.js:607223
(anonymous) @ main.js:607224
webpackJsonpCallback @ runtime.js:321
(anonymous) @ main.js:1
Navigated to https://localhost:4200/my-work/work-list
3DevTools failed to load source map: Could not load content for https://localhost:4200/sockjs.js.map: HTTP error: status code 404, net::ERR_HTTP_RESPONSE_CODE_FAILURE
main.js:452571 Msal Logging: [Tue, 25 Jan 2022 05:09:57 GMT]<EMAIL_ADDRESS>: Info - Emitting event: msal:loginStart
main.js:452583 [Tue, 25 Jan 2022 05:09:57 GMT]<EMAIL_ADDRESS>: Info - Emitting event: msal:loginStart
main.js:73415 Angular is running in development mode. Call enableProdMode() to enable production mode.
main.js:452571 Msal Logging: [Tue, 25 Jan 2022 05:09:57 GMT]<EMAIL_ADDRESS>: Info - Emitting event: msal:handleRedirectStart
main.js:452583 [Tue, 25 Jan 2022 05:09:57 GMT]<EMAIL_ADDRESS>: Info - Emitting event: msal:handleRedirectStart
main.js:73415 Angular is running in development mode. Call enableProdMode() to enable production mode.
main.js:452571 Msal Logging: [Tue, 25 Jan 2022 05:09:57 GMT]<EMAIL_ADDRESS>: Info - Emitting event: msal:loginFailure
main.js:452583 [Tue, 25 Jan 2022 05:09:57 GMT]<EMAIL_ADDRESS>: Info - Emitting event: msal:loginFailure
main.js:47887 ERROR Error: Uncaught (in promise): BrowserAuthError: interaction_in_progress: Interaction is currently in progress. Please ensure that this interaction has been completed before calling an interactive API.  For more visit: aka.ms/msaljs/browser-errors.
BrowserAuthError: interaction_in_progress: Interaction is currently in progress. Please ensure that this interaction has been completed before calling an interactive API.  For more visit: aka.ms/msaljs/browser-errors.
at BrowserAuthError.AuthError [as constructor] (main.js:162927:20)
at new BrowserAuthError (main.js:152364:24)
at Function.BrowserAuthError.createInteractionInProgressError (main.js:152452:12)
at RedirectClient. (main.js:155148:94)
at step (main.js:147797:17)
at Object.next (main.js:147728:14)
at main.js:147700:67
at new ZoneAwarePromise (polyfills.js:14512:23)
at __awaiter (main.js:147679:10)
at RedirectClient.StandardInteractionClient.preflightInteractiveRequest (main.js:155139:72)
at resolvePromise (polyfills.js:14412:21)
at polyfills.js:14307:11
at polyfills.js:14324:27
at ZoneDelegate.invoke (polyfills.js:13339:160)
at Object.onInvoke (main.js:74154:25)
at ZoneDelegate.invoke (polyfills.js:13339:48)
at Zone.run (polyfills.js:13065:37)
at polyfills.js:14485:28
at ZoneDelegate.invokeTask (polyfills.js:13372:173)
at Object.onInvokeTask (main.js:74142:25)
defaultErrorLogger @ main.js:47887
handleError @ main.js:47940
next @ main.js:74929
__tryOrUnsub @ main.js:407452
next @ main.js:407379
_next @ main.js:407315
next @ main.js:407285
next @ main.js:407023
emit @ main.js:70902
(anonymous) @ main.js:74180
ZoneDelegate.invoke @ polyfills.js:13339
Zone.run @ polyfills.js:13065
runOutsideAngular @ main.js:74045
onHandleError @ main.js:74180
ZoneDelegate.handleError @ polyfills.js:13343
Zone.runGuarded @ polyfills.js:13085
_loop_2 @ polyfills.js:14245
api.microtaskDrainDone @ polyfills.js:14258
drainMicroTaskQueue @ polyfills.js:13595
Promise.then (async)
scheduleMicroTask @ polyfills.js:13567
ZoneDelegate.scheduleTask @ polyfills.js:13362
Zone.scheduleTask @ polyfills.js:13170
Zone.scheduleMicroTask @ polyfills.js:13195
scheduleResolveOrReject @ polyfills.js:14473
ZoneAwarePromise.then @ polyfills.js:14674
bootstrapModule @ main.js:74974
965878 @ main.js:519400
webpack_require @ runtime.js:23
webpack_exec @ main.js:607223
(anonymous) @ main.js:607224
webpackJsonpCallback @ runtime.js:321
(anonymous) @ main.js:1
main.js:452571 Msal Logging: [Tue, 25 Jan 2022 05:09:57 GMT] : [d9b12d39-7b34-4860-9541-1a31885e3f7a]<EMAIL_ADDRESS>: Info - in acquireToken call
main.js:452583 [Tue, 25 Jan 2022 05:09:57 GMT] : [d9b12d39-7b34-4860-9541-1a31885e3f7a]<EMAIL_ADDRESS>: Info - in acquireToken call
main.js:452571 Msal Logging: [Tue, 25 Jan 2022 05:09:58 GMT]<EMAIL_ADDRESS>: Info - Emitting event: msal:loginSuccess
main.js:452583 [Tue, 25 Jan 2022 05:09:58 GMT]<EMAIL_ADDRESS>: Info - Emitting event: msal:loginSuccess
main.js:452571 Msal Logging: [Tue, 25 Jan 2022 05:09:58 GMT]<EMAIL_ADDRESS>: Info - Emitting event: msal:handleRedirectEnd
main.js:452583 [Tue, 25 Jan 2022 05:09:58 GMT]<EMAIL_ADDRESS>: Info - Emitting event: msal:handleRedirectEnd
main.js:604772 msal:in progress
polyfills.js:16769 GET https://localhost:4200/client/api/user/.... 401 (Unauthorized)
scheduleTask @ polyfills.js:16769
ZoneDelegate.scheduleTask @ polyfills.js:13360
onScheduleTask @ polyfills.js:13253
ZoneDelegate.scheduleTask @ polyfills.js:13355
Zone.scheduleTask @ polyfills.js:13170
Zone.scheduleMacroTask @ polyfills.js:13199
scheduleMacroTaskWithCurrentZone @ polyfills.js:13759
(anonymous) @ polyfills.js:16814
proto. @ polyfills.js:14121
(anonymous) @ main.js:39366
_trySubscribe @ main.js:406633
subscribe @ main.js:406615
subscribeToResult @ main.js:419955
_innerSub @ main.js:413766
_tryNext @ main.js:413759
_next @ main.js:413740
next @ main.js:407285
.
.
.
.
bootstrapModule @ main.js:74974
965878 @ main.js:519400
webpack_require @ runtime.js:23
webpack_exec @ main.js:607223
(anonymous) @ main.js:607224
webpackJsonpCallback @ runtime.js:321
(anonymous) @ main.js:1
Show 213 more frames
main.js:47887 ERROR Error: Uncaught (in promise): HttpErrorResponse: {"headers":{"normalizedNames":{},"lazyUpdate":null},"status":401,"statusText":"Unauthorized","url":"https://localhost:4200/client/api/user/...","ok":false,"name":"HttpErrorResponse","message":"Http failure response for https://localhost:4200/client/api/user/...: 401 Unauthorized","error":null}
at resolvePromise (polyfills.js:14412:21)
at resolvePromise (polyfills.js:14359:11)
at polyfills.js:14486:11
at ZoneDelegate.invokeTask (polyfills.js:13372:173)
at Object.onInvokeTask (main.js:74142:25)
at ZoneDelegate.invokeTask (polyfills.js:13372:56)
at Zone.runTask (polyfills.js:13122:39)
at drainMicroTaskQueue (polyfills.js:13588:25)
at ZoneTask.invokeTask [as invoke] (polyfills.js:13470:13)
at invokeTask (polyfills.js:14912:12)
defaultErrorLogger @ main.js:47887
handleError @ main.js:47940
next @ main.js:74929
__tryOrUnsub @ main.js:407452
next @ main.js:407379
_next @ main.js:407315
next @ main.js:407285
next @ main.js:407023
.
.
.
MSAL Configuration
export function MSALInstanceFactory(): IPublicClientApplication {
  return new PublicClientApplication({
    auth: {
      clientId: `${environment.adalClientId}`,
      authority: `${environment.adalTenant}`,
      redirectUri: "https://localhost:4200/",
      postLogoutRedirectUri: "https://localhost:4200/"
    },
    cache: {
      cacheLocation: BrowserCacheLocation.LocalStorage,
      storeAuthStateInCookie: isIE
    },
    system: {
      loggerOptions: {
        loggerCallback,
        logLevel: LogLevel.Info,
        piiLoggingEnabled: false
      }
    }
  });
}

export function MSALInterceptorConfigFactory(): MsalInterceptorConfiguration {
  const protectedResourceMap = new Map<string, Array<string>>();
  protectedResourceMap.set('/gms-compliance-trans', null);
  protectedResourceMap.set('/gms-compliance-perf', null);
  protectedResourceMap.set(`${environment.FIRMWIDE_API_BASE_URL}`, null);
  return {
    interactionType: InteractionType.Redirect,
    protectedResourceMap
  };
}

export function MSALGuardConfigFactory(): MsalGuardConfiguration {
  return {
    interactionType: InteractionType.Redirect,
    authRequest: {
      scopes: ['user.read', 'openid', 'profile']
    },
    loginFailedRoute: '/unauthorized'
  };
}

  providers: [
    {
      provide: HTTP_INTERCEPTORS,
      useClass: MsalInterceptor,
      multi: true
    },
    {
      provide: MSAL_INSTANCE,
      useFactory: MSALInstanceFactory
    },
    {
      provide: MSAL_GUARD_CONFIG,
      useFactory: MSALGuardConfigFactory
    },
    {
      provide: MSAL_INTERCEPTOR_CONFIG,
      useFactory: MSALInterceptorConfigFactory
    },
    MsalService,
    MsalGuard,
    MsalBroadcastService
 ]

Relevant Code Snippets
public login(){

    if (this.msalGuardConfig.authRequest) {
      return this.msalService.loginRedirect({
        ...this.msalGuardConfig.authRequest
      } as RedirectRequest);
    } else {
      return this.msalService.loginRedirect();
    }
}

this.msalBroadcastService.msalSubject$
.pipe(
  filter(
	(msg: EventMessage) => msg.eventType === EventType.LOGIN_SUCCESS
  )
)
.subscribe((result: EventMessage) => {
  const payload = result.payload as AuthenticationResult;
  this.msalService.instance.setActiveAccount(payload.account);
  const account = this.msalService.instance.getActiveAccount();
  // calling user api
  this.authService.getUser().then(isActive => {
	console.log('user loaded : ', isActive);
	if (!isActive) {
	  return (this.showContent = true);
	}
  });
});

Reproduction Steps
Use above configuration and just used basic redirect code same as the samples from official doc
Expected Behavior
Token should be sent for api calls once authenticated from AD
Identity Provider
Azure AD / MSA
Browsers Affected (Select all that apply)
Chrome, Firefox, Edge, Internet Explorer
Regression
MSAL V1
Source
External (Customer)

@Sujith2020 In MSAL Angular v2, MSAL Angular will no longer automatically attach a token to API requests to routes on your app.
Add this to your configuration:
protectedResourceMap.set('/client/api/user/*', [ "scope-for-this-api"]);

More: https://github.com/AzureAD/microsoft-authentication-library-for-js/blob/dev/lib/msal-angular/docs/v2-docs/msal-interceptor.md


Updating the release test to use the new logging capabilities

Updating the release test to a) use the new syslog capabilities and b) use logging through the app api
Depends on kubos/kubos#246

 Update app APIs to use logging


"No variable named dependency" when chaining dependency from parent (since v0.54.16)

Describe the bug
v0.54.16 has introduced a regression related to chained dependencies leading up to the parent module which in turn has a dependency.  v0.54.15 is fine, and the issue persists with v0.55.20.
Consider the following layout:
.
├── tfstate/
│   ├── outputs.tf
│   └── terragrunt.hcl
├── vpc/
│   ├── outputs.tf
│   ├── terragrunt.hcl
├── eks/
│   ├── main.tf
│   ├── terragrunt.hcl
└── terragrunt.hcl

With dependencies:

The tfstate dependency is declared in the root-level terragrunt.hcl for purposes of generating backend.tf.  The vpc module works fine, however the eks module generates this error:
ERRO[0000] Error: Unknown variable

ERRO[0000]   on /home/jtackaberry/projects/terragrunt-dep-bug/terragrunt.hcl line 12, in remote_state:
ERRO[0000]   12:     path = "${dependency.tfstate.outputs.prefix}-${path_relative_to_include()}.tfstate"
ERRO[0000]
ERRO[0000] There is no variable named "dependency".

An error like the above is generated for each dependency.tfstate.outputs reference in the remote_state block.
We use this pattern quite a lot in our projects, where we have a standalone tfstate module in the repo (with no dependencies or includes) that bootstraps an S3 bucket and DynamoDB table using a custom module that provides the details as outputs.  Then terragrunt.hcl in the root sources this terragrunt module as a dependency to configure the backend.
To Reproduce
I've created a sample project at https://github.com/jtackaberry/terragrunt-dep-bug
First, ensure you have a terragrunt version greater than or equal to v0.54.16.  Then:
# Clone the example
git clone https://github.com/jtackaberry/terragrunt-dep-bug.git

# Apply mock tfstate module -- this is fine
cd terragrunt-dep-bug/tfstate
terragrunt apply

# Apply mock vpc module -- this is fine
cd ../vpc
terragrunt apply

# Apply mock eks module -- error occurs here
cd ../eks
terragrunt apply

Though not reproduced above, I also believe #2974 is related, and possibly may have the same root cause.  The versions line up, certainly.
Expected behavior
The error message itself actually may be innocuous.  The eks module in the example project does seem to work (insofar as backend.tf is correctly populated).
However the expected behavior is that of pre-0.54.16 where no error is printed.
Versions

Terragrunt version: v0.54.15 (works), v0.54.16 (broken), v0.55.20 (broken)
Terraform version: v1.5.7
Environment details: Ubuntu 20.04, Ubuntu 22.04

I was able to also update the example repo at https://github.com/jtackaberry/terragrunt-dep-bug to also reproduce #2974, as we're running into that one as well.
So now running terragrunt apply in the eks/ directory outputs:
ERRO[0000] Error: Unknown variable

ERRO[0000]   on /home/jtackaberry/projects/terragrunt-dep-bug/terragrunt.hcl line 12, in remote_state:
ERRO[0000]   12:     path = "${dependency.tfstate.outputs.prefix}-${path_relative_to_include()}.tfstate"
ERRO[0000]
ERRO[0000] There is no variable named "dependency".

ERRO[0000] Could not convert include to the execution ctx to evaluate additional locals in file /home/jtackaberry/projects/terragrunt-dep-bug/vpc/terragrunt.hcl  prefix=[/home/jtackaberry/projects/terragrunt-dep-bug/vpc]

Same issue there

This issue is still exist on 0.58.2.

Resolved in v0.62.2 release.


SwipeAnimation duration doesn't used

Hi !
I'm trying to increase the duration of my animation on swipe left or right and I saw the below code  in SwipeListener:
private ViewPropertyAnimator animateOffScreenLeft(int duration) {
        return card.animate()
                .setDuration(SwipeDeck.ANIMATION_DURATION)
                .x(-(parentWidth))
                .y(0)
                .rotation(-30);
    }

    private ViewPropertyAnimator animateOffScreenRight(int duration) {
        return card.animate()
                .setDuration(SwipeDeck.ANIMATION_DURATION)
                .x(parentWidth * 2)
                .y(0)
                .rotation(30);
    }

The parameter duration is never used. Can you change this ?

its fixed already. Can be closed now.

I wonder you will fix this issue thanks


Configure Apache to write access logs to stdout instead of file

I've configured Apache to use piped logs and now it's writing access logs to stdout instead of /tmp/access_log. This change addresses to https://bugzilla.redhat.com/show_bug.cgi?id=1231862
PTAL @rhcarvalho @mfojtik
I've tested in on with php55/php56 and CentOS7.
A couple of related questions:

now there is no /tmp/access_log. Is it ok or we should provide backward compatibility? If we should I think we may change cat to tee and it would work fine
(if the answer to the first question is "No") Should we update our documentation like we did in https://github.com/openshift/openshift-docs/pull/887?

I'll defer the answer to (1) to someone else, but answering (2), in either case we should update the docs to reflect the new reality.

i don't think we have to keep backward compatibility for that file
we should say that all logs are streamed to container output (iow. stdout).

This change LGTM

@remicollet @hhorak FYI

we should say that all logs are streamed to container output (iow. stdout).

@mfojtik To be honest not all logs are streamed to container output. /tmp/error_log is still there, I didn't touch it. Should I replace using of /tmp/error_log by streaming to /dev/stderr?

@php-coder we should stream all logs to stdout so they can be captured by some logging tools or directly by docker (docker logs). We can have option to log to volume in case you want to do some analysis in other container (?).

(2), in either case we should update the docs to reflect the new reality

@rhcarvalho What did you mean when saying "we"? I'm just trying to understand what I should do on my side and what is not my side. Should I create a ticket for that? Or I should provide a pull request?

@php-coder normally if you change the code / behavior, you're also responsible for updating the related documentation. Please provide a PR to update the docs.
I meant "we" in general, and in particular "you" :)

In private conversation with @mfojtik we came to the the following decision:

current logging of access log to /dev/stdout is OK
we don't want to stream error logs to /dev/stderr because we are not sure that is really needed and who/how will handle it
we will add option to save access logs to the file by demand

@mfojtik also told me that there is a possible risk to expose sensitive information (like tokens in a URL). As far I understand we are not doing anything with it for a now.

LGTM @php-coder can you check what we do for sti-perl ? (another httpd based image)

Please provide a PR to update the docs.

Done: https://github.com/openshift/openshift-docs/pull/1058

LGTM @php-coder can you check what we do for sti-perl ? (another httpd based image)

@mfojtik After a first look I can see that sti-perl also writes logs to /tmp/{access,error}_logs. Would we fix it?

@php-coder yes please (i'll merge this, but please open another PR for perl)

we will add option to save access logs to the file by demand

@mfojtik @php-coder doesn't seem like this ever happened, either here or in the perl repo that was also updated?

@bparees Perhaps I should rephrase myself: "we will add option to save access logs to the file if someone ask about it".

@php-coder ok.  I kinda think it should have been there with this change (consider me the person asking about it) but we can live with it as is.


Introduce go modules

This PR is generated by a tool I wrote that helps migrate Go packages that are tagged +2 to Semantic Import Versioning.
Note that this change should be backwards compatible and can still be imported without the /vX suffix when Go Modules is off.

@gmlewis seems that gofmt 1.11 has different rules from 1.10 and 1.9?

Thanks for fixing the Travis CI build, @marwan-at-work!
Since we recently removed support for Go 1.7 and bumped the version number, and this PR now removes support for Go 1.8, can you please make this semantic version be v18.0.0 and we will tag it as such when we merge the PR?
Also, can you please make the necessary change to README.md similar to the one I did here: https://github.com/google/go-github/commit/fbd7fb9c7f3d27aa691e8421690e00be916f8d8d
?

To answer your question about investigating differences in gofmt between v1.11 and v1.10, it seems pretty minor and I'm fine to move forward keeping the builds happy, but if you would like to investigate, you are welcome to, obviously.

Thank you, @juliaferraioli!
Merging then bumping tagged release.

Thank you both :)

I think github.com/google/go-github/github/v18 in the readme is supposed to be github.com/google/go-github/v18/github.

Perhaps the README should contain instructions for pre-go1.11 users as well?

As for pre go 1.11, the latest Go 1.9 and 1.10 should work fine with the new import path. However they wouldn't work with Go 1.8 or before that. So before 1.8, they can just use v17 or below. But maybe the readme should just say the package requires Go1.9.X or above?

...and it does:
go-github requires Go version 1.9 or greater.


feat: added text overrides on StripePaymentInput

Signed-off-by: Haris Spahija<EMAIL_ADDRESS>Part of: #409
Impact: minor
Type: feature
Component
StripePaymentInput now has overrides when i18next will be implemented (see #409)
Breaking changes
No breaking chances, all added fields are optional
Testing

Add a new prop secureCaptionText to <StripePaymentInput />
Add the value "test" to secureCaptionText
Button should display "test" when test is given as a value to the prop. When the prop secureCaptionText is not added, it should default to the values given in default props

Added props:
secureCaptionText: PropTypes.string,

🚀 Preview deployed
Built with commit d082a76e0d7b1758f48c047fc3b0c1f07ad79bac
https://deploy-preview-462--stoic-hodgkin-c0179e.netlify.com

:tada: This PR is included in version 0.68.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


[FP]: CVE-2023-22551 on camel-ftp-starter-3.20.2.jar

Package URl
<EMAIL_ADDRESS>CPE
cpe:2.3:a:ftp_project:ftp::::::::
CVE
CVE-2023-22551
ODC Integration
{"label"=>"Maven Plugin"}
ODC Version
8.2.0
Description
No response

approved

ODC also reports this CVE for org.springframework.integration:spring-integration-ftp:5.2.8.RELEASE, which seems to have nothing to do with the vulnerable library. Should I file a separate "FP Report" for that?

@meeque yes please, a dedicated FP issue allows for an easy integration into the hosted suppressions file.

@aikebah Issue reappeared on 8.3.1


Move panic handling for vfuncs into trait

The default implementation would just abort(), element and others could catch, report an error message and poison the object.
This probably would have to be on the ObjectType trait

Happened in gobject-subclass


For aggregated columns show 0-point using a line across rows

For input data on a negative range, show the point the data has to pass to be To show the point the data has to pass to be positive on average. Here is a sketch:

Not quite sure how well that works for mixed scales, though.

a problem is that mixed/combined columns are always defined in the range [0,1] since the work on the basis of normalized values not the raw ones. So, there is no automatic way determining which is the 0 line position for the combined bar.

Well, you'd have to back to the raw data and get the information what a 0 value would correspond to.

doesn't work in the general case with arbitrary mappings and nesting...

Why?
But anyways, that's probably not super-relevant. We could show that only if we have exclusively +/- items?

sample dataset:
test = cbind(a=runif(100,-1,3),b=runif(100,-2,2),c=runif(100,-2,2),d=runif(100,-1,1))

Cool. Not super-easy to read, but if you know what you're looking for it works. What do you think?

not easy to read. But, that is the drawback of using a stacked bar for encoding negative contributions.
The basic task of the guy was: "The only thing is that for us it is important to talk about whether GEP itself is positive or negative and that information would be lost in the lineup visualization."
Therefore, we might move the zero combined line above the stacked bars.
The zero point indicators in the bar irritate me, since you can't really see the pattern except for the yellow column due to alignment issues.

We could always cross/hatch the negative portion of the bar?

We could always cross/hatch the negative portion of the bar?

you mean the whole negative part of the stacked bar? - not that easy form an implementation point of view. Maybe with an overlay over the bars but the individual stacked bar elements are rendered independently.


Update /terraform page

This PR updates the /terraform page. It brings the page more in line with the layouts we have used recently and also pulls in the tf2pulumi component.

Closing this for now assuming we'll incorporate this into upcoming work somehow.


More robust and concise OpenFF MolCharger dependency management

The current dependency structure and attribute registration of the mdtools.openfftools subpackage is somewhat of a hodge-podge, and to an extent reinvents. Also, for the future it would be nice if all features of polymerist which require parts of the OpenFF stack could be sequestered and controlled within this subpackage, to better control dependencies and allow for the OpenFF dependency to be optional; this is a major barrier to registration of polymerist on PyPi.

[x] Implement checkers and decorators for enforcing package requirements (similar to openff.utilities)

[x] Add support for custom Exception raised for missing packages
[x] Add support for wrapping around methods as well as functions
[x] Write units tests for these

[x] Separate ToolkitWrapper registration case-by-case with import-awareness

[x] Make unit tests aware of missing packages (should not fail due to missing package or license, but reduce number of tests)
[x] Recast MolCharger in terms of register_abstract_class_attr decorator
[x] Have MolCharger implementations rely directly on respective ToolkitWrappers, rather than on the GLOBAL_TOOLKIT_REGISTRY

[x] Write unit tests for MolCharger subclasses

[x] Method name application
[x] Partial_charge attr creation

Resolved by #32


fix

Please add a description to your MR.
This should include at lest include what you're fixing and what your fix is.


StableFast3D/CharacterGen/CRM raise error and I tested triposr/hunyuan3d-1/StableFast3D/CharacterGen/CRM/TriplaneGaussian

example in _Example_Workflows:
triposr     OK
hunyuan3d-1   OK
TriplaneGaussian   OK
StableFast3D     can not find the slang.h
CharacterGen    ...
CRM                  ...
InstantMesh      ...
Unique3D          ...
Thank you, MrForExample.
I am happy to use triposr/hunyuan3d/TriplaneGaussian and will hope the new ComfyUI-3D-Pack.

"pip install -v slangtorch==1.2.6"
I also met this before and this solved my problem

Hi @coddz sorry for the late responds
slangtorch seems already in requirements.txt, I'll take deeper look before next release, cheers 👍


fix bugs + get ingest working

SUMMARY

get rds working on ingestor
fix millions of tiny bugs

TEST PLAN

ingestor now working

LGTM


stack.availability_zones fails if exclude_availability_zones not set in Cloudfile

Description

For some reason @exclude_availability_zones if defaulting to nil even though we set the default to an empty Array.
This was introduced in #232
Expected behavior

@exclude_availability_zones should default to an empty Array if it is not specified in the Cloudfile.
Observed behavior

The following exception is thrown because @exclude_availability_zones is defaulting to nil not an empty Array.
Steps to Reproduce

Install version 1.0.4 of the gem and run convection diff on a stack that includes and the Cloudfile does not include exclude_availability_zones:
stack.availability_zones do
  # something
end

Stack Trace or Log Messages

Stack trace for `brief error context`

.../convection-1.0.4/lib/convection/control/stack.rb:441:in `availability_zones': undefined method `empty?' for nil:NilClass (NoMethodError)
.../templates/ec2/vpc.rb:132:in `block (2 levels) in '
.../convection-1.0.4/lib/convection/model/template.rb:23:in `instance_exec'
...snip...

Resolved in #235.


Prevent build errors due to incompatible cache content after update

Related to a problem?
Yesterday I updated Cecil from version 7.1.2 to the latest 7.11.1 and saw my build fail with the following error message:
Building website...

 [ERROR] Template "/Users/paik/Projects/cecil/resources/layouts/partials/metatags.html.twig:114" (page: another-page):
         Neither the property "missing" nor one of the methods "missing()", "getmissing()"/"ismissing()"/"hasmissing()"
         or "__call()" exist and have public access in class "Cecil\Assets\Asset".

I believe this to have been indirectly caused by the changes in #1490.
The older version of Cecil populated the cache with asset data that has no 'missing' key. The newer Cecil version reads from the cache, expecting the key to exist, causing the error.
A simple deletion has fixed the problem for me, but I spent some time chasing that problem down.
Describe the solution you'd like
Adding the current Cecil version to cache keys could be a simple and pragmatic solution to this kind of problem. Cache entries would be isolated between version, preventing any such incompatibilities.
I have not looked into the Cecil code base too deeply, but this change could potentially be implemented inside the \Cecil\Assets\Cache class.
Describe alternatives you've considered
No response
Additional context
I would gladly attempt to provide an implementation if you believe this to be a good solution. Also, I'd be keen to hear of any other ideas you might have.

Hello @hype09 and thanks a lot for the report.

Adding the current Cecil version to cache keys could be a simple and pragmatic solution to this kind of problem. Cache entries would be isolated between version, preventing any such incompatibilities.

I love this idea: simple et effective :+1:

Done here: 207428c7dab8f13507f4fc54f0e6c16e033b7776.

And released: https://github.com/Cecilapp/Cecil/releases/tag/7.15.4


flet build apk error

Duplicate Check

[X] I have searched the opened issues and there are no duplicates

Describe the bug
Target kernel_snapshot_program failed: Exception
       FAILURE: Build failed with an exception.

       * What went wrong:
       Execution failed for task ':app:compileFlutterBuildRelease'.
       > Process 'command 'C:\Program Files\flutter\bin\flutter.bat'' finished with non-zero exit value 1

       * Try:
       > Run with --stacktrace option to get the stack trace.
       > Run with --info or --debug option to get more log output.
       > Run with --scan to get full insights.
       > Get more help at https://help.gradle.org.

       BUILD FAILED in 30s
       Gradle task assembleRelease failed with exit code 1

       Error building Flet app - see the log of failed command above.

Code sample
Code
[
import flet as ft

# كلمة المرور الصحيحة
PASSWORD = "1234"

def main(page: ft.Page):
    # إخفاء شريط التنقل
    page.title = "حماية بكلمة مرور"
    page.window_width = 300
    page.window_height = 400

    # الحقل الذي يعرض كلمة المرور المدخلة (نجوم)
    password_display = ft.Text(value="• • • •", size=30, text_align="center")

    # لتخزين الأرقام المدخلة
    entered_password = []

    # رسالة الخطأ
    error_label = ft.Text("", color="red")

    # وظيفة لمعالجة الضغط على الأزرار
    def number_button_click(e):
        nonlocal entered_password
        if len(entered_password) < 4:
            entered_password.append(e.control.data)
            update_password_display()

        if len(entered_password) == 4:
            check_password()

    # تحديث عرض كلمة المرور (إضافة النجوم)
    def update_password_display():
        password_display.value = "".join(["•" if len(entered_password) > i else " " for i in range(4)])
        page.update()

    # التحقق من كلمة المرور
    def check_password():
        if "".join(entered_password) == PASSWORD:
            page.controls.clear()
            page.add(ft.Text("مرحبًا بك في التطبيق! 🎉"))
            page.update()
        else:
            entered_password.clear()
            error_label.value = "كلمة المرور خاطئة!"
            update_password_display()
            page.update()

    # إنشاء لوحة الأرقام
    number_buttons = [
        ft.Row(
            [
                ft.ElevatedButton(str(i), on_click=number_button_click, data=str(i))
                for i in range(row_start, row_start + 3)
            ],
            alignment="center",
        )
        for row_start in range(1, 10, 3)
    ]

    # زر "0" وزر الحذف
    extra_row = ft.Row(
        [
            ft.ElevatedButton("0", on_click=number_button_click, data="0"),
            ft.ElevatedButton("حذف", on_click=lambda e: entered_password.pop() if entered_password else None),
        ],
        alignment="center",
    )

    # إضافة العناصر إلى الصفحة
    page.add(
        ft.Column(
            [
                password_display,
                error_label,
                *number_buttons,
                extra_row,
            ],
            alignment="center",
            horizontal_alignment="center",
        )
    )

# تشغيل التطبيق
ft.app(target=main)]

To reproduce
flet build apk
Expected behavior
No response
Screenshots / Videos
No response
Operating System
Windows
Operating system details
windows 11
Flet version
flet 0.25.2
Regression
No, it isn't
Suggestions
No response
Logs
Logs
[Paste your logs here]

Additional details
No response

I had these issues and as far as I understood it has to do with some updates Flutter had in some classes names and this is causing imcompatibility.
It seems that the flet team is already working on these things.
For now, for me, I configured flutter to version 3.24.5 and flet 0.24.0 and worked.
let me know

I had these issues and as far as I understood it has to do with some updates Flutter had in some classes names and this is causing imcompatibility.
It seems that the flet team is already working on these things.
For now, for me, I configured flutter to version 3.24.5 and flet 0.24.0 and worked.
let me know

Thank you for this information, I had the same problem and solved it in the same way you said and it actually worked, so thank you very much

I haven't tried it, I will. Thank you for the explanation. I worked very hard to find a solution for it.

If you want to use Flutter 3.27, follow this: https://github.com/flet-dev/flet/issues/4548#issuecomment-2558093530


Passing parameters to dependency

Description
Sometimes it's needed to pass some parameters to a dependency. Let's look at an example. Let's consider we need to use glad in our project. It generates OpenGL headers using python script. The script uses a few parameters, so there is very much variants of package.
Possible Fix
Use something like parameters (or features like in Rust's cargo). For example:
[[dependency]]
package = "buckaroo-pm/glad"
version = "branch=master"
features = {
    profile = "core",
    api = { gl = "3.2", gles = "" },
    extensions = [
        "GL_EXT_framebuffer_multisample",
        "GL_EXT_texture_filter_anisotropic"
    ]
}

Context
I need to use GLAD as a buckaroo dependency.
Your Environment

Version used: Buckaroo 2.2.0
Operating System and Architecture: Windows 10 x64

Parameters can be passed to Buckaroo packages via the command-line at build-time (demo). These can then be read by the BUCK files of the package in order to configure it.
However, these flags are not part of the resolution process, so it is up to the user to determine the correct set of parameters. This can always be made to work, but it can prevent things from working out-of-the-box.
I think this proposal would be a good improvement.
An open question is how this should work in practice. Can a package require flags for its dependencies be enabled? Can a package mark flag-sets as conflicting? Should a package declare what are valid settings? What is the syntax? How does this interact with the resolver?
It would be good to discuss this before diving into an implementation.

Overview of Rust approach: https://doc.rust-lang.org/cargo/reference/manifest.html#the-features-section

So, there can be problem with this dependency tree:

package1

package2

package2

If we have parameters, this can became a real problem. This can be solved with something like peer dependencies in NodeJS.
So, in this case, package1 will have a peer dependency package2 and root project will have a dependency package2 which will be used by package1. Well, then package1 will force root project to have a dependency package2. This approach needs some way to declare and merge features of package2 from root project and package1. In particular, merging strategy can be defined in package2 (for example set, array, etc.).
I think that features should be an object (but for simplicity without objects inside). So, there should be unit types (string, int). Then, the object will have only values of units and arrays (only of units).
About rust's dependencies based on features, we can use this syntax:
[[dependency]]
name = ...
condition = "feature1"

Conflicting feature sets can be checked by BUCK config, it seems that it is easier to implement them there than in buckaroo.

If we have parameters, this can became a real problem. This can be solved with something like peer dependencies in NodeJS.

In Buckaroo, packages are "peer" (we call them "public") dependencies by default. To have a "private" dependency (like in NPM by default), whose version does not need to be shared with others, you must add private = true.

So, in this case, package1 will have a peer dependency package2 and root project will have a dependency package2 which will be used by package1. Well, then package1 will force root project to have a dependency package2. This approach needs some way to declare and merge features of package2 from root project and package1. In particular, merging strategy can be defined in package2 (for example set, array, etc.).

Your example is supported by Buckaroo. The manifest for package should be something like:
[[dependency]]
package = "package1"
version = "*"
private = true

Conflicting feature sets can be checked by BUCK config, it seems that it is easier to implement them there than in buckaroo.

This is true. It might be nice if a combination of packages that can never work due to the configurations is never picked by the resolver... but this might be expecting too much!

I think that features should be an object (but for simplicity without objects inside). So, there should be unit types (string, int). Then, the object will have only values of units and arrays (only of units).

Interesting. How would integers work with the "condition" syntax?

Forgot to add:
Buck builds lazily, so if you fetch all of the optional dependencies but do not enable the feature then that package will not be built. It is slightly less efficient (since we are "over fetching") but this is not a significant cost compared to "over building".

So, we need some condition syntax, for example:
condition = "feature1" # for boolean features
condition = "feature >= 5" # for integers/floats/versions
condition = "feature == 'abc'" # for previous ones/strings
condition = "'something' in feature" # for sets/arrays

My subjective opinion is that this should be enough. Also, if feature used in condition does not exist, we can consider the whole condition to be false.

Also, then there should be some way to pass features to BUCK configurations and to use them in some convenient way.

Hmm, how are they peer by default? So I can access some functions of package2 from package1 if I a project depends on package1 and package2?

In theory, we can avoid "overfetching":
First download BUCK file of dependency and then execute it until some point (for example, we will force to check features before adding any libraries or binaries).

My subjective opinion is that this should be enough. Also, if feature used in condition does not exist, we can consider the whole condition to be false.

I like this! It would map cleanly to the Skylark (Python) types in Buck.

Also, then there should be some way to pass features to BUCK configurations and to use them in some convenient way.

This is done using the read_config function in Buck: https://buckbuild.com/skylark/generated/read_config.html

Hmm, how are they peer by default? So I can access some functions of package2 from package1 if I a project depends on package1 and package2?

They are "public" in the sense that everyone gets the same version, not in the sense of C++, Java, etc. You can only access the targets of a dependency if you explicitly depend upon it.

In theory, we can avoid "overfetching":
First download BUCK file of dependency and then execute it until some point (for example, we will force to check features before adding any libraries or binaries).

I think it would be hard to make this work, and it might not be worth it. Remember that Buckaroo packages are source-code, so they are quite small.
A simpler approach would be to move the configuration logic into Buckaroo and then the BUCK files access the values from a configuration file generated by Buckaroo. This maintains the one way data-flow we have now:
Manifests -> Buckaroo -> BUCK files + configurations -> Buck -> Clang, GCC etc.

I think it's better to leave only BUCK and download the whole package in any case (at least, it can be changed in future).
Also, since we have buckaroo_macros, we can add functions for features into there.

But also, that type system is not always convenient for configuration in the example:
    api = { gl = "3.2", gles = "" },

Maybe we should allow using flat object as a feature?

Due to TOML restrictions, the config will look like:
[[dependency]]
package = "github.com/Tarik02/glfw"
version = "branch=fix-windows"

  [[dependency.feature]]
  name = "profile"
  value = "core"

  [[dependency.feature]]
  name = "api"
  value = { gl = "3.2", gles = "" }

  [[dependency.feature]]
  name = "extensions"
  value = [
    "GL_EXT_framebuffer_multisample",
    "GL_EXT_texture_filter_anisotropic"
  ]

Does the example you give above work when there are multiple dependencies with different features?

Yes, you can see more info about array of tables in table here.

Ah OK, makes sense.
The next question is where the feature flags would be written to after install. We already write the dependency lists to .buckconfig.d/.buckconfig.buckaroo, so that is the obvious place.

Yes, I thought about it. I think it is good place for the features. Also, it's needed to modify buckaroo_macros.bzl to add functions to access features list. Features should be package-local (package can only access it's features).

Also, I have a question: is there a way to get know what package are we building from function in .buckconfig.d/.buckconfig.buckaroo?

Also, it's needed to modify buckaroo_macros.bzl

I think we should explore using just read_config before extending the macros. Once we add a macro, it is very difficult to change them without breaking packages.

Also, I have a question: is there a way to get know what package are we building from function in .buckconfig.d/.buckconfig.buckaroo?

I don't think so. We could write a "self_name" configuration value or something into this file to enable this.

I think we should explore using just read_config before extending the macros. Once we add a macro, it is very difficult to change them without breaking packages.

@njlr, if we just add a macro, nothing bad happens. Yes, at start we can use just read_config, but in future, there should be some macro like get_feature_int (or without type name), etc.

I don't think so. We could write a "self_name" configuration value or something into this file to enable this.
That was a wrong question, my bad.

if we just add a macro, nothing bad happens.

Well we are committed to maintain macros once they are offered. If they are provided and people use them, then changing them will break packages. I would call this a bad thing! :slightly_smiling_face:

Well we are committed to maintain macros once they are offered. If they are provided and people use them, then changing them will break packages. I would call this a bad thing! 🙂

Have no words to say xD. At least, if features will be useful, we should consider adding macros for them.


Add Roccat support

Reddit user /u/kuronomia requested Roccat support: https://www.reddit.com/message/messages/eh10zf
Hoping that they can dig up info on the SDK for me, because it wasn't obvious how to get a hold of it.

Would really appreciate Roccat Support :)

You should start by complaining to Roccat for not providing an SDK. Nobody can easily/reliably write third-party software for their stuff until they do.

Well, lots of people already complained, are they the only one who didn't release a SDK?

As far as I know. SteelSeries is the other one that's been requested, but it's my fault for not implementing support yet.


Fix No Auth Provider found

This PR is based on #2.
/fix #3

@superbrothers thanks for the updates, I will take a look today.


Bug report: php70-mcrypt install

Remember to follow the pre bug report guide beforehand. Failure to do so might get your issue closed.
Description of issue
Hello, have problem with php70-mcrypt installation.
Output of `brew cask  --verbose`
brew cask install homebrew/php/php70-mcrypt --verbose
Error: undefined method `join' for nil:NilClassMost likely, this means you have an outdated version of Homebrew-Cask. Please run:

    brew uninstall --force brew-cask; brew untap phinze/cask; brew untap caskroom/cask; brew update; brew cleanup; brew cask cleanup

If this doesn’t fix the problem, please report this bug:

    https://github.com/caskroom/homebrew-cask#reporting-bugs

/usr/local/Homebrew/Library/Homebrew/cask/lib/hbc/source/tapped_qualified.rb:20:in `path_for_query'
/usr/local/Homebrew/Library/Homebrew/cask/lib/hbc/source/tapped_qualified.rb:7:in `me?'
/usr/local/Homebrew/Library/Homebrew/cask/lib/hbc/source.rb:29:in `block in for_query'
/usr/local/Homebrew/Library/Homebrew/cask/lib/hbc/source.rb:27:in `each'
/usr/local/Homebrew/Library/Homebrew/cask/lib/hbc/source.rb:27:in `find'
/usr/local/Homebrew/Library/Homebrew/cask/lib/hbc/source.rb:27:in `for_query'
/usr/local/Homebrew/Library/Homebrew/cask/lib/hbc.rb:57:in `load'
/usr/local/Homebrew/Library/Homebrew/cask/lib/hbc/cli/install.rb:20:in `block in install_casks'
/usr/local/Homebrew/Library/Homebrew/cask/lib/hbc/cli/install.rb:18:in `each'
/usr/local/Homebrew/Library/Homebrew/cask/lib/hbc/cli/install.rb:18:in `install_casks'
/usr/local/Homebrew/Library/Homebrew/cask/lib/hbc/cli/install.rb:9:in `run'
/usr/local/Homebrew/Library/Homebrew/cask/lib/hbc/cli.rb:108:in `run_command'
/usr/local/Homebrew/Library/Homebrew/cask/lib/hbc/cli.rb:147:in `process'
/usr/local/Homebrew/Library/Homebrew/cask/cmd/brew-cask.rb:8:in `<top (required)>'
/System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/2.0.0/rubygems/core_ext/kernel_require.rb:55:in `require'
/System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/2.0.0/rubygems/core_ext/kernel_require.rb:55:in `require'
/usr/local/Homebrew/Library/Homebrew/brew.rb:23:in `require?'
/usr/local/Homebrew/Library/Homebrew/brew.rb:102:in `<main>'
Error: Kernel.exit

Output of `brew doctor`
brew doctor
Please note that these warnings are just used to help the Homebrew maintainers
with debugging if you file an issue. If everything you use Homebrew for is
working fine: please don't worry and just ignore them. Thanks!

Warning: Homebrew's sbin was not found in your PATH but you have installed
formulae that put executables in /usr/local/sbin.
 Remove cask from the command.


fix(deps): replace dependency @material-ui/core with @mui/material ^5.0.0

This PR contains the following updates:

Package
Type
Update
Change

@material-ui/core (source)
dependencies
replacement
^4.12.4 -> ^5.0.0

⚠ Dependency Lookup Warnings ⚠
Warnings were logged while processing this repo. Please check the Dependency Dashboard for more information.
This is a special PR that replaces material-ui-core with the community suggested minimal stable replacement version.

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

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

This PR has been generated by Renovate Bot.

Renovate Ignore Notification
Because you closed this PR without merging, Renovate will ignore this update (^5.0.0). You will get a PR once a newer version is released. To ignore this dependency forever, add it to the ignoreDeps array of your Renovate config.
If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR.


Security issues?

Using the latest version of npm i got this.

As discussed offline let's keep this issue open but considering maybe the change of architecture auto-closes this issue ;)


Installation

Hi,
I am new to ansible. The ansible-galaxy role was specified incorrectly in the readme. It should be flaskapp, not ansible-flaskapp. The installation command is therefore:
ansible-galaxy install hypebeast.flaskapp

Thanks for reporting the issue. I'll have a look at it.

You're right. I fixed it.
Thanks for the bug report.


Upgrade to OCP 4.4 base

Migrated Jenkins Pipeline to Tekton
Updated all images and content
Fixed PHP nationalparks

Linked to:
https://github.com/openshift-roadshow/nationalparks/pull/20
https://github.com/openshift-roadshow/php-s2i-mongodb
https://github.com/redhat-cop/agnosticd/compare/development...blues-man:development

LGTM!

Thanks for your review @jankleinert @ryanj, I resolved conflicts just using this branch as primary source for the content since it has been updated a lot and doing patches and diff per commit (mostly repeated images and typo fixes from ocp-4.2) would be extra effort that we can avoid imho.


Feedback on vscode's Webview.toWebviewResource API proposal

Overview
VS Code 1.37 added a proposed api to help webviews create uris for local resources: https://github.com/microsoft/vscode/blob/192e15b613dd4f4dab9c735b7556e175580c6011/src/vs/vscode.proposed.d.ts#L1166
The main addition is a toWebviewResource method property on webviews that translates a local file uri into a webview uri (i.e. one that uses the special vscode-resource: scheme). This api is being added primarily to support running VS Code on the web where the existing vscode-resource: scheme will not work
Request
As a popular user of the VS Code webview API, we'd appreciate your feedback on this api proposal. Does it work as advertised? Does the documentation for it make sense? Is it missing any functionality? Feel free to leave your feedback on this issue or on https://github.com/microsoft/vscode/issues/79242
You can try out the proposed api in VS Code 1.38 insiders by following these instructions. Please let me know if you have any questions about testing it out
PS: There are no plans at the moment to remove the vscode-resource: scheme so your extension should continue to work on desktop VS Code even if it does not adopt this new API

@mjbvz Sorry for the delay -- this looks good to me, and should be vary simple to adopt once it is in stable.


Proposal to avoid memory copies between jacobsa FUSE library and application code

Hello,
I work with a team of engineers and we are using a FUSE filesystem that uses the jacobsa library. Recently, we have been looking into performance improvements for reading and writing large files, and we found that copying data to the ReadFile Dst buffer and from the WriteFile Data buffer is reducing our performance. We created a prototype to remove these copies and saw up to 100-200 MB/s throughput performance improvements (~500 MB/s -> ~700 MB/s) for reads and (~400 -> ~600 MB/s) for writes.
The "vectored read" improvement added in this PR is an important first step for skipping the data copy in ReadFile, but unfortunately it does not seem to fully satisfy our use case, because we don't have any way of knowing when the data has been successfully written back to the kernel (and thus, we don't know when we can free up the data we are holding in memory).
For WriteFile, we have a similar problem, because we want to return a response to the kernel as soon as possible, but we may not yet be ready to free up the InMessage containing the data for the WriteFile request.
I am open to suggestions here, but our proposal to satisfy our use cases for both ReadFile and WriteFile is to add an interface that would essentially wrap the Freelists that are used to get and free up InMessage and OutMessage.
For example, we would add an interface that looks something like:
type MessageProvider interface {

  func GetInMessage(size) *InMessage

  func GetOutMessage(size) *OutMessage

  func PutInMessage(InMessage)

  func PutOutMessage(OutMessage)

}

The mount configurations could allow a custom implementation of this interface to be provided, so that our application code can add hooks to both get notified when the In/OutMessage is no longer needed because the response has been written to the kernel, and we can also control when the In/OutMessage is actually freed up for future reuse.
If no custom implementation is provided in the mount configuration, then a default implementation of this interface would be a lightweight wrapper around the Freelists that exist today.
I am very happy to create a pull request for this issue. Do you have any particular thoughts and/or concerns before I do so?
Thanks,
Scott

Hey Scott! That all seems reasonable to me. I haven’t looked much at the freelists TBH (they predate my involvement with the package), but we can hash out details over the actual PR. No thoughts or concerns beforehand :)

Hi @stapelberg, I created a PR to address this issue: https://github.com/jacobsa/fuse/pull/144
Could you please take a look when you get a chance? Thanks!


Documentation update for the commerce pub/sub topic subscriptions

Documentation update for the commerce pub/sub topic subscriptions

This is configurable for producer portal, so it only needs to be documented for partner portal integrations.


[Blazor][Fixes #12788] Fixes blazor reconnection tests

Enables a customer websocket feature in tests that can be used to trigger errors on the server at will.
Enables conditionally turning errors through cookies so that normal tests aren't affected and run against the product bits.
Cleans up dead code in blazor.server.js that is not longer required.
Moves the reconnection tests out of ComponentsApp.App into basic test app.

Where are my karma points for this @SteveSandersonMS?

Where are my karma points for this @SteveSandersonMS?

💯 🥇

This may well be good (though to be clear, I'll await more explanation before thinking I understand it).
However, do you think you'd be able to check the current real-world behavior of the product code before we consider this to be a solution?

However, do you think you'd be able to check the current real-world behavior of the product code before we consider this to be a solution?

I think this is the right approach. We need to dive in to the real-world behavior and SignalR likely also needs to consider changes here.

I rebased this PR and removed all the copied websocket code. This should be good to go. Independently of what we end up doing with graceful disconnection, we want to take this PR as it offers advantages for testing reconnection. (Mainly no test stuff in product code) and cleans up our tests.

Is the idea that using fault injection in the websocket is a much better approach than forcing the client-side code to disconnect? What are the advantages?

No test code in product code
We can decide for how long we fail
The failure pattern, etc.

No test code in product code

This was true before too.
Can you go into more detail about the other things?

This was true before too.

No it wasn't
https://github.com/aspnet/AspNetCore/pull/12813/files#diff-fdbaeed1d036d944c000f3ef1aa7d066L92

Can you go into more detail about the other things?

We simply disable the socket completely right now, but with this approach we can prevent the client from reconnecting as many times as we want, or force intermittent re-connections.
By controlling it on the server we get more a more realistic scenario than triggering the connection close from the client side. We could for example choose to trigger the connection failure at different points.

No it wasn't

Yeah, you're right! Sorry for mixing that up.

I'm guessing that whether or not we proceed with this PR depends on whether we're proceeding with #12853.

@SteveSandersonMS I still want to get this one in, as I think it cleans-up test code from product code and that's worth it.

@SteveSandersonMS It also represents the scenario more accurately than the client closing the connection.

If it's a tradeoff between:

Having the forceDisconnect method on _internal in the blazor.server.js
Or having all this infrastructure for interrupting a websocket connection

... then given how massively more complex #2 is I'm not totally convinced it's a pragmatic choice. The internals of how websockets work are meant to be transparent to us. If this capability existed in SignalR then sure we'd use it, but since it's not I'm wary about us owning it. Let's discuss in the sync later.

Closing as we'll leave the test around and we have an alternative approach


Partial PDB use

Is your feature request related to a problem? Please describe.
I have two PDB files, one of which has been trimmed but matches the executable. The other PDB was not trimmed (and therefore contains full type information), but is for a slightly different version of the exe, and therefore the symbol addresses do not match.
Describe the solution you'd like
I'd like to be able to pick and choose what parts of a PDB are used by Ghidra, so I could opt to use the type information from the full PDB, but the symbol addresses from the partial PDB.
Describe alternatives you've considered
Developing a tool to merge PDB files, but this would be a rather painful process.

I'd like to experiment some.
What mechanisms do you expect will be used to created the full and trimmed PDBs?
Reference: https://docs.microsoft.com/en-us/cpp/build/reference/debug-generate-debug-info?view=vs-2019
Is an external tool used to "trim" anything?
What do you see in a trimmed PDB? Do you just see public symbols? global symbols?
If I know what options or tools are used, I might be able to generate test sets with which to experiment.

If I know what options or tools are used, I might be able to generate test sets with which to experiment.

The motivating project behind this proposal is the one in the mention seen above. The PDBs are from the Unity game engine, and you can find them on their symbol server.

What do you see in a trimmed PDB? Do you just see public symbols? global symbols?

Essentially just public and global symbols.

What mechanisms do you expect will be used to created the full and trimmed PDBs?
[...]
Is an external tool used to "trim" anything?

An external tool was used to trim them, as PDBs under the Unity_x64_mono.pdb directory on the symbol server are untrimmed, despite the equivalents included with the associated release of the engine being trimmed.
I've attached the included PDB for Unity 2018.4.26f1 to this comment, and you can find the untrimmed counterpart on the symbol server here.
unity_x64_mono.zip


AddModulesAsync only 1 argument?

I copy and pasted the sample to see if it work but this send me an error.
        public async Task InitializeAsync()
        {
            await _commands.AddModulesAsync(Assembly.GetEntryAssembly(), _services);
        }

Error: AddModulesAsync can't accept 2 arguments.

First off, what version of Discord.Net are you using? Second off, these sort of issues are better handled in the support channel in [https://discord.gg/jkrBmQR](Discord API) (dotnet_discord-net)

I have Discord.Net v1.0.2

the 2.0 version is the nightly version?


Add optional ext keyword argument to set_cover()

Previously, set_cover() would rely on the Python standard module imghdr to determine the type of the specified cover image file. Unfortunately, imghdr does not support SVG, so set_cover() could not handle that type (which is permitted by the EPUB spec).
Detecting SVG files programmatically is nontrivial. Instead, simply provide an option for the client to specify the file type with the new keyword argument.
This introduces a minimal addition to the public API of the module.

I have two reservations about this PR:

The parameter name ext. It's not exactly an extension. But it's not exactly a MIME type, either. I'm not sure what a better name would be.
This PR introduces unit testing to the application. There weren't any examples to follow in the existing tests (only high-level integration tests), so I've used my personal preferences regarding mocking and using a class. I'm certainly open to other approaches.

Coverage decreased (-0.4%) to 98.438% when pulling d32e7b583e750e8d760c9eb5cad69b94aab4298e on elebow:set-cover-arg-extension into 255577350fc2aa428073592bf9d9fe15fd110fa7 on anqxyr:master.

It's not exactly an extension. But it's not exactly a MIME type, either.

It is exactly an extension, since it's used as the extension in the filename for the cover. Although I think that using the full word extension would be more clear for the public API instead of ext.

This PR introduces unit testing to the application.

Not a fun of the unittest lib or class-based tests. mkepub already uses pytest for testing, and it has fixtures that should work just fine with function-based tests. Will rewrite this a bit later before merging.

Changed the parameter name to extension.
Changed the tests to use pytest, but also pytest-mock. I'm not sure how you feel about that plugin, but the general approach is about the same as it was before.
Regarding the test class, it's purely for organizational purposes in the test code (and allows, for example, pytest -k TestSetCover). Here's a branch without it, if you prefer that: https://github.com/elebow/mkepub/commits/set-cover-arg-extension-no-test-class. I can update this PR you want.


New version: Tenpi.PhotoViewer version 0.2.5

Pull request has been created with komac v2.6.0 :rocket:
Microsoft Reviewers: Open in CodeFlow

URL: https://github.com/Moebits/Photo-Viewer/releases/download/v0.2.5/Photo-Viewer-Setup-0.2.5.exe
Status Code: 200
(Automated message - build 896)


Compile script with all static files, etc.

How do i compile app, so all static files, html templates would be inside app ?

You could give this a try: https://github.com/rakyll/statik


Fix Mac Profiling build

Some of the new kext unit tests that have been added recently need PerfTracing_RecordSample to be defined when linking as part of the 'Profiling(Release)' build.
Once this PR is merged I'll add the 'Profiling(Release)' build to the "PR - Mac - Build and Unit Test" definition to ensure the profiling build doesn't break again.

/azp run GitHub VFSForGit Mac Functional Tests