Investigate why bookinfo + istio supports low qps

In the rate limit e2e tests we have seen often that on a low cpu cluster, we can only drive 2 qps traffic.
We uses to run the test with 30+ qps before.
https://github.com/istio/istio/pull/676
temporarily lowers the rate limit in tests.

in the simplified env there is no regression, on the contrary there is significant improvements compared to 0.1

what remains for this?  Sounds like you are saying performance is better than 0.1.  curious to see any comparison table/chart you have.

there is a ton of work there - I have some tooling  (fortio) and some setup (the one described in istio/istio/devel/README.md#local) and I've had ongoing PR to keep that setup working, I'll rerun the tests once we have the next build (but again it's only very basic and we need more people looking at that,  it's going to be one of the top focus area for 0.3)

With only 4 simultaneous connection and on a shared cluster I can get:
W0927 01:51:59.298] All done 5123 calls (plus 4 warmup) 7.812 ms avg, 511.8 qps
so I'm closing this for 0.2


fix: allow configuration of logging paths and defaults to stdout

Adds a logging option function for configuring logging paths.
Description
defaults to stdout
References

fixes #1801
Review Checklist

[ ] I have clicked on "allow edits by maintainers".
[ ] I have added documentation for new/changed functionality in this PR or in a PR to openfga.dev [Provide a link to any relevant PRs in the references section above]
[x] The correct base branch is being used, if not main
[ ] I have added tests to validate that the change in functionality is working as expected

Is there any case we want to write to stderr even when system is configured for writing to stdout?

Is there any case we want to write to stderr even when system is configured for writing to stdout?

You have a couple of options:

add both "stderr" and "stdout" as values for the option (it will log to both)
redirect the process stdout to stderr.

In order to conditionally log to different outputs, you would need to configure separate logging cores and pass them to a tee logging core.


OpenSSL 1.1.1 - makefile Syntax Error

I configured openssl correctly, then ran make, then got this error:
makefile:66: *** missing separator.  Stop.
My configuration:
Command line (with current working directory = .):
C:\Perl64\bin\perl.exe Configure VC-WIN64A

Perl information:
C:\Perl64\bin\perl.exe
5.28.1 for MSWin32-x64-multi-thread

Enabled features:
aria
asm
async
autoalginit
autoerrinit
autoload-config
bf
blake2
camellia
capieng
cast
chacha
cmac
cmp
cms
comp
ct
deprecated
des
dgram
dh
dsa
dso
dtls
dynamic-engine
ec
ec2m
ecdh
ecdsa
engine
err
filenames
fips
gost
idea
legacy
makedepend
md4
mdc2
module
multiblock
nextprotoneg
pinshared
ocb
ocsp
padlockeng
pic
poly1305
posix-io
psk
rc2
rc4
rdrand
rfc3779
rmd160
scrypt
secure-memory
seed
shared
siphash
siv
sm2
sm3
sm4
sock
srp
srtp
sse2
ssl
static-engine
stdio
tests
threads
tls
ts
ui-console
uplink
whirlpool
tls1
tls1-method
tls1_1
tls1_1-method
tls1_2
tls1_2-method
tls1_3
dtls1
dtls1-method
dtls1_2
dtls1_2-method

Disabled features:
afalgeng            [not-linux] OPENSSL_NO_AFALGENG
asan                [default]   OPENSSL_NO_ASAN
buildtest-c++       [default]
crypto-mdebug       [default]   OPENSSL_NO_CRYPTO_MDEBUG
devcryptoeng        [default]   OPENSSL_NO_DEVCRYPTOENG
ec_nistp_64_gcc_128 [default]   OPENSSL_NO_EC_NISTP_64_GCC_128
egd                 [default]   OPENSSL_NO_EGD
external-tests      [default]   OPENSSL_NO_EXTERNAL_TESTS
fuzz-libfuzzer      [default]   OPENSSL_NO_FUZZ_LIBFUZZER
fuzz-afl            [default]   OPENSSL_NO_FUZZ_AFL
ktls                [default]   OPENSSL_NO_KTLS
md2                 [default]   OPENSSL_NO_MD2 (skip crypto\md2)
msan                [default]   OPENSSL_NO_MSAN
rc5                 [default]   OPENSSL_NO_RC5 (skip crypto\rc5)
sctp                [default]   OPENSSL_NO_SCTP
ssl-trace           [default]   OPENSSL_NO_SSL_TRACE
trace               [default]   OPENSSL_NO_TRACE
ubsan               [default]   OPENSSL_NO_UBSAN
unit-test           [default]   OPENSSL_NO_UNIT_TEST
weak-ssl-ciphers    [default]   OPENSSL_NO_WEAK_SSL_CIPHERS
zlib                [default]
zlib-dynamic        [default]
ssl3                [default]   OPENSSL_NO_SSL3
ssl3-method         [default]   OPENSSL_NO_SSL3_METHOD

Config target attributes:
AR => "lib",
ARFLAGS => "/nologo",
AS => "nasm",
ASFLAGS => "-g",
CC => "cl",
CFLAGS => "/W3 /wd4090 /nologo /O2",
CPP => "\$(CC) /EP /C",
HASHBANGPERL => "/usr/bin/env perl",
LD => "link",
LDFLAGS => "/nologo /debug",
MT => "mt",
MTFLAGS => "-nologo",
RANLIB => "CODE(0xe0d1a0)",
RC => "rc",
aroutflag => "/out:",
asflags => "-Ox -f win64 -DNEAR",
asm_arch => "x86_64",
asoutflag => "-o ",
bin_cflags => "/Zi /Fdapp.pdb",
bin_lflags => "/subsystem:console /opt:ref",
bn_ops => "SIXTY_FOUR_BIT",
build_file => "makefile",
build_scheme => [ "unified", "windows", "VC-common" ],
cflags => "/Gs0 /GF /Gy /MD",
coutflag => "/Fo",
cppflags => "",
defines => [ "OPENSSL_BUILDING_OPENSSL", "OPENSSL_SYS_WIN32", "WIN32_LEAN_AND_MEAN", "UNICODE", "_UNICODE", "_CRT_SECURE_NO_DEPRECATE", "_WINSOCK_DEPRECATED_NO_WARNINGS" ],
disable => [  ],
dso_cflags => "/Zi /Fddso.pdb",
dso_scheme => "win32",
enable => [  ],
ex_libs => "ws2_32.lib gdi32.lib advapi32.lib crypt32.lib user32.lib",
includes => [  ],
ldoutflag => "/out:",
lflags => "",
lib_cflags => "/Zi /Fdossl_static.pdb",
lib_cppflags => "",
lib_defines => [ "L_ENDIAN" ],
module_cflags => "",
module_cxxflags => undef,
module_ldflags => "/dll",
mtinflag => "-manifest ",
mtoutflag => "-outputresource:",
multilib => "-x64",
perl_platform => "Windows::MSVC",
perlasm_scheme => "auto",
rcoutflag => "/fo",
shared_cflag => "",
shared_defflag => "",
shared_defines => [  ],
shared_ldflag => "/dll",
shared_rcflag => "",
shared_target => "win-shared",
sys_id => "WIN64A",
thread_defines => [  ],
thread_scheme => "winthreads",
unistd => "<unistd.h>",
uplink_arch => "x86_64",

Recorded environment:
AR =
ARFLAGS =
AS =
ASFLAGS =
BUILDFILE =
CC =
CFLAGS =
CPP =
CPPDEFINES =
CPPFLAGS =
CPPINCLUDES =
CROSS_COMPILE =
CXX =
CXXFLAGS =
HASHBANGPERL =
LD =
LDFLAGS =
LDLIBS =
MT =
MTFLAGS =
OPENSSL_LOCAL_CONFIG_DIR =
PERL =
RANLIB =
RC =
RCFLAGS =
RM =
WINDRES =
__CNF_CFLAGS =
__CNF_CPPDEFINES =
__CNF_CPPFLAGS =
__CNF_CPPINCLUDES =
__CNF_CXXFLAGS =
__CNF_LDFLAGS =
__CNF_LDLIBS =

Makevars:
AR              = lib
ARFLAGS         = /nologo
AS              = nasm
ASFLAGS         = -g
CC              = cl
CFLAGS          = /W3 /wd4090 /nologo /O2
CPP             = $(CC) /EP /C
CPPDEFINES      =
CPPFLAGS        =
CPPINCLUDES     =
CXXFLAGS        =
HASHBANGPERL    = /usr/bin/env perl
LD              = link
LDFLAGS         = /nologo /debug
LDLIBS          =
MT              = mt
MTFLAGS         = -nologo
PERL            = C:\Perl64\bin\perl.exe
RC              = rc
RCFLAGS         =

NOTE: These variables only represent the configuration view.  The build file
template may have processed these variables further, please have a look at the
build file for more exact data:
makefile
build file:
makefile

build file templates:
Configurations\common0.tmpl
Configurations\windows-makefile.tmpl
Configurations\common.tmpl

Why is this happening?

Would you mind attaching your makefile so we can see?

makefile.txt
here it is

makefile:66: *** missing separator. Stop.

This looks rather like the error I might expect to see if you use a GNU version of make instead of the MSVC nmake with a Windows makefile (and in fact you say in your first sentence that you ran make - which is unexpected). If you use the VC-WIN64A configure target then you are supposed to use MS tools all the way.

and in fact you say in your first sentence that you ran make - which is unexpected

Oh!  Good catch, I didn't notice that.  Yup, that's sure to be the answer, please use nmake

Yes, this worked. The solution was to use nmake.


Scroll bar should not be moved away from window edge

When in Zen mode, the scroll bar is moved to the edge of the text area. It would be better if it stayed at the edge of the window, to make it easier to click on according to Fitt's Law.
One possible way to implement this would be to remove the right-hand margin entirely (for LTR text with soft-wrapping disabled, at least).

agreed.  this is really jarring

Sadly, with the way Atom's layout is structured internally, this is extremely hard to do.


Initialize a g8 template

Initializes a giter8 template with kenesis lambda example.

For #251

Template repositories can reside on GitHub and should be named with the suffix .g8.

http://www.foundweekends.org/giter8/usage.html#Usage
Woops, I didn't know this :) I guess I better setup a new repo.

@abhishekshree sorry, would you mind re-targeting to here? Thanks!
https://github.com/typelevel/feral.g8


How to set parameter for svg "width"  and "height"

How to set parameter for svg "width"  and "height"? Thanks!

#44 check my answer.

Answered.


chore(master): release 0.23.4

:robot: I have created a release beep boop
0.23.4 (2022-05-18)
Bug Fixes

deps: update dependency fs-extra to v10 (96c9220)

This PR was generated with Release Please. See documentation.

Coverage remained the same at 75.929% when pulling 409829a526f9a3f82ed8bbc17525e53e07e268a6 on release-please--branches--master--components--docusaurus-search-local into 2fe3ae3689a5987c3e1dadd2d8c9a15e45c27ef2 on master.


I can't boot my windows now.

I got stuck at debug... And i can't boot to windows.😭

Please i need help!!!! How i can fix this?! Space bar not working, any key.... Nope, and i tried with bootrec /fixmbr or /rebuildbcd, but doesn't work

I fixed that, if someone will have trouble with this software, you need something that can read \EFI\ system folder and when you edit config of HackBGRT use a program to BE SURE the C: drive has id of Basic Data and not UEFI System....

There is far simpler solution:
1)create USB drive with windows 10 installer
2)go to windows 10 instalation
3)repair
4)comand prompt
here:
format (letter of drive you ASSIGNED to efi partition): /FS:FAT32
bcdboot (lerrer with windows instalation partition):\windows /s (efo letter): /f UEFI

@Leouch1
i tried to use that solution, did worse.


Added chaos experiment documentation guidance

Lines 34-52, added guidance for documenting chaos experiments and underlined the importance of hypothesis

@prasha-microsoft
Can you review the proposed changes?
Important: When the changes are ready for publication, adding a #sign-off comment is the best way to signal that the PR is ready for the review team to merge.
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

#sign-off


shortcut leads to eclient.pyw

shortcut created by installer leads to eclient.pyw but its just path leading to and python file so that shortcut should contain
pythonw C:/path/path/path/eclient.pyw

or you should make it run an executable like this:
#include <windows.h>

int main() {
    // script to run
    char *command = "pythonw.exe eclient.pyw";

    PROCESS_INFORMATION pi;
    STARTUPINFO si;

    ZeroMemory(&si, sizeof(si));
    si.cb = sizeof(si);
    ZeroMemory(&pi, sizeof(pi));

    if (CreateProcess(NULL, command, NULL, NULL, FALSE, CREATE_NEW_PROCESS_GROUP | DETACHED_PROCESS, NULL, NULL, &si, &pi)) {
        CloseHandle(pi.hProcess);
        CloseHandle(pi.hThread);

        // TerminateProcess(GetCurrentProcess(), 0);
        return 0;
    } else {
        return 1;
    }
}

just compile and make shortcut point to it and thats it

ok I'll look into it. Thanks!


Often ThemeShadow breaks and appears on top of elements

Describe the bug

It seems that in classic UWP apps ThemeShadow often breaks, appearing on top of elements using it, such as MenuFlyouts and other popups.
Unfortunately I don't have a pattern to reproduce this issue, but as a user I get this state multiple times per week.
Sometimes it is enough to restart the affected app, other times it happens system wide and you have to reboot the whole PC.
Expected behavior

Shadow appears below the context menu and not on top.
Screenshots

Version Info

Windows 10 version
Saw the problem?

Insider Build (xxxxx)

October 2020 Update (19042)
Yes

May 2020 Update (19041)

November 2019 Update (18363)

May 2019 Update (18362)

October 2018 Update (17763)

April 2018 Update (17134)

Fall Creators Update (16299)

Creators Update (15063)

Device form factor
Saw the problem?

Desktop
Yes

Xbox

Surface Hub

IoT

@FrayxRulez more details on when this happens/repro steps would be useful. Are you saying restarting fixes the issue ? That makes me wonder if this is a rendering issue.

Unfortunately I don’t have any repro steps at the moment, maybe @makisukurisu does, as it seems to happen way more frequently to him than to me.
In most circumstances relaunching the app app is enough, but sometimes a whole OS restart is required, yes.

@FrayxRulez more details on when this happens/repro steps would be useful. Are you saying restarting fixes the issue ? That makes me wonder if this is a rendering issue.

This is a known issue, its been brought up many times before.
Supposedly the base popup was adjusted to fix this, or it was said to be investigated.

Using ambie, it is very easy to reproduce. Is there any known work around for this issue?
https://user-images.githubusercontent.com/16918354/120662975-2ba40f80-c4bc-11eb-9d67-2846fdfb329b.mp4
cc @dpaulino

Yes this happens super often. I never found a specific set of reproduction steps though. In general, just open the fly outs repeatedly, and at some point that bug appears. Really annoying.

It seems to happen a lot in the MUXTestApp when using the CommandBarFlyout test pages

Next time you hit this, can you try restarting explorer.exe to see if that fixes the issue?

@ranjeshj I think I just discovered consistent reproduction steps.

Clone Ambie White Noise https://github.com/jenius-apps/ambie
Run the app. It's a uwp app.
Click the timer button at the top right corner (green arrow on the left in the screenshot)
Then click the ... button near it (orange arrow on the right in the screenshot)

Observe the ... context menu has the broken shadow bug.

Here's another gif showing the bug. You can see that the first time I open ..., the bug isn't present. But after I open the timer menu, the bug is present.

These steps reproduce in Ambie's main branch and in the production release from the store.

@codendone Restarting explorer.exe doesn't fix the issue for me.

Ping. Can I provide more information for this?

@HppZ not he same issue: #5277

@StephenLPeters was this fixed by WinUI 2.6.1?

This might be MSFT:33411893, though that might be Win11+ only builds.

Now that XAML Controls Gallery <IP_ADDRESS> uses WinUI 2.6.1, I can confirm that this was NOT fixed.

@Poopooracoocoo I haven't been able to reproduce this in XCG, can you confirm the steps you are taking to see the issue?

@StephenLPeters on W10 v20H1, I went to the CommandBarFlyout sample and right clicked on the image.

Tracked internally as MSFT:34857240.

Does anyone know a way to deativate the shadows? This issue creates terrible usability. I looks like the items are greyed out and thus misleads the user to assume the option is not available.

FWIW it looks like MSFT:34857240 was fixed sometime around Windows build 22445. MSFT:33411893 got duped to MSFT:34432192, and that looks like it's fixed in all Windows 11 builds? So this might just be fixed OS-side.


Update the way we detect windows versions

While running the agent on Windows 10 I noticed we were submitting the version as "Windows version 6.2", which maps to windows 8.
According to MSDN, the GetVersion call we're using always reports windows 8 for compatibility reasons:

GetVersion may be altered or unavailable for releases after Windows 8.1.
Instead, use the Version Helper functions. For Windows 10 apps, please see
Targeting your applications for
Windows.
With the release of Windows 8.1, the behavior of the GetVersion API has changed
in the value it will return for the operating system version. The value
returned by the GetVersion function now depends on how the application is
manifested.
Applications not manifested for Windows 8.1 or Windows 10 will return the
Windows 8 OS version value (6.2).

Adding a manifest seems to involve embedding XML in the executable, which doesn't sound like fun.
Lucky for us there's an alternative syscall that doesn't lie about the version: RtlGetVersion.
I've tested this on:

Windows 10 (1909) and it reports version "10.0".
Windows 7 and it reports "6.1"

MSDN says RtlGetVersion is available from Windows 2000.

One thing this doesn't address is detecting the difference between server and non-server versions of windows.
According to wikipedia, a major.minor of "10.0" can mean windows 10, but it can also mean:

Windows Server 2016
Windows Server 2019
Windows Server, version 1903
Windows Server, version 1909
Windows Server, version 2004

:shrug:

I just noticed last night that Buildkite was reporting my Windows 10 agent as Windows 8, and was going to look into it.
Thanks!

Seems good on my Windows 10 Pro machine…
Before:

After:


Feat/building solar potential info windows

#368

show info windows for building solar potential layers on hover

#368

show info windows for building solar potential layers on hover

Is that window scrollable? Shouldn't it just expand to the needed height or are there too many properties to show?

Is that window scrollable? Shouldn't it just expand to the needed height or are there too many properties to show?

Yes it is scrollable. It takes a big part of the map's height and then gets scrollable if more elements / properties are available.


Not found route configuration

I would like to be able to specify the not found route in this way:
const routes = {
  component: App,
  childRoutes: [],
  indexRoute: {
    component: Home
  },
  notFoundRoute: {
    component: NotFound,
    path: '*'
  },
  path: '/'
}

The relevant part in the example above is the notFoundRoute property. With this property I wouldn't need to make sure this route always need to stay in the end of the childRoutes array. I found some threads on StackOverflow with a NotFoundRoute component but from the documentation I couldn't understand if that still exists and if there is an equivalent for it in the object config structure.
What do you think? Thank you!

We discussed this on https://github.com/reactjs/react-router/issues/3212 and decided to not do this – it's just not an interesting enough special case of the current API, which handles things quite well enough.


Add Missing Endpoints for non-public clouds

We are missing the OSSRDBMS endpoint for China & the ADO endpoint for Us Gov/China in our providerSettings.ts file.

[ ] OSSRDBMS endpoint - China
[ ] ADO Endpoint - US Gov
[ ] ADO Endpoint - China

These endpoints don't exist in any documentation, closing


(Fix) Set deploymentStep when starting step four

Fixes #593 (the underlying issue).
Switching networks may cause a lot of issues, and I'm not sure we can (or should) fix them all. For example, if you switch networks in the middle of a deployment, you'll be allowed to continue, but the deploy will of course fail.
I guess we could save the id of the network where the deployment started, and alert the user that they are in a different network. But I wouldn't try anything more clever than that (for example, persisting different incomplete deployments in the local storage according to the network that is being used).

Pull Request Test Coverage Report for Build 1593

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

Totals

Change from base Build 1590:
0.0%

Covered Lines:
258

Relevant Lines:
1955

💛  - Coveralls


Add a Ranking Chart of comparable countries to International Dashboard

YFF will be conducting analysis to determine a list of comparable countries to rank UK performance against
Once they have produced a list of countries and provided a description of their inclusion criteria, we will build a ranking chart to show how the UK performs in each data layer. A ranking chart will be shown for each dataset.

Closing #322 as completed:


Expand button

Description
This PR resolves #321 by adding a button to explicitly expand the layer properties. As requested by @jni it preserves the option to doubleclick elsewhere inside the the layer properties to toggle the expansion.
Right now the PR is still in progress as I need help from our style and icon guru @freeman-lab to improve the icon. I have a "sandwhich bar" in there right now but I think I might switch to up / down triangles. Open to other suggestions too if people have them.

Type of change

[ ] New feature (non-breaking change which adds functionality)

How has this been tested?

[x] run examples and toggle button

Final checklist:

[x] My PR is the minimum possible work for the desired functionality
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation
[x] I have added tests that prove my fix is effective or that my feature works

I've updated the style of the icon based on a design from @freeman-lab. See below in the gif. This PR is now ready for review.

Hello @sofroniewn! Thanks for updating this PR. We checked the lines you've touched for PEP 8 issues, and found:

In the file napari/layers/_base_layer/view/properties.py:

Line 92:80: E501 line too long (82 > 79 characters)
Line 102:80: E501 line too long (81 > 79 characters)
Line 201:80: E501 line too long (85 > 79 characters)

the black formatting has cause this PR to explode :-(

Line length issue with black has been fixed by replacing max-line-length with line-length in the pyproject.toml and the python 3.7 compatibility mentioned in #328 by using python3 in our pre-commit-config.yaml. This is already to go and I will merge once the tests pass


feat: window.set_ignore_mouse_events

Possibility to click through window.
In case window is transparent I would like to pass it.

any news on this?
would love to swap from electron to tauri for my apps, i basically only need a switch for mouse_events,
would do it manually on mouse enter leave events in js/react of the divs i need the mouse to be enabled, so i dont even need the "auto transparency" - detection :)

I can implement this soon but it won't be exposed in tauri until v2.

would do it manually on mouse enter leave events
But if the mouse events are disabled, then those events wouldn't trigger, so I don't think it's that simple

would do it manually on mouse enter leave events

But if the mouse events are disabled, then those events wouldn't trigger, so I don't think it's that simple

as far as i know electron has something called forwarding .. so you still can "catch" the events manually if u want to, but their default behaviour is disabled
win.setIgnoreMouseEvents(ignore[, options])
ignore boolean
options Object (optional)
forward boolean (optional) macOS Windows - If true, forwards mouse move messages to Chromium, enabling mouse related events such as mouseleave. Only used when ignore is true. If ignore is false, forwarding is always disabled regardless of this value.

^ copied from their docs

I found a hacky way to do this on windows by using windows crate
in cargo.tmol
[dependencies.windows]
version = "0.36.1"
features = [
    "Win32_Foundation",
    "Win32_UI_WindowsAndMessaging",
]

after built a tranparent and topmost window:
let hwnd = window.hwnd().unwrap().0;
let hwnd = windows::Win32::Foundation::HWND(hwnd);
unsafe {
    use windows::Win32::UI::WindowsAndMessaging::*;
    let nindex = GWL_EXSTYLE;
    let style = WS_EX_APPWINDOW| WS_EX_COMPOSITED | WS_EX_LAYERED | WS_EX_TRANSPARENT | WS_EX_TOPMOST;
    let _pre_val = SetWindowLongA(hwnd, nindex, style.0 as i32);
};

It does work!
references:

https://stackoverflow.com/questions/31313624/click-through-transparent-window-no-dragging-allowed-c
https://docs.microsoft.com/en-us/windows/win32/api/winuser/nf-winuser-setwindowlonga
https://docs.microsoft.com/en-us/windows/win32/winmsg/extended-window-styles

I found a hacky way to do this on windows by using windows crate in cargo.tmol
[dependencies.windows]
version = "0.36.1"
features = [
    "Win32_Foundation",
    "Win32_UI_WindowsAndMessaging",
]

after built a tranparent and topmost window:
let hwnd = window.hwnd().unwrap().0;
let hwnd = windows::Win32::Foundation::HWND(hwnd);
unsafe {
    use windows::Win32::UI::WindowsAndMessaging::*;
    let nindex = GWL_EXSTYLE;
    let style = WS_EX_APPWINDOW| WS_EX_COMPOSITED | WS_EX_LAYERED | WS_EX_TRANSPARENT | WS_EX_TOPMOST;
    let _pre_val = SetWindowLongA(hwnd, nindex, style.0 as i32);
};

It does work!
references:

https://stackoverflow.com/questions/31313624/click-through-transparent-window-no-dragging-allowed-c
https://docs.microsoft.com/en-us/windows/win32/api/winuser/nf-winuser-setwindowlonga
https://docs.microsoft.com/en-us/windows/win32/winmsg/extended-window-styles

Can you create a minimal repo with this working?

^interested to see a basic working example too :) @4t145

@NicolaSpadari @slauko
check this repo https://github.com/4t145/tauri-windows-clickthrough-example

I think the repo is private

I think the repo is private

oh I'm sorry about that, it's public now.

In case anyone needs it, it seems easier to do on macos
You need the cocoa & objc crates then you can access the NSWindow via the webview
let main_window = app.get_window("main").unwrap();
main_window.with_webview( | webview | {
  #[cfg(target_os = "macos")]
  unsafe {
    let () = msg_send![webview.ns_window(), setIgnoresMouseEvents: true];
  }
});

Full example:
#[cfg(target_os = "macos")]
#[macro_use]
extern crate objc;

use tauri::{WindowBuilder, Window, Manager};

fn main() {
  tauri::Builder::default()
  .setup(|app| {
    let main_window = app.get_window("main").unwrap();
    main_window.with_webview(|webview| {
      #[cfg(target_os = "macos")]
      unsafe {
        let () = msg_send![webview.ns_window(), setIgnoresMouseEvents: true];
      }
    });
    Ok(())
  })
  .run(tauri::generate_context!())
  .expect("error while running tauri application");
}


pod install error when use in flutter module

I try to build this lib in a flutter module in iOS and got the following error
Running pod install...
CocoaPods' output:
↳
      Preparing

    Analyzing dependencies

    Inspecting targets to integrate
      Using `ARCHS` setting to build architectures of target `Pods-Runner`: (``)

    Fetching external sources
    -> Fetching podspec for `Flutter` from `Flutter/engine`
    -> Fetching podspec for `FlutterPluginRegistrant` from `Flutter/FlutterPluginRegistrant`
    -> Fetching podspec for `flutter_ble_lib` from `Flutter/.symlinks/flutter_ble_lib/ios`

    Resolving dependencies of `Podfile`
      CDN: trunk Relative path: CocoaPods-version.yml exists! Returning local because checking is only perfomed in repo update
      CDN: trunk Relative path: all_pods_versions_2_a_e.txt exists! Returning local because checking is only perfomed in repo update
      CDN: trunk Relative path: Specs/2/a/e/MultiplatformBleAdapter/0.1.3/MultiplatformBleAdapter.podspec.json exists! Returning local because checking is only perfomed in repo update
      CDN: trunk Relative path: Specs/2/a/e/MultiplatformBleAdapter/0.0.4/MultiplatformBleAdapter.podspec.json exists! Returning local because checking is only perfomed in repo update

    Comparing resolved specification to the sandbox manifest
      A Flutter
      A FlutterPluginRegistrant
      A MultiplatformBleAdapter
      A flutter_ble_lib

    Downloading dependencies

    -> Installing Flutter (1.0.0)

    -> Installing FlutterPluginRegistrant (0.0.1)

    -> Installing MultiplatformBleAdapter (0.0.4)
      > Copying MultiplatformBleAdapter from `/Users/yoshi/Library/Caches/CocoaPods/Pods/Release/MultiplatformBleAdapter/0.0.4-1beec` to `Pods/MultiplatformBleAdapter`

    -> Installing flutter_ble_lib (0.0.1)
      - Running pre install hooks
    [!] Unable to determine Swift version for the following pods:

    - `flutter_ble_lib` does not specify a Swift version and none of the targets (`Runner`) integrating it have the `SWIFT_VERSION` attribute set. Please contact the author or set the `SWIFT_VERSION` attribute in at least one of the targets that integrate this pod.

    /usr/local/Cellar/cocoapods/1.8.3/libexec/gems/cocoapods-1.8.3/lib/cocoapods/installer/xcode/target_validator.rb:125:in `verify_swift_pods_swift_version'
    /usr/local/Cellar/cocoapods/1.8.3/libexec/gems/cocoapods-1.8.3/lib/cocoapods/installer/xcode/target_validator.rb:39:in `validate!'
    /usr/local/Cellar/cocoapods/1.8.3/libexec/gems/cocoapods-1.8.3/lib/cocoapods/installer.rb:590:in `validate_targets'
    /usr/local/Cellar/cocoapods/1.8.3/libexec/gems/cocoapods-1.8.3/lib/cocoapods/installer.rb:158:in `install!'
    /usr/local/Cellar/cocoapods/1.8.3/libexec/gems/cocoapods-1.8.3/lib/cocoapods/command/install.rb:52:in `run'
    /usr/local/Cellar/cocoapods/1.8.3/libexec/gems/claide-1.0.3/lib/claide/command.rb:334:in `run'
    /usr/local/Cellar/cocoapods/1.8.3/libexec/gems/cocoapods-1.8.3/lib/cocoapods/command.rb:52:in `run'
    /usr/local/Cellar/cocoapods/1.8.3/libexec/gems/cocoapods-1.8.3/bin/pod:55:in `<top (required)>'
    /usr/local/Cellar/cocoapods/1.8.3/libexec/bin/pod:23:in `load'
    /usr/local/Cellar/cocoapods/1.8.3/libexec/bin/pod:23:in `<main>'

Error output from CocoaPods:
↳
    /System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/lib/ruby/2.6.0/universal-darwin19/rbconfig.rb:229: warning: Insecure world writable dir /Volumes/External/AndroidSDK in PATH, mode 040777

Finished with error: Error running pod install

What Swift version are you using in your application?

Swift 5
I solved this by adding
s.swift_versions = ['4.0', '4.2', '5.0']
to flutter_ble_lib.podspec

Cool, thanks for info! I'll patch it on my end.


renovatebot(deps): update springsecurity to v5.2.0.m3

This PR contains the following updates:

Package
Update
Change

org.springframework.security:spring-security-cas (source)
patch
5.2.0.M2 -> 5.2.0.M3

org.springframework.security:spring-security-config (source)
patch
5.2.0.M2 -> 5.2.0.M3

org.springframework.security:spring-security-core (source)
patch
5.2.0.M2 -> 5.2.0.M3

org.springframework.security:spring-security-crypto (source)
patch
5.2.0.M2 -> 5.2.0.M3

org.springframework.security:spring-security-web (source)
patch
5.2.0.M2 -> 5.2.0.M3

Release Notes

spring-projects/spring-security
v5.2.0.M3
Compare Source

Renovate configuration
:date: Schedule: At any time (no schedule defined).
:vertical_traffic_light: Automerge: Disabled by config. Please merge this manually once you are satisfied.
:recycle: Rebasing: Whenever PR is stale, or if you modify the PR title to begin with "rebase!".
:no_bell: Ignore: Close this PR and you won't be reminded about these updates again.

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

Available now for Enterprise: Renovate Pro with real-time webhook handling and priority job queue.

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.null seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


[Teams Theme] Radio button label should be 12px

Bug Report
Steps
const RadioGroupItemExample = () => (
  <RadioGroup
    items={[
      {
        key: '1',
        label: 'Make your choice',
        value: '1',
      },
      {
        key: '2',
        label: 'Another option',
        value: '2',
      },
    ]}
  />
)

Expected Result
Radio labels are 12px
Actual Result
Radio labels are 14px 💣
Version
0.27.0

According to @codepretty labels should be 14px by default, closing the issue.


fix(ci): re-generate complianceoperator stores

Description
The resources have moved from central/role/resources to pkg/sac/resources, and due to a missed rebase the generated stores for the compliance operator were using the old, non-existing location for resources.
Re-run code gen to re-create the stores to ensure they use the new package location for resources.
Checklist

[ ] Investigated and inspected CI test results
[ ] Unit test and regression tests added
[ ] Evaluated and added CHANGELOG entry if required
[ ] Determined and documented upgrade steps
[ ] Documented user facing changes (create PR based on openshift/openshift-docs and merge into rhacs-docs)

If any of these don't apply, please comment below.
Testing Performed

see CI passing.

Current dependencies on/for this PR:

master

PR #7065   👈

This comment was auto-generated by Graphite.


Planning report is not finished

Perhaps we put it straight into latex?

maybe we should send it to Fredrik now?


Uable to start EIP VM after the host running virtual router VM reboots

After rebooting the host where virtual router VM runs, the EIP VM cannot start with an error "the VIP has been occupied"

fixed in a51a82baafb1963ccd1d26af91178b43c05b6671


RFC: Opt-in Client metrics / telemetry for dev builds on dev machines

Is your feature request related to a problem? Please describe.
During today's incident (need to cross-link) we weren't sure when the Gateways were most recently working
Describe the solution you'd like
Something outside of the logs that allows us to automatically record how the dogfooding is going without any chance for human error or forgetfulness.

More like a set of data points than a string-based log, something you could graph in Prometheus
Not deleted when the logs are cleared
Only used on dev systems, so privacy is not a problem
Machine-readable to find things like, "This new Client is slower" or "Staging quit working at this exact date and time"

This would give us a little bit of visibility / coverage into tricky platform-specific I/O things that are otherwise undertested or impractical to test properly in CI. CI can't do soak tests either.
Describe alternatives you've considered
This could come from the normal logs, but I usually clear my logs dir before replicating an issue, so that information is lost. The logs may also be either too verbose (using debug defaults) or too terse (using release defaults)
Additional context
Add any other context or screenshots about the feature request here.

This might be a lot of work to add to the existing clients running on dev machines. Would #4506 deliver most of the value here?

Let's do #4506 first. But for this I'd like to also catch I/O problems, since I/O for Linux is well-covered and for Windows is almost not covered at all.
Like right now I've still had to turn off my macOS Client because it was interfering with my UTM dev VM and music player. That isn't automatically captured anywhere.

Might schedule later if it seems useful


[Bug]: Header "Veranstaltungen" and "Organisierte Veranstaltungen" is shown without events on profile/organization page

Closed by #491


Promise function is called only once regardless of its arguments

My problem is when I call function wrapped in promiseCache with different arguments I expect it to be executed once for every unique argument. I'm not if it is a bug or I don't use it incorrectly
Here's example: http://jsfiddle.net/apuchkov/7kcs10ef/
var myApp = angular.module('myApp', ['angular-promise-cache']);

myApp
    .factory('myAwesomeModel', function ($http, promiseCache) {
        return {
            getData: function (id) {
                return promiseCache({
                    args: [id],
                    promise: function (id) {
                        $('#log').append('
Making HTTP call for id: ' + id + '
')
                        return $http.get('/echo/json/');
                    }
                });
            }
        };
    })
    .controller('myAwesomeCtrl', function ($scope, myAwesomeModel) {
        myAwesomeModel.getData(1);
        myAwesomeModel.getData(1);
        myAwesomeModel.getData(2); // I expect a second http call here
        myAwesomeModel.getData(2);
    });

Hi @apuchkov
Currently, the correct way to separate caches is by using the key parameter. In the example you posted above, one way would be to add a key argument to the promiseCache({}) method that is unique based on the argument list - such as key: 'pc_' + id

Works well with the key argument. Thanks!


Add .pod6 filetype to Perl6

.pod6 is only used for Perl 6 so there should not be any issues with adding this. Thanks!

Yes, this actually should be classed as Pod. So in other words, $_ (what he said).
@samcv Could you please amend? =)

Well Perl 6 pod has different syntax than Perl pod. And the grammar we use for Perl 6 supports Perl 6 pod. I could add a sample file though.

Still looks like Plain Old Documentation to me. Am I missing something here?
I'm only familiar with Perl 5, sorry.

Here is a sample of how it currently renders pod:
https://gist.github.com/samcv/6ca5fbeac9482d52145b48f8872be3aa
Maybe I should wait until v1.9 of the grammar gets released. I already have it ready to go, but waiting on the only person who has commit access to commit a ton of changes (a few of which are for pod)

Oooh... right. Indented headings, got it. Alright, well... the correct thing to do would be to actually add a new language entry for it. If it's syntactically distinct from Pod, but still related, we can group it using language_group: Pod (so the two languages share the same usage statistics).
Where's this grammar you speak of?

This is where the grammar is: https://github.com/MadcapJake/language-perl6fe
v1.9 fixes these:
Pod

Pod comments now highlight properly working when there is leading whitespace.
Make sure pod after =para and =for immediately stop that block. Make sure formatting doesn't run on further.
Make sure pod after all other abbreviated forms like =head highlight as comments as well.

The documentation on Perl 6 Pod is here: https://design.perl6.org/S26.html
if you are curious.

Well... I see I'm not alone with sending people fruit-baskets of bug fixes. :D Which reminds me, I indirectly promised I'd redeem that awful Perl grammar Atom uses, but I've had my hands full with file-icons. :c

Alright, the results of the .pod6 file search have finished downloading. All-in-all, we're only looking at 52 unique repositories, distributed between 28 unique users... so I'm afraid the usage is too thin to warrant addition as a new language, methinks. I'm a little concerned about how the syntactic differences might skew the classifier, though...
@pchaigno, any input?

Here is an example of a file that is in Perl 6 pod not loading because it thinks it is Perl pod:
https://github.com/perl6/specs/blob/master/S15-unicode.pod
There are lots of Perl 6 pod that are not classified properly because of the .pod extension.
I think the easiest way to distinguish the two is:

Perl 6 Pod: has =begin pod towards the top and contains =end pod
Perl 5 Pod: has =pod and uses =cut to end the pod section

Running perldoc on a file that had =begin pod will show no information at all, since in perl POD that is meant for things like =begin html and isn't used in the documentation.
I have added a change to the heuristics which correctly classifies my added sample and the Perl POD samples. I'm almost totally sure this will not classify any Perl 5 POD incorrectly.

@Alhadis let me know what a search using these changes comes up. Thanks!

Erm, what do you mean? Are you talking about how many results are returned for the .pod6 extension?
Well, it'll be no different to last time, indexing of recent .pod6 files notwithstanding.

There are lots of Perl 6 pod that are not classified properly because of the .pod extension.

Do you mean that Perl 6 pods also use the .pod file extension?

Well Perl 6 pod has different syntax than Perl pod.

Do you have any Perl 6 pod files where the current Pod highlighting doesn't work correctly?

@pchaigno yes, I linked one yesterday but here it is again:
https://github.com/perl6/specs/blob/master/S15-unicode.pod
It doesn't even render anything at all. Totally failing.

And yeah I meant ones that will match with the new changes. Is that possible? I want to make sure the changes to the heuristics don't improperly flag any Perl 5 Pod. But as I said I am almost completely certain they won't, and err on the side of Perl 5 Pod

@pchaigno yes, I linked one yesterday but here it is again:

@samcv Sorry I missed that.
Files on GitHub are rendered (vs. highlighted) using github/markup and the rendering engines it links to. Markup doesn't seem to support Perl6 pod files yet.
However, it uses Linguist to detect the language of files. Thus, we might be able to make it correctly detect such files as Perl6 pod files. At least, they wouldn't be incorrectly rendered and we could highlight them (display the source code instead of trying to convert it to HTML).
In the meantime, you can use Linguist overrides to disable the rendering (by marking these files as Perl6 for instance).

@Alhadis Would you be able to tell how many users and repositories there are for Perl6 pod files? (I haven't had the time to test your new scraping script yet :/)

103 repositories by 74 users.

That list shows a lot of perltoc.pod files. (original POD)
Which will only exist in an installation of Perl 5 because it is a generated file.
( That is those repositories have a full install of Perl 5 in them, binaries and all )
All of the ones with SPPM-Web are also the original POD
podtreeparser is in POD6
All of them that have perl6 in the pathname seem to be POD6
/S26-documentation.pod is POD6
All of them in perl6/specs that showed up in the list are POD6

So take that into account, it's now only 53 repositories among 31 users. Unless we missed many Perl6 pod files, I don't think it will be enough to warrant support.
The best course of action here is to use Linguist overrides to mark these files as Perl6. An alternative would be to add support for highlighting Perl6 pod to Pod::Simple::HTML, which github.com seems to be using.

Adding support for Pod6 to Pod::Simple::HTML is not going to be worth the effort, as it would be effectivily a complete re-write.
About the best thing it could do is if it finds something Pod6-like it could try to use Inline::Perl6 to defer to a Pod6 parser.
Adding support to a Pod6 parser for Pod5 would be much easier.
When Perl 6 broke compatibility to expand its repertoire, it also did so with Pod.
So it has such things as nested blocks, or adding configuration options.
That is Pod6 is mostly a superset of Pos5.
It would also be easier because a Pod6 parser is more likely to be written with the Perl 6 grammar system.

One of the main reasons that Pod6 isn't being used that much is missing support in common tools.
For esample most of the documentation for the only current Perl 6 implementation Rakudo, and the original design docs (superseded) are written in a common subset of both Pod5 and Pod6.
GitHub is now a common tool
almost everything Perl 6 related is on here
most Perl 5 modules are here

I tested the branch in the PR and it says the Perlito and the perltoc.pod are both Pod, not Perl6, so I'm not sure about that. It would probably be fine to mark it as Perl 6 until there is more usage

@pchaigno what's the current status of this?

🏴 Flagging this as stale 🏴

Is there anything blocking this being merged? @pchaigno

The adoption on github.com I'd say (unless @brandonblack or someone else from GitHub staff thinks we should add it anyway...):

So take that into account, it's now only 53 repositories among 31 users. Unless we missed many Perl6 pod files, I don't think it will be enough to warrant support.
The best course of action here is to use Linguist overrides to mark these files as Perl6.

@pchaigno if popularity is the only thing stopping from merging this (plus, I guess, conflicts now), can you please re-check? There's also this github/markup#1173 which could be helped with this. In fact, pod6 files are not recognized as Perl6 now

So we find ourselves in a position of two PRs (this one and https://github.com/github/linguist/pull/4083 spawned out of an early comment in this PR) essentially implementing the same thing, but in slightly different ways in terms of how it will appear to the end user.  As this is the oldest PR, I'm going to use this PR to discuss which approach is best to take.
First, lets address the popularity thing... .pod6 as an extension, is still not sufficiently popular for inclusion. This search returns over 1700 repos which on the face of things, suggests this is popular enough, but if you then look at how these are spread out, it's surprising to discover a mere 22 repos hold all of these files.
A similar search using .pod returns waaaay more results and these are definitely spread across hundreds of repos clearly indicating they're Perl 6 related, so there is definitely a need for classification, but not for the .pod6 extension.
So whichever option we choose, the .pod6 extension will need to be removed from that PR - it can always be added later when popularity grows, if it does.
Now we come to how are we to present this to users?
I'm far from a Perl expert, and certainly don't know the differences between Perl 5 and Perl 6 and Pod (5) and Pod 6, but from what I've read between the two PRs, Pod 6 is quite different from Pod (5) and is considered by the Perl 6 interpreter itself as Perl 6 and not something else like Perl 5/Pod (5).
If my understanding is correct, then I think we should go the route of classifying these files as Perl 6 (ie use this PR) rather than "Pod 6" (ie https://github.com/github/linguist/pull/4083)...
... buuuuuuut, and this is an important but ...
Is this what the Perl community as a whole expect, document or even want?
So sort of written mandate/preference/guideline would definitely help in this matter too.

A similar search using .pod returns waaaay more results and these are definitely spread across hundreds of repos clearly indicating they're Perl 6 related, so there is definitely a need for classification, but not for the .pod6 extension.

Update: I'll need to double-check this ☝. I've just run my local script and I've come up with only 32 repos. @Alhadis does your harvester return different numbers for the same searches?
The discussion of how we present this to users still stands.

I'm not the whole community (obviously), but yes, I think pod 6 is perl 6. It is interpreted by the language itself, and it's available as a data structure ($=pod) for the program; if you want to interpret an external pod 6 file, you run it through the perl 6 interpreter and access that particular variable, which is not simply the text, but the actual structure composed of Pod::Blocks. In fact, #4066 (my very own PR) took that particular approach, although now references to Perl 6 have been removed in favor of accepting this one.

@Alhadis does your harvester return different numbers for the same searches?

😂 I dig that I spent hours polishing formatting, wording, and structure so Harvester's documentation was as clear and concise as possible... and the next user who sees it goes "Alhadis, can you run this for me?" 😢 Really breaks my heart as a Linguist contributor... I don't think this relationship is working out. @pchaigno, our marriage is off.
Kidding, obvs. You'll need to wait for this thing to finish. Speed is throttled because loading anything too quickly causes your server to bark at me and tell me I'm abusing the site. All that hate when I'm just trying to help you guys. 💔

2018-04-09 16:54 GMT+02:00 John Gardner<EMAIL_ADDRESS>
@Alhadis https://github.com/Alhadis does your harvester return
different numbers for the same searches?
😂 I dig that I spent hours polishing formatting, wording, and structure
so Harvester's documentation was as clear and concise as possible... and
the next user who sees it goes "Alhadis, can you run this for me?" 😢
Really breaks my heart as a Linguist contributor... I don't think this
relationship is working out. @pchaigno https://github.com/pchaigno, our
marriage is off.

:-) :-) Happens all the time.

Kidding, obvs. You'll need to wait for this thing to finish. Speed is
throttled because loading anything too quickly causes your server to bark
at me and tell me I'm abusing the site. All that hate when I'm just trying
to help you guys. 💔

Anyway, I think this is really relevant if we are going to keep Pod 6 and
Perl 6 separate (which we should not). As a matter of fact, pod is right
now like 99 to 1 in relation with pod6, but I seem to remember @alhadis
mentioned a way to make them apart in, well, the other PR (and if we keep
jumping from one PR to another and not paying attention to my very own
PR, my marriage to you both is off)

😂 I dig that I spent hours polishing formatting, wording, and structure so Harvester's documentation was as clear and concise as possible... and the next user who sees it goes "Alhadis, can you run this for me?" 😢 Really breaks my heart as a Linguist contributor... I don't think this relationship is working out. @pchaigno, our marriage is off.

I'm 💔 that you mixed me up with your other bit-on-the-side 😆 🤣.
I was just being lazy as I've seen but not looked at your repo and code. I do really appreciate you taking the time to make it public and document it. I've got a bit of time now so will take a peek. 🙇

Ugh, sorry that took so long. 😞 Results for extension:pod begin pod are in @lildude, I haven't deduped any of the files as I normally would. Will leave it to you to decide how to sort them.
Kicking off a search for extension:pod6 begin pod right now...

@lildude Alright, the .pod6 files are uploaded here. Let me know if there's anything else you need. =)

Personally I think locking in anything with "6" in the name is not a good move in the long term. I would suggest avoiding "pod6" and using something different - IMHO something like ".dod", ".dop" or ".zod" - would be better.

To explain the situation
Let's say we have a file that is made up of both Perl5 and POD. When it has an extension of .pod or .POD it should be seen as POD, and otherwise be seen as Perl5.
Similarly a Perl6/POD6 file should be seen as POD6 if it has an extension of .pod .pod6 .POD .POD6, and otherwise as Perl6.
Ideally it would be nice to view a Perl5/Perl6 file also as POD/POD6. I can see why GitHub wouldn't support that, as most programming languages don't have a full fledged documentation format embedded in them. (POD has been used for writing a book)

Ignoring the other extensions, it would be nice if there was some way to always distinguish between POD and POD6 as there can be large semantic differences.
If there was something that is always in POD, and never in POD6, or vice versa, it could be used to determine which to parse it as. (No such luck)
The problem is 99% of POD syntax is valid POD6, and many files could be successfully parsed as either but again with major semantic differences.
A way to fairly reliably guess is to assume neither version and build up a heuristic by looking at which features are used. There are some features in POD that aren't in POD6, and many in POD6 that aren't in POD. If the file starts with =pod or has =cut it is definitely POD, if it starts with =begin pod it is probably POD6. If there is Perl code outside (or inside) of the POD it could also be added to the heuristic. If you see something like =for table  :caption<Table of Contents> it is POD6. If you see an indented =foobar it is probably POD6.
A less reliable way is to assume POD and switch to POD6 if there is a problem parsing it. (Note that a POD6 file starting with =begin pod may successfully result in an empty document if POD is used.)

This is the reason it was requested that .pod6 be added. There would be no confusion with a file that had it as an extension.

As Perl and POD are currently classified separately, I think it would make sense for Perl6 and POD6 to be classified separately. But I have no stake in this other than to make sure that Perl POD files are still correctly classified and rendered. To that end, I just want to make clear that =pod and =cut are not required to be present in a .pod file for it to be valid Perl 5 POD (or even in pod embedded in a Perl file) -- any directive starting with = will activate the POD parser. I seem to recall that github may not render .pod files without a =pod present so that might be a different issue.

2018-04-10 1:34 GMT+02:00 Dan Book<EMAIL_ADDRESS>
As Perl and POD are currently classified separately, I think it would make
sense for Perl6 and POD6 to be classified separately. But I have no stake
in this other than to make sure that Perl POD files are still correctly
classified and rendered. To that end, I just want to make clear that =pod
and =cut are not required to be present in a .pod file for it to be valid
Perl 5 POD (or even in pod embedded in a Perl file) -- any directive
starting with = will activate the POD parser. I seem to recall that
github may not render .pod files without a =pod present so that might be
a different issue.

Adding to the fact that Pod 6 is interpreted by the Perl 6 interpreter
itself is the fact that it can include Perl 6 as a part of it, for instance
as configuration information
https://docs.perl6.org/language/pod#Configuration_information

Yes, but the question is, if it's recognized as a Perl6 file and not a separate type, will github render it as POD6, while still leaving regular Perl6 files just source highlighted?

That's again a completely different kettle of fish. In fact, there's this
PR waiting in perl6/markup https://github.com/github/markup/pull/1173 which
in fact recognizes Pod 6 as Perl 6

Well the totally ideal situation would probably be rendering Pod6 files like how we do Pod. And only rendering it as html if it is named .pod or .pod6. I think if the end goal is to eventually render Pod6 as html, it should probably be its own filetype. Even though Pod6 is valid Perl6, if it is named as .pod or .pod6 the creator is designating that this is documentation and not code. So even though the Perl 6 interpreter is used to render Pod6, that doesn't mean .pod and .pod6 shouldn't be considered documentation.

Much appreciated @Alhadis. Whilst your figures don't match mine, they are very similar and confirm .pod6 as an extension is definitely not popular enough yet.
@samcv you make a very good point and I think you've got to the crux of the matter: this is really about code vs prose. Each are treated differently by Linguist. Code counts towards the repo language stats, prose does not. Accordingly Perl repos with .pod files will not show Pod in the language stats and a repo containing only Pod files will not show Perl or Pod in the language stats.
I think we should do the same for Pod 6 thus making https://github.com/github/linguist/pull/4083 the preferred PR of the two.

I don't think this relationship is working out. @pchaigno, our marriage is off.

I'm keeping the house, you take the boat.

Closing as we've gone for the approach taken in https://github.com/github/linguist/pull/4083 which has just been merged. Thanks everyone. 🙇


Docs: Set color-scheme: dark when in dark mode.

Description
Fixes: 1155
Also fixes a few spelling config issues
Type of change

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[x] Documentation update

How Has This Been Tested?
:has is quite new but this works with latest Safari, Chrome, Edge and Firefox!
Checklist

[x] My code follows the style guidelines of this project
[ ] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes
[ ] Any dependent changes have been merged and published in downstream modules
[ ] I have checked my code and corrected any misspellings

Screenshot - notice dark mode scrollbar:


Patches for BbML

In this PR:

Remove unused components in BBCtx and fix related bugs
Use hint names for type variables if possible instead of using α everywhere
Fix metaprogramming pattern matching related problems
Fix predef type annotations and add missing operators
Update skolem extrusion
Rename bbml prelude file

LGTM. Plz address my one comment and I'll merge.
In a follow-up PR, it would be good to generate human-readable type variable names, instead of ones that include counters. For this, I think you can directly reuse the codegen.js.Scope helper. It's not really specific to JS, so we could move it out of this js sub-package. OTOH type pretty-printing could be considered a form of codegen, so Scope can remain in codegen.

Good suggestions! I will track this in a new issue.


Add a Codacy badge to readme.md

Codecov Report

Merging #1 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master       #1   +/-   ##
=======================================
  Coverage   16.83%   16.83%
=======================================
  Files           7        7
  Lines         303      303
  Branches       36       36
=======================================
  Hits           51       51
  Misses        252      252

Continue to review full report at Codecov.

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

Added this to readme.md manually


Syntax highlighting on windows

Referring back to #7, we ended up disabling syntax highlighting on Windows. This was a bi-product of correcting some exceptions.
It's still not clear why syntax highlighting is no longer working on Windows. If someone could track it down, it would be great!
How syntax highlighting works
We use hljs (highlight.js) which we include in all the code which is pushed into PhantomJS (headless browser). This should action syntax highlighting and it does in the debug HTML output, however for some reason under PhantomJS it's not rendering out the highlights in the final PDF save.
PhantomJS is a headless browser wrapped into a node module, it's used within the html-pdf package we use. It enables us to kick up a browser, push in the html, and get a PDF out afterwards as well as having some header and footer support we make use of.

@BlueHatbRit Hey! I'm really happy to see you're using showdown-emoji which I have just open-sourced and published it (it was on npm for a while but it wasn't on GitHub).
Also, I open-sourced showdown-highlight which uses highlight.js.
I think that will help since it will generate the highlighting on the server, not on the client. Once added, showdown-highlight will convert the code blocks (pre) into highlighted code blocks.
That means we still need the highlight.js CSS, but not the JavaScript on the client.
I don't have a Windows machine around...
Keep up the good work! 👍

@IonicaBizau thanks so much for open sourcing both of those modules. When I get a chance I'll see about bringing in showdown-highlight. That may well fix the issues we're having.
The emoji module is great as well, thanks for opening it up. I might look at contributing some shorthand emoji's when I get a chance.
Thanks bringing all of this to my attention, keep up the good work yourself!

Great! 😁 Thanks for the kind words! ✨

Note to self: When i get time to look at it, it might also be worth me checking out http://prismjs.com/download.html to see if that works as well. Right now I'm leaning towards showdown-highlight if it works well and provides good language coverage.


Specify (absolute) path for library projects

I'm moving this issue here from codeplex:
https://typescript.codeplex.com/workitem/1414
This feature would help to use "library projects" in a way that you only have to specify the actual path once (eg. with a compiler flag).
I'd love to see this implemented in the official compiler. I think it's small work and adds huge value.
I can have a try at adding this but I'd value some guidelines on how to edit the compiler and how it would make it's way to be part of the official compiler.

Coming from a Java background, this doesn't look much different than the java compiler dealing with classes and packages. In Java, you define classes in a packages (e.g.:  in com.foo.bar,SomeClass) and the compiler finds classes referenced by Java code relative to the classpath:  javac  -classpath c:\someproject\classes  c:\anotherproject\MyClass1.java ....
So if MyClass1 imports com.foo.bar.SomeClass, the compiler will look for that class in file c:\someproject\classes\com\foo\bar\Person.class  and anywhere else you put on the classpath.
Similarily, a tsc compiler option could be added:  --referencePath, and the syntax for a reference could be updated to recognize a path relative to this referencePath using some special character that only has meaning if you use the -referencePath option, maybe '@', or something:
/// <reference<EMAIL_ADDRESS>/>
So, with:  tsc -referencePath C:\someproject\main\ts  C:\someproject\test\ts\SomeTypeScript.ts
the typescript compiler would look for Foo.ts in C:\someproject\main\ts\common\util\Foo.ts
No special configuration files are needed for this.  You would just have to tell the compiler the root(s) of your file structure to search for references, and indicate that the path is relative in your  tag in your .ts files.

It is an anti-pattern to put relative paths in source code. When you move or copy code to a different level in the directory hierarchy, it breaks. When you move a library it breaks all source files that reference it. Also, the library path has to be specified somewhere, in order to load the code, so duplicating the paths in the sources violates the DRY principle.
I agree with @mconner, this problem has already been solved in C and other compilers where you can specify include paths. However, it generally doesn't require the sources to specify a variable (such as "{projectA}" or character (such as "@"). The source file specifies a partial path, or just the file name, and the compiler finds it.
As a workaround I am using a "_references.ts" file and avoiding putting reference paths in other sources.
Proposal
I would like to propose two properties to the "tsconfig.json" file.
    "libraries": [
        "/libs/projectA/src",
        "/libs/projectB/src"
    ],
    "references": [
        "/libs/angularjs/angular.d.ts"
    ]

The "libraries" property is similar to @andrewvarga's proposal, but it only defines search paths, not variables for substitution. A source file can reference "/libs/projectA/src/Foo.ts" using:
    /// <reference path="Foo.ts" />

It should be an error if the reference path does not resolve to a single file.
The "references" property works the same as "_references.ts". Having the property in "tsconfig.json" puts all the configuration information together in one place so it is easier to maintain.
What the Compiler Has to Do

Automatically include the reference paths specified in the "references" property, the same as if they had been specified in "_references.ts".
When a reference path is encountered in the source, search relative to the source file location (for backward compatibility), and also relative to the paths in the "libraries" property.

There is a performance impact because the reference path search needs to be exhaustive, in order to catch ambiguous reference errors. However, the exhaustive search only needs to be done if the developer opts in by specifying a "libraries" property. Also, there are many ways the searching could be optimized, and the results can be cached.
There is no impact on generated code, compatibility, or any other features.

The reason I suggested a special character (e.g.: @) is that without it, the path is ambiguous.  Is it from the root (i.e.: relative to one of the specified paths) , or is it relative to the current file.  In Java, it is always from the root (or roots, as defined by the classpath), and so no special character is necessary. But to support both existing relative paths and root-level paths, it would be better to be explicit.  This also reduces the amount of searching that would be necessary, and eliminates an accidental hit (however unlikely) where the author meant one, but got another.

FWIW I made a proof of concept of the fact that tooling can make it easier : https://github.com/TypeStrong/atom-typescript#relative-paths it can do even more over time.

We consider this thing to be outside the scope of tsc, which we generally think of a compiler that does what it needs to and nothing extra. External build systems that understand TypeScript can provide this functionality themselves and provide better flexibility and configurability.
If those external tools settle on a good common pattern that everyone likes, or don't come up with anything at all, we can revisit this post-2.0.

We consider this thing to be outside the scope of tsc, which we generally think of a compiler that does what it needs to and nothing extra.

@RyanCavanaugh - I would really like this to be the case, but the problem is that tsc has already taken on the task of converting ES6 style module imports to AMD style imports. Now that that decision is made, we're kind of stuck with supporting the quirks of AMD module loading, one of which is the lack of support for relative import paths.
I think the best solution would be for TypeScript to split out the *TypeScript to Javascript compiler" from the the "ES6 module to CommonJS/AMD" compiler. Then we could certainly close this issue as out-of-scope. But if that's not he direction the TS team wants to go, I would like to see better support for AMD.

@eschwartz We are looking into solving some of these issues in  #2338, we expect this to be in TypeScript 1.6; can you take a look at the suggestion and let us know if that solves the issues you are running into with AMD?

Banging my head against this issue currently. My scenario:
Code lives in a 'source' folder that is a sibling of the 'typings' folder (from tsd). So all of the reference tags use relative paths to step out of 'source' and into 'typings'. This code is then being deployed via bower, which, by default, dumps the files into a 'bower_components' folder. So now the  type files (*.d.ts) are within 'bower_components\source' and need one more relative step up to get to the 'typings' folder at the root level.
I'll take a look at the suggested transform suggestions above.

Turns out if I leave out the /// <reference> tags altogether the code still compiles as long as the ambient declaration files are given to the compiler or added to tsd.d.ts

That is by design. See http://blog.icanmakethiswork.io/2015/02/hey-tsconfigjson-where-have-you-been.html?m=1 for more about not needing reference tags

it'd be good to have a ~ like .NET .. then at least we could move around files in the directories themselves whilst not having to worry about breaking relative references
eg
/// <reference path="~/tsDefinitions/jQuery.d.ts" />


Clean up shell scripts

Use shellcheck and clean up the warnings reported.  Also, try to bring them into posix compatibility.

Are you referring to the RPM scripts?

post.sh
postun.sh
pre.sh
preun.sh

The only other .sh scripts are the jdk-wrapper.sh (which should be posix, and is externally maintained) and start-kafka.sh used by our test Kafka docker image (not sure I care enough about that to invest into it).

Yep, that's exactly what I had meant.
On Thu, Apr 30, 2020 at 11:55 AM Ville Koskela<EMAIL_ADDRESS>wrote:

Are you referring to the RPM scripts?

post.sh
postun.sh
pre.sh
preun.sh

The only other .sh scripts are the jdk-wrapper.sh (which should be posix,
and is externally maintained) and start-kafka.sh used by our test Kafka
docker image (not sure I care enough about that to invest into it).
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/ArpNetworking/metrics-aggregator-daemon/issues/50#issuecomment-622039264,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAJM5T2UNACFCMBCWLUDRX3RPHCTHANCNFSM4C6BYQBQ
.


Java version 1.1 Proposal

This is what I'd like to release as v1.1
The "new feature" for users is the builder pattern which ensures that the users will only see options that are valid for the configuration they choose to use.
This is based on #230 #245 & #237 and subsumes #243
Each of the preceding commits has its own PR if you want to look at them individually.
I think there are some rough spots in here still, so any recommendations would be greatly appreciated.
Future Plans (for all bindings):
v1.2 --> Visual support
v1.3 --> Mobile support
v2.0 --> Remove Deprecations

note - I might want to pull back in the enum I made for ScreenResolution in #243

note - I might want to pull back in the enum I made for ScreenResolution in #243


Add create quota command

Add a new create quota command, to allow support users to set values for quotas for specific resources.
Example usage:
re create quota --tenant-id abcdefabcdefabcd --quota-kind labels_per_dataset --limit 50

@dan-ri There might have been some confusion - while I agree that it would be nicer in the future to use the tenant name, I think the PR as is it right now works (even if a bit impractical) and would be valuable to merge in itself.
I will not have the time right now to change the API for using the tenant name instead of ID (maybe I will during our next open day!), so I don't think we should block this PR on the API change.


Olm install is broken due to 0.29.0

Bug Report
operator-sdk olm install by default installs the "latest" release, but the "latest" release is broken (0.29.0) and the artifacts are removed. Therefore operator-sdk olm install fails. In my opinion the latest tag should be put back on 0.28.0 so that the install command works by default. (Or use a different tag than latest)

What did you do?
operator-sdk olm install
What did you expect to see?
OLM installation of the latest stable version
What did you see instead? Under which circumstances?
operator-sdk olm install
INFO[0000] Fetching CRDs for version "latest"
INFO[0000] Fetching resources for resolved version "latest"
FATA[0000] Failed to install OLM version "latest": failed to get resources: failed to fetch CRDs: request failed: failed GET 'https://github.com/operator-framework/operator-lifecycle-manager/releases/latest/download/crds.yaml': unexpected status code 404, expected 200; manifests may not exist for this OLM release,please check https://github.com/operator-framework/operator-lifecycle-manager/releases for olm.yaml and crds.yaml

Environment

operator-lifecycle-manager version:
0.29.0

Kubernetes version information:

Kubernetes cluster kind:

Possible Solution

operator-sdk olm install should point to the latest stable version, not a broken release
Additional context
Add any other context about the problem here.

this appears to be a dup of: https://github.com/operator-framework/operator-lifecycle-manager/issues/3419
A release of 0.30.0 is imminent, from what I understand.

Yes. Closing as a duplicate of #3419


Is there anybody who is in charge of this shit?

Hey team, or is there any human beings that can be called as a team?
 It is certain that you guys have no clue or plan to solve this issue.
If you guys dont know how to do it, then just spit it that you are not capable of this.

Really wonder is there a human being who at least feel sort of responsibility on this. Or you guys doing this only for adding a line of fancy career?

This package is a complete joke :)
I don't know how it's backed by Google. I just lost a day trying this, everything is horrible, starting from build failure ending with horrible performance issues, my nice app became an unusable piece of lagging software, even more, saw that there are open issues related to initialization failure, being an async method it made thousands of sessions to fail in production. I  will not risk that with my app. This package shall be reported or flagged somewhere IDK, it's not usable.
P.S. Switched to admob_flutter seems to work ok. If Google is not ready to deliver ads on their own flutter platform, I'm gonna use Facebook ads or another provider.

Please follow up on the original issue.
Closing as this issue doesn't seem to describe a bug or a feature request.


python3Packages.nuitka: 1.1.5 -> 1.8.4

Description of changes
update to the latest stable release and gain support for python3.11
add nix-update-script
changelog:
https://nuitka.net/posts/nuitka-release-18.html

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

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

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

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

[x] Fits CONTRIBUTING.md.

@ofborg build python310.pkgs.nuitka
@ofborg build python311.pkgs.nuitka

Could you also update the format, nativeBuildInputs, propagatedBuildInputs?
I would like to enable pythonImportsCheck and checkPhase.
I could not get the test passed on darwin.
related PRs
https://github.com/NixOS/nixpkgs/pull/242426
https://github.com/NixOS/nixpkgs/pull/253880

Could you also update the format, nativeBuildInputs, propagatedBuildInputs? I would like to enable pythonImportsCheck and checkPhase. I could not get the test passed on darwin.
related PRs #242426 #253880

according to the tests, nuitka is slow. lots of lines like:
CPython took 0.01s vs 1.53s Nuitka.

but tests do pass on x64 linux and #263242 builds and runs. no idea about darwin.

Thanks for adopting my suggestions.
If you can't fix the darwin build, you can mark it as broken since I don't think it works on darwin.

darwin fails with linker errors -- marked as broken.


I'm having some issues I do not know what to do. Minecraft will not open I am using fabric.

I'm having some issues I do not know what to do. Minecraft will not open.
Could I have some help?

downgrade create that mod had an update just now and you need to wait for this mod to update to the latest version

@DrMango14 should I make a separate issue for the update to v0.5.1.j or can you rename this and just use this issue to track the info

just tried overwriting the dependency and from how it seem that might be enough

You shouldn't be downgrading a major mod to satisfy a minor mod's incompatibility. From the looks of it, this developer hasn't been paying attention to their code for some time and certainly not to issues and can't be bothered keeping their versioning up to date with Fabric's requirements. It's a shame because there were nice things in it but if the dev won't put the effort in, why should I?


"Build Number" for PIpelineRuns scoped to the Pipeline

Feature request
Most Integration Services have a concept of a sequential, human-readable build number.
Jenkins has BUILD_NUMBER https://wiki.jenkins.io/display/JENKINS/Building+a+software+project#Buildingasoftwareproject-belowJenkinsSetEnvironmentVariables
Travis has TRAVIS_BUILD_NUMBER https://docs.travis-ci.com/user/environment-variables/
Circle has CIRCLE_BUILD_NUM https://circleci.com/docs/2.0/env-vars/#built-in-environment-variables
Bamboo has bamboo.buildNumber https://confluence.atlassian.com/bamboo/bamboo-variables-289277087.html
This sort of functionality is not currently available in PipelineRuns, and while, timestamps are useful, humans like numbers that they can relate to.
I spoke to a Jenkins user recently, and they use the build-number for tagging artifacts (including image builds), but there's really no similar functionality in Tekton.
Use case
Being able to use something like $(context.pipelineRun.buildNumber) in an environment variable would make this easier.
Presumably the user would control when the sequence resets, and arguably be able to set a specific value on the sequence (similar to database sequences).

To summarize my views on this (based on multiple discussions) : build number sequences are a "user" concept aka what makes a set of pipelinerun or taskrun part of a given sequence is something the user defines, not tektoncd/pipeline.
That said, as of today, it is not possible to emulate that behavior with Tekton, even with https://github.com/tektoncd/community/pull/147 (integration TEP), we need few things to allow such a construct.

Exposing more information as variables, in context : metadata.uid is a really useful one as it defines the unique uid (set by k8s) of the given *Run.
Having a way to pass runtime information and annotation as environment variables (to mimic other tools like Jenkins, travis, …). This is tracked by https://github.com/tektoncd/pipeline/issues/1606#issuecomment-659930760

With those two "fixed", an integration (in the sense of the proposed TEP) or a webhook (or something else) could be responsible for providing those "build number" based on user rules.

I spoke to a Jenkins user recently, and they use the build-number for tagging artifacts (including image builds), but there's really no similar functionality in Tekton.

If you are able to pass the "build number" as parameter to you task, then it is possible. The core question is, who is responsible for defining the sequence. And there, I think it's another component than tektoncd/pipeline itself (same as triggers for event handling for example). That component could be a tektoncd project too :stuck_out_tongue:

Exposing more information as variables, in context : metadata.uid is a really useful one as it defines the unique uid (set by k8s) of the given *Run.

I like the idea of providing a uid - i think the uid feature in triggers has been really useful and I've run into a few places where I've wanted to use it as well.
Particularly recently trying to create a task that does what our end to end tests do:
# Build a resource name based on $E2E_BASE_NAME, a suffix and $BUILD_NUMBER.
# Restricts the name length to 40 chars (the limit for resource names in GCP).
# Name will have the form $E2E_BASE_NAME-<PREFIX>$BUILD_NUMBER.
# Parameters: $1 - name suffix
function build_resource_name() {
  local prefix=${E2E_BASE_NAME}-$1
  local suffix=${BUILD_NUMBER}
  # Restrict suffix length to 20 chars
  if [[ -n "${suffix}" ]]; then
    suffix=${suffix:${#suffix}<20?0:-20}
  fi
  local name="${prefix:0:20}${suffix}"
  # Ensure name doesn't end with "-"
  echo "${name%-}"
}

They use the BUILD_NUMBER from prow to create a unique resource name: but here is where I want to introduce some caution and suggest we want to be careful with this.
If you look at the prow announcements you can see:
November 6, 2017 plank:0.55 provides Pods with the $BUILD_ID variable as well as the $BUILD_NUMBER variable. The latter is deprecated and will be removed in a future version.

There's an indication that BUILD_NUMBER is deprecated and would be removed, back in 2017. Note that in 2020 we are using this today and also there is really no way that Prow can know who is using that variable and for what; and providing it as an environment variable makes this harder b/c it's impossible to say how many scripts/tools/images have been build assuming that variable will exist.
So I want to make sure we are careful not to make things too auto magical and as much as possible enforce Tasks being clear about what they are using and where i came from - which I think something like metadata.uid would allow!

@bobcatfish k8s do create a metadata.uid when a resource is created :upside_down_face:

In my head, I was envisaging some sort of resource that incremented, and that a PipelineRun could reference to get a number from.
I do think that it could be done via an external integration, perhaps annotating the PipelineRun, assuming that we could make annotations available to the context (to be exposed for use), I guess my only concern is that there could be a race, between the external component adding the annotation, and the value being required.

That sounds almost like something that could be the job of the thing creating the PipelineRun, and could be reflected in both the name of the PipelineRun and potentially the parameter.
If we felt like it was the tekton controller's job to keep track of this, it would have to start storing a count of how many runs of each pipeline have occurred, and if we scaled out the controller, they'd need to coordinate between each other to determine the number.
Maybe you can provide more info on your requirements: does it need to be an incrementing number or could a unique id + a timestamp do the trick?

I agree with @bobcatfish - an incrementing number is very hard to get right in a distributed system. I think we can probably make a simpler form of the uid that might be easier to read/remember.


No module named 'requests'

installed via Pip3
$ subscene 'I.May.Destroy.You.S01E06.720p.AMZN.WEBRip.x264-GalaxyTV.mkv'
then got this
Traceback (most recent call last):
File "/usr/local/bin/subscene", line 5, in
from subscene import main
File "/usr/local/lib/python3.8/site-packages/subscene/init.py", line 1, in
from .subscene import *
File "/usr/local/lib/python3.8/site-packages/subscene/subscene.py", line 5, in
import requests
ModuleNotFoundError: No module named 'requests'
PupikMac:~ zoharargaman$ subscene I.May.Destroy.You.S01E06.720p.AMZN.WEBRip.x264-GalaxyTV.mkv
Traceback (most recent call last):
File "/usr/local/bin/subscene", line 5, in
from subscene import main
File "/usr/local/lib/python3.8/site-packages/subscene/init.py", line 1, in
from .subscene import *
File "/usr/local/lib/python3.8/site-packages/subscene/subscene.py", line 5, in
import requests
ModuleNotFoundError: No module named 'requests'

Reinstall now with pip3 install -U git+https://github.com/rnbdev/subscene-dl


UTOPIA-475: Create Artifactory Project b996e6-tools

Description
This PR includes the following proposed change(s):
UTOPIA-475: Create Artifactory Project b996e6-tools
Type of change

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[x] Refactoring / Documentation
[ ] Version change

How Has This Been Tested?
Please describe the tests that you ran to verify your changes.
Development Dependency Working Agreement

[x] My code DOES NOT include the importing of new dependencies into the DPIA ecosystem
[ ] My code DOES include the importing of new dependencies into the DPIA ecosystem
If new dependencies are being introduced to the DPIA ecosystem:
[ ] The functionality of the dependency drastically reduces code complexity and makes my changes more easily maintainable and readible
[ ] The dependency being introduced does not contain multiple layers of nested dependencies introducing maintainability complexity to the DPIA ecosystem

Frontend Development Changes

[x] N/A
[ ] I have performed a self-review of my own code
[ ] I have made corresponding changes to project documentation or diagrams that reflect my changes
[ ] New and existing unit tests pass locally with my changes
[ ] My code follows Airbnb React Style Guidelines

API Development Changes

[x] N/A
[ ] I have performed a self-review of my own code
[ ] My code follows standards and practices outlined in the BC Government API Development Guidelines
[ ] New and existing unit tests pass locally with my changes
[ ] My changes includes Swagger documentation updates that reflect the changes I am introducing

Definition of Done

just testing the one image, removing this after I've proven it works. I didn't want to make changes to our actual pipelines and block your work.


Problem with CSV dialect sniffing

I tested the new behaviour for CSV dialect sniffing introduced for #41 in #42 and discovered the following problems:

The csv.Sniffer().sniff() method will throw a "Could not determine delimiter" error in case it is unsure about a delimiter.
I can not overwrite this behaviour via the CSVKWARGS configuration because it is applied later.

https://github.com/gitonthescene/csv-reconcile/blob/bc723c711232b523d5f0598a39a911ed0619fa35/csv_reconcile/initdb.py#L76
The reason for csv.Sniffer() being unsure about the delimiter is that while reading a fixed chunk of the csv file this chunk might end in the middle of a csv line and therefore the number of delimiters in this line is off.
Working example with whole file:
import csv
csv.Sniffer().sniff("a,b,c\n1,2,3")

Problematic example with only part of the file (throws error):
import csv
csv.Sniffer().sniff("a,b,c\n1,2")

So I would recommend to use dialect sniffing only (or additionaly?) when the user has not given explicit instructions on the dialect via CSVKWARGS and to use csvfile.readline() to avoid having a line cut somewhere.

I could have sworn I tested exactly this case.  Thanks for opening this issue and the example.  I’ll try to work through it and will post back if I have questions.

Actually, did you use the query.zip file referenced in issue #41?  If not, would you mind posting the file you used to reproduce the error and as much detail about how you ran it as you can?

@b2m Would you mind testing develop before I push this out in a patch?

Awesome.  Thanks.  I’ll try to get this out tomorrow.

Fix pushed in new release.


Fix quoting for ParentCommandLine

The quotes are also included in the field value. Should this be a TA fix, instead?

Actually looks like a double tap on the sysmon macro in there too

All fixed in the latest commit


members search: align styling with other sort dropdowns

Closes https://github.com/inveniosoftware/invenio-app-rdm/issues/1697
Screenshots

Closed as we agreed on a different solution.


nest modules to avoid namespace collision with other pypi packages

This needs to be done eventually or we will have problems.

I tend to like using relative imports instead of full imports, but this all seems fine to me. I agree with @auscompgeek 's suggestions, however.

I'm not sure it's worth renaming them - I think the long names help key readers into the fact that those directories are where the actual characterization code is located.  I suppose I could nest them all further in a characterization submodule, but I'm not sure that's worth it.


Feature autodetection environment GitLab

Idea: awesome-ci should detect the environmet automatically, if it's running inside an GitLab CI

implemented


[fix][compile]unused variable

Proposed changes
Issue Number: close #xxx

Error when compiling master
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


Implementation

Reina, I believe that no one could implement this dll to operate in conjunction with your game-server.
I would love to implement this DLL in my language 'Csharp' but we need information on how to do this, is there any particular type of encryption? Could you please give us more information? Taking advantage, congratulations on your project.

Well, you'll can't implement it in c# because I don't think we can use c# class libraries from c++.
About the particular encryption, it's just Pangya encryption nothing more, nothing less.


[Tests] Test cases for Dojo class

Tests all the logic of the Dojo Room Allocation system.

Coverage increased (+9.09%) to 100.0% when pulling 42d5048c74480ca4f6b772fcf224cb545bd34b03 on tests into 91c883317b45b349f9d2ee79ce524d93e0cfd949 on master.


MB-2509 Clean up service items in Support API

Description

Only status and rejectionReason can be updated via UpdateMTOServiceItemStatus. This PR makes all other fields readOnly so it's less confusing to the user and the fields do not appear  in the docs request payload.

Many date-time fields for MTOServiceItem are not used or stored in the database. There is future work planned around these, so for now consensus was to remove them from support.yaml.

Same hold applies to createdAt and updatedAt -- unsure if we want to include these in the payload. Pop automatically creates these in the db, so an easy revert if we decide to use them in the API response.

Added title, error, instance patter for returning 404 from UpdateMTOServiceItemStatus.

Setup
make db_dev_e2e_populate && make server_run

readOnly fields
redoc-cli serve swagger/support.yaml

Observe updateMTOServiceItemStatus section and confirm only status and rejectionReason appear in the request body schema.
Test support/v1/service-items/:mtoServiceItemID/status and confirm it's working and returns the expected payload.

404 Testing

Submit a request with a faulty uuid to support/v1/service-items/:mtoServiceItemID/status and observe the 404 error returned. It should look similar to the following:

{
    "detail": "id: 00000000-0000-0000-0000-000000000000 not found MTOServiceItemID",
    "instance": "17330d5c-3d36-4272-af8a-a41417169f9b",
    "title": "Not Found Error"
}

Code Review Verification Steps

[ ] Have the Jira acceptance criteria been met for this change?

References

Jira story for this change

Messages

:book:
:link: MB-2509

  Generated by :no_entry_sign: dangerJS against e816d4cffedfd84bf9a403532e532e5b11509217


Error when s + enter

I have no error or any problem at all except for when i save snapshot

Hi @rustanacexd,
Thank you for the bug report.
It should work with v0.8.17, let me know if you still encounter this issue.


3.0 refactor/bump version

This commit include :

Version bumps for libs.
new Validation logic.
Refactoring  (now API, Database and Authentication are separate verticle)

Unit test surefire report available at : PR-12_Surefire-Report.pdf


Add Profanify, Lawman and Faker Stripe

Figured I'd get my packages listed here as I'll be adding some issues to them all in the coming weeks, it would be great to try and get some help on them!
Thanks!

Thanks for the speedy merge @ash-jc-allen 🚀

Huge thank you for the contribution! They should be on the live site now 😎


fix(user-admin): handle hashes (#) in user data export to csv

@stdavis - Don't forget to upgrade this package in deq-enviro after this is merged.

Can you explain the issue a bit more?

I tried using new URL((data:text/csv;charset=utf-8,a,b,c#,d') and it puts everything in the hash property. So I think your solution is a fine one.


Load by using a multiget

This should be a workaround for getting calendar information out from the Lark/Feishu systems - see #459
It's not optimized for speed, more work on this later when we get the server quirk hints in place (ref #402)

No unit tests - we'd have to mock up too much.
No functional tests so far as this is only executed with lark and zimbra - but I'll probably fix that later as part of #402


Enable strict EsLint throughout the codebase

I think we should use the EsLint Atom plugin and always fix linting errors before releasing new versions.

Enforcing eslint would be a great start to improving conding style consistency in the code base.
As today eslint reports 42 problems on the master branch, most of them easy to fix.
After we are done fixing the eslint errors and warnings it would also be great if we could adopt a more strict eslint rule set.  Both airbnb and standard are great at enforcing consistency and best coding practices.

eslint reports 42 problems on the master branch

"`npm bin`/eslint" "Components/**/*.js" "Utils/**/*.js" index.js reports 3996 problems (3953 errors, 43 warnings).

We are using Prettier throughout the project, so we won't add Eslint any more.


ActiveRecord Querying

Hey,
Would you think it is valuable to add querying to the gem like user.where(name: 'John')? I'm considering a PR.
Thanks,

Hi there!
Thank you for checking out the gem!
The main purpose of this gem is to have active_record -like associations,
and its currently limited to that purpose.
I think there are already other gems such as rom which may be the one's you are looking for.
I have had the idea to just rename this gem to be
"active_poro-associations" so that the functionality that it provides goes
better with the actual name, and have "active_poro" as a meta-package or
container gem which could incorporate any other features.
This was mainly a project emerged from the need of bidirectional in-memory
associations (sometimes needed in configuration scenarios) and it was kind
of written as a proof of concept. If you would like to add querying I would
suggest perhaps forking this repo and incorporating them separately
(perhaps active_poro-querying), the idea would be that the gems can be used
in little projects and simple scripts independently.
On Sat, May 23, 2015 at 1:37 PM, Ricardo Nacif<EMAIL_ADDRESS>wrote:

Hey,
Would you think it is valuable to add querying to the gem like user.where(name:
'John')? I'm considering a PR.
Thanks,
—
Reply to this email directly or view it on GitHub
https://github.com/codescrum/active_poro/issues/1.

--
Miguel Diaz

                             *
*Code**Scrum   *

Confidentiality Notice: This e-mail message, including any
attachments, is for the sole use of the intended recipient(s) and may
contain confidential and privileged information. Any unauthorized review,
use, disclosure or distribution is prohibited. If you are not the intended
recipient, please contact the sender by reply e-mail and destroy all copies
of the original message.

Thanks for the answer, I got your point, and I have forgot about rom. It really doesn't make much sense. Closing this issue.


Setup Issues template for the repo

Hi @Abhijay007, just wanted to clarify if the instructions in the following link was what was needed to create an issues templates, if yes, can I be assigned to this? Also if you need both a template for the bug report and the feature request? Thank you

Hi @Abhijay007, just wanted to clarify if the instructions in the following link was what was needed to create an issues templates, if yes, can I be assigned to this? Also if you need both a template for the bug report and the feature request? Thank you

@Mikerniker you can do it via using YAML forms, you can refer to the issue templates from this repo here: https://github.com/open-horizon/open-horizon.github.io/tree/master/.github/ISSUE_TEMPLATE, we mainly need issue templates for bug- reports, features-requests, documentation, and for "others",  try to look into the attached resource and edit that according to our repo.

Ok, can you confirm if this is correct: you need 4 YAML files (for bug reports, features, documentation, and others) and these should be stored in the ISSUE_TEMPLATE folder in the .github directory?

Ok, can you confirm if this is correct: you need 3 YAML files (for bug reports, features, documentation and others) and these should be stored in the ISSUE_TEMPLATE folder in the .github directory?

Ok, can you confirm if this is correct: you need 3 YAML files (for bug reports, features, documentation and others) and these should be stored in the ISSUE_TEMPLATE folder in the .github directory?

ya but "others" is different form documentation so 4

Ok, will try to set it up, thanks

Resolved by #95


Say more about filtering options with def in documentation

There is an example of def("DOCS", env.files, { endsWith: ".md" }) in the documentation but there isn't a link or mention of the full set of filters that can be used in that context.

Fixed by https://github.com/microsoft/genaiscript/commit/71f9aedb1d5c1bca3fe320c576196a3a264152b1


class="vue-highcharts" remove rounded corners works in dev, but not in build.

In an attempt to eliminate the round corners, shadows, margins, paddings, etc.  I did this that worked in development mode:
file: custom.css:
.vue-highcharts {
width: 100%;
display: inline-block;
margin: 0;
border: 0px solid rgba(0, 0, 0, 0);
border-radius: 0px;
box-shadow: 0 0 0px rgba(0, 0, 0, 0);
padding: 0px;
background: #fff;
}
result:

but build mode still resulting in this:

which are best practices to style the highcharts-class ?

It seems to custom css does't  work in build mode. Have you check custom css import in build mode?

@Davidriquelme in the last version, I have removed the default styles.


[Remove package] WHONET 5.6

[x] Have you signed the Contributor License Agreement?
[x] Have you checked that there aren't other open pull requests for the same manifest update/change?
[x] This PR only modifies one (1) manifest
[ ] Have you validated your manifest locally with winget validate --manifest <path>?
[ ] Have you tested your manifest locally with winget install --manifest <path>?
[ ] Does your manifest conform to the 1.5 schema?

Note: <path> is the name of the directory containing the manifest you're submitting.

Microsoft Reviewers: Open in CodeFlow

Why is this package being removed?

Why is this package being removed?

Package is not used by many  people.
No one uses winget for installing this package.

https://github.com/microsoft/winget-pkgs/pull/123574#issuecomment-1777727767

#123574 (comment)

This package is for very selected users (Microbiologists).
Also this is old program, it has been replaced by WHONET 2023.
I am the one submitted it to winget-pkgs in the  first place. Most of the Microbiologists don't even know what "winget" is.


Create facet-filter-tags

Facet filters with filter tags

Hey @heatherco, looks like there hasn't been any action taken on these PRs, so we're going to close them out for now. If you'd like these items to be added to the index, please fill out the .yml file and we can reopen the PR. Thanks!


add easier dev tools for starting cstac

Problem
Dev setup is a pain
Solution
Fix by adding a better start option, maybe a vscode script in the future?

I have a shell script that I use to get a dev Coinstac running. Would that work?


Update hashicorp-vault.md

Vault with HA setup does not have kv engine enabled by default, have added step to enable kv engine with correct version and enabling version if already added.
Signed-off-by: Jeet<EMAIL_ADDRESS>

/approve


Robovm purchase information with currency code

In robovm-iOS the retrieved information about a purchase always had null currency code.
I edited the code to built the Information with the given builder instead of the basic constructor.

Doesn't build due to a 500 error from dependency download...

Thanks for the PR! 0.11.1 release is currently being rolled out to Maven central. Also fixed for iOS MOE backend.