mesa 19.1.2

Created with brew bump-formula-pr.

meson deletes rpaths upon installation

meson patch has been merged upstream, so this is no longer blocked.

still need to translate those gpu/non-gpu settings to the new format.

== /home/linuxbrew/.linuxbrew/Homebrew/Library/Taps/linuxbrew/homebrew-xorg/Formula/mesa.rb ==

C: 53:  1: Trailing whitespace detected.

W:108:  7: Useless assignment to variable - args.

W:114:  7: Useless assignment to variable - args.

C:121:  1: Extra blank line detected.

C:130:  9: Missing space after #.

C:131:  9: Incorrect indentation detected (column 8 instead of 6).

==> brew test --verbose libepoxy
Testing libepoxy
==> /usr/bin/gcc test.c -lepoxy -o test
.
Last 150 lines from /home/linuxbrew/.cache/Homebrew/Logs/libepoxy/test.01.gcc:
2019-09-20 19:18:12 +0000

/usr/bin/gcc
test.c
-lepoxy
-o
test

/home/linuxbrew/.linuxbrew/lib/../lib/libepoxy.so: undefined reference to<EMAIL_ADDRESS>/home/linuxbrew/.linuxbrew/lib/../lib/libepoxy.so: undefined reference to<EMAIL_ADDRESS>/home/linuxbrew/.linuxbrew/lib/../lib/libepoxy.so: undefined reference to<EMAIL_ADDRESS>collect2: error: ld returned 1 exit status
Error: libepoxy: failed
Failed executing:
/home/linuxbrew/.linuxbrew/Homebrew/Library/Homebrew/formula.rb:1914:in `block in system'
/home/linuxbrew/.linuxbrew/Homebrew/Library/Homebrew/formula.rb:1851:in `open'
/home/linuxbrew/.linuxbrew/Homebrew/Library/Homebrew/formula.rb:1851:in `system'
/home/linuxbrew/.linuxbrew/Homebrew/Library/Taps/homebrew/homebrew-core/Formula/libepoxy.rb:65:in `block in <class:Libepoxy>'
/home/linuxbrew/.linuxbrew/Homebrew/Library/Homebrew/formula.rb:1727:in `block (3 levels) in run_test'
/home/linuxbrew/.linuxbrew/Homebrew/Library/Homebrew/utils.rb:479:in `with_env'
/home/linuxbrew/.linuxbrew/Homebrew/Library/Homebrew/formula.rb:1726:in `block (2 levels) in run_test'
/home/linuxbrew/.linuxbrew/Homebrew/Library/Homebrew/formula.rb:866:in `with_logging'
/home/linuxbrew/.linuxbrew/Homebrew/Library/Homebrew/formula.rb:1725:in `block in run_test'
/home/linuxbrew/.linuxbrew/Homebrew/Library/Homebrew/formula.rb:1964:in `block in mktemp'
/home/linuxbrew/.linuxbrew/Homebrew/Library/Homebrew/mktemp.rb:57:in `block in run'
/home/linuxbrew/.linuxbrew/Homebrew/Library/Homebrew/mktemp.rb:57:in `chdir'
/home/linuxbrew/.linuxbrew/Homebrew/Library/Homebrew/mktemp.rb:57:in `run'
/home/linuxbrew/.linuxbrew/Homebrew/Library/Homebrew/formula.rb:1963:in `mktemp'
/home/linuxbrew/.linuxbrew/Homebrew/Library/Homebrew/formula.rb:1719:in `run_test'
/home/linuxbrew/.linuxbrew/Homebrew/Library/Homebrew/test.rb:30:in `block in <main>'
/home/linuxbrew/.linuxbrew/Homebrew/Library/Homebrew/vendor/portable-ruby/2.3.7/lib/ruby/2.3.0/timeout.rb:91:in `block in timeout'
/home/linuxbrew/.linuxbrew/Homebrew/Library/Homebrew/vendor/portable-ruby/2.3.7/lib/ruby/2.3.0/timeout.rb:33:in `block in catch'
/home/linuxbrew/.linuxbrew/Homebrew/Library/Homebrew/vendor/portable-ruby/2.3.7/lib/ruby/2.3.0/timeout.rb:33:in `catch'
/home/linuxbrew/.linuxbrew/Homebrew/Library/Homebrew/vendor/portable-ruby/2.3.7/lib/ruby/2.3.0/timeout.rb:33:in `catch'
/home/linuxbrew/.linuxbrew/Homebrew/Library/Homebrew/vendor/portable-ruby/2.3.7/lib/ruby/2.3.0/timeout.rb:106:in `timeout'
/home/linuxbrew/.linuxbrew/Homebrew/Library/Homebrew/test.rb:29:in `<main>'
==> FAILED


Auto start the engine after shutdown

case Keys.NumPad0:
vehicle.EngineRunning = this.mEngineRunning = !this.mEngineRunning;
break;
The game sitting in the car press 0 and the engine switched off. But immediately turned back on. How to block it? Sorry for my English. please, help

In GTA IV you would have to set the PetrolTankHealth to 0 so that the vehicle couldn't start up.

It is working! Thank you very much! you are the best!


Fix two bugs & do a small refactoring

In this pr I address two bugs and one refactoring:

Don't persist root if the online roles bump fails. This makes sure that the root is stored last when all online roles are bumped.
Give a trusted_root_update() with a more telling name. As we don't update trusted root with _trusted_root_update() and this makes the function name misleading.
Fix: update the delegation key when bumping targets. Strangely, we forgot to change the key referenced in top level targets role when bumping targets with an online key change. This caused a bug that was reported: https://github.com/repository-service-tuf/repository-service-tuf-worker/issues/491

Fixes #491

With this pr, I think I have solved issue #491 as well.
I have made sure we persist root as the last step.
The other part - is to make sure we are persisting timestamp as the last online role is solved as well as:

We have implemented  _run_online_roles_bump() in such a way that makes sure that targets role is first updated, then we call update_snapshot which updates the delegated targets roles, then updates snapshot and finally the new snapshot version is passed to update_timestamp() where we update timestamp.
Each time when we call update_timestamp we call update_snapshot() first which updates all delegated target roles and snapshot. There is only one exception to that rule - when the user forces a new version of timestamp only:  https://github.com/repository-service-tuf/repository-service-tuf-worker/blob/63c77974a402b80f618aecb9f124a6466d61149b/repository_service_tuf_worker/repository.py#L1268, but there we don't need to update anything beforehand.

Because of these reasons, I think we do make sure the timestamp will be the last saved from the online metadata roles.
What do you think @kairoaraujo?
Do we need any tests for that and what they should be?

Because of these reasons, I think we do make sure the timestamp will be the last saved from the online metadata roles. What do you think @kairoaraujo? Do we need any tests for that and what they should be?

The overall issue #494 is solved with your implementation. I agree that the issue solves the bug #494.
The only part I think we can still improve is the recovery from a failure while saving Root. But we should do it in another issue.

Addressed your comment @kairoaraujo in my latest commit.

Amazing work @MVrachev!

Awesome!


Angular initialisation

First off, the plugin is AWESOME!
Is there an official method to initialise the library within an angular route?
All I can find is this thread, however all of the solutions don't seem to work.
Does anyone have any suggestions?

You can place your initialization code whenever you want, but I recommend you to do it just after all the libraries has been loaded
$(document).ready(function() {
    new WOW().init();
});

it still do not work

1)service Win
import {Injectable} from '@angular/core';
function _window(): any {
// return the native window obj
return window;
}
@Injectable()
export class WindowRef {
get nativeWindow(): any {
return _window();
}
}
2)call in component
constructor(private winRef: WindowRef) {
winRef.nativeWindow.WOW().init();
}


A _TypeError occurs (specifically, 'Null' is not a subtype of type TYPE) when attempting to remove the navigation history and navigate back to '/'.

Steps to reproduce
1 - Used GoRouter.of(context).pushNamed() to navigate to a page and pop all previous pages.
2 - Used context.go() to make sure to remove the navigation history.
3 - Used context.go() to navigate to "/"

Problem *
Error - _TypeError (type 'Null' is not a subtype of type 'Goal').

Expected results
Refresh the goRouter when I want to go to "/"
Actual results
Null error occurred.
Code sample
Got error in this section

GoRoute(
        path: whenGoalSaved,
        name: AppRoute.whenGoalSaved.name,
        builder: (context, state) {
          Map<String, dynamic>? data = state.extra is Map<String, dynamic>
              ? state.extra as Map<String, dynamic>
              : null;
          String id =
              data != null && data.containsKey("id") ? data["id"] : "";
          Goal goal = data != null && data.containsKey("goal")
              ? data["goal"]
              : Goal(
                  uid: "uid",
                  createdAt: 0,
                  domain: "domain",
                  startDate: 0,
                  endDate: 0,
                  role: "role",
                  goal: "goal",
                  results: "results",
                  description: "description",
                  id: "id",
                  completed: false);
          return WhenGoalSaved(
            goal: goal,
            id: id,
          );
        },
      )

Screenshots or Video

Screenshot *

Logs
═══════ Exception caught by widgets library ═══════════════════════════════════
The following _TypeError was thrown building Builder(dirty):
type 'Null' is not a subtype of type 'Goal'

The relevant error-causing widget was:
    MediaQuery MediaQuery:file:///Users/saqibshafique/Desktop/Flutter%20Projects/pink_elephants_coaching/lib/core/app.dart:141:18

When the exception was thrown, this was the stack:
#0      AppRoutes.router.<anonymous closure> (package:pink_elephants_coaching/common/routes/app_routes.dart:161:27)
app_routes.dart:161
#1      _CustomNavigatorState._buildPageForGoRoute.<anonymous closure> (package:go_router/src/builder.dart:257:21)
builder.dart:257
#2      Builder.build (package:flutter/src/widgets/basic.dart:7698:48)
basic.dart:7698
#3      StatelessElement.build (package:flutter/src/widgets/framework.dart:5550:49)
framework.dart:5550
#4      ComponentElement.performRebuild (package:flutter/src/widgets/framework.dart:5480:15)
framework.dart:5480

Flutter Doctor output
✓] Flutter (Channel stable, 3.19.6, on macOS 14.5 23F79 darwin-x64, locale
en-PK)
• Flutter version 3.19.6 on channel stable at
/Users/saqibshafique/development/flutter
• Upstream repository https://github.com/flutter/flutter.git
• Framework revision 54e66469a9 (3 months ago), 2024-04-17 13:08:03 -0700
• Engine revision c4cd48e186
• Dart version 3.3.4
• DevTools version 2.31.1
[✓] Android toolchain - develop for Android devices (Android SDK version 35.0.0)
• Android SDK at /Users/saqibshafique/Library/Android/sdk
• Platform android-35, build-tools 35.0.0
• Java binary at: /Applications/Android
Studio.app/Contents/jbr/Contents/Home/bin/java
• Java version OpenJDK Runtime Environment (build
17.0.10+0-17.0.10b1087.21-11609105)
• All Android licenses accepted.
[✓] Xcode - develop for iOS and macOS (Xcode 15.4)
• Xcode at /Applications/Xcode.app/Contents/Developer
• Build 15F31d
• CocoaPods version 1.15.2
[✗] Chrome - develop for the web (Cannot find Chrome executable at
/Applications/Google Chrome.app/Contents/MacOS/Google Chrome)
! Cannot find Chrome. Try setting CHROME_EXECUTABLE to a Chrome executable.
[✓] Android Studio (version 2024.1)
• Android Studio at /Applications/Android Studio.app/Contents
• Flutter plugin can be installed from:
🔨 https://plugins.jetbrains.com/plugin/9212-flutter
• Dart plugin can be installed from:
🔨 https://plugins.jetbrains.com/plugin/6351-dart
• Java version OpenJDK Runtime Environment (build
17.0.10+0-17.0.10b1087.21-11609105)
[✓] VS Code (version 1.91.1)
• VS Code at /Applications/Visual Studio Code.app/Contents
• Flutter extension version 3.92.0
[✓] Connected device (2 available)
• mini (mobile)   • FDE62D40-B2E5-406E-A456-89D5D08349F8 • ios        •
com.apple.CoreSimulator.SimRuntime.iOS-17-5 (simulator)
• macOS (desktop) • macos                                • darwin-x64 •
macOS 14.5 23F79 darwin-x64
! Error: Browsing on the local area network for iPhone. Ensure the device is
unlocked and attached with a cable or associated with the same local area
network as this Mac.
The device must be opted into Developer Mode to connect wirelessly. (code
-27)
[✓] Network resources
• All expected network resources are available.
! Doctor found issues in 1 category.

@iSaqibShafique
Please provide us complete but minimal reproducible code sample without third party implementation that still triggers the reported error.


bug: SonarCloud code scanning errors

Code Scanning results may be out of date
SonarCloud last scanned this code Oct 26, 2023. Please check that this tool is still running correctly.

https://github.com/bcgov/nr-fom/security/code-scanning/tools/SonarCloud/status/configurations/api/53e5130ebc0771ef0a4d89d6c7c8a21a1bb28a976a2d1d7b7cf3e4fbdf553000

FOM isn't actively developed or well tested, making this low enough priority to drop.


Change the logic of creating the Keyboard and Keyboard Buttons

It is very inconvenient that it is impossible to create an inline button with empty parameters in order to operate on it in the future and you have to manually translate the callback_data array every time, so you have to do this:
$keyboardInline = new \Longman\TelegramBot\Entities\InlineKeyboard([]);
 $baseInlineKeyboardButton_1 =  new \Longman\TelegramBot\Entities\InlineKeyboardButton(['text' => 'Text.',
 'callback_data' =>json_encode([
       'name' => 'test_button_1',
       'show' => true
    ])]);
 $baseInlineKeyboardButton_2 =  new \Longman\TelegramBot\Entities\InlineKeyboardButton(['text' => 'Text', 'callback_data' =>json_encode([
       'name' => 'test_button_2',
       'show' => true
    ])]);
$keyboardInline->addRow(
 $baseInlineKeyboardButton_1,
 $baseInlineKeyboardButton_2
);

I think it would be more comfortable and convenient:
$keyboardInline = new \Longman\TelegramBot\Entities\InlineKeyboard([]);

$baseInlineKeyboardButton =  new \Longman\TelegramBot\Entities\InlineKeyboardButton();
$keyboardInline = new \Longman\TelegramBot\Entities\InlineKeyboard([]);
$keyboardInline->addRow(
$baseInlineKeyboardButton->setText('Тестовая кнопка #1')->setCallbackData(([
       'name' => 'test_button_1',
       'show' => true
]),
$baseInlineKeyboardButton->setText('Тестовая кнопка #2')->setCallbackData(([
       'name' => 'test_button_2',
       'show' => true
])
);

without the need to create a new button object each time, specifying all parameters at once and without manual json_encode

I understand what you mean, but don't see such a big difference between the two snippets, as you could inline the new button objects too, which would look pretty much the same:
$keyboardInline = new InlineKeyboard([]);
$keyboardInline->addRow(
    (new InlineKeyboardButton('Тестовая кнопка #1'))->setCallbackData(json_encode([
            'name' => 'test_button_1',
            'show' => true,
        ])),
    (new InlineKeyboardButton('Тестовая кнопка #2'))->setCallbackData(json_encode([
            'name' => 'test_button_2',
            'show' => true,
        ]))
);

Also, in your example you're overwriting the $baseInlineKeyboardButton for the second button, so both buttons will have the same values.
Unless there was an actual method that ends the chaining and outputs the data of that button.
@TiiFuchs What do you think?

@noplanman I agree. I think we shouldn’t do any validation within this class and keep that to the API servers. So we should remove the validation.

Someone willing to remove it? ;D

@TiiFuchs Would make sense to kill it before the next release, what do you think?

Now is as good as anytime.


Increase max file size and refactor tests

This is a PR for the issue #88, and increase max file size to 100mb

Thanks @gabrielrumiranda! Merged!


PHPStan: Fatal error: Declaration of Mabe\Enum\Cl\EmulatedBackedEnum::from($value): BackedEnum must be compatible with BackedEnum::from(string|int $value): static

See https://github.com/phpstan/phpstan/issues/6290

fixed in 1.0.0-rc2


Verbose messages for mqm_lqm

Whenever the document is being saved, the user temporarily receives worrying messages:
 (image by @kocmitom)
The reason for this is that all segments from the document are being asynchronously sent at the same time and can arrive in various orders.
There are two ways of solving this:

Ugly & fast: just make sure of the order of requests
Principled: refactor the data saving code so that it can accept a whole document at once

Maybe resolved by commit c7d91f0.

The implementation in vilemz/develop-mqm is a combination of both approaches. The saving/loading code was rewritten and minified, but it still remains on "save single item" basis. This is because all the other instrumentation expects that, for example the testing and MakeAnnotation.

Tested to be resolved in a755370.


feat: fix deprecated imports, fixed interceptor usage, removed tsconf…

…ig.node.json, updated deprecated things

Can you open it on the same repo? you are maintainer now


Regex for tags and branches

Would be great if you could add support for regex in tags and branches

There's full semver support, so you should use something like version="1.*" for this.
It's in the docs


Docker's Ubuntu version should not be "latest"

Trying to build the docker image from Dockerfile fails, as the latest Ubuntu version as of this ticket time is 24.04. TTS cannot be found in pip sources and there are failure because much of the Python3 is managed by apt.
Changing the first line to from ubuntu:22.04 (as per readme :-) ) works just fine. This should be the case for all "stabilized" software, "latest" is never a good idea...
Cheers, except for some small quirks this is really a good solution! Amazon Polly would be also a nice addition ;)

Thanks, that's a good point!


Will streaming be removed?

I have a trouble understanding what kind of data will be removed: http://apps-of-a-feather.com/
The way I read it, if I stream certain accounts (without authentication) that should not be affected?

I'm concerned about this one too. My app is designed to stream tweets based on topics, hashtags, and/or location. Will this gravely affect tweepy's streaming capability?

From what i've read, only userstreams and sitestreams are being deprecated.
If you are using statuses/filter it will continue to work, according to twitter staff.
Would be good with some clarification on this though.

Have a look at:
https://developer.twitter.com/en/docs/accounts-and-users/subscribe-account-activity/migration/us-ss-migration-guide.html
via https://twitter.com/tinysubversions/status/996947225195438080

User and Site streams have been deprecated and retired in favor of the new Account Activity API.
Stream.filter using the statuses/filter endpoint is unaffected.
For Account Activity API support, see #1075.
Also see:
https://developer.twitter.com/en/docs/accounts-and-users/subscribe-account-activity/migration/us-ss-migration-guide.html
https://blog.twitter.com/developer/en_us/topics/tools/2018/enabling-all-developers-to-build-on-the-account-activity-api.html
https://blog.twitter.com/developer/en_us/topics/tools/2017/announcing-more-functionality-to-improve-customer-engagements-on-twitter.html
https://blog.twitter.com/developer/en_us/topics/tools/2017/building-the-future-of-the-twitter-api-platform.html
https://twittercommunity.com/t/details-and-what-to-expect-from-the-api-deprecations-this-week-on-august-16-2018/110746
https://twittercommunity.com/t/reminder-site-streams-user-streams-and-legacy-dm-endpoints-will-be-sunset-august-16th/109482
https://twittercommunity.com/t/building-on-site-streams-user-streams-or-direct-messages-action-required-to-preserve-and-prevent-disruption-to-your-twitter-integration/105736
https://twittercommunity.com/t/date-for-full-deprecation-of-user-streams-site-streams-and-legacy-direct-message-api-endpoints/98734


stdstream support

symlinks /dev/std{in,out,err} to /proc/self/fd/{0,1,2} and cleanup after
tests included

Nice! Could we add one more test that actually uses these streams, rather than just testing that the devices exist?
Here's a simple test script that reads a number x from stdin and outputs 2x on stdout and 3x on stderr:
read x
echo $((x * 2))
echo $((x * 3)) >&2

We should be able to run echo 5 | try $SCRIPT and get 10 on stdout and 15 on stderr. Similarly, we should be able to run echo 5 >FILE; try $SCRIPT <FILE (NB redir is in our shell, not in try's arg) and get the same result.

That example would also pass outside of this PR since it seems like sh does not need /dev/std{in,out,err} for those streams. @mgree

That example would also pass outside of this PR since it seems like sh does not need /dev/std{in,out,err} for those streams. @mgree

Oh! Good point lol. Then we should write a test that uses those devices appropriately.


Fix typo

There are some of BOOST_NO_EXCEPTION, which are typo of BOOST_NO_EXCEPTIONS
This makes throw_exception unusable under the existence of BOOST_NO_EXCEPTIONS.

Is there any problem with this PR?
I thought this would be merged pretty soon since this is just a typo fix.

Merged to branch origin/topic/PR107-BOOST_NO_EXCEPTIONS-typos, thanks!

Merged to develop


Update to sbt 1.2.x (1.3+ not working yet); fix latent scalastyle issue

Not sure why, but different classpath treatment during tests in sbt 1.3 makes Spark 2.x tests fail.
Otherwise just fixing a breakage in master while updating to at least SBT 1.2.8

I don't think Travis CI PR builds are populating here anymore for some reason; here it is: https://travis-ci.org/github/databricks/spark-xml/builds/733981411
I think that the StaxXmlGeneratorSuite was not actually being run (!) possibly because its package was wrong. I cleaned it up a bit and it works.
I'm also not totally clear why the scalastyle errors weren't being picked up by the PR builds before merging to master. Probably missed this in the confusion of not finding the PR results linked here.
The sbt 1.3+ error concerns Guava; somehow there's a version conflict in the classpath when building for Spark 2.x but not 3.x.


JS function bracket is meta instead of punctuation when call the function

Version: 1.37.1
Commit: f06011ac164ae4dc8e753a3fe7f9549844d15e35
Date: 2019-08-15T16:16:34.800Z
Electron: 4.2.7
Chrome: 69.0.3497.128
Node.js: 10.11.0
V8: 6.9.427.31-electron.0
OS: Darwin x64 18.2.0
Steps to Reproduce:

create a file, copy the following code and paste it. select javascript mode

function func1(word1) {
  return word1;
};

func1("hello world");

Inspect TM scopes

Does this issue occur when all extensions are disabled?: Yes
brackets are punctuation when define function

brackets are meta when call the function

I test this basic code in other languages like golang, ruby. brackets are always punctuation instead of meta.
Should JS function bracket be meta instead of punctuation when calling the function?

This is the same scoping done by other grammars and we want to maintain that so this wont be fixed.

Sorry closed and commented on wrong issue earlierr


Deploy this website to vercel

You can start the work and do the PR

Hello, we can deploy this ourselves, no need issue for this


letencrypt cert permission issue

hi,
every letsencrypt cert and its folder structure will be created with root:root privileges, but i run docker with user-docker:docker privileges.  everything works nice, but nor the letsencrypt shit cant be updated via sour dockerbunker (because of permission issues)
any advice ? imho letsencrypt should also run under docker-user ?!

Hi again.. let's encrypt is containerized and running as root in the certbot container...
Are you sure renewal does not work? AFAICT renewal should be no issue because during renewal the certbot container runs again as root...
If necessary you can always add a certbot post-renewal hook that does chown -R on the dir
e.g. save the following in /path/to/dockerbunker/data/conf/nginx/ssl/letsencrypt/renewal-hooks/post/fix-permissions.sh .. replace uid and gid with the ones of your user and group
#!/bin/sh

chown -R 1000:1000 /etc/letsencrypt

The next time certbot renews certs it will set the proper permissions. But again, I don't think this is necessary for a successful renewal.

Just realizing .. it makes sense to add this post-renewal hook via dockerbunker, as dockerbunker needs to read the contents of that directory. I'll do this when I have some spare time (also welcoming PR's :)

thx i will check it out.

@chaosbunker sorry for the long wait.
i did not describe the problem well, let me try it again.
problem:
after initializing a dockerbunker-service with letsencrypt-certs i tried to remove this service via dockerbunker menu.
everything was removed as expected, expect from nginx/ssl/letsencrypt/ folder, because the docker-certbot container writes cert-files with root-privileges. dockerbunker runs without root-privileges and cant remove this cert-files.
solution ?
now, i understand dockerbunker and think this is not an dockerbunker issue.
but for dockerbunker users its not clear what todo. so it should be mentioned as "steps after removal".
@chaosbunker what do you think?


Postprocess shaders offline

Once we have generated SPIRV offline there are a few things that we can now do to benefit the project

Bundle the SPIRV into a header so that it is compiled into the executable
Perform reflection on the SPIRV ahead of time
Identify broken functionality
Identify any divergence between HLSL and GLSL versions of the shader
Generate shader documentation of expected inputs and outputs

Not all of the above points are important. However, there is some value in defining some process where we can achieve the above over time.
Acceptance Criteria

Create an executable that can be used to reflect and post-process shaders
Check that GLSL/HLSL shaders contain the same interfaces (inputs and outputs match)
Add a CI task to run the shader check if any shaders have been altered in a PR
(optional) Bundle the SPIRV so that we don't need to load from the file system

Closing this to clean up issues related to finalizing HLSL support.


Make PriceComp fields public

While writing some unit tests for deserializing the Pyth data types, I couldn't create a PriceComp of my own. I believe the pubs may have been desired there anyway (it's the only struct without them).

Thanks, I believe this was resolved with the latest commit


✨ Generalize existing E2E tests over local vs released

Summary
This PR introduces two release tests, by generalizing the existing E2E tests.
Related issue(s)
Fixes #

/cc @pdettori
/cc @effi-ofer
/cc @ezrasilvera
/cc @nirrozenbaum

/approve


The difficulty can be set for each match.

Couldn't be completed since we lost a group member in the beginning.
Please find further explanation in the group report.


python312Packages.robotframework: 7.1 -> 7.1.1

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for python312Packages.robotframework is: Generic test automation framework
meta.homepage for python312Packages.robotframework is: https://robotframework.org/
meta.changelog for python312Packages.robotframework is: https://github.com/robotframework/robotframework/blob/master/doc/releasenotes/rf-7.1.1.rst
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 7.1.1 with grep in /nix/store/iz1jd6r59zcixxahkbqkxcyxw8zmzrda-python3.12-robotframework-7.1.1
found 7.1.1 in filename of file in /nix/store/iz1jd6r59zcixxahkbqkxcyxw8zmzrda-python3.12-robotframework-7.1.1

Rebuild report (if merged into master) (click to expand)

24 total rebuild path(s)

24 package rebuild(s)

First fifty rebuilds by attrpath

geogram
python311Packages.robomachine
python311Packages.robotframework
python311Packages.robotframework-databaselibrary
python311Packages.robotframework-excellib
python311Packages.robotframework-pythonlibcore
python311Packages.robotframework-requests
python311Packages.robotframework-selenium2library
python311Packages.robotframework-seleniumlibrary
python311Packages.robotframework-sshlibrary
python311Packages.robotstatuschecker
python311Packages.robotsuite
python312Packages.robomachine
python312Packages.robotframework
python312Packages.robotframework-databaselibrary
python312Packages.robotframework-excellib
python312Packages.robotframework-requests
python312Packages.robotframework-sshlibrary
python312Packages.robotstatuschecker
python312Packages.robotsuite
renode
renode-unstable
robotframework-tidy

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/iz1jd6r59zcixxahkbqkxcyxw8zmzrda-python3.12-robotframework-7.1.1 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A python312Packages.robotframework https://github.com/r-ryantm/nixpkgs/archive/4f65ffa29edaa5894971743bba7219e30e71bc04.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/4f65ffa29edaa5894971743bba7219e30e71bc04#python312Packages.robotframework

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/iz1jd6r59zcixxahkbqkxcyxw8zmzrda-python3.12-robotframework-7.1.1
ls -la /nix/store/iz1jd6r59zcixxahkbqkxcyxw8zmzrda-python3.12-robotframework-7.1.1/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
nixpkgs-review result
Generated using nixpkgs-review.
Command: nixpkgs-review

x86_64-linux

:white_check_mark: 47 packages built:

geogram
geogram.bin
geogram.dev
geogram.doc
geogram.lib
python311Packages.robomachine
python311Packages.robomachine.dist
python311Packages.robotframework
python311Packages.robotframework-databaselibrary
python311Packages.robotframework-databaselibrary.dist
python311Packages.robotframework-excellib
python311Packages.robotframework-excellib.dist
python311Packages.robotframework-pythonlibcore
python311Packages.robotframework-pythonlibcore.dist
python311Packages.robotframework-requests
python311Packages.robotframework-requests.dist
python311Packages.robotframework-selenium2library
python311Packages.robotframework-selenium2library.dist
python311Packages.robotframework-seleniumlibrary
python311Packages.robotframework-seleniumlibrary.dist
python311Packages.robotframework-sshlibrary
python311Packages.robotframework-sshlibrary.dist
python311Packages.robotframework.dist
python311Packages.robotstatuschecker
python311Packages.robotstatuschecker.dist
python311Packages.robotsuite
python311Packages.robotsuite.dist
python312Packages.robomachine
python312Packages.robomachine.dist
python312Packages.robotframework
python312Packages.robotframework-databaselibrary
python312Packages.robotframework-databaselibrary.dist
python312Packages.robotframework-excellib
python312Packages.robotframework-excellib.dist
python312Packages.robotframework-requests
python312Packages.robotframework-requests.dist
python312Packages.robotframework-sshlibrary
python312Packages.robotframework-sshlibrary.dist
python312Packages.robotframework.dist
python312Packages.robotstatuschecker
python312Packages.robotstatuschecker.dist
python312Packages.robotsuite
python312Packages.robotsuite.dist
renode
renode-unstable
robotframework-tidy
robotframework-tidy.dist

Maintainer pings
cc @bjornfor for testing.

[!TIP]
As a maintainer, if your package is located under pkgs/by-name/*, you can comment @NixOS/nixpkgs-merge-bot merge to automatically merge this update using the nixpkgs-merge-bot.

Add a :+1: reaction to pull requests you find important.

nixpkgs-review result
Generated using nixpkgs-review.
Command: nixpkgs-review pr 349837

x86_64-darwin

:white_check_mark: 45 packages built:

geogram
geogram.bin
geogram.dev
geogram.doc
geogram.lib
python311Packages.robomachine
python311Packages.robomachine.dist
python311Packages.robotframework
python311Packages.robotframework-databaselibrary
python311Packages.robotframework-databaselibrary.dist
python311Packages.robotframework-excellib
python311Packages.robotframework-excellib.dist
python311Packages.robotframework-pythonlibcore
python311Packages.robotframework-pythonlibcore.dist
python311Packages.robotframework-requests
python311Packages.robotframework-requests.dist
python311Packages.robotframework-selenium2library
python311Packages.robotframework-selenium2library.dist
python311Packages.robotframework-seleniumlibrary
python311Packages.robotframework-seleniumlibrary.dist
python311Packages.robotframework-sshlibrary
python311Packages.robotframework-sshlibrary.dist
python311Packages.robotframework.dist
python311Packages.robotstatuschecker
python311Packages.robotstatuschecker.dist
python311Packages.robotsuite
python311Packages.robotsuite.dist
python312Packages.robomachine
python312Packages.robomachine.dist
python312Packages.robotframework
python312Packages.robotframework-databaselibrary
python312Packages.robotframework-databaselibrary.dist
python312Packages.robotframework-excellib
python312Packages.robotframework-excellib.dist
python312Packages.robotframework-requests
python312Packages.robotframework-requests.dist
python312Packages.robotframework-sshlibrary
python312Packages.robotframework-sshlibrary.dist
python312Packages.robotframework.dist
python312Packages.robotstatuschecker
python312Packages.robotstatuschecker.dist
python312Packages.robotsuite
python312Packages.robotsuite.dist
robotframework-tidy
robotframework-tidy.dist


Support 3scale endpoint

Mashape is not the only endpoint that is used now.
3scale has a different endpoint and different header key.
https://api-2445582011268.apicast.io
header: key is 32 characters long.
user-key: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
mashape keys are 50 characters long. We could use that to automatically set the endpoint to use.

Now allowing multiple service endpoints with backwards compatibility. Now passing a apiService object around instead of importing the config into files.


Use typegen 0.17.0 in the CLI

Addressing https://github.com/GoogleContainerTools/kpt/issues/561

Shouldn't we also uprev create-kpt-fns to 17.1 and do a release?


Apply sortable components

react-sortable-component has been removed in favour of using https://www.npmjs.com/package/sortablejs or https://www.npmjs.com/package/react-sortablejs

[x] nav-group
[x] tab-group
[x] list-group

Close with https://github.com/react-photonkit/react-photonkit/commit/ed3e4257aba084243f6dc4ce81e8bc5003df7199


[RFR] Example: create button for referenced resource

Fix #1402

-1 for adding a custom example for that, because:

we can add it to the simple demo
every new example we add, we'll need to maintain. As there are many similarities between demos, this adds to our maintenance work
the place for a solution to a custom problem like that would be StackOverflow / codesandbox.

Can you add it to the simple demo instead?

Actually, I was wondering if we should add an Examples or Recipes section in the documentation with links to codesandboxes instead of having multiple example apps directly in our repository like next.js

I think you're reinventing StackOverflow ;)

That was the whole point of the examples section actually as explained when we introduced it: https://github.com/marmelab/admin-on-rest/pull/1368
I do agree that keeping many examples in our repository would make it too heavy though.

I doubt that a person with a specific question about prepopulated create forms will look in the Examples section of the documentation. My bet is that, most of the time, they'll google their question. In that case, they'll probably end up in Stack Overflow.
So for discoverability, StakOverflow is already better than us. Additionally, we could drop a few grains here and there in the documentation, where users may find them.
Sharing snippets and examples is a good idea. Implementing an entire blog admin clone for that is too much work. So IMO, a codesandbox link or a stack overflow snippet is the right format.


Reusable Blocks are not available

In functions.php on line 159 'core/reusableBlock', should enable reusable blocks for all post types. This does not work.
I replaced this line with 'core/block', and the reusable blocks appeared. I don't know if it's the correct fix but worked.

This is the correct fix, fyi.

Fixed in 7.9.5.


Define Testing Parameters for Releases for future regression testing automation

After the regression in performance of v0.34.0, it is clear that we will need a further, more comprehensive testing process for future releases which includes our various environments, setups and specific parameters we should ensure catches critical regressions in node performance. The end goal of this is to eventually automate this process in our testing environments and automatically detect regression in our defined metrics for passing beta release testing.
Our minimal testing environments include a combination of the following:
Hardware Resource Diversity Requirements:

Hetzner-powered servers (high-end performance devices)
Contabo-powered servers (low-end performance devices)

Validator Set Requirements:

Servers with minimal validators attached (<10)
Servers with many validators attached (>500)

Environment Requirements:

Lodestar instances on docker setups
Lodestar instances on bare metal setups.

A combination of each of these environments should be tested for no shorter than three days and compared with the previous stable version to analyze regression in any metrics. The following metrics checklist will determine criteria required to pass our release beta testing:

[ ] Slot chart shows consistent consensus
[ ] Stable peer count
[ ] Clock drift not greater than 5
[ ] No sync status issues
[ ] Head drift is not consistently behind (>1)
[ ] Heap space used is constant and flat with no signs of memory leaks
[ ] External memory used is constant and flat with no signs of memory leaks
[ ] Process heap bytes is constant and flat
[ ] GC pause time rate does not exceed 20%
[ ] Prometheus scrape duration does not show signs of slower response time
[ ] Validator inclusion distance at 1 as much as possible. (% of avg delays compared to previous version)
[ ] Compare validator correct head percentage average to previous release.
[ ] Compare validator previous epoch ATTESTER and TARGET miss ratios to previous release. Should be as low as possible
[ ] Compare epoch transition average time to previous release. Should be as low as possible.
[ ] Compare epoch transition utilization rate to previous release. Should be as low as possible.
[ ] Compare process block average time to previous release. Should be as low as possible.
[ ] Compare process block utilization rate to previous release. Should be as low as possible.
[ ] Compare epoch transition count per epoch to previous release. Should be at 1 as much as possible.
[ ] Compare process block per slot to previous release. Should be at 1 as much as possible.

List is a draft and WIP.

@dapplion When going through the metrics for analysis on the new beta, can you contribute to this checklist so in the future we can think about finding a way to automate? Similar to what you did for benchmarking?

From Apr 1 planning meeting, extra notes in regards to planning out testing infrastructure:
Dade: For testing infrastructure, issues don't usually show up unless we run for a couple of days, could affect velocity. How should we manage this?
Phil: We should define how an ideal testing infrastructure should look like. We want to put the work into a good process, but make sure it's accurately giving us metrics/data that helps find potential issues.
Phil: Do we need a controlled devnet environment to do testing in where we can influence parameters to simulate potential issues? Or is that too much work which doesn't reflect realities of public testnets and mainnet?
Cayman: Devnets are too small, things scale with validators and it's difficult to reproduce this on our own devnet. Should we focus on how a devnet would be beneficial for preliminary type tests such as sending/receive messages and not getting banned immediately, Beacon API endpoints, etc? Would this infrastructure be worth it? Will take additional servers and such.
Cayman: Maybe there's a way to set slots per second higher? Compress the amount of work? Change chain params to have it happen quicker?
Dade: The problem is not necessarily functional bugs, but rather performance regression. These are usually seen in a longer period of time. We should invest more in metrics monitoring. Should be some balance resources in setting up better metrics alongside testing infrastructure.
Phil: True. We should ensure the work we put into a testing infrastructure yields good data and results for it to be worth the work. If we do setup a testnet in a controlled environment, it should probably focus more on functional type testing to ensure our Beacon APIs are not broken for example. And push more of the testing infrastructure to help test against a more real-world environment like Prater. It should be focused to help relieve some grunt work (automation).

Closing for #4724


Port changes of [#11537] to branch-2.2

Cherry-pick https://github.com/Alluxio/alluxio/pull/11537 to branch-2.2
In certain applications like Presto, frequently initializing FileSystem
instance may be costly in CPU overhead. Further analysis shows when
Hadoop configuration is large, regexp used in Alluxio to check whether
an given configuration property from Hadoop can be recognized by Alluxio
property template contributed a lot to the CPU overhead.
This PR aims to remove this cost. My initial attempt was to introduce
extra logic to avoid PropertyKey.isValid. However, this approach has a
fairly large footprint in multiple most basic and important classes in
Alluxio codebase, and increases complexity. I am concerned with the
potential risk to reason and maintain the code after a patch like this.
Later I decided to instead add a cache inside PropertyKey.isValid,
given the inquiries are likely to be repeated. This approach has much
less footprint to the codebase. In this PR I also cleaned up
AbstractFileSystem.initialize in terms of configuration init.
pr-link: Alluxio/alluxio#11537
change-id: cid-f096b0232adb48c53a3a735c14ed69c0cb0b5f93

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-PR-Builder/9940/
Test FAILed.

Jenkins, test this please

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-PR-Builder/9945/
Test FAILed.

Jenkins, test this please

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-PR-Builder/9961/
Test FAILed.

Jenkins, test this please

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-PR-Builder/9963/
Test PASSed.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-PR-Builder/9968/
Test PASSed.

alluxio-bot, merge this please


Improve NWC support (return response from send payment, get_balance, make_invoice/lookup_invoice)

Hi, we added a mutiny wallet connector to Bitcoin Connect so you can connect to your wallet in any lightning webapp and seamlessly execute lightning functionality, as long as the wallet is open on a second device (e.g. keep the Mutiny wallet open on your PC and then use Bitcoin Connect to connect to it on your phone).
Unfortunately there are some issues:

Send Payment works, but it seems Mutiny Wallet never sends a response event, or at least not within 60 seconds. I had the wallet open on my phone and it marked the payment as sent within 20 seconds or so.
Get Balance and Make invoice just don't seem to be supported at all?

I created an issue here: https://github.com/getAlby/bitcoin-connect/issues/150

The response event is a problem with our relay.
What is the filter you're using to try and get it?

@benthecarman we use this code:
const event = await this.signEvent(unsignedEvent);
const sub = this.relay.sub([
  {
    kinds: [23195],
    authors: [this.walletServicePubkey],
    "#e": [event.id],
  },
]);

Ah okay, looks like we were only allowing filters that had the authors and #p defined. Have a change ready to fix that: https://github.com/MutinyWallet/blastr/pull/31

Get Balance and Make invoice just don't seem to be supported at all?

We haven't done get_balance because of the privacy concerns. I think we can add make_invoice without any issues though

Is there any info or capabilities feature of NWC? Now that the new NWC extensions are going to add a ton more API calls, some we may or may not implement. I wonder what's the best way to indicate who supports what.

@TonyGiorgio good point, it would be nice to add a methods property in the get_info RPC call at https://github.com/nostr-protocol/nips/pull/685/files
That is currently how WebLN does it: https://www.webln.guide/building-lightning-apps/webln-reference/webln.getinfo - I think this makes sense because it can be per-connection (not per-wallet-service as per the NIP-47 info event)
I will add a suggestion there.

There is the info event that you create when you create the NWC, but yeah adding to the get_info event makes sense

We added a NWC connector to the Alby extension and it will be shipped soon. It uses the get_info event which unfortunately fails with Mutiny.
If you make any progress here please let us know. I think it's cool to use your Mutiny wallet and pay on desktop using Alby with WebLN :rocket:

We added a NWC connector to the Alby extension and it will be shipped soon. It uses the get_info event which unfortunately fails with Mutiny.
If you make any progress here please let us know. I think it's cool to use your Mutiny wallet and pay on desktop using Alby with WebLN 🚀

What is it that you need out of the get_info call? So far we haven't needed to support it so I'm curious what is needed out of it besides firing off an invoice.

@TonyGiorgio if the get_info call was supported and returned a list of methods we could then know what Mutiny does and does not support (get_balance for example which Ben mentioned is not possible right now).
Currently we use get_info to test the connection. However, if the call times out we can fallback to just assuming pay_invoice is the only supported method. Unfortunately that means we cannot actually test the NWC URL is valid or not.
Adding extra support to Mutiny for the extension methods is not necessary, it'll just improve the UX in the Alby extension.

We definitely want to support most of the functions. I don't think get_info for that purpose will work well with mutiny however. It can only send responses when the wallet is open so it won't be able to register what it supports. The info event is really meant to signal what the connection supports

@benthecarman I think it's ok to require the user to have their wallet open while using the Alby extension. We can instructions there.
Currently the WebLN spec assumes the web application connected to a wallet can get a response directly from that wallet (e.g. within 60 seconds).

Okay if that is fine with you guys I guess that's okay.

By the way, was https://github.com/MutinyWallet/blastr/pull/31 deployed? I still didn't seem to get a response event when I tested again today.

It is. I tested with the filter you gave me and was able to get a response

@benthecarman thanks! it seems to be working now. The first payment I did failed with this error but then the next two succeeded. Can you check the error code?
{
  error: 'Failed to pay invoice: Payment timed out.',
  code: 'INSUFFICIENT_BALANCE'
}

It says payment timed out. That normally means the payment will fail. We send this if the payment hasn't completed after 30 seconds.

@benthecarman would it make sense to add one in the extensions PR? to me it just feels confusing because I had sufficient balance.

Currently doing concurrent requests cause all the requests to time out (e.g. if there is an outstanding get_balance or get_info request, I never get a response for send_payment even though the payment is sent). Are there any restrictions on your side we need to be aware of?

Looks like PAYMENT_FAILED was defined just not in rust-nostr will add it to my PR.

Are there any restrictions on your side we need to be aware of?

Sounds like a bug on our side, I think I might know the cause

Currently doing concurrent requests cause all the requests to time out (e.g. if there is an outstanding get_balance or get_info request, I never get a response for send_payment even though the payment is sent). Are there any restrictions on your side we need to be aware of?

Added what I think is a fix in #905. We weren't responding to events with different commands instead of sending NOT_IMPLEMENTED so we would have to continually reprocess the events. If you left the wallet open for long enough it should eventually respond I believe unless we are running into limits on the relay side.

@benthecarman thanks for looking into it. We currently set a timeout of 60 seconds so we also time out there, but I think more than 60 seconds is too long for a user to wait in our case. I will try again when the fix is merged


Is it possible langage Changing?

Sorry write a question at the issues.
but, I cannot find language setting.
is it possible language changing?
How can I change language?

There is not feature in Faker.Net.Portable itself to change the language.
However changing the value in Thread.CurrentThread.CurrentUICulture would also change the language Faker.Net.Portable uses.


OctopOS Prime Mascot Design-50

Design a cape for OctopOS Prime that is sleek and modern, appropriate for their mission.


Consider simplifying the UX for CloudControl images in Terraform

See discussion in #64.
We could change ddcloud_server to have just 3 properties:

image_id - The Id of the CloudControl OS or customer image to use.
image_name - The name of the CloudControl OS or customer image to use.
image_type - Either os, customer, or auto.
If os or customer, the the provider will attempt to resolve the Id / name as either an OS or customer image.
If auto, then the provider will attempt to resolve the Id / name first as an OS image and then as a customer image (if no matching OS image was found).
Default would be auto.

So a typical configuration that uses the "Ubuntu 14.04 2 CPU" OS image would be:
resource "ddcloud_server" "my_server" {
  // ...

  image_name = "Unbutu 14.04 2 CPU"
}

Or if you wanted to force it to use a customer image named "Ubuntu 14.04 2 CPU":
resource "ddcloud_server" "my_server" {
  // ...

  image_name = "Unbutu 14.04 2 CPU"
  image_type = "customer"
}

@mingsheng36 - what do you think?

Great! I dont know if this might be too much to ask, but can "image_type" be ?

I can do it, but only if you don't specify an image type. If you actually specify "auto" then if I reset it during deployment to the actual image type then Terraform will think it's changed and destroy / recreate the server during the next deployment.
I could make the default for image_type an empty string, which implies auto. That way, you either specify it explicitly, or it'll be computed for you. But that means users will need to understand that to auto-detect you don't specify it at all. That's probably OK though, since it's the default behaviour, and you only specify it if you want to override it.

My little opinion - I see no point or use case where Users need to define whether it is OS image or Client image (outcome - is to the server deployed & running). Since you are able to make it "auto" which means it can be computed, should we leave it this way (not allowing client to define)? It looks more elegant, simple and also reduces the chances of human errors. (Putting a name or id with mismatch type)

Problem is, when you remove the ability to override, someone inevitably comes up with a scenario you can't handle (e.g. creating a customer image with the same name as an OS image). So I'm happy to try to work out what they mean as sensible default behaviour, but experience has taught me that software is hardly ever smart enough to satisfy the user and so they will sometimes want to override the choice my code made for them :)
On 28 Nov. 2016, at 11:35 am, Ming Sheng <notifications<EMAIL_ADDRESS>wrote:
My little opinion - I see no point or use case where Users need to define whether it is OS image or Client image (outcome - is to the server deployed & running). Since you are able to make it "auto" which means it can be computed, should we leave it this way (not allowing client to define)? It looks more elegant, simple and also reduces the chances of human errors. (Putting a name or id with mismatch type)

You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/DimensionDataResearch/dd-cloud-compute-terraform/issues/66#issuecomment-263159844, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ABkezJyuarKIW9jzIeOWqEURDTseQHA9ks5rCiHUgaJpZM4K9TT4.
itevomcid

Make sense to me. :+1:

I think the scenario where Users having the same name for Client && Default Images is quite impossible (given the fact that Client Images cannot contain "spaces" and all other Default Images contain spaces in their names). However, there are no official documentation on that and from what I know, spaces might be allowed for Client Images soon (while they are imported from OVF) hence there is still a possibility to what you have mentioned.
Just my thoughts.

Interesting - hadn’t considered that :)
I think I’m comfortable with the implicit-defaults-that-you-can-explicitly-override approach for now; I think it strikes a decent balance between convenience and correctness.
On 28 Nov 2016, at 12:04 PM, Ming Sheng <notifications<EMAIL_ADDRESS>wrote:
I think the scenario where Users having the same name for Client && Default Images is quite impossible (given the fact that Client Images cannot contain "spaces" and all other Default Images contain spaces in their names). However, there are no official documentation on that and from what I know, spaces might be allowed for Client Images soon (while they are imported from OVF) hence there is still a possibility to what you have mentioned.
Just my thoughts.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/DimensionDataResearch/dd-cloud-compute-terraform/issues/66#issuecomment-263161974, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ABkezI3OKMz2zwyOYZsf29Ej7q0N3MQiks5rCiiQgaJpZM4K9TT4.
itevomcid

Yup. Well-said. esp on "implicit-defaults-that-you-can-explicitly-override". 💯

Seems like CloudControl API v2.4 just got released to public. Would have to take a look at it and see if it changes the design & implementation.

Yeah, R&D did that yesterday though the UI stuff is not there yet.  That is set for next week in preparation for the formal release.
Regards,
William Ninobla
Sr. Solutions Architect
Cloud Business Unit
Dimension Data

From: Ming Sheng<EMAIL_ADDRESS>Sent: Tuesday, November 29, 2016 6:41 AM
To: DimensionDataResearch/dd-cloud-compute-terraform
Subject: Re: [DimensionDataResearch/dd-cloud-compute-terraform] Consider simplifying the UX for CloudControl images in Terraform (#66)
Seems like CloudControl API v2.4 just got released to public. Would have to take a look at it and see if it changes the design & implementation.

You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://github.com/DimensionDataResearch/dd-cloud-compute-terraform/issues/66#issuecomment-263587773, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AQe9v0jkhqjk-FaxhaA9yaVt2SnjXVxzks5rDDmegaJpZM4K9TT4.
itevomcid

Thanks for the heads up Will. Really really really... needed the Cluster Awareness feature man.

Well it's aimed squarely at private deployments for now but it's a good step in the right direction.  I talked to product about that all re: public so hope that will come also.
Regards,
William Ninobla
Sr. Solutions Architect
Cloud Business Unit
Dimension Data

From: Ming Sheng<EMAIL_ADDRESS>Sent: Tuesday, November 29, 2016 6:45 AM
To: DimensionDataResearch/dd-cloud-compute-terraform
Cc: William Ninobla (ITaaS); Comment
Subject: Re: [DimensionDataResearch/dd-cloud-compute-terraform] Consider simplifying the UX for CloudControl images in Terraform (#66)
Thanks for the heads up Will. Really really really... needed the Cluster Awareness feature man.
�
You are receiving this because you commented.
Reply to this email directly, view it on GitHubhttps://github.com/DimensionDataResearch/dd-cloud-compute-terraform/issues/66#issuecomment-263588862, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AQe9vwmB3QC_OU-vus60aUIA91rY-HOdks5rDDqNgaJpZM4K9TT4.
itevomcid

Question: When I deploy customer images, do I need to specify the type?
The config below gives no error, but if I do not specify the "type" it shows terraform crashed
  image {
    id = "a6b0aaa9-d013-4fbf-8b76-7cfa1cbc035a"
    type = "customer" # crashes when not specified
  }

The config below works fine for default images which I thought was supposed to be the same for customer images
  image {
    name = "Redhat 7 64-bit 2 CPU"
  }

Definitely shouldn't need to specify it - defaults to auto. Can you post the log?
On 6 Dec. 2016, at 2:33 am, Ming Sheng <notifications<EMAIL_ADDRESS>wrote:
Question: When I deploy customer images, do I need to specify the type?
The config below gives no error, but if I do not specify the "type" it shows terraform crashed
image {
id = "a6b0aaa9-d013-4fbf-8b76-7cfa1cbc035a"
type = "customer" # crashes when not specified
}
The config below works fine for default images which I thought was supposed to be the same for customer images
image {
name = "Redhat 7 64-bit 2 CPU"
}

You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/DimensionDataResearch/dd-cloud-compute-terraform/issues/66#issuecomment-264884842, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ABkezLdXPvIC02NEtzjOchtRcx2Ylfq4ks5rFC6lgaJpZM4K9TT4.
itevomcid

Sorry but it's not that simple - because we fall back from OS to Customer and never the other way around, we need to give them the ability to override that.
Sensible defaults, but they can be overridden for the rare cases where that's necessary. So yes - default is to omit image type but the option is there to be explicit.
On 28 Nov. 2016, at 11:35 am, Ming Sheng <notifications<EMAIL_ADDRESS>wrote:
My little opinion - I see no point or use case where Users need to define whether it is OS image or Client image (outcome - is to the server deployed & running). Since you are able to make it "auto" which means it can be computed, should we leave it this way (not allowing client to define)? It looks more elegant, simple and also reduces the chances of human errors. (Putting a name or id with mismatch type)

You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/DimensionDataResearch/dd-cloud-compute-terraform/issues/66#issuecomment-263159844, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ABkezJyuarKIW9jzIeOWqEURDTseQHA9ks5rCiHUgaJpZM4K9TT4.
itevomcid

Never mind - I can reproduce that.

BTW, I am considering collapsing the image block to just 2 properties:
resource "ddcloud_server" "server1" {
  # ...
  image = "name|id"
  image_type = "customer" # optional, defaults to "auto"
  # ...
}

@mingsheng36 @wninobla - what do you reckon? It looks cleaner to me.

Ok, @mingsheng36 @wninobla v1.2.0-alpha1 is ready - feel free to play around and let me know what's broken :)

BTW, I am considering collapsing the image block to just 2 properties

I am fully with you on this. Looks much more cleaner!

Ok then - that's how it will work in alpha2 :)

@tintoy Seems like it is still crashing when using Client Images to deploy.
  image = "Ming Redhat 7" # Client Image Name, terraform crashes
  //  image = "a6b0aaa9-d013-4fbf-8b76-7cfa1cbc035a" # Client Image ID, terraform crashes
  //  image = "Redhat 7 64-bit 2 CPU" # Default Image Name, works
  //  image = "dde11c6a-588c-44fb-84d9-64a1d94c8dcc" # Default Image ID, terraform crashes

Terraform - v0.7.13
terraform-provider-ddcloud - v1.2.0-alpha3

Log?

Ok, so it looks like it works if you specify image_type="customer" but not if you specify image_type="auto" or omit image_type entirely.

Ok - will be fixed in the next build.

v1.2.0-alpha4

Verified (manually and via automated acceptance tests) in v1.2.0-beta1.


service is down?

Error:
https://i0.wp.com/ui-avatars.com/api/ivelinasheetl/48/9B5DE5/FFFFFF/2/0.5/false/true/false/png?ssl=1
Error:
https://i0.wp.com/ui-avatars.com/api/JennaFairlo/64/A5A58D/FFFFFF/1/0.5/false/true/false/png?ssl=1
Good:
https://i0.wp.com/ui-avatars.com/api/JennaFairlo/64/A5A58D/FFFFFF/2/0.5/false/true/false/png?ssl=1

There was some issues, my apologies! it is up


Enable safe_load in default_vars

Can one of the admins verify this patch?

"ok to test" to accept this pull request for testing
"test this please" for a one time test run
"add to whitelist" to add the author to the whitelist

Your commit message tells me what you did, but it doesn't tell me why you did it. Can you please explain?

Sure thing @j2sol! The openstack community is moving away from load in favor of safe_load to decrease a chance of a python method injection. See here: http://pyyaml.org/wiki/PyYAMLDocumentation#LoadingYAML for the risks and see here: https://security.openstack.org/guidelines/dg_avoid-dangerous-input-parsing-libraries.html for the recommendation. I realize this isnt really an issue for BlueBox but community wise it would be ideal considering we dont know how this could ever be implemented.

ok to test


Rake tasks to create and publish special routes

Trello: https://trello.com/c/j3ZOI1fQ/227-add-route-to-the-design-system-at-design-system
This introduces two rake tasks that allow special routes to be created and published.
It is intended to be used for publishing the GOV.UK design system by running the task as special_route:draft[/design-system, Design System, design-system] and then a subsequent publish task.
There is a content schemas PR, https://github.com/alphagov/govuk-content-schemas/pull/775, which adds the necessary app names so this can be used.

FYI centralising special routes came up before in https://github.com/alphagov/govuk-rfcs/pull/85
I'm a bit uneasy about this change because it feels like special routes are not very well defined - some have very minimal metadata whereas others seem to add HTML or other data to the special route content item.
It's clear how they are rendered, but how should other parts of the system handle them?
When we were working on search we had to add a blacklist because it wasn't clear which things should be searchable. And if there is no text in the content item then all search has to go on is the title.
The same thing applies to the data warehouse - is this something we want to analyse in the same as way as every other content item? If so we need a way of extracting the text of the page.

@MatMoore Yeah they're an opaque part of the stack.
I think with their "special" nature there isn't a guarantee of consistency between them. I think of them as basically means to mount applications on GOV.UK, by forgoing the standard content item approach they can't be searched, they can't be email alerts, they're an outlier - but that's just my opinion.
I think though that this PR is just there to add ease of how to add ease and consistency in adding them to the system rather than whether they should exist as a concept. It feels like that has already past and they're now a part of the stack whether or not they should be.

Since the design system will live on a service domain for now, maybe we can take the opportunity to rethink this? I think it would be better to either do this in service manual (because it's related), or start doing these special routes from short-url-manager. I think it would be a good principle to keep that all publishing of content should go via publishing-api's HTTP API, for consistency with the rest of the platform.

Closing as the team are going with a service domain


Improve performance of select() and addSelect()

We just profiled a 25.8s request with Blackfire, and found that 11.5s / 44.5% was spent on yii\db\Query::getUniqueColumns() (called by select() and addSelect()), and its callee, getUnaliasedColumnsFromSelect().

View on Blackfire ➡
We rewrote select() and addSelect() to be more efficient, avoiding getUniqueColumns() altogether and ensuring uniqueness by normalizing SELECT columns similar to the way orderBy() / normalizeOrderBy() works. Now aliases are always normalized into the ['alias' => 'column'] syntax, and even un-aliased column names (excluding expressions, sub-selects, and strings with parentheses) are aliased to themselves (['column' => 'column']).
The result:  select() isn’t even showing up on Blackfire’s radar anymore, and addSelect() is only taking up 663ms (17.3x faster), bringing the request time down to 14.1s (1.8x faster).

View on Blackfire ➡
We hope that is a performance improvement worth considering :)

Q
A

Is bugfix?
no

New feature?
no

Breaks BC?
no

Tests pass?
yes

@samdark Sorry for being a little trigger happy on this PR, but it’s good to go now :)

Merged. Thank you!

I've tested on some projects I have without issues.

Awesome! The only change we had to make in Craft was due to an array_splice() call on $query->select(), as the key that was passed in was no longer numeric. Doubt many people are doing things like that with normal queries. Probably worth mentioning that yii\db\Query::select() and addSelect() now normalize the columns when saving them to $this->select, so code that works directly with that property may need to be modified.


Enhancement request; Provide option to sort Requests on left panel alphabetically.

It would be very useful if an option was provide to sort the list of Request items (left panel) alphabetically. Thanks!

Hi @dgilbertsei, thanks for the suggestion! Can you provide more context as to why you'd find this feature useful? What problem are you having that would be solved by being able to sort requests by name?

I've created dozens of requests and use a specific naming convention, so it would just be a convenience to have them automatically sort rather than me having to drag each one as it's created to the correct position in the list. This feature is also missing from SoapUI and it's one of the features I was hoping to find in Insomnia. But Insomnia does allow for nested folders which is very useful for organizing many requests.

I also would find this feature useful, our organization is closing in on 100 individual microservices each with there own series of apis. Being able to sort your collection automatically by name would be a great time saver.

This feature is very useful to keep the requests organized, I was looking for an option to sort them manually but I don't see any

This feature is very useful to keep the requests organized, I was looking for an option to sort them manually but I don't see any

There was a duplicate issue #2594, which was resolved by #2738. This feature will be a part of the next release, so I will go ahead and close as resolved! 🎉

There was a duplicate issue #2594, which was resolved by #2738. This feature will be a part of the next release, so I will go ahead and close as resolved! 🎉


Trustless gateway broker should use subdomain gateway to prevent 301 roundtrips

Background
The current Trustless gateway broker uses path resolution by default and has 4 subdomain gateways defined in the defaults. This leads to it getting 301s for most requests because subdomain gateways redirect from path requests to the subdomain. For example:
https://cf-ipfs.com/ipfs/QmTUAobz6YU1Ej5dTibodQPNtKk2TNnQek5TXHv13Dk2zq?format=raw -> 301 https://bafybeicmg6dvbhclp6sctn7nfhaex64x7fuw552cufodvjt56zispmvhoy.ipfs.cf-ipfs.com/

https://dweb.link/ipfs/QmRCKiUi5g4w4QBpyNkTiczrcTiwQtGK9DHLnncxXdfD7c?format=raw -> 301 https://bafybeibkodyc2gs43vfj4cond2tw2kb4qsuik72bmeij5dpvwiyvsfasl4.ipfs.dweb.link/?format=raw

Since 301s are permanent, the browser will cache these after the initial request, however, this results in an additional round trip per CID.
https://github.com/ipfs/helia/blob/299bb0942bbfae492db938c4ccad4e835bab2dbd/packages/helia/src/block-brokers/trustless-gateway/trustless-gateway.ts#L48-L53
Suggested solutions

By default, use subdomain gateway URLs to fetch blocks in the gateway broker.
Use path gateways
Maybe make the gateway broker aware of whether a gateway supports subdomain resolution, since some of the public trustless gateways don't support subdomain resolution

I think we should use attempt to use subdomain gateways, and convert any cidv0 to v1

One thing to consider is that not all gateways support subdomain resolution. If we only support subdomain gateways we're limiting users because they are less common. If we support both, it comes with the added complexity (which seems fine).
I realise that subdomain resolution is important for origin isolation, but only relevant for loading sites directly from the trustless gateway.


OpenFunction website Initiation

After we discussed the website initiation in our community call, we are going to use a Hugo template Docsy to build the OpenFunction website from scratch.
Proposed steps:

Create a new GitHub repo for this website in OpenFunction Org.
Initiate the website framework.
Make it accessible, we can preview it locally or access it from the internet.
Adjust the style and design to be aligned with the OpenFunction.
Migrate the content to the website.

/cc @yuanyi-au

Please also help to add the instruction in the README, see KubeSphere website as an example.

We can close this issue now? @FeynmanZhou

Yes.


Make sure that generating pyapi does not throw errors

due to directory structure, or linenos

@postrational :   The blank line is necessary or the documentation build throws an error locally and fails to import the example.py correctly due to the literalinclude

I tried again and it's okay.  2 blank lines were on the original PR even though only one shows up on Github


Update nicd_daily_national_report.csv

@vukosim @vaibhavijames I updated the data from 17 June up to yesterday (24 June). I couldn't find a file for 19 June, despite trying quite a few possible file name iterations. Is it OK to merge this?

I am okay with it. @vaibhavijames can you chime in?

It looks good to me! We can make the changes


Fix wrong descriptions in EditorSettings

Fix wrong descriptions about editors/3d/grid_division_level_max/editors/3d/grid_division_level_min.

Can you amend the commit message to refer to which description was corrected?

The commit message has been modified.

What at first felt like just a typo, actually seems more complicated.
https://github.com/godotengine/godot/blob/6ef2f358c741c993b5cdc9680489e2c4f5da25cc/editor/plugins/node_3d_editor_plugin.cpp#L6941-L6948

Thanks!


Access to a state in on_enter, and maybe on_exit

This is actually self-descriptive.
I need to perform some behavior (insert a component) that depends on the state I'm inserting. If I have no access to the state, then I cannot effectively perform any logic inside on_enter.
I can help on PR.

This seems reasonable API-wise, but I may significantly change some of the APIs in Bevy 0.14 (because of observers). So I'll get back to this.
For now, you can use the Added filter in a system, or an odd workaround like this:
commands.spawn((
    SomeInitialState,
    StateMachine::default()
        .on_enter::<MyState>(|entity_cmds| entity_cmds.add(|entity: Entity, world: &mut World| {
            if world.get::<MyState>(entity).should_also_be_fancy {
                world.entity_mut(entity).insert(Fancy);
            }
        })),
));

I actually did use .command_on_enter as I have only one entity with a given state at the moment, so I can just query it. But thanks for the idea.
Looking forward 0.14 and observers

Ok, I don't plan to make large API changes, so this issue is unblocked. I'd accept a PR for this.


Fixing study contrast for ot_crispr OTAR2054

The contrast for some of the OTAR2054 studies are not correct:

[x] Make sure the contrast and the MAGeCK files are consistent.
[x] Make sure the correct data is propagated to evidence.

Configuration was fixed in PR#6, and is released by v23.04.1
New evidence file generated and validated against schema, however for OTAR035, the schema needed to be a bit relaxed to allow missing studyOverview
Number of evidence in the resulting set is: 8600. (Same number as before)
The fix was manually checked and the file was uploaded: gs://otar013-ppp/ot_crispr/ot_crispr_2023-04-06.json.gz


make dq.stack general for SparseDIAQArray

This PR changes the code for dq.qarray to accept SparseDIAQArray objects that do not share the same offsets and works for batched versions of the sparse objects.
diags = [
    jnp.array([[0,1,2], [0,0,3]]),
    jnp.array([[0,4,5], [0,0,6]]),
    jnp.array([[0,7,8], [0,0,9]]),

]
offsets = (1,2)
x = SparseDIAQArray(dims, offsets, diags)

diags = [
    jnp.array([[1,2,3], [0,1,2], [0,0,4]]),
    jnp.array([[4,5,6], [0,1,2], [0,0,7]]),
    jnp.array([[8,9,10], [0,1,2], [0,0,11]]),
]
offsets = (0,1,2)
y = SparseDIAQArray(dims, offsets, diags)

stacked_z = stack([x,y]) #stacked_z.shape = (2,3,3,3)

Closing with @bsaoptima's agreement, to integrate the code in another PR


refactor: de-depulicate make_dep_prefix implementation

What does this PR try to resolve?
I don't know why make_dep_prefix was there but maybe they shouldn't repeat themselves.
How should we test and review this PR?
Should have no behavioral change.

@bors r+

:pushpin: Commit ae17f2cd114314550761f0d43da64c2a6622359a has been approved by epage
It is now in the queue for this repository.

:hourglass: Testing commit ae17f2cd114314550761f0d43da64c2a6622359a with merge 202eb1d8a028bf54082d187e989c93b19962d408...

:sunny: Test successful - checks-actions
Approved by: epage
Pushing 202eb1d8a028bf54082d187e989c93b19962d408 to master...


translation EG cutting is affecting other devices

Hi,
Devices that are actual vacuums are now "cutting" the floor?
This is a weird issue that has happend to me since upgrading.
for example;
Changed to Cutting triggered by automation Turn vacuum on triggered by time

Hello,
sorry for the very late answer, i have been busy at work !
I had not spotted this. Thanks for the report, i'll have a look into it

Hi,
I have the same issue. Maybe this can help to solve this.
From the Husqvarna github: https://github.com/Thomas55555/husqvarna_automower/pull/184


[BUG] fix persistent HNSW parameter migration

Description of changes
Now correctly handles migration of persistent HNSW params.
Test plan
I updated the cross_version_persist test to parameterize across with_persistent_hnsw_params = [False, True]. Before the changes to chromadb/db/mixins/sysdb.py, the updated test was failing.

If someone upgraded to 0.5.4, and the migration already ran, will it have to be rerun?

If someone upgraded to 0.5.4, and the migration already ran, will it have to be rerun?

yes, @atroyn do you know where would be a good place to hook in for this?

If someone upgraded to 0.5.4, and the migration already ran, will it have to be rerun?

yes, @atroyn do you know where would be a good place to hook in for this?

I think this will have to re-run if it's already migrated, yes. The reason is the migration (which calls _insert_config_from_legacy_params on read) only checks for a None collection config string. Users who have already migrated will have this populated, so the migration will not trigger. This is my fault for missing that the persistent HNSW params were extracted on a different codepath.
The fix is going to be to make sure that the HNSWConfiguration represented in the CollectionConfiguration string contains all the HNSW metadata keys. This is annoying because it means we have to check metadata on every read.
I am not sure we want to eat that performance hit for the possibly 0 users who will have ever changed hnsw:batch_size or hnsw:sync_threshold since these are completely undocumented parameters, for which we otherwise set defaults.

Without this fix, chromadb will completely refuse to fetch a collection with persistent parameters:

I would be ok changing the config logic here to bypass this check as that code is deprecated anyways. As far as I know letting previously-configured hnsw:batch_size/hnsw:sync_threshold revert to their defaults shouldn't result in any correctness bugs.
I wonder if it'd be worth adding telemetry for config fields so we have more data in the future.

I'm unclear on why this is triggering since the migration is nondestructive?


Helper methods

What are your thoughts on providing helper methods such as fetch.post and fetch.put? They would just automatically add { method: 'WHATEVER' } to the options argument.

I am kinda against introducing API out of fetch spec's scope. It's pretty easy to write a helper library to extend node-fetch functionality if you prefer.
Plus it's easier to think of fetch as a simple function returning promise, instead of an instance of Fetch

Gotcha, fair enough!


Get Overloaded css stylesheet without scss

How to receive separately the file css, separately from most bootstrap?
Example
<link href="css/bootstrap.min.css" rel="stylesheet">
<link href="css/style.css" rel="stylesheet">  -- this is overload main bootstrap css

We don't use bootstrap css files, because we use custom variables and overwrite bootstrap styles. So you should use only our styles.

It is bad as won't allow to receive timely updates in case of a release of the new version bootstrap


Questions

Hi there, I have two questions,

Is it possible to get the value of a Variable and how if so? For example:

Variable paramVar = handleMaker.param(idx).invoke("get", p.getName());
String paramValue = ???

Is there any way that I can call a function from the java standard library?
For example, how do I call the Integer.parseInt function? Something like this:

ClassMaker cm = ClassMaker.begin().classLoader().loadClass("java.lang.Integer");
MethodMaker mm = cm.getMethod("parseInt", String.class);
Variable intParamVar = mm.invoke("parseInt", paramVar);
Thanks a lot.

I don't understand what you mean here. The parameter doesn't have a value except when the code is finished and it's run.
var intParamVar = mm.var(Integer.class).invoke("parseInt", paramVar);

So I can't get the value of the variable when the bytecode is run?
Ok that makes sense, should have thought about that, thanks.

The first solution worked, so yeah I don't need to get the value itself to then call the parseInt function. Thank you.


QA-15156 Backport mimetype resolution

JIRA

https://jira.jahia.org/browse/QA-15156
Description
Backport mimetype resolution

In the ticket, we also have these follow-up PRs https://github.com/Jahia/jcontent/pull/1290/files?w=1 and https://github.com/Jahia/jcontent/pull/1293/files?w=1.
Do we need to include these in the backport as well?


Add documentation to clarify un-interpolatable type on animation blending

Context https://github.com/godotengine/godot/issues/95684#issuecomment-2295029182

Clarify that interpolation is not possible for the following variant types and that other values can be interpolated by animation.

Nil
NodePath
RID
Object
Callable
Signal
Dictionary
PackedByteArray

Thanks!


AttributeError: 'AdamW' object has no attribute 'half'

Hi
I am trying to make the minimal example work with deepspeed, here is my codes:
test_deepspeed.py
import io
import torch
import torch.nn as nn
import deepspeed
import json

class Model(nn.Module):
  def __init__(self):
       super(Model, self).__init__()
       self.classifier = nn.Linear(50, 3)
  def forward(self, x):
      return self.classifier(x)

if __name__ == "__main__":
   with io.open('ds_config.json', "r", encoding="utf-8") as f:
       config = json.load(f)

   deepspeed.init_distributed()
   model = Model().cuda()
   optimizer = torch.optim.AdamW(model.parameters(), lr=0.001)
   model = deepspeed.initialize(model, optimizer, config_params=config)

here is ds_config.json file's content:
{
    "train_batch_size": 10,
    "fp16": {
        "enabled": true,
        "loss_scale": 0,
        "loss_scale_window": 1000,
        "hysteresis": 2,
        "min_loss_scale": 1
    },
    "zero_optimization": {
        "stage": 2,
       "allgather_partitions": true,
       "allgather_bucket_size": 2e8,
       "reduce_scatter": true,
       "reduce_bucket_size": 2e8,
        "overlap_comm": true,
        "contiguous_gradients": true,
        "cpu_offload": true
    },
    "optimizer": {
        "type": "AdamW",
        "params": {
            "lr": 3e-5,
            "betas": [ 0.9, 0.999 ],
            "eps": 1e-8,
            "weight_decay": 3e-7
        }
    }
}

here is how I run the codes:
deepspeed codes.py
here is the error I got
  File "test_deepspeed.py", line 23, in <module>
    optimizer = torch.optim.AdamW(model.parameters(), lr=0.001).half()
AttributeError: 'AdamW' object has no attribute 'half'

could you assist me please with helping me completing this minimal example? this is also helpful to share some working example such as this in the repo for the new comers such as me.
thanks

I am not too familiar with DeepSpeed, but this seems to be a pytorch error as the AdamW cannot be combined with half().
Please correct me if I am wrong.

@lukasfolle Thanks for  your response, which is correct.
@juliahane AdamW is a torch.optim.Optimizer type which does not have half() method. On the other hand, half() is defined on other types such as Modules and Tensors. With DeepSpeed, you don't need to worry about calling half() to enable mixed-precision training, the DeepSpeed engine will do that for you.
@lukasfolle  Thanks for helping to resolve this.
@juliahane I will close this now, please feel free to reopen if needed.


Add Appveyor CI support

After mentioning it in #1097, I've added an appveyor.yml (based on the one in rust-everywhere, which builds all variants of {stable, beta, nightly}, {MSVC x64, MSVC x86, gcc x64, gcc x86}) and a link to an Appveyor badge in README.md.
To complete the job, the rustfmt repo will have to be added as a new project in Appveyor. I've added my fork under my Appveyor account and it's running on Appveyor as expected.

Awesome, thank you!

Ok, I added rustfmt to Appveyor and kicked off a new build, let's see if it works!


Bug in Documentation Fixed Issue#2631

There was this 2 mistakes in documentation which I have fixed

Wrong image for Square root block
Wrong image for Absolute block
Square root being referred as Sqrt in 2 places

Can one of the admins verify this patch?

@ewpatton I made my changes to a separate branch as per your suggestion thank you.

@ewpatton it looks good, I checked it.

all block images are changed from sqrt to square root.
no broken links.
gifs are also updated to square root.

If we don't consider the height and width of the block images then it looks good otherwise the size of the new images is larger than the previous one.
@devarsh-mavani-19 I think you had downloaded block as png from block editor then used in docs while other block images are just screenshots.


Grid not aligned with ticks

Grid lines don't seem to be aligned with the ticks even in the non zoomed view.

I second this. The grid should :
1- be aligned to the ticks
2- be aligned to the ticks for which the label is displayed


Operator does not meet minimum stake requirement for quorum

Issue Summary
root@ip-172-31-44-221:~/.eigenlayer/operator_keys# eigenlayer operator status operator.yaml
✅ Operator configuration file read successfully 0xA83d546ce7451CEb37595e864Af11b7c33a8af87
✅ Operator configuration file validated successfully 0xA83d546ce7451CEb37595e864Af11b7c33a8af87
✅ Operator is registered on EigenLayer
--------------------------- Operator Details ---------------------------
Address: 0xA83d546ce7451CEb37595e864Af11b7c33a8af87
Earnings Receiver Address: 0xA83d546ce7451CEb37595e864Af11b7c33a8af87
Delegation Approver Address: 0x0000000000000000000000000000000000000000
Staker Opt Out Window Blocks: 33
Environment
.

EigenDA version: eigenlayer-clie 0.7.2
Operating System: 22.04.1-Ubuntu
Node configuration (if applicable):
Any specific settings or modifications:

Steps to Reproduce

./run.sh opt-in 0,1

Expected Behavior

Actual Behavior
.
Possible Solution
.
Additional Context
.

use this command "./run.sh opt-in 0" return the same error

is this holesky or mainnet?

Holesky I have the same.


Add alternate pager (thumbs) / synchronized carousels

Feature request.
Alternate pager - thumbnails, etc.
http://jquery.malsup.com/cycle2/demo/pager.php
Would allow for the ability to create synchronized carousels (using thumbs for pager):http://jquery.malsup.com/cycle2/demo/caro-pager.php
I'll take a look at this as well.

Hey wjthomas9, maybe you can share your code how you got the custom pager (first screenshot) working?

No help there apparently, but here it is working with numbers:
http://bouvet-toredahl.herokuapp.com/bouvet/diakonhjemmet/master.html?page=karusell

hey toredahl, any chance you could share how you accomplished that paging system with numbers? :)

Can we also choose where the ul.slick-dots is located in our html?
For example: outside the div.slick-slider

@jennybeaumont you do that with the customPaging option, @goslingcools you do that with the appendDots option

Aha I see..! Your documentation on https://github.com/kenwheeler/slick/ is more complete than on  http://kenwheeler.github.io/slick/ :-)

Hi! Awesome slider, the best!
One feature request:
any element on the page could be an alternate pager like this http://bxslider.com/examples/thumbnail-pager-1
It would be very helpfull, this feature alows acting slider like tabs. And it's not the same as 'thumbs' feature.
Thank you!

@jasonday wrote in the first post:

Would allow for the ability to create synchronized carousels (using thumbs for pager): http://jquery.malsup.com/cycle2/demo/caro-pager.php

@kenwheeler Did you also add this feature? thx

I've used this method to setup a custom pager, http://codepen.io/anon/pen/NPeLrd as well with some jquery to add an active class the navigation it works like a charm.  The one restriction is if you click really fast, before the slides transition has finished it doesnt update the slide in time however I just set a very fast fade speed and it fixes the issue. I suppose you could apply a CSS transition in there too on slick-current to simulate a slower fade if you wanted.

The following author's example is wrong:
customPaging: function(slick,index) {
    return slick.$slides.eq(i).find('img').prop('outerHTML');
}

should be:
customPaging: function(slick,index) {
    return slick.$slides.eq(index).find('img').prop('outerHTML');
}


Format of the Answer - orphan control for defense titles

Note that we should have a set of word styles that we apply consistently for all of the text in the Answer


x/*/{query,client/{cli,rest}}: query for single object by ID.

Deployment
Order
Bid
Lease
Provider

Will take this.

@gosuri check this https://github.com/ovrclk/akash/commit/104608644947bcaf3c495b197851fc1d8199778b. We used codec.MarshalJSONIndent instead of sdkutil.RenderQueryResponse to get query response and it worked. Do we specifically need to use sdkutil or is it fine to use codec?

Also for providers, we don't have any provider id for now. To query single provider, should we use host and owner?

@gosuri check this 1046086. We used codec.MarshalJSONIndent instead of sdkutil.RenderQueryResponse to get query response and it worked. Do we specifically need to use sdkutil or is it fine to use codec?

@boz can help you with that

every provider has a public key

I created provider with host, region and moniker values. But when I tried to query all providers list, I got this output:
[
  {
    "owner": "akash1kzpa4zlvxyqlz4kqe0rneap3l5c9r2x3u3cse0",
    "host-uri": "http://akash.sahithnarahari.com",
    "attributes": [
      {
        "key": "cmVnaW9u",
        "value": "c2Zv"
      },
      {
        "key": "bW9uaWtlcg==",
        "value": "YWtoaWw="
      }
    ]
  }
]

In above provider details, I can't find any public key for provider.

Yes, there's no pubkey in the output. Can you dig into the code and try to add a pubkey to the response? Btw, @gosuri we cannot read plain private key of an account now, do you suggest any other method to create provider private key? previous docs ref: https://docs.akash.network/providers/kube#deploy-akash-provider-service-on-kubernetes

Sorry, I'm just seeing this now.
The provider address is it's owner's address; you can use the account owner's keys.
I added the single provider query in #453
sdkutil.RenderQueryResponse is a small wrapper around codec.MarshalJSONIndent to reduce repetition across all of the query handlers.  Please continue to use it or remove it from everywhere if there's a good reason to.
Thanks for looking into this!

note that #440 should be done prior to this for the REST endpoints.

Implement REST and CLI interfaces for singular and collection objects:
* [ ]  Deployment

* [ ]  Order

* [ ]  Bid

* [ ]  Lease

* [ ]  Provider

Notes:
Singular vs Collection
The default mechanism is akash query provider provider for singular and akash query provider providers for collection. Ideally, a single command should handle both type of objects.
For example: akash query providers <provider>.. should present a single or multiple records
Remote filtering
Currently, the filtering happens on the client. Ideally, the filtering should happen on the server for optimal user experience.

There occurs a problem if we change provider query to akash query providers <provider> where provider is optional. By this, we can have only this command in provider module. We cannot add further any query commands to provider module if required.

Good point. I forget - does cobra allow default commands?  Alternatively, how about something like this:

type
command
notes

collection
provider list

singular
provider get [address]
address defaults to current key address if --from is given

Good point. I forget - does cobra allow default commands? Alternatively, how about something like this:
type 	command 	notes
collection 	provider list
singular 	provider get [address] 	address defaults to current key address if --from is given

Looks good. We can update to this.

Good point. I forget - does cobra allow default commands? Alternatively, how about something like this:
type 	command 	notes
collection 	provider list
singular 	provider get [address] 	address defaults to current key address if --from is given

We cannot use --from flag in queries as it is to specify key used for signing. Instead we can go with arguments as per cosmos structure. provider get  command without --from flag is good for singular type.

Yes, I think SDK registered this flag for txs and there would be conflict if we re-use them for queries. Instead we can use owner flag but that doesn't fit best. It's better if we keep all the required params in the query cmd and avoid flags. We can use flags for optional params may be.
... provider get <address> looks like a better convesion without making the address param optional
Also, what if there are more than one providers registered from single address? Are we restricting this in create provider @akhilkumarpilli ?

Yeah, we are restricting in create provider. Only one provider can be created per single address.

There are some existing utilities for getting IDs for the get commands, and I believe that they can be used for filtering as well.
There are two components of each: one for adding flags to the command, one for parsing them when executing the command.

object
add flag
parse flag

DeploymentID
AddDeploymentIDFlags
DeploymentIDFromFlags

GroupID
AddGroupIDFlags
GroupIDFromFlags

The pattern continues for OrderID and BidID in x/market.
The original idea was that if for get commands you would have to supply all of the options, for list commands the populated flags would be used for filtering the results.


ISIS-1162 Add attribute for permission ldap extraction

I propose new permisions creation from LDAP attribute
Alternatively, permissions can be extracted from the base itself with the parameter searchUserBase,
the attribute list as userExtractedAttribute and the permission url as permissionByUserAttribute.
The idea is to extract attribute from the user or the group of the user and map directly to permission rule in replacing the string {attribute} by the extracted attribute (can me multiple).
See the sample for group and user attribute and mapping:
ldapRealm.searchUserBase = ou=users,o=mojo
ldapRealm.userObjectClass=inetOrgPerson
ldapRealm.userObjectClass=organizationnalPerson
ldapRealm.groupExtractedAttribute=street,country
ldapRealm.userExtractedAttribute=street,country
ldapRealm.permissionByGroupAttribute=attribute:Folder.{street}:Read,attribute:Portfolio.{country}
ldapRealm.permissionByUserAttribute=attribute:Folder.{street}:Read,attribute:Portfolio.{country}

In disorder , sorry the JIRA ISIS-1162

Thanks for this contribution... haven't forgotten about it, just need to find time to review.  Currently working towards putting out a 1.9.0 release, so hopefully later on this month.
thx again,
Dan


Update docker-compose.yml to include Pipelines

NOTE: their docs also say to....
Connect to Open WebUI:

Navigate to the Settings > Connections > OpenAI API section in Open WebUI.
Set the API URL to http://localhost:9099 and the API key to 0p3n-w3bu!. Your pipelines should now be active.

Citation:
https://github.com/open-webui/pipelines/tree/main?tab=readme-ov-file#-quick-start-with-docker

Thanks @jeffscottward! I actually thought pipelines was already a part of Open WebUI even without this change. Could you expand on that a bit more and what this is adding?

It's adding the pipelines feature.
Presently if I go to my out of the box Ollama/openwebUI install from Coolify, I see this
When in actuality (after the install I should see this)

I believe the reason being is that it requires a separate server.

Please do test it before merging, I did it quick and haven't tested but matched the config as best as I understand.


chore(master): release 1.0.3

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

github release binaries hopefully (b901bc0)
update nix flake to build lsp (00e97af)

This PR was generated with Release Please. See documentation.

Codecov Report

Merging #158 (160b3b0) into master (cef70f1) will not change coverage.
The diff coverage is n/a.

@@          Coverage Diff           @@
##           master    #158   +/-   ##
======================================
  Coverage    0.09%   0.09%
======================================
  Files          13      13
  Lines        1053    1053
======================================
  Hits            1       1
  Misses       1052    1052

Continue to review full report at Codecov.

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

:robot: Release is at https://github.com/polarmutex/beancount-language-server/releases/tag/v1.0.3 :sunflower: