Allow computed get/set to have different types

resolve #7271
In certain cases, we would like the computed property's getter and setter to have different types. This would provide added convenience in our usage, such as having the getter return a string while the setter accepts an object. In this PR, I have added a second generic parameter to the computed property to specify the type of the setter. With this enhancement, we can set different types for the getter and setter of computed using the following approach.
Examples:

const obj = ref({
  name: 'foo'
})

const newObj = computed<string, typeof obj.value>({
  get() {
    return JSON.stringify(obj.value)
  },
  set(val) {
    obj.value = val
  }
})
console.log(newObj.value) // string

newObj.value = { name: 'bar' } // object

That's great! It's exactly what I wanted to do before. However, we need to explore ways to ensure compatibility with TS versions higher than 4.4. Perhaps we can use typeVersions to differentiate between TS >= 5.1 and other versions.

I don't think of a good compatibility solution at the moment. If we use typeVersions to distinguish, it will cause users to modify the tsconfig.json file in the project.

That's great! It's exactly what I wanted to do before. However, we need to explore ways to ensure compatibility with TS versions higher than 4.4. Perhaps we can use typeVersions to differentiate between TS >= 5.1 and other versions.

If you use typeVersions to handle it, will it cause users to need to modify the tsconfig.json file in the project?

No, it doesn't need to. The only thing that needs to be done is to add typesVersions in the package.json file of Vue.
https://www.typescriptlang.org/docs/handbook/declaration-files/publishing.html#version-selection-with-typesversions

That's great, we can use typesVersions to differentiate versions less than 5.1.


linuxquota: 4.05 -> 4.06

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/quota/versions.
meta.description for linuxquota is: "Tools to manage kernel-level quotas in Linux"
meta.homepage for linuxquota is: "https://sourceforge.net/projects/linuxquota/"
meta.changelog for linuxquota is: ""
Updates performed

Version update

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS

The tests defined in passthru.tests, if any, passed

0 of 0 passed binary check by having a zero exit code.

0 of 0 passed binary check by having the new version present in output.

found 4.06 with grep in /nix/store/bi1d27ygfzmfw1hvg6gy6pis5c1q1d7a-quota-4.06

directory tree listing: https://gist.github.com/0d5a80f04bacfad78576097b93004962

du listing: https://gist.github.com/0c60c1beaa301568330cad661e8df3de

Rebuild report (if merged into master) (click to expand)

12 total rebuild path(s)

4 package rebuild(s)

4 x86_64-linux rebuild(s)
4 i686-linux rebuild(s)
0 x86_64-darwin rebuild(s)
4 aarch64-linux rebuild(s)

First fifty rebuilds by attrpath
linuxquota
quota
unixtools.quota
xfstests

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/bi1d27ygfzmfw1hvg6gy6pis5c1q1d7a-quota-4.06 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A linuxquota https://github.com/r-ryantm/nixpkgs/archive/9282a96ebcbc683766ccf490bc54c7539c29a60c.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/bi1d27ygfzmfw1hvg6gy6pis5c1q1d7a-quota-4.06
ls -la /nix/store/bi1d27ygfzmfw1hvg6gy6pis5c1q1d7a-quota-4.06/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

3 packages built:

linuxquota
unixtools.quota
xfstests

Maintainer pings
cc @dezgeg for testing.

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

3 packages built:

quota (linuxquota)
unixtools.quota
xfstests


can we receive webhook requests as well

i want to receive the webhook requests in my streamlit app? is that possible?

Are you referring to something like this? https://github.com/alphasecio/webhook-server

thanks, exactly what i wanted


Added some help to Write-String

#10
Let me know if the help based OK for you

@Ichigo49 Thanks very much for your help! If you want let me know your twitter username, I'll give you a shoutout :)


refactor validate_publish to supports :publish

What?
Refactor all method definitions called validate_publish to DSL like definition supports :publish
Background
The validate_publish methods are used mainly by the UI to query an instance if it supports a specific feature. The return value is a bit obscure. It returns a Hash with two keys :available and :message. If :available is false, then the feature is generally unsupported by all instances of that class. If true, then it's generally supported, but you would have to look at the :message. If this is present, it's not supported for that particular instance, because of the reason named by :message.
The SupportsFeatureMixin seeks to remedy this by introducing a nice DSL like approach to define the conditions when a feature is supported or not. Please read the documentation. Things worth noting:

You will have to register the feature here
By default all features are unsupported. So mostly you'll only want to define supports :publish on subclasses that actually support it - a whitelist approach. Not the other way round.

Why?
Other than making the definition more appealing it also lets us produce awesome spreadsheets like this - everybody likes tabellen, right?
How?

Have a look at https://github.com/ManageIQ/manageiq/pull/9683 as an example PR
git grep 'validate_publish' to find what to refactor - peek
git grep 'is_available.*:publish to find if the UI still uses the old methods and refactor those too

Bonus Points
Also have a look at the amazon provider if something lurks in there.
please leave a comment to grab this issue.
@miq-bot add_label hacktoberfest

@miq-bot assign anuvazhayil

@anuvazhayil looks like our bot doesnt want to assign to people outside our team.
I guess you still want to work on this?

@durandom Someone already works on it or I can take it?


resolves #371 consult :to_dir option on document to resolve output directory

Thanks!
We should probably also update the JavaScript code:
https://github.com/Mogztter/asciidoctor-kroki/blob/4c9cb535ec6747f2e76d088944451114957002e3/src/fetch.js#L7
I will try to add a test case on both Ruby and JavaScript to make sure that the to_dir option is honored.


Prevent display problems caused by narrowing of the browser window.

One of the testers had his screen fairly narrow and it caused display issues, particularly in the file upload section. See screenshot. It would be good to address this. My guess is that setting a minimum width somehow would be the way to go.

Preventing a narrower screen may be an accessibility concern and might prevent the site from being useful when people use tablets or mobile devices.  A better solution would be to develop a design for this row for narrower viewports.

@astridu This isn't a high priority, but would benefit from your input when you have a chance. Thanks.

We probably should have some breakpoints, but wondering if the screen was narrow because she had the testing doc open side by side? Or is this a more widespread problem? I hadn't thought of it because I assumed people wouldn't be viewing on tablet/mobile, but if you think it could be a common use case where they reduce the size of their window because they're working side-by-side on another browser, we can revisit.

I have no idea why he had the screen so narrow, since I could see a lot of desktop on the right. Screenshot below.

I would not expect people to be doing this on a tablet or mobile, because they would need to have easy access to the files to upload as well. I have never had a user mention doing it on a mobile device.

@amyehodge There is no barrier to uploading from mobile devices.  Many people use tablet, or tablet like devices (I'm thinking Microsoft Surface) as their primary devices.

@jcoyne that's true for many things, but I find it less likely that people are doing their main research on mobile devices or even have files stored in places that are accessible via mobile devices. How easy is it to get to a department server, for example, via a mobile device? Then again, I remember being shocked when some previous survey of library users produced a comment from someone who complained of some task on our website being difficult to do from a mobile WHILE RIDING A BIKE. Is there a way we can find out how many people access sdr.stanford.edu from a mobile device?

I believe that information is available via google analytics. I don't have the account for that.
Regardless, of what the usage data is now, the current sdr.stanford.edu works acceptably on all sizes. I don't think we should go out of our way to implement a design that would prevent people from using the site on the device of their choice.

I think there's a screen width/zoom level that results in the save/publish button disappearing in the current Hydrus. It's come up a few times when helping users but may have been addressed.
I would think a tablet is more likely than a phone as mobile use, but that even if people aren't doing the whole deposit on mobile they may want to review progress or check on previous deposits there. FWIW, I've remediated items from my phone before, but I would discourage generalizing from my own usage.


Protocol state hash in pending coinbase stacks

Add a protocol state hash (State_hash.t) to pending coinbase stacks.
When we do a push operation, we update the stack data, as before, and now also the state hash component. Coinbase transactions contain a state body hash, which is used to update the state hash. Staged ledger diffs now contain a state body hash computed from the previous protocol state, to be used when creating a coinbase.
When adding a coinbase, we store the state hash of the resulting stack as the previous state hash in the updated stack at the top level of the pending coinbases. That's used as the state hash when we add a coinbase to a new stack.
Note that this change doubles the hashing burden for this software component.
Closes #2536.

is this still live?

It's live, as far as I know. I'm waiting for review before fixing the conflicts.

Did merge of develop, still needs some cleanup.

Put a temp commit in, code is in known-broken state.

Abstracted over the two checked pushes. Tests break now, though, presumably because of changes elsewhere in the codebase.

@imeckler The push for the state hash changed, so its algorithm is different than the push for the stack data; so there's no code to be factored out.

Could you add a validation in External_transition.Staged_ledger_validation.validate_staged_ledger_diff to check if the state_body_hash in the staged_ledger_diff is the equal to the hash of Protocol_state.body (External_transition.Validated.protocol_state parent.validated_transition) ?

Actually, the state_body_hash in staged_ledger_diff is redundant. Since we know what the previous state body hash is, it could be passed as an argument directly to Staged_ledger.apply.

Actually, state_body_hash in staged_ledger_diff is redundant. Since we know what the previous state body hash is, it could be passed as an argument directly to Staged_ledger.apply.

We could separate the state_body_hasn. I was thinking it's nice to package up all that apply needs in a single argument.

Actually, state_body_hash in staged_ledger_diff is redundant. Since we know what the previous state body hash is, it could be passed as an argument directly to Staged_ledger.apply.

We could separate the state_body_hasn. I was thinking it's nice to package up all that apply needs in a single argument.

We broadcast Staged_ledger_diff so we don't want anything in there that is available in the current state


Add NetworkProtection controller

Proposed Changes
The NetworkProtection controller ensures that a finalizer is present on the Network resource as long as it is being referenced/used by resources like NetworkInterfaces or AliasPrefixes.
Fixes #444

Thanks @adracus for the review! Regarding the non cached access: from looking at the pv protection controller there is only one GET for the PV object via the PersistentVolumeLister. Determining if a PV is being used is done just by checking the Phase of the PV - so pretty trivial to what we need to do here.


how to deploy the application to Heroku?

refer to #21, tooling is not recommended to be included in devDependencies, so what is the recommended way to deploy the application built by tooling to Heroku?

The bundled results are just static files, what do you mean by deploy them to heroku?

Currently, I need to do the following steps to deploy my application to
Heroku:

compile bundle.js on my laptop
stage them onto the repository
git push to Heroku

However, I soon find that my build directory messed up by expired versions
of bundle.js. Is there any better ways to avoid the situation?
If bundle.js needed to be compiled on Heroku, I would have to add tooling
as devDependencies and register postinstall hook in package.json
BTW, I use harp.js as my production web server.
EGOISTIAN<EMAIL_ADDRESS>於 2016年3月12日 星期六寫道：

The bundled results are just static files, what do you mean by deploy
them to heroku?
—
Reply to this email directly or view it on GitHub
https://github.com/egoist/tooling/issues/22#issuecomment-195679366.

--
吳恒毅
Tel: 0917-131-831
email<EMAIL_ADDRESS>

Feel free to install tooling as devDep on heroku, it's only not recommended to install tooling on your local machine, because it's slow. Or is there a way to install tooling globally on heroku? I dunno that.
If you feel messy about your build dir, just do add rm -rf build into your npm script before build.


Change package name to underscore

Description

Change package name to underscore so both wheel and tar.gz has the same pattern:
ms_recommenders-0.6.0.post1623931532-py3-none-manylinux1_x86_64.whl
ms_recommenders-0.6.0.post1623931532.tar.gz

Related Issues

Checklist:

[ ] I have followed the contribution guidelines and code style for this project.
[ ] I have added tests covering my contributions.
[ ] I have updated the documentation accordingly.
[ ] This PR is being made to staging branch and not to main branch.

If scikit-learn does what we have been doing, is there a need for this change?

i agree, using hyphens in the package name and underscores in the import is not unusual. i think we should keep it as is and not go through creating a new package on pypi

Happy to revert this, this is like a cosmetic change, so not super important
Just to provide more clarity. with ms-recommenders in the setup.py, we get these two files:
ms_recommenders-0.6.0.post1623931532-py3-none-manylinux1_x86_64.whl
ms-recommenders-0.6.0.post1623931532.tar.gz

with ms_recommenders in the setup.py, we get this:
ms_recommenders-0.6.0.post1623931532-py3-none-manylinux1_x86_64.whl
ms_recommenders-0.6.0.post1623931532.tar.gz

The name of the package in pypi is the same: ms-recommenders, I was able to upload to test.pypi the files with ms_recommenders: https://test.pypi.org/project/ms-recommenders/0.6.0.post1623931532/, see here the files: https://test.pypi.org/project/ms-recommenders/0.6.0.post1623931532/#files.
But again, happy to revert this

oh ok, i was worried we were proposing a name change to the package. i'm fine with this.


v1.6: On call of onEnable, on disable from business-logic, persist this change inside database

…nge inside database
Describe your changes
Storage of enable/disable calls inside database.
Issue ticket number and link
https://github.com/EVerest/libocpp/issues/626
Checklist before requesting a review

[x] I have performed a self-review of my code
[x] I have made corresponding changes to the documentation
[ ] If OCPP 2.0.1: I have updated the OCPP 2.0.1 status document
[x] I read the contribution documentation and made sure that my changes meet its requirements

Hi @bWF0dGhpYXMK , thanks for this contribution.
Im closing this because on_enabled and on_disabled can and shall be called even if the operative state shall not be persisted (e.g. when temporarily disabled for FW updates or the charger logic suspends charging for some reason). Libocpp takes care of the persistence for ChangeAvailability.req internally.


Unable to install module

Always it is returning Couldn't download feature2:-2.Help me in this.

Hi @DurgaArunkumarSmitiv , I am able to run the demo app but not my own app.
Note: I create an app based on this link

Hi @DurgaArunkumarSmitiv , I found the reason why I am not able to open the feature.
In the code of app -> ... -> MainActivity:
Intent intent = new Intent().setClassName(getPackageName(), "com.bapspatil.feature1.FeatureOneActivity");

Please change the com.bapspatil.feature1.FeatureOneActivity to your package name.
It works for me, hope it can help you too 😄


ddoc_cache_remove_test fails in ets:info

ddoc_cache_remove_test: check_refresh_test_...*failed*
in function ddoc_cache_remove_test:'-remove_custom_error/1-fun-1-'/0 (test/ddoc_cache_remove_test.erl, line 188)
**error:{assertEqual,[{module,ddoc_cache_remove_test},
              {line,188},
              {expression,"ets : info ( ? CACHE , size )"},
              {expected,0},
              {value,undefined}]}
  output:<<"">>

This is our most frequent failure in Jenkins CI.
/cc @davisp

This is now starting to show up in Jenkins.
https://builds.apache.org/job/CouchDB/job/master/388/
https://builds.apache.org/blue/organizations/jenkins/CouchDB/detail/master/384/pipeline

this one is actually ddoc_cache_remove_test: check_refresh_test_

Too old to act on; closing for now.


only set the execType to RERAN, if the changeset was actually executed

Impact

[x] Bug fix (non-breaking change which fixes expected existing functionality)
[ ] Enhancement/New feature (adds functionality without impacting existing logic)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Description
Bugfix for issue #3913.
In the UpdateVisitor class the result of the changeset execution "execType" is automatically set to RERAN, if the previous runstatus of the changeset is not equal to NOT_RUN (even if the changeset got skipped or failed). I changed the logic so that the execType is set to RERAN, only if the changeset executed successfully.

Things to be aware of

Things to worry about

Additional Context

Initial/Pre-Review Thoughts
Change looks like it's in the right spot, thanks for the fix for the issue, @AlexGruebel !
Questions I have:

None

Potential risks:

None

What could make the full review difficult:

Nothing


Pin docker images to SHA

Description
This PR pins the base docker images in the Dockerfiles to commit SHAs so that Renovate (or Dependabot if Renovate doesn't work) can create PRs each time there is a change in the upstream base images that the base images are set to use as new SHAs are generated on every upstream change. Not sure if Renovate will also update the OS versions but if it doesn't then we will have to do the Alpine version updates manually for now.
Please note that I have pinned it to an older SHA to verify that Renovate (or Dependabot if Renovate doesn't work) will create a PR.
Testing instructions

[ ] Review code
[ ] Check Actions build

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

Project coverage is 93.66%. Comparing base (588a98d) to head (5311c92).
Report is 4 commits behind head on develop.

Additional details and impacted files
@@           Coverage Diff            @@
##           develop     #436   +/-   ##
========================================
  Coverage    93.66%   93.66%
========================================
  Files           60       60
  Lines        15990    15990
  Branches      2072     2072
========================================
  Hits         14977    14977
  Misses        1008     1008
  Partials         5        5

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

Renovate created PRs to update the SHAs https://github.com/ral-facilities/inventory-management-system/pull/443/files and https://github.com/ral-facilities/inventory-management-system/pull/444


Add disallow-proc-self-fd-workingdir.yaml (CVE-2024-21626)

Mitigation for CVE-2024-21626
Related Issue(s)

Description

Checklist

[x] I have read the policy contribution guidelines.
[x] I have added test manifests and resources covering both positive and negative tests that prove this policy works as intended.
[x] I have added the artifacthub-pkg.yml file and have verified it is complete and correct.

I think the policy is not sufficient to prevent an attack, because the WORKDIR may be specified in the container image and not in the k8s manifest.

That's true and this should probably be specified in the description of the policy.

The WORKDIR instruction can resolve environment variables previously set using ENV. You can only use environment variables explicitly set in the Dockerfile.

And if I interpret the docker docs correctly, the WORKDIR maybe specified also via environment variables, so the policy should also match on that in k8s manifests?
apiVersion: v1
kind: Pod
metadata:
  name: envar-demo
spec:
  containers:
  - name: envar-demo-container
    image: gcr.io/google-samples/node-hello:1.0
    env:
    - name: WORKDIR
      value: "/proc/self/fd/1"

And if I interpret the docker docs correctly, the WORKDIR maybe specified also via environment variables, so the policy should also match on that in k8s manifests?

This is not correct. Although the environment variable WORKDIR may be set in an k8s manifest, it is not evaluated (picked up).

This isn't going to work with the YAML anchors because Kyverno will interpret spec.definitions.customCheck as a literal path to the resource. Please re-write without using YAML anchors (but still using Kyverno validate anchors).

@lobuhi, status?

No response, closing.


https://github.com/WasmEdge/WasmEdge summary

Installer does not work on Fish shell
https://github.com/WasmEdge/WasmEdge/issues/2749
Issue: Installer does not work on Fish shell
The issue is that a backward incompatible change has been introduced in a commit, breaking the installation for shells different from bash and zsh, which were previously working successfully. The user expects a successful installation.
Potential solutions:

The user has raised the issue and is awaiting a response from the developers.

User '.alabulei1' has tagged the developers and requested their attention.

It is implied that the developers, 'SAtacker' and 'hydai', need to investigate and fix the issue.
                  this result is generated by flows.network. Triggered by @jaykchen

Wasmedge may have a performance error when handling a non-WASI wasm binary.
https://github.com/WasmEdge/WasmEdge/issues/2748
The central problem discussed in the issue is that Wasmedge, when processing a non-WASI wasm binary, is slower compared to other runtimes like wasmtime and wasmer. The user provided a wasm binary file as an example. The main solutions proposed or agreed upon are not mentioned in the post.
                    this result is generated by flows.network. Triggered by @jaykchen

Abortion report on the instruction memory.grow
https://github.com/WasmEdge/WasmEdge/issues/2745
The central problem discussed in the issue is an abortion report on the instruction memory.grow in the WasmEdge project. The user provides the current state and expected behavior, along with the steps to reproduce the issue. Another user comments that they cannot reproduce the issue on their testing platform. The main solutions proposed or agreed upon are not explicitly mentioned in the issue content.
                    this result is generated by flows.network. Triggered by @jaykchen

Crash report about the instruction table.init
https://github.com/WasmEdge/WasmEdge/issues/2744
The central problem discussed in the issue is a crash report related to the instruction table.init. The user expects an exception indicating "OOB" (out of bounds) to be raised instead of a segmentation fault. The main solution proposed is for an internal handler to catch this error and prevent the segmentation fault.
                    this result is generated by flows.network. Triggered by @jaykchen

Crash report about the instruction memory.init
https://github.com/WasmEdge/WasmEdge/issues/2743
The central problem discussed in the issue is a crash report related to the instruction memory.init in the WasmEdge project. The user expects an exception indicating "OOB" (out-of-bounds) to be raised instead of a segmentation fault. The hardware architecture is amd64, and the operating system is Ubuntu 20.04. One suggested solution is for the crash to be caught by an internal handler rather than triggering a segmentation fault.
                    this result is generated by flows.network. Triggered by @jaykchen

Do not terminate while executing the given testcase
https://github.com/WasmEdge/WasmEdge/issues/2733
The central problem discussed in the issue is that while executing a given testcase, WasmEdge hangs and does not terminate. Other wasm runtimes like Wasmer, Wasmtime, and Wasmi also have issues with this testcase. The expected result is unclear due to a lack of understanding of WebAssembly. The main suggested solution is for the maintainer (@hydai) to investigate the problem.
                    this result is generated by flows.network. Triggered by @jaykchen

feat: LFX create a ffmpeg plugin
https://github.com/WasmEdge/WasmEdge/issues/2689
Issue: feat: LFX create a ffmpeg plugin
Label: LFX Mentorship
The issue discusses the need to improve the performance of the mediapipe-rs project, which currently uses Wasm-compiled ffmpeg functions. The proposed solution is to create a ffmpeg plugin for WasmEdge, allowing Wasm applications to call native ffmpeg functions. The expected outcomes include developing the plugin, a Rust SDK for Wasm programs to access ffmpeg functions, and refactoring the mediapipe-rs project. The deliverables should cover at least 80% of all ffmpeg functions and have comprehensive unit tests and documentation. The recommended skills include C
                    this result is generated by flows.network. Triggered by @jaykchen

OSPP: Enabling WasmEdge Compilation with MSVC Toolchain
https://github.com/WasmEdge/WasmEdge/issues/2629
The central problem discussed in the issue is enabling WasmEdge compilation with the MSVC toolchain. The main solutions proposed include fixing compilation errors, modifying the code to avoid designated initializers, rewriting SIMD-related instructions with unrolling, and creating a workflow for MSVC build.
                    this result is generated by flows.network. Triggered by @jaykchen

[Feature] [binding-java] Publish java to maven repository
https://github.com/WasmEdge/WasmEdge/issues/2596
Issue: '[Feature] [binding-java] Publish java to maven repository'
User 'liangyuanpeng' opened this issue to propose the addition of a feature to publish Java for WasmEdge to the Maven repository. The motivation behind this is to make it easier for users to use WasmEdge.
@sarthaksarthak9 requested more details regarding the issue, and @Hrushi20 showed interest in working on it. They suggested the following solutions:

Registering WasmEdge with Sonatype to create a namespace.

Creating PGP keys for signing.

Adding the feature to the pipelines
                 this result is generated by flows.network. Triggered by @jaykchen

LFX Workspace: A stream log processing framework for WasmEdge
https://github.com/WasmEdge/WasmEdge/issues/2552
The central problem discussed in the issue is the development of a stream log processing framework for WasmEdge. The goal is to provide a framework that can collect, transform, and route logs from various services. The main solutions proposed include designing and implementing the components of the framework such as collectors, transformers, dispatchers, and routers. The use of custom events and event routing is also discussed. Additionally, there are suggestions to explore options for custom transformers, add support for log collection from files, and investigate the possibility of creating a WasmEdge plugin for filesystem notifications.
                    this result is generated by flows.network. Triggered by @jaykchen

LFX Workspace: Support Tensorflow and PyTorch in WasmEdge’s Python runtime
https://github.com/WasmEdge/WasmEdge/issues/2545
The central problem discussed in the issue is the need to support Tensorflow and PyTorch in WasmEdge's Python runtime for lightweight deployment of AI applications. The proposed solution includes incorporating WasmEdge's NN extensions into the Python interpreter, creating CPython wrappers for host functions, and creating high-level Python wrapper functions. The aim is to create a demoable solution at the end of each milestone and provide detailed documentation and tutorials.
                    this result is generated by flows.network. Triggered by @jaykchen

Support "Named Models" in WASI NN
https://github.com/WasmEdge/WasmEdge/issues/2504
The central problem discussed in the issue is the lack of a way to deregister registered models in the Named Models feature of WASI NN. The main solution proposed is to implement an extension function to address this limitation. Additionally, there is mention of implementing a superset of the official spec and waiting for the release of wasi-nn before opening a PR for review.
                    this result is generated by flows.network. Triggered by @jaykchen

@flows


GrabCut output polygon

We need to put some thought into how we differentiate between the path that results in the interior of the polygon and the path that results in the exterior of the polygon (foreground/background). If I start drawing with one of the tools, I can't tell I'm specifying the interior or exterior.
In another implementation of GrabCut, we specify lines as 'water' and 'land'. Perhaps we can change the icons to depict something like that? Or to be more generic, at least an 'in polygon' and 'outside polygon' icon.

closing in favor of #178


Enhancement: High DPI display support for client.

My device has high resolution display with 200% scaling.
This is how client looks normally

If I go to properties>compatibility>change high dpi>override display scaling by Application it looks much better, but server and service logs aren't readable.

Client logs however look great

So this was a very strange issue brought to you by Microsoft Bug Studio, where if I change displays (Remoted into from laptop in another room, not unusual), a forced desktop rescale would cause Forms Designer to rescale my Forms for me, and totally messed up the GUI yesterday. What you see now is a few hours of resetting sizes, paddings, and margins on all of the controls.  Interior padding (Mind you, these values were never modified by my hands) had some 9x13 value, and this would cause the full-size textbox to wrap out of view. Thanks for the catch! I had to change my own scaling settings to see this... I will push a fix build to this soon!

New build uploaded to fix the bug. I will consider looking into responding to scaling changes, though I have a feeling that much of that is a flaw with Forms integration in to .NET Core, or just the fact that Forms is a bit outdated. I'm sure I will be bored enough at work to do this research someday soon, lol.

Found a method today that .NET Core uses to set WinForms DPI modes. I have enabled what looks to be the best option for this setting, the next build may look different for you! I am not high-res and unfortunately do not have the grounds for testing.

I'd be happy to test although I'm not sure if there's anything to improve in this regard. The last few versions already look perfect. The only thing is I had to turn on application scaling by going to compatibility settings which should be on by default.

I wanna pop a post here at @demifiend9 , Just to see if the latest build doesn't make or break something related to this?

It looks great by default! No problems related to this.


Not all devices are listed

Only my Yeelight Bulb is listed, but on the Mi Home app, I have a Mijia 360 2K camera as well.

I guess that your devices are registred across 2 different accounts or 2 different servers,
try to use your phone number / email as username
and anyway you can try my cli tool which uses this micloud library but search across different locales.


Feature/tt2 202 split e2e and int tests

Splits the e2e and integration tests into 2 different suites

Assuming you've run everything and it all still works, I'm happy!

I've run the 2 suites and I've generated an Allure report for each.
Where it might go wrong is the run-tests.sh script as we promote through the pipeline but there's not a nice way to test that prior to merge (I'm relatively confident the bash is fine).


Improving the navigation bar

1)Will add space between the contents
2)change the font

Can u assign me this issue


fix(KFLUXBUGS-1340):  add branch param from fork to snapshot

fixing when the source of git repo of fork PR should take the branch so which was lately exposed in PaC v0.27.1
KFLUXBUGS-1340

[ ] Commit messages are descriptive enough (hints)
[ ] Code coverage from testing does not decrease and new code is covered (check the PR coverage on codecov)
[ ] Controllers diagrams are updated when PR changes controllers code  (if applicable)

Codecov Report
Attention: Patch coverage is 0% with 1 line in your changes missing coverage. Please review.

Please upload report for BASE (main@7e11559). Learn more about missing BASE report.

Files with missing lines
Patch %
Lines

internal/controller/snapshot/snapshot_adapter.go
0.00%
1 Missing :warning:

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #893   +/-   ##
=======================================
  Coverage        ?   69.01%
=======================================
  Files           ?       43
  Lines           ?     4577
  Branches        ?        0
=======================================
  Hits            ?     3159
  Misses          ?     1079
  Partials        ?      339

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

failed on rosa provision and dashboard upload
/retest

/retst

/retest

/retest

deployment issue,
/retest

/retest


Generate math functions for various number types

There is a lot of repetition in the math part where we copy the same function over and over and just change the type signature
It would be cool if we could auto generate this

Made a generator thingy


Confusion about some hyper-parameters

A nice work! but I am confused about some hyper-parameters.

First is model_dim, it is set to 64 in resnet_320x1024.txt and resnet_192x640.txt, but it's 32 in args_res50_kitti_192x640_train.txt, 56 in args_cityscapes_train.txt.
Then is min_depth and max_depth. In most config files, they are set to 0.001 and 80. But max_depth is set to 10 in args_cityscapes_train.txt and max_depth is set to 0.01 in resnet_320x1024.txt.
And also, query_nums, dim_out and so on have different settings
I wonder how these hyper-parameters can influence the final performance. Now I want to train on Cityscapes from scratch, should I follow the same setting in args_cityscapes_train.txt (max_depth=10 is somewhat strange to me, why not 80?)

max_depth does not influence the scores (Because self-supervised training doesn't  require absolute depth scale, and in evaluation,  median-scaling is used for align depth_gts and depth predictions), but min_depth does.
You can change model_dim, query_nums, dim_out if you like, but these hyper-parameters can influence the scores, model parameters, model speed, etc.

Thank you for your reply. Actually I think the influence of min_depth is also slight if it is small enough, i.e., setting it to 0.1, 0.01 or 0.001 may have a slight gap.


Grooming seems to delete jobs to soon

We need to investigate this but I think the groom job deleted some scripts I had run a couple hours ago.

Fix issue with grooming.


Blur settings

The blur setting seems to only be true or false not an integer as specified - is this a mistake or am I doing something wrong.

Yes and no. If you're using GD, the value can only be true or false (or, 0 and whatever else). In Imagick you can use an integer where a higher value means more blur.
I'll make sure to get this into the docs.


fix issue with group by limit pushdown for extractionFn, expressions, joins, etc

Description
This PR fixes a bug with group by limit pushdown which causes incorrect query results when grouping on string columns ... TBD.
This is done by adding two new flags to ColumnCapabilities, areDictionaryValuesSorted and areDictionaryValuesUnique, which both must be true for pushdown to occur, and checking for their presence when deciding whether or not pushdown can occur in HashAggregateIterator.
Capabilities has been removed since the dimensionValuesSorted it provided is now more granularly provided by ColumnCapabilities.
A new enum has been introduced to provide a tri-state boolean for ColumnCapabilities:
  enum Capable
  {
    FALSE,
    TRUE,
    UNKNOWN;
    ...
}

in favor of adding them as booleans. As a follow-up, I intend to replace the other booleans on ColumnCapabilities with Capable so that we can remove ColumnCapabilities.isComplete and instead check for individual capabilities.
simple example that illustrates the bug
given rows
dim1, dim2
----------
'a', 'aa'
'a', 'ab'
'a', 'ba

and the following query
SELECT
  dim1, substring(dim2, 1, 1), count(*)
FROM
  exampleRows
GROUP BY 1,2
LIMIT 2

prior to the changes in this PR the results would be
[['a', 'a', 2]]

rather than the expected:
[['a', 'a', 2],['a', 'b', 1]]

This PR has:

[ ] been self-reviewed.
[ ] added Javadocs for most classes and all non-trivial methods. Linked related entities via Javadoc links.
[x] added comments explaining the "why" and the intent of the code wherever would not be obvious for an unfamiliar reader.
[x] added unit tests or modified existing tests to cover new code paths.
[ ] added integration tests.
[x] been tested in a test Druid cluster.

I restarted LGTM.


latest openfl

is this working on latest openfl?

havent used openfl for a few months now :(
Cheers,
Jesse   -    "jjwallace"
Jesse Wallace  :  Indie Game & App Developer / Engineer
cell:<PHONE_NUMBER> | skype: jjaywallace | gchat:
<EMAIL_ADDRESS>http://gmail.com | aim: jjaywallaceim
PORTFOLIO WEBSITE http://www.jjwallace.info/ | PLEASE CONNECT VIA LINKEDIN
http://www.linkedin.com/in/jjwallace/* | TWITTER
http://twitter.com/jjaywallace | YOUTUBE
http://www.youtube.com/user/jjaywallace*
On Fri, Mar 6, 2015 at 2:22 AM, Hermanto<EMAIL_ADDRESS>wrote:

is this working on latest openfl?
—
Reply to this email directly or view it on GitHub
https://github.com/hyperfiction/HypFacebook/issues/14.


[WIP] refactor test_annotations

this is the counter-part of #5418

I'll close this as there is no commit and work has been done on this already


Is there a global settings for PdfConversionSettings.PdfToolPath?

Or anything else in the  PdfConversionSettings  for that matter?  Like adding a logo on all generated document.
Since PdfConvert is global static, it seems making sense to have global settings as well?
Thanks.

I guess I don't follow on what you mean by global. I assume you mean the shape of the API isn't intuitive for you? There are various Custom**Args properties on PdfConversionSettings that you can set for the more advanced use cases.
If you want to modify anything, please feel free to submit a PR and I'll review it (faster than I responded to this issue, sorry...).
I had started a refactor (builder pattern, sensible defaults, etc) of the whole project, but with moving and a new job and everything just haven't been able to allocate time for it. Also, haven't found the flash drive it was on (probably in an unpacked box, heh).
Again, sorry for the delay.

Thanks for the update.  It's really trivial stuff, for example,

I have wkhtmltopdf.exe in a custom location, but too lazy to set it
Maybe there's a custom section I want to add to all document generated

Wonder if it can be set once in startup and forget about.
PdfConversionSettings.PdfToolPath = "wherever";

I have a workaround like this.
   public class MyPdfConversionSettings : PdfConversionSettings
    {
        public MyPdfConversionSettings()
        {
            base.PdfToolPath = Path.Combine(
                Path.GetPathRoot(Environment.CurrentDirectory), "wkhtmltopdf", "wkhtmltopdf.exe");
        }
    }

Not really a big deal, whatever you planned.  Appreciate all the great work!

Well, shoot. I can't seem to find the work I've done on converting this library to the "builder" pattern. I would continue using what you have, if it's still a need for your project. If you still would like to submit a PR for anything, I'll get to it quicker now. Promise. Thanks for your patience.


Adding cudaDeviceSynchronize in instlibs/utils/sassi_lazyallocator.hpp

Added cudaDeviceSynchronize in the main CUPTI callback that handles launches. Without cudaDeviceSynchronize, I'm not able to access managed variables that are used by the GPU kernel from the user callback routine.

My instrumentation libraries still work with this fix, so I'm merging the change. Thanks Siva!


Adding test report files to the payment-request directory

This PR adds the report files of test runs in Firefox Quantum 62.0 and Chrome 69.0
This is in accordance with #54

@marcoscaceres Can you have a look at these reports ?

(Sorry about all the typos, doing this on my phone)


Best integration of oft / ttf math fonts in Manim

By changing the preamble in tex_template.tex, one may use different fonts for the animations, both for text and math formulas. However, some of the most interesting math fonts are only available in otf / ttf, which is usually related with a xelatex engine.
Is it possible right now to use these fonts in Manim? Which is the easiest integration?
Thanks in advance

https://github.com/3b1b/manim/pull/680

Does it support math formulas?

No, if you want to use the Math format you have to add the corresponding package to the tex_template.tex file, if you want to create multiple files tex_template I recommend you see this PR, for example, if you want to add this font then you must add this to your tex_template file:
\usepackage[condensed,math]{anttor}
\usepackage[T1]{fontenc}

And use it like:
TextMobject(r"\normalfont Normal font \scshape SC shape")

This only works if you have the font installed, if not, you must install it, either with the help of TexMaker or manually. If you do it manually, you must download the source from its official repository in the CTAN (this is the repository of the example font) and install it. If you don't know how to do that you should investigate it on your own.

@zavden This method only works with the tfm font (the old TeX font), if you want to include modern font (ttf and oft font), you need XeTeX or LuaTeX.

@kexplorning the trick works great. I added
\setmainfont{Lato-Light.otf}

\newfontfamily\texttt[%
  Scale=MatchLowercase
]{SourceCodePro-ExtraLight.otf}

\newfontfamily\fira[%
  Scale=MatchLowercase
]{FiraSans-ExtraLight.otf}

\RequirePackage{unicode-math}
\setmathfont[%
       Scale=1.2%use instead of 12pt
]{GFSNeohellenicMath.otf}

to ctex_template.tex, then set TEX_USE_CTEX=True and installed the required libraries.
You may see the result here: math font is GFSNeohellenicMath
Additionally, here's the code of the video: https://github.com/TungstenHub/tngt-manim
Thanks @zavden too for your very useful comments


e2e: fetch and version-sort github releases to get latest release.

Our method of querying github.com/$repo/releases/latest to determine the latest release of containerd, CRI-O or kubernetes is unasafe. The semantics of 'latest' is up to the package maintainer. Since errors happen, we can end up picking and trying to use a too old version. So instead, list releases and version-sort them to find the latest one.
Ideally we would use the official github API to list all tagged releases not marked as a prerelease, and pick the latest one by tag. However, without authenticating that API is severly rate limited and fails often from behind busy proxies. So instead, fetch pages of releases, parse them for release URLs, sort them by version and pick the

BTW: There are probably plenty of more low hanging fruits to fix/improve on this front. For instance, I just noticed that the scripts determine the latest runtime and K8s release (thus accessing and fetching plenty of data from github) for every single test we run. Since these cannot really change once the test VM has been provisioned it would be better to determine the versions once then store them under the test VM directory in case they are needed for further, version-specific test scripting logic.

BTW: There are probably plenty of more low hanging fruits to fix/improve on this front. For instance, I just noticed that the scripts determine the latest runtime and K8s release (thus accessing and fetching plenty of data from github) for every single test we run. Since these cannot really change once the test VM has been provisioned it would be better to determine the versions once then store them under the test VM directory in case they are needed for further, version-specific test scripting logic.

This is now addressed in #324, which is stacked on top of this PR.


Replace Spring HttpMethod with enum.

Without this change and when Spring and Hibernate are upgraded Jackson is not able to unmarshall JSON into HttpMethod objects and the following error occurs:
com.fasterxml.jackson.databind.exc.MismatchedInputException: Cannot construct instance of org.springframework.http.HttpMethod (although at least one Creator exists): cannot deserialize from Object value (no delegate- or property-based Creator)
HttpMethod was previously an enum class (Spring v 4.14) which was serializable by Jackson but following the upgrade it is now neither an enum class nor serializable.
This PR adds in a serializable enum HTTP method class and uses it to construct a temporary MarshallablePreemptiveCacheMetadata from which the PreemptiveCacheMetadata object can be created.

This has been superseded by:
https://github.com/ministryofjustice/hmpps-approved-premises-api/pull/2089
https://github.com/ministryofjustice/hmpps-approved-premises-api/pull/2085


Authelia - Basic Auth does not work with Backbox-Exporter

Dear clems4ever,
{
  "kind": "Ingress",
  "apiVersion": "extensions/v1beta1",
  "metadata": {
    "name": "kibana",
    "namespace": "logging",
    "annotations": {
      "ingress.kubernetes.io/auth-signin": "https://login-dev.example.com",
      "ingress.kubernetes.io/auth-url": "https://login-dev.example.com/api/verify",
      "ingress.kubernetes.io/force-ssl-redirect": "false",
      "ingress.kubernetes.io/proxy-buffer-size": "256k",
      "ingress.kubernetes.io/ssl-redirect": "false",
      "kubernetes.io/ingress.class": "nginx"
    }
  },
  "spec": {
    "rules": [
      {
        "host": "kibana-dev-ops.example.com",
        "http": {
          "paths": [
            {
              "path": "/",
              "backend": {
                "serviceName": "kibana",
                "servicePort": 5601
              }
            }
          ]
        }
      }
    ]
  }
}

my ingress is configured as seen here.
###############################################################
#                   Authelia configuration                    #
###############################################################

# The port to listen on
port: 8080

# Log level
#
# Level of verbosity for logs
logs_level: debug

# Default redirection URL
#
# If user tries to authenticate without any referer, Authelia
# does not know where to redirect the user to at the end of the
# authentication process.
# This parameter allows you to specify the default redirection
# URL Authelia will use in such a case.
#
# Note: this parameter is optional. If not provided, user won't
# be redirected upon successful authentication.
#default_redirection_url: https://home.example.com:8080/

# TOTP Issuer Name
#
# This will be the issuer name displayed in Google Authenticator
# See: https://github.com/google/google-authenticator/wiki/Key-Uri-Format for more info on issuer names
totp:
  issuer: login-dev.example.com

# The authentication backend to use for verifying user passwords
# and retrieve information such as email address and groups
# users belong to.
#
# There are two supported backends: `ldap` and `file`.
authentication_backend:
  ldap:
    # The url of the ldap server
    url: ldaps://LDAPURL:636

    # The base dn for every entries
    base_dn: BASEDN

    # An additional dn to define the scope to all users
    additional_users_dn: ou=People

    # The users filter used to find the user DN
    # {0} is a matcher replaced by username.
    # 'cn={0}' by default.
    users_filter: uid={0}

    # An additional dn to define the scope of groups
    additional_groups_dn: ou=Groups

    # The groups filter used for retrieving groups of a given user.                                                                                [136/9221]
    # {0} is a matcher replaced by username.
    # {dn} is a matcher replaced by user DN.
    # 'member={dn}' by default.
    groups_filter: (&(memberUid={0})(objectclass=posixGroup))

    # The attribute holding the name of the group
    group_name_attribute: cn

    # The attribute holding the mail address of the user
    mail_attribute: mail

    # The username and password of the admin user.
    user: LDAPUSER
    password: LDAPPASSWORD

# Access Control
#
# Access control is a list of rules defining the authorizations applied for one
# resource to users or group of users.
#
# If 'access_control' is not defined, ACL rules are disabled and the `bypass`
# rule is applied, i.e., access is allowed to anyone. Otherwise restrictions follow
# the rules defined.
#
# Note: One can use the wildcard * to match any subdomain.
# It must stand at the beginning of the pattern. (example: *.mydomain.com)
#
# Note: You must put patterns containing wildcards between simple quotes for the YAML
# to be syntaxically correct.
#
# Definition: A `rule` is an object with the following keys: `domain`, `subject`,
# `policy` and `resources`.
#
# - `domain` defines which domain or set of domains the rule applies to.
#
# - `subject` defines the subject to apply authorizations to. This parameter is
#    optional and matching any user if not provided. If provided, the parameter
#    represents either a user or a group. It should be of the form 'user:<username>'
#    or 'group:<groupname>'.
#
# - `policy` is the policy to apply to resources. It must be either `bypass`,
#   `one_factor`, `two_factor` or `deny`.
#
# - `resources` is a list of regular expressions that matches a set of resources to
#    apply the policy to. This parameter is optional and matches any resource if not
#    provided.
#
# Note: the order of the rules is important. The first policy matching
# (domain, resource, subject) applies.
access_control:
  # Default policy can either be `bypass`, `one_factor`, `two_factor` or `deny`.
  # It is the policy applied to any resource if there is no policy to be applied
  # to the user.
  default_policy: deny

  rules:                                                                                [68/9221]
    # Rules applied to everyone
    - domain: '*.example.com'
      policy: one_factor
#    - domain: single_factor.example.com
#      policy: one_factor

    # Rules applied to 'admin' group
#    - domain: 'mx2.mail.example.com'
#      subject: 'group:admin'
#      policy: deny
#    - domain: '*.example.com'
#      subject: 'group:admin'
#      policy: two_factor

    # Rules applied to 'dev' group
#    - domain: dev.example.com
#      resources:
#        - '^/groups/dev/.*$'
#      subject: 'group:dev'
#      policy: two_factor

    # Rules applied to user 'john'
#    - domain: dev.example.com
#      resources:
#        - '^/users/john/.*$'
#      subject: 'user:john'
#      policy: two_factor

    # Rules applied to user 'harry'
#    - domain: dev.example.com
#      resources:
#        - '^/users/harry/.*$'
#      subject: 'user:harry'
#      policy: two_factor

    # Rules applied to user 'bob'
#    - domain: '*.mail.example.com'
#      subject: 'user:bob'
#      policy: two_factor
#    - domain: 'dev.example.com'
#      resources:
#        - '^/users/bob/.*$'
#      subject: 'user:bob'
#      policy: two_factor

# Configuration of session cookies
#
# The session cookies identify the user once logged in.
session:
  # The name of the session cookie. (default: authelia_session).
  name: authelia_session

  # The secret to encrypt the session cookie.
  secret: SESSIONSECRET

  # The time in ms before the cookie expires and session is reset.
  expiration: 3600000 # 1 hour

  # The inactivity time in ms before the session is reset.
  inactivity: 3600000 # 1 hour

  # The domain to protect.
  # Note: the authenticator must also be in that domain. If empty, the cookie
  # is restricted to the subdomain of the issuer.
  domain: example.com

  # The redis connection details
  redis:
    host: authelia-redis-master
    port: 6379
    password: REDISPASSWORD

# Configuration of the authentication regulation mechanism.
#
# This mechanism prevents attackers from brute forcing the first factor.
# It bans the user if too many attempts are done in a short period of
# time.
regulation:
  # The number of failed login attempts before user is banned.
  # Set it to 0 to disable regulation.
  max_retries: 3

  # The time range during which the user can attempt login before being banned.
  # The user is banned if the authenticaction failed `max_retries` times in a `find_time` seconds window.
  find_time: 120

  # The length of time before a banned user can login again.
  ban_time: 300

# Configuration of the storage backend used to store data and secrets.
#
# You must use only an available configuration: local, mongo
storage:
  # The directory where the DB files will be saved
  ## local:
  ##   path: /var/lib/authelia/store

  # Settings to connect to mongo server
  mongo:
    url: mongodb://mongo-0.mongo:27017,mongo-1.mongo:27017,mongo-2.mongo:27017/?replicaSet=rs0
    database: authelia
    auth:
      username: MONGOUSER
      password: MONGOPASSWORD

# Configuration of the notification system.
#
# Notifications are sent to users when they require a password reset, a u2f
# registration or a TOTP registration.
# Use only an available configuration: filesystem, gmail
notifier:
  # For testing purpose, notifications can be sent in a file
  ## filesystem:
  ##   filename: /tmp/authelia/notification.txt

  # Use your email account to send the notifications. You can use an app password.
  # List of valid services can be found here: https://nodemailer.com/smtp/well-known/
  ## email:
  ##   username<EMAIL_ADDRESS>  ##   password: yourpassword
  ##   sender<EMAIL_ADDRESS>  ##   service: gmail

  # Use a SMTP server for sending notifications
  smtp:
    #username: test
    #password: password
    secure: false
    host: 'SMTPHOST'
    port: 25
    sender: EMAIL

The login is working in the browser (great job!). But not the probing against Authelia with BasicAuth.
Do You require a specific nginx version?
What could be the reason?

Hello @RafalMaleska , I don't see anything weird in your conf. Can you extract some logs?

Hi @clems4ever , just want to provide more information.
As @RafalMaleska said, the login (with LDAP credentials) is working via browser perfectly.
For some cases we need basic auth. For example with curl (or blackbox exporter is also working with basic auth):
curl -u ldapuser https://some-app.example.com
This results in:

<title>302 Found</title>

302 Found

nginx/1.13.8

A curl with -L (follow redirects)
curl -L -u ldapuser https://some-app.example.com
results in:
<!DOCTYPE html><title>Authelia - 2FA</title><meta name="viewport" content="width=device-width, initial-scale=1.0"><meta name="robots" content="noindex, nofollow, nosnippet, noarchive"><meta http-equiv="Content-Security-Policy" content="default-src 'self'; img-src 'self' data:;"><link rel="icon" href="/img/icon.png" type="image/png" sizes="32x32"><link rel="stylesheet" type="text/css" href="/css/authelia.css">

Sign in

Enter your credentials to sign in
<form class="form-signin">
<input class="form-control" type="text" id="username" placeholder="Username" required autofocus><input class="form-control" type="password" id="password" placeholder="Password" required>
<button class="btn btn-lg btn-primary btn-block" id="signin" type="submit">Sign in</button>
<input type="checkbox" id="keep_me_logged_in" name="keep_me_logged_in" value="true">Keep me logged in

Forgot password?
</form>

Powered by Authelia

%

These curl calls produce the following authelia logs:
debug: date='Tue Mar 05 2019 12:12:27 GMT+0000 (UTC)' method='GET', path='/api/verify' requestId='90342486-eddb-4520-b48d-5b9fbb1aa3a6' sessionId='u0h5nwD_fHMF4hYorUqJBDuEVIT_aayt' ip='<IP_ADDRESS>' message='Headers = {"host":"login-dev.example.com","connection":"close","x-real-ip":"<IP_ADDRESS>","x-forwarded-for":"<IP_ADDRESS>","x-forwarded-host":"login-dev.example.com","x-forwarded-port":"443","x-forwarded-proto":"https","x-original-uri":"/api/verify","x-scheme":"https","x-original-forwarded-for":"<IP_ADDRESS>, <IP_ADDRESS>","accept-encoding":"gzip","user-agent":"Go-http-client/1.1","x-auth-request-redirect":"/","x-original-method":"GET","x-original-url":"http://some-app.example.com/","x-sent-from":"nginx-ingress-controller"}'
debug: date='Tue Mar 05 2019 12:12:27 GMT+0000 (UTC)' method='GET', path='/api/verify' requestId='90342486-eddb-4520-b48d-5b9fbb1aa3a6' sessionId='u0h5nwD_fHMF4hYorUqJBDuEVIT_aayt' ip='<IP_ADDRESS>' message='Authentication session u0h5nwD_fHMF4hYorUqJBDuEVIT_aayt was undefined. Resetting.'
error: date='Tue Mar 05 2019 12:12:27 GMT+0000 (UTC)' method='GET', path='/api/verify' requestId='90342486-eddb-4520-b48d-5b9fbb1aa3a6' sessionId='u0h5nwD_fHMF4hYorUqJBDuEVIT_aayt' ip='<IP_ADDRESS>' message='Reply with error 401: userid is missing'
debug: date='Tue Mar 05 2019 12:12:27 GMT+0000 (UTC)' method='GET', path='/api/verify' requestId='90342486-eddb-4520-b48d-5b9fbb1aa3a6' sessionId='u0h5nwD_fHMF4hYorUqJBDuEVIT_aayt' ip='<IP_ADDRESS>' message='AccessDeniedError: userid is missing
    at BluebirdPromise.resolve.then (/usr/src/server/src/lib/routes/verify/get_session_cookie.js:31:43)
    at tryCatcher (/usr/src/node_modules/bluebird/js/release/util.js:16:23)
    at Promise._settlePromiseFromHandler (/usr/src/node_modules/bluebird/js/release/promise.js:512:31)
    at Promise._settlePromise (/usr/src/node_modules/bluebird/js/release/promise.js:569:18)
    at Promise._settlePromiseCtx (/usr/src/node_modules/bluebird/js/release/promise.js:606:10)
    at _drainQueueStep (/usr/src/node_modules/bluebird/js/release/async.js:142:12)
    at _drainQueue (/usr/src/node_modules/bluebird/js/release/async.js:131:9)
    at Async._drainQueues (/usr/src/node_modules/bluebird/js/release/async.js:147:5)
    at Immediate.Async.drainQueues (/usr/src/node_modules/bluebird/js/release/async.js:17:14)
    at runCallback (timers.js:785:20)
    at tryOnImmediate (timers.js:747:5)
    at processImmediate [as _immediateCallback] (timers.js:718:5)'

Do you have any ideas?

Hello @RafalMaleska and @dbluxo , I found what's causing your issue. It's because the authorization header to log in basic auth is not Authorization but Proxy-Authorization instead. You need something like
curl -H "Proxy-Authorization: Basic XXXXXXXXXX" https://some-app.example.com.
https://github.com/clems4ever/authelia/blob/f8a12b8482c3a013697e0ed2b616b7fd277146db/server/src/lib/routes/verify/get.ts#L24
https://developer.mozilla.org/en-US/docs/Web/HTTP/Authentication#Proxy_authentication
What you can do is rewrite the header in nginx to transform Authorization to Proxy-Authorization before sending the query to Authelia.
I'll add more logs in Authelia to make this problem clearer and I'll close the issue afterwards.

Hello @RafalMaleska , @dbluxo , did it solve your issue?

Hi @clems4ever,
we have tried it as you suggested, but without success:
curl -L -H "Proxy-Authorization: Basic XXXXXXXXXXX"  https://some-app.example.com
This results in:
<!DOCTYPE html><title>Authelia - 2FA</title><meta name="viewport" content="width=device-width, initial-scale=1.0"><meta name="robots" content="noindex, nofollow, nosnippet, noarchive"><meta http-equiv="Content-Security-Policy" content="default-src 'self'; img-src 'self' data:;"><link rel="icon" href="/img/icon.png" type="image/png" sizes="32x32"><link rel="stylesheet" type="text/css" href="/css/authelia.css">

Sign in

Enter your credentials to sign in
<form class="form-signin">
<input class="form-control" type="text" id="username" placeholder="Username" required autofocus><input class="form-control" type="password" id="password" placeholder="Password" required>
<button class="btn btn-lg btn-primary btn-block" id="signin" type="submit">Sign in</button>
<input type="checkbox" id="keep_me_logged_in" name="keep_me_logged_in" value="true">Keep me logged in

Forgot password?
</form>

Powered by Authelia

The curl call produce the following authelia logs:
debug: date='Tue Mar 12 2019 09:16:21 GMT+0000 (UTC)' method='GET', path='/api/verify' requestId='292f8a43-60fc-40c8-9769-15b987f9eb61' sessionId='Q1__Rs-spKnLFe46xxdkJkuUxs-58FOM' ip='<IP_ADDRESS>' message='Headers = {"host":"login-dev.example.com","connection":"close","x-real-ip":"<IP_ADDRESS>","x-forwarded-for":"<IP_ADDRESS>","x-forwarded-host":"login-dev.example.com","x-forwarded-port":"443","x-forwarded-proto":"https","x-original-uri":"/api/verify","x-scheme":"https","x-original-forwarded-for":"<IP_ADDRESS>, <IP_ADDRESS>","x-amzn-trace-id":"Self=1-5c8778e5-73821c0e1016c14e29430f1a;Root=1-5c8778e5-8b4336d01b1b9a584d6dee68","x-original-url":"http://some-app.example.com/","x-original-method":"GET","x-sent-from":"nginx-ingress-controller","x-auth-request-redirect":"/","user-agent":"curl/7.61.1","accept":"*/*"}'
debug: date='Tue Mar 12 2019 09:16:21 GMT+0000 (UTC)' method='GET', path='/api/verify' requestId='292f8a43-60fc-40c8-9769-15b987f9eb61' sessionId='Q1__Rs-spKnLFe46xxdkJkuUxs-58FOM' ip='<IP_ADDRESS>' message='Authentication session Q1__Rs-spKnLFe46xxdkJkuUxs-58FOM was undefined. Resetting.'
error: date='Tue Mar 12 2019 09:16:21 GMT+0000 (UTC)' method='GET', path='/api/verify' requestId='292f8a43-60fc-40c8-9769-15b987f9eb61' sessionId='Q1__Rs-spKnLFe46xxdkJkuUxs-58FOM' ip='<IP_ADDRESS>' message='Reply with error 401: userid is missing'
debug: date='Tue Mar 12 2019 09:16:21 GMT+0000 (UTC)' method='GET', path='/api/verify' requestId='292f8a43-60fc-40c8-9769-15b987f9eb61' sessionId='Q1__Rs-spKnLFe46xxdkJkuUxs-58FOM' ip='<IP_ADDRESS>' message='AccessDeniedError: userid is missing
    at BluebirdPromise.resolve.then (/usr/src/server/src/lib/routes/verify/get_session_cookie.js:31:43)
    at tryCatcher (/usr/src/node_modules/bluebird/js/release/util.js:16:23)
    at Promise._settlePromiseFromHandler (/usr/src/node_modules/bluebird/js/release/promise.js:512:31)
    at Promise._settlePromise (/usr/src/node_modules/bluebird/js/release/promise.js:569:18)
    at Promise._settlePromiseCtx (/usr/src/node_modules/bluebird/js/release/promise.js:606:10)
    at _drainQueueStep (/usr/src/node_modules/bluebird/js/release/async.js:142:12)
    at _drainQueue (/usr/src/node_modules/bluebird/js/release/async.js:131:9)
    at Async._drainQueues (/usr/src/node_modules/bluebird/js/release/async.js:147:5)
    at Immediate.Async.drainQueues (/usr/src/node_modules/bluebird/js/release/async.js:17:14)
    at runCallback (timers.js:785:20)
    at tryOnImmediate (timers.js:747:5)
    at processImmediate [as _immediateCallback] (timers.js:718:5)'
debug: date='Tue Mar 12 2019 09:16:21 GMT+0000 (UTC)' method='GET', path='/' requestId='07d2bb25-6e1f-416f-a86f-6a61a8219a8c' sessionId='V9E86iWIPeNSbX-igDnXT84dDDQyUMvd' ip='<IP_ADDRESS>' message='Headers = {"host":"login-k8s03-dev-ops.reisendeninfo.aws.db.de","connection":"close","x-real-ip":"<IP_ADDRESS>","x-forwarded-for":"<IP_ADDRESS>","x-forwarded-host":"login-dev.example.com","x-forwarded-port":"443","x-forwarded-proto":"https","x-original-uri":"/?rd=https://some-app.example.com/","x-scheme":"https","x-original-forwarded-for":"<IP_ADDRESS>","x-amzn-trace-id":"Root=1-5c8778e5-ee81ee28b7a6c317373cc391","user-agent":"curl/7.61.1","accept":"*/*"}'
debug: date='Tue Mar 12 2019 09:16:21 GMT+0000 (UTC)' method='GET', path='/' requestId='07d2bb25-6e1f-416f-a86f-6a61a8219a8c' sessionId='V9E86iWIPeNSbX-igDnXT84dDDQyUMvd' ip='<IP_ADDRESS>' message='Authentication session V9E86iWIPeNSbX-igDnXT84dDDQyUMvd was undefined. Resetting.'

We have deployed nginx-ingress-controller and all ingresses as you described in your example for kubernetes:
https://github.com/clems4ever/authelia/tree/master/example/kube
Any further ideas?

Hi @clems4ever,
we figured out that the problem was at the Nginx Ingress Controller in Kubernetes.
There are two settings in the Nginx Ingress Controller we have to configure in the official Helm-Chart (https://github.com/helm/charts/tree/master/stable/nginx-ingress).
With Nginx Ingress Controller > 0.21.0 we have to set:
    controller:
      config:
        proxy-real-ip-cidr: "<IP_ADDRESS>/0"
        use-forwarded-headers: "true"
      headers:
        Proxy-Authorization: $http_authorization

With Nginx Ingress Controller <= 0.21.0 we only have to set:
    controller:
      headers:
        Proxy-Authorization: $http_authorization

Now basic-auth with Nginx Ingress Controller in Kubernetes is working as expected.
Thank you for the great work.

Wow, interesting! I will certainly include this in a doc somewhere.
Thanks for giving back your investigation results!


[to#127]fix ossfile upload_chunk location bug

Hello, @idling11
Thanks for your contribution, but because the tests relied on some Github secrets, could you please push the branch directly to repo git@github.com:fsspec/ossfs.git instead of the forked one. The Github secrets can only be used from internal branches.

@karajan1001 Ok ,thx for your trust


Movement rubberbanding

Player characters tend to rubber-band after movement controls are released. They snap back to a previous position after a button is released

Fixed in PR #36


feat: migrate to GitHub Actions

What
feat: migrate to GitHub Actions

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


add VS Code and Rider user specific files

Current advice from JetBrains is not to ignore the whole .idea folder. See https://intellij-support.jetbrains.com/hc/en-us/articles/206544839-How-to-manage-projects-under-Version-Control-Systems
You can combine with the JetBrains.gitignore locally foe a full list of you would like.


[wip] update master

this is a test.

Please sign your commits following these rules:
https://github.com/moby/moby/blob/master/CONTRIBUTING.md#sign-your-work
The easiest way to do this is to amend the last commit:
$ git clone -b "update_master" git@github.com:vieux/docker-ce.git somewhere
$ cd somewhere
$ git rebase -i HEAD~842354320416
editor opens
change each 'pick' to 'edit'
save the file and quit
$ git commit --amend -s --no-edit
$ git rebase --continue # and repeat the amend for each commit
$ git push -f

Amending updates the existing PR. You DO NOT need to open a new one.

master is already updated. closing.


Wire gates for applying force, torque, offset force only work in single player

Hello,
I have a contraption that uses the apply force gate, apply torque gate and apply offset force gate. This works in single player, but not on other servers that have wiremod. 4 servers with latest wiremod had this problem. For further testing, I tried sending large vector values to entities through all these gates on every server. The debugger would show the correct vector in the gate applying a specific force, but nothing would happen to the entity.
Other gates seem to work fine.
A similar issue seems to have popped up last November, which is by now closed: https://github.com/wiremod/wire/issues/745

Those servers use Github version if wiremod? Because the one from the workshop isn't updated often.. The last update was before the fix was applied.

I've been trying to find out who managed the workshop auto updater so that they can fix it, but people aren't replying

Faron, AKA Rowan, has access to the workshop account. I think he made an auto uploader but its never worked, I always ask him to manually upload it.

@Nebual, :O ! I was always under the impression that it was working (but I never actually really checked)
@FaronFox what's the situation?

@arduinium
I didn't ask any of the owners whether they used the github version or workshop one. I have the github version. If the workshop one has this problem then the owners likely have that version.

The Apply Force, Apply Offset Force, Apply Angular Force and Apply Torque gates work fine for me - in a dedicated server, as non-admin, with no prop protection mods installed.


UWP: impossible to start updates in characteristic

Steps to reproduce

Open BLE solution in Visual Studio, set Samples->BLE.Client.UWP (Universal Windows) as startup project and run
Connect to device and open characteristic supporting Update
Click button Start updates

Expected behavior
Text "Start updates" below
Actual behavior
Message box "[StartUpdatesNativeAsync] failed with status: ProtocolError and protocol error Write Not Permitted"
Crashlog
SystemException "[StartUpdatesNativeAsync] failed with status: ProtocolError and protocol error Write Not Permitted"
Stack:
Plugin.BLE.Extensions.GattResultExtensions.ThrowIfError(GattCommunicationStatus status, String tag, Nullable`1 protocolError)
Plugin.BLE.UWP.Characteristic.d__17.MoveNext()
Configuration
Version of the Plugin: 2.2.0-pre5
Platform: Windows 11 Pro build 22000.856
Device: ESP32

Hi @andrey-val-rodin,
I'm the friendly issue checker.
Thanks for using the issue template :star2:
I appreciate it very much. I'm sure, the maintainers of this repository will answer, soon.

Looks like Windows 11 issue: https://docs.microsoft.com/en-us/answers/questions/962564/wrlc-ble-writeclientcharacteristicconfigurationdes.html

So Windows 10 works fine?

I don't know

I solved issue. The problem was that Windows requires writable Client Characteristic Configuration Descriptor 2902 ("00002902-0000-1000-8000-00805f9b34fb") in characteristic in order to activate updatings: https://stackoverflow.com/a/69126661/8340167. Whereas Android and iOS won't crash if the peripheral doesn't meet the requirements, Windows currently throws exception.
Since I use programmable Bluetooth device (ESP32), I can meet these technical requirements.
But I also faced another challenge: if you add your Bluetooth device in Settings, Windows uses stored device configuration and ignores changes in the device. And for a long time I couldn't figure out why my changes in device didn't work.
Maybe it would be nice to add these findings to Readme.


add method for stop pinging like when setTimes(100000) and need to stop pinging

@medozeus please use the .cancel() method


API - getTransactionDetail

TransactionDetail is returning “No Matching Model”
Though the payload is valid.
As raised by @anzbankau:
https://github.com/ConsumerDataStandardsAustralia/engineering/issues/52#issuecomment-539832429

@anzbankau: is it possible to get the getTransactionDetail payload from you?
That'll help us investigate the issue. Thank you.

@fyang1024
Below is a sample of the payload we are testing with:
{     "data": {         "accountId": "1BSv4uXrYDqvGOMbAG92-adc_5zAvKpWB9q1W_yj-cA",         "transactionId": "ERic5DDiW65VcB_rB2H7cplvlplbdoWRShs7dEAp8SA",         "isDetailAvailable": true,         "type": "TRANSFER_INCOMING",         "status": "POSTED",         "description": "FUNDS RETURNED FOR 109904               PAYMENT TO Testland Mutual B/S Ltd Finance ' Admin Dept1",         "postingDateTime": "2015-12-31T00:00:00+11:00",         "valueDateTime": "2015-12-31T00:00:00+11:00",         "executionDateTime": "2018-03-13T15:37:44+11:00",         "amount": "3.60",         "currency": "AUD",         "reference": "3026V1099044",         "extendedData": {             "payer": "OUT CUSTOMER1",             "payee": "OFFUS Testing22",             "extensionUType": "x2p101Payload",             "x2p101Payload": {                 "extendedDescription": "發送😊😊"             },             "service": "X2P1.01"         }     },     "links": {         "self": "/cds-au/v1/banking/accounts/1BSv4uXrYDqvGOMbAG92-adc_5zAvKpWB9q1W_yj-cA/transactions/ERic5DDiW65VcB_rB2H7cplvlplbdoWRShs7dEAp8SA"     },     "meta": {} }

@anzbankau ,
Thank you for the data. I find the data structure is missing a few fields.

The fields with null value are not in your data structure.
The fixed version is below
{ "data": { "accountId": "1BSv4uXrYDqvGOMbAG92-adc_5zAvKpWB9q1W_yj-cA", "transactionId": "ERic5DDiW65VcB_rB2H7cplvlplbdoWRShs7dEAp8SA", "isDetailAvailable": true, "type": "TRANSFER_INCOMING", "status": "POSTED", "description": "FUNDS RETURNED FOR 109904 PAYMENT TO Testland Mutual B/S Ltd Finance ' Admin Dept1", "postingDateTime": "2015-12-31T00:00:00+11:00", "valueDateTime": "2015-12-31T00:00:00+11:00", "executionDateTime": "2018-03-13T15:37:44+11:00", "amount": "3.60", "currency": "AUD", "reference": "3026V1099044", "merchantName":null,"merchantCategoryCode":null,"billerCode":null, "billerName":null, "crn":null, "apcaNumber":null, "extendedData": { "payer": "OUT CUSTOMER1", "payee": "OFFUS Testing22", "extensionUType": "x2p101Payload", "x2p101Payload": { "extendedDescription": "發送😊😊", "endToEndId":null, "purposeCode": null }, "service": "X2P1.01" } }, "links": { "self": "/cds-au/v1/banking/accounts/1BSv4uXrYDqvGOMbAG92-adc_5zAvKpWB9q1W_yj-cA/transactions/ERic5DDiW65VcB_rB2H7cplvlplbdoWRShs7dEAp8SA" }, "meta": {} }```

However, this example does help me find a bug in the code, that is,
Jackson ObjectMapper should be configured with DeserializationFeature.READ_ENUMS_USING_TO_STRING feature so that it can correctly read `X2P1.01` Service enum value. I have put the fix in codegen-attempt branch. It will be available in 1.0.0-RC2 release soon

Hi @fyang1024
Our take on optional fields is they can be present and null or not present at all and therefore treated as null as per the standards:

Optional fields MAY be present but this is not guaranteed. It is also valid for these fields to be present but have a null value. Note that optional fields indicate that data may sometimes not be held by a Data Holder and this is an expected scenario.
And

Empty/Null Fields
An empty field (ie. a field that is not present in a payload) will be considered equivalent with a field that is present with a null value.

keen to get your thoughts?

Hi @anzbankau
Thank you for pointing that out. We've confirmed that.
I've put the fix in codegen-attempt branch. It'll be ready in 1.0.0-RC2 release

Hi @anzbankau,
Can you please try out the latest code / artefacts and let us know if the issue persists?


Feat/styled components

Codecov Report

Merging #7 (941b4f3) into master (02d2a27) will increase coverage by 100.00%.
The diff coverage is 100.00%.

@@              Coverage Diff              @@
##           master        #7        +/-   ##
=============================================
+ Coverage        0   100.00%   +100.00%
=============================================
  Files           0         5         +5
  Lines           0       117       +117
  Branches        0        33        +33
=============================================
+ Hits            0       117       +117

Impacted Files
Coverage Δ

src/notify.js
100.00% <ø> (ø)

src/components/ReactNoti/ReactNoti.js
100.00% <100.00%> (ø)

src/components/Toast/Toast.js
100.00% <100.00%> (ø)

src/utils/constants.js
100.00% <100.00%> (ø)

src/utils/helpers.js
100.00% <0.00%> (ø)

Continue to review full report at Codecov.

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


[RFC] Use CMSIS-NN with TVM

This RFC details integration of CMSIS-NN API into TVM to support code generation for Arm(R) Cortex-M using the following library: https://github.com/ARM-software/CMSIS_5/tree/develop/CMSIS/NN
cc : @areusch @mbaret @tqchen  @mousius @manupa-arm

Minor nit - the title of the RFC should really read - [RFC] Use CMSIS-NN with TVM.
@manupa-arm , @Mousius ..

Would be great to update the RFC naming per https://github.com/apache/tvm-rfcs/pull/17. cc @comaniac @zhiics who might have some insights from BYOC and @echuraev who might draw some parallels from Apple lib integration

Merging as Cody said LGTM in his last review


QUESTION: how to create a list of tables?

Hello there, nice job with this project!
The only thing is the README and examples are somewhat a little confusing.
Can anyone point me out to the needed resources for:

creating a table / list (if it doesn't exist)
each "row" of the previous is a new table
🙏

Sorry, after a few tests I was only able to add rows to an existing table.

@pdonorio  Could you please share steps for creating a new table?  I tried few approaches without success.

Hi @ajames-branch, I still don't have those steps.
The solution for my project at the moment is to use existing tables.

@pdonorio  I was able to create tables. Thanks to https://github.com/jamalex/notion-py/blob/master/notion/smoke_test.py#L75
Hopee you find it helpful as well.


"ctorParameters.map is not a function" error when the ContextMenuModule is imported

As soon as I try to add the ContextMenuModule to imports of my module I get "ctorParameters.map is not a function" error. Has anybody encountered this problem before?

I haven't seen this.  What version of angular are you using?

I have installed 2.0.1. Just I'm going to try to update...

Apparently other libraries have this issue too when people are using < 2.3.1.

It's working after I upgraded the Angular to 2.4.3. Thanks @isaacplmann to pointing me!


Errors (Received SYN_REPLY with unopened or closed Stream...) during high traffic.

Hi,
I made just a slight modification on the example server and client. The client starts number of concurrent function each keep sending requests at given rate, the server replies with one 1KB of random data.
At 10x concurrent functions each making 1000 request /s  there are errors reported:
(spdy) 2016/02/01 22:16:58 error_handling.go:18: Error: Received SYN_REPLY with unopened or closed Stream ID 15065.
(spdy) 2016/02/01 22:16:58 io.go:19: Encountered receive error: runtime error: invalid memory address or nil pointer dereference (runtime.errorString)
Not sure, if it is a bug in the protocol implementation or my client/server share some data between concurrent functions that should not be shared.
Attaching full log and my updated code.
git log -1
commit 431b911c621782fff951b92948f9ce38633188f0
(github, didn't accept .zip file so I rename to txt)
spdy_go_test.zip.txt

Hi,
Sorry to hear about the error. It sounds like it's probably an error of the library, but I don't have a dev machine available at the moment. I'll do what I can to triage this, but it'll probably be a week away. Sorry for the delay.

No problem, thanks for the replay. Let me know if you would need any more logs, network capture etc.

I've had a look at the code but I can't work out where this is going wrong. Very sorry. I'm afraid I don't really have time to maintain this any more. I'd recommend using HTTP/2, such as with bradfitz's package http2, which will be in the standard library from Go1.6.


TypeScript 4.5.5 is over one year old. Could we have an update please?

What type of issue is this?
Question
What SharePoint development model, framework, SDK or API is this about?
💥 SharePoint Framework
Target SharePoint environment
SharePoint Online
What browser(s) / client(s) have you tested

[ ] 💥 Internet Explorer
[ ] 💥 Microsoft Edge
[ ] 💥 Google Chrome
[ ] 💥 FireFox
[ ] 💥 Safari
[ ] mobile (iOS/iPadOS)
[ ] mobile (Android)
[X] not applicable
[ ] other (enter in the "Additional environment details" area below)

Additional environment details

SPFx version1.16.1

Issue description
A lot of modern npm packages can't be used in SPFx anymore because the bundled TypeScript version is too old. Is there a workaround for installing 4.9? When will SPFx support TS 4.9?

@smolattack - we have TypeScript bump in our backlog

@AJIXuMuK  v1.18 still uses 4.5.5. Are you sure de-prioritizing a Typescript version bump is the right call?

I saw that as well. I understand that supporting new features is an important part of updates, but this should not come at the expense of keeping the fundamentals at such old versions. SPFx is the only project I know of that encapsulates the whole build process in this way and it's a very frustrating experience...

The version has been bumped in 1.18

The version has been bumped in 1.18

That's not really an improvement - TypeScript 4.7 was released in May 2022. Currently we have October 2023, so almost 1.5 years later...


Replace laminas-db

Feature Request

Q
A

New Feature
yes

Summary
laminas-db is in security-only maintenance mode and will not be continued, so it should no longer be used. A (simple) alternative should be used, like PDO which is already used in mezzio-authentication.
Reference

https://getlaminas.org/packages-maintenance-status/
https://github.com/laminas/technical-steering-committee/blob/main/meetings/minutes/2022-02-07-TSC-Minutes.md#is-laminas-db-abandoned

@tyrsson and I have forked the project and intend to work on it, plus, I've always loved it.

@tyrsson and I have forked the project and intend to work on it…

You can also maintain the original component, but that means a lot of work.

…I've always loved it.

My problem with it: no support for relationships out of the box.

@froschdesign I intend to address that. Going to take some work though.