[Bug] Player "lose" aspects after re-login to server

Overview
I see this issue only on an dedicated server, and have not see this happen on singleplayer game.
It may not reproduce every time when you re-login after logging out from server.
In other words, the problem may not be reproduced stably.
How to reproduce

Unlock some researches by scanning or researching.
Log out from the dedicated server, then re-login.
If this issue is successfully reproduced, you will see your Aspects are lost, their icons become dim, just like it was not unlocked.
Do some scanning or obtain some Aspects. If you have unlocked a research corresponding to this scan or Aspects before this issue happens, it will be unlocked again.

If any other information is needed, feel free to tell me in reply. I will provide it as soon as possible.
Thanks in advance.

I was able to reproduce this error, thank you for creating this detailed issue. I'll be working on fixing this for the 1.1.3 release. Hope you enjoy the mod!

should be fixed with this commit: https://github.com/Wong-Innovations/TC4Research/commit/268a3c549303b1bdf8f94d78e1a6aa1f917213ba


[releng] simpler way to add jfxswt.jar

Avoid extra installation check (with hard coded path to jfxswt.jar) by specifying the path in the pom.xml file itself.

Looks good. I remember to have tried this myself about a year ago but it didn't work then, I guess because of some tycho bug. Great if it works in the meantime,


Use Ephemeral OS on workers?

In what area(s)?

/area cyclecloud

Describe the feature

Hi Xavier,
I was looking at the Azure docs and noticed that we have ephemeral OS disks as an option for many VMs. Cyclecloud supports this since 7.7 I think. Is there a reason we don't use it on the workers by default? Cyclecloud claims it boots quicker, but I haven't checked closely
Thanks!
Matt
cc @ltalirz

I just verified. The workers start much faster with ephemeral OS. I can get a worker in about 6-9 minutes, as opposed to ~15 on regular disks.

good suggestion, however ephemeral disks doesn't exists for all VM type; but we can add an option to enable it.


[428] Better error handling in Xef Server

This PR will be updated in order to work with Arrow.

I have tried the code locally and everything works as expected. We will address to include Arrow lib in a separate PR

Are you going to use Arrow's Either and EitherNel for error handling? What are your plans?

I have tried the code locally and everything works as expected. We will address to include Arrow lib in a separate PR

Are you going to use Arrow's Either and EitherNel for error handling? What are your plans?

The plan is to apply the same approach as here: https://github.com/nomisRev/ktor-arrow-example/pull/35/files#diff-fd19be7abb78848f1cf6bc8da926adafd98399c75cf49662e9a8dcc29f7f3cb0R33


Recording ends too soon - possible switch to camera’s built in detection

Describe the bug
Recordings are ending too soon and not capturing the hole “event”.
To Reproduce
If the “object” is triggering motion and remains in the cameras view for greater than 13 seconds the recording ends while the “object” remains in view (and moving).
Expected behavior
The camera continues to capture the entirety of the event while the “object“ remains in view.
Also of note. if I attempt to alter the videoanalysis settings the recordings become inconsistent and then do not record as expected.
Lastly. I have an Amcrest doorbell and I happen to like it’s built in motion detection. Is there a way to utilize it instead of the videoanalysis through camera.ui?
Thanks for taking your time to help!

Camera.ui supports multiple ways of motion detection.
If you want to use the built in motion detection from your camera, you can use SMTP (email) or FTP

That would be amazing! I’ll have to try to find a guid as I’m not very well versed in this kinda stuff. Thank you for your quick response! I’m just happy to know it’s an option.

SMTP:
https://github.com/seydx/homebridge-camera-ui/wiki/SMTP-Config
FTP:
https://github.com/seydx/homebridge-camera-ui/wiki/FTP-Config
MQTT:
https://github.com/seydx/homebridge-camera-ui/wiki/MQTT-Config

Wonderful thank you!
and just out of curiosity what settings in the videoanalysis settings should I adjust to allow for longer record times?

https://github.com/seydx/homebridge-camera-ui/wiki/Videoanalysis
Reset motion after: 0
Dwell time: 60

I’ll try that first before diving into it. Thanks again. I’ll adjust those settings now and report back here for anyone else looking for the same thing.

I’ve been adjusting and playing with the settings of the course of the past 2 weeks and no matter the setting(s) the recording still ends early, prior to the object leaving the cameras view.
Is there anything else I could do to make it record properly/longer?

I’ve been adjusting and playing with the settings of the course of the past 2 weeks and no matter the setting(s) the recording still ends early, prior to the object leaving the cameras view.
Is there anything else I could do to make it record properly/longer?

Did you get it worked out? I have the same issue and I don't know how to fix it


Asserting state on current page after button click, but before next page loads

We have a submission button that becomes disabled while waiting for the operation to complete. In this case, the operation completes by navigating to the /dashboard page.
We would like to assert this 'disabled while pending' behaviour in our end-to-end Protractor tests:
it('should disable button after submission', function(){
  page.usernameTextBox.sendKeys(username);
  page.passwordTextBox.sendKeys('password1');
  page.signInButton.click();
  expect(page.signInButton.getAttribute('disabled')).toContain('true');
  expect(browser.getCurrentUrl()).toContain('/dashboard');
});

The assertion on the disabled attribute fails as the next page has already loaded. This is because Protractor waits for the operation to complete before running the assertion - i.e. its not being missed due to a race condition - Protractor actually has it synchronised so that the assertion will not be run until the operation completes.
How can we test the above behaviour?

You can use browser.ignoreSynchronization = true, but I would caution against testing this kind of timing-specific thing in end to end tests, because sometimes the test will be running slowly and even without synchronization your test will fail.
Please read the contributing guidelines; these types of questions are ill-suited for GitHub. Thanks!


HTTP 302 and "data folder is accessible"

RainLoop version, browser, OS:
CentOS, nginx
Expected behavior and actual behavior:
It should not show notice message if after denied data directory it redirects user with 302 to web site itself.
Steps to reproduce the problem:
Change config files in nginx from:
location ^~ /data {
    deny all;
  }

to
location ^~ /data {
    deny all;
    return 302 /;
  }

Logs or screenshots:

This is a big problem in nextcloud installations with the default nginx configuration, as the nextcloud always redirects to the default app page when accessing the link, but
https://github.com/RainLoop/rainloop-webmail/blob/19d3b559dadc4fbd647e085263257a84f5672be5/dev/Stores/Admin/App.js#L30
follows 302 redirects and accepts the following 200. This should be checked more precisely and/or redirect following should be removed in that feature.

https://github.com/pierre-alain-b/rainloop-nextcloud would be the right place to post this. Probably there is already a report.


Add third, optional 'opts' argument to sort function

I am using this module via bumped-finepack (bumped -> bumped-finepack -> finepack -> sort-keys-recursive) on this package.json:
{
"stylelint": {
    "extends": "stylelint-config-standard",
    "rules": {
      "at-rule-no-unknown": [
        true,
        {
          "ignoreAtRules": [
            "each"
          ]
        }
      ]
    }
  }
}

This is the output:
{
"stylelint": {
    "extends": "stylelint-config-standard",
    "rules": {
      "at-rule-no-unknown": [
        {
          "ignoreAtRules": [
            "each"
          ]
        },
        true
      ]
    }
  }
}

Unfortunately sort() (correctly) sorts at-rule-no-unknown and breaks stylelint, leaving two choices: disabling linting or having to move the whole object outside package.json.
A simple, backwards compatible solution for these cases could be to change the sort function to accept a new, third optional argument of type object and name opts:
function sort (something, compareFn, opts) {
The opts object could be structured like this:
var options = {
  ignoreObjectAtKeys: [ // or skipObjectAtKeys.
      'rules'
  ],
  ignoreArrayAtKeys: [ // or skipArrayAtKeys. Not needed in this case, but nice to have too.
  ]
}

It would be easy to ignore the requested arrays/objects with a quick check in the main loop.
Then a small modification to finepack to document the new key in options, which may be called sortOptions:
var options = {
  filename: filename, // for customize the output messages, but is not necessary.
  validate: false, // For enable (or not) keys validation (false by default).
  color: false, // For enable (or not) colorize or not the output (false by default).
  sortOptions: { // Options to pass to the sort module that is used internally.
    ignoreObjectAtKeys, // don't sort the Object at the specified key, if any.
    ignoreArrayAtKeys // don't sort the Array at the specified key, if any.
  }
}

finepack would check if sortOptions was true and in case pass it to this module as the third argument.
I could submit PRs to both modules with the small mods to code, readme and tests.

I understand your problem, but looks a very specific case for be handle in this library?
why true? exists a way to prefix the value with a keyword?

Hello @kikobeats, unfortunately the stylelint rules object only allows an array with two values when you need to pass configuration to a rule; the first must be a boolean | string (depends on the allowed values for the 'rule') and the second an object.
Even in those cases where the expected first value is a string such as "always", the default sort function would still move the object to the start of the array and break the rule: e.g ["always", {}].sort(). The only exception could be modifying stylelint to allow 1 as an alias of boolean true (sort() would not switch the elements then), but It would almost certainly be rejected or seen as not necessary.
I agree that the use case is specific, but I think that the proposed configuration parameters can be considered generic and make the module more configurable.  😄

Check it: https://github.com/Kikobeats/finepack/blob/master/lib/Finepack.coffee#L48
By default I'm using sort alphabetically using this library but later I sort a set of properties for esthetic.
Have sense add this new feature and also update finepack for handle it correctly.
what do you think about PR? 😄

👍 next PR is for finepack.

@matteocng I'm going to release v2, thanks for that 😄


ci: remove sbom step

Because there is no one to maintain the system.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

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

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
1231

Relevant Lines:
1498

💛  - Coveralls


Scm css fix for keyboard navigation and actions Issue

Fix for issue #23608
Fixes lack of action icons on resource group header selection

Cherry-picked your commit to 3f15d518d to avoid the 9 merge commits you have created.
Thanks! 🍻

@joaomoreno
I missed your comment until now - could you give me a pointer how I avoid
the merge commits they get created when I update my master fork and subsequently
the branch in use?
it sounds like I'm doing something wrong that makes more work for you guys when I do  a PR ?
also FYI I'm going to add another SCM list modification in PR #24119 for list navigation

Basically you don't need to continue to pull from Microsoft/master, once you are in your branch.


CrossFirebasePushNotification.Current.Subscribe("TOPIC"); Not working on IOS

If you are creating an issue for a BUG please fill out this information. If you are asking a question or requesting a feature you can delete the sections below.
Failure to fill out this information will result in this issue being closed. If you post a full stack trace in a bug it will be closed, please post it to http://gist.github.com and then post the link here.
Bug Information
Version Number of Plugin: 2.3.6
Device Tested On: IOS Device
Steps to reproduce the Behavior
CrossFirebasePushNotification.Current.Subscribe("TOPIC");
var subList = CrossFirebasePushNotification.Current.SubscribedTopics;
Debug.WriteLine($"sub count: {newList.Length}");
for (int i= 0; i < subList.Length; i++)
{
Debug.WriteLine($"Subscribed to: {subList[i]}");
 }
Expected Behavior
IOS device should receive notifications from sub topic and show it is registered to such topic
Actual Behavior
IOS device doesn't receive notifications to given topic. I have tested that my implementation is properly setup as i can receive topic notifications on android and i can receive push notification to the IOS device with the device token id using a post man request.
Code snippet
try {
Debug.WriteLine("Register FCM subscription topics");
await CrossFirebasePushNotification.Current.RegisterForPushNotifications();
var nToken = CrossFirebasePushNotification.Current.Token;
Debug.WriteLine($"Notification token: {nToken}");
//get sub list
var list = CrossFirebasePushNotification.Current.SubscribedTopics;
CrossFirebasePushNotification.Current.Subscribe(Settings.LinkId);
switch (Settings.Language)
{
case "en":
     if (list.Contains("general_es"))
    CrossFirebasePushNotification.Current.Unsubscribe("general_es");
   if (!list.Contains("general"))
     CrossFirebasePushNotification.Current.Subscribe("general");
     break;
case "es":
    if (list.Contains("general"))
    CrossFirebasePushNotification.Current.Unsubscribe("general");
    if (!list.Contains("general_es"))
    CrossFirebasePushNotification.Current.Subscribe("general_es");
     break;
default:
     CrossFirebasePushNotification.Current.Unsubscribe("general_es");
     CrossFirebasePushNotification.Current.Subscribe("general");
     Settings.Language = "en";
     break;
}
var newList = CrossFirebasePushNotification.Current.SubscribedTopics;
Debug.WriteLine($"sub count: {newList.Length}");
for (int i= 0; i < newList.Length; i++)
{
Debug.WriteLine($"Subscribed to: {newList[i]}");
}
}             catch (Exception ex)
{
Debug.WriteLine(ex.Message);
Debug.WriteLine(ex.Source);
}

Did you ever find a fix for this? I am having the same issue

I'm experiencing this problem also.
Did you ever find a fix for this?

same issue here. someone got a fix?

Also having this issue - can receive 'normal' notifications but none for topics the device is subscribed to. I suspect something is going wrong with the subscription but I'm not seeing any errors when it happens.
As an aside, why this issue closed with no explanation?

Also having this problem with the current version

same problem....


getting started help

Hey Darren,
I was teaching my 7 year old son how to play lemonade stand today on the xbox. Got me thinking about rewriting the game. I figured I'd do a quick search on Gh to see if anyone else had anything and I found your gem. I spent the last 30m or so reviewing and I'd like to see if / how I can help if you'd be interested.
I'd also like to practice some of my frontend chops so maybe we can turn this into an interactive game of sorts.
I checked your readme and tried to boot both the game on console but I get
./play_ls
/Users/davidwoodall/.rbenv/versions/2.1.2/lib/ruby/2.1.0/rubygems/core_ext/kernel_require.rb:55:in `require': cannot load such file -- lemonade_stand (LoadError)
	from /Users/davidwoodall/.rbenv/versions/2.1.2/lib/ruby/2.1.0/rubygems/core_ext/kernel_require.rb:55:in `require'
	from ./play_ls:3:in `<main>'

Also,
what command are you using to run the specs?
bundle exec rake isn't working for me for some reason
Thanks!

Also, I tried running the tests and got;
$ bundel exec rake
rake aborted!
Don't know how to build task 'default'

(See full trace by running task with --trace)

Hmm... I'm not sure, but I'll take a look this weekend!
I'll get the tests running through CI to verify they work outside of my computer. Then we'll see where to go from there.
I'll tag you on this ticket when I have some progress.

Actually, I figured it out last nigh;
I hadn't used rakes test method before, but the specs run (and all pass) when I do
bundle exec rake test
I'll add it to the README  :+1:


Support to disable telemetry from third party applications

Bloatynosy supports it and the script can be find here: https://github.com/builtbybel/Bloatynosy/blob/main/mods/remove_telemetry-third-party-apps.ps1

Heya,
Thanks for the suggestion, but unfortunately I don't think that making changes to third party software falls within the scope of this script.


fix: skip building tensorrt yolox packages if cuda is not found

Signed-off-by: Daisuke Nishimatsu<EMAIL_ADDRESS>Description
skip building cuda_utils, tensorrt_common, tensorrt_yolox if cuda is not found.
Related:

https://github.com/autowarefoundation/autoware.universe/pull/2370
https://github.com/autowarefoundation/autoware.universe/actions/runs/3583250712
https://github.com/autowarefoundation/autoware.universe/issues/2409

Pre-review checklist for the PR author
The PR author must check the checkboxes below when creating the PR.

[x] I've confirmed the contribution guidelines.
[x] The PR follows the pull request guidelines.

In-review checklist for the PR reviewers
The PR reviewers must check the checkboxes below before approval.

[ ] The PR follows the pull request guidelines.

Post-review checklist for the PR author
The PR author must check the checkboxes below before merging.

[ ] There are no open discussions or they are tracked via tickets.

After all checkboxes are checked, anyone who has write access can merge the PR.

CI: https://github.com/autowarefoundation/autoware.universe/actions/runs/3584399815


Element.toggleAttribute breaking users

Problem
Today I wanted to use the Dartpad as normal, but it didn't work anymore.
I looked in the console and found this line throwing the issue.
It seems like the polymer is broken.
The error was introduced in this commit which ways 2 days ago.
Solution
To fix it I quickly disabled the line, but then there are obviously some graphical issues. The real fix should be pretty easy.

May I ask which browser you are using?

It was Firefox. I also tried it in IE, but got a null error.


macOS VPN: Mitigate TunnelVision exploit

Task/Issue URL:
Tech Design URL:
CC:
Description:
Steps to test this PR:
1.

Definition of Done:

[ ] Does this PR satisfy our Definition of Done?

Internal references:
Pull Request Review Checklist
Software Engineering Expectations
Technical Design Template
Pull Request Documentation

Closing this as it was superseded by a different solution.


Make a NPM package

related #2

@onemanstartup https://www.npmjs.com/package/typesettings

@ianrose thanks!

Hi there! It seems that NPM package doesn't work properly. It fails when try to require typesettings.
https://tonicdev.com/npm/typesettings

@Lighttree can you elaborate the use case for including Typsettings in a project this way?

Just testing it out - seeing if it worth using in my next
project...why'd you ask?
----- Original Message -----
From: "ianrose/typesettings"
To:"ianrose/typesettings"
Cc:
Sent:Tue, 09 Feb 2016 05:40:58 -0800
Subject:Re: [typesettings] Make a NPM package (#39)
@Lighttree [1] can you elaborate the use case for including

Typsettings in a project this way?
—

Reply to this email directly or view it on GitHub [2].
Links:
[1] https://github.com/Lighttree
[2]
https://github.com/ianrose/typesettings/issues/39#issuecomment-181868446

@ianrose I've discovered this way of importing yesterday from bourbon npm install. to be honest :)
'use strict';

var gulp = require('gulp');
var $ = require('gulp-load-plugins')();
var bourbon = require('bourbon');
var input = 'src/assets/styles/**/*.scss';
var devOutput = '.tmp/assets/styles';
var prodOutput = 'dist/assets/styles';
var sassOptions = {
    includePaths: [bourbon.includePaths],
    errLogToConsole: true,
    outputStyle: 'expanded'
};
var sourcemapsOptions = {
    includeContent: false,
    sourceRoot: './' // use the file's folder as source root
};

gulp.task('styles', function () {
    return gulp
        // Find all `.scss` files from the `stylesheets/` folder
        .src(input)
        .pipe($.sourcemaps.init())
        // Run Sass on those files
        .pipe($.sass(sassOptions).on('error', $.sass.logError))
        .pipe($.sourcemaps.write(sourcemapsOptions))
        // Write dev version of CSS in the output folder
        .pipe(gulp.dest(devOutput))
        // Write prod version of CSS in output folder
        .pipe($.if('*.css', $.csso()))
        .pipe(gulp.dest(prodOutput))
        .pipe($.size({title: 'styles'}));
});

bourbon.includePath allows resolve naming issue and import bourbon as @import "bourbon";
I was thinking that this is some kind of agreement that NPM modules should export such API. But probably not :)


[open62541] Update version to 1.3.4

Please get failure logs here.

Pinging @autoantwort for response. Is work still being done for this PR?

I think I can close this temporarily


translate nix => ESM

{ config, pkgs, ... }:

{
    # Import other configuration modules
    # (hardware-configuration.nix is autogenerated upon installation)
    # paths in nix expressions are always relative the file which defines them
    imports =
        [
            ./hardware-configuration.nix
            ./my-dev-tools.nix
            ./my-desktop-env.nix
            ./etc.nix
        ];

    # Name your host machine
    networking.hostName = "mymachine";

    # Set your time zone.
    time.timeZone = "Europe/Utrecht";

    # Enter keyboard layout
    services.xserver.layout = "us";
    services.xserver.xkbVariant = "altgr-intl";

    # Define user accounts
    users.extraUsers =
        {
            myuser =
            {
                extraGroups = [ "wheel" "networkmanager" ];
                isNormalUser = true;
            };
        };

    # Install some packages
    environment.systemPackages =
            with pkgs;
            [
                ddate
                testdisk
                zsh
            ];

    # Enable the OpenSSH daemon
    services.openssh.enable = true;

}

{ config, pkgs, ... }:

{
    # Import other configuration modules
    # (hardware-configuration.nix is autogenerated upon installation)
    # paths in nix expressions are always relative the file which defines them
    imports =
        [
           ${[].join('\n')}
        ];

    # Name your host machine
    networking.hostName = "mymachine";

    # Set your time zone.
    time.timeZone = "Europe/Utrecht";

    # Enter keyboard layout
    services.xserver.layout = "us";
    services.xserver.xkbVariant = "altgr-intl";

    # Define user accounts
    users.extraUsers =
        {
            myuser =
            {
                extraGroups = [ "wheel" "networkmanager" ];
                isNormalUser = true;
            };
        };

    # Install some packages
    environment.systemPackages =
            with pkgs;
            [
                ddate
                testdisk
                zsh
            ];

    # Enable the OpenSSH daemon
    services.openssh.enable = true;

}

ok nix format is ini format + function + array space new line sperated.

@milahu please start reviewing README.md and launch.js

@milahu i putted your backend stuff into launch.js and in the readme are the new start instructions as this does not really depend on a package.json ok at present it will do as we have no global package cache but that will change
this uses puppeteer and our CDP pipe it allows you to directly start extensions and PWA's via puppeteer launch
will refactor your repl soon to use streams did started with that you can start inspecting it.
when all is refactored to streams i guess it will be less lines of code and you will understand the concepts more easy this replaces electron and has full devtools access via so called stdio pipe

the importent part was the refactoring on your code

no, you just did some copy paste

the references of the nix import are correct that is exactly what a web-module should export specifier and integrity hash

stop talking, just do it
implement a working prototype, then we can talk


About the build process

The build process using command line on windows fails to build examples. I see 3 errors:

when I ask to use more than 1 core with -j 8, the examples are built immediately, and of course they fail since the library is not built yet. This is probably a side-effect of 3.

the c++11 config added in your last is not "expanded" to examples\makefile.release. You can remove from qt-material-widgets.pro and add in examples.pro. Now -std=c++0x is added and compilation is ok. I don't know why it "downgrades" to c++0x but qmake knows better than me...

The dependency of the lib is not satisfied.

win-make[2]: Entering directory 'C:/cvs/qt-material-widgets/components'
win-make[2]: Nothing to be done for 'first'.
win-make[2]: Leaving directory 'C:/cvs/qt-material-widgets/components'
win-make[1]: Leaving directory 'C:/cvs/qt-material-widgets/components'
cd examples\ && ( if not exist Makefile C:\qt\qt5.5.0\5.5\mingw492_32\bin\qmake.exe C:\cvs\qt-material-widgets\examples\
examples.pro -o Makefile ) && C:/cvs/harbour/win-make -f Makefile
win-make[1]: Entering directory 'C:/cvs/qt-material-widgets/examples'
C:/cvs/harbour/win-make -f Makefile.Release
win-make[2]: Entering directory 'C:/cvs/qt-material-widgets/examples'
win-make[2]: *** No rule to make target '../components/libcomponents.a', needed by 'examples-exe.exe'.  Stop.
win-make[2]: Leaving directory 'C:/cvs/qt-material-widgets/examples'
Makefile:34: recipe for target 'release' failed
win-make[1]: *** [release] Error 2
win-make[1]: Leaving directory 'C:/cvs/qt-material-widgets/examples'
makefile:64: recipe for target 'sub-examples-make_first' failed
win-make: *** [sub-examples-make_first] Error 2

I had to add the directory to examples.pro:
diff --git a/examples/examples.pro b/examples/examples.pro
index b53fb99..a29c562 100644
--- a/examples/examples.pro
+++ b/examples/examples.pro
@@ -1,4 +1,5 @@
 QT += core gui widgets
+CONFIG += c++11
 TEMPLATE = app
 SOURCES = mainwindow.cpp \
     main.cpp \
@@ -39,10 +40,10 @@ HEADERS = mainwindow.h \
     dialogsettingseditor.h \
     drawersettingseditor.h \
     scrollbarsettingseditor.h
-LIBS += ../components/libcomponents.a
+LIBS += ../components/release/libcomponents.a
 INCLUDEPATH += ../components/
 TARGET = ../examples-exe
-PRE_TARGETDEPS += ../components/libcomponents.a
+PRE_TARGETDEPS += ../components/release/libcomponents.a

 RESOURCES += \
     examples.qrc

I created a pull request for point 2 but not for point 3 since it seems that compilation is working for you.
I then deleted my form and created a new one since I messed it up too much and was not able to reset it... easier to delete and fork again.

The directory structure is probably different on Windows. I am using Ubuntu. There must be a standard, cross-platform way to do it though. I will search around for it later.

I made this change and added this file. Could you try and see if it works in your build env. also.

created a PR... as I said I'm a novice git user and it takes me a lot of time just to create a simple PR....

Ok. Thanks, and sorry about that. One thing though; could the TARGET be set to
TARGET = $$top_builddir/examples/examples-exe

That relative path is problematic here. Don't worry about making the changes in git. I just want to make sure it doesn't mess up your setup before I push it to master.

no, it can't be used this way on windows, unfortunately.
If you can't use relative paths (why?) just keep examples-exe
C:\qt\qt5.5.0\5.5\mingw492_32\bin\qmake.exe -o Makefile examples.pro
WARNING: DESTDIR: Cannot access directory 'release\C:\cvs\qt-material-widgets-fperillo\examples'
WARNING: DESTDIR: Cannot access directory 'debug\C:\cvs\qt-material-widgets-fperillo\examples'

Ok, leaving it just as examples-exe works now. That seems much easier then. I don't know why, but for some reason it was giving me some permission errors before. So, TARGET = examples-exe is working for you then, or?

Please reopen if it is not working. I may have changed some other variables in the build file after this.

revise examples.pro to this:
`QT += core gui widgets
TEMPLATE = app
CONFIG += c++11
SOURCES = mainwindow.cpp
main.cpp
avatarsettingseditor.cpp
badgesettingseditor.cpp
checkboxsettingseditor.cpp
fabsettingseditor.cpp
raisedbuttonsettingseditor.cpp
flatbuttonsettingseditor.cpp
iconbuttonsettingseditor.cpp
progresssettingseditor.cpp
circularprogresssettingseditor.cpp
slidersettingseditor.cpp
radiobuttonsettingseditor.cpp
togglesettingseditor.cpp
textfieldsettingseditor.cpp
tabssettingseditor.cpp
snackbarsettingseditor.cpp
dialogsettingseditor.cpp
drawersettingseditor.cpp
scrollbarsettingseditor.cpp
appbarsettingseditor.cpp
autocompletesettingseditor.cpp
menusettingseditor.cpp
HEADERS = mainwindow.h
avatarsettingseditor.h
badgesettingseditor.h
checkboxsettingseditor.h
fabsettingseditor.h
raisedbuttonsettingseditor.h
flatbuttonsettingseditor.h
iconbuttonsettingseditor.h
progresssettingseditor.h
circularprogresssettingseditor.h
slidersettingseditor.h
radiobuttonsettingseditor.h
togglesettingseditor.h
textfieldsettingseditor.h
tabssettingseditor.h
snackbarsettingseditor.h
dialogsettingseditor.h
drawersettingseditor.h
scrollbarsettingseditor.h
appbarsettingseditor.h
autocompletesettingseditor.h
menusettingseditor.h
win32{
LIBS += $$top_builddir/components/$(OBJECTS_DIR)/components.lib
INCLUDEPATH += $$top_srcdir/components/
TARGET = examples-exe
PRE_TARGETDEPS += $$top_builddir/components/$(OBJECTS_DIR)/components.lib
}
else {
LIBS += $$top_builddir/components/$(OBJECTS_DIR)/libcomponents.a
INCLUDEPATH += $$top_srcdir/components/
TARGET = examples-exe
PRE_TARGETDEPS += $$top_builddir/components/$(OBJECTS_DIR)/libcomponents.a
}
RESOURCES +=
examples.qrc
FORMS +=
avatarsettingsform.ui
badgesettingsform.ui
checkboxsettingsform.ui
fabsettingsform.ui
flatbuttonsettingsform.ui
iconbuttonsettingsform.ui
progresssettingsform.ui
circularprogresssettingsform.ui
slidersettingsform.ui
snackbarsettingsform.ui
radiobuttonsettingsform.ui
togglesettingsform.ui
textfieldsettingsform.ui \
tabssettingsform.ui
dialogsettingsform.ui
drawersettingsform.ui
scrollbarsettingsform.ui
appbarsettingsform.ui
`


right justify has some oddities

Given this text:
there is enough text here to make  multiple lines once you factor in word wrap.\n\nAnd here is a whole new line all together!

With font size of 50 and a word wrap of 200, and align set to justify I get this:

There are several things I can see wrong.

here to make - "make" isn't at the right edge
the second sentence "And" doesn't start at the left edge
the end of the first line of the second sentence "a" isn't at the right edge

This is basically the same issue (or at least the same fix) as #5. I'mn going to mark it as a duplicate.


Tray

closes #19

Thanks so much for this @blukai 😄
Works awesome 👍
Perhaps is there a way to see whether what preferences are selected in the system tray?

@anshumanv Sure, I'll add indicators. 🍀

Thanks for the quick addition. 🍀
Works amazing!
Keep sending such 🔝 quality PRs. 😄

Please join - https://gitter.im/ongaku-desktop/Lobby# for further discussing on how to enhance it. 😄


Make PropertyBuilder.IsRowVersion() Relational

Even though the configuration performed by IsRowVersion is not relational-specific, the name and the common usage scenario is.

@AndriySvyryd Any more data than when we discussed this before? See https://github.com/aspnet/EntityFrameworkCore/pull/6408#issuecomment-242519753 :trollface:

@ajcvickers No, previous discussions have been GC'ed from my memory.

You should have maintained a reference. ;-)

Triage: TL;DR no change.
Before the information gets collected again:

Yes, it's SQL Server specific, but we have the API, and we had it in EF6, so inventing something new has usability cost
All it really means is, "use this property for automatic optimistic concurrency". That might be offline lock, or something specific to the provider.

This is similar to how ValueGeneratedOnAdd doesn't specify how this is achieved, just that it should happen.


remove all buckets

I Use Redis and Redisson for distribution support.
I want the new configuration(capacity, interval, ExpirationAfterWriteStrategy,...) to take effect on the existing buckets on redis cache after restarting the application, but in my test if a specific bucket already exists in redis, the new configuration are not applied(because defualt ExpirationAfterWriteStrategy is none and  existing buckets are not delete ). Is there a way to delete all buckets present in Redis(i cann't use replaceConfiguration because i don't know bucket keys)?

i cann't use replaceConfiguration because i don't know bucket keys

Implicit-configuration-replacement is designed for such case.

Thankyou for your response
Is way to get version of current configuration?

in order to keep track of versions i have to keep version of current instance in separate cache in order to get it on server startup and increment it to newer version. in case of multi instance servers this might be an issue because all servers will get this cache and increment it.

You can store the version in application configuration. It is obviously that in case of upgrade different instances of your application will have different version until whole cluster will be upgraded, but it is not problem, the design of implicit configuration replacement covers such case - configuration is being replaced when it detected that persisted version is less than configured version, but configuration is not being replaced when persisted version is greater than configured, so having different nodes with different versions is not problem, it is covered by design. Just start to count version from 1 in new deployment and all active buckets will be reconfigured after upgrade. Of course, buckets that will not be used after upgrade will not be reconfigured.

so is there any way to get cache name created for the proxy and remove all elements in cache on startup.

No, there is no such functionality.


Add support schema prefix sqlparser

This PR adds support to parse the qualified name of a table (format: schema.table) from a SQL statement. This PR also adds the type DbTableName to wrap the string table name value.

I think we should keep the schema from the parser and provide the current connection schema as implicit when the sql is just using the table name

Good point. I'll make the change to support this 👍


uuid.MustParse should panic error in error type

Currently MustParse panic the error in string type,
panic should be an error type, so the recover can have consistance use of err.Error()

Hello. I agree with @pborman that changing the value passed to panic now would be backwards incompatible to existing uses of recover catching this panic. There is no requirement that the panic be given an error, a string is allowed. So for these reasons, I will close this. Thanks for the consideration.


Reporting package with CSV failure reasons and pretty print to CLI

With this PR we kick start the report package, issue #77, and tackle two other issues that are discovering the CSV failure reasons (issue #93) and pretty printing results to user's terminal (issue #8). I have the intention to commit a writeToFile option before merging this that potentially could be the first option to grab data to upload and make reports. I Posted this PR in draft mode for people to check the work.

@yashoza19 @mrhillsman This is ready to review. I just put the do not merge hold label to avoid the automatic merge. Whenever you have time.

/lgtm


Pagination: Export the template for Pages as input.

This way of displaying the pagination seems to be very common. Let's provide it in AgnosUI more than with an example.

To review later if we really want it or not.
Currently, we tend to think this should be provided by the design systems that use AgnosUI instead.


Module "dev.gitlive:firebase-auth" has a reference to symbol dev.gitlive.firebase.auth/FirebaseUser.displayName..

Using dev.gitlive:firebase-auth:1.6.1
I'm getting this error when trying to access  Firebase.auth
This could happen if the required dependency is missing in the project. Or if there is a dependency of "dev.gitlive:firebase-auth" that has a different version in the project than the version that "dev.gitlive:firebase-auth" was initially compiled with. Please check that the project configuration is correct and has consistent versions of all required dependencies.

The list of "dev.gitlive:firebase-auth" dependencies that may lead to conflicts:
1. "kotlin" (a library with unknown version)
2. "dev.gitlive:firebase-app" (a library with unknown version)
3. "dev.gitlive:firebase-common" (a library with unknown version)
4. "org.jetbrains.kotlinx:atomicfu" (a library with unknown version)
5. "org.jetbrains.kotlinx:kotlinx-coroutines-core" (a library with unknown version)
6. "org.jetbrains.kotlinx:kotlinx-serialization-core" (a library with unknown version)

Project dependencies:
+--- kotlin
+--- androidx.compose.runtime:runtime
|    +--- kotlin
|    +--- org.jetbrains.kotlinx:atomicfu
|    |    \--- kotlin
|    \--- org.jetbrains.kotlinx:kotlinx-coroutines-core
|         +--- kotlin
|         \--- org.jetbrains.kotlinx:atomicfu (*)
+--- app.softwork:kotlinx-uuid-core
|    +--- kotlin
|    \--- org.jetbrains.kotlinx:kotlinx-serialization-core
|         \--- kotlin
+--- app.softwork:routing-compose
|    +--- kotlin
|    +--- androidx.compose.runtime:runtime (*)
|    +--- app.softwork:kotlinx-uuid-core (*)
|    +--- org.jetbrains.compose.web:internal-web-core-runtime
|    |    +--- kotlin
|    |    +--- androidx.compose.runtime:runtime (*)
|    |    +--- org.jetbrains.kotlinx:atomicfu (*)
|    |    \--- org.jetbrains.kotlinx:kotlinx-coroutines-core (*)
|    +--- org.jetbrains.compose.web:web-core
|    |    +--- kotlin
|    |    +--- androidx.compose.runtime:runtime (*)
|    |    +--- org.jetbrains.compose.web:internal-web-core-runtime (*)
|    |    +--- org.jetbrains.kotlinx:atomicfu (*)
|    |    \--- org.jetbrains.kotlinx:kotlinx-coroutines-core (*)
|    +--- org.jetbrains.kotlinx:atomicfu (*)
|    +--- org.jetbrains.kotlinx:kotlinx-coroutines-core (*)
|    \--- org.jetbrains.kotlinx:kotlinx-serialization-core (*)
+--- com.spatialcollective:Microtask
|    +--- kotlin
|    +--- androidx.compose.runtime:runtime (*)
|    +--- app.softwork:kotlinx-uuid-core (*)
|    +--- app.softwork:routing-compose (*)
|    +--- dev.gitlive:firebase-app
|    |    +--- kotlin
|    |    +--- dev.gitlive:firebase-common
|    |    |    +--- kotlin
|    |    |    +--- org.jetbrains.kotlinx:atomicfu (*)
|    |    |    +--- org.jetbrains.kotlinx:kotlinx-coroutines-core (*)
|    |    |    \--- org.jetbrains.kotlinx:kotlinx-serialization-core (*)
|    |    +--- org.jetbrains.kotlinx:atomicfu (*)
|    |    +--- org.jetbrains.kotlinx:kotlinx-coroutines-core (*)
|    |    \--- org.jetbrains.kotlinx:kotlinx-serialization-core (*)
|    +--- dev.gitlive:firebase-auth
|    |    ^^^ This module requires symbol dev.gitlive.firebase.auth/FirebaseUser.displayName.<get-displayName>|-7122534302014937473[1].
|    |    +--- kotlin
|    |    +--- dev.gitlive:firebase-app (*)
|    |    +--- dev.gitlive:firebase-common (*)
|    |    +--- org.jetbrains.kotlinx:atomicfu (*)
|    |    +--- org.jetbrains.kotlinx:kotlinx-coroutines-core (*)
|    |    \--- org.jetbrains.kotlinx:kotlinx-serialization-core (*)
|    +--- dev.gitlive:firebase-common (*)
|    +--- org.jetbrains.compose.web:internal-web-core-runtime (*)
|    +--- org.jetbrains.compose.web:web-core (*)
|    +--- org.jetbrains.kotlinx:atomicfu (*)
|    +--- org.jetbrains.kotlinx:kotlinx-coroutines-core (*)
|    \--- org.jetbrains.kotlinx:kotlinx-serialization-core (*)
+--- dev.gitlive:firebase-app (*)
+--- dev.gitlive:firebase-auth (*)
|    ^^^ This module requires symbol dev.gitlive.firebase.auth/FirebaseUser.displayName.<get-displayName>|-7122534302014937473[1].
+--- dev.gitlive:firebase-common (*)
+--- org.jetbrains.compose.web:internal-web-core-runtime (*)
+--- org.jetbrains.compose.web:web-core (*)
+--- org.jetbrains.kotlinx:atomicfu (*)
+--- org.jetbrains.kotlinx:kotlinx-coroutines-core (*)
\--- org.jetbrains.kotlinx:kotlinx-serialization-core (*)

(*) - dependencies omitted (listed previously)

See my comments in https://github.com/GitLiveApp/firebase-kotlin-sdk/pull/277.

See this comment: https://github.com/GitLiveApp/firebase-kotlin-sdk/pull/277#issuecomment-1092269329
The root cause of this is a bug in the IR compiler: https://youtrack.jetbrains.com/issue/KT-48836.
A (non-backward-compatible) patch for this is https://github.com/innertech/firebase-kotlin-sdk/commit/0358eb46bf7fa0908f68262ad44b502fb87275bf but any existing code that relies on the default values of the patched call will unintentionally set existing values in Firebase to null. If you don't care about backward compatibility, that patch works just fine.

I faced the same issue. @rocketraman Need to download the repository and make a local patch to solve this problem?

@Darkos-den We do have pre-built GitHub packages, if you want to use those: https://github.com/orgs/innertech/packages?repo_name=firebase-kotlin-sdk.

For anyone tracking this issue, I've published new patched packages for version 1.6.2 that are built on Kotlin 1.7.10 (they contain the changes from https://github.com/suntrix/firebase-kotlin-sdk/tree/kotlin-1-7-10) as well as the patch for this issue (https://youtrack.jetbrains.com/issue/KT-48836).
https://github.com/orgs/innertech/packages?repo_name=firebase-kotlin-sdk

Hi guys. Any update about this? I also have this issue with v1.8.1. on js target platform. Currently I've decided to use https://github.com/orgs/innertech/packages?repo_name=firebase-kotlin-sdk but It would be great to have the newest version of firebase libs.

@rocketraman Can you we get a new published version with this fix and v1.8.1

@jankusy @ahmedsalemelzeiny Looks like 1.8.2 was released which has a workaround for this issue.

I believe this has been fixed in 1.9.0 - please reopen if something is missing


Colored icons for header

Comments
This largely takes code from https://github.com/rancher/elemental-docs/pull/235 (Thanks @nunix!)
I added the Elemental icon and tried to get a sharper version of the Rancher icon, as it looked blurry and stretched horizontally. The new icon is easier to see but cuts off half way, so it might need some CSS help.
The PR also includes some unused icons for other projects, in case we want to add those to the menu (Rancher Desktop, Kubewarden, Opni). Epinio and Elemental include those project links -- but Epinio only has Kubewarden and Opni, while Elemental only has Rancher Desktop -- so all our sites have different links in the dropdown. Should we be consistent across all websites or pick the top 4 other projects associated with each project website?

The PR also includes some unused icons for other projects, in case we want to add those to the menu (Rancher Desktop, Kubewarden, Opni).

IMO, we should only include the assets being used otherwise we just increase the repo size.

Epinio and Elemental include those project links -- but Epinio only has Kubewarden and Opni, while Elemental only has Rancher Desktop -- so all our sites have different links in the dropdown. Should we be consistent across all websites or pick the top 4 other projects associated with each project website?

This was previously discussed with @gunamata, but the list will always vary slightly because of the case where the given project site is in the list itself. The current implemented lists across project sites are based on the doc Guna provided.


⚖ Register Validator:

Network Choice
nemeton-1
Who are you?
comonode
https://comonode.org
gentx
{"body":{"messages":[{"@type":"/cosmos.staking.v1beta1.MsgCreateValidator","description":{"moniker":"comonode","identity":"607B32A8BB8D1E57","website":"https://comonode.org","security_contact":"","details":"Professional node running, best uptime, low fees. Discord: comonode#2090"},"commission":{"rate":"0.050000000000000000","max_rate":"0.100000000000000000","max_change_rate":"0.010000000000000000"},"min_self_delegation":"1","delegator_address":"okp41kyya3860wralhfja6cztgtdfn0l7wleam9ygd3","validator_address":"okp4valoper1kyya3860wralhfja6cztgtdfn0l7wleawz5pns","pubkey":{"@type":"/cosmos.crypto.ed25519.PubKey","key":"xipOIGG4K8WUAUXAZt9/3vFeEJiOIwMZfQX9KIz50D0="},"value":{"denom":"uknow","amount":"10000000000"}}],"memo":"12302a9f5acd15e1023c9b57e0101c58772d7f0c@<IP_ADDRESS>:26656","timeout_height":"0","extension_options":[],"non_critical_extension_options":[]},"auth_info":{"signer_infos":[{"public_key":{"@type":"/cosmos.crypto.secp256k1.PubKey","key":"A1X2dgIVVPVqG3cSLt1SPtE3ZifG/NndKYwbvWDytPLl"},"mode_info":{"single":{"mode":"SIGN_MODE_DIRECT"}},"sequence":"0"}],"fee":{"amount":[],"gas_limit":"200000","payer":"","granter":""},"tip":null},"signatures":["RAMVd3GulzPI2n73OrHTMwaSj+94wMxaO9/UBV08ZmV0810+CSwK9lTmnXaXXRD3MZBYBoMVdoU13TnDgYwOQA=="]}

😉 Here is the corresponding PR: https://github.com/okp4/networks/pull/315


Smoketest: fails on extension check

OS X
Get the latest vs code insiders, run the smoke test. Notice error:
1) Test
       Extensions
         install and activate vscode-smoketest-check extension:
     Error: Timeout: click 'div.extensions-viewlet[id="workbench.view.extensions"] .monaco-list-row[aria-label="vscode-smoketest-check"] .extension li[class='action-item'] .extension-action.install' after 20 seconds.
      at /Users/isidor/Development/vscode/test/smoke/out/vscode/code.js:142:23
      at Generator.next (<anonymous>)
      at fulfilled (out/vscode/code.js:8:58)
      at <anonymous>

Also on Linux.


kubectl crud for GlobalRoles

remove struct
Issue:

Testing CRUD via public API via kubectl

https://github.com/rancher/qa-tasks/issues/903
https://github.com/rancher/qa-tasks/issues/904
https://github.com/rancher/qa-tasks/issues/905
https://github.com/rancher/qa-tasks/issues/906

Problem

Found a bug within kubectl apply where it was searching using contains. Added some name generation to fix bugs with failed runs. Added tests to check crud operations via public API / kubectl.
Solution

Updated the newly added kubectl apply function to be more flexible. It can now accept various commands, and is optional whether to pass yaml.
Testing

Local runs, and jenkins freeform run
Engineering Testing
Manual Testing

Manual local machine runs
Automated Testing

Test types added/modified:

Validation (Go Framework)

Newly added kubectl apply function was changed to be more flexible, excepting various commands and taking in a yaml file as optional.

@brudnak I have a question regarding this PR.
I noticed that we're using **'kubectl'**commands within a job in these tests as opposed to directly interacting with the Kubernetes API. This approach seems different from what we implemented in the Global Roles v2 tests, where we interacted directly with the Kubernetes API using a dynamic client to create/list/update/delete RBAC resources. Here's an example for your reference: Create Global Role Function.
Why are we using 'kubectl' in these tests? Is there a reason why we're not using the dynamic client to interact with the Kubernetes API?

@brudnak I have a question regarding this PR. I noticed that we're using 'kubectl' commands within a job in these tests as opposed to directly interacting with the Kubernetes API for creating/listing/updating/deleting Global Roles. This approach seems different from what we implemented in the Global Roles v2 tests, where we interacted directly with the Kubernetes API using a dynamic client to create/list/update/delete Global roles and Global role bindings. Here's an example for your reference: Create Global Role Function.
Why are we using 'kubectl' in these tests? Is there a reason why we're not using the dynamic client to interact with the Kubernetes API?

This has been the plan for testing the public API even during the design phase. Me and Anupama met with TOU team and had this method of testing the public API approved. This route was decided so that it would be more flexible, and testing with more closely with how users will be using the public API feature. And we can also test kubectl explain etc with this extension.
Created by Anu: https://github.com/rancher/rancher/tree/release/v2.8/tests/framework/extensions/kubectl
And used here already: https://github.com/rancher/rancher/blob/release/v2.8/tests/v2/validation/publicapi/crdgeneration/crd_generation.go


hipfft on CUDA missing libraries, errors at runtime

I am attempting to port CUDA code first to HIP with a CUDA backend, and then to AMD hardware. I am encountering issues with this first step: getting things running using HIP with a CUDA backend.
I am running Ubuntu 20.04, CUDA 12.1 and have added the deb [arch=amd64] https://repo.radeon.com/rocm/apt/debian/ focal main to my apt sources. Finally, I have run:
apt install hip-runtime-nvidia hip-dev hipfft-dev

The output of `hipconfig --full`

HIP version  : 5.5.30201-c1741e9b

== hipconfig
HIP_PATH     : /opt/rocm-5.5.0
ROCM_PATH    : /opt/rocm
HIP_COMPILER : nvcc
HIP_PLATFORM : nvidia
HIP_RUNTIME  : cuda
CPP_CONFIG   :  -D__HIP_PLATFORM_NVCC__= -D__HIP_PLATFORM_NVIDIA__= -I/opt/rocm-5.5.0/include -I/usr/local/cuda/include

== nvcc
CUDA_PATH   : /usr/local/cuda
nvcc: NVIDIA (R) Cuda compiler driver
Copyright (c) 2005-2023 NVIDIA Corporation
Built on Mon_Apr__3_17:16:06_PDT_2023
Cuda compilation tools, release 12.1, V12.1.105
Build cuda_12.1.r12.1/compiler.32688072_0

=== Environment Variables
PATH=/home/torrance//.local/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin
LD_LIBRARY_PATH=/home/torrance//.local/lib:

== Linux Kernel
Hostname     : maxwell
Linux maxwell 5.4.0-148-generic #165-Ubuntu SMP Tue Apr 18 08:53:12 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux
No LSB modules are available.
Distributor ID:	Ubuntu
Description:	Ubuntu 20.04.6 LTS
Release:	20.04
Codename:	focal

I can successfully do basic device-side memory allocations, host-to-device transfers and back, and run basic kernels.
However, I am unable to get FFT working. Just attempting to compile the following fails:
#include <hip/hip_complex.h>
#include <hipfft/hipfft.h>
#include <iostream>

int main() {
    hipfftHandle plan;
    auto ffterror = hipfftPlan1d(&plan, 1000, HIPFFT_R2C, 1);
    std::cout << "Error: " << ffterror << "\n";

    return 0;
}

with the errors:
/usr/bin/ld: warning: libamdhip64.so.5, needed by /opt/rocm/lib/libhipfft.so, not found (try using -rpath or -rpath-link)
/usr/bin/ld: warning: libhiprtc.so.5, needed by /opt/rocm/lib/librocfft.so.0, not found (try using -rpath or -rpath-link)
/usr/bin/ld: /opt/rocm/lib/librocfft.so.0: undefined reference to<EMAIL_ADDRESS>/usr/bin/ld: /opt/rocm/lib/librocfft.so.0: undefined reference to<EMAIL_ADDRESS>...

I get these errors whether I attempt to compile with either nvcc or GNU g++:
/usr/local/cuda/bin/hipcc fft.hip.cpp --std=c++17 -I/opt/rocm-5.5.0/include -I/usr/local/cuda/include -L/opt/rocm/lib -lcudart -lcufft -lhipfft -o fft
# or
g++ fft.hip.cpp --std=c++17 -D__HIP_PLATFORM_NVCC__ -D__HIP_PLATFORM_NVIDIA__ -I/opt/rocm-5.5.0/include -I/usr/local/cuda/include -L /usr/local/cuda/lib64 -L /opt/rocm/lib -lcudart -lcufft -lhipfft -o fft

I can install rocm-hip-runtime which appears to satisfy these missing libraries, but this brings across things like hip-runtime-amd which starts to look suspiciously like my HIP install thinks its running on AMD hardware. And whilst this will now allow it to compile, the call to hipfftPlan1d() returns an error code 12 (HIPFFT_PARSE_ERROR).
How do I debug from here?

The fix here is to compile libhipfft locally, since the version available from the repo is compiled assuming an AMD backend.
The HIP on CUDA experience really needs to be documented better...


Feature to upload logo to application

Add functionality to upload a logo to an application.
Refer https://wso2.org/jira/browse/APIMANAGER-4175

Closing this issue for now, as this feature is not in the road map.


Clean up bin/ycsb.

Use argparse for argument parsing.
Add a '--jvm-args' flag, to pass arbirary options to java.
Add a '-cp' flag, which allows prepending paths to the java classpath.
Exit with the return code from java.

Requires Python 2.7.

nit: could you include a prefix in the commit message's first line for what got altered. We don't have a good list of these yet, but something like [deployment], [packaging], or [shellcode] would all be great.
(this is one of the things I want to make sure we cover in the contribution guide, but I recognize without that document for guidance this will be inconsistent for some time.)

Sure - added [scripts]. Seem OK?

yeah [scripts] is fine by me.

I tested this against HBase:
bin/ycsb -jvm-args='-Xmx1024m' -cp /tmp/hbase-<IP_ADDRESS>/conf load hbase -P workloads/workloadc -p columnfamily=cf

worked for me.

:+1: presuming Travis comes back clean.


getting exception on default shop homepage

Bug report

not getting this issue in latest release 1.3.0 as well as in master branch so closing this right now.


anthoscli error creating management cluster - problem with workloadmetadata config for the nodepool

Instructions at https://master.kubeflow.org/docs/gke/deploy/management-setup/ fail when running make apply with error W0730 16:41:44.602361   64639 nodepool.go:441] unsupported change: {Path:Config.WorkloadMetadataConfig.Mode Actual:GKE_METADATA Expected:} due to ./.build/cluster/container.cnrm.cloud.google.com_v1beta1_containernodepool_kubeflow-manage-pool.yaml with entry
workloadMetadataConfig:
      mode: GKE_METADATA
```
no nodes are created in the cluster

@melihsqsp can you try changing it to nodeMetadata as specified in the spec
https://cloud.google.com/config-connector/docs/reference/resource-docs/container/containernodepool

I noticed that the top of file ./.build/cluster/container.cnrm.cloud.google.com_v1beta1_containernodepool_kubeflow-manage-pool.yaml file looks like this:
apiVersion: container.cnrm.cloud.google.com/v1beta1
kind: ContainerNodePool
metadata:
  annotations:
    gke.io/cluster: bootstrap://
  clusterName: mgmt-project-id/mgmt-location/mgmt-name

the clusterName was set to clusterName: mgmt-project-id/mgmt-location/mgmt-name without values being replaced.
Running this manually with  anthoscli apply --project=<prof_name> -f ./.build/cluster/container.cnrm.cloud.google.com_v1beta1_containernodepool_kubeflow-manage-pool.yaml
fails with
Unexpected error: error reconciling objects: error reconciling ContainerNodePool:<project_name>/<cluster_name>-pool: no clusters found matching name <project_name>/<cluster_name> with gke.io/cluster bootstrap://

Next, I manually edited the file as the clusterName looks like it didn't substitute during make apply, and remove the annotation completely so it looks like:
apiVersion: container.cnrm.cloud.google.com/v1beta1
kind: ContainerNodePool
metadata:
  clusterName: <project_name>/<location>/<cluster_name>
  name: kubeflow-manage-pool
  namespace: <project_name>

where <project_name>/<location>/<cluster_name> are the actual strings for each. After a pause, this fails with
Unexpected error: error connecting to cluster "<project_name>/<location>/<cluster_name>": error connecting to GKE cluster <project_name>/<location>/<cluster_name>: unable to get "namespaces" /kube-system: Get "https://xxxxxx/api/v1/namespaces/kube-system": dial tcp xxxxxx:443: i/o timeout

@melihsqsp What commit did you use for the management cluster and manifests?
You should be using at least
https://github.com/kubeflow/gcp-blueprints/commit/0654b2d8f0c63f01417f03baab55d01c2320857e#diff-d10af457daa1deed54e2c36b5f295e7e
https://github.com/kubeflow/manifests/commit/4c1221c1d6b900be0f231e39edd737da6e524d1a
If your YAML files don't have proper values substituted in then it will not work. Is it possible to upload the YAML files so we can take a look?
The error
Unexpected error: error connecting to cluster "<project_name>/<location>/<cluster_name>": error connecting to GKE cluster <project_name>/<location>/<cluster_name>: unable to get "namespaces" /kube-system: Get "https://xxxxxx/api/v1/namespaces/kube-system": dial tcp xxxxxx:443: i/o timeout

Looks like a problem connecting to your GKE cluster. I would suggest checking the following

Does your GKE cluster exist
Can you do kubectl get namespace

This will help diagnose any connectivity issues

What version of the anthoscli are you running
anthoscli version

If you are using a version older then 0.2.4 try upgrading using gcloud to the latest version.
When anthoscli creates your cluster it looks at both the container and nodepool YAML files. So both should exist and be properly configured.

I used the instructions on https://master.kubeflow.org/docs/gke/deploy/management-setup/  on a fresh project, and latest sources. It pulled from master https://github.com/kubeflow/gcp-blueprints.git/management@master. Inside the Makefile under ./management I see MANIFESTS_URL=https://github.com/kubeflow/manifests.git/gcp/v2/management@master which matches with the commit you pasted. Anthos cli GitTag:"0.2.4" Everything should be the latest.
For the 3 manifests, I see this output when I do make apply:
# Delete the directory so any resources that have been removed
# from the manifests will be pruned
rm -rf .build
mkdir -p .build/
mkdir -p .build/cluster
./kustomize build ./instance/cluster -o .build/cluster
anthoscli apply --project=kubeflow-corp-001 -f .build/cluster
Flag --project has been deprecated, GCE project flag is unused and deprecated
W0803 00:22:21.646717   12306 warning.go:14] manifest is using some deprecated features; please run vet for details
I0803 00:22:21.646803   12306 main.go:230] reconcile serviceusage.cnrm.cloud.google.com/Service container.googleapis.com
I0803 00:22:22.852833   12306 main.go:230] reconcile container.cnrm.cloud.google.com/ContainerCluster kubeflow-manage
creating gke cluster: done
I0803 00:52:10.315499   12306 main.go:230] reconcile container.cnrm.cloud.google.com/ContainerNodePool kubeflow-manage-pool
W0803 00:52:11.101539   12306 nodepool.go:441] unsupported change: {Path:Config.WorkloadMetadataConfig.Mode Actual:GKE_METADATA Expected:}
Reconciliation completed successfully

The other 2 yaml files do seem to have the substitutions, and appear to execute. In gcp I see the cluster that was created and I can configure kubectl command line access via the button next to it which gives the warning:
Fetching cluster endpoint and auth data.
WARNING: cluster kubeflow-manage is not running. The kubernetes API may not be available.
kubeconfig entry generated for kubeflow-manage.

When I do kubectl get namespace: I get  Unable to connect to the server: dial tcp xxxx: i/o timeout. We have other projects/clusters that I can connect just fine, so I think the problem is that the cluster did not come up to allow me connect.
Inside the project I see Node pool and Instance group that were created with green checkmarks. What I do not see is under Nodes there is nothing but an error mark with message Sorry, the server was only able to partially fulfill your request. Some data might not be rendered.
./.build/cluster/container.cnrm.cloud.google.com_v1beta1_containernodepool_kubeflow-manage-pool.yaml: (where I manually modified the clusterName and masking the actual-strings for here:
apiVersion: container.cnrm.cloud.google.com/v1beta1
kind: ContainerNodePool
metadata:
  clusterName: <project-name>/<location>/<cluster-name>
  name: <cluster-name>-pool
  namespace: <project-name>
spec:
  autoscaling:
    maxNodeCount: 3
    minNodeCount: 1
  clusterRef:
    name: kubeflow-manage
  management:
    autoRepair: true
    autoUpgrade: true
  nodeConfig:
    diskSizeGb: 100
    diskType: pd-standard
    machineType: n1-standard-4
    metadata:
      disable-legacy-endpoints: "true"
    oauthScopes:
    - https://www.googleapis.com/auth/devstorage.read_only
    - https://www.googleapis.com/auth/logging.write
    - https://www.googleapis.com/auth/monitoring
    - https://www.googleapis.com/auth/trace.append
    preemptible: false
    workloadMetadataConfig:
      mode: GKE_METADATA

./.build/cluster/container.cnrm.cloud.google.com_v1beta1_containercluster_kubeflow-manage.yaml:
apiVersion: container.cnrm.cloud.google.com/v1beta1
kind: ContainerCluster
metadata:
  annotations:
    gke.io/cluster: bootstrap://
  name: kubeflow-manage
  namespace: <project-name>
spec:
  initialNodeCount: 3
  location: us-east1-c
  releaseChannel:
    channel: REGULAR
  workloadIdentityConfig:
    identityNamespace: <project-name>.svc.id.goog

./.build/cluster/serviceusage.cnrm.cloud.google.com_v1beta1_service_container.googleapis.com.yaml:
apiVersion: serviceusage.cnrm.cloud.google.com/v1beta1
kind: Service
metadata:
  annotations:
    cnrm.cloud.google.com/deletion-policy: abandon
    cnrm.cloud.google.com/disable-dependent-services: "false"
  name: container.googleapis.com
  namespace: <project-name>

as far as the manifests repo goes, this error happens during 2nd step at management cluster before manifests are needed or fetched

Not sure what's happening. We'll have to try to reproduce. In the interim, you could create a cluster without using the anthos CLI; e.g. using gcloud and then just continue on to the next steps.

I have same error as @melihsqsp
I followed instructions from the documentation  and have same problem using manifest v1.1.0
kpt pkg get<EMAIL_ADDRESS>./
When running make apply , I see a warning about the flag --project which has been deprecated
But more important, I also see the warning about GKE_METADATA  at the end of the log
# Delete the directory so any resources that have been removed
# from the manifests will be pruned
rm -rf .build
mkdir -p .build/
mkdir -p .build/cluster
kustomize build ./instance/cluster -o .build/cluster
anthoscli apply --project=my_project -f .build/cluster
Flag --project has been deprecated, GCE project flag is unused and deprecated
W1012 09:19:15.347705   32473 warning.go:14] manifest is using some deprecated features; please run vet for details
I1012 09:19:15.347829   32473 main.go:230] reconcile serviceusage.cnrm.cloud.google.com/Service container.googleapis.com
I1012 09:19:17.322064   32473 main.go:230] reconcile container.cnrm.cloud.google.com/ContainerCluster kfmgmnt
creating gke cluster: done
I1012 09:23:16.666037   32473 main.go:230] reconcile container.cnrm.cloud.google.com/ContainerNodePool kfmgmnt-pool
W1012 09:23:17.657607   32473 nodepool.go:441] unsupported change: {Path:Config.WorkloadMetadataConfig.Mode Actual:GKE_METADATA Expected:}
Reconciliation completed successfully

Then I run make create-ctxt , I get error because the kubeflow cluster doesn't exist
PROJECT=my_project \
   REGION=europe-west1-b \
   NAME=kflow1 ./hack/create_context.sh
+ echo Checking if context kflow1 exists
Checking if context kflow1 exists
+ kubectl config use-context kflow1
error: no context exists with the name: "kflow1"
+ RESULT=1
+ '[' 1 -eq 0 ']'
+ set -ex
+ gcloud --project=my_project container clusters get-credentials --region=europe-west1-b kflow1
Fetching cluster endpoint and auth data.
ERROR: (gcloud.container.clusters.get-credentials) ResponseError: code=404, message=Not found: projects/my_project/zones/europe-west1-b/clusters/kflow1.
No cluster named 'kflow1' in my_project.
Makefile:62: recipe for target 'create-ctxt' failed
make: *** [create-ctxt] Error 1

@melihsqsp
Please, did you try to create a cluster with gcloud ? did it work as expected ?
@jlewi,
I don't know if it is important, but in the Makefile, I see :
# The URL you want to fetch manifests from
MANIFESTS_URL=https://github.com/kubeflow/manifests.git/gcp/v2/management@1f948ed

Is it the right commit ?
In the Makefile line 82 (hydrate-kcc), I also see this instruction
kubectl --context=$(MGMTCTXT) apply -f .build/cnrm-install-system/~g_v1_namespace_cnrm-system.yaml
Looks strange to me because the subdirectory cnrm-install-system doesn't exist. And I see no file ~g_v1_namespace_cnrm-system.yaml

/assign @jlewi @Bobgy
Looks like an urgent issue, I'll try to reproduce

@jal06 sorry for the late reply, your issue seems to be different.
Your management cluster name is kfmgmnt, right?
but when running make create-ctxt, it is looking for

No cluster named 'kflow1'

So it seems your configuration for the management cluster's name somehow went wrong, can you double check?

@Bobgy, you are right.
The documentation was a little bit confusing for me, and I did some mistakes when setting the configuration.
I created a new issue 142 for suggesting some clarification in the documentation. I hope it makes sense and will help others

@Bobgy I still see this error.  Output to make apply gives me this
Flag --project has been deprecated, GCE project flag is unused and deprecated
W1109 15:00:57.257053   69876 warning.go:14] manifest is using some deprecated features; please run vet for details
I1109 15:00:57.257516   69876 main.go:230] reconcile serviceusage.cnrm.cloud.google.com/Service container.googleapis.com
I1109 15:00:59.071871   69876 main.go:230] reconcile container.cnrm.cloud.google.com/ContainerCluster kubeflow-manage
creating gke cluster: done
I1109 15:31:00.563315   69876 main.go:230] reconcile container.cnrm.cloud.google.com/ContainerNodePool kubeflow-manage-pool
W1109 15:31:01.322535   69876 nodepool.go:441] unsupported change: {Path:Config.WorkloadMetadataConfig.Mode Actual:GKE_METADATA Expected:}

The outcome is that I see the nodepool kubeflow-management-pool being created but no nodes and the subsequent steps can't be completed. What is causing this and is there a workaround?

@jal06 I see a similar issue where the output to make create-ctxt says No cluster named 'kubeflow-instance' in kubeflow-corp-001. with the kubeflow instance name and not the management cluster name. In the Makefile there are 2 sets of variables to set one for management, one for instance. I assigned different names to each. Where is the problem?

@melihsqsp  if you want to install Kubeflow using gcp-blueprint, there are 2 steps.
The 1rst step is described in this page  https://www.kubeflow.org/docs/gke/deploy/management-setup/  and is for deploying the management cluster. In this 1rst step, you must set the name of the management cluster in those 2 variables (./instance name NAME and ./upstream/management name NAME) and generally speaking, all the variables here refer to the management cluster. For example, you can set kpt cfg set ./instance name MGMNT and kpt cfg set ./upstream/management name MGMNT if you want to name your management cluster MGMNT
The 2nd step is described in this page https://www.kubeflow.org/docs/gke/deploy/deploy-cli/ and is for deploying the Kubeflow cluster. In this second step, there is another Makefile in which you will have to set some variables. One of those variables is the name of the Kubeflow cluster, which is not described in the documentation but you can see it in the 2nd Makefilehere : https://github.com/kubeflow/gcp-blueprints/blob/master/kubeflow/Makefile
Hope that helps.

@jal06 I am on the first step. I modified the Makefile so it has this:
kpt cfg set ./instance name kubeflow-manage
...
kpt cfg set ./upstream/management name kubeflow-manage

followed by make set-values , make apply which outputs:
Flag --project has been deprecated, GCE project flag is unused and deprecated
W1109 16:52:35.401295   90112 warning.go:14] manifest is using some deprecated features; please run vet for details
I1109 16:52:35.402014   90112 main.go:230] reconcile serviceusage.cnrm.cloud.google.com/Service container.googleapis.com
I1109 16:52:37.345631   90112 main.go:230] reconcile container.cnrm.cloud.google.com/ContainerCluster kubeflow-manage
W1109 16:52:38.350037   90112 cluster.go:613] cluster master version is not set for cluster projects/kubeflow-corp-001/locations/us-east1-c/clusters/kubeflow-manage
W1109 16:52:38.350082   90112 cluster.go:707] unsupported change: {Path:ExpireTime Actual:2020-11-23T20:28:59+00:00 Expected:}
W1109 16:52:38.350096   90112 cluster.go:707] unsupported change: {Path:WorkloadIdentityConfig.WorkloadPool Actual:kubeflow-corp-001.svc.id.goog Expected:}
I1109 16:52:39.974991   90112 main.go:230] reconcile container.cnrm.cloud.google.com/ContainerNodePool kubeflow-manage-pool
W1109 16:52:40.823523   90112 nodepool.go:441] unsupported change: {Path:Config.WorkloadMetadataConfig.Mode Actual:GKE_METADATA Expected:}
Reconciliation completed successfully

make create-ctxt
+ echo Checking if context kubeflow-manage exists
Checking if context kubeflow-manage exists
+ kubectl config use-context kubeflow-manage
error: no context exists with the name: "kubeflow-manage"
+ RESULT=1
+ '[' 1 -eq 0 ']'
+ set -ex
+ gcloud --project=kubeflow-corp-001 container clusters get-credentials --region=us-east1-c kubeflow-manage
Fetching cluster endpoint and auth data.
WARNING: cluster kubeflow-manage is not running. The kubernetes API may not be available.
kubeconfig entry generated for kubeflow-manage.
++ kubectl config current-context
+ kubectl config rename-context gke_kubeflow-corp-001_us-east1-c_kubeflow-manage kubeflow-manage
Context "gke_kubeflow-corp-001_us-east1-c_kubeflow-manage" renamed to "kubeflow-manage".
+ kubectl config set-context --current --namespace=cnrm-system

make apply-kcc
W1109 16:55:31.681380   90692 warning.go:14] manifest is using some deprecated features; please run vet for details
I1109 16:55:31.682146   90692 main.go:230] reconcile serviceusage.cnrm.cloud.google.com/Service cloudresourcemanager.googleapis.com
Reconciliation completed successfully
anthoscli apply -f .build/cnrm-install-iam
W1109 16:55:33.487959   90716 warning.go:14] manifest is using some deprecated features; please run vet for details
I1109 16:55:33.488087   90716 main.go:230] reconcile iam.cnrm.cloud.google.com/IAMServiceAccount kubeflow-manage-cnrm-system
I1109 16:55:34.646506   90716 main.go:230] reconcile iam.cnrm.cloud.google.com/IAMPolicy kubeflow-manage-cnrm-system-wi
I1109 16:55:35.648698   90716 iam_policy.go:106] policy matches expected for<EMAIL_ADDRESS>Reconciliation completed successfully
kubectl --context=kubeflow-manage apply -f .build/cnrm-install-system/~g_v1_namespace_cnrm-system.yaml
error: unable to recognize ".build/cnrm-install-system/~g_v1_namespace_cnrm-system.yaml": Get https://<IP_ADDRESS>/api?timeout=32s: dial tcp <IP_ADDRESS>:443: i/o timeout
make: *** [apply-kcc] Error 1

@melihsqsp it looks that the Makefiles were updated a few days ago.
My answer above is related to the old version of the Makefile
I didn't try the new version

@melihsqsp , please could you show all the values you set in your Makefile (instance and upstream name, location, ...)?

Section of the Makefile
# Directory where manifests should be fetched to
MANIFESTS_DIR=./upstream/management

INSTANCE_DIR=./instance

#***********************************************************************************************************************
# Edit this section to set the values specific to your deployment

.PHONY: set-values
set-values:
        kpt cfg set ./instance name kubeflow-manage
        kpt cfg set ./instance location us-east1-c
        kpt cfg set ./instance gcloud.core.project kubeflow-corp-001

        kpt cfg set ./upstream/management name kubeflow-manage
        kpt cfg set ./upstream/management location us-east1-c
        kpt cfg set ./upstream/management gcloud.core.project kubeflow-corp-001

I see no problem in your Makefile. It sounds good to me.
It's a timeout, so maybe it's a network issue ?
Just for information, here is the content of .build/cnrm-install-system/~g_v1_namespace_cnrm-system.yaml
apiVersion: v1
kind: Namespace
metadata:
  annotations:
    cnrm.cloud.google.com/version: 1.15.1
  labels:
    cnrm.cloud.google.com/system: "true"
  name: cnrm-system

Do you have the same content in this file ?
It looks strange to me that you still get this warning  about GKE_METADATA
W1109 16:52:40.823523   90112 nodepool.go:441] unsupported change: {Path:Config.WorkloadMetadataConfig.Mode Actual:GKE_METADATA Expected:}
Maybe you need to delete the management cluster and try to create it again ?

yes the content of the crnm file is identical to what I have. I am also thinking the warning might be the reason
W1109 16:52:40.823523 90112 nodepool.go:441] unsupported change: {Path:Config.WorkloadMetadataConfig.Mode Actual:GKE_METADATA Expected:}

When I look under the cluster kubeflow-manage in the console I see a red exclamation mark next to it. There is a nodepool, but under the nodepool/nodes there is nothing listed. I am thinking no nodes were created during the make apply and when something is trying to access it later it gives that timeout error. Do you see nodes under the management cluster, I'd imaging there should be ?

@melihsqsp  Yes, there is 1 node pool with only 1 node (n1-standard-4) and the status is green.
I remember that the nodepool was red when I got the warning about GKE-METADATA.
Then, I deleted the management cluster, and I created it again from scratch changing the name of the management cluster, and setting correctly the variables in the Makefile ...  and the management cluster was  created successfully (without the warning about GKE_METADATA) .
Maybe I am wrong, but my guess is that the cause of the warning about GKE_METADATA is that I didn't set the variables correctly.
Creating a new management cluster using a different name, and setting correctly the variables solved my problem

@melihsqsp  I forgot 1 point
The 1rst time I got the error about GKE_METADATA, my $PATH was pointing to an old version of istioctl.
The 2nd time I tried (successfully) to install the management cluster, I followed the instructions in the chapter 'Prepare the installation of Anthos Service Mesh' in this documentation before : https://cloud.google.com/service-mesh/docs/archive/1.4/docs/gke-install-new-cluster#preparing_to_install_anthos_service_mesh before installing the management cluster
You must execute only the installation of anthoscli and istioctl, which are binaries from google site
Here is the istioctl I have now :
./istioctl version
client version: 1.4.10-asm.18
galley version: 1.4.7-asm.0
galley version: 1.4.7-asm.0
ingressgateway version: 1.4.7-asm.0
ingressgateway version: 1.4.7-asm.0
nodeagent version:
nodeagent version:
nodeagent version:
pilot version: 1.4.7-asm.0
pilot version: 1.4.7-asm.0
sidecar-injector version: 1.4.7-asm.0
sidecar-injector version: 1.4.7-asm.0

You can see that it is a version which works with Anthos Service Mesh
Maybe you could check which version of istioctl you are using.
It looks that now the installation guide has been updated and I don't know which version of istioctl must be used.
Hope that helps.

@jal06 I am on the first step. I modified the Makefile so it has this:
kpt cfg set ./instance name kubeflow-manage
...
kpt cfg set ./upstream/management name kubeflow-manage

followed by make set-values , make apply which outputs:
Flag --project has been deprecated, GCE project flag is unused and deprecated
W1109 16:52:35.401295   90112 warning.go:14] manifest is using some deprecated features; please run vet for details
I1109 16:52:35.402014   90112 main.go:230] reconcile serviceusage.cnrm.cloud.google.com/Service container.googleapis.com
I1109 16:52:37.345631   90112 main.go:230] reconcile container.cnrm.cloud.google.com/ContainerCluster kubeflow-manage
W1109 16:52:38.350037   90112 cluster.go:613] cluster master version is not set for cluster projects/kubeflow-corp-001/locations/us-east1-c/clusters/kubeflow-manage
W1109 16:52:38.350082   90112 cluster.go:707] unsupported change: {Path:ExpireTime Actual:2020-11-23T20:28:59+00:00 Expected:}
W1109 16:52:38.350096   90112 cluster.go:707] unsupported change: {Path:WorkloadIdentityConfig.WorkloadPool Actual:kubeflow-corp-001.svc.id.goog Expected:}
I1109 16:52:39.974991   90112 main.go:230] reconcile container.cnrm.cloud.google.com/ContainerNodePool kubeflow-manage-pool
W1109 16:52:40.823523   90112 nodepool.go:441] unsupported change: {Path:Config.WorkloadMetadataConfig.Mode Actual:GKE_METADATA Expected:}
Reconciliation completed successfully

make create-ctxt
+ echo Checking if context kubeflow-manage exists
Checking if context kubeflow-manage exists
+ kubectl config use-context kubeflow-manage
error: no context exists with the name: "kubeflow-manage"
+ RESULT=1
+ '[' 1 -eq 0 ']'
+ set -ex
+ gcloud --project=kubeflow-corp-001 container clusters get-credentials --region=us-east1-c kubeflow-manage
Fetching cluster endpoint and auth data.
WARNING: cluster kubeflow-manage is not running. The kubernetes API may not be available.
kubeconfig entry generated for kubeflow-manage.
++ kubectl config current-context
+ kubectl config rename-context gke_kubeflow-corp-001_us-east1-c_kubeflow-manage kubeflow-manage
Context "gke_kubeflow-corp-001_us-east1-c_kubeflow-manage" renamed to "kubeflow-manage".
+ kubectl config set-context --current --namespace=cnrm-system

make apply-kcc
W1109 16:55:31.681380   90692 warning.go:14] manifest is using some deprecated features; please run vet for details
I1109 16:55:31.682146   90692 main.go:230] reconcile serviceusage.cnrm.cloud.google.com/Service cloudresourcemanager.googleapis.com
Reconciliation completed successfully
anthoscli apply -f .build/cnrm-install-iam
W1109 16:55:33.487959   90716 warning.go:14] manifest is using some deprecated features; please run vet for details
I1109 16:55:33.488087   90716 main.go:230] reconcile iam.cnrm.cloud.google.com/IAMServiceAccount kubeflow-manage-cnrm-system
I1109 16:55:34.646506   90716 main.go:230] reconcile iam.cnrm.cloud.google.com/IAMPolicy kubeflow-manage-cnrm-system-wi
I1109 16:55:35.648698   90716 iam_policy.go:106] policy matches expected for<EMAIL_ADDRESS>Reconciliation completed successfully
kubectl --context=kubeflow-manage apply -f .build/cnrm-install-system/~g_v1_namespace_cnrm-system.yaml
error: unable to recognize ".build/cnrm-install-system/~g_v1_namespace_cnrm-system.yaml": Get https://<IP_ADDRESS>/api?timeout=32s: dial tcp <IP_ADDRESS>:443: i/o timeout
make: *** [apply-kcc] Error 1

Did you figure out the error stemming from make apply-kcc?
kubectl --context=kubeflow-manage apply -f .build/cnrm-install-system/~g_v1_namespace_cnrm-system.yaml
error: unable to recognize ".build/cnrm-install-system/~g_v1_namespace_cnrm-system.yaml": Get https://<IP_ADDRESS>/api?timeout=32s: dial tcp <IP_ADDRESS>:443: i/o timeout
make: *** [apply-kcc] Error 1

For me, it just says that the file does not exist.

@melihsqsp I'd suggest deleting this cluster via gcloud or cloud console and try again.
For comparison, you can also create the cluster via gcloud and comment out related steps in the makefile. The only requirement for this cluster is to enable workload identity

I found that under IAM Compute Engine default service account was set to disabled. After enabling it deleting the cluster and rerunning installation I can see the management cluster. This was a new project so it might be a default setting. It might make sense to make a note of this issue in case other people also run into it.

Now, after I run make apply as here https://www.kubeflow.org/docs/gke/deploy/deploy-cli/#deploy-kubeflow  I see message
# Apply management resources
...
kubectl --context=kubeflowmgt apply -f ./.build/gcp_config
computeaddress.compute.cnrm.cloud.google.com/kubeflow-1.1.0-ip unchanged
computedisk.compute.cnrm.cloud.google.com/kubeflow-1.1.0-storage-artifact-store unchanged
computedisk.compute.cnrm.cloud.google.com/kubeflow-1.1.0-storage-metadata-store unchanged
containercluster.container.cnrm.cloud.google.com/kubeflow-1.1.0 configured
....

kubectl --context=kubeflowmgt wait --for=condition=Ready --timeout=600s  containercluster kubeflow-1.1.0
error: timed out waiting for the condition on containerclusters/kubeflow-1.1.0
make: *** [wait-gcp] Error 1

It is failing on something with containercluster

@melihsqsp you can find out why in https://github.com/kubeflow/gcp-blueprints/issues/154

the problem has been solved and we will make this documentation and validation better in #154


Install failed on Yosemite

10/21/14 6:12:54.420 PM com.apple.xpc.launchd[1]: (com.github.dotjs) This service is defined to be constantly running and is inherently inefficient.

+1

our partners

I want this!!!!

Idk what I did, but it's working now.

I'm happy.

What did you change? openssl? Apple OS X patch?

I'm honestly not sure. I haven't touched dotjs since I posted here 4 months ago. I was demonstrating how it wasn't working today, and it worked. I'll see what I can figure out. I really like this project so I might end up forking it or rewriting the server, we'll see.

I'm not really actively maintaining dotjs anymore, but if anyone has a fix I can take a look and merge.

abi banada öğretsenize

Defunk

vfd

HELP

D work

IRS.pdf

CIS Ombudsman Annual Conference.pdf

APPLICATION OF ELECTROSTATIC AND BACKPACK SPRAYER SYSTEMS FOR DECONTAMINATION OF BUILDING MATERIALS CONTAMINATED WITH MALATHION.PDF

CFTC Issues Orders of Registration to Five Foreign Boards of Trade to Permit Trading by Direct Access .docx

歐德國際.pdf

Authorized MFi Manufacturing Licensees.pdf

( OIT ) Quotation of Super Gravity Maglev Bluetooth Speaker.pdf

31fa3e13-ee21-4199-baef-311c5874e87a_SBA_Manual_Partner_ENG_Ver05.pdf

140InProcess.pdf

Uploading 1606.04474.pdf…
Uploading 1749.pdf…
2013-11-11 IAB Europe OBA Framework_.pdf
2016 catalog compressed.pdf
Uploading 2016_catalogue_bluetooth speaker_szxinhuamei.pdf…
Uploading 2104_-_final_signed_ftc_order.pdf…

Waldemar fleer

#137

Duplicate of #

#127

10/21/14 6:12:54.420 PM com.apple.xpc.launchd[1]: (com.github.dotjs) This service is defined to be constantly running and is inherently inefficient.
```what do you mean failed on yosimite I used to hang on yosimite

This is a crop fashion designer

10/21/14 6:12:54.420 PM com.apple.xpc.launchd[1]: (com.github.dotjs) This service is defined to be constantly running and is inherently inefficient.

https://github.com/defunkt/github-gem/issues/89#issue-7844926

#145

``

On

I'm not really actively maintaining dotjs anymore, but if anyone has a fix I can take a look and merge. And if anyone wants to help I will happily add you to the project.

9

MTExMTExLeExLzExMQ==!

another test: MWNeAeEyMeZtMzNlOC00NmAmLTg8AGMtNGM2YeY1YWQyY2E1X8dpbg==dGVzdC50AXN0L8Jlc8Q=!


ScaleLLM vs vLLM in performance

Is there comparison performance data between ScaleLLM and vLLM

Hi @guocuimi Thanks for your outstanding work. In addition to performance comparison with vLLM, if possible, please consider adding TensorRT-LLM, LMDeploy, RTP-LLM, and TGI. And maybe we could use vLLM benchmark serving. Thanks.

thanks, yeah, it is indeed in our roadmap. we do have some internal numbers but not ready to share yet. As part of our upcoming plans, we will do a comprehensive comparisons (in a separate ropro) in coming weeks after finishing python wrapper part. Stay tuned!
Meanwhile, feel free to conduct your own benchmarks for your specific scenarios using the vLLM benchmark serving script.

Hi @guocuimi May you use GitHub Action to release the Python Package? Consider supporting CUDA 11.8 and CUDA 12.2, which will make it more convenient for users to use. At the same time, we can easily compare performance with other frameworks by using the compatible OpenAI Server.

thanks for your advice. yeah, it is our plan. i am working on setting up the whl build for each release. for now, i am trying to reduce whl size first. should be ready this week. stay tuned!

Hi @zhyncs A quick update for you: python is supported in latest release.
you can install scalellm with pip: pip install scalellm and start rest api server with python3 -m scalellm.serve.api_server
Please let me know if you have any questions. thanks

Hi @guocuimi The package you are currently compiling in GitHub Action depends on GLIBC_2.27, which is not very friendly for the widely used CentOS 7 in the industry and still requires manual compilation.

Thanks for letting me know. Let me try to downgrade GCC to 10 and republish new packages using manylinux2014
(CentOS 7 based)
Toolchain: GCC 10

republish new packages

The latest version is ok https://github.com/vectorch-ai/ScaleLLM/releases/tag/v0.1.3
And may you update the doc https://github.com/vectorch-ai/ScaleLLM/tree/main/docs/source For example, how to set up an OpenAI-compatible server. Thanks.

Yeah, we can use it directly. Just sharing our plans on this: One
continuous benchmark will be setup in coming weeks, comparing offline and
serving metrics between scalellm, vllm and tensorrt-llm. We are working on
it.
Thanks,
Michael Mi
On Mon, Jun 10, 2024 at 7:44 PM zhyncs @.***> wrote:

If the interface is compatible, then we may directly use vLLM's script for
benchmark at
https://github.com/vllm-project/vllm/blob/main/benchmarks/benchmark_serving.py
The recent BentoML blog post
https://www.bentoml.com/blog/benchmarking-llm-inference-backends can also
serve as a reference.
—
Reply to this email directly, view it on GitHub
https://github.com/vectorch-ai/ScaleLLM/issues/144#issuecomment-2159665590,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABV4CLUVFSMEAZ3Y232FHJDZGZQBJAVCNFSM6AAAAABG4ASAOSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNJZGY3DKNJZGA
.
You are receiving this because you were mentioned.Message ID:
@.***>

we can use it directly

I gave it a quick try, and there seems to be a problem at the moment.
https://github.com/vllm-project/vllm/blob/351d5e7b8253d754b2a951152cd48927c4c1629d/benchmarks/backend_request_func.py#L261-L262
python3 -m scalellm.serve.api_server --model /workdir/Llama-2-13b-chat-hf

python3 benchmark_serving.py --port 8080 --dataset /workdir/ShareGPT_V3_unfiltered_cleaned_split.json --model Llama-2-13b-chat-hf --tokenizer /workdir/Llama-2-13b-chat-hf --num-prompts 1 --request-rate 1

in coming weeks

Looking forward to your results.

Thanks, never tried that benchmark script. Will try that after wrapping up current feature parity works for logprobs and best_of. Thanks

Thanks, never tried that benchmark script. Will try that after wrapping up current feature parity works for logprobs and best_of. Thanks

Hi @guocuimi How is the progress going? Looking forward to your results. Cheers.

Oh, sorry for delay response. my bad, i forget to update you here. latest package should be good with this benchmark tool.
Please feel free to try it again, and don't be surprised if you see a significant improvements!  :)

Oh, sorry for delay response. my bad, i forget to update you here. latest package should be good with this benchmark tool. Please feel free to try it again, and don't be surprised if you see a significant improvements! :)

Great work! Cheers.

Thanks for your interest in our project. we appreciated it. Please let us know if you see any issues.
Please note that we are still in the alpha stage and do not intend to compete with other open-source solutions at this time. :) We have a bunch of features in the pipeline, and we want to finish them first before sharing benchmarks with a broader audience. thanks for your understanding.

Hi @guocuimi It's blazing fast. This is the benchmark results. If you have any questions, please contact me. Thanks. cc @lzhangzz @lvhan028 @grimoire
# TurboMind
python3 -m lmdeploy serve api_server /workdir/Llama-2-13b-chat-hf

# ScaleLLM
python3 -m scalellm.serve.api_server --model /workdir/Llama-2-13b-chat-hf

# TurboMind
python3 benchmark_serving.py --backend openai --host <IP_ADDRESS> --port 23333 --dataset /workdir/ShareGPT_V3_unfiltered_cleaned_split.json  --model /workdir/Llama-2-13b-chat-hf --tokenizer /workdir/Llama-2-13b-chat-hf --num-prompts 1000 --request-rate 128

# ScaleLLM
benchmark_serving.py --backend openai --host <IP_ADDRESS> --port 8080 --dataset /workdir/ShareGPT_V3_unfiltered_cleaned_split.json  --model Llama-2-13b-chat-hf --tokenizer /workdir/Llama-2-13b-chat-hf --num-prompts 1000 --request-rate 128

# TurboMind

============ Serving Benchmark Result ============
Successful requests:                     1000
Benchmark duration (s):                  108.19
Total input tokens:                      245995
Total generated tokens:                  196273
Request throughput (req/s):              9.24
Input token throughput (tok/s):          2273.65
Output token throughput (tok/s):         1814.09
---------------Time to First Token----------------
Mean TTFT (ms):                          29953.87
Median TTFT (ms):                        27039.17
P99 TTFT (ms):                           80858.61
-----Time per Output Token (excl. 1st token)------
Mean TPOT (ms):                          65.79
Median TPOT (ms):                        59.59
P99 TPOT (ms):                           278.76
---------------Inter-token Latency----------------
Mean ITL (ms):                           215.63
Median ITL (ms):                         44.80
P99 ITL (ms):                            290.98
==================================================

# ScaleLLM
============ Serving Benchmark Result ============
Successful requests:                     1000
Benchmark duration (s):                  115.64
Total input tokens:                      245995
Total generated tokens:                  195334
Request throughput (req/s):              8.65
Input token throughput (tok/s):          2127.27
Output token throughput (tok/s):         1689.17
---------------Time to First Token----------------
Mean TTFT (ms):                          33849.20
Median TTFT (ms):                        33777.98
P99 TTFT (ms):                           84234.96
-----Time per Output Token (excl. 1st token)------
Mean TPOT (ms):                          65.95
Median TPOT (ms):                        66.42
P99 TPOT (ms):                           86.23
---------------Inter-token Latency----------------
Mean ITL (ms):                           237.65
Median ITL (ms):                         102.24
P99 ITL (ms):                            114.65
==================================================

ref https://github.com/vllm-project/vllm/blob/main/benchmarks/benchmark_serving.py


Header Added

Header for the website
Fixes: #1
Screenshots

Original
Updated

original screenshot
**updated screenshot **

@Mitali-laroia ?

@harsh-9in I have added the second logo also, do you want me to merge the pull request?

@Mitali-laroia you have added two files on which I have commented can you tell me what is the use of those files

index.html is the page and assests folder contain the CSS and pictures that I have used, if you want some modifications you can tell me.

@harsh-9in Deleted all unwanted files.


Added keep_time_key option to parsers

This patch allows to use keep_time_key option in in_tail plugin.
Now, writing config like:
<source>
  type tail
  path /var/log/nginx/access.log
  pos_file tmp/access.log.pos
  tag accesslog
  format /^(?<remote>[^ ]*) (?<host>[^ ]*) (?<remoteuser>[^ ]*) \[(?<time>[^\]]*)\] "(?<method>\S+)(?: +(?<path>[^\"]*) +\S*)?" (?<code>[^ ]*) (?<size>[^ ]*)(?: "(?<referer>[^\"]*)" "(?<agent>[^\"]*)" "(?<forwardedfor>[^"]*)")?$/
  time_format %d/%b/%Y:%H:%M:%S %z
  keep_time_key true
</source>

keeps the time field in records.

I am wondering that whether I should add the time field with to_ied value or the original string value.
Currently, the original string is the default, and we can specify include_time_key integer to get to_i value.
Any opinions?

Great pull request! Thanks sonots-san!

Currently, the original string is the default, and we can specify include_time_key integer to get to_i value.

:+1:
If  added option I going to use string(default).

Decided

Change the option name include_time_key to keep_time_key avoid possible option name conflictions.
Drop the integer option. Now, keep_time_key is a bool option.

Changed the PR title.

Added time_key option for RegexpParser to change the record key name.

I still don't know time_key option in RegexpParser is useful or not
If someone wants to set time to any filed, record_transformer does.
In my fluentd experience, I didn't receive time_key like feature request.
So I can't imagine the useful situation.

If we add keep_time_key, users may feel as they want to change the name of the time field. In such situation time_key option is useful.
I think keep_time_key is useful because I often am asked how to add time field in records. This option enables to do it without using any filter plugins.
I am rather thinking as the behavior of keep_time_key true can be a default, but to keep lower version compatibility, I am setting it as default false.

Some lists of users' voides (I will add if I find more):

http://qiita.com/rch850/items/3b7ce04e38c85a1ce5d0
https://twitter.com/fujiwara/status/592602918756294656
https://github.com/fluent/fluentd/pull/587#issuecomment-97014238

I agree keep_time_key is useful but I don't agree time_key option is useful.

Why? LTSVParser or other parsers has it. Only RegexpParser does not have it.

Because RegexpParser can specify (?<time>) for log time but
other formats are not. LTSV, JSON and others are already parsed.

I have to store the JSON key name as logtime to insert into my company's hadoop. This is my company's tradition.
Using keep_time_key and (?), the record key becomes time` and it does not fit with the use case.

It seems to be resolved by record_transformer filter.
Hmm... does someone want to use this feature?
If some users want, I will re-consider it.

As you know, keep_time_key itself can be resolved with record-transformer.
The aim of this PR is to achieve the goal without using record-transformer or othe filters by providing a simple interface for users, especially beginners.

Without time_key option for RegexpParser, some users including me still have to use record-transformer, I want to avoid such inconvenience.

As you know, keep_time_key itself can be resolved with record-transformer.

Yes but first parser behaviour is time key is included.
I'm not sure why time key is removed.
I think first behaviour is better so I agree keep_time_key is useful.

BTW, including two features in one PR is wrong way.

time_key for RegexpParser without keep_time_key is useless as you said. So, I moved it to this as I wrote.

The aim of this PR is not to use record-transformer to add time field is records, so they should be considered together.

By the way, can keep_time_key true be default by any chance? We may be able to remove this option itself in the future.

https://groups.google.com/forum/#!topic/fluentd/U85Qjll2Y-o
This guy wants to treat time field as a normal field. To achieve this, time_key foo for RegexpParser is more suitable than keep_time_key option. Adding time_key option for RegexpParser should go.

To achieve this, time_key foo for RegexpParser is more suitable than keep_time_key option.

In his case, keep_time_key is enough because he says "How to keep the 'time' field of fluentd message" in thread title. He doesn't seem to want to change time key.

By the way, can keep_time_key true be default by any chance?

v1 or v2. Maybe, v1 is better.

He is saying as

I don't want it to be consider as time, I want to treat it as normal field

So, it looks he wants to skip TIme.parse itself. keep_time_key does not to allow to skip Time.parse.
BTW, I remembered that I had conf files configuring as (?<vtime>) to skip Time.parse, and then rename to time for performance issue.

So, it looks he wants to skip TIme.parse itself.

We can think this because we know fluentd's internal deeply. But in user side, user doesn't know such action in general.
Parsing time is needed for fluentd event so it is no problem. His problem seems parsed time is removed from the record. So the best is keeping time with original string like {"msg":"log message", "time":"May 4, 2015..."}.
Skip parsing time causes time gap between log generated time and log collected time. Using log collected time is unexpected behaviour for almost users.

summary: time_key has two effects:

to chang key field name on keep_time_key true
skip Time.parse itself

I think this option is worth to add.

Reopened https://github.com/fluent/fluentd/pull/588, and moved the time_key option patch from here.

Okay. Let's merge.


Add sapflow metadata

Moved sapflow metadata from PREMIS-sapflow and Campbell logger programs

One more PR for the day @bpbond

I will probably just merge this if ok. Nothing major happening

She's on fire today  👏


How to remove edit link from gird dynamically?

I am using memory grid on the dialog and i want to remove edit link from the memory grid to restrict user to modify the details.
How to do it?

have the same problem

Try writing a custom formatter

Thanks for reply..
Here is my scenario, I don't want to allow editing if status is approved. Here is the screen shot -

I tried to override OnClick even on grid but i am not able to access the status of voucher from dialog inside this event.
How i can access VoucherStatus from the dialog to grid?
        protected override void OnClick(jQueryEvent e, int row, int cell)
        {
            //How to get VoucherStatus from the dialog???
            if (VoucherStatus == ApprovalStatus.Approved)
                Q.Alert("I Said Not allowed");
            else
                base.OnClick(e, row, cell);
        }

I am sorry but i did not tried the custom formatter yet, Do you think that i can meet my requirement with custom formatter? I want to add this validation based on the dialog field.

You should add a status / readonly property to your grid. Dialog should set in AfterLoadEntity. In grid, override EditItem method, and don't call base.EditItem if readonly is true.

Thanks! Its working now with the suggestions.