Remove Gemfile.lock from Git

As per the recommendation of the Bundler and RubyGems teams:

When developing a gem, use the gemspec method in your Gemfile to avoid duplication. In general, a gem's Gemfile should contain the Rubygems source and a single gemspec line. Do not check your Gemfile.lock into version control, since it enforces precision that does not exist in the gem command, which is used to install gems in practice. Even if the precision could be enforced, you wouldn't want it, since it would prevent people from using your library with versions of its dependencies that are different from the ones you used to develop the gem.

Hi @stevenharman, I merged this change in https://github.com/intercom/intercom-rails/pull/228
Sorry it took so long :/


Feature/azure openai

I just reviewed the changes. I think the script could be a bit easier and it could also store the necessary attributes so you don't have to enter them so often.

Did you also sign your commits?

Did you also sign your commits?

not yet.
I will sign, squash and write documentation before removing the draft state.


error: ‘long unsigned int newsbeuter::openssl_mth_id_function()’ defined but not used

When attempting to compile newsbeuter (https://github.com/akrennmair/newsbeuter/commit/20330eaf3441a47b1f1c0d0a134a2052fdc1ac74) I get the following errors:
g++ -march=x86-64 -mtune=generic -O2 -pipe -fstack-protector-strong -fno-plt -std=c++11 -ggdb -Iinclude -Istfl -Ifilter -I. -Irss -Werror -Wall -Wextra -Wunreachable-code -DLOCALEDIR=\"/usr/local/share/locale\" -DGIT_HASH=\"20330\" -I/usr/include/libxml2  -I/usr/include/json-c  -D_GNU_SOURCE -D_DEFAULT_SOURCE  -DHAVE_OPENSSL=1 -march=x86-64 -mtune=generic -O2 -pipe -fstack-protector-strong -fno-plt -o src/cache.o -c src/cache.cpp
src/utils.cpp:1149:22: error: ‘long unsigned int newsbeuter::openssl_mth_id_function()’ defined but not used [-Werror=unused-function]
 static unsigned long openssl_mth_id_function(void) {
                      ^~~~~~~~~~~~~~~~~~~~~~~
src/utils.cpp:1135:13: error: ‘void newsbeuter::openssl_mth_locking_function(int, int, const char*, int)’ defined but not used [-Werror=unused-function]
 static void openssl_mth_locking_function(int mode, int n, const char * file, int line) {
             ^~~~~~~~~~~~~~~~~~~~~~~~~~~~

Recently we switched to openssl 1.1.0e which is likely the cause for this breakage.
% openssl version
OpenSSL 1.1.0e  16 Feb 2017

Is there any other information or any suggestions about what I can do next?

This is probably related to this entry in the changelog for 1.1.0:

*) OpenSSL now uses a new threading API. It is no longer necessary to
set locking callbacks to use OpenSSL in a multi-threaded environment. There
are two supported threading models: pthreads and windows threads. It is
also possible to configure OpenSSL at compile time for "no-threads". The
old threading API should no longer be used. The functions have been
replaced with "no-op" compatibility macros.
[Alessandro Ghedini, Matt Caswell]

Thanks for reporting! I'll look into fixing this tomorrow.

I should really stop making such promises. Large PR got merged and ate all my computer time for the evening. This issue will have to wait a bit more.

I'm in no hurry, don't worry.  Thank you for looking into at all \o

I don't have 1.1.0, so I can't test this locally (without building OpenSSL and Curl from source, at least). Can you please pull down bugfix/522-openssl-new-threading-api branch and see if it works for you?

With that branch I see two new errors of the same calibur:
src/utils.cpp:1152:22: error: ‘long unsigned int newsbeuter::openssl_mth_id_function()’ defined but not used [-Werror=unused-function]
 static unsigned long openssl_mth_id_function(void) {
                      ^~~~~~~~~~~~~~~~~~~~~~~
src/utils.cpp:1138:13: error: ‘void newsbeuter::openssl_mth_locking_function(int, int, const char*, int)’ defined but not used [-Werror=unused-function]
 static void openssl_mth_locking_function(int mode, int n, const char * file, int line) {
             ^~~~~~~~~~~~~~~~~~~~~~~~~~~~

Perhaps you added one too many 0's?

Definitely looks like that!

Compiling https://github.com/akrennmair/newsbeuter/commit/9e44cb564b31e21ecfc03582bc3b8a314e166a59 I get no errors or warnings and newsbeuter seems to function fine pulling feeds from https urls.  From what little I know, this seems to be a success. o/


Improve doctor output for partial xcode install

Hi all, I just migrated all my data from my previous Mac to another, then I tried to install flutter, everything was fine except when I run flutter doctor -v, it can not find Xcode11.
Here are outputs from flutter doctor -v:
[✓] Flutter (Channel stable, v1.9.1+hotfix.4, on Mac OS X 10.14.5 18F203, locale en-AU)
    • Flutter version 1.9.1+hotfix.4 at /Users/kevinhao426/flutterSDK/flutter
    • Framework revision cc949a8e8b (10 days ago), 2019-09-27 15:04:59 -0700
    • Engine revision b863200c37
    • Dart version 2.5.0

[✓] Android toolchain - develop for Android devices (Android SDK version 29.0.0)
    • Android SDK at /Users/kevinhao426/Library/Android/sdk
    • Android NDK location not configured (optional; useful for native profiling support)
    • Platform android-29, build-tools 29.0.0
    • Java binary at: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 1.8.0_202-release-1483-b49-5587405)
    • All Android licenses accepted.

[!] Xcode - develop for iOS and macOS
    ✗ Xcode installation is incomplete; a full installation is necessary for iOS development.
      Download at: https://developer.apple.com/xcode/download/
      Or install Xcode via the App Store.
      Once installed, run:
        sudo xcode-select --switch /Applications/Xcode.app/Contents/Developer
    • CocoaPods version 1.8.3

[✓] Android Studio (version 3.5)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin version 40.0.2
    • Dart plugin version 191.8423
    • Java version OpenJDK Runtime Environment (build 1.8.0_202-release-1483-b49-5587405)

[!] Connected device
    ! No devices available

! Doctor found issues in 2 categories.

I tried sudo xcode-select --switch /Applications/Xcode.app/Contents/Developer, then flutter doctor, but nothing changes.
I also tried to re-install xcode, and all other solutions I found, but the problem still exists.
Could anyone please give me some suggestions on this?
My system version is macOS: 10.14.5-x86_64;
Xcode version 11.0

What does xcrun xcodebuild -version say?

The response for xcrun xcodebuild -version is:
dyld: Library not loaded: @rpath/DVTFoundation.framework/Versions/A/DVTFoundation
Referenced from: /usr/bin/xcodebuild
Reason: image not found
[1]    77483 abort      xcrun xcodebuild -version
I also tried to find the solution for this error but failed to fix.

It is your XCode installation problem. Reinstall XCode and make sure that command line tool is installed.

@jmagman Would it be helpful for the doctor to include the suggestion of inspecting the output of xcrun xcodebuild -version?

Yes, a good thing to add to the "Xcode installation is incomplete" repair instructions.

It is your XCode installation problem. Reinstall XCode and make sure that command line tool is installed.

Well I tried that, uninstall my Xcode and clean files under Library/Developer/CommandLineTools then reinstall Xcode and CommandLineTools, but this does not solve the problem. Is there anything that I missed or I did it in the wrong way?

It is your XCode installation problem. Reinstall XCode and make sure that command line tool is installed.

Well I tried that, uninstall my Xcode and clean files under Library/Developer/CommandLineTools then reinstall Xcode and CommandLineTools, but this does not solve the problem. Is there anything that I missed or I did it in the wrong way?

You shouldn't need to explicitly install command line tools.
sudo xcode-select -s /path/to/Xcode.app
sudo xcodebuild -runFirstLaunch

You aren't hitting a Flutter-specific issue, you're hitting a Xcode installation issue, so Stack Overflow might be a better place to ask your question.  Once xcrun xcodebuild -version returns a real version of Xcode > 9.2, flutter commands should work.
We're using this issue to track making the flutter doctor output more helpful.

It is your XCode installation problem. Reinstall XCode and make sure that command line tool is installed.

Well I tried that, uninstall my Xcode and clean files under Library/Developer/CommandLineTools then reinstall Xcode and CommandLineTools, but this does not solve the problem. Is there anything that I missed or I did it in the wrong way?

You shouldn't need to explicitly install command line tools.
sudo xcode-select -s /path/to/Xcode.app
sudo xcodebuild -runFirstLaunch

You aren't hitting a Flutter-specific issue, you're hitting a Xcode installation issue, so Stack Overflow might be a better place to ask your question. Once xcrun xcodebuild -version returns a real version of Xcode > 9.2, flutter commands should work.
We're using this issue to track making the flutter doctor output more helpful.

Thank you for your reply. Actually I have tried all of the solutions including those from StackOverflow to solve the Xcode installation issue but they all failed.
Due to I don't have much time finding a correct solution for this, I had to reset my MacBook then init my work environment for Android and Flutter. Now everything works fine. Only sad that the issue stays unsolved and I cannot help others that face a similar problem.

Reopening, we want to make the tool output more helpful in this scenario.


IDL doesn't exist

I tried running anchor test and i got the error Error: IDL doesn't exist I already ran cargo clean then cargo build but the error still exist.

You need to run anchor build instead of cargo build to generate the IDL. Also, anchor test builds the programs by default too, so if you still get this error, it might be because of a mismatch between your program name in various places e.g. Anchor.toml and Cargo.toml.

To add to the previous post, the latest version (v0.30.0) includes various fixes to the IDL generation workflow, making it very likely that the problem you're having is fixed.


C++: new query for futile arguments to C functions

This query addresses a corner-case of the C standard: functions declared in header files with empty parameter lists are considered to have an unknown parameter list, not an empty one. This means that arguments can be provided in calls that only have the declaration in scope, but will be ignored by the callee.
An LGTM test run is here. The one result looks correct.

I'm new to the thread and am trying to digest the discussion thus far.  It would seem to me that the first order of business would be to work out a precise definition of when the diagnostic should be raised.
So let me propose mine:
"A call to a ()-forward-declared function shall issue a diagnostic unless there is also a definition of same function with the requisite number and type of parameters.  (Should this definition also be ()-formed, it will be treated as if it were (void)-formed.)"
What I'm unsure of (since I'm new to all this) is the scope of the search for the definition of said function.  Should it be confined to the same translation unit? To the entire project?
Also, this should apply only to C, never C++.
There is another case: we do find a definition of the function, but its parameters/return type is incompatible with our arguments.  This would be the subject of a different QL query with different wording ("We were able to locate the definition of F, but its parameters do not match your argument list"...)

I just tested to see whether such a query would overlap with compiler warnings, and I was surprised to find no compiler warnings even when the argument mismatch is within the same file. Here's an example:
#include <stdio.h>

int foo();

int main() {
  printf("%d\n", foo());
  return 0;
}

int foo(int x) {
  return x;
}

This program produces no warnings with Clang or GCC even when passing -Wall -Wpedantic. And sure enough, it prints garbage when I run it. On my Mac it prints 0 when compiled with -O2 and 1 otherwise.
When it's that easy to pass too few parameters, I'd expect good results from a query that looks for this mistake.

@zlaski Your definition of what the analysis should do looks good to me in an ideal setting, but I think it could be difficult to get the "same types of parameters" part right. It can be fairly subtle which types are compatible on which platforms. Developers might argue that it's perfectly fine to cast their mystruct * into a long through the function call since that works on the platforms they care about. I suggest starting with a query that checks only for a mismatch in the parameter count, leaving the matching of types for later.
I hope the extractor will think of the three uses of the foo identifier in the above example as referring to the same Function with multiple FunctionDeclarationEntrys. Otherwise, let's talk about possible workarounds.

@jbj, I agree about leaving the types for later.  I'll also leave the issue of multiple definitions; another query should (and maybe already does) address this.

The c-extractor is behaving a bit strangely -- to me, anyway
If I run a query against test.c

from FunctionCall fc , Function f
where fc.getTarget() = f
select fc, f

it produces the following .expected output:

| test.c:7:3:7:16 | call to declared_empty | test.c:1:6:1:19 | declared_empty |
| test.c:8:3:8:16 | call to declared_empty | test.c:1:6:1:19 | declared_empty |
| test.c:9:3:9:15 | call to declared_void | test.c:2:6:2:18 | declared_void |
| test.c:10:3:10:15 | call to declared_with | test.c:3:6:3:18 | declared_with |
| test.c:12:3:12:12 | call to undeclared | test.c:12:3:12:3 | undeclared |
| test.c:14:3:14:19 | call to not_yet_declared1 | test.c:14:3:14:3 | not_yet_declared1 |
| test.c:14:3:14:19 | call to not_yet_declared1 | test.c:25:6:25:22 | not_yet_declared1 |
| test.c:15:3:15:19 | call to not_yet_declared2 | test.c:15:3:15:3 | not_yet_declared2 |
| test.c:15:3:15:19 | call to not_yet_declared2 | test.c:26:6:26:22 | not_yet_declared2 |
| test.c:17:3:17:29 | call to declared_empty_defined_with | test.c:27:6:27:32 | declared_empty_defined_with |
| test.c:18:3:18:29 | call to declared_empty_defined_with | test.c:27:6:27:32 | declared_empty_defined_with |
| test.c:21:3:21:29 | call to declared_empty_defined_with | test.c:27:6:27:32 | declared_empty_defined_with |
| test.c:22:3:22:29 | call to declared_empty_defined_with | test.c:27:6:27:32 | declared_empty_defined_with |
| test.cpp:5:3:5:13 | call to cpp_varargs | test.cpp:1:6:1:16 | cpp_varargs |
| test.cpp:6:3:6:13 | call to cpp_varargs | test.cpp:1:6:1:16 | cpp_varargs |

And so some FunctionCalls appear to have more than one target!  I've chatted with some people in the office and we made an educated guess as to why we might have multiple Function objects for each function (a case of mistaken ad-hoc polymorphism).  But how can a signle FunctionCall be bound to multiple Functions?
I've been trying to cobble together FutileParams.ql that would correctly handle test.c, thus far unsuccessfully...

We can't tell from that test output whether it's the call to getTarget that has multiple results or if it's the implicit call to getLocation that's used to produce the final output. One way to test that is by querying for it:
from FunctionCall fc, Function f
where fc.getTarget() = f
select fc, f, strictcount(fc.getTarget())

I ran the query

from FunctionCall fc, Function f
where fc.getTarget() = f
select fc, f, strictcount(fc.getTarget()), strictcount(f.getLocation())

and got

| test.c:7:3:7:16 | call to declared_empty | test.c:1:6:1:19 | declared_empty | 1 | 1 |
| test.c:8:3:8:16 | call to declared_empty | test.c:1:6:1:19 | declared_empty | 1 | 1 |
| test.c:9:3:9:15 | call to declared_void | test.c:2:6:2:18 | declared_void | 1 | 1 |
| test.c:10:3:10:15 | call to declared_with | test.c:3:6:3:18 | declared_with | 1 | 1 |
| test.c:12:3:12:12 | call to undeclared | test.c:12:3:12:3 | undeclared | 1 | 1 |
| test.c:14:3:14:19 | call to not_yet_declared1 | test.c:14:3:14:3 | not_yet_declared1 | 1 | 2 |
| test.c:14:3:14:19 | call to not_yet_declared1 | test.c:25:6:25:22 | not_yet_declared1 | 1 | 2 |
| test.c:15:3:15:19 | call to not_yet_declared2 | test.c:15:3:15:3 | not_yet_declared2 | 1 | 2 |
| test.c:15:3:15:19 | call to not_yet_declared2 | test.c:26:6:26:22 | not_yet_declared2 | 1 | 2 |
| test.c:17:3:17:29 | call to declared_empty_defined_with | test.c:27:6:27:32 | declared_empty_defined_with | 1 | 1 |
| test.c:18:3:18:29 | call to declared_empty_defined_with | test.c:27:6:27:32 | declared_empty_defined_with | 1 | 1 |
| test.c:21:3:21:29 | call to declared_empty_defined_with | test.c:27:6:27:32 | declared_empty_defined_with | 1 | 1 |
| test.c:22:3:22:29 | call to declared_empty_defined_with | test.c:27:6:27:32 | declared_empty_defined_with | 1 | 1 |
| test.cpp:5:3:5:13 | call to cpp_varargs | test.cpp:1:6:1:16 | cpp_varargs | 1 | 1 |
| test.cpp:6:3:6:13 | call to cpp_varargs | test.cpp:1:6:1:16 | cpp_varargs | 1 | 1 |

and so it would indeed appear that we are dealing with unique Function objects, some with multiple locations.  So now the question becomes, how do I get rid of the extra rows?  Perhaps I should eliminate Function f from the from clause altogether?  If someone else could chime in here and provide solution, I'd be eternally grateful (and will have learned something in the process).

It's not necessarily an issue that there are multiple locations. They should get merged into single alerts on LGTM even though they look funny in the qltest output. You can test your prototype queries in the LGTM query console to see roughly how alerts will look.
If you find a need to exclude some of the locations, you can try selecting FunctionDeclarationEntrys instead of Functions. That might let you distinguish the implicit declarations from the explicit ones. But if they're all equally valid declarations of the same function, maybe it's perfectly correct to select them all.

Should we treat undeclared functions (undeclared in test.c) similarly to how we treat ()-declared functions?  The general concept is the same, namely that the caller cannot reliably determine the number or type of arguments to use.

@rdmarsh2, I have the QL query (along with updates to qhelp, test and test results) sitting on the zlaski-semmle:cpp340 branch.  Is there a way for those to get pulled into the current PR, or should I create a new PR?

It sounds right to treat undeclared functions the same as ()-declared functions.
This PR (#790) is merged, so please make a new PR for your new query.


Investigate how to call the rules engine from the front-end

Investigate handling for calling rules engine:

[ ] Determine whether to deliver the rules engine as a single file, or to package it as a wheel
[x] Figure out what can be passed back and forth between the front-end and the rules engine (can we do objects, or do we have to use primitives?) #66

Maybe use Proxy

For the second, we can use instantiated classes (python objects).

Rules engine has merged example of multiple files into main.

From what I understand, testing showed us that we need the wheel to split the rules engine into multiple files.  Since this is desirable for the rules engine, I've logged #88 for us to build a wheel.  I think that closes out the investigation for this task.


[WIP] Separate NixOS lib and nixpkgs lib

Motivation for this change
This was motivated by this comment.
The ultimate goal of this PR is to be able to include NixOS lib functions in an easy manner for custom projects, eg with import <nixpkgs/nixos>; lib.....
An other objective is to have a clearer separation between nixos and nixpkgs functions.
Until now, only nixpkgs had a lib, and NixOS related functions were part of this lib, directly called via imports (eval-config) or directly defined in files (test related functions).
For a better separation and cleaner namespaces, this PR create a new lib to nixos, that can be called with with import <nixpkgs/nixos/lib>; ... or with import <nixpkgs/nixos>; lib.... and move the functions that has nothing to do with nixpkgs in the nixos library.
This is a work in progress, and this aims to be as much backward compatible as possible.
nixpkgs lib side
options, types, modules have moved to nixos lib, but each file (lib/options.nix, ...) is still present to not break any direct imports (eg, import <nixpkgs/lib/options.nix>) that users might have in their setups.
The nixos lib, can be accessed via the lib.nixos namespace. So if options functions must be used in nixpkgs context, they can be accessed with lib.nixos.options.
Note that there is no trace of usage of options, types and modules in the nixpkgs only source, so the new namespace should not break things.
nixos lib side
A lib top level attribute was added to ./nixos that can be used with "with import <nixpkgs/nixos>; lib..." or "with import <nixpkgs/nixos/lib>;".
This lib includes previous nixpkgs lib options, types and modules.
The nixpkgs lib is in the namespace lib.nixpkgs AND at top-level.
This is the lib that is used in the module system, so having nixpkgs lib at top level is required to not break modules code that expect nixpkgs lib functions to be accessible from lib.

This is in early state and will require more extensive testing to be sure nothing break it is much backward compatible as possible before being mergeable.
In current state, this can build the manual and a simple config via VM.
Feedback is welcomed.

cc @edolstra

Any opinions on this?

The idea at least seems good to me, but I haven't done much nixos/* stuff, so better if someone else looks at it as well.

I think this change would have made sense when nixpkgs and NixOS were in separated repository.
I honestly do not recall why I chose nixpkgs lib over adding a new one to NixOS back then, probably because we were already heavily using nixpkgs/lib.

I think this change would have made sense when nixpkgs and NixOS were in separated repository.

As it was only linked in the description and easy to miss, bellow is the quote from @edolstra comment that motivated this PR:

I don't think we should move the NixOS testing stuff to the non-NixOS part of Nixpkgs. They're NixOS-specific after all.

I do agree with that, but I think that it could be useful to have some NixOS specific functions easily available from external projects, like testing related functions.
Making a NixOS specific library that could be imported with import <nixpkgs/nixos> {}; lib.callTest felt like a good solution for this.
In this process, it made sense to also move NixOS specific parts of the nixpkgs lib to that library.
I hope this can help to clarify the motivation.

I've found the module system nice to be able to use outside of NixOS, for example in defining a user environment (see https://github.com/rycee/home-manager for instance), so I'd like to see it continue to be available from the main Nixpkgs lib. I don't see it as being NixOS specific.

I have totally forgot about this one.
I agree that it is easy to use nix lib from outside of nixpkgs, and I do that in a few of my personal projects.
The main goal of this PR was to have a cleaner organization of libs with a new lib.nixos namespace.
And also to have a cleaner lib available in nixos modules to avoid #19899 like problems.
Anyway, closing as this has been open for too long.
Will reopen if someone is interested by this.


TKTDebugger class>>registerToolsOn: broken

The extension method ToolsRegistry>>registerDebugger:withRank: has been removed in the GT-Debugger package, so this method needs to be fixed.

The most likely fix is just to remove enable/disabled methods and IsEnabled class variable because now all debuggers are available by default in pharo9.

+1
Loading fails on Pharo 9

Loading only core avoids the error.

Ah, I duplicated it in #94

And PR #95 aims at fixing it.

Sorry, I will close the original issue and keep the duplicated as to avoid confusion with the PR


Handle when go get prepends a status string to errors

When go get -d<EMAIL_ADDRESS>starts with an empty module
cache, it appears to prepend an additional status string (copied from https://github.com/dependabot/dependabot-core/issues/4625#issuecomment-1067578732):
# first run throws full error - note that repo2 is a direct dependency of repo1
[dependabot-core-dev] ~/dependabot-core/tmp/<redacted-org>/repo1 $ GOPRIVATE=* go get -d<EMAIL_ADDRESS>go: downloading github.com/<redacted-org>/repo2 v0.39.0
go get: reading google.golang.org/grpc/go.mod at revision v1.33.0: unknown revision

# second run doesn't include the `go: downloading...` line
[dependabot-core-dev] ~/dependabot-core/tmp/<redacted-org>/repo1 $ GOPRIVATE=* go get -d<EMAIL_ADDRESS>go get: reading google.golang.org/grpc/go.mod at revision v1.33.0: unknown revision v1.33.0

# clean the modcache
[dependabot-core-dev] ~/dependabot-core/tmp/<redacted-org>/repo1 $ go clean -modcache

# the full error shows up again
[dependabot-core-dev] ~/dependabot-core/tmp/<redacted-org>/repo1 $ GOPRIVATE=* go get -d<EMAIL_ADDRESS>go: downloading github.com/<redacted-org>/repo2 v0.39.0
go get: reading google.golang.org/grpc/go.mod at revision v1.33.0: unknown revision

It's currently unclear if this is only thrown on unknown revision
errors, or any generic error that happens from a clean module cache. I
suspect the latter, but haven't yet taken the time to dive into the go get source.
Most likely this will be fixed by stripping out the status line very
early in the error handling pipeline, and then passing along the normal
error.
But the first step is getting a working test case to repro the error...
this PR is currently a WIP at doing that, and then will be gradually
updated to actually fix the issue.
Note that I don't know much Ruby, let alone Rspec, so once I hack
together a semi-workable solution this will definitely need some further
polish from actual Rubyists before being ready for merge.
Fix #4625

Total WIP, just trying to get a working test case before doing anything else...

Closing in favor of https://github.com/dependabot/dependabot-core/pull/4910.
I figured out the root cause a bit better, and turns out to be non-reproducible currently because it happened under go 1.17 but not go 1.18... at least not that I'm seeing, it could still be a race of some sort. And it only appears with an empty go module cache, so I could reliably reproduce manually, but not in rspec, even when I explicitly called go clean -modcache it'd still never appear.


Garbled ascii on specific terminal geometries

wiki-tui is gaining users 👍
But, with it issues as well.
Please revisit my forum post, https://www.unitedbsd.com/d/603-wikipedia-on-the-terminal
and read through some findings.
Can the suggestion on the last post be implemented as a fix for the garbled ascii on certain terminal geometries?

Thanks for your bug report!

the garbled ascii on certain terminal geometries?

Yeah, this issues has been around with wiki-tui since I've added the welcome screen. It seems that when the terminal width is odd, the logo gets garbled.
I'll try and fix it.

I've uploaded a patch onto experimental, can you please check if it fixed the error for you?

@Builditluc wow, that was fast.
Yes, I can apply the patch locally and check.
Actually, as soon as I had posted the issue, I realized that I should have tried this fix myself and commit back if working.
I'll get back to you with the result but, it might take a few hours, not at home right now.

The only thing I did was making each of the logo line the same length (as the user rvp wrote in your post).

I'll get back to you with the result but, it might take a few hours, not at home right now.

No problem

@Builditluc

The only thing I did was making each of the logo line the same length (as the user rvp wrote in your post).

Exactly why I said, I should have done it myself :)
Anyway, this fixed it, no more garnled ascii.
I should say that I used the whole main.rs from the experimental branch, i.e.
$NetBSD$

--- src/main.rs.orig	2021-11-05 06:25:22.000000000 +0000
+++ src/main.rs
@@ -13,7 +13,6 @@ use cursive::views::*;
 use cursive::Cursive;
 use std::fs;
 use std::io::Write;
-use std::{thread, time};

 pub mod config;
 pub mod error;
@@ -22,10 +21,10 @@ pub mod ui;
 pub mod wiki;

 pub const LOGO: &str = "
-  _      __   (_)   / /__   (_)         / /_  __  __   (_)
-| | /| / /  / /   / //_/  / /  ______ / __/ / / / /  / /
-| |/ |/ /  / /   / ,<    / /  /_____// /_  / /_/ /  / /
-|__/|__/  /_/   /_/|_|  /_/          \\__/  \\__,_/  /_/
+ _      __   (_)   / /__   (_)         / /_  __  __   (_)
+| | /| / /  / /   / //_/  / /  ______ / __/ / / / /  / /
+| |/ |/ /  / /   / ,<    / /  /_____// /_  / /_/ /  / /
+|__/|__/  /_/   /_/|_|  /_/          \\__/  \\__,_/  /_/
 ";

 fn main() {
@@ -41,23 +40,7 @@ fn main() {
         };
     });

-    let initializing_thread = thread::spawn(move || {
-        println!("{}", LOGO);
-
-        // create the logger
-        let logger = logging::Logger::new();
-
-        // Create the wiki struct, used for interaction with the wikipedia website/api
-        let wiki = wiki::WikiApi::new();
-
-        // Initialize the logger
-        logger.initialize();
-
-        thread::sleep(time::Duration::from_millis(250));
-        return wiki;
-    });
-
-    let wiki = match initializing_thread.join() {
+    let wiki = match initialize() {
         Ok(wiki) => wiki,
         Err(error) => {
             panic!("Something happend during initialization:\n{:?}", error);
@@ -67,6 +50,16 @@ fn main() {
     start_application(wiki);
 }

+fn initialize() -> Result<wiki::WikiApi> {
+    println!("{}", LOGO);
+
+    // create and initialize the logger
+    logging::Logger::new().initialize();
+
+    // Create the wiki struct, used for interaction with the wikipedia website/api
+    Ok(wiki::WikiApi::new())
+}
+
 fn start_application(wiki: wiki::WikiApi) {
     let mut siv = cursive::default();
     siv.add_global_callback('q', Cursive::quit);

@all-contributors please add @0323pin for bug and platform


Navbar at top of v4 Offcanvas example is broken

Can this be closed since #17183 was merged?

Indeed.


Fix mvn

The purpose is to make maven embedded work.  They way it has been written is the following : it runs the script located inside $MAVEN_HOME/bin/mvn.  Not having the script will cause archetypes tests to fail for example.  But this is true for everything any plugin using the Maven Invoker.  I think the reason is that the maven.home property is set to the mvnd home :  https://github.com/mvndaemon/mvnd/blob/156ab7e3232aece8d21a42d564e30a4bc5eec5ff/daemon/src/main/java/org/apache/maven/cli/DaemonMavenCli.java#L205-L208

The purpose is to make maven embedded work. They way it has been written is the following : it runs the script located inside $MAVEN_HOME/bin/mvn. Not having the script will cause archetypes tests to fail for example. But this is true for everything any plugin using the Maven Invoker.

Hm... that's a valid point. Let me try which mvn gets picked when I install this PR via sdkman. It  surely depends on ordering and it perhaps can be done somehow that both kinds of users are happy: the ones with pre-installed mvn and the ones expecting mvn embedded to work within mvnd.

If both mvnd and mvn are installed via sdkman, then the following happens:
which mvn
~/.sdkman/candidates/mvnd/current/bin/mvn

which is a bad news, IMO.

echo $MAVEN_HOME
/home/ppalaga/.sdkman/candidates/maven/current

mvn -v
Apache Maven 3.6.3 (cecedd343002696d0abb50b32b541b8a6ba2883f)
Maven home: /home/ppalaga/.sdkman/candidates/mvnd/current
Java version: 11.0.8, vendor: AdoptOpenJDK, runtime: /home/ppalaga/.sdkman/candidates/java/11.0.8.hs-adpt
Default locale: en_IE, platform encoding: UTF-8
OS name: "linux", version: "5.8.13-100.fc31.x86_64", arch: "amd64", family: "unix"

I wonder what can we do about that.
A. Making our mvn delegate to stock mvn if MAVEN_HOME is set (or if other mvn binaries can be found in the PATH) sounds dirty and dangerous.
B. Maybe we could try to play with the Java code on our side so that mvn is not required for the embedded scenarios. I am afraid this could turn out to be a lot of work.
C. We could advertise our distro as a Maven distro, so that providing our own mvn executable is expected and so that it is not possible (at least with sdkman) to have both stock Maven and mvnd active at the same time. I would not like this personally. I perfer not to be the first level support for all issues happening with mvn.
Other ideas?

I wonder what can we do about that.
A. Making our mvn delegate to stock mvn if MAVEN_HOME is set (or if other mvn binaries can be found in the PATH) sounds dirty and dangerous.
B. Maybe we could try to play with the Java code on our side so that mvn is not required for the embedded scenarios. I am afraid this could turn out to be a lot of work.
C. We could advertise our distro as a Maven distro, so that providing our own mvn executable is expected and so that it is not possible (at least with sdkman) to have both stock Maven and mvnd active at the same time. I would not like this personally. I perfer not to be the first level support for all issues happening with mvn.
Other ideas?

I'd rather go for C.  I don't really understand the problem with having our own mvn script.  I'm not a heavy user of sdkman, but I do choose the executables using the ordering of the $PATH variable when needed.  In all cases, we do embed the jars from maven, so if anything is problematic in maven or if we want to upgrade the internal maven, we'd have to do another release.  There may be subtle changes between the stock mvn and our own, but we could either resolve those, or advertise them more.
Also, that was the case until a few weeks ago https://github.com/mvndaemon/mvnd/commit/922403171e30e9cd38356766987adb689666a4d1#diff-9cff1802f6c575e8a1147f0f4b8d2673b0c2ac9b26bfc27b0012e2ead4795fdeR23

Asked on SDKMAN https://github.com/sdkman/sdkman-cli/issues/809

Asked on SDKMAN sdkman/sdkman-cli#809

Marco says

We could introduce a post-install hook that removes executable rights from your mvn executable

I assume that would help us, right? We need to have the mvn script executable for the embedded use cases to work, don't we?

Romain Manni-Bucau proposed the option D.:

relayout the distribution: mvnd/bin does not contain mvn but set maven.home to a folder not in path with mvn script.

We should try this (a follow up would be fine). I'd prefer this option if it turns out to work well.
That actually brings another follow up: We should have a test for some scenario using mvn.


allow adding new values when installed for DevOps Server

when the control is added using Processes UI, there is a checkbox to allow users enter new values.  How do we control this setting when using witadmin and import? thank you.

Thanks for reporting, can you describe the issues and your environment?


update cmake build

Set compiler flags.
Write executable to out/ directory.
git rm Makefile, since this is generated now

also cc: @gengjiawen and @saghul. I guess I can only request reviews through the UI for project collaborators.


RAPH-01 - Fixed syntax errors and improvised README.md

1 - Added two missing colons in the sample code.
2 - Separated the input and output to increase readability.

Hello @raphc43,
Just to tell you that: after trying to push improvements in this library without success, I have decided to clone it and evolve it on my own, now there is a new library in PyPI, jsonmask-ng, with the proposed improvements and others that I have needed.
I'm doing my best, but I'm no so much expert in python. Any comment about it will be welcome and I will try to attend suggestions.
Regards


Creating empty driver packages

Using 6.5.6 with HP machines. According to the logs, I can see the drivers download, extract, and create the packages. The logs reference the source of the files, but the directory is empty. The only errors we see is the "Error: A parameter cannot be found that matches parameter name 'Fast'. " which has been mentioned before. I have verified permissions and even created a new source share so the paths are shorter.

Duplicate of #243 - same symptoms.


ref(*): kubernetes v1.8 support

ping @mattfarina in case you're interested in taking a look at this. I'll give it a spin this afternoon.

@bacongobbler thanks for the ping. I'll take a look at this on Monday.

I have created a test image for tiller
helm init --tiller-image quay.io/adamreese/tiller:kube-v1.8
```

I used minikube start --kubernetes-version v1.8.0 --bootstrapper kubeadm to get a 1.8.0 environment. Note, PV/PVC does not work in that environment and it's a known issue. This limits the number of charts that can be tested with it. I tested several stable charts and with the exception of PV/PVC they worked.
I used helm create to create a new chart. Deployment is now part of the group apps/v1beta2 so I tried to change the deployment.yaml to this API group (since it defaulted to extensions/v1beta1). I got the error:
Error: release winsome-yak failed: Deployment.apps "winsome-yak-foo" is invalid: [spec.selector: Required value, spec.template.metadata.labels: Invalid value: map[string]string{"app":"foo", "release":"winsome-yak"}: `selector` does not match template `labels`]

The object has changed. At what point does create start a chart with a newer version of API objects? Ideally it would know the version of k8s and generate something for that version. Not suggesting that in this PR but asking the question to make sure I'm not missing something.

Note, PV/PVC does not work in that environment and it's a known issue

Aha! So that's why consul failed for me on 1.8. Good to know. :)

so I tried to change the deployment.yaml to this API group (since it defaulted to extensions/v1beta1).

That's great feedback actually. We should probably update the deployment generated on helm init as well as the initial starter chart used for helm create.

At what point does create start a chart with a newer version of API objects?

That should be starting with this release, IMO.


propel init

I've a database, and I've tried to launch "propel init", that creates Base and Map folders and many php files. And then? I've read documentation but it doesn't explain how to start with a blank file: what I have to include?

http://propelorm.org/documentation/02-buildtime.html
Paragraph "Runtime connection settings".
Il 04/ott/2015 18:27, "mmiat"<EMAIL_ADDRESS>ha scritto:

I've a database, and I've tried to launch "propel init", that creates Base
and Map folders and many php files. And then? I've read documentation but
it doesn't explain how to start with a blank file: what I have to include?
—
Reply to this email directly or view it on GitHub
https://github.com/propelorm/Propel2/issues/1004.

thanks but I still dont' understand

I create a folder called test, and using composer now I've composer.json and composer.phar files and vendor folder
I've yet a populated database, so I've launched "propel init" and now I've propel.yml and schema.xml
I've launched model:build and it creates many php files in my root, and folders Base and Map
I've launched config:convert and now I've generated-conf folder too

This is my test folder:
\Base
\generated-conf
\Map
\vendor
Articoli.php
ArticoliQuery.php
composer.json
composer.phar
propel.yml
schema.xml
now I create a test.php file:

// setup the autoloading
require_once 'vendor/autoload.php';

// setup Propel
require_once 'generated-conf/config.php';

$articolo = new Articoli();
echo $articolo->getId();

and I've:
Fatal error: Class 'Articoli' not found in D:\xampp\htdocs\propel\test.php on line 9

What's the content of your composer.json? I guess the autoloader is not configured properly, from the docs: "After generating the classes, you have to autoload them. For example, with composer this can be achieved with: [...] and then executing the command composer dump-autoload. See also namespaces recipe if you prefer to autoload your model classes following PSR-0." (http://propelorm.org/documentation/02-buildtime.html)

Here's how your composer.json should look like:
{
    // ... some other stuff
    "autoload": {
        "psr-4": {"YourNameSpace\\": "src/"}
    }
}

YourNameSpace should be replaced with whatever you responded to Which namespace should the generated php models use? during the propel init step. If you don't know this anymore you can check your schema.xml, at the top of this file should be a namespace attribute.
After you've done this run composer dump-autoload and everything should be working :)

mmm, I created my composer.json reading here: http://propelorm.org/documentation/01-installation.html
so it contains only:
{
    "require": {
        "propel/propel": "~2.0@dev"
    }
}
and in schema.xml there is no namespace's field

now I've copied my schema.xml on http://sandbox.propelorm.org/, create a new example, downloaded it, put in a new folder, made a new install, then launched model:build and config:convert and now it works. I don't know how.... :P

Great :) In case you've more issues you can reach many propel users via gitter. I guess this issue can be closed then, right?

I think so


Not compatible with React 0.12.x

Uncaught TypeError: Cannot read property '__reactAutoBindMap' of null

Add react 0.13.x to peerDependencies in package.json


Mason

[Enter feedback here]

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

ID: 83b9172a-8e15-23aa-ac78-bea94db0da55
Version Independent ID: c86dfa40-aa1b-6fa7-a918-a49b8b2a0605
Content: Setup a development environment on Windows
Content Source: hub/dev-environment/index.md
Product: dev-environment
Technology: windows-nodejs
GitHub Login: @mattwojo
Microsoft Alias: mattwoj

An integer is a number without decimal points. Maybe you have a decimal here. Try Math. floor(...) or Math. round(...) and see whether that fixes it.


Inconsistent spelling of Tor in messages

I see three different spellings of Tor being used in messages: Tor, tor and TOR.
I believe the correct spelling is Tor according to torproject.org so we should fix so spelling is consistent.

Modified all user visible strings which refer to Tor to use the spelling "Tor" and not "tor" or "TOR". Files were modified in mwc-wallet, mwc713, and mwc-qt-wallet.

Observed TOR in QT wallet.

Still observing the issue, hence re-opening this ticket.

TOR in the list of listeners at the bottom is now spelled Tor.

Successfully verified with the latest build, hence closing this ticket.


Ordering files by last modified after upload

So you can find the just uploaded files faster.

@lory87 could you please check if this pr still works with recent JS changes?


[SPARK-39451][SQL] Support casting intervals to integrals in ANSI mode

What changes were proposed in this pull request?
In the PR, I propose to support casting of interval types to the integral type: TINYINT, SMALLINT, INT, BIGINT.
Why are the changes needed?
To conform the SQL standard which allows such casting:

Does this PR introduce any user-facing change?
No, it extends existing behavior.
How was this patch tested?
By running new tests:
$ build/sbt "sql/testOnly org.apache.spark.sql.SQLQueryTestSuite -- -z cast.sql"

cc @srielau

What about exact numeric for fractional seconds?
We keep coming back to that….
CAST(INTERVAL ‚12345.678‘ SECOND As DECIMAL(8,3))

What about exact numeric for fractional seconds?

I will implement this separately.  This PR leverages existing functionality of non-ANSI mode.

cc @gengliangwang FYI

Merging to master. Thank you, @gengliangwang and @srielau for review.


Adopt physical plan serde from arrow-ballista

Hi. I'm wondering about your thoughts on adopting the physical plan serde code from ballista: https://github.com/apache/arrow-ballista/tree/master/ballista/rust/core/src/serde/physical_plan.
This will allow other users of datafusion to use and extend it (including ballista). The problem with using ballista code serde code in other projects is that it is ballista specific, rather than datafusion.

I would favor moving this into the DataFusion repo. It makes sense to have serialization be at the same level as the object that is being defined.

I agree it makes sense to me as well to have physical plan serialization in datafusion

I agree ! Thank you @nvartolomei


"Failed to interpret file %s as a pickle" % repr(file))

Hi
I am getting an error sometimes and I do not know how to fix it :(
I am at the 10. video and the code I am having is like this:
file_name = 'training_data.npy'
if os.path.isfile(file_name):
    print('Loading Data..')
    training_data = list(np.load(file_name))
else:
    print('No data file, starting fresh')
    training_data = []
and error:
C:\Users\rait.grp\PycharmProjects\pyGTA\venv\Scripts\python.exe C:/Users/rait.grp/PycharmProjects/pyGTA/main.py
Traceback (most recent call last):
  File "C:\Users\rait.grp\PycharmProjects\pyGTA\venv\lib\site-packages\numpy\lib\npyio.py", line 447, in load
    return pickle.load(fid, **pickle_kwargs)
EOFError: Ran out of input
`During handling of the above exception, another exception occurred:`
Traceback (most recent call last):
  File "C:/Users/rait.grp/PycharmProjects/pyGTA/main.py", line 163, in <module>
    training_data = list(np.load(file_name))
  File "C:\Users\rait.grp\PycharmProjects\pyGTA\venv\lib\site-packages\numpy\lib\npyio.py", line 450, in load
    "Failed to interpret file %s as a pickle" % repr(file))
OSError: Failed to interpret file 'training_data.npy' as a pickle
Loading Data..
Process finished with exit code 1

i noticed that every time I have this error my training data has been erased by the previous training session.
now I know that I have to keep backups until i find the reason

I am watching this thread after about a year, and I encountered the same issue today. Any solutions?


dead lock "Wallet-1.0/open.lock" causes "connecting to network"

Given there was an update, I decided to see if the new version would fix my connecting to network issues. It didn't. I decided to dig around a bit more by starting ./cardano-node manually:
./cardano-node "--report-server" "http://report-server.cardano-mainnet.iohk.io:8080" "--db-path" "/Users/llfourn/Library/Application Support/Daedalus/DB-1.0" "--configuration-file" "./configuration.yaml" "--configuration-key" "mainnet_wallet_macos64" "--update-latest-path" "/Users/llfourn/Library/Application Support/Daedalus/installer.pkg" "--keyfile" "/Users/llfourn/Library/Application Support/Daedalus/Secrets-1.0/secret.key" "--logs-prefix" "/Users/llfourn/Library/Application Support/Daedalus/Logs" "--wallet-db-path" "/Users/llfourn/Library/Application Support/Daedalus/Wallet-1.0" "--update-server" "https://update-cardano-mainnet.iohk.io" "--update-with-package" "--no-ntp" "--tlscert" "./tls/server/server.crt" "--tlskey" "./tls/server/server.key" "--tlsca" "./tls/ca/ca.crt" "--topology" "./wallet-topology.yaml" "--log-config" "log-config-prod.yaml"
[*production*:INFO:ThreadId 4] [2018-03-08 01:08:26.11 UTC] [Attention] Software is built with wallet part
[*production*:INFO:ThreadId 4] [2018-03-08 01:08:26.11 UTC] using configurations: ConfigurationOptions {cfoFilePath = "./configuration.yaml", cfoKey = "mainnet_wallet_macos64", cfoSystemStart = Nothing, cfoSeed = Nothing}
[*production*:INFO:ThreadId 4] [2018-03-08 01:08:26.84 UTC] System start time is<PHONE_NUMBER>000000
[*production*:INFO:ThreadId 4] [2018-03-08 01:08:26.84 UTC] Current time is<PHONE_NUMBER>843123
[*production*:INFO:ThreadId 4] [2018-03-08 01:08:26.84 UTC] Using configs and genesis:
ConfigurationOptions {cfoFilePath = "./configuration.yaml", cfoKey = "mainnet_wallet_macos64", cfoSystemStart = Nothing, cfoSeed = Nothing}
[*production*:INFO:ThreadId 4] [2018-03-08 01:08:26.84 UTC] Wallet is enabled!
[*production*:INFO:ThreadId 4] [2018-03-08 01:08:26.84 UTC] Running `actionWithWallet'
[node:ERROR:ThreadId 4] [2018-03-08 01:08:26.84 UTC] /Users/llfourn/Library/Application Support/Daedalus/Wallet-1.0/open.lock: Locked by 745: resource busy

So it looks like a simple case of a dead lock file.
The pid that had locked it was:
$ cat ~/Library/"Application Support"/Daedalus/Wallet-1.0/open.lock
745
$ ps 745
  PID   TT  STAT      TIME COMMAND
  745   ??  S      0:23.20 /Applications/iTunes.app/Contents/MacOS/iTunesHelper.app/Contents/MacOS/iTunesHelper

So the reason Daedalus can never start for me is because the process died at some point without removing its lock file and then the pid was used for some other process.
rm ~/Library/"Application Support"/Daedalus/Wallet-1.0/open.lock

Fixed it for me. I'd guess checking whether the process that owns the lock is actually a child of Daedalus or not would solve a lot of  "connecting to network" issues.

See also #2653


[fix](inverted index)Remove the strong check for parser when creating a table with inverted index (#31391)

Proposed changes
pick from master #31391

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall


[FSDE-12536] Migrate Progress component to new Vue documentation

The CI pipeline run successfully in https://jenkinsprod.corp.intranet:8443/job/UX-CHI/job/Productive/job/Chi/job/PR-282/1/. :white_check_mark:

You can check this PRs instance in https://ba96b0a06181d7ffb8862b6c43f4e41811b1e589-chi-pr.enterprise.ctl.io (external) and in https://nginx-pr-282-ux-chi.kubeodc-test.corp.intranet/ (internal)

The CI pipeline did not run successfully in https://jenkinsprod.corp.intranet:8443/job/UX-CHI/job/Productive/job/Chi/job/PR-282/2/. :x:

The CI pipeline run successfully in https://jenkinsprod.corp.intranet:8443/job/UX-CHI/job/Productive/job/Chi/job/PR-282/3/. :white_check_mark:

You can check this PRs instance in https://25c364299db6166ea4fc19c397e3207e8a407edc-chi-pr.enterprise.ctl.io (external) and in https://nginx-pr-282-ux-chi.kubeodc-test.corp.intranet/ (internal)

The CI pipeline run successfully in https://jenkinsprod.corp.intranet:8443/job/UX-CHI/job/Productive/job/Chi/job/PR-282/4/. :white_check_mark:

You can check this PRs instance in https://b845e5652cefd67ca716901ccb7adbd9919d4a6b-chi-pr.enterprise.ctl.io (external) and in https://nginx-pr-282-ux-chi.kubeodc-test.corp.intranet/ (internal)


Mac: Native M1 and older macOS support 10.13?

Interestingly, I cannot use lite-xl with my older Intel Mac and (probably can) with my new M1.
Can you build a legacy macOS supported as a lot of still excellent machines from 2011 are stuck with 10.13.6? It is more important for those to have a light editor than for the new ones?
And at the same time, can you target Macs with the M1 chip? Is it complicated?

Hi,
I am glad to have some feedback from a macOS user. I don't have a Mac myself and I was able to release a macOS package only recently, using a VM running Mojave and with some help from @gingerbeardman and @mathewmariani.
So, thank you for reporting the problem, I will do some investigations and I will try to release a package compatible with macOS 10.13. I may ask you to make some testing if you want and you have some spare time.
As for the M1, well it is more complicated because I don't have access to any machine running on a M1 chip, not event a VM. It could be possible having some support from someone who a M1 macOS machine. The process of building lite-xl from the source code is not complicated but it require installing a few things using homebrew.
If you feel like you want to contribute to lite-xl and you have some familiarity with compiling software I can give you some instructions to compile lite-xl from source code. Otherwise for the M1 I cannot do anything by myself for the moment.

I found the compilers setting to declare macOS version compatibility.
You may test the release there:
https://github.com/franko/lite-xl/releases/tag/v1.16.9-dev-1
It should work on macOS 10.13 and later.

Hey, @franko it is Sunday, take a rest! 😂
On a quick look, it works on macOS 10.13.6, I tried opening a small HTML and 300MB SQL file which reported too many symbols. It occupied 56MB of RAM and operated normally.
I can help/give a hand and I will try to follow instructions and compile. I'm an old school when we first compiled to ASM and then to OBJ and then linked that to get .com or .exe which would run under DOS (ancient times). But I wasn't in the compiling game for a while other than trying to compile PHP or Nginx but that is the other story.
I have some fuss at the job but I will try to compile on my MacBook M1 and report back.
And I can always jump in to test, I'd be glad to.
On a first look, it look fast and lite (and I like that) but being used to Sublime Text (main competitor) and JetBrains PhpStorm, as expected I have higher demands.
My first and most important is regular expressions for whatever, and search/replace in first place.
Others are lack of menu on the top, non standard fileproject open dialog (left sidebar did not appear to work?), unusual keyboard shortcuts and lack of standard macOS file and other native UI dialogs.
You may throw a look at TextMate, which is open sourced but Mac only.
https://github.com/textmate/textmate

Hey, @franko it is Sunday, take a rest!

I do all this for the pleasure, in this moment lite-xl is my favourite toy project.

On a quick look, it works on macOS 10.13.6, I tried opening a small HTML and 300MB SQL file which reported too many symbols. It occupied 56MB of RAM and operated normally.

Fine, thank you for testing. I will publish the next release with macOS 10.13 compatibility. I'll call it lite-xl professional High Sierra edition.

I can help/give a hand and I will try to follow instructions and compile. I'm an old school when we first compiled to ASM and then to OBJ and then linked that to get .com or .exe which would run under DOS (ancient times). But I wasn't in the compiling game for a while other than trying to compile PHP or Nginx but that is the other story.

Ok, so if you want to have some fun you can just begin installing a recent version of bash, meson and clang the compiler using homebrew. As for the required libraries, freetype and SDL2, we can see this later if you want to continue.

And I can always jump in to test, I'd be glad to.

Hey, thank you!

On a first look, it look fast and lite (and I like that) but being used to Sublime Text (main competitor) and JetBrains PhpStorm, as expected I have higher demands.

Don't expect lite-xl to be on par with Sublime Text or JetBrains because it is not.
The gap with Sublime Text is not huge but there is a gap. Sublime Text is more polished and has definetely more features.
JetBrains is much more powerful in term of programming tools.
The selling points of lite-xl are to be light on resource usage, fast and responsive and it can be customized with Lua.
It is also free software and everyone can contribute to improve it.
Personally, for some reason, I cannot bear to use any of these, big, heavy applications like visual studio code and jetbrains but this is just about feeling.
I cannot use an editor if it isn't fast and responsive.
I was using Sublime Text before, for me it was the perfect editor except that it isn't free software.
Lite-xl is more closer to Sublime Text than to JetBrains.

My first and most important is regular expressions for whatever, and search/replace in first place.

Normally we already have regular expressions in the dev branch thank to a new amazing contributor so we will have them very soon.
Otherwise Lua patterns are pretty fine but I understand that regular expressions are the standard and people expect to have them.

Others are lack of menu on the top

Well, currently lite-xl it is thought to be used without menus, using keyboard commands, a little bit like with vim.

non standard fileproject open dialog (left sidebar did not appear to work?)

If you opened lite-xl in a directory with too many files, like you home directory, the treeview on the left will
not be able to index all the files and will not work correctly.
You are supposed to change directory using the command Core: Change Project Folder to open the directory of a
project with a reasonable number of files.

unusual keyboard shortcuts and lack of standard macOS file and other native UI dialogs.

If you have suggestions about the keyboard shortcuts on macOS you are welcome.
They can be easily adjusted by modifying the file data/core/keymap-macos.lua.

You may throw a look at TextMate, which is open sourced but Mac only.
https://github.com/textmate/textmate

Nice to know that textmate is opensource! I may have a look.
Hovewer there is no plan to use native UI dialogs for lite-xl, this is not the way lite-xl is supposed to be.
That was a long writing. Thank you for sharing your thoughts, it makes an interesting discussion.

The new release is out, it should work on High Sierra. You may test if you are interested.

Testing in macOS 10.13.6

The application starts and operates normally
As a Drupal developer, when I open a project, it fails to list files in the sidebar: vendors get listed but web with Drupal core do not - it should not traverse everything but just what it expands, that would save resources while offering expected experience.
If two windows are open, that appears as two app instances running which is not expected behaviour and therefore one cannot view all app windows as they are separated
Nice and quick quitting
On Mac mostly all CTRL is substituted with CMD (symbol ⌘) and usually, ⌘-W closes tab or window.

I do welcome the ability to tab expand path, even more, it is a bit zsh style.
I really do like JetBrains auto-save when losing editor focus and run menu where I can run npm scripts, gulp/grunt tasks is a huge plus.
A terminal section is also a huge plus.

Testing in macOS 10.13.6

Thank you for the feedback, since the last few release a few macos developers like you are now testing lite-xl.

As a Drupal developer, when I open a project, it fails to list files in the sidebar: vendors get listed but web with Drupal core do not - it should not traverse everything but just what it expands, that would save resources while offering expected experience.

I agree, this is something I should fix. I thought exactly like you, the application should read and show the directory content progressively, as they are expanded. I just put this thing aside to focus on other priorities but now it is probably time to fix this problem.
By the way this happens because you have a lot of files in your project directory. To mitigate the problem in the mean time you may set config.ignore_files to ignore the files or directory you don't want to be listed in the sidebar. You can also increase config.max_project_files to something bigger.

If two windows are open, that appears as two app instances running which is not expected behaviour and therefore one cannot view all app windows as they are separated

Ok, I didn't know about that. I will try to ind the information about what API I need to use to implement the right behavior.

Nice and quick quitting

Not sure I understand but yes, the application quits quickly. I mean, normally it even starts quickly!

On Mac mostly all CTRL is substituted with CMD (symbol ⌘) and usually, ⌘-W closes tab or window.

Right, I got the impression that this was the more sensible thing to do on macos and seems to be quite okay up to now.

I do welcome the ability to tab expand path, even more, it is a bit zsh style.

You see, there are also some advantages about not using the standard UI elements. The lite editor was thought around a keyboard based workflow and it is vert effective to quickly open files. This is to the merit of lite's original author, rxi.

I really do like JetBrains auto-save when losing editor focus and run menu where I can run npm scripts, gulp/grunt tasks is a huge plus.
A terminal section is also a huge plus.

We have a nice autosave plugin made by @vincens2005 is the lite-xl plugins page but it saves also when the window is focused. Probably it can be easily adapted to save only when out-of-focus.
For the terminal, well you may like the console plugin, by rxi, adapted for lite-xl. I think it may do just what you are looking for.


Decide what to do with var/lib/dkms/mok.key

trivy complains about this key being in our images: https://github.com/kairos-io/kairos/pull/677/checks?check_run_id=11845758902
This key exists so that it signs modules and user imports it to EFI. Although it should be unique for every user, deleting it may not be the best choice because it has already signed modules while building the image.
Another option would be to generate a new one in cloud-init so that it's unique per installation.

the dkms key is supposed to auto sign any created modules in the system when there is a kernel upgrade, for example the nvidia modules.
That is so if you are booting on secure boot and upgrade kernel, the modules will be regenerated but not signed, so your kernel will NOT insert them during boot. If you have a dkms key and insert into your EFI database, any modules regenerated during a kernel upgrade will be signed by it and the kernel will be able to insert them and boot as normal.


Alt Column

When I Alt A column as columnA From varchar(number1) to varchar(number2), two columnA appears in the table tree

Hi @liudaac ,
Please provide more details about the issue you are seeing.

What is the OmniDB version?
What is the OmniDB flavor (app or server)?
What is the operating system version?
Exact steps to reproduce the issue, i.e., DDL to create the table, then DDL to change the column type;
A screenshot showing the issue in the tree view would also help.

Best regards,
William


Not properly formatting the data element of the MessageEnvelope

Describe the bug
According to the Cloud Event spect, https://github.com/cloudevents/spec/blob/v1.0.2/cloudevents/formats/json-format.md#3-envelope
If the datacontenttype is unspecified (and from what I have seen is not) then SHOULD proceed as if datacontenttype had been specified explicity as application/json.  "The data value MUST be stored directly as a JSON value, rather than as an encoded JSON document represented as a string."
Currently, that is how data is being stored.  Working on either end of the messages, this isn't a problem, however when publishing to an EventBus you cannot reference these values in Event pattern matching.
Regression Issue

[ ] Select this option if this issue appears to be a regression.

Expected Behavior
A setting is provided to specify the datacontenttype and is respected according to the spec.
If no datacontenttype is specified, as stated in the spec, it should be stored as a JSON value and not an encoded JSON document as a string.
Current Behavior
data is stored as an encoded JSON document represented as a string.
Reproduction Steps
Define a POCO for an EventBridge payload, use the AWS.Messaging library to publish the event.  Have an Event Rule defined that will log to a Log Watch group and view the full json of the event, specifically in the detail section.
Possible Solution
No response
Additional Information/Context
No response
AWS.Messaging (or related) package versions
AWS.Messaging-0.9.2
Targeted .NET Platform
.NET 8
Operating System and version
Windows 11, any.

Hi @Scott-transtar,
Thank you for reporting the issue. Can you please share a minimal reproducible code solution for this issue?
Regards,
Chaitanya

Sure, here is a repo that can reproduce the issue.  You will need to supply the ARN of your EventBridge in the Program.cs file.
https://github.com/[Scott-transtar/AWS.Messaging.SerializatinIssue](https://github.com/Scott-transtar/AWS.Messaging.SerializatinIssue)

Hello @Scott-transtar,
I appreciate you providing the self-contained code sample, which allows me to replicate the issue quickly.
To reproduce the problem, I followed below steps:

Create an Event Bus from AWS console.
For the above Event Bus, create a Rule.
Set the Rule type to Rule with an event pattern.
In the EventBridge pattern, select below pattern to match ANY source

 {
  "source": [{
    "prefix": ""
  }]
}

For the Target types, choose AWS service (CloudWatch log group)."
Execute the AWS.Messaging.SerializationIssue program.
Check the Cloudwatch Log Event, which contains the following:

"detail": {
        "id": "070289aa-332e-4e69-a69b-429c1e39650f",
        "source": "/AmazonEC2/i-***",
        "specversion": "1.0",
        "type": "Payload",
        "time": "2024-12-27T16:08:24.7524137+00:00",
        "data": "{\"Id\":\"052dbeff-2648-4d1f-9efa-b7737c2fd851\",\"Name\":\"Test\",\"SomeValue\":42}"
    }

As you mentioned, the data field is represented as a string containing escaped JSON.
I will further investigate this issue with the team and provide an update.
Regards,
Chaitaya


Update nox -s tag docstring

Closes #
Code Changes

[x] update the docstring for nox -s tag
[x] refactor tag session to use params instead of posargs
[x] update how documentation is presented for the usage command

Steps to Confirm

[ ] try the 3 new tag session params

Pre-Merge Checklist

[ ] All CI Pipelines Succeeded
Documentation:

[ ] documentation complete, PR opened in fidesdocs
[ ] documentation issue created in fidesdocs

[ ] Issue Requirements are Met
[ ] Relevant Follow-Up Issues Created
[ ] Update CHANGELOG.md
[ ] For API changes, the Postman collection has been updated

Description Of Changes
New Usage Session Output

@adamsachs I opened this to simply update the docstring and ended up taking things a bit further...
To give some background, I made the switch from posargs to params because in my opinion, the uses generally match the following patterns:

posargs = Good for situations where you might want multiple to be applied at the same time, or want to pass in some kind of arbitrary value
params = Good for situations where you have a clear pre-defined notion of what each option would do, and you wouldn't want/need them to overlap in functionality

Let me know if that makes sense to you or you have strong feelings about keeping them as posargs!

this makes a lot of sense, thank you for taking the time and thought to update! the choice to go with posargs was definitely a product of me just getting my bearings with nox. a param makes a lot more sense to me here!
things looked good when i ran locally, i also liked the improved usage docs and the additional cleanup. thanks again for the nice improvement!
because we don't share nox code across fides/fidesplus (not saying we should), we should also adjust the same command on the fidesplus side. i can open up a quick PR to do that. it's pretty much just c+p.

Huge thanks for the "mirror" update on plus! I so wish we had a way to share nox updates across but alas it truly isn't feasible or probably worth it hah


webex: init at version <IP_ADDRESS>40

This change adds a derivation for the Cisco Webex collaboration app,
supporting calls, meetings, messaging and events.
Home page: https://www.webex.com/

Motivation for this change
Cisco Webex collaboration application with calls, meetings, messaging and events.
Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[X] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[X] Tested execution of all binary files (usually in ./result/bin/)
21.11 Release Notes (or backporting 21.05 Relase notes)

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

[ ] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 129851 at 83d6c6eb run on x86_64-linux 1

1 package built successfully:

webex

2 suggestions:

warning: missing-phase-hooks
installPhase should probably contain runHook preInstall and runHook postInstall.
Near pkgs/applications/networking/instant-messengers/webex/default.nix:66:3:
   |
66 |   installPhase = ''
   |   ^

warning: missing-phase-hooks
buildPhase should probably contain runHook preBuild and runHook postBuild.
Near pkgs/applications/networking/instant-messengers/webex/default.nix:49:3:
   |
49 |   buildPhase = ''
   |   ^

I just discovered this update script: https://github.com/NixOS/nixpkgs/blob/master/maintainers/scripts/update.nix. That's probably something we want to use here as well.
See also: https://nixos.org/manual/nixpkgs/stable/#var-passthru-updateScript

Closing this for the time being due to a couple of unresolved upstream issues related to the apps auto-upgrade.

@myme Do you know if any of the upstream issues have been resolved and whether this can be reopened?

Do you know if anybody's able and interested in picking this back up @uvNikita?


Updated dependencies

updated dependencies in package.json

@hegdeashwin I have added a pull request, but wasn't sure if you wanted it on develop or not. Thanks! :+1:

:+1: Appreciated @mdxprograms for the update


LED programming

Hi Joel, congratulations for your work.
I bought 2 devices.
Why not use the 3 LEDs to have a better understanding of the operation of the device?!
Also use a led to indicate signal reception as a "tester"
Example:
LED 1 = Power on signal (As now) :)
LED 2 = On when receiving signal / Flashing if signal in log memory.
LED 3 = On steady or flashing when transmitting a signal.
Thanks for your attention.

Hi!
Yes, you can turn the LEDs on and off with a task. This has not been implemented because each person has to decide when to turn on and off the leds.
The pins are as follows:
led_1 io12
led_2 io13
led_3 io15
Thanks!

Thank you for your reply. Unfortunately I don't have the skills to program. Your devices fascinate expert and non-expert users.
For this reason i thought you would program this and other function as an example "De Bruijn attack", "ROLLJAM" ecc..
Expert user will change the code, non-expert user (like me) will not have the function. Thanks for your attention. My is only suggestion that can increase your sales ;)


which way to support facevarying values for meshes/subdivs?

setting vertex.texcoord means just a pair for each mesh point. Of course we can split mesh to parts  according to texture islands, but it will not work for subdivs (ok, I know, that it will work, making extra poly-stripes and disabling boundaries interpolation, but it is too much fun and not an universal solution)

Currently OSPRay only supports a single topology, i.e. if a vertex position is shared also its attributes are shared between faces. For meshes you sketched the workaround: not sharing the vertex. But you need that mainly for SubDs? SubD support in OSPRay is a first step, thus we should add support for multiple typologies (concretely an optional index.texcoord) in a further iteration? What about color?

All varying parameters can be passed in facevarying mode - color, normals, textures. it is a standard feature now. Of course, subdivs are popular and useful visual primitives, for modern renderer is better to pay attention this fact.
Why are you keep away from OpenSubdiv?

while it doesn't sound like you are using ptex, facevarying is supported in OSPRay through the ptex module, https://github.com/ospray/module_ptex.  Embree's subd params are compatible with opensubdiv's.  You could map the output of OpenSubdiv to a quadmesh if you are already using OpenSubdiv, but it would likely make more sense to use the grid primitive which hasn't been exposed through OSPRay yet, though will likely be put in soon.  Fortunately OSPRay is pretty easy to extend through modules...

ptex module published is for obsolete API, I have some adventures compiling it for OSPRay2, but still didn't see its using result, may be later. Possible, my version doesn't work. Noone can say.
Sorry, but module developement is less documented , than it should be.
Even if I use opensubdiv - nothing can force embree use vertex varying data as facevarying. You should implement them in embree anyway.

Embree does support face-varying data: https://www.embree.org/api.html#face-varying-data
And I think OSPRay should as well, i.e. it's SubD geometry should be OpenSubDiv compatible. Internally we will use Embree's grid primitive, but hide that from the user (i.e., not expose as own geometry, unless there are compelling reasons (maybe displacement mapping?)). This means adding optional parameters

uint[] index.texcoord (defaulting to index if not present)
int mode.texcoord (defaulting to mode if not present)
uint[] index.color (defaulting to index if not present)
int mode.color (defaulting to mode if not present)

Does this look ok?

It looks nice (except of normal, but it is very rare usecase), but is it implemented in OSPRay? I look into its sources and found just same set of parameters, as mentioned in doc, none of above.
Displacement - if you operate with regular grids - can be tricky, because it is getting more and more popular photometric and depth scans, they may require huge datasets, which can be stored as level maps for optimizing and may require highly irregular grid structures.

OSPRay uses the geometry normal of the (limit) surface for SubDs, currently no support for vertex normals.
index.texcoord, etc., is a proposal, not implemented yet.

yes we need to update the ptex module.
hopefully our example module is helpful to some degree, though it only shows a small example with documentation- https://github.com/ospray/ospray/tree/master/modules/pluggableGeometryExample
Embree itself supports face-varying interpolation for the subdiv input buffers.  We haven't exposed that in OSPRay, but are you saying Embree's implementation itself is not sufficient?

Yes, I said, that since OSPRay serves as Embree frontend -it is good to wait when it will support this feature. And some other like loop subdivision scheme.
I feel myself overhelmed a bit with poor documented source code now, sleazy cmake files, obsolete dependencies etc. Of course, it is typical situation, all my skills was achieved in same conditions - but I had some general line in developing which I permanently shoud leave to another siddhi :). Better have a documentation for this.
Yes, I seem it is an hour of work, if I understood that sourcecode right. I can promice to test it asap too

@iqch yes, OSPRay was originally focused on scientific visualization and we are still adding in features for studio rendering.  We appreciate your comments and hope to add that soon, even if it may have taken us a while to get to it:)

coming in the next release via 7d080b6eb30e8457c404f2eb388d32afddd63e01


Validate m4dmodule with taxonomy

Change the way the m4module is validated to be compliant with the pluggable taxonomy approach.

[ ] Define for m4dmodule what to validate in with the CRD validation and what should be validated externally with the taxonomy schema validation
[ ] Add schema validation json
[ ] Add scheme validation code
[ ] Add webhook to validate module registrations
[ ] Remove validation that moved to taxonomy validation from the CRD validation JSON
prerequisite:
[ ] #537

M4DModule validation is split between:

K8S CR validation which address the schema and base formats, including immutable values
Taxonomy validation for values to a subset of the fields (see below)

Taxonomy checks for m4dmodule:

spec.capabilities.actions.{id, level} - to be checked with defined the available actions (assume actions are pre-defined by the admin)
spec.capabilities.api.{dataformat, protocol}  - depends on #537
spec.capabilities.supportedInterfaces.sink.{dataformat, protocol} - depends on #537
spec.capabilities.supportedInterfaces.source.{dataformat, protocol} - depends on #537


feat: add new module 'images' to render multiple images under one gtk container

This module is inspired by already existing image module. The difference is this module will give user capability to render multiple images with support of custom styles to use per image and each image will be able to run distinct on-click custom commands.
Resolves #944, resolves #2734

Can you rather add a new option to the existing image module to render multiple images?

Hello
Unfortunately I was not able to notice your comment until now.
I can update this PR as you request when I will have some free time, hopefully in a near future

Hello @Alexays
Finally I was able to make a new changes as you requested in your last comment. The changes was not possible without introduction of breaking changes in configuration, for this reason I have separated old(single) and new(multiple) image rendering functionality in two strategies and implemented them separately.
I have not changed anything regarding the old implementation to avoid any kind of breaking changes, therefore configuration for a single image stays the same.
Regarding whats new: I have written new implementation for rendering multiple images, if "multiple"=true is passed in configuration than this changes will render one or more images from new structure of config json(i.e. it will look for entries array(or exec script which returns array of image file paths).
Also man page has been edited accordingly.
Let me know if any correction is necessary.


plugin->custom operator

we try not to use the word "plugin" in our user-facing docs, even though it's throughout the code. For consistency we the product docs let's call it the Custom Operator SDK.

Thanks @nelsonam! Good catch.


very fast inference, so far one of the best

i have successfully installed and able to produce the video, i have noticed two things:

when image has a beards then it is not able to generate proper output, infact it is worst in that case.
if image is not a close up or face is far in the photo or image is a full body photo then it is not able to create talking face, instead the behaviour should be, it should crop the face, make it animated and paste back or similar.
lipsync sometimes poort, sometimes good but still need improvement.

what other languages are supported?
Any update on the next release? eagarly waiting for it.

please let me know if any update on this? as we need those features to work, any one can help?

@Arvrairobo
regarding second point, please try the new WebUI and post results.
https://github.com/X-LANCE/AniTalker/issues/40

@nitinmukesh yes perfect, it has worked for me by following to your tutorial as well as your repo, but i am finding other challenges which i have written in https://github.com/X-LANCE/AniTalker/issues/40


Key presses report "virtual" key presses (including repetition), not physical key down events

Glutin currently supports key press events and key release events. But (on Windows at least), key press events correspond to the virtual key presses that the OS does, including the repeated presses that occur when you hold the key down. I would really like to be able to get actual physical key down events as well, and distinguish between "presses" and key down events. At the moment, you can get more key press events than release events due to press repetition. I need this distinction for integration with the Chromium Embedded Framework, which has three types of key event - up, down and press.
The ElementState enum currently contains Pressed and Released. Ideally it would change to Pressed, Down and  Up. This would be a breaking change, but easy to correct in user applications.

I would also like to add that this is not a blocking issue for CEF, since the behaviour can be emulated by tracking key state.

I am not sure, but I think this also causes LAlt not to function on Windows.

Closing for https://github.com/tomaka/winit/issues/52


refactor: move curve operations to new subcrate

This PR moves Stark curve operations to a new subcrate starknet-curve and removes unused curve points.
Before the removal, the wasm output from the starknet-wasm example was 328 KB. With this PR the output size becomes 292 KB - 11% reduction.

Merging anyways since the CI failures are rather caused by #244.


Svg files with children with id cause duplicate id issues when used multiple times in single page

Some svg elements have children with id, such as clippath or lineargradient. Using such svg multiple times in single page causes duplicate id errors. This issue is usually handled by randomizing id each time svg is included.
<svg width="18" height="18" viewBox="0 0 18 18" fill="none" xmlns="http://www.w3.org/2000/svg">
  <circle cx="9" cy="9" r="9" fill="#C91000" fill-opacity="0.38"/>
  <g clip-path="url(#clip0_1742_1634)">
  <path d="M14.5 12L9.75 7.25L7.25 9.75L3.5 6" stroke="#C91000" stroke-width="1.25" stroke-linecap="round" stroke-linejoin="round"/>
  <path d="M11.5 12H14.5V9" stroke="#C91000" stroke-width="1.25" stroke-linecap="round" stroke-linejoin="round"/>
  </g>
  <defs>
    <clipPath id="clip0_1742_1634">
      <rect width="12" height="12" fill="white" transform="translate(3 3)"/>
    </clipPath>
  </defs>
</svg>

<svg width="256" height="256" viewBox="0 0 256 256">
    <defs>
      <linearGradient id="gradient1">
        <stop class="stop1" offset="0%"/>
        <stop class="stop2" offset="100%"/>
      </linearGradient>
    </defs>
    <circle fill="url(#gradient1)" cx="128" cy="128" r="100" />
  </svg>

Collect ids
Relace ids with random values

I tried to handle this issue.

Required

Replace ids in SVG with random id

Optional

Maintain replaced ids after re-rendering

I have no idea how to solve the optional requirements.


Update README.md

@shizn,
Thanks for your contribution as a Microsoft full-time employee or intern. You do not need to sign a CLA.
Thanks,
Microsoft Pull Request Bot


Add CatalogSource selection during Submariner deployment in UI

Add CatalogSource selection during Submariner deployment in UI

/cc sridhargaddam skitt KevinFCormier

@MaxBab, @vthapar, does this include all the configuration fields we need?
@aswinsuryan, AFAIK other components use a selection list for some of these; I’m not sure whether that’s appropriate here, but unless there’s a specific reason not to, we should use the same UX.

@MaxBab, @vthapar, does this include all the configuration fields we need?
@aswinsuryan, AFAIK other components use a selection list for some of these; I’m not sure whether that’s appropriate here, but unless there’s a specific reason not to, we should use the same UX.

@skitt was it in ACM UI or Openshift UI, I did a quick search in console repo but did not find a UI where we can configure these.

@skitt was it in ACM UI or Openshift UI, I did a quick search in console repo but did not find a UI where we can configure these.

In the main OpenShift UI, you can choose the update channel; I think the VolSync addon has something similar. @MaxBab had something specific in mind.

Will wait for @MaxBab to get his thoughts.

@aswinsuryan
Two questions, please.

This configuration block exists on a per each cluster section. Right?
Could we add a note for a user that startingCSV is an optional parameter?
Better to not use it to fetch the latest version of the channel.

sts on a per each cluster section. Right?
Yes this is a per cluster configuration
Could we add a note for a user that s
I will add that.

@MaxBab Do you think some of these values should be pre-populated? Since this is for using custom versions I thought of having text boxes which allow filling any values should be useful than drop downs with pre-populated values.

sts on a per each cluster section. Right?
Yes this is a per cluster configuration
Could we add a note for a user that s
I will add that.

@MaxBab Do you think some of these values should be pre-populated? Since this is for using custom versions I thought of having text boxes which allow filling any values should be useful than drop downs with pre-populated values.

@aswinsuryan
This section is optional and by default will not be used during the deployment.
So, I don't think it should be pre-populated with values.
Here we agree.
I'm just saying, that if the user will choose to provide custom values, maybe it worth mention, near the name of the parameter, that it's optional.
So the user will know that he don't need to fill up this parameter if it's not really required for him.

@MaxBab Added isRequired for other fields(*) expect for startingCSV

@KevinFCormier I have addressed the issuw with UI string and this PR is good to go.

@KevinFCormier sorry missed it, I updated the remaining.

/retest-required

/lgtm

/retest-required


Display an error instead of throwing an exception when refreshing a block with repeated fields

If a block has repeated fields C5 will display an exception instead of a user friendly error.
https://github.com/concrete5/concrete5/pull/7864

Instead of this:

have this:

This is a developer-only issue, right? So, I don't think that displaying the full exception details is so bad: it may give you more details about what went wrong...


Added in-browser print map plugin with print modes and custom print background.

Added a link to an in-browser print plugin that allows you to choose one of 4 different modes for printing, and use custom tiles layer as print background.
Supported v0.7.7 and v1.0.3 with all basic leaflet layers.
Demo with text and custom print tiles layer

Looking good!


JAMES-3921: Use lenient parser, which should help parsing invalid datetime fields

JAMES-3921: Use lenient parser, which should help parsing invalid datetime fields; more informative log entry

Not sure, but keep in mind that this PR is rather a WIP - I included a test in later commit to indicate that using lenient alone doesn't fix the issue - but fix in apache-mime4j does (more in Jira, would have been easier to keep it in one place :) )

So need to wait for the fix in mime4j that you propose to be merged then, new mime4j release and upgrade in James, correct?

Hello,
Taking a deeper look at this (turning on the IDE...) I realized the date is parsed twice and that our code did not need to manage GMT convertion because Lucene takes care of it for us.
Please see https://github.com/apache/james-project/pull/1621

Taking a deeper look at this (turning on the IDE...) I realized the date is parsed twice and that our code did not need to manage GMT convertion because Lucene takes care of it for us.

Oh, so the whole code wasn't needed altogether :-)
Btw. why use zoned GMT instead of UTC? (they are virtually the same but still…)


Upgrade criterion to 0.5.1

What it says on the tin.
See the Criterion changelog for details.

The larger effect of this is that it drops clap v3.x from the dev build tree :)


failed test case?

I tried this test case which i can manually verify it's valid:
a b c = triangle12 a b c; d e f g = centroid d e f g b a c; h = s_angle c b h 30; i = intersection_lt i d h c g a
but when running through DDAR I got the numericals.InvalidLineIntersectError:
 File "<stdin>", line 1, in <module>
 File "/root/code/alphageometry/ddar.py", line 95, in solve
   dervs, eq4, next_branches, added = saturate_or_goal(
 File "/root/code/alphageometry/ddar.py", line 50, in saturate_or_goal
   added, derv, eq4, n_branching = dd.bfs_one_level(
 File "/root/code/alphageometry/dd.py", line 1094, in bfs_one_level
   add = g.add_piece(name, args, deps=deps)
 File "/root/code/alphageometry/graph.py", line 697, in add_piece
   return self.add_cyclic(args, deps)
 File "/root/code/alphageometry/graph.py", line 1524, in add_cyclic
   circle = self.get_new_circle_thru_triplet(p1, p2, p3)
 File "/root/code/alphageometry/graph.py", line 869, in get_new_circle_thru_triplet
   circle.num = nm.Circle(p1=p1.num, p2=p2.num, p3=p3.num)
 File "/root/code/alphageometry/numericals.py", line 409, in __init__
   center = line_line_intersection(l12, l23)
 File "/root/code/alphageometry/numericals.py", line 586, in line_line_intersection
   raise InvalidLineIntersectError
numericals.InvalidLineIntersectError```

does anyone know if this is a known bug in DDAR?

我尝试了这个测试用例，我可以手动验证它的有效性：
a b c = triangle12 a b c; d e f g = centroid d e f g b a c; h = s_angle c b h 30; i = intersection_lt i d h c g a
但是当运行 DDAR 时我得到了numericals.InvalidLineIntersectError：
 File "<stdin>", line 1, in <module>
 File "/root/code/alphageometry/ddar.py", line 95, in solve
   dervs, eq4, next_branches, added = saturate_or_goal(
 File "/root/code/alphageometry/ddar.py", line 50, in saturate_or_goal
   added, derv, eq4, n_branching = dd.bfs_one_level(
 File "/root/code/alphageometry/dd.py", line 1094, in bfs_one_level
   add = g.add_piece(name, args, deps=deps)
 File "/root/code/alphageometry/graph.py", line 697, in add_piece
   return self.add_cyclic(args, deps)
 File "/root/code/alphageometry/graph.py", line 1524, in add_cyclic
   circle = self.get_new_circle_thru_triplet(p1, p2, p3)
 File "/root/code/alphageometry/graph.py", line 869, in get_new_circle_thru_triplet
   circle.num = nm.Circle(p1=p1.num, p2=p2.num, p3=p3.num)
 File "/root/code/alphageometry/numericals.py", line 409, in __init__
   center = line_line_intersection(l12, l23)
 File "/root/code/alphageometry/numericals.py", line 586, in line_line_intersection
   raise InvalidLineIntersectError
numericals.InvalidLineIntersectError```

does anyone know if this is a known bug in DDAR?

I also encountered this problem in the IMO problem. Have you solved this problem?


fix: sidecar back/forward should be ordered by visitation rather than insertion

Fixes #4746

Description of what you did:

My PR is a:

[ ] 💥 Breaking change
[x] 🐛 Bug fix
[ ] 💅 Enhancement
[ ] 🚀 New feature

Please confirm that your PR fulfills these requirements

[x] Multiple commits are squashed into one commit.
[x] The commit message follows Conventional Commits, which allows us to autogenerate release notes; e.g. fix(plugins/plugin-k8s): fixed annoying bugs
[x] All npm dependencies are pinned.

this is a great fix, thanks.
with your PR, the forward button won’t be displayed if there is no back? so we may have a “< default / Pod / nginx”?
i think we need to have either no buttons visible, or both (with possible one or the other disabled)
otherwise, as i click back and forth, the place i have to click, e.g. to continue going forward may change
scenario: say i’m at the beginning: i click forward in “slot 1”. now, to continue forward, i need to move my mouse to “slot 2", because (now) the back button is also visible.

solved, thanks!


Help with anticheats?

So like 2 days ago i asked for a help becouse osiris doesnt work on community servers. So after some digging i realised that it has to do with anticheat on one server.(in other servers it works great) So if anyone have some tips on how to bypass it let me know <3

https://github.com/JDW1337/AntiDLL
EventListener::EventListener() noexcept
{
    assert(interfaces);

    // If you add here listeners which aren't used by client.dll (e.g., item_purchase, bullet_impact), the cheat will be detected by AntiDLL (community anticheat).
    // Instead, register listeners dynamically and only when certain functions are enabled - see Misc::updateEventListeners(), Visuals::updateEventListeners()

    const auto gameEventManager = interfaces->gameEventManager;
    gameEventManager->addListener(this, "cs_win_panel_match");
    gameEventManager->addListener(this, "round_start");
    gameEventManager->addListener(this, "round_freeze_end");
    gameEventManager->addListener(this, "player_hurt");
    gameEventManager->addListener(this, "player_death");
    gameEventManager->addListener(this, "vote_cast");

    if (const auto desc = memory->getEventDescriptor(gameEventManager, "player_death", nullptr))
        std::swap(desc->listeners[0], desc->listeners[desc->listeners.size - 1]);
    else
        assert(false);
}

this used to be in the osiris source, it bypassed the anticheat but it was removed at some point idk when


clean up card status

Move all card status logic to <esphome-card>.
Move 'highlight' to be shown as a status for 10 seconds
Automatically highlight any new device added after first render (import/wizard/new file on disk)
automate the status color for a second to draw attention
Move status text slightly up

https://user-images.githubusercontent.com/1444314/138026978-59285c04-fb92-4bb0-a775-4f9456087166.mp4

I am only going to respond to feedback related to the changes in this PR. If you have any other comments, feel free to open an issue.

Moving the label down and pushing long headers to a second line means that cards will shift around because all of a sudden the text is broken down.
I'll changed the word "highlight" to "new"
I'll play with the popping of the card

For comparison, this is the current highlight feature in ESPHome dashboard:
https://user-images.githubusercontent.com/1444314/138116198-ee998443-fd4b-435e-9228-424673e5124c.mp4


⚠ Bofrost.de has degraded performance

In 67fdf9c, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 1426 ms

Resolved: Bofrost.de performance has improved in 711dc6c after 6 minutes.


SFCP <Error: Unknown lstring ID XXX>

Since the newest update, 1.9.71, and this is with a freshly downloaded SFCP, there are hundreds of <Error: Unknown lstring ID XXX> errors when looking in XEdit. Just about all worldspace, cells, and other overrides.

Details
Since the newest update, 1.9.71, and this is with a freshly downloaded SFCP, there are hundreds of <Error: Unknown lstring ID XXX> errors when looking in XEdit. I fixed a lot of them in my copy, but there was no fixing things like NPCs. Things like Red Harvest Double Malt Whiskey are coming up as Volii Hotel. Seems there is a database record sequence mismatch.
Game Version
<IP_ADDRESS>
New Game
Yes
Reproduction Steps
Updated to 1.9.71, open in XEdit by itself and look.

This can be closed out as non-issue. Corrupted ver 1.9.71 Bethesda BA2 from their update. Verified game files and it pulled a new one down.


fix: LEAP-466: Don't sanitize text tasks monorepo

Hi @hlomzik!
This PR was created in a response to PRs in upstream repos:

https://github.com/HumanSignal/label-studio-frontend/pull/1646

closing this as monorepo was merged to develop branch


Patch 1

If I have nested ENV variables it is not populated
FIRST_NAME="Joe"
SURNAME="Doe"
FULL_NAME="${FIRST_NAME} ${SURNAME}"

It should combine
source .env && echo $FULL_NAME
Joe Doe

I'll defer to @pcattori here but I think our original intention with dotenv integration is to provide simple/minimal support out of the box, but if you needed more complex logic you would do that in your custom server/scripts (similar to our stance on remix-server versus a custom express server).  The additional dotenv-expand package could be argued as something that belongs in userland since it's nor part of the built-in/minimal dotenv support.

I fully understand and partially agree. The idea is that: by default env variables works like that by default, but the framework parses env variables differently. As an end user I couldn't understand why it is not working 😔


Add dfid_research_output schema/examples

Has country, dfid_authors, first_published_at
Related PRs
https://github.com/alphagov/specialist-publisher-rebuild/issues/815

🍏


UVI Request

--- UVI JSON ---
{
  "vendor_name": "Linux",
  "product_name": "Kernel",
  "product_version": "versions from v5.4 to before v5.12.11",
  "vulnerability_type": "unspecified",
  "affected_component": "unspecified",
  "attack_vector": "unspecified",
  "impact": "unspecified",
  "credit": "",
  "references": [
    "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=380e0055bc7e4a5c687436ba3ccebb4667836b95",
    "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=9fb088ce13bc3c59a51260207b487db3e556f275"
  ],
  "extended_references": [
    {
      "type": "commit",
      "value": "380e0055bc7e4a5c687436ba3ccebb4667836b95",
      "note": "introduced"
    },
    {
      "type": "commit",
      "value": "9fb088ce13bc3c59a51260207b487db3e556f275",
      "note": "fixed"
    }
  ],
  "reporter": "joshbressers",
  "reporter_id": 1692786,
  "notes": "",
  "description": "KVM: x86: Ensure liveliness of nested VM-Enter fail tracepoint message\n\nThis is an automated ID intended to aid in discovery of potential security vulnerabilities. The actual impact and attack plausibility have not yet been proven.\nThis ID is fixed in Linux Kernel version v5.12.11 by commit 9fb088ce13bc3c59a51260207b487db3e556f275, it was introduced in version v5.4 by commit 380e0055bc7e4a5c687436ba3ccebb4667836b95. For more details please see the references link."
}
--- UVI JSON ---

This issue has been assigned UVI-2021-1001041