Build Error while installing cutorch

Hi,
I'm facing build error while installing cutorch. Can someone help?
root@deepmask-1:/home/deepmask# luarocks install cutorch
Installing https://raw.githubusercontent.com/torch/rocks/master/cutorch-scm-1.rockspec...
Using https://raw.githubusercontent.com/torch/rocks/master/cutorch-scm-1.rockspec... switching to 'build' mode
Cloning into 'cutorch'...
remote: Counting objects: 229, done.
remote: Compressing objects: 100% (183/183), done.
remote: Total 229 (delta 63), reused 88 (delta 44), pack-reused 0
Receiving objects: 100% (229/229), 241.20 KiB | 0 bytes/s, done.
Resolving deltas: 100% (63/63), done.
Checking connectivity... done.
Warning: unmatched variable LUALIB
jopts=$(getconf _NPROCESSORS_CONF)
echo "Building on $jopts cores"
cmake -E make_directory build && cd build && cmake .. -DLUALIB= -DLUA_INCDIR=/root/torch/install/include -DCMAKE_CXX_FLAGS=${CMAKE_CXX_FLAGS} -DCMAKE_BUILD_TYPE=Release -DCMAKE_PREFIX_PATH="/root/torch/install/bin/.." -DCMAKE_INSTALL_PREFIX="/root/torch/install/lib/luarocks/rocks/cutorch/scm-1" && make -j$jopts install
Building on 4 cores
-- The C compiler identification is GNU 5.4.0
-- The CXX compiler identification is GNU 5.4.0
-- Check for working C compiler: /usr/bin/cc
-- Check for working C compiler: /usr/bin/cc -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Detecting C compile features
-- Detecting C compile features - done
-- Check for working CXX compiler: /usr/bin/c++
-- Check for working CXX compiler: /usr/bin/c++ -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- Found Torch7 in /root/torch/install
CMake Error at /usr/share/cmake-3.5/Modules/FindCUDA.cmake:617 (message):
Specify CUDA_TOOLKIT_ROOT_DIR
Call Stack (most recent call first):
CMakeLists.txt:7 (FIND_PACKAGE)
-- Configuring incomplete, errors occurred!
See also "/tmp/luarocks_cutorch-scm-1-5744/cutorch/build/CMakeFiles/CMakeOutput.log".
Error: Build error: Failed building.

HI,
Do you have CUDA properly installed?
If so, you may have installed it in a non standard path and you want to specify where it is with CUDA_TOOLKIT_ROOT_DIR.

Cuda is not installed on my system. I have tried installing using the command. However, it's giving me below error. can someone please help me? I want to work with deepmask and sharp mask. I heard that it works with CUDA version 7.0 or lower only..I'm not sure.
root@deepmask-1:~# nvcc --version
The program 'nvcc' is currently not installed. You can install it by typing:
apt install nvidia-cuda-toolkit
root@deepmask-1:~# apt install nvidia-cuda-toolkit
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:
The following packages have unmet dependencies:
nvidia-cuda-toolkit : Depends: nvidia-profiler (= 7.5.18-0ubuntu1) but it is not going to be installed
Depends: nvidia-cuda-dev (= 7.5.18-0ubuntu1) but it is not going to be installed
Recommends: nvidia-visual-profiler (= 7.5.18-0ubuntu1) but it is not going to be installed
E: Unable to correct problems, you have held broken packages.
root@deepmask-1:~#


README file creation

version 1.0 is complete.
will amend as we progress - would be nice to have a little "what we learned" quote from each of us

awaiting comments from team


[RFC] Providing viewport tag by default

Feature request
Is your feature request related to a problem? Please describe.
By default Next.js doesn't add a <meta name="viewport"> to the HTML document, meaning that browsers default to a behavior that you probably don't want in most cases because of media queries behaving unexpectedly, so @rauchg suggested adding <meta name="viewport"> by default.
Describe the solution you'd like
It's probably a good idea to mirror the AMP viewport tag:
<meta name="viewport" content="width=device-width,minimum-scale=1,initial-scale=1" />

However I'd like to collect some more feedback around this.

That seems like a sensible default to me. Will it still be possible to use a custom viewport tag?

Will it still be possible to use a custom viewport tag?

Yes definitely!


HMR changes not reflecting on android emulator with NativeScript 8.0.0

these are packages
"dependencies": {
"@angular/animations": "~11.2.7",
"@angular/common": "~11.2.7",
"@angular/compiler": "~11.2.7",
"@angular/core": "~11.2.7",
"@angular/forms": "~11.2.7",
"@angular/platform-browser": "~11.2.7",
"@angular/platform-browser-dynamic": "~11.2.7",
"@angular/router": "~11.2.7",
"@nativescript/angular": "~11.8.0",
"@nativescript/core": "~8.0.0",
"@nativescript/theme": "~3.0.1",
"reflect-metadata": "~0.1.13",
"rxjs": "~6.6.7",
"zone.js": "~0.11.4"
},
"devDependencies": {
"@angular/compiler-cli": "~11.2.7",
"@nativescript/android": "8.0.0",
"@nativescript/types": "~8.0.0",
"@nativescript/webpack": "beta",
"@ngtools/webpack": "~11.2.6",
"typescript": "~4.0.0"
},
Describe the bug
I am new to the native script. I have created a new app ns create name --ng. Throwing error with starting emulator when I start the app by  ns run android.
If I run the emulator manually and then execute ns run android there is no error and the app is installed on the android emulator however it's not powering up and it's not syncing with changes in VS Code.
To Reproduce
ns run android
Expected behavior
I should be able to see the changes on the emulator (sync up with vs code changes)
Additional context
windows 10, Android studio emulator (system-images;android-30;google_apis;x86 )

same


Compute NotebookIndex to Diagnostics on stdin

Summary
This PR fixes the bug where the NotebookIndex was not being computed when
using stdin as the input source.
Test Plan
TODO

Current dependencies on/for this PR:

main

PR #7662

PR #7663   👈

This comment was auto-generated by Graphite.


[Web Portal] Tweak job submission page layout

scrollbar position
column's min width

Coverage remained the same at 51.225% when pulling dbeb97a901819a6848c0c03e3295b6c9e6d3a7af on qinsu/portal/layout into 8c46e2a05e0489a0693aec7c97a8fa33cce772e8 on pai-0.14.y.

Coverage remained the same at 51.225% when pulling dbeb97a901819a6848c0c03e3295b6c9e6d3a7af on qinsu/portal/layout into 8c46e2a05e0489a0693aec7c97a8fa33cce772e8 on pai-0.14.y.


precompute List.map

The implementation should be straight-forward (similar to Array.prototype.map), but may require we check for whether @algebraic/collections is defined. It may make more sense to put this in @algebraic/collections (but that could be weird with circular dependencies).

Fixed: https://github.com/runkitdev/parallel-branch/commit/0833eda06f77da6d2dcdb1b5312e891c6e3409fc


multi-root-workspace support for language server features

VSCode supports the idea of having a workspace with multiple root-directories, which are allowed to be located at totally different file system locations. Currently we seem to use a deprecated interface, which only gives the first added root directory and not all of them.
e.g:

This is a multi root workspace where i added both root dirs NC and test.
When trying "Go To Definition" on L test.ncit doesnt find any because our search is based on the root path of the workspace which is currently only one and therefore always the first one NC. This doesn't contain any test.nc so none is found.
Solution: Search for newer vscode interface to get all of the root-dirs and include all of them in our searching process for the language server features.

This comes with the following question. Let's assume we have our test.nc not in the test but in the NC root-dir. If executing "Go To Definition" on the previously shown L test.nc within subPrograms.nc should we find the program within the NC root-dir or shouldn't we because it is not found in the used root-dir?
If yes, how should the priorisation process look like when the filename can be found in both/multiple root-dirs?

This comes with the following question. Let's assume we have our test.nc not in the test but in the NC root-dir. If executing "Go To Definition" on the previously shown L test.nc within subPrograms.nc should we find the program within the NC root-dir or shouldn't we because it is not found in the used root-dir? If yes, how should the priorisation process look like when the filename can be found in both/multiple root-dirs?

For this we decided to just show all possible found definitions so the user can pick which definition they want to jump to. This is necessary due to nc-configurations which we can't know in our extension.


Packages: Move dashboard to new structure

Feature Description

[ ] Move code from /assets/src/dashboard to /packages/dashboard/src/
[ ] Update imports where necessary.
Use @web-stories-wp/... imports for anything that is already a package, relative imports for everything else.
[ ] Create /packages/dashboard/package.json referencing its dependencies
[ ] Create /packages/dashboard/README.md with short documentation.

Alternatives Considered

Additional Context

Do not alter or remove anything below. The following sections will be managed by moderators only.
Acceptance Criteria

Implementation Brief

Related: https://github.com/google/web-stories-wp/issues/8614


Classic Flow - Redirection to app instead of classic web

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: 9.0.64-0
Reproducible in staging?: Y
Reproducible in production?: Y
Issue was found when executing this PR: https://github.com/Expensify/App/pull/52526
Email or phone of affected tester (no customers<EMAIL_ADDRESS>Issue reported by: Applause Internal Team
Action Performed:

Navigate to staging.expensify.com
Select 10+ employees and input new gmail
Open OD LHN and tap on support and tap on concierge
After being navigated to NewDot tap on settings > Switch to Expensify classic > Tap on take me there

Expected Result:
App redirects to Expensify Classic on mWeb
Actual Result:
App redirects to Expensify Classic app
Workaround:
Unknown
Platforms:

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

Screenshots/Videos
https://github.com/user-attachments/assets/517543ac-f9de-40ed-990f-45d713ada615

View all open jobs on GitHub

Closaroooo


Migrate from batch/v1beta1 to batch/v1

The batch/v1beta1 API version of CronJob will no longer be served in v1.25, we should migrate to batch/v1

Duplicated from #2408


⚠ Bofrost.lu has degraded performance

In 0b0058e, Bofrost.lu (https://www.bofrost.lu) experienced degraded performance:

HTTP code: 200
Response time: 1185 ms

Resolved: Bofrost.lu performance has improved in c6f1dda.


New release v0.0.2

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.2 out of 3 committers have signed the CLA.:white_check_mark: SIthuralde:white_check_mark: guidomodarelli:x: ithurraldeYou have signed the CLA already but the status is still pending? Let us recheck it.


Allow creation of streaming device in daemon mode + don't register another device when spawning TUI

Is your feature request related to a problem? Please describe.
Currently if I spawn spotify_player in daemon and then launch another instance in TUI mode - two streaming devices in total are being registered - both with the same name but different IDs
If I set enable_streaming to false TUI doesn't register new streaming device but then same happens to daemon mode.
Describe the solution you'd like
I would like to use spotify_player in daemon mode akin to spotifyd and let it register as streaming device.
Then I would like to use spotify_player in TUI mode from time to time in order to control what is being played.
I tend to control spotify device with Raycast plugin and thus I don't need TUI to be opened 100% of the time.
I use spotify_player in --daemon mode so it registers itself as streaming device.
But from time to time when I want to change playlist I use TUI mode - I would expect TUI to NOT register another streaming device
I wonder if I miss some option to allow such setup or it isn't possible right now.

I don't think it's possible now to run TUI with streaming disabled beside setting enable_streaming=false.  Should be easy to add a new cli option to disable streaming when running the TUI. Maybe we can remove enable_streaming as a config option in favours of cli option as it's more flexible.


Found an interesting bug related to synchronisation of threads

Lately we have been experiencing an interesting bug in go-threads.
The problem occurs when we have a lot of records and we are trying to synchornize them.
In our application happens as follows:

Device A has thread with 0 records and it tries to get a lot of records from Device B regarding Log B (for example 1000)
At the same time Device A requests Head of Log B through GetRecord effectively getting it through Bitswap. As a result of this the Head of Log B is added to Blockstore.
When Device B returns 1000 records to Device A, Device A tries to put them using putRecords. So it checks them using isKnown which looks into blockstore and sees that we already have the Head of Log B (which we got through bitswap), so it decides not to proceed with saving the records.
So the Head of Log B in Device A stays as Undef as we haven't updated it.
So ExchangeEdges will see that we have different heads and will try to get records again. Thus we will have an infinite loop of unsuccesfull record updates.

I tried to reproduce this isKnown problem on testground:

First instance creates a thread and adds 200 records
Second instance starts after (so it doesn't receive anything through pubsub or push) and pulls the thread thus calling get records.
At the same time Second instance tries to get the head through bitswap using GetRecord.
Because Second instance receives head earlier than the batch of 200 records it will effectively skip adding them and thus will not update its head.

The test is not of super good quality, but at least it sometimes works :-) Feel free to ping me in case I missed something.
https://github.com/mcrakhman/go-threads/tree/sync-bug-demonstration
To run the test type testground run composition --wait -f sync-bug-exec.toml.
When the test stops running you will see some prints in the console like:
got log 12D3KooWAhDczANHAuX8JgqDofkmhZsdftzfS9Q7GTt3kvqDECbB with head b (see GetHeads method)
You can observe different behaviour in case there will be not 200 but 3 records. In this case the log of First instance will be in sync with log of Second instance.

Does this sound familiar, given your recent tests using test ground @merlinran ?

At the same time Device A requests Head of Log B through GetRecord effectively getting it through Bitswap. As a result of this the Head of Log B is added to Blockstore.

IIUC what triggers this bug is that Device A gets the log head via a 3rd party channel and calls GetRecord before the records being synced (I tried the same when drafting the first Testground test, that's why SharedInfo.LogHead exists but was not used!). It's probably not an initially envisioned use case of go-threads, but definitely a legit one.
What if there's a new API call so Device A can explicitly tell go-threads that this is the log head so the data structure gets set properly? Far from an elegant solution but it introduces no performance penalty.

What if there's a new API call so Device A can explicitly tell go-threads that this is the log head so the data structure gets set properly? Far from an elegant solution but it introduces no performance penalty.

Can you elaborate please?
What I initially thought. That as far as I understand SetHead preserves the invariant that before the head there are no gaps in the records. Therefore we can introduce some kind of counter just for the head. Obviously because we set new head just after the previous one we can always maintain the counter just by incrementing it every time we set new head.
Thus if every log has a counter for its head we can easily compare them (at the time we get records) to see if we need to accept more records and how many records should be between the heads. It seems it would be easy to implement such a solution if I am not mistaken.

Sorry my understanding of the codebase is still far from complete, and my proposal simply breaks the invariant of calling SetHead which would cause more headaches.
Having the counter for log depth sounds like a brilliant idea! Naive question: how can a peer get the expected value of the counter for a log? Does it mean that each record brings the counter?

Yes, the log depth counter is what we had in mind for our vector clock proposal exactly. I'm a big fan of this simple feature, because it actually buys us a lot of features in terms of peer synchronization beyond just this bug here. It would require an update to the head data structure, which, while minimal, would likely require some thought. Now is a good time to do this though, as we already have some breaking changes in the pipeline.

Since only one peer is able to write to a given log, if you get a head from a peer, you know that that head counter value is correct (as far as that head record is concerned). This also means you can compare your head counters with another peer's head counters to get all the semantics that come with vector clocks.

Do you think it makes sense for me to draft some proposal, so we would look at it on Thursday? And maybe you would already give me some comments

That would be fantastic!

I reference the PR here (https://github.com/textileio/go-threads/pull/531), it is not finished and a lot of the stuff there is not final. The only thing which is implemented is the get records logic which fixes the bug. I didn't have time to check other things yet (including to properly test it, except for the testground test which is working for me), I will do that after our discussion on Thursday.

So here are some things to note:

I still need to update AddHeads method which should be easy. Though I see that we don't use multihead logs anywhere. Is that a real use case?
We should probably do a small migration to add head counters for the logs which currently don't have them (for example if a person had an older version). Haven't implemented that though.
Initially I added the counter to push record, for example if a somebody creates a record we obviously know the counter for that record and thus we can send it. In some cases it is impossible though (for example if we AddRecord), so we can just send a default value. Should we use this logic for a push record or should we omit it altogether?
Not sure if I did a proper backward compatibility checks everywhere (if counter value is zero we use old isKnown checks)


[cxx-interop] Instantiate C++ class templates from Swift

This PR makes it possible to instantiate C++ class templates from Swift. Given a C++ header:
// C++ module `ClassTemplates`
template<class T>
struct MagicWrapper {
  T t;
};

struct MagicNumber {};

it is now possible to write in Swift:
import ClassTemplates

func x() -> MagicWrapper<MagicNumber> {
  return MagicWrapper<MagicNumber>()
}

This is achieved by importing C++ class templates as generic structs, and then when Swift type checker calls applyGenericArguments we detect when the generic struct is backed by the C++ class template and call Clang to instantiate the template. In order to make it possible to put class instantiations such as MagicWrapper<MagicNumber> into Swift signatures, we have created a new field in StructDecl named TemplateInstantiationType where the typechecker stores the BoundGenericType which we serialize. Deserializer then notices that the BoundGenericType is actually a C++ class template and performs the instantiation logic.
Depends on https://github.com/apple/swift/pull/33420.
Progress towards https://bugs.swift.org/browse/SR-13261.
Fixes https://bugs.swift.org/browse/SR-13775.

This PR depends on https://github.com/apple/swift/pull/32950.

@swift-ci please test

@swift-ci please test

Build failed
Swift Test OS X Platform
Git Sha - 45c63aa2b14a998fae298340038c588295a6a60f

Build failed
Swift Test Linux Platform
Git Sha - 45c63aa2b14a998fae298340038c588295a6a60f

@swift-ci please test

@swift-ci please test

Build failed
Swift Test Linux Platform
Git Sha - 69ae2439706a2c03b385d6cd987a387b9601b200

@swift-ci please test

@swift-ci please test

Build failed
Swift Test OS X Platform
Git Sha - 69ae2439706a2c03b385d6cd987a387b9601b200

@swift-ci please test

Build failed
Swift Test Linux Platform
Git Sha - 69ae2439706a2c03b385d6cd987a387b9601b200

Build failed
Swift Test OS X Platform
Git Sha - 69ae2439706a2c03b385d6cd987a387b9601b200

@swift-ci please test

Build failed
Swift Test Linux Platform
Git Sha - be2e706371902be6ef1c7943c476bf73e218b5e1

Build failed
Swift Test OS X Platform
Git Sha - be2e706371902be6ef1c7943c476bf73e218b5e1

@swift-ci please test

Build failed
Swift Test Linux Platform
Git Sha - 1ca883bd84f73332e065870ef090bc5f61a39e13

Build failed
Swift Test OS X Platform
Git Sha - 1ca883bd84f73332e065870ef090bc5f61a39e13

@swift-ci please test

Build failed
Swift Test OS X Platform
Git Sha - 9eb0a1fa35881b7cca100d5fa894649e3d2855af

Build failed
Swift Test Linux Platform
Git Sha - 9eb0a1fa35881b7cca100d5fa894649e3d2855af

Could you please rewrite the history into self-contained commits with commit messages that describe what the change in each commit is?

Could you please rewrite the history into self-contained commits with commit messages that describe what the change in each commit is?

I generally squash and merge when merging the PR, so at the end there's just one commit with the description being the description of the PR. This PR got out of hand with commits though so I'll squash them now too :)

Thanks so much for the first round of comments!

@swift-ci please test

@swift-ci please test windows platform

@swift-ci please test

Here's a test case that crashes:
template<class...>
class Foo;

template<>
class Foo<> {
  enum Maybe { No, Yes };
};

But, I think it would be fair to fix that in another patch.

@swift-ci please test

Build failed
Swift Test Linux Platform
Git Sha - 7feb939cdd287ee01187394d782c41ebfcf40d52

Build failed
Swift Test OS X Platform
Git Sha - 7feb939cdd287ee01187394d782c41ebfcf40d52

@swift-ci please test

Build failed
Swift Test OS X Platform
Git Sha - 156f2ed1215db957c8a1dc5a65047d4e68fc4645

@swift-ci please test

Build failed
Swift Test OS X Platform
Git Sha - 5f2a2a559dbc8b388de28081f209f998269cabbc

@swift-ci please test

@swift-ci please test.

@swift-ci please test

Addressed the comments, ptal :)

@swift-ci please test.

@swift-ci please test.

Build failed
Swift Test OS X Platform
Git Sha - e9a44d42d3e08d291f18cb9a67104de07f8021f3

Build failed
Swift Test OS X Platform
Git Sha - e9a44d42d3e08d291f18cb9a67104de07f8021f3

Build failed
Swift Test Linux Platform
Git Sha - e9a44d42d3e08d291f18cb9a67104de07f8021f3

Build failed
Swift Test Linux Platform
Git Sha - e9a44d42d3e08d291f18cb9a67104de07f8021f3

@swift-ci please test.

@swift-ci please test.

Build failed
Swift Test Linux Platform
Git Sha - 71a9065231f12cf40dd0682a5c572d2cf84e55cd

Build failed
Swift Test Linux Platform
Git Sha - 71a9065231f12cf40dd0682a5c572d2cf84e55cd

Build failed
Swift Test OS X Platform
Git Sha - 71a9065231f12cf40dd0682a5c572d2cf84e55cd

Build failed
Swift Test OS X Platform
Git Sha - 71a9065231f12cf40dd0682a5c572d2cf84e55cd

@swift-ci please test.

@swift-ci please test.

Build failed
Swift Test OS X Platform
Git Sha - c082a8c9f484837351bb196a16b9108d2c600f03

Build failed
Swift Test OS X Platform
Git Sha - c082a8c9f484837351bb196a16b9108d2c600f03

(Failure on mac came from lldb, not related to this PR)

(Failure on mac came from lldb, not related to this PR)

@swift-ci please test.

@swift-ci please test.

Build failed
Swift Test OS X Platform
Git Sha - 3bfdce6fa595a3681c4d6e76d5da630413a23f5a

Build failed
Swift Test OS X Platform
Git Sha - 3bfdce6fa595a3681c4d6e76d5da630413a23f5a

@swift-ci please test.

@swift-ci please test.

Build failed
Swift Test OS X Platform
Git Sha - ff7cdc3284a1a946cea4d2fa341b3360abfb9e95

Build failed
Swift Test OS X Platform
Git Sha - ff7cdc3284a1a946cea4d2fa341b3360abfb9e95

@swift-ci please test macos platform.

@swift-ci please test macos platform.

@swift-ci please test.

@swift-ci please test.


Get endpoints column popup title from resource

I noticed this was hardcoded. Should come from resource for localizaiton.


C# code sample has invalid variable in preferred domain section

The C# code sample has invalid variable passed to PlacementPolicies.Add() method in Preferred Domain section.
ServicePlacementPreferPrimaryDomainPolicyDescription primaryDomain = new ServicePlacementPreferPrimaryDomainPolicyDescription();
primaryDomain.DomainName = "fd:/EastUS/";
serviceDescription.PlacementPolicies.Add(invalidDomain); // <- should be "primaryDomain" here

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

ID: 06ba51b6-2b88-3bdf-138f-a42b099c215d
Version Independent ID: b17952ec-0075-18fc-1f49-4044b2c07a75
Content: Service Fabric Cluster Resource Manager - Placement Policies
Content Source: articles/service-fabric/service-fabric-cluster-resource-manager-advanced-placement-rules-placement-policies.md
Service: service-fabric
Product: unspecified
GitHub Login: @masnider
Microsoft Alias: masnider

@OlegKarasik Thanks for the feedback! We are currently investigating and will update you shortly.

@OlegKarasik thanks for the find! I have made the changes. Once they merge this issue will automatically close.


Single instance continuously failing gRPC connections

We've observed an issue (once while rolling a cf-d, once when experimenting by changing code on a single instance and rolling it) wherein one instance will fail to answer any requests. During this time, its logs will contain a constant stream of gRPC connection failure messages.
Resolution of this condition requires restarting the other instance. This has only been observer to date in a two instance configuration.

Fixed in https://github.com/cloudfoundry/log-cache/commit/3f7228cd5af83dee3bda0008e18e4037d71b25c9
The underlying cause was a deadlock between portions of the meta store.


Create psvpec.txt

@sheltonanton Please rename lib/domains/in/psvpec to lib/domains/in/psvpec.txt

@sheltonanton I am sorry, this request remains unanswered for a while. I have to close it without merging. Please reopen and comment if you have an update regarding the abovementioned issue. Thank you for the understanding!


Remote - SSH extension try to map local port zero

Issue Type: Bug

connect to a remote host specified from ~/.ssh/config
the connection stopped with message "Could not establish connection to "xxx". Illegal argument: port".
With the full log in "OUTPUT" window, I can see the extension try to map remote port 42007 to local port 0, while port 0 is invalid.

SSH Resolver called for "ssh-remote+aliyun"
SSH Resolver called for host: aliyun
Setting up SSH remote "aliyun"
Using commit id "473af338e1bd9ad4d9853933da1cd9d5d9e07dc9" and quality "insider" for server
Install and start server if needed

Welcome to Ubuntu 16.04.4 LTS (GNU/Linux 4.4.0-117-generic x86_64)

Documentation:  https://help.ubuntu.com
Management:     https://landscape.canonical.com
Support:        https://ubuntu.com/advantage
New release '18.04.2 LTS' available.
Run 'do-release-upgrade' to upgrade to it.

Welcome to Alibaba Cloud Elastic Compute Service !
mesg: ttyname failed: Inappropriate ioctl for device
bash: cannot set terminal process group (7824): Inappropriate ioctl for device
bash: no job control in this shell
Found existing installation...
mesg: ttyname failed: Inappropriate ioctl for device
Found running server...

Reminder: You may only use this software with Visual Studio family products,
as described in the license (https://go.microsoft.com/fwlink/?linkid=2077057)

ebaaff07-47c7-4d23-ad0e-65c0dd7d2fc6==42007==
"install" terminal command done
Received install output: ebaaff07-47c7-4d23-ad0e-65c0dd7d2fc6==42007==
Server is listening on port 42007
Spawning tunnel with: ssh  aliyun -N -L localhost:0:localhost:42007
Spawned SSH tunnel between local port 0 and remote port 42007
Waiting for ssh tunnel to be ready
Tunneling remote port 42007 to local port 0
Resolving "ssh-remote+aliyun" to "localhost:0", attempt: 1
Illegal argument: port
Tunnel(42007) stderr: Bad local forwarding specification 'localhost:0:localhost:42007

VS Code version: Code - Insiders 1.34.0-insider (473af338e1bd9ad4d9853933da1cd9d5d9e07dc9, 2019-05-01T00:21:48.884Z)
OS version: Darwin x64 18.2.0
Fetching remote diagnostics for 'SSH: aliyun' failed: Illegal argument: port

System Info

Item
Value

CPUs
Intel(R) Core(TM) i5-5287U CPU @ 2.90GHz (4 x 2900)

GPU Status
2d_canvas: enabledchecker_imaging: disabled_offflash_3d: enabledflash_stage3d: enabledflash_stage3d_baseline: enabledgpu_compositing: enabledmultiple_raster_threads: enabled_onnative_gpu_memory_buffers: enabledrasterization: enabledsurface_synchronization: enabled_onvideo_decode: enabledwebgl: enabledwebgl2: enabled

Load (avg)
3, 3, 3

Memory (System)
16.00GB (0.03GB free)

Process Argv
-psn_0_22820290

Screen Reader
no

VM
0%

Fetching remote diagnostics for 'SSH: aliyun' failed: Illegal argument: port
Extensions: none

Duplicate of https://github.com/microsoft/vscode-remote-release/issues/216


How to set Time out For Particular Action

Am trying to upload a CSV file, It upload file of small size but when am trying to upload large size file it give me TIMEOUT error.
I want to increase my time only for particular method not for all as we can set in application controller.

See wait overtime in readme.


Fix docblock for FileSystemError

This change is a simple fix to the doc block for FileSystemError.  The current doc block seems to reference an old error type that was likely missed as a part of: https://github.com/microsoft/vscode/commit/bf6155555d6276ce479b3cfafaff4f3a62073ef2#diff-4878e8b25d41f2ab7c2715852b1b97aa

cc @jrieken


[feat] Configurable secret path for hasicorp vault

Changelog

Add:
network.yaml configurations for vault can now accept an secret_path option.
This option changes the secret engine used for this vault. If not provided it will default to secret/
For below example the vault will use the secret engine supersecret/

# Hashicorp Vault server address and root-token. Vault should be unsealed.
# Do not check-in root_token
vault:
    url: "vault_addr"
    root_token: "vault_root_token"
    secret_path: "supersecret"

This initial commit doesn't contain any documentation changes because I am unsure of the scope.
Since this is optional, should I add it to the example network.yaml files but comment it out?
# Hashicorp Vault server address and root-token. Vault should be unsealed.
# Do not check-in root_token
vault:
    url: "vault_addr"
    root_token: "vault_root_token"
    # secret_path: "vault_secret_path"

Is there another place it should be refrenced?
Reviewed by
@developer_github_id
Linked issue
#1153

Thanks for this PR. In the sample network.yaml you can add the default path.

done.
Added:
      # Hashicorp Vault server address and root-token. Vault should be unsealed.
      # Do not check-in root_token
      vault:
        url: "vault_addr"
        root_token: "vault_root_token"
        secret_path: "secret"


firecracker-bin, jailer-bin, greengrass-bin: simplify LICENSE path to…

… allow auto-upgrades

/run


removed unnecessary else statements

What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
Cleaner code.
What is the current behavior? (You can also link to an open issue here)
What is the new behavior (if this is a feature change)?
Does this PR introduce a breaking change?
No.
Please check if the PR fulfills these requirements

[ ] The commit message follows our guidelines: https://github.com/angular/angular.js/blob/master/CONTRIBUTING.md#commit-message-format
[ ] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been added / updated (for bug fixes / features)

Other information:

I signed it

Can you please update the commit message to refactor(\$interpolate): remove unnecessary else ?


TileMaps, Sprites YSorting is not working properly

Godot version
4.0 beta 6
System information
manjaro linux
Issue description
I'm making a isometric 2D game, and even with YSort enabled the ysorting doesnt work!
cc @groud
Steps to reproduce

AnimatedSprite2D -> Tileset

AnimatedSprite2D -> AnimatedSprite2D
Minimal reproduction project
MRP.zip

You need to enable Y-sort on the top node. Y-sort only works for common nodes in a hierarchy if they share a root node with Y-sort enabled. Also, you have to set the texture_offset (and Y-sort origin if you need to) on tiles.
https://user-images.githubusercontent.com/6093119/204788724-7f78e7c8-5610-4dfa-81a3-22c1d3dc6203.mp4
The only thing that seems is not working is setting the origin on animated tiles, while it works on normal sprites. But that's another bug which need its own report.
Closing as this is an expected behavior.


tmt tests lint --fix does not process virtual cases correctly

tmt tests lint does not complain about the relevancy and --fix does not fix that in case of a virtual case.
E.g. the test https://github.com/RedHat-SP-Security/tests/tree/master/rsyslog/Regression/bz1223566-RFE-imrelp-does-not-support-binding-to-a-specific

Thanks, simplified reproducer:
==> a.fmf <==
tag: []

==> main.fmf <==
test: echo
relevancy: |
  distro == rhel: False

I'm lazy to file another issue as it can be connected, but if b.fmf is empty file then lint fails with
$ touch b.fmf
$ tmt t lint

  File "/usr/lib/python3.10/site-packages/tmt/cli.py", line 418, in lint_tests
    if not test.lint():
  File "/usr/lib/python3.10/site-packages/tmt/base.py", line 488, in lint
    relevancy = metadata.pop('relevancy', None)
AttributeError: 'NoneType' object has no attribute 'pop'

Looks tmt lint should try to find where 'relevancy' was used and change that file, not final metadata - https://github.com/teemtee/tmt/blob/main/tmt/base.py#L504

If an empty file is specified, tmt t lint looks good now because of https://github.com/teemtee/tmt/pull/1332.
(tmt) huanli@kvm1:foo$ tree -a
.
├── 1197
│   └── b.fmf
├── .fmf
│   └── version
└── main.fmf

2 directories, 3 files
(tmt) huanli@kvm1:foo$ cat main.fmf
test: echo
relevancy: |
  distro == rhel: False
(tmt) huanli@kvm1:foo$ cat 1197/b.fmf
(tmt) huanli@kvm1:foo$ tmt tests ls
/1197/b
(tmt) huanli@kvm1:foo$ tmt t lint
/1197/b
pass test script must be defined
pass directory path must be absolute
pass directory path must exist
warn summary is very useful for quick inspection
pass correct attributes are used

@lukaszachy, with tmt-1.15.0, I failed to reproduce it via your simple reproducer, any idea?
(tmt) huanli@kvm1:foo$ tree -a
.
├── 1197
│   └── a.fmf
├── .fmf
│   └── version
└── main.fmf

2 directories, 3 files
(tmt) huanli@kvm1:foo$ cat main.fmf
test: echo
relevancy: |
  distro == rhel: False
(tmt) huanli@kvm1:foo$
(tmt) huanli@kvm1:foo$ cat 1197/a.fmf
tag: []
(tmt) huanli@kvm1:foo$
(tmt) huanli@kvm1:foo$ tmt tests ls
/1197/a
(tmt) huanli@kvm1:foo$ tmt t lint
/1197/a
pass test script must be defined
pass directory path must be absolute
pass directory path must exist
warn summary is very useful for quick inspection
pass correct attributes are used


corrected error testing function

Changes the checking procedure for error messages (see #133).

@rabernat, could you confirm that this error message is deprecated?
    with pytest.raises(ValueError) as excinfo:
        ax.interp(ds.data_c, "left", boundary="fill")
    assert (
        excinfo.value.args[0] == "`boundary=fill` is not allowed "
        "with periodic axis X."
    )

I could not find this message in the code anywhere.

Codecov Report

Merging #135 into master will increase coverage by 0.32%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master     #135      +/-   ##
==========================================
+ Coverage   87.35%   87.68%   +0.32%
==========================================
  Files           4        4
  Lines         609      609
  Branches      130      130
==========================================
+ Hits          532      534       +2
+ Misses         41       40       -1
+ Partials       36       35       -1

Impacted Files
Coverage Δ

xgcm/comodo.py
90.32% <0%> (+3.22%)
:arrow_up:

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 f9b58ff...20481eb. Read the comment docs.

closed via #136

Sorry I am reinventing all the bug fixes that you already discovered. 🤷♂

Thats ok. I just have to add that using this PR would have been more “atomic“...muhahaha, jk.


[AppConfig] Add Snapshot samples

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


[BUG] Failed to register OIDC Routers with OpenSearch Dashboards Client

What is the bug?
OIDC authentication handlers failed to register with OpenSearch Dashboards (OSD) client randomly after OSD reboots. Due to this reason, OSD users will encounter  Unauthenticated Exception.
Issues is addressed along with PR #1110

@aoguan1990 Can this ticket be closed?

@aoguan1990 Can this issue be closed?
@cwperks Thank you so much for following up on this issue. Issue is addressed by the PR #1110. So close it.


feat(slot-reservations): Add expansionRate parameter to support contract changes

Closes #909.
This is part 2 of a longer list of tasks for slot reservations to prevent PRs from being too large.
Adds expansionRate field to the StorageRequest object, to mirror the object in the contracts.
The CodexClient api module uses a default value of 100, which means that all SPs will be available to reserve slots immediately, when the functionality is finally implemented. It was chosen to provide as little disruption to existing as possible, and may change in the future.
The default value for the REST API endpoint was 60, meaning 60% of the total time before expiry will have all addresses eligible to fill the slot.

Holding off on the expanding window work for now. Can resurrect this PR once the expanding window work is planned.


[bug] Spark Operator fails to create due to karpenter resources

Description
When creating the stack on latest this morning i saw a failure due to the karpenter resources that are created via karpenter_resources_helm_config

[x] ✋ I have searched the open/closed issues and my issue is not listed.

⚠ Note
Versions

Module version [Required]: v1.0.3 (latest)

Terraform version:  v1.9.5

Provider version(s):

provider registry.terraform.io/gavinbunney/kubectl v1.14.0
provider registry.terraform.io/hashicorp/aws v5.70.0
provider registry.terraform.io/hashicorp/cloudinit v2.3.5
provider registry.terraform.io/hashicorp/helm v2.15.0
provider registry.terraform.io/hashicorp/kubernetes v2.32.0
provider registry.terraform.io/hashicorp/random v3.3.2
provider registry.terraform.io/hashicorp/time v0.12.1
provider registry.terraform.io/hashicorp/tls v4.0.6

Reproduction Code [Required]

Steps to reproduce the behavior:
Pull the latest and try to create the spark operator v4 solution

Expected behavior
the stack creates successfully with the ./install.sh script
Actual behavior
The stack failed with the error below while creating the module.eks_data_addons.helm_release.karpenter_resources resources
│ Error: unable to build kubernetes objects from release manifest: [resource mapping not found for name: "spark-memory-optimized" namespace: "" from "": no matches for kind "EC2NodeClass" in version "karpenter.k8s.aws/v1"
│ ensure CRDs are installed first, resource mapping not found for name: "spark-memory-optimized" namespace: "" from "": no matches for kind "NodePool" in version "karpenter.sh/v1"
│ ensure CRDs are installed first]
│
│   with module.eks_data_addons.helm_release.karpenter_resources["spark-memory-optimized"],
│   on .terraform/modules/eks_data_addons/karpenter-resources.tf line 6, in resource "helm_release" "karpenter_resources":
│    6: resource "helm_release" "karpenter_resources" {
│
╵
╷
│ Error: unable to build kubernetes objects from release manifest: [resource mapping not found for name: "spark-vertical-ebs-scale" namespace: "" from "": no matches for kind "EC2NodeClass" in version "karpenter.k8s.aws/v1"
│ ensure CRDs are installed first, resource mapping not found for name: "spark-vertical-ebs-scale" namespace: "" from "": no matches for kind "NodePool" in version "karpenter.sh/v1"
│ ensure CRDs are installed first]
│
│   with module.eks_data_addons.helm_release.karpenter_resources["spark-vertical-ebs-scale"],
│   on .terraform/modules/eks_data_addons/karpenter-resources.tf line 6, in resource "helm_release" "karpenter_resources":
│    6: resource "helm_release" "karpenter_resources" {
│
╵

Additional context
Looks like https://github.com/aws-ia/terraform-aws-eks-data-addons/pull/45 updated the resources to karpenter v1 spec, since the ones in spark operator are still beta i think we just need to update the nodepools/classes.
This can also take care of https://github.com/awslabs/data-on-eks/issues/611 for the spark operator solution 🥳

This is a regression. The karpenter v1 changes should've been applied to all existing blueprints.

Customers can pin the Data addons version to previous tag to work with old Karpenter version.

handled in #683


Using PIR sensors

Add more detailed page for using PIR sensors

Thank you very much!
I do have a small request though. Could you also add information that a more flexible solution can be achieved using PIR usermod? With a few examples?

Yes, this was actually planned as a next step (well, would take some time, though). But my idea was to add to level section (after "Advanced") called Usermods and then make a separate page for each usermod there, not to mix them with integrated WLED functionality. How do you think about that?


[@whatwg-node/server] serverAdapter could not get property instance methods

I develop a Node.js server using graphql-yoga.
graphql-yoga v3.7.1 is using @whatwg-node/server
https://github.com/dotansimha/graphql-yoga/blob/release-1677934258532/packages/graphql-yoga/src/server.ts#L610
But it has this error occurred.
https://github.com/dotansimha/graphql-yoga/issues/2534
I think it might be caused by these codes.
https://github.com/ardatan/whatwg-node/blob/master/packages/server/src/createServerAdapter.ts#L284-L289
Because  I modified<EMAIL_ADDRESS>directly like following code, and checked running correctly.
                        return function (...args) {
                            const returnedVal = serverAdapterBaseObject[prop](...args);
                            if (returnedVal === serverAdapterBaseObject) {
                                return serverAdapter;
                            }
                            return returnedVal;  // <- add this line because it becomes undefined.
                        };

I don't know if It is wrong using or if the code is bad.
Please check it.
To Reproduce Steps to reproduce the behavior:
https://codesandbox.io/p/sandbox/amazing-rubin-34zkkw?file=%2Fsrc%2Fmain.ts
Expected behavior
To get appropriate methods of serverAdapterBaseObject instance.
Environment:
OS: [macOS]
NodeJS: [18.14.2]
@graphql-yoga/* version(s): [3.7.1]
Additional context
https://github.com/ardatan/whatwg-node/pull/380/

Fixed in 0.7.3


Do not clean up types via a regex

This was meant to reduce the clutter on printed terms, but our pretty
printer is now smarter about it.
See also FStarLang/FStar#1869

Hey Clément. Any opinion on this PR? Thanks!

LGTM, thanks!


Switched usage event to 'keydown', as it will capture a string of key…

…s entered via a constant keypress and hold. It also has less of a delay of obfuscating the characters on standard input.
Also made some of the comparison operators strict where necessary (changed == to ===)
The strict comparison operator (===) will compare value and type of the objects being compared.

@terrylinooo any thoughts on this?

@terrylinooo any thouights?


Add function app config to latest Web API

ARM (Control Plane) API Specification Update Pull Request

Tip: overwhelmed by all this guidance? See the Getting help section at the bottom of this PR description.

PR Description
This PR contains the following changes:

Added functionAppConfig definition
Added CreateOrUpdateFunctionApp.json example

PR review workflow diagram
Please understand this diagram before proceeding. It explains how to get your PR approved & merged.

 Click here to see the details of Step 1
Breaking changes review (Diagram Step 1)
If the automation determines you have breaking changes, i.e. Step 1 from the diagram applies to you,
you must follow the breaking changes process.
IMPORTANT This applies even if:

The tool fails while it shouldn't, e.g. due to runtime exception, or incorrect detection of breaking changes.
You believe there is no need for you to request breaking change approval, for any reason.
Such claims must be reviewed, and the process is the same.

 Click here to see the details of Step 2
ARM API changes review (Diagram Step 2)

If this PR is in purview of ARM review then automation will add the ARMReview label.
If you want to force ARM review, add the label yourself.
Proceed according to the diagram at the top of this comment.

 Click here to see the diagram footnotes
Diagram footnotes
[1] ARM review queue (for merge queues, see [2])
The PRs are processed by time opened, ascending. Your PR may show up on 2nd or later page.
If you addressed Step 1 from the diagram and your PR is not showing up in the queue, ensure the label ARMChangesRequested
is removed from your PR. This should cause the label WaitForARMFeedback to be added.
[2] public repo merge queue, private repo merge queue (for ARM review queue, [1])
If you need further help with anything, see Getting help section below.

Purpose of this PR
What's the purpose of this PR? Check all that apply. This is mandatory!

[ ] New API version. (If API spec is not defined in TypeSpec, the PR should have been generated using OpenAPI Hub).
[x] Update existing version for a new feature. (This is applicable only when you are revising a private preview API version.)
[ ] Update existing version to fix swagger quality issues in S360.
[ ] Other, please clarify:

edit this with your clarification

Due diligence checklist
To merge this PR, you must go through the following checklist and confirm you understood
and followed the instructions by checking all the boxes:

[x] I confirm this PR is modifying Azure Resource Manager (ARM) related specifications, and not data plane related specifications.
[ ] I have reviewed following Resource Provider guidelines, including
ARM resource provider contract and
REST guidelines (estimated time: 4 hours).
I understand this is required before I can proceed to the Diagram Step 2, "ARM API changes Review", for this PR.

Additional information

 Viewing API changes
For convenient view of the API changes made by this PR, refer to the URLs provided in the table
in the Generated ApiView comment added to this PR. You can use ApiView to show API versions diff.

Suppressing failures
If one or multiple validation error/warning suppression(s) is detected in your PR, please follow the
Swagger-Suppression-Process
to get approval.

Getting help

First, please carefully read through this PR description, from top to bottom. Please fill out the Purpose of this PR and Due diligence checklist.
To understand what you must do next to merge this PR, see the Next Steps to Merge comment. It will appear within few minutes of submitting this PR and will continue to be up-to-date with current PR state.
For guidance on fixing this PR CI check failures, see the hyperlinks provided in given failure
and https://aka.ms/ci-fix.
If the PR CI checks appear to be stuck in queued state, please add a comment with contents /azp run.
This should result in a new comment denoting a PR validation pipeline has started and the checks should be updated after few minutes.
If the help provided by the previous points is not enough, post to https://aka.ms/azsdk/support/specreview-channel and link to this PR.

@Francisco-Gamino This is an unreleased API, correct?

Model Validation issues need to be fixed, no matter where they are from.
Are the breaking changes from your changes, or the other changes in your development branch?

@Francisco-Gamino This is an unreleased API, correct?

@TimLovellSmith -- Yes, that is correct.

Model Validation issues need to be fixed, no matter where they are from.

I will work on fixing the validation failures.

Are the breaking changes from your changes, or the other changes in your development branch?

No, there are not. I am introducing a brand new functionAppConfig with this PR.

Hello @TimLovellSmith -- All Model Validation issues have been resolved. Could you please take another look? Thank you.
/cc @AnatoliB @davidmrdavid

@Francisco-Gamino Linter errors should be fixed too, assuming they are indeed related to this API version - either in this PR, or some other way in the target branch ... (you can ignore the ones about flattening, its no longer recommended), and then we can rerun the pipeline.
❌ XmsEnumValidation | The enum types should have x-ms-enum type extension set with appropriate options.Location: Microsoft.Web/stable/2023-12-01/CommonDefinitions.json#L3614 |
❌ DefinitionsPropertiesNamesCamelCase | Property name should be camel case.Location: Microsoft.Web/stable/2023-12-01/CommonDefinitions.json#L3632 |
❌ XmsEnumValidation | The enum types should have x-ms-enum type extension set with appropriate options.Location: Microsoft.Web/stable/2023-12-01/CommonDefinitions.json#L3697

@Francisco-Gamino Linter errors should be fixed too, assuming they are indeed related to this API version - either in this PR, or some other way in the target branch ... (you can ignore the ones about flattening, its no longer recommended), and then we can rerun the pipeline.
❌ XmsEnumValidation | The enum types should have x-ms-enum type extension set with appropriate options.Location: Microsoft.Web/stable/2023-12-01/CommonDefinitions.json#L3614 |   ❌ DefinitionsPropertiesNamesCamelCase | Property name should be camel case.Location: Microsoft.Web/stable/2023-12-01/CommonDefinitions.json#L3632 |   ❌ XmsEnumValidation | The enum types should have x-ms-enum type extension set with appropriate options.Location: Microsoft.Web/stable/2023-12-01/CommonDefinitions.json#L3697

Thank you @TimLovellSmith for the follow up. I've fixed the linter errors. I will continue working with the next reviewer.


[Bug] Issue with NextWeb API Key Deactivation Error

Bug Description
I encountered an issue where I received the following error message while using the NextWeb API:
{
  "msg": "Invalid OpenAI Response",
  "type": "application/json; charset=utf-8",
  "body": {
    "error": {
      "message": "The OpenAI account associated with this API key has been deactivated. If you are the developer for this OpenAI app, please check your email for more information. If you are seeing this error while using another app or site, please reach out to them for more help.",
      "type": "invalid_request_error",
      "param": null,
      "code": "account_deactivated"
    }
  },
  "status": 401,
  "edgeId": "next-edge-l8TUp14GKpp38atZ2wW5c"
}

Despite having sufficient quota in my account, I am receiving this account_deactivated error. I kindly request assistance in resolving this issue promptly.
Steps to Reproduce
See content.
Expected Behavior
See content.
Screenshots
No response
Deployment Method

[ ] Docker
[ ] Vercel
[ ] Server

Desktop OS
No response
Desktop Browser
No response
Desktop Browser Version
No response
Smartphone Device
No response
Smartphone OS
No response
Smartphone Browser
No response
Smartphone Browser Version
No response
Additional Logs
No response

@JiaxiangBU hi, it seems to be the api key have been deactivated, its has nothing to do with whether your account has sufficient balance

@JiaxiangBU hi, it seems to be the api key have been deactivated, its has nothing to do with whether your account has sufficient balance

Hi, thank you for the clarification. Just to confirm, does this mean that there is an issue with the author's API key being deactivated, regardless of the balance in my account?

yep

I contacted the developer of the project, and the API is now functioning normally.


Stop setting the Gatekeeper constraint as compliant without audit results

Relates:
https://issues.redhat.com/browse/ACM-5147

@dhaiducek this is ready for review now.


Configuration for pg_stat_statements extension

When enabled, postgres will provide statistics about executed statements that can be used for performance analysis and optimization.
An example query could be something like:
select substring(query, 1, 100) as query,
       calls,
       round((total_time)::numeric, 3) as total_time,
       round((total_time / calls)::numeric, 3) as mean_time
from pg_stat_statements
where dbid in (select oid from pg_database where datname = 'ccdb')
order by total_time desc limit 50;

and the results would be:
                                                query                                                 | calls | total_time | mean_time
------------------------------------------------------------------------------------------------------+-------+------------+-----------
 SELECT * FROM "delayed_jobs" WHERE (((("run_at" <= ?) AND ("locked_at" IS NULL)) OR ("locked_by" = ? |  3228 |    100.756 |     0.031
 SELECT * FROM "users" WHERE ("guid" = ?) LIMIT ?                                                     |  2319 |     64.266 |     0.028
 SELECT * FROM "apps" WHERE ("guid" = ?) LIMIT ?                                                      |  1709 |     52.066 |     0.030
 INSERT INTO "events" ("space_guid", "type", "timestamp", "actee", "actee_type", "actee_name", "actor |   322 |     39.481 |     0.123
 SELECT * FROM "spaces" WHERE (("spaces"."id" IN (?)) AND ("id" IN (SELECT "id" FROM (SELECT * FROM ( |   889 |     37.196 |     0.042
 SELECT count(*) AS "count" FROM "apps" WHERE (("space_id" IN (SELECT "id" FROM (SELECT * FROM (SELEC |   549 |     28.167 |     0.051
 UPDATE "delayed_jobs" SET "locked_at" = ?, "locked_by" = ? WHERE (((("run_at" <= ?) AND ("locked_at" |   415 |     27.996 |     0.067
 UPDATE "apps" SET "guid" = ?, "created_at" = ?, "updated_at" = CURRENT_TIMESTAMP, "name" = ?, "produ |   259 |     25.995 |     0.100
 SELECT "users".* FROM "users" INNER JOIN "spaces_developers" ON ("spaces_developers"."user_id" = "us |  1043 |     25.298 |     0.024
 SELECT * FROM "organizations" WHERE ("id" = ?)                                                       |  1397 |     24.195 |     0.017
 INSERT INTO "delayed_jobs" ("queue", "handler", "priority", "created_at", "run_at", "guid") VALUES ( |   395 |     23.703 |     0.060
 SELECT * FROM "spaces" WHERE ("spaces"."guid" = ?) LIMIT ?                                           |   860 |     21.012 |     0.024
 SELECT * FROM "apps" WHERE ("id" = ?)                                                                |   584 |     18.334 |     0.031
 SELECT "routes".*, "apps_routes"."app_id" AS "x_foreign_key_x" FROM "routes" INNER JOIN "apps_routes |   239 |     17.120 |     0.072
 SELECT * FROM "buildpacks" WHERE "id" = ?                                                            |   894 |     16.901 |     0.019
 SELECT * FROM "stacks" WHERE ("stacks"."id" IN (?))                                                  |  1086 |     16.813 |     0.015
 DELETE FROM "apps" WHERE "id" = ?                                                                    |    56 |     16.459 |     0.294
 SELECT * FROM "spaces" WHERE ("id" = ?)                                                              |   788 |     15.453 |     0.020
 SELECT * FROM "apps" WHERE ("id" = ?) LIMIT ? FOR UPDATE                                             |   359 |     13.005 |     0.036
 SELECT * FROM "quota_definitions" WHERE ("id" = ?)                                                   |   701 |     12.428 |     0.018
 SELECT count(*) AS "count" FROM "spaces" WHERE (("id" IN (SELECT "id" FROM (SELECT * FROM (SELECT *  |   222 |     11.758 |     0.053
 SELECT * FROM "apps" WHERE (("apps"."space_id" = ?) AND ("space_id" IN (SELECT "id" FROM (SELECT * F |   222 |     11.646 |     0.052
 SELECT * FROM "organizations" WHERE (("organizations"."id" IN (?)) AND ("id" IN (SELECT "id" FROM (S |   327 |     11.604 |     0.035
 INSERT INTO "apps_routes" ("app_id", "route_id") VALUES (?, ?) RETURNING ?                           |    64 |     11.410 |     0.178
 INSERT INTO "events" ("space_guid", "type", "actee", "actee_type", "actee_name", "actor", "actor_typ |    75 |      9.100 |     0.121
 SELECT count(*) AS "count" FROM "apps" WHERE (("apps"."space_id" = ?) AND ("space_id" IN (SELECT "id |   222 |      8.698 |     0.039
 DELETE FROM "delayed_jobs" WHERE "id" = ?                                                            |   409 |      8.698 |     0.021
 SELECT * FROM "delayed_jobs" WHERE ("guid" = ?) LIMIT ?                                              |   396 |      8.521 |     0.022
 SELECT * FROM "spaces" WHERE ("spaces"."organization_id" IN (?))                                     |   470 |      8.115 |     0.017
 INSERT INTO "app_usage_events" ("state", "package_state", "instance_count", "memory_in_mb_per_instan |   181 |      7.753 |     0.043
 SELECT "routes".* FROM "routes" INNER JOIN "apps_routes" ON ("apps_routes"."route_id" = "routes"."id |   208 |      6.531 |     0.031
 INSERT INTO "routes" ("host", "domain_id", "space_id", "created_at", "guid") VALUES (?, ?, ?, CURREN |    58 |      6.407 |     0.110
 SELECT * FROM "droplets" WHERE ("droplets"."droplet_hash" = ?) LIMIT ?                               |   407 |      6.345 |     0.016
 SELECT count(*) AS "count" FROM "apps" WHERE (("space_id" = ?) AND ("name" = ?) AND ("id" != ?)) LIM |   429 |      6.219 |     0.014
 DELETE FROM "routes" WHERE "id" = ?                                                                  |    64 |      6.180 |     0.097
 UPDATE "apps" SET "updated_at" = CURRENT_TIMESTAMP, "staging_task_id" = ? WHERE ("id" = ?)           |    57 |      6.109 |     0.107
 UPDATE "apps" SET "guid" = ?, "created_at" = ?, "updated_at" = CURRENT_TIMESTAMP, "name" = ?, "produ |    59 |      6.105 |     0.103
 INSERT INTO "apps" ("name", "production", "space_id", "admin_buildpack_id", "buildpack", "salt", "en |    42 |      5.885 |     0.140
 SELECT * FROM "domains" WHERE (("domains"."id" IN (?)) AND (("owning_organization_id" IS NULL) OR (" |   312 |      5.812 |     0.019
 SELECT * FROM "organizations" WHERE ("guid" = ?) LIMIT ?                                             |   222 |      5.273 |     0.024
 UPDATE "apps" SET "updated_at" = CURRENT_TIMESTAMP, "package_state" = ?, "detected_buildpack_guid" = |    45 |      5.255 |     0.117
 SELECT sum(("memory" * "instances")) AS "sum" FROM "apps" WHERE (("apps"."space_id" IN (?)) AND ("st |   478 |      5.159 |     0.011
 SELECT count(*) AS "count" FROM "buildpacks" WHERE (("name" = ?) AND ("id" != ?)) LIMIT ?            |   415 |      4.692 |     0.011
 DELETE FROM "spaces" WHERE "id" = ?                                                                  |    12 |      4.256 |     0.355
 SELECT "queue", count(*) AS "count" FROM "delayed_jobs" WHERE ("attempts" = ?) GROUP BY "queue"      |   145 |      4.125 |     0.028
 SELECT "queue", count(*) AS "count" FROM "delayed_jobs" WHERE (failed_at IS NOT NULL) GROUP BY "queu |   145 |      4.118 |     0.028
 DELETE FROM "organizations" WHERE "id" = ?                                                           |    12 |      3.993 |     0.333
 SELECT DISTINCT ON ("app_id") "apps".* FROM "apps" INNER JOIN "service_bindings" ON ("service_bindin |   285 |      3.922 |     0.014
 DELETE FROM "users" WHERE "id" = ?                                                                   |    13 |      3.621 |     0.279
 SELECT * FROM "domains" WHERE "id" = ?                                                               |   220 |      3.618 |     0.016
(50 rows)

Thanks @sykesm
Can you set the value in the infrastructure templates to null rather than false?  This way they can still be overridden by stubs, but we don't defaults in both manifest templates and jobs specs.

@Amit-PivotalLabs, done. Thanks.


SAK-22934 Portal: Linked the logo to /portal/

https://jira.sakaiproject.org/browse/SAK-22934
Changed the span tag that contained the institution logo to an anchor tag so that clicking it takes the user to the /portal/ page. However, the questions of whether every user has a /portal/ page arose. Should probably test with different types of users.

I agree that clicking the logo is a convention although it's a convention we've avoided implementing for quite some time. Accidental navigation in an LMS is far more costly than accidental navigation in a commercial website. The end user could lose content or work because of an accidental click.
Additionally, if we did want this behavior, it looks like the modification here is not accessible. What does a screenreader hear with this link?

I see. I could add accessibility, but I do understand that accidental navigation is a problem. I thought linking the logo would be helpful because I've heard a lot of complaints about the logo not being linked, since its convention to have it linked. Should we just scrap this then?

Hi Michelle that's probably the best course of action at this time, closing this.


Revert "Google Sign-In update to v4.0.1"

Reverts xamarin/GoogleApisForiOSComponents#47

We need to delay this update of Sign-In.  It is required that we update many other Google libraries as well.  Starting with Firebase.Core and Firebase Analytics.


Add check for empty email form submissions

Description
This PR addresses issue https://github.com/pulumi/marketing/issues/864 by adding a check to make sure events generated from Hubspot's callback do not generate fake form submission events to Segment, polluting metrics with empty form fills.

@cnunciato are any other changes needed?


Pitch: string trimming feature

Using the trimming function results in more concise a and nice-looking code compared to achieving the same effect by manipulating the Whitespace() parsers. Besides, it's convenient and intuitive to use this kind of function in such a way and context.

Probably it's better to extend the existing Conversions.SubstringToString with the functionality, rather then to create a new conversion which refer to "fake" TrimmedString type 🙄

Probably, I should have put this in the "Discussion" section instead 🙄


Devcontainer support for web ide

Is your feature request related to a problem? Please describe.
Atm web ide does not have extension for working with devcontainer projects
Describe the solution you'd like
Web ide should have devcontainer extension preinstalled.

This Issue has been automatically marked as "stale" because it has not had recent activity (for 14 days). It will be closed if no further activity occurs. Thanks for the feedback.

Closing this as it is out of scope for this repo.


GPU Particles 3D dies if their "Scale Curve" stays in zero for too long

Godot version
v4.1.2.stable; v4.2.beta2
System information
Godot v4.2.beta2 - Windows 10.0.19045 - Vulkan (Forward+, Mobile) - GLES3 (Compatibility) - dedicated NVIDIA GeForce GTX 1650 (NVIDIA; <IP_ADDRESS>42) - Intel(R) Core(TM) i7-2600K CPU @ 3.40GHz (8 Threads)
Issue description
3D particles with a scale curve that stays in zero for a period of time will die silently.

The period seems to be around 0.05+ of the normalized curve time.
Those particles disappear and don't emit sub-particles.
2D particles don't have the same issue.

The workaround is to use small values, like 0.001, instead of absolute zero.

Steps to reproduce
The reproduction project has a "main_3d" scene that shows the issue, even in the editor.
There is also a "main_2d" scene to show that 2D particles work fine using the same curve.
Minimal reproduction project
GPUParticle3D Scale Curve Zero.zip

Related to https://github.com/godotengine/godot/issues/68809.

Tested in v4.3-stable and v4.4-dev6. The issue is still the same.


disable parent node selection

In the tree view , i would like to disabled the selection of the parent node .
->Parent
-> child1
-> child2
We should be able to only click/select the child nodes. I added ngclass to disable if its a parent node .
disabling works fine in UI, but i can still click it on parent node and it gets selected .

Hi, you can use actionMapping.mouse.click and override the default behaviour

@adamkleingit is it possible to share any live examples?


Cannot Import Keystore JSON Exported From binance.org

Reproduce:

Create a new wallet on binance.org and save it as keystore json
Import the keystore json using NewKeyStoreKeyManager
Shows decryption error

@touhonoob  the keystore mismatch with binance.org going to fixe in https://github.com/binance-chain/go-sdk/pull/48.


add transaction summary modal

What does this pull request do? Explain your changes. (required)
This PR introduces a "transaction summary modal" as described by Rimble effectively preventing users from accidentally triggering multiple wallet prompts. In a follow up PR we can introduce other important information to this modal such as estimated fees and time as described in the Rimble guide.
Does this pull request close any open issues?
Fixes #709
Screenshots (optional):

Could a helper be used here so we don't have to add Apollo client writeData logic whenever we submit a tx?

ah yeah totally, that would be much more DRY :) Will follow up with a helper inside utils.tsx.


replace nprogress with topbar

nprogress was used in the initial versions of LiveView, but it's 6 years old and has some accessibility issues regarding invalid aria roles, as caught in https://rocketvalidator.com/s/624562a6-bdbe-4411-9c28-3652a4887982/v/15063573
In recent versions of LiveView, topbar is used instead:
http://buunguyen.github.io/topbar/
This PR replaces nprogress with topbar

Ah ha! I noticed this change in a recent project I generated but I hadn't had time to dig in to see why there was a change.

@doomspork I tend to keep package-lock

Ah yes, maybe it's because my code editor (VS Code) formatted it? I think I opened the file to see the changes and then it applied formatting.


chore(deps): upgrade dev dependencies

Upgrades project dependencies. See details in workflow run.

Automatically created by projen via the "upgrade-dev-dependencies-k8s-31-main" workflow

⚪ Backport skipped
The pull request was not backported as there were no branches to backport to. If this is a mistake, please apply the desired version labels or run the backport tool manually.
Manual backport
To create the backport manually run:
backport --pr 4934

Questions ?
Please refer to the Backport tool documentation


Add a grpc section to APIs

Excited for this feature!

https://github.com/cosmos/chain-registry/issues/127#issuecomment-1003282772
See #127


Optionally pull in project SDK versions

Fixes build issues with RN 56

this PR should be approved

Thanks @ds8k


Prereqs + Coreqs Parser

Summary
Adds the prereqs + coreqs parser to the courseplan codebase and adds some tests to check the parser. It also adds python code to the codebase and adds a Pipfile + Pipfile.lock files to handle libraries that python requires (similar to the package.json and package-lock.json). Documentation will be linked once it's been added to Notion. https://www.notion.so/courseplan/Python-Development-7e8f11eb35624ee9a2cc32d44fb1450c

[x] turn prereqs string into more structured format (boolean string)

Remaining TODOs:

[ ] turn boolean expression string into tree structure
[ ] have some script to run the python tests

Test Plan

Added tests under test_prereqs_parse.py

Notes
This is the first python code in the codebase (I think)! Either way, I will link the documentation in the notion about python development due to the addition of Pipfile and Pipfile.lock. https://www.notion.so/courseplan/Python-Development-7e8f11eb35624ee9a2cc32d44fb1450c

I <33 langchain! Now that OpenAI has released finetuning for GPT-3.5 maybe we can consider finetuning for specific tasks that we do. An alternative would maybe be validating the response from GPT-3.5 in some way and passing it back through to GPT if it's wrong (something like "This is not a json, correct your mistake"). These might be overkill for this task but if we use GPT for anything else more intensive, it might be good to keep in mind. Also might we consider setting up an organization account for DTI on OpenAI 😳 so Andrew doesn't have to pay for calls LOL.

Wow using GPT 3.5 to interpret and parse the requirements of specific courses seems like a great idea! I am excited to see where this goes and to see the first lines of Python code being added to the code base.
Some comments/suggestions are that it might be useful to insert some idea of the accuracy of this model into the documentation. I would be interested seeing how we can generate more test data for the model as well as how much data would be need to ensure high accuracy.

How sure are we that GPT will always be able to correctly parse the nlp input? Do we want to consider retrying with higher temperature if an error occurs?


[Feature] Create Apple Silicon binaries

Thanks for this amazing tool. It would be awesome to have a native Apple Silicon build if that is possible.
Thanks!

Turns out my goreleaser setup already makes Apple Silicon builds, I just need to expose them as build artifacts!

Works like a charm! Thanks so much for the quick turnaround!


get does not add model to req object

The client's get method does not add the last model to req object and therefore other middleware cannot access the model.
The post method does add the last model - is it by design that the get method does not?

I think you're right if you are assuming that this is a mistake. It's really inconsistent for sure.
I searched the commit history and I found this commit where the methods get and post get introduced; and it already includes a model attribute for post; but not for get. Sadly there's no explanation in the commit message so I really don't know if this is by design or not.
Anyhow, if you could create a PR that set model too for a get which doesn't result in any breaking tests then I would definitely be inclined to merge it. 😄

Resolved in https://github.com/twg/devour/pull/217


Cloud run service requires location property

When creating a gcp.cloudrun.Service, it requires a location property. From the little documentation I can find online, this is just the region. This should not be required as it should pull in from gcp:region.

@nesl247 Thanks for the suggestion, it totally makes sense to me. I've created an issue upstream, fill free to vote and engage there.
For now, your best bet is to refer to gcp.config manually:
const cloudRun = new gcp.cloudrun.Service("asd", {
    location: gcp.config.region!,
    metadata: {
        namespace: gcp.config.project!,
    },
    spec: {
        containers: [{
            image: "gcr.io/cloudrun/hello",
        }],
    },
});

Thanks for the sample. I actually had no idea about gcp.config.* either. I've been doing a new pulumi.config() for it.
I've voted on the linked issue. Thanks!

The upstream issue got closed as "won't fix", so I'll do the same here


Change the name of example providers

This repo has config for the AWS provider, but it is not the real config since that lives in pulumi-aws. To avoid confusion, we should change the name of these example providers to something clearly phony, like example1, example2, ...
See https://github.com/pulumi/ci-mgmt/pull/755 for details

I think the added warning comments are fine so no need to work this out.

Sounds good. Fixed in https://github.com/pulumi/ci-mgmt/pull/755/commits/4de683b996dddf184e25ede1072ea8282dae77e1.


ID of the CellTower in use

Description
I would love to have a method that would get the ID of currently used mobile network celltower.
Should be related to https://developer.android.com/reference/android/telephony/TelephonyManager#getAllCellInfo()
Use Case
Displaying information/interacting with users depending on their location, which in some cases can be obtained immediately by using a known cell ID.

Or maybe https://github.com/mroczis/netmonster-core could be used?

I'd prefer not to have a new dependency if possible
We are over minSdkVersion 17 so the API you cite is available
If you implemented that and returned a reasonable JSON tree of info representing all the stuff that came back that seems reasonable. Might be more reasonable in react-native-netinfo (where you'll meet me again, I'm the main maintainer over there as well at the moment...)

Indeed it makes more sense to implement it in netinfo. See you there!


Remove HttpPipelineNextPolicy

To quote @alzimmermsft:

If we're going to be changing the API to remove HttpPipelineNextPolicy I think we should do a major break here instead of trying to retain a similar flow as azure-core. Right now, each pipeline has a mutable state with nextPolicy and HttpPipeline is supposed to be thread-safe which this will break. If two requests are being made where a common RetryPolicy is shared between two pipelines the nextPolicy may not point to the right following policy.
What I'll propose, split process into two methods, onRequest(HttpRequest) : HttpRequest and onResponse(HttpResponse) : HttpResponse. This makes HttpPipelinePolicy a stateless call and removes, what I believe wasn't a great pattern before, where the pipeline policy was both a mutator of requests and responses and managed a small bit of state management as it was forced to call HttpPipelineNextPolicy.process, and if it didn't now it broke the HttpPipeline call.
Simplifying HttpPipelinePolicy to onRequest and onResponse removes state management. It no longer needs to make a call to process the next policy, allowing the HttpPipelinePolicy to be a request and response mutator and HttpPipeline completely owns the state management. This would also allow for policies to be extended into more responsibilities in the future such as onException, if we find additional requirements (though I believe onRequest and onResponse would be sufficient for a long time).


weird C++ crash, probably from nix, only triggerable with nfb (and only via the remote invocation)

I did some garbage collection on a machine today, nothing else really out of the normal.
My "builder" box runs a github-runner, and runs a job that uses nfb internally. It seems to still be running.
Sometimes I remote to my "server" box and run nfb (set to remotely copy/build on "builder"). Today, after the GCing on both sides, I've been getting this:
▒▒ nfb: .#devShells.x86_64-linux
INFO:nix_fast_build:run nix --experimental-features 'nix-command flakes' flake metadata --json .
warning: Git tree '/home/cole/code/nixcfg' is dirty
INFO:nix_fast_build:run ssh <IP_ADDRESS> -- 'nix --experimental-features '"'"'nix-command flakes'"'"' shell --extra-experimental-features nix-command --extra-experimental-features flakes '"'"'nixpkgs#nix-eval-
jobs'"'"' -c nix-eval-jobs --gc-roots-dir /tmp/tmp.M5wTxuYP7m --force-recurse --max-memory-size 4096 --workers 2 --flake '"'"'/nix/store/zapw3ii39jpqj45j25alnba9mhr8sf31-source#devShells.x86_64-linux'"'"''
INFO:nix_fast_build:builds: 0, uploads: 0, downloads: 0
warning: unknown setting 'allowed-users'
warning: unknown setting 'trusted-users'
/nix/store/NN152MGPDFCW92B3B03G9KMNLPD9JRIS-gcc-13.2.0/include/c++/13.2.0/optional:477: constexpr _Tp& std::_Optional_base_impl<_Tp, _Dp>::_M_get() [with _Tp = std::__cxx11::basic_string<char>; _Dp = std::_Optio
nal_base<std::__cxx11::basic_string<char>, false, false>]: Assertion 'this->_M_is_engaged()' failed.
/nix/store/NN152MGPDFCW92B3B03G9KMNLPD9JRIS-gcc-13.2.0/include/c++/13.2.0/optional:477: constexpr _Tp& std::_Optional_base_impl<_Tp, _Dp>::_M_get() [with _Tp = std::__cxx11::basic_string<char>; _Dp = std::_Optio
nal_base<std::__cxx11::basic_string<char>, false, false>]: Assertion 'this->_M_is_engaged()' failed.
qerror: while checking worker process, evaluation worker got killed by signal 6 (Aborted)
ERROR:nix_fast_build:nix-eval-jobs exited with 1
INFO:nix_fast_build:run ssh <IP_ADDRESS> -- rm -rf /tmp/tmp.M5wTxuYP7m

If I ssh to that box:
╭ raisin  /var/lib/github-actions-runners/raisin-default/work/nixcfg  305ms
╰🡒  nix shell 'nixpkgs#nix-eval-jobs' -c nix-eval-jobs --gc-roots-dir /tmp/tmp.l4yqnHLARO --force-recurse --max-memory-size 4096 --workers 2 --flake
 '/nix/store/qnwbim6jba2dn300ck8iba9qq7z1lpkm-source#devShells.x86_64-linux'
warning: unknown setting 'allowed-users'
warning: unknown setting 'trusted-users'
/nix/store/NN152MGPDFCW92B3B03G9KMNLPD9JRIS-gcc-13.2.0/include/c++/13.2.0/optional:477: constexpr _Tp& std::_Optional_base_impl<_Tp, _Dp>::_M_get()
[with _Tp = std::__cxx11::basic_string<char>; _Dp = std::_Optional_base<std::__cxx11::basic_string<char>, false, false>]: Assertion 'this->_M_is_eng
aged()' failed.
/nix/store/NN152MGPDFCW92B3B03G9KMNLPD9JRIS-gcc-13.2.0/include/c++/13.2.0/optional:477: constexpr _Tp& std::_Optional_base_impl<_Tp, _Dp>::_M_get()
[with _Tp = std::__cxx11::basic_string<char>; _Dp = std::_Optional_base<std::__cxx11::basic_string<char>, false, false>]: Assertion 'this->_M_is_eng
aged()' failed.
error: while checking worker process, evaluation worker got killed by signal 6 (Aborted)

but I'm able to manually spot eval some output derivations manually still, and like I said, running the same nix-fast-build flake->devshell->direnv from the CI job seems fine.
I realize this is probably a nix bug, but I can only repro though nix-fast-build right now.
Any ideas?

I've tried restarting the nix-daemon on both sides, that didn't really help.

Great, my system registry nixpkgs are on different revs. Really, really, really wish the flake registry didn't exist, or at least that everyone would just not use them for anything.

I guess maybe this is more of a potential nix-eval-jobs bug.
It doesn't happen if I pop a shell from nixos-23.11's nix-eval-jobs and run the eval command.

I think I'm seeing the same thing, and this was with nix-eval-jobs only (ci run), nix-fast-build not involved

Fixed in https://github.com/nix-community/nix-eval-jobs/pull/298

Doesn't #52 mean that nix-fast-build is still broken, despite the fix submitted to nix-eval-jobs (https://github.com/nix-community/nix-eval-jobs/issues/297 + https://github.com/nix-community/nix-eval-jobs/pull/298).
Why not make nix-fast-build use nix-eval-jobs via the latter's flake?

Could be an option. However I wanted to minimize the copy of nixpkgs that a user has to download.

#52 seems relevant, it was quite disappointing to find out my build tools are relying on global system state, and even more so now that nix-eval-jobs is fixed, and I still can't use nix-fast-build via its flake.
It feels like a subversion of the point and benefits of flakes, and the resulting downside.
I can send a PR, if you give me an idea what you think the right fix is, or would merge.

A first good step would be to only use nixpkgs#nix-eval-jobs if we have --remote enabled and otherwise rely on things in $PATH instead.

I think that's the case: https://github.com/Mic92/nix-fast-build/blob/f024a66e6a1f83de95aba109287a97dd6ca76127/nix_fast_build/init.py#L451-L452
(and then tracing flake->default.nix it looks like the input for nix-eval-jobs is an input to derivation, so I assume it uses that, rather than the broader system's PATH for nix-eval-jobs binary.
how would you feel if I:

read flake.lock json
read out the locked nix-eval-jobs
(maybe "fragile"), recompose the locked flakeref and use {nej_locked_flakeref}#nix-eval-jobs instead of nixpkgs#nix-eval-jobs
??

For nix-fast-build from the flake we can use the nixpkgs provided, although this would trigger a rebuild everytime there is a nixpkgs bump.


v1.8.0 now always redirects to Vite server instead of loading the dotnet application

When I use version 1.8.0, I can't load the dotnet application anymore (I'm using Umbraco)
Using v1.6.2 and below can load the dotnet application and run vite dev server at the same time. Not sure what happened on v1.8.0.
I skipped v1.7 because it doesn't allow me to set WorkingDirectory (on v1.6.2 and below) or PackageDirectory on v1.8.
Could you please help?
Logs on v1.6.2

Logs on v1.8

Hello, do you have a minimal repro project? to track the problem faster.

Hi @Eptagone thanks for responding
Here is a minimal repro project: https://github.com/Webcoda/test-viteaspnetcore18
you might need to

Run pnpm install on FE_DEV folder
To repro, you can run dotnet build && dotnet run on UmbracoCMS\
To run the Umbraco correctly, you can comment line 70 in UmbracoCMS\Startup.cs

Hi @Webcoda, thanks. I'll take a look.

@Eptagone I think I might have found the way to fix it.
I put the app.UseViteDevMiddleware() after app.UseUmbraco() and it works ok now

Hi, I see. So, it's just an issue with the order of the middlewares. Something similar happened with another issue (#12)

Yes, I believe so. I need to put the app.UseViteDevMiddleWare() after app.UseUmbraco() if I use v1.8.0 and before app.UseUmbraco() for version v1.6.2


Enable particles to "move" in two directions (up and down)

Which version are you using?
1.18.12
Is the latest version affected?

[X ] Yes
[ ] No

Which library are you using?

[ X] Vanilla JS (tsparticles)
[ ] React (react-tsparticles)
[ ] Vue.js 2.x (particles.vue)
[ ] Vue.js 3.x (particles.vue3)
[ ] Angular (ng-particles)
[ ] Svelte (svelte-particles)
[ ] Preact (preact-particles)
[ ] Inferno (inferno-particles)
[ ] jQuery (jquery-particles)

Is your feature request related to a problem? Please describe.
Currently it seems like you can only make particle travel in a single global direction.
Describe the solution you'd like
Would it be possible to set direction as an array, so for example 50% of particles could travel up the page, and 50% could travel down.
Describe alternatives you've considered
We considered doing this with two canvas elements, but in our use case we are using the "line linking" because particle as an visual indicator.
Additional context
Thank you in advance

Hi @alexwybraniec,
This configuration can be achieved with the 1.18.x version using a little trick, in the upcoming 2.0.0 it will be easier using particles groups (#1006)
You can try this configuration
tsParticles.load("tsparticles", {
  background: {
    color: "#fff"
  },
  backgroundMode: {
    enable: true
  },
  detectRetina: true,
  fpsLimit: 60,
  interactivity: {
    detectsOn: "canvas",
    events: {
      onClick: {
        enable: true,
        mode: "push"
      },
      onHover: {
        enable: true,
        mode: "bubble"
      },
      resize: true
    },
    modes: {
      bubble: {
        distance: 400,
        duration: 2,
        opacity: 1,
        size: 40,
        speed: 3
      },
      push: {
        quantity: 4
      }
    }
  },
  particles: {
    rotate: {
      value: 0,
      random: false,
      direction: "clockwise",
      animation: {
        enable: false,
        speed: 5,
        sync: false
      }
    },
    move: {
      enable: true,
      outMode: "out",
      speed: 2
    },
    number: {
      density: {
        enable: true,
        area: 800
      },
      value: 80
    },
    opacity: {
      value: 0.8
    },
    shape: {
      type: "circle",
      options: {
        circle: [ // this is the workaround
          {
            particles: { // this overrides the main particles section
              color: {
                value: "#f00"
              },
              move: {
                direction: "top"
              }
            }
          },
          {
            particles: {
              color: {
                value: "#00f"
              },
              move: {
                direction: "bottom"
              }
            }
          }
        ]
      }
    },
    size: {
      value: 16
    }
  }
});


Command reconstruction - verb noun

Reconstruction of the command structure within the CLI. It has been changed from a noun verb to verb noun structure, as described in issue #216
Folders added:

Commands - all the top-level commands
Test - holds all the test files
Object

app
call
context
log
route
server

Common
Run - all run related files

Open for suggestions: I don’t like the way the structure no handles apps and routes config.
fn list config apps I think it would be nicer to have fn list apps config but urfave will be expecting that 4th command and therefore fn list apps will not be valid.
^^ We went with fn config [app | route] <key> <value> to set a configuration.
Following changes to documentation and commands:
Fn #1031
Tutorials #87
Flow Lib Go #5
Fdk-ruby #13
Fdk-java #138

Would be nice to get https://github.com/fnproject/cli/issues/296 done as part of this change as well.

At least one of the tests is broken:
2018/05/25 12:41:31 Expected sdterr message (Unable to parse annotation value 'value'. Annotations values must be valid JSON strings.) not found in result: COMMAND: /home/circleci/go/src/github.com/fnproject/cli/fn create routes xpldnjob myroute --image foo/duffimage:0.0.1 --annotation test=value
INPUT:
RESULT: true

maybe a regression?

Black box review:

can you accept both plural and singular of of apps and app , call/calls log/logs etc everywhere?
add ‘ls’ as an alias for list
Remove lambda command ?  or put it at the bottom or hide it  - it doesn't work anyway
fn push docs:  “push function to Docker Hub” - > Push function to docker regsitry

Also fn set app foo  key value is a synonym for fn update app foo -c key=value
not sure it botheres me that much but just noticed.

In regard to single vs plural, we can one command name and then multiple aliases. It will just change the help text to have the 3 options apps, app, a etc.. If this is fine then it can be added?

I did a quick scan and I think you pick up most uses of the command that need changing in docs with the following grep:
 fgrep -rE "fn +(apps|routes|calls|logs|context|update) "  *  | grep -v \.git

@rikgibson the help command comes with urfave so there is no way to add a category.
version can be moved to other commands but then it would be on its own?


Error: out_of_range

I'm trying to read in a .txt file which is packed with JSON Objects. Afterwards I want to get a specific object out of the document, but everytime I try to run my problem I get an Error-Message like:

untreated exception at 0x778B17D2 in "programm_name.exe": Microsoft C++-exception:nlohmann:detail:parse_error at memorylocation 0x008FE65C

(Sorry for bad english);
However this is just for testing purpose. Later I want to parse the return string of an function.
But for this problem my code looks like this:
`string text;
json temp;
ifstream read;
read.open("response_enumerate.txt");
getline(read, text);
read.close();
json in = json::parse(text);

temp = in["/device/command/0"_json_pointer];
cout << temp;`

and my .txt file with the JSON Objects looks like this (just a part of it because otherwise nobody would look at this post because it would be to long)
{"device":[{ "command":"enumerate", "statusCode":0, "wait":0, "deviceMake":"Digilent", "deviceModel":"OpenScope MZ", "firmwareVersion":{ "major":1, "minor":301, "patch":0}, "macAddress":"00:7E:G0:8B:6C:CC", "calibrationSource":"flash", "nics":{ "wlan0":{ "macAddress":"00:1E:B0:8B:5B:AC"}}, "requiredCalibrationVer":17, "requiredWiFiParameterVer":8, "awg":{ "numChans":1,

The problem seems to be that your input is invalid JSON. At least this is the output you mention. I am confused, because the title of this issue mentions out_of_range. Are these two individual problems?
The parse error should also contain a position in the code (since 3.4.0 with a line and column), and a detailed error message (like "unexepected end of file" or "invalid Unicode byte"). Can you please double check whether you can get the complete error message? You could also catch json::parse_error and output the result of .what().
Furthermore, you could use tools like https://jsonlint.com to see where the parse error is.

No I think that these problems are linked together. It's not like an "classic" error which appears in the Error-Section. While debugging it just stops the process, opens the "json_sax.hpp" file, and indicates an error in line 253 which says:

case 4: JSON_THROW(reinterpret_cast<const detail::out_of_range>(&ex)) // LCOV_EXCL_START

Thats why I mentioned "out_of_range" in the title of this issue.
And it says, as I mentioned above:

untreated exception at 0x778B17D2 in "programm_name.exe": Microsoft C++  exception:nlohmann:detail:parse_error at memorylocation 0x008FE65C

I'm sorry if this is an stupid error or mistake but I'm pretty new to programming.

The parser only throws an out_of_range error in case of number overflow. Can you share your JSON file, or check whether it contains numbers that cannot be expressed (e.g., really really large exponents)?

I tried different JSON files with different content but there is still the same error.
The JSON file I used looks like this:
{   "device": [     {       "command": "resetInstruments",       "statusCode": 0,       "wait": 1000     }   ] }
So there isn't any large number but it still throws an out_of_range error.
Just to make sure, this is the c++ code I use for printing out the JSON Object:
`#include "pch.h"
#include "OwnUtil.h"
#include
#include
#include
#include <Windows.h>
#include <stdio.h>
#include <SFML/Network.hpp>
#include <nlohmann/json.hpp>
#include <nlohmann/adl_serializer.hpp>
using json = nlohmann::json;
using namespace std;
int main()
{
string text;
json temp;
ifstream read;
read.open("response_resetinstruments.txt");
getline(read, text);
read.close();
json in = json::parse(text);
temp = in["/device/command/0"_json_pointer];
cout << temp;
`

Firstly, you can immediately parse from an std::ifstream - just pass it to the parser like this:
std::ifstream read("response_resetinstruments.txt");
json in = json::parse(read);

Secondly, JSON Pointer /device/command/0 cannot be applied to the JSON value:

/device accesses the array [ { "command": "resetInstruments", "statusCode": 0, "wait": 1000 } ]
/command is then invalid, because in an array, you can only use integers.

To access "resetInstruments", the correct JSON Pointer would be /device/0/command.

Ok. I'm new to this so I want it as clear as possible. But still thank you for the improvement.
However, I applied what you mentioned above, and there is still the same error. It points to the out_of_range part in the json_sax headerfile.

This code works for me:
#include "json.hpp"
#include <iostream>
#include <fstream>

using json = nlohmann::json;

int main()
{
    std::ifstream read("response_resetinstruments.txt");
    json in = json::parse(read);
    auto temp = in["/device/0/command"_json_pointer];
    std::cout << temp << std::endl;
}

and outputs
"resetInstruments"

Can you try this code?

Copied your code, inserted it in my programm and I still get the same error. I just had to include "pch.h" and the headerfiles are one folder above, so I have to include #include "nlohmann/json.hpp". But the rest is exactly the same.

To rule out issues with the input file, can you try
#include "json.hpp"
#include <iostream>

using json = nlohmann::json;

int main()
{
    json in = R"({ "device": [ { "command": "resetInstruments", "statusCode": 0, "wait": 1000 } ] })"_json;
    auto temp = in["/device/0/command"_json_pointer];
    std::cout << temp << std::endl;
}

Sorry for not responting.
I had to add "pch.h" again but then it finally worked. Why isn't there any error message if I store the string directly into the JSON Obejct? And, even more important, what do I have to change in order to use some sort of .txt file or an response from another function as an imput?
Did I make some sort of mistake or did I overlook something?
Thanks in advance you really helpt me.

I do not understand your questions. Can you please be more specific?

I very appreciate that the code works if I directly store the String in the JSON variable.
However I need to parse a string which is just the return of a function. But if I use a variable I can‘t write R“(...);.
So do you have any additional Information or tips on how I can parse from a string variable instead of a string directly?

You can call json j = json::parse(your_string);


Importing electron causes fs.existsSync error

Just storing this here, steps to repro are just import electron into new app.

Can I have the error message and stack trace please?


Apply Noto Sans TC (via Google webfont)

This supersedes #111 and fixes #98.
Safari on OS X:

Edge on Windows 10:

Internet Explorer on Windows 10:

Current coverage is 91.45%

Merging #145 into master will not affect coverage as of ce6f720

@@            master    #145   diff @@
======================================
  Files           33      33
  Stmts         1030    1030
  Branches         0       0
  Methods          0       0
======================================
  Hit            942     942
  Partial          0       0
  Missed          88      88

Review entire Coverage Diff as of ce6f720

Powered by Codecov. Updated on successful CI builds.


ci: create

Codecov Report

:exclamation: No coverage uploaded for pull request base (main@abffaed). Click here to learn what that means.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main       #1   +/-   ##
=======================================
  Coverage        ?   94.66%
=======================================
  Files           ?        4
  Lines           ?      281
  Branches        ?        0
=======================================
  Hits            ?      266
  Misses          ?       12
  Partials        ?        3

Flag
Coverage Δ

unittests
94.66% <0.00%> (?)

Flags with carried forward coverage won't be shown. Click here to find out more.

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 abffaed...ffddd4e. Read the comment docs.


Multiple collaborators

Hey @kgretzky ,
I believe it might make sense to support you in managing the Github projects.
There was a longer time of inactivity, and @hash3liZer and I kept working on the fork.
Maybe it's a good idea for this repository to add some contributors with write permission, so that we can make sure the PRs, issues etc are reviewed and merged in the future as well.

Hey James!
Thank you and sorry for late response. I've just checked the fork and it looks great. I'm super glad that you are finding the time to fix issues in evilginx on your own. This is a great idea although I'd prefer to be implementing the fixes on my own when I have time. I know I could be doing much better in maintaining this project as I don't have that much time for it. As much as I'd like to add you guys as active collaborators I feel it would generate additional work overhead for me to be verifying the changes and I simply do not have the time :(
I think it is best if you continued to maintain the fork and I can link to it here in case anyone wants to use evilginx version with faster fixes :). Please do send some links to your commits on the fork, when you can, so that I can look into them and reimplement the fixes here in the base repo.

Sure, got it. I've PRed some changes here: https://github.com/kgretzky/evilginx2/pull/504


Use weights_only for load

torch.load without weights_only parameter is unsafe. Explicitly set weights_only to False only if you trust the data you load and full pickle functionality is needed, otherwise set weights_only=True.
If weights_only=True doesn't work for some cases, then explicit weights_only=False should be used.
Found with https://github.com/pytorch-labs/torchfix/

Do you know the version it was introduced in?

The PR that added the option is https://github.com/pytorch/pytorch/pull/86812, first release with it is PyTorch 1.13.0

Thank you! I have dropped the support for torch<=1.12 to be able to use weights_only everywhere.
I also plan to add a hash-check protocol for our plugins to ensure that downloaded files are safe to read. I have already implemented part of that protocol in #6.


Misleading HistoryAndWarmupRegressionAlgorithm.cs

Searching for a coarse selection algo + history i found your HistoryAndWarmupRegressionAlgorithm
but there is no history?
it is just a warmup example algo.

Closed in #2171