Pasting

When pasting an image with alpha color section of an image over an area which is protected but not finished, it will clear the queue and replace that area with what is currently placed down instead of the queue already there.
It should prioritize currently queued pixels when pasting an image with sections of alpha instead of what has been placed down already.

the same issue happens with the queue adder when in the middle of filing an area with queued pixels it clears the queue in favor of what's already on screen in the selected area

the same issue happens with the queue adder when in the middle of filing an area with queued pixels it clears the queue in favor of what's already on screen in the selected area

maybe this one ill keep as a feature with unintended side effects to those who don't understand but I will make a reference to the issue in the tools explanation,  for the paste tool it shouldn't affect the queue status if its an alpha color.


Remove appended newline

For the sake of having a clean api I don't think a newline should automatically be appended to strings to be printed. This would allow for freer use of the library.
Signed-off-by: Grantseltzer<EMAIL_ADDRESS>

I can't merge this as this breaks the package's API. You're free to use custom color.PrintFunc() which  doesn't append it. Thanks


check if the watsonx admin apikey is empty

Description
check if the watsonx admin apikey is empty, currently we only check if it is null.

Release required?

[ ] No release
[x] Patch release (x.x.X)
[ ] Minor release (x.X.x)
[ ] Major release (X.x.x)

Release notes content

Run the pipeline
If the CI pipeline doesn't run when you create the PR, the PR requires a user with GitHub collaborators access to run the pipeline.
Run the CI pipeline when the PR is ready for review and you expect tests to pass. Add a comment to the PR with the following text:
/run pipeline

Checklist for reviewers

[ ] If relevant, a test for the change is included or updated with this PR.
[ ] If relevant, documentation for the change is included or updated with this PR.

For mergers

Use a conventional commit message to set the release level. Follow the guidelines.
Include information that users need to know about the PR in the commit message. The commit message becomes part of the GitHub release notes.
Use the Squash and merge option.

/run pipeline

:tada: This PR is included in version 0.3.2 :tada:
The release is available on:

GitHub release
v0.3.2

Your semantic-release bot :package::rocket:


foobar2000 icon

my contribution :). this should be on the media category

Looks amazing. If you can follow the guide in https://github.com/edent/SuperTinyIcons/blob/master/CONTRIBUTING.md then I'll merge it.

Thanks!


Caught exception: Error: fetching abi for myaccount: Unsupported abi version

I deployed a contract, but when I call back the above error, is it because of my contract version, how do I need to update the contract?

contract

The easiest approach is to use eosio.cdt 1.6.1 to generate the ABI instead of writing it by hand and instead of using the old deprecated (and buggy) ABI generator.


Keyboard hangs for Input widget in Android

Steps to Reproduce
When I type something with the Android keyboard, the keyboard hangs on the key press animation.
Code snippet:
// newRecipient is a field inside a State that is connected to a StatefulWidget

// Text Changed Handler
void _handleInputChange(InputValue input) {
    setState(() {
      newRecipient = input.text;
    });
  }

// Text Input
new Input(
  onChanged: _handleInputChange,
  value: new InputValue(text: newRecipient),
)

Flutter Doctor
[✓] Flutter (on Mac OS, channel master)
• Flutter at /Users/dayang/fuchsia/sysui/third_party/flutter
• Framework revision 9109bb02b9 (6 days ago), 2016-09-15 09:15:11
• Engine revision e9dd3e4e0d
• Tools Dart version 1.20.0-dev.1.0
[✓] Android toolchain - develop for Android devices (Android SDK 23.0.3)
• Android SDK at /Users/dayang/Library/Android/sdk
• Platform android-23, build-tools 23.0.3
• Java(TM) SE Runtime Environment (build 1.8.0_91-b14)
[✓] iOS toolchain - develop for iOS devices (Xcode 7.3)
• XCode at /Applications/Xcode.app/Contents/Developer
• Xcode 7.3, Build version 7D175
[✓] Atom - a lightweight development environment for Flutter
• flutter plugin version 0.2.5
• dartlang plugin version 0.6.39
[✓] Connected devices
• Nexus 6P • 8XV5T15A23006055 • android-arm
Logs and Crash Reports
E/ActivityManager: ANR in com.google.android.inputmethod.latin
E/ActivityManager: PID: 17724
E/ActivityManager: Reason: Broadcast of Intent { act=android.intent.action.SCREEN_OFF flg=0x50000010 }
E/ActivityManager: Load: 0.0 / 0.0 / 0.0
E/ActivityManager: CPU usage from 11020ms to 0ms ago (2016-09-21 15:57:35.279 to 2016-09-21 15:57:46.299):
E/ActivityManager:   71% 900/system_server: 60% user + 11% kernel / faults: 5188 minor
E/ActivityManager:   62% 17724/com.google.android.inputmethod.latin: 53% user + 9.4% kernel / faults: 40406 minor
E/ActivityManager:   19% 4337/com.google.android.gms.persistent: 13% user + 6% kernel / faults: 2245 minor
E/ActivityManager:   8.8% 15886/adbd: 2.6% user + 6.2% kernel / faults: 4851 minor
E/ActivityManager:   8.7% 17635/org.domokit: 5.1% user + 3.5% kernel / faults: 187 minor
E/ActivityManager:   5.2% 356/logd: 1.9% user + 3.3% kernel / faults: 11 minor
E/ActivityManager:   4.8% 15146/android.process.acore: 2.6% user + 2.1% kernel / faults: 347 minor
E/ActivityManager:   3.6% 248/mmcqd/0: 0% user + 3.6% kernel
E/ActivityManager:   3.3% 17610/logcat: 1.6% user + 1.7% kernel
E/ActivityManager:   2.5% 8/rcu_preempt: 0% user + 2.5% kernel
E/ActivityManager:   1.6% 523/jbd2/dm-2-8: 0% user + 1.6% kernel
E/ActivityManager:   1.1% 3/ksoftirqd/0: 0% user + 1.1% kernel
E/ActivityManager:   1% 3880/com.android.phone: 0.5% user + 0.5% kernel / faults: 1 minor
E/ActivityManager:   0.9% 408/servicemanager: 0.2% user + 0.7% kernel
E/ActivityManager:   0.9% 500/dmcrypt_write: 0% user + 0.9% kernel
E/ActivityManager:   0.8% 12/ksoftirqd/1: 0% user + 0.8% kernel
E/ActivityManager:   0.8% 292/msm-core:sampli: 0% user + 0.8% kernel
E/ActivityManager:   0.8% 14746/kworker/u16:4: 0% user + 0.8% kernel
E/ActivityManager:   0.7% 16/ksoftirqd/2: 0% user + 0.7% kernel
E/ActivityManager:   0.6% 41/ksoftirqd/4: 0% user + 0.6% kernel
E/ActivityManager:   0.6% 239/cfinteractive: 0% user + 0.6% kernel
E/ActivityManager:   0.6% 17103/kworker/0:1: 0% user + 0.6% kernel
E/ActivityManager:   0.6% 17989/kworker/u17:6: 0% user + 0.6% kernel
E/ActivityManager:   0.5% 456/irq/215-fc38800: 0% user + 0.5% kernel
E/ActivityManager:   0.5% 3736/com.android.systemui: 0.2% user + 0.2% kernel / faults: 14 minor
E/ActivityManager:   0.5% 17183/kworker/u17:7: 0% user + 0.5% kernel
E/ActivityManager:   0.5% 17299/kworker/2:3: 0% user + 0.5% kernel
E/ActivityManager:   0.4% 17531/kworker/1:0: 0% user + 0.4% kernel
E/ActivityManager:   0.3% 20/ksoftirqd/3: 0% user + 0.3% kernel
E/ActivityManager:   0.3% 436/ksoftirqd/5: 0% user + 0.3% kernel
E/ActivityManager:   0.3% 17130/kworker/u17:5: 0% user + 0.3% kernel
E/ActivityManager:   0.2% 17853/kworker/u17:1: 0% user + 0.2% kernel
E/ActivityManager:   0.1% 35/kworker/u17:0: 0% user + 0.1% kernel
E/ActivityManager:   0.1% 51/system: 0% user + 0.1% kernel
E/ActivityManager:   0.1% 252/irq/224-spdm_bw: 0% user + 0.1% kernel
E/ActivityManager:   0.1% 409/surfaceflinger: 0% user + 0.1% kernel / faults: 1 minor
E/ActivityManager:   0.1% 16937/kworker/u17:2: 0% user + 0.1% kernel
E/ActivityManager:   0% 231/irq/216-tsens_i: 0% user + 0% kernel
E/ActivityManager:   0% 443/ksoftirqd/6: 0% user + 0% kernel
E/ActivityManager:   0% 543/oem_qmi_server: 0% user + 0% kernel / faults: 165 minor 36 major
E/ActivityManager:   0% 3749/wpa_supplicant: 0% user + 0% kernel
E/ActivityManager:   0% 4402/com.android.nfc: 0% user + 0% kernel / faults: 15 minor
E/ActivityManager:   0% 14974/android.process.media: 0% user + 0% kernel
E/ActivityManager:   0% 16947/kworker/u16:2: 0% user + 0% kernel
E/ActivityManager:   0% 17185/com.android.keychain: 0% user + 0% kernel
E/ActivityManager: 28% TOTAL: 18% user + 7.2% kernel + 1.8% iowait + 0.4% irq + 0.4% softirq
E/ActivityManager: CPU usage from 24478357ms to 24478357ms ago (1969-12-31 16:00:00.000 to 1969-12-31 16:00:00.000) with 0% awake:
E/ActivityManager: 0% TOTAL: 0% user + 0% kernel
W/ActivityManager: Scheduling restart of crashed service com.google.android.inputmethod.latin/com.android.inputmethod.latin.LatinIME in 1000ms

It is also important to note that the Flutter app does not crash and is fully functional.

CC @jason-simmons @mpcomplete

Full code is here:
https://github.com/dvdwasibi/modules/blob/email_composer_to_input/packages/widgets/lib/email/editor_recipient_field_input.dart

  value: new InputValue(text: newRecipient),

What happens if you hold the entire input value you receive in the _handleInputChange callback and supply it here instead of extracting the text?  The other fields of the InputValue are important to the Input widget (e.g., they control the selection and editing state of the control).

@abarth that did the trick!
I'll write this up in my FlutterTips doc :)

Is this something we should mention in the API docs for this widget?

Is this something we should mention in the API docs for this widget?

Yes, definitely.

@sethladd
Yes. Well actually, I think more importantly it might be very useful to have some quick code snippets showing the whole text input workflow within a StatefulWidget.
The FlutterChat example was taken down, so I was just doing stuff based on memory on how ReactNative text inputs work (which is pretty much the same pattern, minus the encapsulated InputValue object, which was also what got me).
Here is ReactNative's documentation on input:
https://facebook.github.io/react-native/docs/textinput.html
Input is a pretty vital "UI/functional atom" for most types of apps, so it's a key thing to focus on for documentation and examples.

I think more importantly it might be very useful to have some quick code snippets showing the whole text input workflow within a StatefulWidget.

We can include that in the docs.  :)

@adam, I can work on putting the example in the docs if you have too much on your plate :)

Thanks!

@dvdwasibi thanks! if you're going to add code snippets to the API docs (yay!) we might want to think about https://github.com/flutter/flutter/issues/5992

@sethladd, maybe we should think of putting the examples and explanations in the  Flutter website itself first (and maybe link to it from the Dart Docs)

Input is a "UI atom" that should be a first tier citizen that is exposed early on to users.

sgtm. Let's file a new issue (maybe like "Document input"). We'd definitely accept a Markdown doc talking about our input system, and then you can link to it from the API docs. Good stuff!

Okay cool. There is more flexibility for formatting there too.
On Thu, Sep 22, 2016 at 9:33 AM Seth Ladd<EMAIL_ADDRESS>wrote:

sgtm. Let's file a new issue (maybe like "Document input"). We'd
definitely accept a Markdown doc talking about our input system, and then
you can link to it from the API docs. Good stuff!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/flutter/flutter/issues/5987#issuecomment-248956950,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ADd42GbcmObIKPWe_Tfq55RQ0VP-gRFxks5qsq3jgaJpZM4KDXuF
.

See also #6097

Really hard to tell what to do with this bug.  I suspect we should either open a new one with a specific doc request or just close this as fixed?

This has been solved: the problem was that you should replace the whole InputValue on any change instead of just updating the text field of the InputValue.


gentx json

Please make sure your node is up and running now. Join #validators on Discord for help: https://discord.gg/QeJWCrE.


Improvements

Cherry-pick useful commits from react-native-image-resizer.
Update podspec and gradle.
Support loading image from url on Android.

 Resize image before uploading inspection photos to property


flutter-devicelab-windows-1 test failing with INSTALL_FAILED_INSUFFICIENT_STORAGE

stderr:            adb: failed to install C:\Users\flutter\.cocoon\flutter\dev\integration_tests\flavors\build\app\outputs\flutter-apk\app.apk: Failure [INSTALL_FAILED_INSUFFICIENT_STORAGE: Package couldn't be installed in /data/app/com.yourcompany.flavors-1: Creating application package com.yourcompany.flavors failed]

flavors_test_win_7e41425_2.log

related to https://github.com/flutter/flutter/issues/39925

Phone was cleaned up.


Example: rebase of Change_Index_HTML on master

I think I kinda understand rebase now, and here is a video which illustrates well.


Static lights not working after the scene reload

issue and a repro project: https://forum.playcanvas.com/t/issue-with-static-lights/19233/25

This likely won't get fixed as we're aiming at deprecating static lights, in favour of clustered lighting.


URL Path Support

Hello,
I am trying to use the plugin on Grafana cloud. Will there be support for URL to database instead of absolute file path?
I couldnt find any way to upload afile to Grafana Cloud and provide an absolute path.

found already strated topic in discussions
https://github.com/fr-ser/grafana-sqlite-datasource/discussions/40


Duplicative Adversary Records Are Created

Multiple duplicate MISP Events are created for the same Adversary:

These are evidently duplicated on each run of --adversary

I can't recreate this with the most recent version (the event.info field is compared, with the update being skipped on a match.)  I'm worried there's confusion across the disparate branches.  Working on aligning these to main and then will ask you to retest.

Any estimate on when everything will be aligned to main?

In the meantime which branch should I be using?

In the meantime which branch should I be using?

ver_0.6.2
I'll get this PR put together and reviewed shortly.

Hi @packet-rat -
This PR is merged.  Please update from the main branch, retry adversary import (while adversaries already exist within the MISP instance), and let us know if you're still seeing duplicates?
Thank you! 🙇

Closing as resolved in v0.6.3.  Please reopen this ticket if you encounter this issue again.

No problem.  I’m happy to reload to ensure we are all working from a common baseline.   I suggest that this version/lineage information be annotated in the ‘opening’ Information log entries (I think I created a ticket for the version in beginning of logs [vs. buried in the Banner…]
Patrick Maroney
Principal - Cybersecurity
Chief Security Office
Office:<PHONE_NUMBER> | Cell:<PHONE_NUMBER> | Email<EMAIL_ADDRESS>From: Joshua Hiller @.>
Date: Tuesday, August 30, 2022 at 2:18 AM
To: CrowdStrike/MISP-tools @.>
Cc: MARONEY, PATRICK @.>, Author @.>
Subject: Re: [CrowdStrike/MISP-tools] Duplicative Adversary Records Are Created (Issue #46)
I can't recreate this with the most recent version (the event.info field is compared, with the update being skipped on a match.) I'm worried there's confusion across the disparate branches. Working on aligning these to main and then will ask you to retest.
—
Reply to this email directly, view it on GitHubhttps://urldefense.com/v3/__https:/github.com/CrowdStrike/MISP-tools/issues/46*issuecomment-1231195280__;Iw!!BhdT!iF6mSXaaFbSVWNOo0OBrxlARMEcUqOdHnDVWbWarjO9XST-du7ftq8Mv7vk-s3CrL--_xDS15JbeNZzKjAL77hRUMdo$, or unsubscribehttps://urldefense.com/v3/__https:/github.com/notifications/unsubscribe-auth/AAYSFYN33IX7H3KBMOBMGVTV3WRTRANCNFSM57X5UEUA__;!!BhdT!iF6mSXaaFbSVWNOo0OBrxlARMEcUqOdHnDVWbWarjO9XST-du7ftq8Mv7vk-s3CrL--_xDS15JbeNZzKjAL79_fiLC8$.
You are receiving this because you authored the thread.Message ID: @.***>

FYSA: I have been running v0.6.2

From: Joshua Hiller @.>
Sent: Wednesday, August 31, 2022 3:15:11 PM
To: CrowdStrike/MISP-tools @.>
Cc: MARONEY, PATRICK @.>; Author @.>
Subject: Re: [CrowdStrike/MISP-tools] Duplicative Adversary Records Are Created (Issue #46)
In the meantime which branch should I be using?
ver_0.6.2
I'll get this PR put together and reviewed shortly.
—
Reply to this email directly, view it on GitHubhttps://urldefense.com/v3/__https://github.com/CrowdStrike/MISP-tools/issues/46*issuecomment-1233324933__;Iw!!BhdT!lFGluFa5egqIusjpBaYUqvr38ndu-9EUZZAkNVNcmGON_unAWy8aVMbgQFCWr5g9JGkOpmxC0Lwjd9wWBu4lmE77POU$, or unsubscribehttps://urldefense.com/v3/__https://github.com/notifications/unsubscribe-auth/AAYSFYPEZRS72TPBWQHKNMLV36VL7ANCNFSM57X5UEUA__;!!BhdT!lFGluFa5egqIusjpBaYUqvr38ndu-9EUZZAkNVNcmGON_unAWy8aVMbgQFCWr5g9JGkOpmxC0Lwjd9wWBu4l_dTlXAY$.
You are receiving this because you authored the thread.Message ID: @.***>


Create Allure report for perf tests

This PR adds Allure reports to performance tests, also it removes uploading test results to artifacts (everything should be available in the Allure report)
Output for performance tests: https://neon-github-public-dev.s3.amazonaws.com/reports/pr-2326/release/2934695175/index.html#suites/da6c1eb856842e7b0eacf9ab8c06985f
Flamegraphs are attached as well: https://neon-github-public-dev.s3.amazonaws.com/reports/pr-2326/release/2934695175/index.html#suites/5008d72a1ba3c0d618a030a938fc035c/4e98b5bf171ae8fa/ (expand Tear down section, then test_output_dir, you'll see repo/flamegraph.svg)

we seem to not include etcd services logs? They are created in test_output/neon/ by default.

Thanks for pointing this out! I've added etcd logs as well


format issue in eqs

need change the codes of eqs.

the page supports the language of Ruby, which is weird in equation edits.
The dollar sign ($) is commonly used in LaTeX and some Markdown flavors to denote mathematical equations or inline math. However, in Ruby, the dollar sign is not used for this purpose.
I leave this issue open. We shall discuss this or follow an existing page to convert all the equtions.


Resolve function stopping state to load

My resolve function returns a promise. Due to this states are not loading.
Would really appreciate any help on this. It was working a day ago. Seems like an update of ui-router broke it. Reason for adding promise in resolve function was earlier when it was working, it was just loading default page without loginService returning its status back to resolve. But now resolve itself stopped working. I am doing a small demo project. If moving to an earlier version can resolve this issue please let me know what version should I use? thanks.
Here is the code.
.state('home', {
url: '/',
templateUrl: "./src/dashboard.html",
resolve: {
loggedin: isLoggedIn
}
})
function isLoggedIn($location, loginService) {
var deferred = $q.defer();
return loginService
.loggedin()
.then( function(result) {
if (!result){
$location.url('/login');
}
deferred.resolve(true);
},
function(err){
$location.url('/login');
deferred.resolve(true);
});
return deferred.promise;
};

Any help please?

No worries I found the problem. I was bitten by a very silly mistake. Order of dependencies in my loginService module and service function were not matching and hence resolve function was not working.


chore: add linter for 'import Lean'

I guess we should upstream #minimize_imports too, so people don't have to do this by hand. :-)


/home/ubuntu/miniconda3/envs/py37-cuda101/lib/python3.7/site-packages/mmcv/_ext.cpython-37m-x86_64-linux-gnu.so:undefined symbol: _ZN3c106Symbol14fromQualStringERKSs,how can I solve the problem?

The environment infomation is
Ubuntu=18.04
python=3.7
pytorch=1.4.0
cuda 10.1
mmcv=1.1.5
Every time I run the code
import mmcv
It will be shown in such errors.
So how can I slove the problem?Thank you!

You can

Refer to the trouble shooting
search some related issues like this

I believe you can find wut you want.

Ok,I have solved the problem.You should recompile the mmcv on your computer.
Thank you!


CI010.XMinecraftLauncher version 0.30.2

[ ] Have you signed the Contributor License Agreement?
[ ] Have you checked that there aren't other open pull requests for the same manifest update/change?
[ ] 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.1 schema?

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

Microsoft Reviewers: Open in CodeFlow

Close this due to wrong account


gamescope: Does not work with lutris

Describe the bug
When trying to use gamescope from inside lutris (Configure -> System options -> Enable Gamescope), the game will simply not start.
Steps To Reproduce
Lutris isn't providing any gamescope logs, so I tried to run it manually from inside the fshenv via the built-in terminal (Open Bash terminal):
gamescope -f -- \
  gamemoderun \
    ~/.local/share/lutris/runners/wine/wine-ge-8-26-x86_64/bin/wine \
    ~/Games/foo/bar.exe

And I got this error:
failed to inherit capabilities: Operation not permitted

This is my gamescope & gamemode config:
programs = {
  gamescope = {
    enable = true;
    capSysNice = true;
  };
  gamemode = {
    enable = true;
    enableRenice = true;
  };
};

Expected behavior
Games in Lutris should be able to run with gamescope.
Notify maintainers
@kira-bruneau @nrdxp @Madouura

Metadata
Please run nix-shell -p nix-info --run "nix-info -m" and paste the result.
[user@system:~]$ nix-shell -p nix-info --run "nix-info -m"
 - system: `"x86_64-linux"`
 - host os: `Linux 6.1.79, NixOS, 24.05 (Uakari), 24.05.20240226.13aff9b`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.18.1`
 - nixpkgs: `/nix/store/1gpgihsi21bni03hy6i5ccw9lfrhnbqi-source`

Add a :+1: reaction to issues you find important.

I get the same error in steam. As both are inside a fhsenv maybe it is worth investigating bwrap ? I saw that in steam there is a security wrapper for setuid bit. But that doesnt seem to be sufficient

I created an account just to share this. Extremely hacky and unsafe but this allows lutris to work with gamescope with capSysNice enabled.
myLutrisPkg = let
hackedPkgs = pkgs.extend (final: prev: {
buildFHSEnv = args:
prev.buildFHSEnv (args
// {
extraBwrapArgs =
(args.extraBwrapArgs or [])
++ [
"--cap-add ALL"
];
});
});
in
hackedPkgs.lutris;
Basically I overrode the package to add an extra bwrap argument of "--cap-add ALL" which fixes the issues with lutris not being able to get permission to set niceness in the FHS env. Add that to top of file and add myLutrisPkg instead of lutris in your systemPackages. This works with gamemode niceness enabled and gamescope capSysNice.

I haven't experienced any issues, however I did notice there was an issue with vkCreateDevice obtaining a high priority queue so not sure if the niceness actually is working, but it bypassed the error and gamescope doesn't state that it doesn't have cap_sys_nice... This could be due to my use of chaotic nyx mesa_git or my older polaris card.

I'm facing this when trying to set launch options on a game with steam for example:
gamescope -W 3840 -H 2160 -r 60 -- %command%
Results in:
failed to inherit capabilities: Operation not permittedUploaded AppInterfaceStats to Steam

I haven't experienced any issues, however I did notice there was an issue with vkCreateDevice obtaining a high priority queue so not sure if the niceness actually is working, but it bypassed the error and gamescope doesn't state that it doesn't have cap_sys_nice... This could be due to my use of chaotic nyx mesa_git or my older polaris card.

Thanks for ure workaround I am pretty confident that the vkCreateDevice is from mesa-git I got that same error also on mesa git. I am wondering whether it would be sufficient to add the renice capability instead of all, have you tried that ?

I did try just adding —cap-add sys_nice I think it was however that didn’t resolve the issue so I just added all the capabilities. It’s just an issue with using bubblewrap for lutris that you don’t have the necessary permissions in the namespace. I also initially tried overriding the bwrap executable used in the module with a wrapped one (tried setuid and just set cap) but that didn’t work.

Not sure if this would fix your issue with Lutris, but I recently had a similar issue with running gamescope from steam (e.g. gamescope -- %command% in the game's launch options). Running steam from the terminal allowed me to see what the issue is. First it was something about failed to inherit capabilities, after disabling cap_sys_nice it said something about missing libraries. Ultimately this is the config that fixed it for me:
services = {
    steam.enable = true;
    # Fixes using gamescope in steam
    steam.package = pkgs.steam.override {
      extraPkgs = pkgs:
        with pkgs; [
          xorg.libXcursor
          xorg.libXi
          xorg.libXinerama
          xorg.libXScrnSaver
          libpng
          libpulseaudio
          libvorbis
          stdenv.cc.cc.lib
          libkrb5
          keyutils
        ];
    };

    gamescope.enable = true;
    gamescope.capSysNice = false; # Breaks gamescope in steam

};

This issue has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/unable-to-activate-gamescope-capsysnice-option/37843/6


Creation of SuperAgent and calling HTTP Method Redundant

The creation of a SuperAgent object via gorequest.New() and the act of calling a HTTP method seems some what redundant. This is due to the fact that the internal state of the SuperAgent is getting reset on the verb method via ClearSuperAgent which means that any state that you put into the SuperAgent object after the object was created is pretty much wiped out.
This promotes the one liner gorequest.New().Get(...)... which then begs the question, is there any reason, if your state gets wiped on calling Get/Post/Put/..., to have the creation of the object and the HTTP verb be two different actions?
Would gorequest.<Get/Post/Put/...>() not be sufficient?

I send a pull request to allow user to prevent from clearing up the superagent object stats.
Here is the PR:
https://github.com/parnurzeal/gorequest/pull/109
Please review it.

Fix in #140


Fix missing network for uniarts

Uniarts network missed a network key in ss58-registry.json, this PR fixes that.
Fixes #7651

@joepetrowski @jacogr Could you please review it? It fixes #7651. Thanks!

@joepetrowski @jacogr Could you please review it? It fixes #7651. Thanks!


Add support for TLS

Certificate verification, validation, CA &etc can be configured via environment variables. See https://access.redhat.com/articles/2039753 for more details
THE FOLLOWING DISCLAIMER APPLIES TO ALL SOFTWARE CODE AND OTHER MATERIALS CONTRIBUTED IN CONNECTION WITH THIS SOFTWARE:
THIS SOFTWARE IS LICENSED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS “AS IS” AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE AND ANY WARRANTY OF NON-INFRINGEMENT, ARE DISCLAIMED.  THIS SOFTWARE MAY BE REDISTRIBUTED TO OTHERS ONLY BY EFFECTIVELY USING THIS OR ANOTHER EQUIVALENT DISCLAIMER IN ADDITION TO ANY OTHER REQUIRED LICENSE TERMS.
 NO OTHER SOFTWARE CODE OR MATERIALS ARE A CONTRIBUTION.

We got around this limitation by inheriting from QConnection, also allows us to pass in the ssl_context (as we're using self-signed certs):
import socket

from qpython.qconnection import QConnection

class MyQConnection(QConnection):

    def __init__(self, *args, **kwargs):
        self.ssl_context = kwargs.pop("ssl_context", None)
        super().__init__(*args, **kwargs)

    def _init_socket(self):
        '''Initialises the socket used for communicating with a q service,'''
        try:
            sock = socket.socket(socket.AF_INET, socket.SOCK_STREAM)
            if self.ssl_context is not None:
                sock = self.ssl_context.wrap_socket(sock, server_hostname=self.host)
            self._connection = sock
            self._connection.connect((self.host, self.port))
            self._connection.settimeout(self.timeout)
            self._connection_file = self._connection.makefile('b')
        except:
            self._connection = None
            self._connection_file = None
            raise


Update nuget issue53

Update all nuget packages
Resolve issue #53

With the migration to .NET 7, the packages were also updated to the latest version. See more here: #59 .


Minor changes plus test code

Dear Lia,
very interesting work. I was wondering if you also have python code for tbnew, or did you take the output from xspec?
Cheers,
Johannes

Thanks Johannes.  I merged your changes.
I do not have python code for TBnew.
The TBnew models shown in my paper were computed from XSPEC.  From the author of TBnew:

tbnew has a (not so well known) feature that a negative depletion
value for a given element is interpreted as the negative of the column
of that element. (so setting the Neon abundance to -1e19 will give you
absorption for a Ne-column of 1e19/cm^2)


HDDS-10720. Datanode volume DU reserved percent should have a non-zero default value.

What changes were proposed in this pull request?
Currently there are two ways to reserve space in datanode volumes:

hdds.datanode.dir.du.reserved.percent allows specifying a percentage of the volume's space to be unused. It applies to all volumes
hdds.datanode.dir.du.reserved allows specifying a map of volume name to bytes reserved. Since it depends on a volume path, it cannot have a default value.

By default Ozone should not allow datanode volumes to get 100% full. This can cause the drive to "lock up" because some operations like block delete that would free up space still need extra disk space before they can complete because they must append to the RocksDB WAL. Once encountered, such issues are difficult to resolve. Add a default value for hdds.datanode.dir.du.reserved.percent to prevent this from happening.
A default value of 0.0001f is currently chosen. This is 0.01% which reserves 1GB out of a 10TB volume, 1MB out of a 1TB volume, etc. Ideally we could reserve a fixed size (like 1GB) regardless of drive size, but we would need to re-work the configs before we can do that which might need more discussion. See HDDS-10721.
This PR also fixes a few other bugs that prevented tests from passing after the change:

A non-zero default value for hdds.datanode.dir.du.reserved.percent would not be used.
Canonicalization was not done on paths in hdds.datanode.dir.du.reserved. This may have passed in CI but was failing due to my local filesystem setup.
Invalid space reserved configurations would fall back to 0 (hardcoded) instead of the default value.

What is the link to the Apache JIRA
HDDS-10720
How was this patch tested?
Unit test added.

Looks like there's other tests that were depending on 0 being the default value. Let me get them fixed on my fork before running CI here.

Green CI on my fork, ready for review.

Thanks for the review @adoroszlai


Remove trailing whitespaces in macro_rules!

Closes #878.

Closing this PR since it removes trailing whitespaces from raw strings inside macro_rules! as well.


Participants can't change events that have already happened.

Describe the bug
Currently, anyone can go back and edit their participation on any number of events, either manually or via POST requests.
Once an event is finished, they shouldn't be able to.

UI part is merged, POST is TODO

Done & merged on Sun just forgot to deal with the issue


backend info messages

Backend info messages as described here: https://github.com/deeplearning4j/nd4j/issues/1573

Build triggered. sha1 is merged.

Build finished. No test results found.

Refer to this link for build results (access rights to CI server needed):
/job/nd4j_PR/152/


Minor cleanup

would be nice to add shellcheck as a test so this doesn't regress!  maybe could be added to https://github.com/micahflee/torbrowser-launcher/blob/develop/.github/workflows/python.yml ?


Feature: List active window for each monitor

Thank you for this amazing small program. It was just what I needed!
I was wondering if you could add an option like hyprland-workspaces (hyprland-workspaces _) so that each monitor prints its active window.
If you could also print this information in json, it would be possible to define a single widget in eww with a parameter. Something like the following
(deflisten windows "hyprland-activewindow _ --json")

(defwidget window [monitor]
  (box
    (label :text "${windows['${monitor}']}")
  )
)

I think this would greatly simplify the eww configuration for multi-monitor setups.

I've implemented this under the wildcard branch for testing. Let me know how it goes and I'll merge it into the main branch.
I've forgone the --json flag, as there isn't really any other usable way of outputting all monitors. It uses json automatically when using "_" mode.

I noticed that the title does not update to an empty string if I close the last window of a workspace. Is this expected behavior?
Other than that, it seems to be working just fine!

Thanks for your feedback.

I noticed that the title does not update to an empty string if I close the last window of a workspace. Is this expected behavior?

That is not expected behaviour and looks like a bug. I've included in a fix with the all monitor support (which I'll call advanced mode).
I'll merge and push out a new release shortly.

Hey, sorry to reopen this issue, but I think there is some problem with the proc-macro2 package. I don't really know rust, but I could only compile the code using version 1.0.60 in the Cargo.lock file.
Other than that, it seems that the nightly rust release is required as well. Could you update the PKGBUILD in the AUR to address this?

The Cargo.lock file is auto generated by cargo. It shouldn't be edited.
If you're having issues compiling, I would suggest blowing away your local copy and cloning the repo down again. You could also try a cargo update if you're still having issues.


Restrict Npgsql version >=3.2.5 and <4.0

This would allow nuget package that is published to limit the version of npgsql, this way we can enforce the version during package installation of Marten without waiting for runtime errors to occur
Related to #1081

Looks good to me. @jeremydmiller I think that merging this change would solve common issue that is visible on the gitter and lot of confusion. Especially after we finish with the final version 3.0.


Audio doesn't play in iOS Simulator

Describe the Bug
Although audio plays in the android simulator for an app built using the same code, audio doesn't play for the same app in the iOS simulator.
Using console logs to debug, it appears that await TrackPlayer.add(tracks)'s promise doesn't resolve, so the audio never gets to play.
Steps To Reproduce
Code To Reproduce
import React, { useEffect, useRef } from 'react';
import LottieView from 'lottie-react-native';

import TrackPlayer, {
  useTrackPlayerEvents, Event, Capability, RepeatMode,
} from 'react-native-track-player';

const helixSong = {
  id: 4,
  url: 'https://www.soundhelix.com/examples/mp3/SoundHelix-Song-1.mp3',
  title: 'helix song',
};

const tracks = [
  helixSong
];

const setupIfNecessary = async () => {
  console.log('setupIfNecessary');
  // if app was relaunched and music was already playing, we don't setup again.
  const currentTrack = await TrackPlayer.getCurrentTrack();
  if (currentTrack !== null) {
    console.log('current track is not null', currentTrack);
    return;
  }
  console.log('setting up player', currentTrack);
  await TrackPlayer.setupPlayer({});
  console.log('updating options for player');
  await TrackPlayer.updateOptions({
    stopWithApp: true,
    capabilities: [
      Capability.Play,
      Capability.Pause,
      Capability.Stop,
    ],
    compactCapabilities: [Capability.Play, Capability.Pause],
  });

  console.log('adding tracks in player set up');
  await TrackPlayer.add(tracks);
  console.log('added. queue in setup', await TrackPlayer.getQueue());
  TrackPlayer.setRepeatMode(RepeatMode.Queue);
  console.log('set repeat mode');
};

export default (props: NavigationScreenProps<'MindfulBreathingExerciseScreen'>) => {
  const lottieView = useRef<LottieView>(null);
  useTrackPlayerEvents([
    Event.PlaybackState,
    Event.PlaybackError,
    Event.PlaybackQueueEnded,
    Event.PlaybackTrackChanged,
    Event.PlaybackMetadataReceived,
  ], async (event) => {
    console.log('EVENT:', event);
  });
  useEffect(() => {
    setupIfNecessary();

    return () => {
      TrackPlayer.stop();
      TrackPlayer.reset();
    };
  }, []);

  const handleStart = async () => {
    lottieView.current?.play(); // play animation
    await TrackPlayer.setVolume(1);
    console.log('set volume');
    await TrackPlayer.add(tracks);
    console.log('added tracks on start');
    console.log('resulting queue', await TrackPlayer.getQueue());
    await TrackPlayer.play();
    console.log('played track');
  };

  const handleFinish = async () => {
    console.log('handle finish');
    lottieView.current?.pause(); // pause animation
    console.log('paused animation');
    TrackPlayer.stop();
    console.log('stopped music');
  };
  return (
    <CircleTimerScreen
      onStart={handleStart}
      onFinish={handleFinish}
      onUnfocus={() => {
        lottieView.current?.reset();
        lottieView.current?.pause();
        TrackPlayer.pause();
      }}
      buttonText="Finish"
      animated
      autoStart
      duration={60}
    >
  );
};

Environment Info:
Paste the results of npx react-native info
System:
    OS: macOS 11.5.2
    CPU: (16) x64 Intel(R) Core(TM) i9-9880H CPU @ 2.30GHz
    Memory: 189.16 MB / 16.00 GB
    Shell: 5.8 - /bin/zsh
  Binaries:
    Node: 16.9.1 - ~/.nvm/versions/node/v16.9.1/bin/node
    Yarn: 1.22.17 - /usr/local/bin/yarn
    npm: 7.21.1 - ~/.nvm/versions/node/v16.9.1/bin/npm
    Watchman: 2<IP_ADDRESS> - /usr/local/bin/watchman
  Managers:
    CocoaPods: 1.11.3 - /Users/tinaquach/.rvm/rubies/ruby-3.0.0/bin/pod
  SDKs:
    iOS SDK:
      Platforms: DriverKit 21.0.1, iOS 15.0, macOS 12.0, tvOS 15.0, watchOS 8.0
    Android SDK:
      API Levels: 29, 30, 31
      Build Tools: 28.0.3, 29.0.2, 31.0.0
      System Images: android-29 | Intel x86 Atom_64, android-30 | Google Play Intel x86 Atom
      Android NDK: Not Found
  IDEs:
    Android Studio: 2020.3 AI-203.7717.56.2031.7784292
    Xcode: 13.1/13A1030d - /usr/bin/xcodebuild
  Languages:
    Java: 1.8.0_232b09 - /Users/tinaquach/.sdkman/candidates/java/current/bin/javac
  npmPackages:
    @react-native-community/cli: Not Found
    react: 17.0.2 => 17.0.2
    react-native: 0.65.1 => 0.65.1
    react-native-macos: Not Found
  npmGlobalPackages:
    *react-native*: Not Found

Paste the exact react-native-track-player version you are using
2.1.3
Real device? Or simulator?
iPhone 12, iOS 15 simulator running on
What OS are you running?
macOS Big Sur 11.5.2
How I can Help
What can you do to help resolve this?
(i'm stuck)
Have you investigated the underlying JS or Swift/Android code causing this bug?
(i need help with this)
Can you create a Pull Request with a fix?

Does adding artist and artwork to your track object fix the issue?. I recall having a similar issue and ended up adding those for some reason but it might have been to get rid of a swift warning.

Hi @tina-at-limbix this seems more like a question for the Discord group.
Does the example app also not play for you in the simulator?

adding the 'artist' property to the tracks fixed the issue.

I have opened a new issue for this as I believe it is an underlying bug which should be fixed.

For me it was working with local file path like require(my_file_path). But it was not with remote URL and what I found is url needs to be prefixed with https not http.
await TrackPlayer.add([
    {
      url: 'https://your_file.mp3',
    },
  ]);


[HUDI-4071] Remove default value for mandatory record key field

Change Logs
Record key field is mandatory, so this PR removed the default value for that field. This is not backwards compatible. Most users set the record key, but if some user relied on uuid (current default value) as record key, then they need to set it explicitly using hoodie.datasource.write.recordkey.field.
Impact
No public API change or performance impact. But, it needs to be called out in the release notes. Created HUDI-4849 to track doc changes.
Risk level: none | low | medium | high
High.
Contributor's checklist

[ ] Read through contributor's guide
[ ] Change Logs and Impact were stated clearly
[ ] Adequate tests were added if applicable
[ ] CI passed

@codope : once the patch is ready to be reviewed again, remove WIP label.


Request for Update to SSIS 2019

Dear fan130,
I kindly ask whether you might help me out and provide support for SSIS 2019 for the Sharepoint List Adapters. Appreciate your effort! Thanks!
Best regards,
Andreas

Hello @fan130,  @InspektorDerrick ,
Me too I need a solution to upgrade SSIS packages with Sharepoint List Adapters to SSIS 2019.
@InspektorDerrick, I think this thread can help you to find a short term solution : https://stackoverflow.com/questions/63042097/how-to-install-codeplex-2017-sharepoint-list-adapter-onto-ssis-sql-server-2019/63042098#63042098.
Best regards,
Mathieu

Thank you very much, I will give it a try!

I repost the answer in this thread, I didn't write it, just repeating from:
https://stackoverflow.com/questions/63042097/how-to-install-codeplex-2017-sharepoint-list-adapter-onto-ssis-sql-server-2019/63042098#63042098

If you upgraded your SSIS SQL Server dev/prod environments to 2019 & have packages from 2012/2014/2016 that perform SharePoint List Record downloads/inserts/updates; you will soon notice the 2017 SharePoint List Adapter installation does not target SQL Server 2019. You may use OData Source to download list records, but sometimes your business needs require more than that.
To overcome this, try the following steps. This worked well for our needs and are now running packages that use Codeplex 2017 SharePoint List Adapter from SQL Server 2019, Jobs.
Step 1: If you don't have it already, get the 2017 SharePoint List Adapter here
Install adapter. If it gives error, most likely need to install .NET Framework 3.5, retry installer.
Step 2: Locate path >>> in dev/prod: C:\Program Files (x86)\Microsoft SQL Server\150\DTS
The following folders must be available or created: Connections, PipelineComponents, UpgradeMappings
Add the following files into each folder below:
The following files can be found in previous installation folders within C:\Program Files (x86)\Microsoft SQL Server such as \140\DTS. That's where I pulled them from. But in the steps below, we need to add them onto the \150\DTS locations for SQL Server 2019.
C:\Program Files (x86)\Microsoft SQL Server\150\DTS\Connections

SharePointListConnectionManager.dll

C:\Program Files (x86)\Microsoft SQL Server\150\DTS\PipelineComponents

SharePointListAdapters.dll

C:\Program Files (x86)\Microsoft SQL Server\150\DTS\UpgradeMappings

MicrosoftSamples.SharepointListAdapters.UpgradeMappings.xml
MicrosoftSamples.SharepointListAdapters.xml

Step 3: Register the adapter using the script below with Powershell Admin mode
Set-location "C:\Program Files (x86)\Microsoft SQL Server\150\DTS\PipelineComponents"
[System.Reflection.Assembly]::Load("System.EnterpriseServices, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a")
$publish = New-Object System.EnterpriseServices.Internal.Publish
$publish.GacInstall("C:\Program Files (x86)\Microsoft SQL Server\150\DTS\PipelineComponents\SharePointListAdapters.dll")
$publish.GacInstall("C:\Program Files (x86)\Microsoft SQL Server\150\DTS\Connections\SharePointListConnectionManager.dll")
When adapter registers successfully, run your SSIS Package from SQL Server Agent, Jobs. Remember to run in 32-bit mode
You should able to now perform the following actions in a SharePoint List from your 2019 Server:

Download rows to SQL Table
Insert rows to SharePoint List
Modify/Update SharePoint List rows
Deleting SharePoint List rows from Server Job didn't work for me, but I'll update this post in case I figure out why.

All of the above can also work from your client side computer. You should be able to use steps 1 through 2 to make the adapter work when you build packages on your computer targeting 2017/2019 SQL Server.

Added a pull request for this, but if someone is looking for 2019 support in the meantime I've created a release over in my own fork. https://github.com/czielin/mssql-ssis-community-samples/releases/tag/SqlServer2019


System is not defined error

Hi
This app works fine using npm start, however whenever I try to call it through localhost or file:// I get a System is not defined error, and all resources are not loaded.
I have also used the quickstart clone here https://github.com/angular/quickstart
I have completed the tutorial on the official angular 2 website using above as a template, in all cases I get the same error outside of npm start. Not a single version will run.
Strangely, I did the 5 Min Quickstart tutorial from the angular 2 website and this is OK in and outside of npm start, I can run the 5 Min index.html inside a browser from a file:// or localhost reference.
Any help would be appreciated, I really want to get to grips with ng2.
Further investigation shows no resources are being loaded:

Best Regards
Steve

closing since this was rewritten with the CLI


Use github actions & codecov

This PR removes travis and tox and uses github actions with codecov
If you want to use the automated pypi-package publish script (triggered if you release a new tag-version in https://github.com/moccu/pytest-isort/releases/new/ ), you have to add 2 environment variables in your github repo settings - called ´secrets´ (https://github.com/moccu/pytest-isort/settings/secrets):
Add your pypi credentials to the ´secrets´:
One is called ´PYPI_USERNAME´ and the other one is called ´PYPI_PASSWORD´
There is a helper command to easily tag the code for the pypi-package publish script:
$ make release-tag

Why did you delete tox.ini? We need that to run the tests locally in different environments, don't we?

Hmm good point. I thought just github CI is ok. I´ll revert it!


Manual instructions not working

Hi there,
I tried to follow the manual steps, but I get the following:
The system cannot restart because the configuration is not valid: Integration error: powercalc - Integration 'powercalc' not found.

I did copy the powercalc folder into the config folder as instructed.
Can anyone advise?
Thank you !

Nevermind, I got it, I needed to create the custom_components folder too.


Update index.md

@BiscuiTech : Thanks for your contribution! The author, @KathrynEE, has been notified to review your proposed change.

@BiscuiTech Thank you for fixing that.


Support for fp16 in SpM x DnsM on GPU

Description
enables fp16 DType suport in following case
dot(csr, dense1) = dense2 and dot(csr.T, dense1) = dense2

Will add test case shortly
Checklist
Essentials
Please feel free to remove inapplicable items for your PR.

[x] Changes are complete (i.e. I finished coding on this PR)
[ ] All changes have test coverage:
Unit tests are added for small changes to verify correctness (e.g. adding a new operator)
Nightly tests are added for complicated/long-running ones (e.g. changing distributed kvstore)
Build tests will be added for build configuration changes (e.g. adding a new build option with NCCL)
[x] To the best of my knowledge, examples are either not affected by this change, or have been fixed to be compatible with this change

Changes

[ ] Feature1, tests, (and when applicable, API doc)
[ ] Feature2, tests, (and when applicable, API doc)

Comments

If this change is a backward incompatible change, why must this change be made.
Interesting edge cases to note here

@mxnet-label-bot add [pr-work-in-progress]

@ptrendx Can you take an initial look ? I am yet to add test case though

Looks good :-)

@mxnet-label-bot update [pr-ready-to-review]

@ptrendx I have added test case. Can you help with review and merge

Merging per previous review by @ptrendx


Speed up LexiconNER

This PR is meant to provoke Travis into running unit tests.  Please do not merge yet.  It will be tested with reach next.

Do unit tests in Reach pass with this change?
Also, would it be possible to get times for "sbt main/test" in Reach before/after this change

It doesn't work with reach yet.  In one case reach skips the LexiconNER and goes directly for a HashTrie which I had eliminated.  I'm starting to put that back in so that reach builds without change.
FWIW there seems to be an existing compilation problem in HomeController that neither the build nor tests catch.

main/test running on processors 7.4.4 ran in 5:04 minutes just now with the original code, and 7.4.5-SNAPSHOT ran in 3:27 minutes with the new code.  I wasn't expecting that much of a difference.  Some more numbers will appear at #302.

Nice!
I wonder what these numbers would look in Reach, assuming the same data structures are used?

On Feb 26, 2019, at 4:31 PM, Keith Alcock<EMAIL_ADDRESS>wrote:
main/test running on processors 7.4.4 ran in 5:04 minutes just now with the original code, and 7.4.5-SNAPSHOT ran in 3:27 minutes with the new code. I wasn't expecting that much of a difference. Some more numbers will appear at #302.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.

I wasn't clear above.  The times are from reach's main/test when build.sbt is configured to use the old and new version of processors.  reach seems to use the BioCluProcessor which in turn uses the LexiconNER which has been rewritten.  The BioCluProcessor is what I have been timing in processors as well via a new test case.  The intention is that it is ready to go and reach will be faster after the merge and republishing of processors and then an update to the dependency in reach.  There are a couple of other PRs ready for processors that should also go in.

If someone needs/wants to test how this might affect some application of reach on some corpus, then doing a publishLocal on this branch (kwalcock-DuoHashTrie) and then changing reach's main/build.sbt procVer to 7.4.5-SNAPSHOT should do the trick.

Thanks!

Yes, they do.

Cool. Then merge?

On Feb 27, 2019, at 9:44 AM, Keith Alcock<EMAIL_ADDRESS>wrote:
Yes, they do.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.

If you please.  #295 and #305 should also be merged before the next release.  I'm not sure about the others.

Done. Can you please update the CHANGES file (let’s use as next version 7.5.0), and release?

On Feb 27, 2019, at 10:17 AM, Keith Alcock<EMAIL_ADDRESS>wrote:
If you please. #295 and #305 should also be merged before the next release. I'm not sure about the others.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.


github-actions: Add bionic-frontend-backend job.

Testing Plan: GitHub Actions CI passes successfully.

While we’re adding variables to the Dockerfile, we could also replace the silly generate-dockerfiles template mechanism with variables too, if you want.

@andersk to be clear, you mean use ARG for base_image and extra_packages so we can do sudo docker build <path> --build-arg base_image=...

I am trying to figure out why using cache from bionic causes error in focal like we do in circleci. So we should hold off on merging last two commits. I'd like to know if the approach in provision: Do service <service-name> start instead of restart. is plausible to avoid flakes in Focal.
This is the relevant step that causes error:
        # TODO: Doing this on Focal causes errors later in provision
        # possibly because we are reusing cache:
        #   Could not find platform independent libraries <prefix>
        #   Could not find platform dependent libraries <exec_prefix>
        #   Consider setting $PYTHONHOME to <prefix>[:<exec_prefix>]
        #   Fatal Python error: Py_Initialize: Unable to get the locale encoding
        #   ModuleNotFoundError: No module named 'encodings'
        #   Current thread 0x00007fb7efa04740 (most recent call first):
        #   Provisioning failed (exit code 134)!
        # sudo chmod -R 0777 /__w/_temp/

And, CircleCI Builds: https://circleci.com/gh/priyank-p/zulip/tree/github-actions

The issue was focal build was that we were using cache from bionic build. I missed the part that adds the job name as a cache restore key when migrating this from CircleCI config. Both bionic and focal jobs run successfully now.

I merged the first 3 commits.  @arpit551 @amanagr can you help review the new GitHub Actions configuration?  I feel like someone should at least carefully compare it with the old CircleCI logic and make sure we have comments around any changes.
I'd also be on board with making .template.yml using YAML anchors and having a tool that reads it in and writes the result back out for GitHub's use to let us reuse code more effectively.

This looks good regarding the code reusability thing I am not sure it will be straight forward. There are some issues regarding it https://github.community/t/support-for-yaml-anchors/16128/33,
https://github.community/t/reusing-sharing-inheriting-steps-between-jobs-declarations/16851/3.

Can we not use strategy to run the same steps on multiple platforms, along with variables and if conditionals to handle differences between platforms?

I added two more commits for minor cleanups. For the strategy commit I used this script to verify all the steps are correctly migrated.

Script
"""
This script prints out the ignore steps first. Then
prints out each step of both circle and actions side-by-side.
One step is out of order for bionic but verfying correction is
still easier. Format:
Actions: Install dependencies
Circle CI: install dependencies
...
"""
import yaml

with open('.circleci/config.yml') as f:
    circleci_config = yaml.safe_load(f)

with open('.github/workflows/zulip-ci.yml') as f:
    actions_config = yaml.safe_load(f)

circle_bionic_steps = []
circle_focal_steps = []
actions_bionic_steps = []
actions_focal_steps = []

# We ignore casper artifact upload, save_cache, and
# store_tests_reports steps.
def get_circleci_steps(job, arr):
    for step in circleci_config['jobs'][job]['steps']:
        if isinstance(step, str):
            arr.append(step)
            continue

        step_name = step.get('run', {}).get('name', False)
        if not step_name:
            if step.get('restore_cache'):
                key = step['restore_cache']['keys'][0].split('.')[0]
                step_name = f'<restore-cache> {key}'
            elif step.get('store_artifacts', False):
                destination = step['store_artifacts']['destination']
                step_name = f'<store-artificats> {destination}'

                if destination == 'casper':
                    # This is no longer needed
                    print('Ignoring step:')
                    print(step)
                    print()
                    continue
            else:
                # We don't care about save_cache; github-actions
                # does this automatically, and store_tests_reports
                # is circelci timing specific.
		print('Ignoring step:')
                print(step)
                print()
                continue

        if step_name != 'On fail':
            arr.append(step_name)

get_circleci_steps('bionic-backend-frontend', circle_bionic_steps)
get_circleci_steps('focal-backend', circle_focal_steps)

# We ignore there steps specific to github-actions
for step in actions_config['jobs']['focal_bionic']['steps']:
    BOTH_OS = 'BOTH_OS'
    if_check = step.get('if', BOTH_OS)
    step_name = step.get('name')

    if step_name is None:
        step_name = step['uses']

    if (
        step_name == 'Upgrade git for bionic' or
        step_name == 'Add required permissions' or
        step_name == 'Move test reports to var'
    ):
        print('Ignoring step:')
        print(step)
        print()
        # These are github-actions specific; see comments in config
        continue

    if if_check == BOTH_OS:
        actions_bionic_steps.append(step_name)
        actions_focal_steps.append(step_name)
    elif 'is_bionic' in if_check:
        actions_bionic_steps.append(step_name)
    else:
        actions_focal_steps.append(step_name)

bionic = zip(circle_bionic_steps, actions_bionic_steps)
focal = zip(circle_focal_steps, actions_focal_steps)

print('Bionic steps:')
for (circle_step, actions_step) in bionic:
    print(f'CircleCI: {circle_step}')
    print(f'Actions: {actions_step}')
    print()

print('Focal steps:')
for (circle_step, actions_step) in focal:
    print(f'CircleCI: {circle_step}')
    print(f'Actions: {actions_step}')
    print()

This seems good enough that it's worth merging and we can iterate from here.  Huge thanks for prototyping this @priyank-p!
I think we might want to expand the flags we set on matrix to be more semantic (E.g. "include_frontend_tests" for the conditional for things that are about that, not about the OS version).
Please post in #backend with updates on this, and we should start working on moving the production suites.


Support symbol renaming

Currently go-rename exists (MELPA), but is excruciatingly slow on even small code-bases. It would be really nice to have rename-support via go-langserver.

This has been debated a few times in go tools issues. The problem is go guru/rename/mvpkg/etc have a concept of scope which very often defaults to your whole GOPATH.
However, earlier this year there was mention of the go team improving this https://github.com/golang/go/issues/10917#issuecomment-284481820
But I think it is worth implementing this ourselves in go-langserver since we have the additional concept of a workspace so we can limit the rename work to just the current workspace. We do the same for find references, which is why find references is likely faster in go-langserver than the usual vscode-go shelling out to guru.
I'll happily accept patches around this since I won't have time to work on this soon.

At least in my environment, all application git-repos are GOPATH roots, so I clone example project foo.git to directory foo, and will then have foo/.git, foo/src/foo/main.go, foo/src/vendor/bar etc. go-projectile detects this and configures GOPATH accordingly and lets guru and all other tools play nice in emacs. I haven't used go-langserver yet, found it just an hour ago and I'm excited to try it out. How does it deal with GOPATH, from what I can tell, emacs doesn't send GOPATH to it at least. Should probably just play around with it instead of asking silly questions here :)

aah, and its still slow? Then I'm not sure if we could make it faster. Although in theory it should be as fast as find references which we have made faster than go guru.

I am just commenting to say I would also love to have go-langserver support symbol renaming 👍 !

Can this issue be marked as closed as of #337 ?


New Pattern: aws-kinesisstreams-gluejob

Issue #: https://github.com/awslabs/aws-solutions-constructs/issues/40
Description of changes: Added a new construct to create a streaming glue etl job, that sources data from Amazon Kinesis Data Stream and writes to an S3 bucket. With the default set of parameters, the construct creates an Amazon Kinesis Data Stream, AWS Glue Job, AWS Glue Database, AWS Glue Table, IAM Role with policies required for the job, an output S3 bucket as well an asset based S3 bucket for the ETL script.
The pull request also has a working example under use cases folder on using this construct.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

AWS CodeBuild CI Report

CodeBuild project: codebuildgithubautobuildPro-QfXHf1ULVFb1
Commit ID: dc83095a32295007bade9798dbe887ea503578b8
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: codebuildgithubautobuildPro-QfXHf1ULVFb1
Commit ID: dc83095a32295007bade9798dbe887ea503578b8
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: codebuildgithubautobuildPro-QfXHf1ULVFb1
Commit ID: 6b0ef07acc33da7183f6e29a9bfb8ac125d481a6
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: codebuildgithubautobuildPro-QfXHf1ULVFb1
Commit ID: 6b0ef07acc33da7183f6e29a9bfb8ac125d481a6
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: codebuildgithubautobuildPro-QfXHf1ULVFb1
Commit ID: 7ad1ca696705315eff80acda215c8f53eef6649d
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: codebuildgithubautobuildPro-QfXHf1ULVFb1
Commit ID: 7ad1ca696705315eff80acda215c8f53eef6649d
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: codebuildgithubautobuildPro-QfXHf1ULVFb1
Commit ID: 14ffdb0cdadf34df5dc393bef516ae77ed8b6977
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: codebuildgithubautobuildPro-QfXHf1ULVFb1
Commit ID: 14ffdb0cdadf34df5dc393bef516ae77ed8b6977
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: codebuildgithubautobuildPro-QfXHf1ULVFb1
Commit ID: 1d84029e8e5912ccb8c7df8dd9701cac42e2edaa
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: codebuildgithubautobuildPro-QfXHf1ULVFb1
Commit ID: 1d84029e8e5912ccb8c7df8dd9701cac42e2edaa
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: codebuildgithubautobuildPro-QfXHf1ULVFb1
Commit ID: 5783f5eaa410f7365dd3b85f9ee1870128dd5ec8
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: codebuildgithubautobuildPro-QfXHf1ULVFb1
Commit ID: 5783f5eaa410f7365dd3b85f9ee1870128dd5ec8
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: codebuildgithubautobuildPro-QfXHf1ULVFb1
Commit ID: f40ef7635982681e21ecd7fbe6a5aae4952ca9d0
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: codebuildgithubautobuildPro-QfXHf1ULVFb1
Commit ID: f40ef7635982681e21ecd7fbe6a5aae4952ca9d0
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: codebuildgithubautobuildPro-QfXHf1ULVFb1
Commit ID: e64e742dac79903bed66aa005bbc5c39c13e8b44
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: codebuildgithubautobuildPro-QfXHf1ULVFb1
Commit ID: e64e742dac79903bed66aa005bbc5c39c13e8b44
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: codebuildgithubautobuildPro-QfXHf1ULVFb1
Commit ID: 8100d192b79387105153cd3da3f9b7e57cff3b79
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: codebuildgithubautobuildPro-QfXHf1ULVFb1
Commit ID: 8100d192b79387105153cd3da3f9b7e57cff3b79
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: codebuildgithubautobuildPro-QfXHf1ULVFb1
Commit ID: 0fc781ff70826f107ba7ff36daa64367b8b8c834
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: codebuildgithubautobuildPro-QfXHf1ULVFb1
Commit ID: 0fc781ff70826f107ba7ff36daa64367b8b8c834
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: codebuildgithubautobuildPro-QfXHf1ULVFb1
Commit ID: c3ab317e3b9f7f634f883486976a2b96a020a1bc
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: codebuildgithubautobuildPro-QfXHf1ULVFb1
Commit ID: c3ab317e3b9f7f634f883486976a2b96a020a1bc
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: codebuildgithubautobuildPro-QfXHf1ULVFb1
Commit ID: afb173f55e826a33957a626930fba393e8e795d7
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: codebuildgithubautobuildPro-QfXHf1ULVFb1
Commit ID: afb173f55e826a33957a626930fba393e8e795d7
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: codebuildgithubautobuildPro-QfXHf1ULVFb1
Commit ID: 8ff7c8c5c37078c8bc20560b47b122dc5f4890b1
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: codebuildgithubautobuildPro-QfXHf1ULVFb1
Commit ID: 8ff7c8c5c37078c8bc20560b47b122dc5f4890b1
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: codebuildgithubautobuildPro-QfXHf1ULVFb1
Commit ID: 342f3de64e053a07314ab1681b84c807b503a012
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: codebuildgithubautobuildPro-QfXHf1ULVFb1
Commit ID: 342f3de64e053a07314ab1681b84c807b503a012
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: codebuildgithubautobuildPro-QfXHf1ULVFb1
Commit ID: 7b2264ba03519329ae41eda985e4d4c4777c4ac4
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: codebuildgithubautobuildPro-QfXHf1ULVFb1
Commit ID: 18307843b51d8d77676cd5268d225ff3c641e80f
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: codebuildgithubautobuildPro-QfXHf1ULVFb1
Commit ID: 5a82e154cb87d63549a13e7ae73545901731eefa
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: codebuildgithubautobuildPro-QfXHf1ULVFb1
Commit ID: 844620bfe5aafbc4cbef5ee02c012823325bbf34
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: codebuildgithubautobuildPro-QfXHf1ULVFb1
Commit ID: 0e2c9c3213db52696ef52f21cefa7f973c0a0214
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: codebuildgithubautobuildPro-QfXHf1ULVFb1
Commit ID: 7211d7d9002baf71640a448bd0502e470b973dda
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: codebuildgithubautobuildPro-QfXHf1ULVFb1
Commit ID: 24779df4998a11654f5fd195a9d1c8df25e8f6a3
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: codebuildgithubautobuildPro-QfXHf1ULVFb1
Commit ID: 3291b5ed314c683732b7d470df9c3cc7bf79ab3f
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: codebuildgithubautobuildPro-QfXHf1ULVFb1
Commit ID: 6928f6f9f954b07c5072811ff60085a1a65b43b9
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: codebuildgithubautobuildPro-QfXHf1ULVFb1
Commit ID: 75a869f5457101c60bf8367508d452331158d3c9
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: codebuildgithubautobuildPro-QfXHf1ULVFb1
Commit ID: cfd9836fb6c9050da8507999d78f0c23cea8089c
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: codebuildgithubautobuildPro-QfXHf1ULVFb1
Commit ID: 8c12c6cb81372b3de6de99d1dce6687871e63e30
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: codebuildgithubautobuildPro-QfXHf1ULVFb1
Commit ID: 285dbfa9bb86339de7def3c0a0368fec6442bfaf
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: codebuildgithubautobuildPro-QfXHf1ULVFb1
Commit ID: 7a8a8d1ee0accce86461a3f98d70b4fde51966c6
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: codebuildgithubautobuildPro-QfXHf1ULVFb1
Commit ID: a489345c35a6d48560634fb3ba42b9b521512849
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: codebuildgithubautobuildPro-QfXHf1ULVFb1
Commit ID: fd6c92d5650556f1da74cb89793ba044a3efed68
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository


GraphQL implementation for the HL7 FHIR specification based on the current implementation guide for GraphQL with FHIR

@boumaza429 we definitely see the value in this feature but don't have an ETA on when it would be prioritized for our roadmap. For now I'm going to flag as up for grabs incase someone wants to start looking at the development.


More than 1000 request in network console while using DevExtremeModule module.

devextreme-angular package version .
"devextreme": "^16.2.3",
"devextreme-angular": "^16.2.3-rc.3",
"devextreme-angular2": "^16.1.7",

I've grid with group by and column filter search implemented. For the same I'm using DxDataGridComponent from DevExtremeModule. But As soon as use grid on the page, I can see more than 1k request in network bar. I checked all of the files almost 95% files seems to belongs to devexpress. Check below screen shot

Even you can take look at this sample plunkr by opening Network Tab. There are 2389 request for simple DxButton.
May I know, is there any way to minimize this number of roundtrip to server? I mean minimize number of request to server.

Side Note: I guess because so many request at one go, the page will get stucked in IE10.

Hi,

Loading such a number of modules is not recommended. We assume that a production build should be bundled by a webpack or another module bundler. Such a build will eliminate this problem.

Loading modules by SystemJS is OK for demo purposes. But, we advise against using it for production. If the use of SystemJS is required, we can advise using SystemJS Build Tool to reduce the count of network requests. We are using it in our demos.

@kvet Thanks for your response.
I end up creating a bundle for my all packages using browserify & uglifyjs.


Browse Users

Describe the bug
Doesn't show all of the users  when you browse uses in the admin panel
Attached is the screenshot of it

@pH-7 I found out that its not showing the nav bar or the footer for this.   I know you are busy.   Hit me up when you have a chance so we can fix this..   I have been looking over the code for this but couldn't find that...    I know when i do page view source it wont show all of the code it stops at login   and wont show the nav part or the footer..
Looking forward to hear back from you on this..

+1 same issue here after clean version install. v17.9.1 stable download.

Refreshing page shows a different user each time - but only one user at a time.

Enabling developer mode outputs the following errors

Fatal error: Uncaught TypeError: PH7\Framework\Url\Url::encode(): Argument #1 ($sUrl) must be of type string, int given, called in /var/www/clients/client1/web7/web/_protectedsecure/framework/Layout/Html/Design.class.php on line 326 and defined in /var/www/clients/client1/web7/web/_protectedsecure/framework/Url/Url.class.php:29 Stack trace: #0 /var/www/clients/client1/web7/web/_protectedsecure/framework/Layout/Html/Design.class.php(326): PH7\Framework\Url\Url::encode() #1 /var/www/clients/client1/web7/web/_protectedsecure/data/cache/pH7tpl_compile/admin123_da8e79671268676c5445b24dee646dc0/base/user/browse.cpl.php(15): PH7\Framework\Layout\Html\Design->popupLinkConfirm() #2 /var/www/clients/client1/web7/web/_protectedsecure/framework/Layout/Tpl/Engine/PH7Tpl/PH7Tpl.class.php(353): require('...') #3 /var/www/clients/client1/web7/web/_protectedsecure/data/cache/pH7tpl_compile/public_main/base/layout.cpl.phplayout.cpl.php(15): PH7\Framework\Layout\Tpl\Engine\PH7Tpl\PH7Tpl->display() #4 /var/www/clients/client1/web7/web/_protectedsecure/framework/Layout/Tpl/Engine/PH7Tpl/PH7Tpl.class.php(353): require('...') #5 /var/www/clients/client1/web7/web/_protectedsecure/framework/Mvc/Controller/Controller.class.php(85): PH7\Framework\Layout\Tpl\Engine\PH7Tpl\PH7Tpl->display() #6 /var/www/clients/client1/web7/web/_protectedsecure/app/system/modules/admin123/controllers/UserController.php(92): PH7\Framework\Mvc\Controller\Controller->output() #7 [internal function]: PH7\UserController->browse() #8 /var/www/clients/client1/web7/web/_protectedsecure/framework/Mvc/Router/FrontController.class.php(656): ReflectionMethod->invokeArgs() #9 /var/www/clients/client1/web7/web/_protectedsecure/framework/Mvc/Router/FrontController.class.php(615): PH7\Framework\Mvc\Router\FrontController->runController() #10 /var/www/clients/client1/web7/web/_protectedsecure/app/Bootstrap.php(92): PH7\Framework\Mvc\Router\FrontController->runRouter() #11 /var/www/clients/client1/web7/web/index.php(45): PH7\Bootstrap->run() #12 {main} thrown in /var/www/clients/client1/web7/web/_protectedsecure/framework/Url/Url.class.php on line 29

@Mateable-com I found changing PHP from V8.1 down to V8.0 fixes the issue

Its crazy it works on 8.0 but not on 8.2   but the admin browse works just fine.   there has to be away to take the admin one and make it work with the user one and modify it..  I am still trying to learn where all the files are at cause there are soooo many files.

Thanks very much for reporting this @Mateable-com! I really appreciate it. I gave a fix (available here https://github.com/pH7Software/pH7-Social-Dating-CMS/commit/005fe0633506e0f44d0c62e1f92278a6ec4a3dfd).
It will also be release in the next version of pH7Builder 😊

Its crazy it works on 8.0 but not on 8.2 but the admin browse works just fine. there has to be away to take the admin one and make it work with the user one and modify it.. I am still trying to learn where all the files are at cause there are soooo many files.

Keep PHP 8.0 for now. That's absolutely fine too! 🙂


Create left_rotation_array.py

Please read the CONTRIBUTING.md file and follow instructions there.
https://github.com/aniketsharma00411/algorithmsUse/blob/master/CONTRIBUTING.md

@aniketsharma00411  is this repo still active? so that i can raise PR


Solcast integration question / suggestion

Describe the bug
It's not super clear from the documentation that Solcast forecast retrieval is supported by EMHASS.
I'm happy to update the documentation, but I'm not sure how often EMHASS calls Solcast to retrieve forecasts.  A comment on this issue clarifying that will be enough for me to fork the repo to clarify the documentation.
Additional context
Hi, I'm somewhat reluctantly opening an issue (as there's no discussion option on this repo) regarding Solcast forecasts.
I'm guessing based on what I saw in https://github.com/davidusb-geek/emhass-add-on/pull/69 that if you add
   solcast_api_key:
   solcast_rooftop_id:

to secrets_emhass.yaml and specify weather_forecast_method: solcast in config_emhass.yaml and the changelog, and given the code at https://github.com/davidusb-geek/emhass/blob/c9686cd657844cf193b1101c45f0fc7496af0221/src/emhass/forecast.py#L235, that there's support for EMHASS directly calling Solcast for insolation forecasts.
But there really isn't any documentation other than the example of setting up your own Solcast sensor (https://emhass.readthedocs.io/en/latest/forecasts.html#example-using-solcast-forecast-amber-prices).
As an aside, given that there is a HACS add in Solcast Integration (that integrates nicely with HA and the energy dashboard) - https://github.com/oziee/ha-solcast-solar - what would be ideal would be an option to use this just like var_PV and var_load (so that you don't use limited API calls) - so add in var_ForecastSolcast.

Hi the Solcast method is well documented in the second paragraph here: https://emhass.readthedocs.io/en/latest/forecasts.html#pv-power-production-forecast
You probably oversaw that. But yes any improvement to this documentation is welcomed.
This method is directly called in the code, on the line that you showed. And as with the other endpoints of the EMHASS API it is you that control the number of calls to the Solcast API from your automation on the HomeAssistant side. If you setup this method then the Solcast API is called each time that you launch an optimization task.
I'm aware that there are other integrations for Solcast in Home Assistant. The REST sensor is another option. So if someone is already using Solcast, then the preferred method is to pass the forecast to EMHASS using lists of data passed at runtime on your shell commands or REST commands.

Thanks, that's really helpful (and yes, I did miss that information - though I did try to read through the documentation before raising the issue).
Thanks for confirmation that improvements to documentation are welcomed; I'll take the time to read it again properly before submitting any suggested changes, so that I can both be sure of all of the contents, as well as suggest changes that make it easier to find things for first time users setting it up.
I know you and other contributors have put a lot of effort into the add on; for those who are running in docker, it's a bit harder to get going and if I can contribute to make that easier, then, when I'm sure that I'm adding value, I will attempt to.
I'll have to look into passing in the forecast, as I'd ideally like to re-optimise regularly (with a five-minute market here in Australia, once a day won't really cut it!).

Passing the forecast data as runtime parameters to the optimizations have several advantages. Solcast has a limited amount of API calls on their free plan, so you can have a better control of API call usage from HA.
I have an automation running that only updates Solcast during the day (when the sun is up), then pass the values as a runtime parameter as part of the REST call:
I create the REST call in a HA script. Create a bunch of value parameters and then set them all together to the runtime call. Here's the code for the solcast value parameter:
solcast=((state_attr('sensor.solcast_pv_forecast_forecast_today',
    'detailedHourly') | map(attribute='pv_estimate') | map('multiply',1000) |
    map('int') | list
      + state_attr('sensor.solcast_pv_forecast_forecast_tomorrow', 'detailedHourly') | map(attribute='pv_estimate') | map('multiply',1000) | map('int') | list))
      [now().hour:][:24] %}

This creates a list that can be sent in the REST JSON.

This creates a list that can be sent in the REST JSON.

Thanks.
I'm slowly figuring this out, but, for the moment, have put any further work on hold: primarily as my training data for the ML optimisation is in kW not W, so I can't utilise the ML forecast of load with any appreciable history.
The second reason is that, unless you use sensors and configuration, it becomes more complex again for what is already complex; that's not a complaint, just an observation.
If I could get around the kW issue, I'd pursue this, but I don't think I can; I've loaded W history data into a new sensor using https://github.com/klausj1/homeassistant-statistics but that doesn't seem to be adequate; whatever this does, it isn't sufficient to populate the history / statistics tables in such a way that EMHASS can then retrieve the data.  Given that it is unsupported, I'm stuck; run ML with a few days of history or just use a naive prediction (which won't be any better than sum of load).

Yes I did not found the time to answer to that second issue. I don't think that adding more configurations parameters will help on getting this easier to set-up.
So we will keep units as they are. However you can still set-up your configuration and use the ML forecaster with that sensor in kW.
Here is how: set a new custom ML forecaster for that sensor in kW. With the long history data that you have you'll certainly obtain some nice results. This custom ML object should provide you with forecast of that sensor in kW. Then on HA create a template sensor that prepares this forecast into a list of values multiplied by 1000 to change from W to kW, then feed that list of values at runtime to the optimization. This totally feasible with the current code as it is without adding more complexity.

Here is how: set a new custom ML forecaster for that sensor in kW

Thanks.  I'll see if I can figure out how to do this.


Ajax call not working inside getToolbarButtons()

Hello ,i need read one config from Web.config file and then create two buttons. I try a ajax call for get the config in getToolbarButtons() but not work. Rare thing, I log de button and my buttons are there but not showing. I think that is something with the ajax call because if a put the buttons.push outside the Ajax work. Other thing that hapend is if i go to mozilla inspect and debug step by step the ts code the, buttons appear after finish. Here my code.
	getToolbarButtons() {
	$.ajax({
				type: 'Post',
				//url: '/Muelle/Fiscal/CreateInvoice',
				url: Q.resolveUrl("~/Fiscal/GetIfElectronica"),
				success(data) {

					try {
						var response = jQuery.parseJSON(data);

						buttons.push({
							title: 'Ver Factura',
							cssClass: 'rvfact',
							onClick: (e) => {
								e.preventDefault();
								window.open(response[1], '_blank');

							}
						});

						buttons.push({
							title: 'Ver Voucher',
							cssClass: 'rvvoucher',
							onClick: (e) => {
								e.preventDefault();
								window.open(response[2], '_blank');

							}
						});

					}
					catch (ex) {
						console.log(ex);
					}

				},
				error(req, stat, err) {
					console.log('No se pudo crear el boton');
				}
			});
			console.log(buttons);
			return buttons;
	}

Auto answer here, the problem was caused by ajax request asyncronous, i dont know if the delay of the request cause function malfunction( in the log the button appear), but change the request to async: false the problem was solved.


Add killable future combinator

Closes #693

@cramertj want to retarget at 0.2 to merge?

@cramertj what's the status here?

Is AtomicTask used to make it safe to move the future to different tasks? What about the case where I'm just doing tokio::spawn(killable_future)? It can't change tasks then, right? So

Any chance to get this in for 0.3?

Closing, opened #1079 targeting 0.3.


[Optimization]optimize and added some permission

Purpose of the pull request

优化一些权限
优化数据源跳转方式
细分添加数据源详情的权限控制
常量化前端权限枚举值

Brief change log

Verify this pull request

This pull request is code cleanup without any test coverage.
(or)
This pull request is already covered by existing tests, such as (please describe tests).
(or)
This change added tests and can be verified as follows:

close #3002
close #3029


Preferences for modified request acceptance

Hi, I wanted to suggest an idea I had a while ago and may or may not have brought up in a meeting.
Instead of designing and implementing a state machine to negotiate modified requests (which I think has the potential to need some fairly complex logic, new endpoints, etc.), can we include flags or some other options in the request to indicate whether or not the caller will accept modifications? This way, the request is guaranteed to be either accepted (fully or with modifications, depending on the preferences) or rejected after only one call.
Example flags to illustrate:

allow-additional-sessions

If server generates sessions in addition to the requested ones, client agrees (tentatively?) to configure them

allow-partial-sessions

If server only wants to configure a subset of the requested sessions, client agrees to configure only those ones

A slightly simpler alternative:

reject-on-mismatch

If request does not exactly match what the server determined, return error

With either of these implementations, in case of a disagreement where client has not agreed to accept changes, return an error explaining what the mismatch was or which options need to be enabled.
I'm not that familiar with these types of negotiations, so if there are scenarios this wouldn't cover, please bring them up and maybe there is a way to account for them.

Thanks - I like the idea, but I think it still is going to require the full state machine, since the client may not configure additional sessions for other reasons (i.e., political).
I could see adding reject-on-mismatch as an easier way to describe requirements, but if we need to add a flag for that, I'm not sure we're actually gaining much.
It's definitely interesting, might be helpful to look at this along side some reference code. :)
What do others think?

In general, I like this idea, as it makes it easier for the client and server to do more peering
For a v0, this additional handshaking may add more complexity that we want to outline in the doc, but I think our spec is open enough that we could add this in a v1 or future version of the spec.
The current way to do it is, if the server wants to request additional sessions, it files a separate request to the client.
If the server wants to accept fewer sessions than those in the full set in the request, does it accept the request and only configure some, or does it reject the request outright and submit a smaller request to the client?
One way to get around the "submitting separate requests" would be as follows:
Accept all and more case:
Client requests sessions as follows: {session1, session2, session3, allow_change=true}
Server decides that it also wants to configure session4
Server replies back with {ACCEPT: session1, session2, session3, session4}
(I thought about adding an additional flag to say "modified", but decided that was unnecessary)
At this point, the server has to commit to configure session1, session2, session3, session4.
The client has to configure session1, session2, and session3.  The client can now decide whether or not to configure session4.
If it does, it comes up.  If it doesn't, session4 gets garbage-collected.
Accept only some case
Client requests sessions as follows: {session1, session2, session3, session4 allow_change=true}
Server decides that it does not want to configure session2
Server replies back with {ACCEPT: session1, session3, session4}
At this point, the server has to commit to configure session1, session3, session4.
The client has to configure session1, session3, and session4.  If the client wants to read back the reply from the server (I think it should, but that's my opinion), the client does not need to configure session2.  If the client wants to take the simplest implementation, it can configure session2 as in its original request and leave it to be cleaned up later.
A requirement in both of these cases is that both sides have good router hygiene and garbage collect their down sessions.  I think this is a good idea in general, but I don't know if it is something we can fix as a standard.
I switched from "allow_additional" to "allow_change" so we would have fewer flags.  "reject_on_mismatch" as proposed by Ben would work as well.

The current way to do it is, if the server wants to request additional sessions, it files a separate request to the client.
If the server wants to accept fewer sessions than those in the full set in the request, does it accept the request and only configure some, or does it reject the request outright and submit a smaller request to the client?

That is not my understanding of it -- the server replies with a different set of sessions, it does not file a separate request to the client.
If the client is happy with the session changes, it would then send a request to the server for that set of sessions, if the server agrees, it would reply with the same set, thus agreeing to everything.
Am I misunderstanding that?
Err, just finished reading your use cases, I believe that's how we've always discussed doing this. Either way, it sounds like we are in agreement with how it should work, which does function without having an allow_change flag.
Adding a flag for that allows a short circuit, which is probably worth adding flags for? Since we don't have other flags, I think I could see it either way. If we did have other flags, I would be all for adding that.


[BUG] Failure when a Uri with a double slash between the storage endpoint and container name is passed to the Storage Client

Describe the bug
Getting the following exception when trying to download blobs using AzureSasCredential or AzurePowerShellCredential:
<?xml version="1.0" encoding="utf-8"?><Error>InvalidQueryParameterValue<Message>Value for one of the query parameters specified in the request URI is invalid.
</Message><QueryParameterName>comp</QueryParameterName><QueryParameterValue /><Reason /></Error>

To Reproduce
The following code fails in the call to the Download() method when using AzureSasCredential and AzurePowerShellCredential (listing containers and blobs works fine).
All operations work fine when using the connection string.
			var accountName = "";
			var accessKey = "";
			var connectionString = $"DefaultEndpointsProtocol=https;AccountName={accountName};" +
				$"AccountKey={accessKey};EndpointSuffix=core.windows.net";

			//var credential = new AzureSasCredential("");
			//var storageUrl = $"https://{accountName}.blob.core.windows.net/";

			var serviceClient = new BlobServiceClient(connectionString);
			//var serviceClient = new BlobServiceClient(new(storageUrl), credential);

			foreach (var container in serviceClient.GetBlobContainers())
			{
				Console.WriteLine(container.Name);
				var containerClient = new BlobContainerClient(connectionString, container.Name);
				//var containerClient = new BlobContainerClient(new Uri($"{storageUrl}/{container.Name}"), credential);
				foreach (var blob in containerClient.GetBlobs())
				{
					Console.WriteLine($"\t{blob.Name}");
					var blobClient = containerClient.GetBlobClient(blob.Name);
					var response = blobClient.Download();
					using var reader = new StreamReader(response.Value.Content);
					reader.ReadToEnd();
				}
			}

Environment:
Azure.Storage.Blobs 12.10.0
Azure.Identity 1.5.0

PS stack trace
   at Azure.Storage.Blobs.BlobRestClient.Download(String snapshot, String versionId, Nullable`1 timeout, String range, String leaseId, Nullable`1 rangeGetContentMD5, Nullable`1 rangeGetContentCRC64, String encryptionKey, String encryptionKeySha256, Nullable`1 encryptionAlgorithm, Nullable`1 ifModifiedSince, Nullable`1 ifUnmodifiedSince, String ifMatch, String ifNoneMatch, String ifTags, CancellationToken cancellationToken)
   at Azure.Storage.Blobs.Specialized.BlobBaseClient.StartDownloadAsync(HttpRange range, BlobRequestConditions conditions, Boolean rangeGetContentHash, Int64 startOffset, Boolean async, CancellationToken cancellationToken)
   at Azure.Storage.Blobs.Specialized.BlobBaseClient.DownloadStreamingInternal(HttpRange range, BlobRequestConditions conditions, Boolean rangeGetContentHash, String operationName, Boolean async, CancellationToken cancellationToken)
   at Azure.Storage.Blobs.Specialized.BlobBaseClient.DownloadInternal(HttpRange range, BlobRequestConditions conditions, Boolean rangeGetContentHash, Boolean async, CancellationToken cancellationToken)
   at Azure.Core.Pipeline.TaskExtensions.EnsureCompleted[T](Task`1 task)
   at Azure.Storage.Blobs.Specialized.BlobBaseClient.Download(HttpRange range, BlobRequestConditions conditions, Boolean rangeGetContentHash, CancellationToken cancellationToken)
   at Azure.Storage.Blobs.Specialized.BlobBaseClient.Download(CancellationToken cancellationToken)
   at Azure.Storage.Blobs.Specialized.BlobBaseClient.Download()
...

@andrei-faber We are looking into this and get back to you.

@andrei-faber How are you generating the AzureSasCredential as SAS credential expects a SAS token. Can you please share the code.

@SaurabhSharma-MSFT manually via the portal. It does work for listing blobs.
Also, plz note that same bug happens when using AzurePowerShellCredential.

PS StorageSharedKeyCredential throws same error, with same storage name and access key as used in the connection string (that works)

PS StorageSharedKeyCredential throws same error, with same storage name and access key as used in the connection string (that works)

Sounds like something is different in the endpoint that's being passed then. Let's take this offline, I will send you an email @andrei-faber

Came to a conclusion offline. Looks like there's a bug within the BlobUriBuilder which is triggered when a customer passes the Uri with a double slash between the Blob Endpoint and the container name.
e.g. https://{accountName}.blob.core.windows.net**//**{containerName}
This is due to the parsing method, we see the container name to be between two slashes but since there isn't, we assumed there's no container name. Thus causing the error above, since it creates a blob URL that no longer has the container name (or blob name).
Looking into considering a fix into all the {storageService}UriBuilders.
As a mitigation, the appended slash must be removed.
e.g. var containerClient = new BlobContainerClient(new Uri($"{storageUrl}{container.Name}")

I ran into this one as well, thanks for pointing out this bug.