minilp solver?

Opening discussion: there is a native implementation of a LP solver in Rust: minilp. Supporting it would provide

a native experience, no external installation involved (glpk, cbc, etc.);
an useful fallback for higher level crates that rely on lp_modeler;
yet another solver to maintain.

Would this be interesting for the crate?

Kindly pinging the author of minilp @ztlpn; maybe you find this interesting.

It could be great. All contributions are welcome. Effectively, it would be more to maintain but it makes sense to promote such rust project. We just need to keep in mind to have the minimum of dependencies. If we can't, we could imagine integrating solver-modules independently from the core lib.

Great! We can make subcrates and/or put new solvers as a feature if needed, that would be very convenient. These are the ones from minilp (which are a bit outdated):
minilp v0.2.2 (/home/georg/GIT/minilp)
├── log v0.4.11
│   └── cfg-if v0.1.10
└── sprs v0.7.1
    ├── ndarray v0.13.1
    │   ├── matrixmultiply v0.2.3
    │   │   └── rawpointer v0.2.1
    │   ├── num-complex v0.2.4
    │   │   └── num-traits v0.2.14
    │   │       [build-dependencies]
    │   │       └── autocfg v1.0.1
    │   │   [build-dependencies]
    │   │   └── autocfg v1.0.1
    │   ├── num-integer v0.1.44
    │   │   └── num-traits v0.2.14 (*)
    │   │   [build-dependencies]
    │   │   └── autocfg v1.0.1
    │   ├── num-traits v0.2.14 (*)
    │   └── rawpointer v0.2.1
    ├── num-complex v0.2.4 (*)
    └── num-traits v0.1.43
        └── num-traits v0.2.14 (*)

I would suggest to integrate it as a non default feature.
At least as long as it describes itself as "an early-stage project".


in v0.4.2 tagged release the manifest still refers to v0.4.1 container image

Hi
Please update the container image tag in v.0.4.2 as it still  points to the debian bases based distro
Thanks
Niki Dokovski

hi @nickytd , thanks for reporting, the issue is casued because our githu actions does not replace it, not sure if it can be done in automatic way, will try to tackle that

https://github.com/metacontroller/metacontroller/issues/25

Closing as duplicate of https://github.com/metacontroller/metacontroller/issues/25


Wireguard selective routing gateways loop detected

Important notices
Before you add a new report, we ask you kindly to acknowledge the following:

[x] I have read the contributing guide lines at https://github.com/opnsense/core/blob/master/CONTRIBUTING.md
[x] I am convinced that my issue is new after having checked both open and closed issues at https://github.com/opnsense/core/issues?q=is%3Aissue

Describe the bug
Somewhat regularly, about once a day, one of the gateways I have set up for Mullvad will get 100% packet loss and General System Logs will show wgX: loop detected. If I manually disable then enable the gateways, things will be fine for a while.
I have created 3 tunnels to mullvad, put into a gateway group, following the mullvad roadwarrior and the selective routing guides to a tee.
To Reproduce
Steps to reproduce the behavior:

Create multiple mullvad tunnels and set up selective routing
Eventually one of the gateways will loop

Expected behavior
For the loops to not happen.
Describe alternatives you considered
Not sure of any viable alternatives.
Screenshots
Gateways if helpful:

Relevant log files
The logs show hundreds of lines of wgX: loop detected in the space of a few seconds. There are no consistent preceding events that I can find.
Additional context
I have opnsense sitting behind an AT&T fiber gateway in passthrough mode with the WAN gateway set to Far Gateway.
Separately, as a stopgap measure, is it possible to have monit restart the gateways? I was unable to find any commands that are capable of doing so.
Environment
Software version used and hardware type if relevant, e.g.:
OPNsense 23.7.7_3 (amd64, OpenSSL).
Intel i5-8600T 2.3Ghz 6 Core
Network Supermicro AOC-STGN-I2S

Same here https://forum.opnsense.org/index.php?topic=35919.0 ... since this pertains Mullvad and the kernel module I'm not entirely sure we can do anything here. Marking upstream for now.

I was following the docs for creating a site-to-site and noticed it has a normalization section in setting up firewall rules that doesn't exist for the mullvad & selective routing docs. After setting up the site-to-site I haven't had any issues.


[FLIP-321] Update the docs to add migration periods for deprecated APIs.

What is the purpose of the change
This PR update the ops doc to add the migration periods for deprecated APIs, which are specified in FLIP-321.
Brief change log
See the title.
Verifying this change
Build the docs and check the website locally at the following address:
http://localhost:1313/docs/ops/upgrading/#deprecated-api-migration-period
Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): (no)
The public API, i.e., is any changed class annotated with @Public(Evolving): (no)
The serializers: (no)
The runtime per-record code paths (performance sensitive): (no)
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn, ZooKeeper: (no)
The S3 file system connector: (no)

Documentation

Does this pull request introduce a new feature? (no)
If yes, how is the feature documented? (not applicable)

@mbalassi Do you have time to take a look at the doc update? Thanks!

@becketqin: We might want to edit the previous section too.
I think it is a bit misleading when we state there that a PublicEvolving API is not source/binary compatible across minor releases. (here we refer to the API as the active version of the API disregarding the deprecation period)
If I understand correctly, this is only true for the active version of the API. Contrary to the table in the docs - because of the proposed deprecation period - the source compatibility will be kept.
Also when we state this:

Code written against a PublicEvolving API in 1.15.2 will continue to run in 1.15.3, without having to recompile the code.
That same code would have to be recompiled when upgrading to 1.16.0 though.

This is only true because of the deprecation period we define later (here we refer to the API with the deprecation period in mind)

I've had an in-depth look on the compatibility guarantee matrix together with the deprecation policy and here are my findings:

The doc basically looks good from content perspective though I think adding it is not enough. Please see my later bullet points.
The binary compatibility matrix has a bug. Namely in Minor release we can't provide source compatibility without binary compatibility (according to the actual source code) because when we do compatibility check then we do both all the time. I think this must be guarantee provided both cases but explaining under what circumstances. (Please see my last bullet point)
The most important thing is that the binary compatibility matrix is not true anymore. Namely:

Some of the API changes are simply not possible because japicmp will block it (good example is patch releases where public API broken). How is planned to deal with japicmp? Personally I can't find any chapter about this.
With the new FLIP practically we don't have any kind of hard guarantees from now on which can be expressed with a simple true/false flag. I think the guarantee matrix would be good to be rephrased to reflect the actual state. (Basically all the green marks would be good to be explained under what circumstances are they true). When I would be a user and would see a simple green mark without conditions then I would think that it's true under any circumstances but it's not like that.

@pvary @mbalassi @gaborgsomogyi @JingGe Thanks a lot for the reviews.
From what I understand, FLIP-321 does not change the API stability guarantee, it only specifies a migration period. For example. For example, PublicEvolving APIs still can be removed with a minor version bump. It is just that with FLIP-321, the removal has to wait for at least an additional minor release.
In terms of the source / binary compatibility, the main reason we do not provide binary compatibility in minor releases for any API stability level is because we treat the protocol / format behind the public API as internal. For example, state format might change although the state backend API remains the same. An RPC protocol may change although the APIs in the user library remain the same. In these cases, users don't have to change their code, but they may have to recompile the code or rerun the job, due to the missing binary compatibility. It is not ideal, but it is what we currently do.
I agree the compatibility table looks confusing, although the contents seem accurate. I am wondering if some more concrete examples can help here.

Thanks for the explanation!

In terms of the source / binary compatibility, the main reason we do not provide binary compatibility in minor releases for any API stability level is because we treat the protocol / format behind the public API as internal.

If I understand correctly then couple of terms/compatibility levels are aggregated in the table. Since we're having japicmp which purely guarantees java based source/binary compatibility I was checking the table only from that point of view. The underneath protocols/internal files compatibility is not considered.
All in all that makes sense. Maybe we can highlight this info in a note to spare some time to others to avoid this pitfall.

I agree the compatibility table looks confusing, although the contents seem accurate. I am wondering if some more concrete examples can help here.

With fresh mind I've re-read/evaluated the whole again and seems like I've thought that Public and PublicEvolving description are having the same pattern in terms of when to remove old API statements (2 and 1 minor release 🙂). I can confirm the migration guide fits with the guarantees matrix.
In general I've the conclusion that existing documentation is valid but users are going to spend quite some time to understand each tiny pieces.

I would suggest to change the previous paragraph, like the following (remove the API compatibility related parts from there):
The top part could remain the same, just the title changed to Compatibility guarantees:
Compatibility guarantees

The classes & members of the Java/Scala APIs that are intended for users are annotated
with the following stability annotations:

- Public
- PublicEvolving
- Experimental

Annotations on a class also apply to all members of that class, unless otherwise annotated.
Any API without such an annotation is considered internal to Flink, with no guarantees being provided.

Then we should create 2 sub-paragraphs.
The 1st one could be Binary compatibility:
We guarantee binary compatibility only between patch releases for Public, and PublicEvolving interfaces.

Example: Code written against Public and PublicEvolving interfaces in 1.15.2 will continue to run in 1.15.3,
without having to recompile the code.
That same code would have to be recompiled when upgrading to 1.16.0 though, even if no code change is
required based on the API compatibility guarantees.

The 2nd one could be API compatibility, and here could come the paragraph written by @becketqin

@pvary Sorry for the late response. I read the section a few times and found that the compatibility guarantee statement itself is actually concise and accurate. However, the the example section is a little biased and probably should be articulated a bit more. I updated the patch with a few more examples.  Hopefully this makes the documents clear enough.

@becketqin: Thanks for the example changes! They really help to make sense of the previous table.


createUploadSession returns "API not found"

According to the onedrive api docs to upload large files to OneDrive, first you create an upload session, then you send the fragments. That all makes sense, but for some reason it's telling me that my request is invalid when I try the createUploadSession call to start the process.
Following the documentation, it says the request uri must follow this pattern:
POST /drive/root:/{path_to_item}:/createUploadSession

request:
method: 'POST'
uri: 'https://api.onedrive.com/v1.0/drive/root:/testfile-lg-1488040561730.bin:/createUploadSession
headers: { Authorization: 'Bearer .....' }

response:
status: 400
{ error: { code: 'invalidRequest', message: 'API not found' } }

I've tried various combinations of createUploadSession all lowercase, all uppercase, etc. It's perhaps worth noting that the small file <4MB simple file upload is working just fine.
cross posted here:
http://stackoverflow.com/questions/42458796/onedrive-api-createuploadsession-api-not-found

that was it 👍


[FLINK-13086]add Chinese documentation for catalogs

What is the purpose of the change
(For example: This pull request makes task deployment go through the blob server, rather than through RPC. That way we avoid re-transferring them on each deployment (during recovery).)
Brief change log
(for example:)

The TaskInfo is stored in the blob store on job creation time as a persistent artifact
Deployments RPC transmits only the blob storage reference
TaskManagers retrieve the TaskInfo from the blob cache

Verifying this change
(Please pick either of the following options)
This change is a trivial rework / code cleanup without any test coverage.
(or)
This change is already covered by existing tests, such as (please describe tests).
(or)
This change added tests and can be verified as follows:
(example:)

Added integration tests for end-to-end deployment with large payloads (100MB)
Extended integration test for recovery after master (JobManager) failure
Added test that validates that TaskInfo is transferred only once across recoveries
Manually verified the change by running a 4 node cluser with 2 JobManagers and 4 TaskManagers, a stateful streaming program, and killing one JobManager and two TaskManagers during the execution, verifying that recovery happens correctly.

Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): (yes / no)
The public API, i.e., is any changed class annotated with @Public(Evolving): (yes / no)
The serializers: (yes / no / don't know)
The runtime per-record code paths (performance sensitive): (yes / no / don't know)
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Yarn/Mesos, ZooKeeper: (yes / no / don't know)
The S3 file system connector: (yes / no / don't know)

Documentation

Does this pull request introduce a new feature? (yes / no)
If yes, how is the feature documented? (not applicable / docs / JavaDocs / not documented)

hi @yiduwangkai , why we removed sqlClient.zh.md page? Is that a mistake?

@wuchong sqlClient.zh.md split to another issue  https://github.com/apache/flink/pull/9164

i have updated @bowenli86

@yiduwangkai , please rebase your commit on the latest master and do not use "merge".

yes i used rebase at first, But when I execute this command, when I push,
git asks for pull, maybe it is improper operation before, causing the
situation to be merged when the pull occurs, but please be assured that no
other files have been changed. thx
Jark Wu<EMAIL_ADDRESS>于2019年7月21日周日 下午10:19写道：

@yiduwangkai https://github.com/yiduwangkai , please rebase your commit
on the latest master and do not use "merge".
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/apache/flink/pull/9163?email_source=notifications&email_token=AD2ZDBHSBSJYWL6VVB3N7PTQARV7HA5CNFSM4IE2BCW2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD2OEPIQ#issuecomment-513558434,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AD2ZDBA2MWPASONZMY55QPTQARV7HANCNFSM4IE2BCWQ
.

Why is there a new merge commit extra information, because I use the pull
command to pull the latest code of the upstream branch, this record will be
generated if the local branch lags behind the upstream branch
kai wang<EMAIL_ADDRESS>于2019年7月21日周日 下午11:28写道：

yes i used rebase at first, But when I execute this command, when I push,
git asks for pull, maybe it is improper operation before, causing the
situation to be merged when the pull occurs, but please be assured that no
other files have been changed. thx
Jark Wu<EMAIL_ADDRESS>于2019年7月21日周日 下午10:19写道：

@yiduwangkai https://github.com/yiduwangkai , please rebase your
commit on the latest master and do not use "merge".
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/apache/flink/pull/9163?email_source=notifications&email_token=AD2ZDBHSBSJYWL6VVB3N7PTQARV7HA5CNFSM4IE2BCW2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD2OEPIQ#issuecomment-513558434,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AD2ZDBA2MWPASONZMY55QPTQARV7HANCNFSM4IE2BCWQ
.

Hi @yiduwangkai , can you rebase this PR?

can you rebase this PR?

oK

OK
Bowen L<EMAIL_ADDRESS>于2019年8月13日周二 上午2:36写道：

Hi @yiduwangkai https://github.com/yiduwangkai , can you rebase this PR?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/apache/flink/pull/9163?email_source=notifications&email_token=AD2ZDBDYPEUR3FY6OMMBCLLQEGUULA5CNFSM4IE2BCW2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD4DN7RQ#issuecomment-520544198,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AD2ZDBHLVP7EAE6YKR3FAR3QEGUULANCNFSM4IE2BCWQ
.

i want to close this pr, merge [apache/flink] [FLINK-13086]add Chinese
documentation for catalogs (#9163)
and [apache/flink] [FLINK-12894]add Chinese documentation of how to
configure and use catalogs in SQL CLI (#9164) together and submit a new
one, do you agree
kai wang<EMAIL_ADDRESS>于2019年8月13日周二 上午9:32写道：

OK
Bowen L<EMAIL_ADDRESS>于2019年8月13日周二 上午2:36写道：

Hi @yiduwangkai https://github.com/yiduwangkai , can you rebase this
PR?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/apache/flink/pull/9163?email_source=notifications&email_token=AD2ZDBDYPEUR3FY6OMMBCLLQEGUULA5CNFSM4IE2BCW2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD4DN7RQ#issuecomment-520544198,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AD2ZDBHLVP7EAE6YKR3FAR3QEGUULANCNFSM4IE2BCWQ
.

opening a single PR with multi commits sounds good to me


Routing access

I installed this project, but didn't my interface routing add an API after the address? Why can't you access it?

Hey @libaowei924
Sorry but I can't quite understand the issue, can you please describe in more detail?

Should I add an API after the link? Such as http://laravel-api-boilerplate.test/api/home

Should I add an API after the link? Such as http://laravel-api-boilerplate.test/api/home
404 no matter how I access it

@specialtactics

Only docker?

Hi, how are you sending these messages? I Cannot find on github
On Mon, Nov 18, 2019 at 4:28 PM libaowei924<EMAIL_ADDRESS>wrote:

Only docker?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/specialtactics/laravel-api-boilerplate/issues/33?email_source=notifications&email_token=AAWRT2VND367XEBSED4ECYTQUIRXPA5CNFSM4JONRRR2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEEJHK3A#issuecomment-554857836,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAWRT2W3BLXHBNU75RJLKXLQUIRXPANCNFSM4JONRRRQ
.


How to use amplitude in Angular 5 ?

Trying to understand the possibility of using amplitude in Angular Applications. How do I import the whole library, any demos ?

+1

Import amplitudejs as below and you are good to go.
import * as amplitudejs from 'amplitudejs'

this doesn't seem to work when doing a production build. amplitude is null. may or may not relate to use of lazy loaded modules too

You should be able to use AmplitudeJS inside of any angular component when you import it. I'll release some examples for how to do this

So u took almost 5 months to reply the same message u replied the first
day. Haha
On Wed, May 23, 2018, 9:57 PM Dan Pastori<EMAIL_ADDRESS>wrote:

You should be able to use AmplitudeJS inside of any angular component when
you import it. I'll release some examples for how to do this
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/521dimensions/amplitudejs/issues/231#issuecomment-391411535,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ADR8XkJvw3jGX3Bl47W_baQFQ-MvXomPks5t1Y3VgaJpZM4RQFmK
.

Hey @warlockdn,
Thanks for understanding that this is an open source project. We don't get paid to maintain this and sometimes we have our own lives to take care of.
You have just as much capabilities to make contributions, so if you like to speed things up -- volunteer and submit a pull request.

import * as amplitudejs from 'amplitudejs'

I think you also need to install the DefinitelyTyped amplitude-js @types/amplitude-js
Then you can import amplitude in every file us use as @ashecret  mentioned.


Can not use more than one instance, first instance crashes when opening a second one.

Hello, I hope this is the right place.
Something makes it that opening multiple vscode instances crashes all instances when using wayland. I tested it by opening two windows, as soon as I open the second one both crash. Sometimes I the second window works once but when I close and open it again the crash happens.
I see this issues propably since a year, I did not want to spend time with it and switched to Xwayland thought it would get fixed cause it's quite a problem if you can not open more than one vscode instance at a time. Is it just me who has this issue - Should I ask the question in the arch community?
There seem to be two problems. Leftover lock-files (can no longer reproduce right now) and issues with the GPU cache or something. When I delete .config/Code/GPUCache and .config/Code/Crashpad/pending I am able to launch two windows I thought, but not does not always help, maybe sometimes I have to delete even more like the whole folder more cache related dirs.
The flags I start vscode with are --ozone-platform-hint=auto --enable-features=WaylandWindowDecorations and have set "window.titleBarStyle": "custom".
I used code --log debug --verbose cause code --crash-reporter-directory did not work, I think it is only an option to debug crashes that happen from inside the one instance. I wonder why only the first vscode instance keeps logging, while the second one just finishes, it's propably designed to allow some special interaction between vscode instances?
 I don't know if it matters or not, but I tested with and without options i915 enable_guc=2 and I tested on linux and linux-zen kernel. It does not affect the situation.
Logs
The log of the second (causing) editor - Crashpad (pending lock files)
Could not reproduce it. Will try again later. Also saw some vscode crashpad processes hanging around, when no vsocde instances are running.
The log of the second (causing) editor - Sandbox (GPU Cache)
Warning: 'ozone-platform-hint' is not in the list of known options, but still passed to Electron/Chromium.
Warning: 'enable-features' is not in the list of known options, but still passed to Electron/Chromium.
[0124/100409.947933:ERROR:file_io_posix.cc(152)] open /home/cartok/.config/Code/Crashpad/pending/d278bae3-a8de-4c0d-9890-61da205b0759.lock: File exists (17)
[42663:0124/100409.949408:WARNING:wayland_object.cc(157)] Binding to zwp_linux_dmabuf_v1 version 3 but version 4 is available.
[42663:0124/100409.949515:WARNING:wayland_object.cc(157)] Binding to zwp_pointer_gestures_v1 version 1 but version 3 is available.
[42663:0124/100409.996647:WARNING:bluez_dbus_manager.cc(247)] Floss manager not present, cannot set Floss enable/disable.
[main 2024-01-24T09:04:10.050Z] [File Watcher (node.js)] Request to start watching: /home/cartok/.config/Code/User (excludes: <none>, includes: <all>, correlationId: <none>),/home/cartok/.config/Code/User/settings.json (excludes: <none>, includes: <all>, correlationId: <none>)
[42706:0124/100410.053289:WARNING:sandbox_linux.cc(393)] InitializeSandbox() called with multiple threads in process gpu-process.
[main 2024-01-24T09:04:10.059Z] Sending env to running instance...
[main 2024-01-24T09:04:10.060Z] [File Watcher (node.js)] Started watching: '/home/cartok/.config/Code/User'
[main 2024-01-24T09:04:10.060Z] [File Watcher (node.js)] Started watching: '/home/cartok/.config/Code/User/settings.json'
[main 2024-01-24T09:04:10.077Z] Sent env to running instance. Terminating...
[main 2024-01-24T09:04:10.078Z] Lifecycle#kill()
[main 2024-01-24T09:04:10.078Z] Lifecycle#onWillShutdown.fire()

The log of the first editor
[main 2024-01-24T09:42:57.599Z] Lifecycle#onBeforeCloseWindow.fire() - window ID 4
[main 2024-01-24T09:42:57.601Z] IPC Object URL: Removed channel vscode:9d1990c0-b132-46c8-bc18-93b786656254.
[main 2024-01-24T09:42:57.603Z] Lifecycle#window.on('closed') - window ID 4
[main 2024-01-24T09:42:57.603Z] [UtilityProcess id: 4, type: fileWatcher, pid: 60338]: attempting to kill the process...
[main 2024-01-24T09:42:57.603Z] [UtilityProcess id: 4, type: fileWatcher, pid: 60338]: successfully killed the process
[main 2024-01-24T09:42:57.608Z] [UtilityProcess id: 4, type: fileWatcher, pid: 60338]: received exit event with code 15
[main 2024-01-24T09:42:57.608Z] [UtilityProcessWorker]: terminated unexpectedly with code 15, signal: unknown
[main 2024-01-24T09:42:57.608Z] [UtilityProcess id: 4, type: fileWatcher, pid: 60338]: crashed with code 15 and reason 'killed'
[main 2024-01-24T09:42:57.615Z] [UtilityProcess id: 4, type: extensionHost, pid: 60349]: received exit event with code 0
[main 2024-01-24T09:42:57.615Z] Extension host with pid 60349 exited with code: 0, signal: unknown.
[main 2024-01-24T09:42:58.784Z] resolveShellEnv(): skipped (VSCODE_CLI is set)
[main 2024-01-24T09:42:59.029Z] resolveShellEnv(): skipped (VSCODE_CLI is set)
[main 2024-01-24T09:43:01.029Z] resolveShellEnv(): skipped (VSCODE_CLI is set)
[main 2024-01-24T09:43:01.104Z] Received data from other instance:  {
  _: [ '/home/cartok/tests' ],
  diff: false,
  merge: false,
  add: false,
  goto: false,
  'new-window': false,
  'reuse-window': false,
  wait: false,
  help: false,
  'list-extensions': false,
  'show-versions': false,
  'pre-release': false,
  version: false,
  verbose: true,
  log: [ 'debug' ],
  status: false,
  'prof-startup': false,
  'no-cached-data': false,
  'prof-v8-extensions': false,
  'disable-extensions': false,
  'disable-gpu': false,
  'disable-chromium-sandbox': false,
  'ms-enable-electron-run-as-node': false,
  telemetry: false,
  debugRenderer: false,
  'enable-smoke-test-driver': false,
  logExtensionHostCommunication: false,
  'skip-release-notes': false,
  'skip-welcome': false,
  'disable-telemetry': false,
  'disable-updates': false,
  'use-inmemory-secretstorage': false,
  'disable-workspace-trust': false,
  'disable-crash-reporter': false,
  'crash-reporter-id': '44a270ac-b647-41f3-82be-2f35bffb1b16',
  'skip-add-to-recently-opened': false,
  'unity-launch': false,
  'open-url': false,
  'file-write': false,
  'file-chmod': false,
  force: false,
  'do-not-sync': false,
  trace: false,
  'force-user-env': false,
  'force-disable-user-env': false,
  'open-devtools': false,
  'disable-gpu-sandbox': false,
  '__enable-file-policy': false,
  'enable-coi': false,
  'no-proxy-server': false,
  'no-sandbox': false,
  nolazy: false,
  'force-renderer-accessibility': false,
  'ignore-certificate-errors': false,
  'allow-insecure-localhost': false,
  'disable-dev-shm-usage': false,
  'profile-temp': false,
  logsPath: '/home/cartok/.config/Code/logs/20240124T104301'
} {
  SHELL: '/bin/zsh',
  WINDOWID: '100981401194320',
  LINUX_CONFIGS_USER_CONFIGS: '/usr/local/share/linux-configs/src/skel/home/cartok/.config',
  COLORTERM: 'truecolor',
  ZPWR_TABSTOP: '__________',
  FNM_ARCH: 'x64',
  PKG_CONFIG_PATH: '/usr/local/share/pkgconfig:/usr/local/lib64/pkgconfig:/usr/local/lib/pkgconfig:/usr/local/share/pkgconfig:/usr/local/lib64/pkgconfig:/usr/local/lib/pkgconfig:',
  ZPWR_EXPAND_NATIVE: 'false',
  QT_WAYLAND_DISABLE_WINDOWDECORATION: '1',
  I3SOCK: '/run/user/1000/sway-ipc.1000.7884.sock',
  LC_ADDRESS: 'de_DE.UTF-8',
  OPENER: 'xdg-open',
  LC_NAME: 'de_DE.UTF-8',
  LINUX_CONFIGS_MACHINE: 'desktop',
  FNM_NODE_DIST_MIRROR: 'https://nodejs.org/dist',
  LC_MONETARY: 'de_DE.UTF-8',
  LINUX_CONFIGS_GREY_4: '#969696',
  LINUX_CONFIGS_GREY_5: '#a1a8aa',
  LINUX_CONFIGS_GREY_6: '#e7e7e7',
  LINUX_CONFIGS_GREY_7: '#dfdfdf',
  LINUX_CONFIGS_GREY_1: '#1e1e1e',
  LINUX_CONFIGS_GREY_2: '#3d3d3d',
  LINUX_CONFIGS_GREY_3: '#5f676a',
  XCURSOR_SIZE: '24',
  EDITOR: 'nano',
  XDG_SEAT: 'seat0',
  PWD: '/home/cartok',
  LOGNAME: 'cartok',
  QT_QPA_PLATFORMTHEME: 'gnome',
  ZPWR_EXPAND: 'true',
  XDG_SESSION_TYPE: 'wayland',
  ZPWR_CORRECT: 'false',
  BEMENU_BACKEND: 'wayland',
  FZF_DEFAULT_COMMAND: 'fd --strip-cwd-prefix --one-file-system --ignore-file ~/.config/fd/ignore',
  TERMINAL: '/bin/alacritty',
  MOTD_SHOWN: 'pam',
  LINUX_CONFIGS: '/usr/local/share/linux-configs/src',
  LINUX_CONFIGS_STATE: '/home/cartok/.local/state/linux-configs',
  USER_NAME: 'cartok',
  HOME: '/home/cartok',
  LANG: 'de_DE.UTF-8',
  LC_PAPER: 'de_DE.UTF-8',
  FNM_COREPACK_ENABLED: 'false',
  XDG_CURRENT_DESKTOP: 'sway',
  STARSHIP_SHELL: 'zsh',
  SWAYSOCK: '/run/user/1000/sway-ipc.1000.7884.sock',
  WAYLAND_DISPLAY: 'wayland-1',
  ZPWR_EXPAND_TO_HISTORY: 'false',
  MANROFFOPT: '-c',
  LINUX_CONFIGS_TERMINAL_BG: '#222222',
  LINUX_CONFIGS_CHROME_BG: '#1f1f1f',
  ZPWR_EXPAND_QUOTE_SINGLE: 'false',
  STARSHIP_SESSION_KEY: '2590022290289231',
  QT_QPA_PLATFORM: 'wayland;xcb',
  ALACRITTY_SOCKET: '/run/user/1000/Alacritty-wayland-1-51088.sock',
  SWAY_CONFIGS_DIR: '/usr/local/share/linux-configs/src/skel/home/cartok/.config/sway',
  XDG_SESSION_CLASS: 'user',
  LC_IDENTIFICATION: 'de_DE.UTF-8',
  TERM: 'alacritty',
  BAT_PAGER: '/usr/bin/less -RF --mouse --use-color --wheel-lines=2',
  LINUX_CONFIGS_BLUE_1: '#2e9ef4',
  LINUX_CONFIGS_BLUE_3: '#4c7899',
  LINUX_CONFIGS_BLUE_2: '#285577',
  LINUX_CONFIGS_BLUE_4: '#5d8fb4',
  ASDF_DIR: '/opt/asdf-vm',
  USER: 'cartok',
  LINUX_CONFIGS_ROOT: '/usr/local/share/linux-configs',
  LINUX_CONFIGS_MACHINE_DIR: '/usr/local/share/linux-configs/src/machines/by-name/desktop',
  MANPAGER: "  sh -c 'col --no-backspaces --spaces     | /usr/bin/bat --paging always --plain --language man --theme Nord' ",
  VISUAL: 'code',
  DISPLAY: ':0',
  SHLVL: '3',
  MOZ_ENABLE_WAYLAND: '1',
  CHROME_EXECUTABLE: '/usr/bin/google-chrome-stable',
  PAGER: "/usr/bin/bat --theme='base16-256' --wrap='never'",
  LINUX_CONFIGS_LOGS: '/var/log/linux-configs',
  LC_TELEPHONE: 'de_DE.UTF-8',
  ZPWR_CORRECT_EXPAND: 'true',
  LC_MESSAGES: 'POSIX',
  LC_MEASUREMENT: 'de_DE.UTF-8',
  FNM_VERSION_FILE_STRATEGY: 'local',
  XDG_VTNR: '1',
  XDG_SESSION_ID: '1',
  ATUIN_SESSION: '018d3ac1f77d710fb4c8f1d4a53f0226',
  SWAY_SCRIPTS_DIR: '/usr/local/share/linux-configs/src/skel/home/cartok/.config/sway/scripts',
  LINUX_CONFIGS_WHITE: '#ffffff',
  ATUIN_HISTORY_ID: '018d3ad9fb7c7925a1fca4e78570ab54',
  LD_LIBRARY_PATH: '/usr/local/lib64/:/usr/local/lib/:',
  LC_CTYPE: 'de_DE.UTF-8',
  XDG_RUNTIME_DIR: '/run/user/1000',
  FNM_RESOLVE_ENGINES: 'false',
  LINUX_CONFIGS_BLACK: '#000000',
  NODE_PATH: '/home/cartok/.local/share/fnm/node-versions/v21.0.0/installation/lib/node_modules',
  DEBUGINFOD_URLS: 'https://debuginfod.archlinux.org ',
  LC_TIME: 'de_DE.UTF-8',
  SWAY_APPS_DIR: '/usr/local/share/linux-configs/src/skel/home/cartok/.config/sway/apps.d',
  ZPWR_EXPAND_SECOND_POSITION: 'true',
  LC_COLLATE: 'POSIX',
  XDG_DATA_DIRS: '/usr/local/share:/usr/share:/var/lib/snapd/desktop',
  PATH: '/run/user/1000/fnm_multishells/51161_1706087806854/bin:/home/cartok/.local/share/fnm:/run/user/1000/fnm_multishells/51111_1706087806733/bin:/home/cartok/.local/share/fnm:/run/user/1000/fnm_multishells/925_1706023140301/bin:/home/cartok/.local/share/fnm:/run/user/1000/fnm_multishells/861_1706023140099/bin:/home/cartok/.asdf/shims:/opt/asdf-vm/bin:/usr/local/sbin:/usr/local/bin:/usr/bin:/usr/lib/jvm/default/bin:/usr/bin/site_perl:/usr/bin/vendor_perl:/usr/bin/core_perl:/var/lib/snapd/snap/bin:/home/cartok/.local/bin:/home/cartok/.bun/bin:/home/cartok/.local/share/sheldon/repos/github.com/reegnz/jq-zsh-plugin/bin:/home/cartok/.local/share/sheldon/repos/github.com/reegnz/jq-zsh-plugin/bin',
  ALACRITTY_LOG: '/tmp/Alacritty-51088.log',
  QTWEBENGINE_CHROMIUM_FLAGS: '--no-sandbox',
  DBUS_SESSION_BUS_ADDRESS: 'unix:path=/run/user/1000/bus',
  MAIL: '/var/spool/mail/cartok',
  FNM_DIR: '/home/cartok/.local/share/fnm',
  FNM_MULTISHELL_PATH: '/run/user/1000/fnm_multishells/51161_1706087806854',
  ZPWR_EXPAND_QUOTE_DOUBLE: 'true',
  ALACRITTY_WINDOW_ID: '100981401194320',
  FNM_LOGLEVEL: 'info',
  LC_NUMERIC: 'en_US.UTF-8',
  OLDPWD: '/home/cartok',
  LINUX_CONFIGS_SKEL: '/usr/local/share/linux-configs/src/skel',
  _: '/opt/visual-studio-code/bin/../code',
  VSCODE_CWD: '/home/cartok',
  VSCODE_CLI: '1',
  ELECTRON_NO_ATTACH_CONSOLE: '1',
  ELECTRON_ENABLE_LOGGING: '1',
  CHROME_DESKTOP: 'code-url-handler.desktop',
  ORIGINAL_XDG_CURRENT_DESKTOP: 'sway',
  GDK_BACKEND: 'wayland',
  NO_AT_BRIDGE: '1',
  VSCODE_NLS_CONFIG: '{"locale":"en-us","osLocale":"posix","availableLanguages":{},"_languagePackSupport":true}',
  VSCODE_CODE_CACHE_PATH: '/home/cartok/.config/Code/CachedData/0ee08df0cf4527e40edc9aa28f4b5bd38bbff2b2',
  VSCODE_IPC_HOOK: '/run/user/1000/vscode-ab725310-1.85-main.sock'
}
[main 2024-01-24T09:43:01.105Z] windowsManager#open
[main 2024-01-24T09:43:01.105Z] windowsManager#open pathsToOpen [
  {
    workspace: { id: '6aab973033dcf65633ce07010ddf934d', uri: [$] },
    type: 2,
    exists: true
  }
]
[main 2024-01-24T09:43:01.105Z] windowsManager#doOpenFolderOrWorkspace {
  folderOrWorkspace: {
    workspace: { id: '6aab973033dcf65633ce07010ddf934d', uri: [$] },
    type: 2,
    exists: true
  },
  filesToOpen: undefined
}
[main 2024-01-24T09:43:01.105Z] IPC Object URL: Registered new channel vscode:346b576b-6ae9-4160-96ed-42bab09afddd.
[main 2024-01-24T09:43:01.105Z] window#validateWindowState: validating window state on 1 display(s) {
  width: 1024,
  height: 768,
  mode: 1,
  x: 3128,
  y: 336,
  hasDefaultState: true
}
[main 2024-01-24T09:43:01.105Z] window#validateWindowState: 1 monitor working area { x: 1920, y: 0, width: 3440, height: 1440 }
[main 2024-01-24T09:43:01.105Z] window#ctor: using window state {
  width: 1024,
  height: 768,
  mode: 1,
  x: 3128,
  y: 336,
  hasDefaultState: true
}
[main 2024-01-24T09:43:01.113Z] window#load: attempt to load window (id: 5)
[main 2024-01-24T09:43:01.116Z] windowsManager#open used window count 1 (workspacesToOpen: 0, foldersToOpen: 1, emptyToRestore: 0, emptyToOpen: 0)
[main 2024-01-24T09:43:01.140Z] resolveShellEnv(): skipped (VSCODE_CLI is set)
[0124/104301.157996:ERROR:elf_dynamic_array_reader.h(64)] tag not found
[0124/104301.163708:ERROR:directory_reader_posix.cc(42)] opendir /home/cartok/.config/Code/Crashpad/attachments/b93477bb-6971-4452-a7a0-823fde12f216: No such file or directory (2)

Another suspect log from the first editor which I can't reproduce tho
file://vscode-app/opt/visual-studio-code/resources/app/out/vs/workbench/workbench.desktop.main.js (643)
[main 2024-01-24T09:40:19.141Z] [UtilityProcess type: ptyHost, pid: <none>]: creating new...
[main 2024-01-24T09:40:19.144Z] PtyHostService#_startPtyHost
    at g.U (/opt/visual-studio-code/resources/app/out/vs/code/electron-main/main.js:103:2969)
    at g.h (/opt/visual-studio-code/resources/app/out/vs/code/electron-main/main.js:103:1428)
    at get f [as f] (/opt/visual-studio-code/resources/app/out/vs/code/electron-main/main.js:103:1378)
    at g.setTerminalLayoutInfo (/opt/visual-studio-code/resources/app/out/vs/code/electron-main/main.js:103:5987)
    at Object.call (/opt/visual-studio-code/resources/app/out/vs/code/electron-main/main.js:42:5005)
    at A.s (/opt/visual-studio-code/resources/app/out/vs/code/electron-main/main.js:40:5116)
    at A.q (/opt/visual-studio-code/resources/app/out/vs/code/electron-main/main.js:40:4639)
    at $.value (/opt/visual-studio-code/resources/app/out/vs/code/electron-main/main.js:40:4050)
    at a.y (/opt/visual-studio-code/resources/app/out/vs/code/electron-main/main.js:35:1902)
    at a.z (/opt/visual-studio-code/resources/app/out/vs/code/electron-main/main.js:35:1972)
    at a.fire (/opt/visual-studio-code/resources/app/out/vs/code/electron-main/main.js:35:2188)
    at $.value (/opt/visual-studio-code/resources/app/out/vs/code/electron-main/main.js:33:28535)
    at a.y (/opt/visual-studio-code/resources/app/out/vs/code/electron-main/main.js:35:1902)
    at a.fire (/opt/visual-studio-code/resources/app/out/vs/code/electron-main/main.js:35:2119)
    at $.value (/opt/visual-studio-code/resources/app/out/vs/code/electron-main/main.js:33:28742)
    at a.y (/opt/visual-studio-code/resources/app/out/vs/code/electron-main/main.js:35:1902)
    at a.fire (/opt/visual-studio-code/resources/app/out/vs/code/electron-main/main.js:35:2119)
    at me (/opt/visual-studio-code/resources/app/out/vs/code/electron-main/main.js:33:31189)
    at IpcMainImpl.u (/opt/visual-studio-code/resources/app/out/vs/code/electron-main/main.js:42:18858)
    at IpcMainImpl.emit (node:events:525:35)
    at WebContents.<anonymous> (node:electron/js2c/browser_init:2:88654)
    at WebContents.emit (node:events:513:28)
[main 2024-01-24T09:40:19.146Z] [UtilityProcess type: ptyHost, pid: 59800]: successfully created
[main 2024-01-24T09:40:19.149Z] Lifecycle#onBeforeCloseWindow.fire() - window ID 2
[main 2024-01-24T09:40:19.153Z] IPC Object URL: Removed channel vscode:b4d7138c-7ab1-4c30-a4a1-8585fcdba230.
[main 2024-01-24T09:40:19.155Z] Lifecycle#window.on('closed') - window ID 2
[main 2024-01-24T09:40:19.156Z] [UtilityProcess id: 2, type: fileWatcher, pid: 59681]: attempting to kill the process...
[main 2024-01-24T09:40:19.156Z] [UtilityProcess id: 2, type: fileWatcher, pid: 59681]: successfully killed the process
[main 2024-01-24T09:40:19.161Z] [UtilityProcess id: 2, type: fileWatcher, pid: 59681]: received exit event with code 0
[main 2024-01-24T09:40:19.161Z] [UtilityProcessWorker]: terminated normally with code 0, signal: unknown
[main 2024-01-24T09:40:19.162Z] [UtilityProcess id: 2, type: fileWatcher, pid: 59681]: crashed with code 15 and reason 'killed'
[main 2024-01-24T09:40:19.164Z] [UtilityProcess id: 2, type: extensionHost, pid: 59691]: received exit event with code 0
[main 2024-01-24T09:40:19.165Z] Extension host with pid 59691 exited with code: 0, signal: unknown.
[main 2024-01-24T09:40:21.165Z] resolveShellEnv(): skipped (VSCODE_CLI is set)

Another thing
Don't know if it is related, could be, I expected this to vanish some day but it still persists.
Warning: 'ozone-platform-hint' is not in the list of known options, but still passed to Electron/Chromium.
Warning: 'enable-features' is not in the list of known options, but still passed to Electron/Chromium.

I wonder why only the first vscode instance keeps logging, while the second one just finishes, it's propably designed to allow some special interaction between vscode instances?

We have a singleton implementation for running instances, basically the first instance will act as a server and if new instances are launched they will connect to this server to check if they can be merged, if yes then instead of creating a completely new process tree the new instance will just be a child window of the first instance. Hence you see the logs cut off in the second instance after the merge happens.
Can you check if the crash repros with our insiders version as well https://code.visualstudio.com/insiders, you can avoid passing --crash-reporter-directory. The crashes should be available in .config/Code - Insiders/Crashpad

Thanks @deepak1556
On the insider version, two or more windows open, but only one is usable. I recorded a short 5 min video to demonstrate the issues and uploaded it here: https://www.youtube.com/watch?v=FwQp6InxCb8
This is the crashpad: vscode-issue-203310-crashpad-1.zip

Hey @deepak1556, this issue might need further attention.
@cartok, you can help us out by closing this issue if the problem no longer exists, or adding more information.

I don't experience this issue anymore.


powerdevil: build with ddcutil support

Description of changes
Powerdevil supports changing external monitor brightness via ddcutil, which sends DDC protocol messages over an I2C bus to the external monitor. However, powerdevil needs to be built with ddcutil and needs user access for the i2c bus. Therefore, I added ddcutil to the powerdevil package and enabled i2c along with powerdevil in the plasma module.
Shoutout @getchoo for the help!
Things done

Built on platform(s)

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

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

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

[X] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

This has been brought up before. DDC/CI is very unreliable, and using it incorrectly can lead to permanently messing up your hardware. It should not be enabled by default.

If you're talking about previous KDE versions, at least starting with version 6.0, KDE has refined their approach to using libddcutil as explained in [this blog](Starting with Plasma 6.0.4, our DDC/CI code was restructured so that a monitor is only hogged for the short time it takes to change the brightness. ddcutil works again as intended in a Plasma session.) here. Furthermore, distros like Arch have enabled ddcutil as of recent, and everything seems to be fine now.

No, that's not the issue. The issue is that ddcutil, and DDC/CI in general, provides no way to enumerate devices, and has to blindly poke I2C buses and hope the right thing is on the other end, which can severely confuse other I2C hardware.

Alright, I appreciate the information. Thanks for taking the time for a response 👍


encountered  error while using npm start

Thanks for reporting the error @ookangzheng.
I'm seeing the same issue and have reported it in the underlying library that create-choo-app is using for compilation, bankai.
As a temporary workaround to get you back up and running you can amend the version of bankai in your package.json to 9.5.0 and reinstall your node modules. This should avoid the issue which seems to have appeared in 9.6.0.

npm update should give you<EMAIL_ADDRESS>which fixes this. thanks!

yap, thanks a lot


Dependabot, Multi-repo, AzureDevOps

Is there an existing issue for this?

[X] I have searched the existing issues

Package ecosystem
AzureDevOps
Package manager version
Terraform
Language version
Terraform
Manifest location and content before the Dependabot update
I’m using Dependabot to manage Terraform dependencies in my Azure DevOps pipeline, but I’m encountering the "Requirements to unlock update_not_possible" message for all my Terraform providers. Despite trying various configurations, Dependabot does not generate pull requests to update the dependencies.
dependabot.yml content
version: 2
updates:

package-ecosystem: "terraform"
directory: "/"
schedule:
interval: "weekly"
ignore:

dependency-name: "some-unwanted-dependency"
allow:
dependency-name: "akeyless-community/akeyless"
dependency-name: "azure/azapi"
dependency-name: "hashicorp/azurerm"
dependency-name: "hashicorp/tls"
dependency-name: "tchupp/env"
#- dependency-name: "truth::azure::hugoboss/TerraformModule/_git/hb_az_ministry_of_truth"
commit-message:
prefix: "terraform"
labels:
"dependencies"
open-pull-requests-limit: 5
reviewers:
"reviewer-github-username"
versioning-strategy: "increase-if-necessary"
insecure-external-code-execution: "allow"
rebase-strategy: "auto"
log-level: "debug"

Updated dependency
Found 7 dependency file(s) at commit d98b4bc2a4b172fd84a6770c6d6cd5e36dd7ac32

/data.tf
/inputs.tf
/locals.tf
/main.tf
/outputs.tf
/providers.tf
/secret.tf
Parsing dependencies information
##[debug]Agent environment resources - Disk: / Available 20340.00 MB out of 74244.00 MB, Memory: Used 771.00 MB out of 6921.00 MB, CPU: Usage 15.81%
Found 6 dependencies
akeyless-community/akeyless ()
azure/azapi ()
hashicorp/azurerm ()
hashicorp/tls ()
tchupp/env ()
truth::azure::hugoboss/TerraformModule/_git/hb_az_ministry_of_truth::stable/v2 ()
🌍 --> GET https://dev.azure.com/hugoboss/_apis/connectionData
🌍 <-- 200 https://dev.azure.com/hugoboss/_apis/connectionData
🌍 --> GET https://dev.azure.com/hugoboss/TerraformModule/_apis/git/repositories/hb_az_virtual_machine
🌍 <-- 200 https://dev.azure.com/hugoboss/TerraformModule/_apis/git/repositories/hb_az_virtual_machine
🌍 --> GET https://dev.azure.com/hugoboss/TerraformModule/_apis/git/repositories/hb_az_virtual_machine/pullrequests?api-version=7.1&searchCriteria.status=active&searchCriteria.creatorId=5205a1c5-6569-4b1f-a34f-27da7cadf742&searchCriteria.targetRefName=refs/heads/main
🌍 <-- 200 https://dev.azure.com/hugoboss/TerraformModule/_apis/git/repositories/hb_az_virtual_machine/pullrequests?api-version=7.1&searchCriteria.status=active&searchCriteria.creatorId=5205a1c5-6569-4b1f-a34f-27da7cadf742&searchCriteria.targetRefName=refs/heads/main
Checking if akeyless-community/akeyless  needs updating
🌍 --> GET https://registry.terraform.io/.well-known/terraform.json
🌍 <-- 200 https://registry.terraform.io/.well-known/terraform.json
🌍 --> GET https://registry.terraform.io/v1/providers/akeyless-community/akeyless/versions
🌍 <-- 200 https://registry.terraform.io/v1/providers/akeyless-community/akeyless/versions
Requirements to unlock update_not_possible
Requirements update strategy #Dependabot::RequirementsUpdateStrategy::BumpVersionsIfNecessary
Checking if azure/azapi  needs updating

What you expected to see, versus what you actually saw
I was expecting a creation of a Pull Request for the updates of the dependencies
Native package manager behavior
No response
Images of the diff or a link to the PR, issue, or logs
No response
Smallest manifest that reproduces the issue
No response

Hey @CodeMalasartes, looking at your log output, you're using the Dependabot Azure DevOps Extension. There are some known issues with the version of the update script you are using and it is possible that this issue is caused by the Azure DevOps implementation, not dependabot-core itself. Are you able to see if any of the below helps fix your issue:

Use the newer "vNext" update script in the DevOps extension; This is based on newer updater code dependabot-core's updater project and should be more accurate when compared to the update script shown in your logs. You can enable the vNext script by ticking the "Use latest update script (vNext)" checkbox under "Advanced" in the task options, or using useUpdateScriptvNext: true if using YML pipelines.

Add dependency-type: all to your allowed dependencies in dependabot.yml. e.g.
allow:
  - dependency-name: "akeyless-community/akeyless"
    dependency-type: all
  - dependency-name: "azure/azapi"
    dependency-type: all
  - dependency-name: "hashicorp/azurerm"
    dependency-type: all
  - dependency-name: "hashicorp/tls"
    dependency-type: all
  - dependency-name: "tchupp/env"
    dependency-type: all

This shouldn't be required as "all" is the default based on official examples, but it is possible the Azure DevOps extension is not defaulting this to "all" so explicitly setting might help.

When using Terrform, the versioning-strategy option is not supported. This shouldn't cause any issues, but just a FYI.


How to enable notifications?

Within the IOS Home App, long pressing the accessory, tapping Details, Status and Notifications, shows no options for notifications.  Is this something that needs to be enabled/coded in the plug-in (ISY-JS in my case), or is this not supported by Homebridge?
Thanks and regards, Mike

these notifications are only available for security devices like locks and door/window openers.
not for regular devices like lights and switches.

Thanks for the info.  Its too bad that is the case.  Notifications when a door is opened, etc., are quite useful.

will be in ios 10.2 :-) !

Duh!  It's there in the beta.  Did not notice it until now.  Thanks!

Reverse of the question - is there a way to (mass) disable the notifications, not though the Home app though, but maybe through some flag in a config? Maybe an overriding default of off? I am running the envisalink plugin and all my windows and doors have notifications turned on and I would like to not have to manually turn each one off every time (like setting up my wife's phone).


快捷键冲突无法修改

We're aware of this enhancement opportunity! Closing the ticket to avoid duplicates.

You can edit the shortcut. See this reply: https://github.com/mintlify/writer/issues/34#issuecomment-1115004816


mobile: Add the stats prefix to the ADS xDS registration

The stats_prefix field in the GoogleGrpc config has a proto validation rule that the field must be populated and have a length of at least 1.
This change adds the stat_prefix field whenever the ADS builder API is used, and adds tests to validate it.
Lastly, this change makes the mobile_compile_time_options CI job turn on proto validation, so we can ensure we never commit invalid proto, even though mobile normally disables proto validation for binary size purposes. The default value for the PVG template is the empty string (https://github.com/bufbuild/protoc-gen-validate/blob/38260ee45796b420276ac925d826ecec8fc3e9a8/bazel/BUILD#L11), so the mobile_compile_time_options sets template-flavor to the empty string instead of the default nop for mobile.
Signed-off-by: Ali Beyad<EMAIL_ADDRESS>

/retest


Ember.HTMLBars._registerHelper deprecated

When updating to ember 2, this is now deprecated
Ember.HTMLBars._registerHelper

Can you post the stack trace.  Afaik everything was converted to the new stateful helpers.  I will double check when I get near a computer.  Are you on latest?

Okay, I will look.  Likely an issue with the condition not being satisfied gt('2.0.0') I would expect to be truthy against 2.0.2 but it's probably not for you.  Will patch soon.

Super confused by this, can you validate you are on the latest version of ember moment?  I can't reproduce.

  "version": "3.6.2",

3.6.3 should fix this.  I wasn't able to reproduce it, but I changed the version detection.

awesome thanks @jasonmit


Fixed bug when smartnode list changes during request

During certain time sensitive updates, retrieving the smartnode list could change during the call, possibly causing a crash.  Protected from the possible crash.

The crash can occur if the result is resized to larger than its actual size.  Some callers retrieve the last element of the vector, which is a null pointer, and dereference it, causing the crash.


Zlabel Position Error

I just run fc8 from the example dir. I don't know why the position of Z-label is wrong ...

I modify the zlabels in file "RightBandedBox.sty" and it works for me.

You are probably using Latex 2018, right ?
Changing pos=0 to pos=0.5 solved the problem for me.
\tikzstyle{depthlabel}=[pos=0.5,text width=14*\z,text centered,sloped]

I met the same problem using MacLatex. The two solutions above failed together. Can someone help me?

close

Anyone knows which parameter can I modify to hide the labels ?

Anyone knows which parameter can I modify to hide the labels ?

Modify the zlabels in file "RightBandedBox.sty" works for me ;)
@Btrox148 Try to hide the labels removing their text:
xlabel={{"64","64"}},ylabel=224,zlabel=,fill=...

\tikzstyle{depthlabel}=[pos=0,text width=14*\z,text centered,sloped]       in  RightBandedBox.sty ...
Changing pos=0 to pos=0.5
That works for me.

You are probably using Latex 2018, right ? Changing pos=0 to pos=0.5 solved the problem for me.
\tikzstyle{depthlabel}=[pos=0.5,text width=14*\z,text centered,sloped]

I change `\tikzstyle{depthlabel}=[pos=0,text width=14*\z,text centered,sloped]  ` to `\tikzstyle{depthlabel}=[pos=0.5,text width=14*\z,text centered,sloped] ` in Box.sty(or RightBandedBox.sty ), and this solved the problem for me.


fix: remove extra spaces in social media prompts

This update removes unnecessary additional spaces found in the social media prompt strings for Facebook, Twitter, Instagram, and LinkedIn in the ai.ts file. These changes ensure consistency in formatting.

amazing thanks :)


progid:DXImageTransform causes error on ios

[x] I'm reporting a bug, not asking for help
[x] I've looked at the documentation to make sure the behaviour is documented and expected
[x] I'm sure this is a Leaflet code issue, not an issue with my own code nor with the framework I'm using (Cordova, Ionic, Angular, React…)
[x] I've searched through the issues to make sure it's not yet reported
There is a pull request that fixes this issue, but it has been closed without merge: https://github.com/Leaflet/Leaflet/pull/4122/commits/0a2a736d57eee2308922d1a4cfdd57984c87add8

How to reproduce

Leaflet version I'm using: 1.0.1
Browser (with version) I'm using: Safari on ios (9.3)
OS/Platform (with version) I'm using: ios (9.3)
include a map in an ios build. In this case it is an ionic application
open to see the following:

What behaviour I'm expecting and which behaviour I'm seeing
No warnings
The above pullrequest fixes it.

Duplicate of https://github.com/Leaflet/Leaflet/pull/4977, https://github.com/Leaflet/Leaflet/pull/4122.
Besides, that's an error, not a warning. Compatibility for old IEs is more important than warnings in Safari.

Does quoting the line break anything?

Yes. See #4977.

Clear. I only read (and referenced) #4122 thanks for clearing this up.


[Doc] All the user store manager properties should specify the mandatory fields

Type: Improvement
Priority: High
Severity: Minor
Release: wso2is-5.4.0-update1
All the user stores managers under this page have a table which describes the properties and their descriptions. Need another column specifying if this field is mandatory or not. This is really helpful when using admin services as we have to manual configure most of these properties
https://docs.wso2.com/display/IS540/Configuring+User+Stores

Thank you for your contribution!
We are closing this issue since it has not been prioritized for a long time. Chances are that it has already been solved in more recent versions. If not, we will be re-evaluating this when it becomes a priority.


adding GPU caching to reduce init time

Added the caching for OpenVINO and so when we use GPU it won't need to recompile.
https://docs.openvino.ai/latest/openvino_docs_OV_UG_Model_caching_overview.html

Why only GPU? Shouldn't it work for the CPU as well?


Reconsider design decisions

After reaching MVP, it’s a good idea to look through the project one more time to make sure that every crucial decision (e.g. domain objects) is made in the optimal way.

Should we add Core layer?
Should Id be filled on Domain layer (in constructor), Application (in command) or Infrastructure (handled by underlying database system)?
Should we have Created and Updated timestamps in entities?


Scale down control plane not working

Create a cluster with 3 control plane and then scale down to 1 is buggy, need more investigation.

Wonderful! @nasusoba
So we've begin to gain from e2e test!

Seems that after adding etcd.k3s.cattle.io/remove="true" annotation to the node before deleting the Machine, the scaling down of CP could be completed. refer to [master] Add etcd-member-management controller to K3s by Oats87 · Pull Request #4001 · k3s-io/k3s (github.com)
But the node drain is never finished (the machine will be forced to deleted after 10min). Need more investigation on why draining is failed, and if adding the annotation is the official way to remove a node.


Is it support Bookmark feature?

Please anyone tell me how implement bookmark feature to it .

Did you read README?

Thanks for your reply. I read READE.md and sample. I also clone this project to android studio. But, i can not understand that support bookmark feature or not.  But in pdffium, i saw BookmarksTree. So i think its possible.

This is main class from sample https://github.com/barteksc/AndroidPdfViewer/blob/master/sample/src/main/java/com/github/barteksc/sample/PDFViewActivity.java

thanks. but i think, like as foxit reader, page bookmarking feature is not available to it.

how make page swipe-horizontal sound for going to next page?

Is swiping pages related to bookmarking?

no no. its another question. I can not solve those two questions.

So please move second question to separated thread.
You can read bookmarks as it is shown in sample

ok. thanks


test/client_utils.h: out-of-bound access found by Coverity

18        do {
  CID 1408204 (#1 of 1): Out-of-bounds access (OVERRUN)1. overrun-buffer-arg: Overrunning array text of 10240 2-byte elements by passing it to a function which accesses it at element index 20479 (byte offset 40959) using argument 20480.
19            rc = SQLGetDiagRec(type, handle, ++i, state, &native, text, sizeof(text), &len );
20            if (SQL_SUCCEEDED(rc)) {
21                if (!result.empty())
22                    result += '\n';
23                result += std::to_string(i) + ":";
24                result += "[" + toUTF8(state) + "]";
25                result += "[" + std::to_string(native) + "]";
26                result += toUTF8(text);
27            }
28        } while (rc == SQL_SUCCESS);
29
30        return result;

Thanks for the find! Do you have precise steps to reproduce?

I'm not sure it is reproducible.
I ran scan.coverity.com build
It might be false positive


Remove non-ascii character from source

Fixes C4828 warning emitted by Visual C++ compiler using /utf8 or
/validate-charset flag.

A similar fix was applied in 2010 in commit 6b0b95873608.

If you're going to change the comment, I'd rather see a reference to "fpos.operations" rather than the section number. In C++11, that is section <IP_ADDRESS> (instead of <IP_ADDRESS>)

The boost contribution guidelines recommends avoiding drive-by-fixes.
https://svn.boost.org/trac/boost/wiki/StartModPatchAndPullReq#AvoidDrive-byFixes
Do you still want me to amend the pull request with a reference to fpos.operations instead of the section number?

Yes.  Because the section number is out of date, and has been for five years.

Added as separate commit.

Okay, I misunderstood that. Will fix.


feat(wallet): add unspendable utxo observable and store

Context
Allow wallet to set unspendable UTxO set, which won't be present in available UTxO or balance for input selection.
Jira Issue: ADP-1647
Proposed Solution

Add unspendable$ at UtxoTracker and BalanceTracker
Add setUnspendable(utxo: Cardano.Utxo[]) at UtxoTracker to update store values
Filter out unspendable utxo in available$ utxo in UtxoTracker

Important Changes Introduced

UtxoTracker now has unspendableStore and unspendableUtxoSource$ arguments
PersistentCollectionTrackerSubject.next now also sets all store values

LGTM! Could you please also verify that yarn test:e2e from wallet package is still passing? You might need to create a .env with your own secrets to do that

They pass
Test Suites: 5 passed, 5 total
Tests:       7 passed, 7 total


Where to put static files?

Thanks for your simple yet cool sgg generator.
I dont have a clue on how to use static files in minissg. Is this feature exists or still in development?
One thing i notice is when we put static files in public folder, on every build, it will get removed.

Thank you @lakuapik
Here is the site on how to install and where put your files.
mini ssg website
Take a look at point nr. 3a,
Your static files live in dev/pages/
example: dev/pages/index.html or dev/pages/about.html , etc..
Scroll through the bottom of that link, you'll find the general folder structure
Let me know if something not clear

Thanks @hilmanski
I thought the dev/pages folder just for html files only.
IMHO, would it be better if there is dedicated folder to store static files (css/js/img) rather than put into dev/pages folder?

I've seen some SSG put their "static files" in separate folder.
At first I did separate assets folder and pages , but after some consideration, I bring them back together.
Mini SSG is different from typical SSG, where they have 'dynamic' and 'static' sites,
Mini SSG is currently focusing on simplicity to prevent your write DRY HTML files (not to write dynamic content like blog), that's the reason I make a same entry location.
Thanks for your input. It might be change in the future.
BTW, have you tried it, how was your experience?

Hi @lakuapik
I did change the folder structure today, with version >= 0.2 of mini SSG
all static folder and files move/live in '/dev/static' folder.
So if you have any css, js, sitemap.xml etc... you can put it there.
thanks for your input


docs(tabs): add note for core bug that breaks md-tab-nav-bar

add info to docs to avoid more people hitting this bug
there have been quite a few reports about this recently
it is not obvious to users that it is a core bug and not a bug in their code
Relates to #1967

This specifically relates to the following https://github.com/angular/material2/issues/1967#issuecomment-271090596.
If you would like me to add the workaround to the docs (perhaps for users that won't be soon updating to the Angular 2.4.x release that eventually includes https://github.com/angular/angular/pull/13273), then please let me know.

Thank you @splaktar

I'm hesitant to add to the docs something ephemeral. I'll escalate the issue with the core team so that it should just go away soon.

No problem. Just know that multiple people each day are trying out material2 and they may be running into this issue (since 2 months ago) and the component may be one of the first used in their app.
Their initial experience in trying it out (even in beta) is likely an important aspect of them deciding to use the library or go with something else.
To most people, this failure doesn't appear to be a bug in the core, but rather the component or their implementation of it.


Improve transaction fetching

fixes #1475

@Liubov-crypto ensure that every transactions is loading and everything transaction related is working properly.

In general LGTM, except that the wallet is very slow and doesn't load all transactions.

if I  switch the wallet from the test network to the main network, then the wrong balance of tokens is showed up:

Should be:

To see the maximum number of transactions, I need to scroll the list of transactions to the maximum down, otherwise I will not see transactions for the previous year.
The wallet is still slow and when the user scrolls fast, the list of transactions may be visible with breaks.


Add partial autocorrect support for Lint/LiteralAsCondition

Makes progress on #12840.
Before submitting the PR make sure the following are checked:

[x] The PR relates to only one subject with a clear title and description in grammatically correct, complete sentences.
[x] Wrote good commit messages.
[x] Commit message starts with [Fix #issue-number] (if the related issue exists).
[x] Feature branch is up-to-date with master (if not - rebase it).
[x] Squashed related commits together.
[ ] Added tests.
[x] Ran bundle exec rake default. It executes all tests and runs RuboCop on its own code.
[x] Added an entry (file) to the changelog folder named {change_type}_{change_description}.md if the new code introduces user-observable changes. See changelog entry format for details.

Tests do not cover the post-loop while case as I was unable to prevent it from also checking post-loop until's, which do not autocorrect as all the literals tested by the spec are truthy literals.

Good point-- I've added that.

The current autocorrection for code which has a redundant conditional check is just to remove the check-- right now nothing is being done to code which has a conditional check that will never pass (i.e. if false, unless true).
Thinking about it, that is unreachable code, and so the autocorrection would be just to delete the code entirely. Or maybe it should fall under the purview of Lint/UnreachableCode?

Thinking about it, that is unreachable code, and so the autocorrection would be just to delete the code entirely. Or maybe it should fall under the purview of Lint/UnreachableCode?

I'd say - Lint/UnreachableCode. It's good to keep cop focus relatively narrow.

Ok, I'll handle that cop in a second PR.

Although, implementing this further, it does seem to make more sense to have the autocorrect logic in the same place-- right now I'm just raising an offense to maintain behaviour, but the testing and the logic setup are much better suited here than they are in Lint/UnreachableCode, even if the goals of the cops line up a little less.
As it stands I'll keep things as they are, but unless anyone has strong objections I'll probably add autocorrect for if false and the like in a few days here.


keep original width

The default setting resized the gif. I don't see a button to let it be the original width or just not change the width. I would expect things not to get changed unless I've actively clicked anything. I don't know what the best UI would be, but perhaps leave numbers at the original values on opening files?

Yes, keeping original size by default is important. Also it would be great if leaving us a way to save the preferences, such as fps, start/end frame, etc.


Add a test runner to run tests for multiple components

Right now, we can only run one component test at a time. Example:  node tests/counter.js
It would be great to have a test runner, so can run multiple components test file at a time.
Simplest solution would be -
const files = process.argv.slice(2);

const cp = require("child_process");

// Load each file using `require`
files.forEach((file) => {
  cp.fork(file);
});

Then we can run multiple components test with - node test-runner.js ./tests/*.test.js
In addition, it would be nice to collect all the stats from all the test and then show it all together.

Added: https://github.com/totaljs/flowstreamcomponents/commit/42991f9c0002483fbba044615a10b91357440098
More info: https://github.com/totaljs/flowstreamcomponents#run-unit-test-for-all-tests


[$500] Android-BA-Tapping connect online with plaid shows 2 spin circles loading

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

**Version Number:**1.4.6-1
Reproducible in staging?: Y
Reproducible in production?: Y
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by: Applause - Internal Team
Slack conversation:
Action Performed:

Launch app
Tap profile icon
Tap Workspaces
Tap on a Workspace
Tap Bank account
Tap "connect online with plaid"

Expected Result:
When user taps "connect online with plaid", single spinner loading in the page must be shown
Actual Result:
When user taps "connect online with plaid", double spinner can be seen in the page loading for few seconds
Workaround:
Unknown
Platforms:

Which of our officially supported platforms is this issue occurring on?

[x] Android: Native
[ ] Android: mWeb Chrome
[ ] iOS: Native
[ ] iOS: mWeb Safari
[ ] MacOS: Chrome / Safari
[ ] MacOS: Desktop

Screenshots/Videos
Add any screenshot/video evidence

https://github.com/Expensify/App/assets/78819774/b346c674-f510-4bd8-8f77-3044fe45c8be
View all open jobs on GitHub
Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~0196db5598b3527ce7
Upwork Job ID:<PHONE_NUMBER>315976192
Last Price Increase: 2023-11-30

Proposal
Please re-state the problem that we are trying to solve in this issue.
Android-BA-Tapping connect online with plaid shows 2 spin circles loading
What is the root cause of that problem?
The problem is related to the display of components
Since they are displayed in parallel
There are cases when the condition for the loader and the condition for PlaidLink are fulfilled simultaneously
https://github.com/Expensify/App/blob/ee7d5dc8d8c6d8706564e1dee685b093f9f4baa3/src/components/AddPlaidBankAccount.js#L188-L227
And that's why we see 2 loaders
What changes do you think we should make in order to solve the problem?
Instead of using && for each condition
We can refactor this component
To use if / else
So that when we have PlaidLink available, we will disable the loader
What alternative solutions did you explore? (Optional)
NA

@akinwale would love your thoughts on the proposals.

I suggest going with @ZhenjaHorbach's proposal since a refactor will result in clearer, more readable code making it easier to understand return paths.
🎀 👀 🎀 C+ reviewed.

📣 @ZhenjaHorbach 🎉 An offer has been automatically sent to your Upwork account for the Contributor role 🎉 Thanks for contributing to the Expensify app!
Offer link Upwork job Please accept the offer and leave a comment on the Github issue letting us know when we can expect a PR to be ready for review 🧑💻 Keep in mind: Code of Conduct | Contributing 📖

PR will be ready today or tomorrow

@akinwale @ZhenjaHorbach Based on the comment from the QA here the issue did not get resolved on Desktop. Would you be able to take a look into this one?

That is apparently it so we are good

@Beamanator and @akinwale - is this correct? If so, I can pay out once https://github.com/Expensify/App/issues/33890 is deployed at $250 instead.

Hmm actually, @marcaaron removed the deployblocker. I'm going to pay this out as normal.
Payment Summary:
@akinwale paid $500 here (Reviewer)
@ZhenjaHorbach paid $500 here (Contributor)

Just waiting on @akinwale to complete the checklist.

BugZero Checklist: The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed:

[x]  [@akinwale] The PR that introduced the bug has been identified. Link to the PR:
[x]  [@akinwale] The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake. Link to comment:
[x]  [@akinwale] A discussion in #expensify-bugs has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner. Link to discussion:

Not a regression. This is a specific case that was not handled in the code.

[x]  [@akinwale] Determine if we should create a regression test for this bug.
[x]  [@akinwale] If we decide to create a regression test for the bug, please propose the regression test steps to ensure the same bug will not reach production again.

Regression test steps

Launch the Expensify app on Android
Tap on the profile picture and navigate to Workspaces
Select any workspace without a bank account, or create a new workspace if none exist
Select Bank account
Tap "Connect online with Plaid"
Verify that only one loading indicator is displayed during the loading process

Do we agree 👍 or 👎?


feat: show no internet card when there is no internet

fixes #145

@iamareebjamal PR updated. Please review