Iissue 1197 eigen methods for autodiff types

Summary
Uses Eigen's plugin system to add methods for extracting and manipulating the values/gradients from matrices of fvar and var.
For var:

.val() provides read-only access to the values
.adj() provides read and write access to the adjoints

For fvar<T>:

.val_() provides read and write access to the values
.d_()  provides read and write access to the tangents

This also works with mixed-mode variables, such as fvar<var> (e.g. .val_().val())
This requires that the header prim/mat/fun/Eigen.hpp be included before any other Eigen headers.
I had to modify the fvar struct to have a method for returning the type of the containing variable. Without this, another header file would have been needed (like ```partials_type``)`
Tests
fwd/mat/fun/determinant has been re-written to use the new methods
Side Effects
None
Checklist

[x] Math issue #1197

[x] Copyright holder: Andrew Johnson
The copyright holder is typically you or your assignee, such as a university or company. By submitting this pull request, the copyright holder is agreeing to the license the submitted work under the following licenses:
- Code: BSD 3-clause (https://opensource.org/licenses/BSD-3-Clause)
- Documentation: CC-BY 4.0 (https://creativecommons.org/licenses/by/4.0/)

[x] the basic tests are passing

unit tests pass (to run, use: ./runTests.py test/unit)
header checks pass, (make test-headers)
docs build, (make doxygen)
code passes the built in C++ standards checks (make cpplint)

[x] the code is written in idiomatic C++ and changes are documented in the doxygen

[x] the new changes are tested

I'll close this for now until the discussion in #1197 is resolved, no sense clogging up the queue!


Missing dylib - System.DllNotFoundException: libc.dylib

Issue Description
OmniSharp crashes on load
Steps to Reproduce

Install C# extension for VSCode
Load VSCode

Expected Behavior
Doesn't crash
Actual Behavior
Crashes
Logs
OmniSharp log
Starting OmniSharp server at 11/1/2019, 11:19:38 AM
    Target: /Users/tomchambers/projects/interactive-tree-2/interactive-tree-2.sln

OmniSharp server started with Mono 6.0.0.
    Path: /Users/tomchambers/.vscode/extensions/ms-vscode.csharp-1.21.5/.omnisharp/1.34.5/omnisharp/OmniSharp.exe
    PID: 38108

System.DllNotFoundException: libc.dylib
  at (wrapper managed-to-native) OmniSharp.Utilities.PlatformHelper.Unix_realpath(string,intptr)
  at OmniSharp.Utilities.PlatformHelper.RealPath (System.String path) [0x00012] in <9ffa92e8694e48d1b573209b14265063>:0
  at OmniSharp.Utilities.PlatformHelper.GetMonoRuntimePath () [0x00050] in <9ffa92e8694e48d1b573209b14265063>:0
  at OmniSharp.MSBuild.Discovery.Providers.MonoInstanceProvider.GetInstances () [0x0000d] in <4ac205bc4ff74f949c5f51469aff0882>:0
  at OmniSharp.MSBuild.Discovery.MSBuildLocator.GetInstances () [0x0001e] in <4ac205bc4ff74f949c5f51469aff0882>:0
  at OmniSharp.MSBuild.Discovery.Extensions.GetBestInstance (OmniSharp.MSBuild.Discovery.IMSBuildLocator msbuildLocator, System.Boolean& invalidVSFound) [0x00007] in <4ac205bc4ff74f949c5f51469aff0882>:0
  at OmniSharp.MSBuild.Discovery.Extensions.RegisterDefaultInstance (OmniSharp.MSBuild.Discovery.IMSBuildLocator msbuildLocator, Microsoft.Extensions.Logging.ILogger logger) [0x00000] in <4ac205bc4ff74f949c5f51469aff0882>:0
  at OmniSharp.CompositionHostBuilder.Build () [0x00098] in <4ac205bc4ff74f949c5f51469aff0882>:0
  at OmniSharp.Stdio.Host..ctor (System.IO.TextReader input, OmniSharp.Services.ISharedTextWriter writer, OmniSharp.IOmniSharpEnvironment environment, System.IServiceProvider serviceProvider, OmniSharp.CompositionHostBuilder compositionHostBuilder, Microsoft.Extensions.Logging.ILoggerFactory loggerFactory, System.Threading.CancellationTokenSource cancellationTokenSource) [0x00057] in <e4936d2fc4a345db9e9e45ce23594cb9>:0
  at OmniSharp.Stdio.Driver.Program+<>c__DisplayClass0_1.<Main>b__1 () [0x00138] in <f72791d974f4428c987a822ce12b519e>:0
  at OmniSharp.CommandLineApplication+<>c__DisplayClass11_0.<OnExecute>b__0 () [0x0000b] in <4ac205bc4ff74f949c5f51469aff0882>:0
  at McMaster.Extensions.CommandLineUtils.CommandLineApplication.Execute (System.String[] args) [0x00039] in <344a1e8cd6594b17b1e01f8df6ae8827>:0
  at OmniSharp.CommandLineApplication.Execute (System.Collections.Generic.IEnumerable`1[T] args) [0x00042] in <4ac205bc4ff74f949c5f51469aff0882>:0
  at OmniSharp.Stdio.Driver.Program+<>c__DisplayClass0_0.<Main>b__0 () [0x00028] in <f72791d974f4428c987a822ce12b519e>:0
  at OmniSharp.HostHelpers.Start (System.Func`1[TResult] action) [0x0001c] in <4ac205bc4ff74f949c5f51469aff0882>:0

[ERROR] Error: OmniSharp server load timed out. Use the 'omnisharp.projectLoadTimeout' setting to override the default delay (one minute).

C# log
Post the output from Output-->C# here
Environment information
VSCode version: 1.39.2
C# Extension: 1.21.5
Mono Information
        OmniSharp using global mono :6.0.0
Dotnet Information
.NET Core SDK (reflecting any global.json):
 Version:   3.0.100
 Commit:    02df19ceac
Runtime Environment:
OS Name:     Mac OS X
OS Version:  10.14
OS Platform: Darwin
RID:         osx.10.14-x64
Base Path:   /usr/local/share/dotnet/sdk/3.0.100/
Host (useful for support):
Version: 3.0.0
Commit:  7d57652f33
.NET Core SDKs installed:
2.1.301 [/usr/local/share/dotnet/sdk]
2.1.504 [/usr/local/share/dotnet/sdk]
2.1.505 [/usr/local/share/dotnet/sdk]
2.1.701 [/usr/local/share/dotnet/sdk]
3.0.100 [/usr/local/share/dotnet/sdk]
.NET Core runtimes installed:
Microsoft.AspNetCore.All 2.1.1 [/usr/local/share/dotnet/shared/Microsoft.AspNetCore.All]
Microsoft.AspNetCore.All 2.1.8 [/usr/local/share/dotnet/shared/Microsoft.AspNetCore.All]
Microsoft.AspNetCore.All 2.1.9 [/usr/local/share/dotnet/shared/Microsoft.AspNetCore.All]
Microsoft.AspNetCore.All 2.1.12 [/usr/local/share/dotnet/shared/Microsoft.AspNetCore.All]
Microsoft.AspNetCore.App 2.1.1 [/usr/local/share/dotnet/shared/Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 2.1.8 [/usr/local/share/dotnet/shared/Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 2.1.9 [/usr/local/share/dotnet/shared/Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 2.1.12 [/usr/local/share/dotnet/shared/Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 3.0.0 [/usr/local/share/dotnet/shared/Microsoft.AspNetCore.App]
Microsoft.NETCore.App 2.1.1 [/usr/local/share/dotnet/shared/Microsoft.NETCore.App]
Microsoft.NETCore.App 2.1.8 [/usr/local/share/dotnet/shared/Microsoft.NETCore.App]
Microsoft.NETCore.App 2.1.9 [/usr/local/share/dotnet/shared/Microsoft.NETCore.App]
Microsoft.NETCore.App 2.1.12 [/usr/local/share/dotnet/shared/Microsoft.NETCore.App]
Microsoft.NETCore.App 3.0.0 [/usr/local/share/dotnet/shared/Microsoft.NETCore.App]
To install additional .NET Core runtimes or SDKs:
https://aka.ms/dotnet-download

Visual Studio Code Extensions

Extension
Author
Version

csharp
ms-vscode
1.21.5

prettier-vscode
esbenp
2.3.0

terraform
mauve
1.4.0

unity-tools
Tobiah
1.1.1

vscode-yaml
redhat
0.5.3

try updating to Mono 6.4.0 https://www.mono-project.com/download/stable/

I hope this will help you but I am afraid it this looks more like a problem with your environment.
libc is the user level standard C library that is part of OS X.
/usr/lib/libc.dylib is a symlink to /usr/lib/libsystem.dylib. if those can't be resolved correctly then it's not really an OmniSharp issue

Hey @tomchambers2 does this still reproduce for you with the latest version?

Closing out as no additional info was added.

edit ~/.zshrc
`
.Net Core
export DOTNET_ROOT="$(dirname $(which dotnet))"
export DYLD_FALLBACK_LIBRARY_PATH="/usr/lib"
export PATH="$PATH:$DOTNET_ROOT"
Export PATH="$PATH:$DYLD_FALLBACK_LIBRARY_PATH"
`
After setup, restart the VSCode


fix: a bunch of small universal.sh bugs

closes #984
closes #974
- What I did
Fixes:

removed the @sshnp path segment in the path for np.sh

The path should be ~/.local/bin/np.sh now

instead of entering "/done" to enter the devices, just enter an empty line

This is arguably worse for people who don't read, but if they didn't read to setup the np.sh script, they probably didn't read how to use it either.

Make sure that authorized_keys file is owned by the correct user
Make sure that ~/.atsign/keys is owned by the correct user

Chores:

Better atSign input overall, make sure people know which atSign they are entering at all times. See commit 0db36f699ae382cc9e4563e5f8532f72792dc3ab

- How I did it
- How to verify it
- Description for the changelog
fix: a bunch of small universal.sh bugs

The path should be ~/.local/bin/np.sh now
I would have thought a personal np.sh would be put in ~/.local/bin


release v1.12.0

added import/external-module-folders (thanks to @zloirock)

@jfmengels, any concerns?

Coverage decreased (-2.0%) to 95.665% when pulling 6e12c9e24e6c4fc770093637f976e1a84b633d40 on master into 79905968cbd2ae469484d70b0c952e59067fbf48 on release.

None, LGTM :+1:


add build status to README

tbh I just want the link to the travis build

Codecov Report

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

@@           Coverage Diff           @@
##           master      #20   +/-   ##
=======================================
  Coverage   48.37%   48.37%
=======================================
  Files           2        2
  Lines         215      215
=======================================
  Hits          104      104
  Misses        103      103
  Partials        8        8

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 59cd486...26dd1ba. Read the comment docs.


Preserving custom headers & dynamic session instantiation for bypassing more secure CSRF defense systems

Pull request
Title self-explanatory. If any more documentation is needed, please let me know and I would be happy to go into the code and add more comments.
These changes also make it possible to host the MITM-compromised site in a subdomain or subdirectory. This feature was required for a project of mine and more people may benefit from its inclusion in the library.
This code should be 100% backward compatible as almost all changes are either to internals or adding more keyword arguments.

Thanks. Looks like isort is failing. You can test locally by running tox. Also I did a new push yesterday if you could rebase off that.


Function to combines overlapping events into combination events.

The function should perform this task based on the parameter -- combinationWindow which specifies the time that two event eras need to overlap to be considered a combination treatment. If there are more than two overlapping event eras, we sequentially combine treatments, starting from the ﬁrst two overlapping event eras.

fixed in #37


Lumen

Hi there,
Is it possible to have migrations-generator in Lumen too?
trying to use it in Lumen but failed.

Here my composer.json looks like

Would have to investigate. Don't really use Lumen myself. But if you are able to fix it, submit a PR and I'll merge

php artisan migrate:generate
[Doctrine\DBAL\DBALException]
Unknown database type json requested, Doctrine\DBAL\Platforms\MySqlPlatform may not support it.
Didn`t support type json ,my database is mysql version >=5.7

php artisan migrate:generate
[Doctrine\DBAL\DBALException]
Unknown database type json requested, Doctrine\DBAL\Platforms\MySqlPlatform may not support it.
Didn`t support type json ,my database is mysql version >=5.7

php artisan migrate:generate
[Doctrine\DBAL\DBALException]
Unknown database type json requested, Doctrine\DBAL\Platforms\MySqlPlatform may not support it.
Didn`t support type json ,my database is mysql version >=5.7

This doesn't seem to be related to Lumen though, but rather with Doctrine's support for the new MySQL JSON Types. Best to open a issue on Doctrine's repo.

Any update?

I'm sure it would be possible. Seems like there might be one or two changes one might have to make. Let me know if you run into any problems.

Got it working in a Lumen (5.4.6) (Laravel Components 5.4.*) Application.
Basically, Lumen is missing a few core methods that we are copy-pasting back from Laravel.
// bootstrap/app.php

/*
|--------------------------------------------------------------------------
| Create The Application
|--------------------------------------------------------------------------
|
| Here we will load the environment and create the application instance
| that serves as the central piece of this framework. We'll use this
| application as an "IoC" container and router for this framework.
|
*/
class Application extends Laravel\Lumen\Application
{
    /**
     * Get the path to the application configuration files.
     *
     * @param string $path Optionally, a path to append to the config path
     * @return string
     */
    public function configPath($path = '')
    {
        return $this->basePath.DIRECTORY_SEPARATOR.'config'.($path ? DIRECTORY_SEPARATOR.$path : $path);
    }
}

if (!function_exists('config_path')) {
    /**
     * Get the configuration path.
     *
     * @param  string $path
     * @return string
     */
    function config_path($path = '')
    {
        return app()->basePath() . '/config' . ($path ? '/' . $path : $path);
    }
}

if (!function_exists('app_path')) {
    /**
     * Get the path to the application folder.
     *
     * @param  string $path
     * @return string
     */
    function app_path($path = '')
    {
        return app('path') . ($path ? DIRECTORY_SEPARATOR . $path : $path);
    }
}

class_alias('Illuminate\Support\Facades\Config', 'Config');

$app = new Application(
    realpath(__DIR__.'/../')
);

// $app->withFacades();

 $app->withEloquent();

Now running artisan migrate:generate should work as expected in Lumen.
@nasrulhazim @Xethron Hope this helps!


Texlive issue

My students have been using JuliaBox for AA228, but it appears that something happened with the packages included on texlive. We used to be able to do this:
using BayesNets
test = BayesNet([:A, :B])
test

but now it errors with "LaTeX Error: File `xunicode.sty' not found." I believe this can be fixed by ensuring that xunicode is included. You can add it using "tlmgr install xunicode", but my students aren't able to do this themselves:
juser@juliabox:~$ tlmgr install xunicode
You don't have permission to change the installation in any way,
specifically, the directory /usr/local/texlive/2014/tlpkg/ is not writable.
Please run this program as administrator, or contact your local admin.
tlmgr: An error has occurred. See above messages. Exiting.

Is this something that can be fixed?

It was working just fine back when #113 was resolved.

Thanks for pointing it out.
Is this something that can be installed with tlmgr usermode?
If not, I suppose the texlive.profile used in image creation needs to be updated. I'm hoping to release a new image this weekend, and will include this change.

Thanks! I got it working with this:
juser@juliabox:~$ tlmgr init-usertree
tlmgr: action init-usertree returned a warning.
juser@juliabox:~$ tlmgr --usermode install xunicode
tlmgr: package repository http://mirror.utexas.edu/ctan/systems/texlive/tlnet
[1/1, ??:??/??:??] install: xunicode [26k]
tlmgr: package log updated: /home/juser/texmf/web2c/tlmgr.log
running mktexlsr ...
done running mktexlsr.

It might be good if xunicode could be included in the image to reduce the steps required by students to get this going.

We should be able to do that.

fixed via https://github.com/tanmaykm/JuliaDockerImages/commit/9a84d5d7cffc4135e9c635844cec1df854c66e70


MudMenu: Introduce OnClickHandlerAsync to fix #6645

Description
Resolved issue #6645 by introducing a new API, OnClickHandlerAsync, which properly awaits OnClick.InvokeAsync to show exceptions.
There are still some concerns with SelectedItem and SelectedValue as they call methods that should be awaited. We should avoid overriding the Parameters getter and setters and look for an alternative solution.
Additionally, to catch the MudMenuItem exception, it's necessary to have the MudPopoverProvider inside the ErrorBoundary since the MudPopoverProvider renders the list popover which is a significant disadvantage.
How Has This Been Tested?
new unit test + visual check on https://try.mudblazor.com/snippet/GOwnkebdRgyviedF
Types of changes

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

Checklist:

[x] The PR is submitted to the correct branch (dev).
[x] My code follows the code style of this project.
[x] I've added relevant tests.

To be honest @ScarletKuro, I think we really need the global exception handler in MudBlazor I mentioned earlier. Because I think here a .AndForget() is a good solution. WPF has this also, a UnhandledDispatcherException event that you can subscribe to get all events that were handled by unawaitable async logic.

WPF has this also, a UnhandledDispatcherException event that you can subscribe to get all events that were handled by unawaitable async logic.

I don't agree.
Using UnhandledDispatcherException as the sole means of handling exceptions in a WPF application is not recommended. This approach only catches exceptions that were not handled on a background UI/worker thread and is intended as a last resort to prevent the application from crashing and later investigate the problem via logs. In fact, you will not find a single built-in WPF component that relies on subscribing to UnhandledDispatcherException. Nowadays, I haven't seen this practice in WPF much either. Most modern MVVM / Reactive frameworks have an async wrapper ICommand that can be awaited and if you don't want to handle the error on UI thread there is options not to opt-in for it.

Because I think here a .AndForget() is a good solution

Could you please provide more details on this? It seems that both the community and our team have already identified and fixed several instances where an awaited task was missing. Whether a task is long-running or not does not really matter. In any case, the menu is closed before the task is executed, so even if the task takes hours to complete, it does not impact the user experience. By properly awaiting the task, the UI thread can continue processing, which prevents it from freezing. However, if we were to use .GetAwaiter().GetResult() (which is not possible in Blazor), it would cause the UI thread to freeze until the task is completed.

In the aspnetcore repository, there are similar issues where Microsoft advises against using the fire-and-forget pattern. If it is used, there should be a mechanism to bubble up exceptions from such methods (e.g. .AndForget()). Unfortunately, we don't have any of these mechanisms, and it would take considerable effort to implement them properly. Therefore, I suggest that we begin by making the errors observable, as this PR does. Afterward, we can consider how to provide both options.

Of course you would handle exceptions if you can in WPF, the handler is for observing those you forgot to handle. We may be talking about different things entirely. I was talking about this line:
_ = SetSelectedValueAsync(value, force: true);  ... here the task is discarded.

In the aspnetcore repository, there are similar issues where Microsoft advises against using the fire-and-forget pattern. If it is used, there should be a mechanism to bubble up exceptions from such methods (e.g. .AndForget()). Unfortunately, we don't have any of these mechanisms, and it would take considerable effort to implement them properly. Therefore, I suggest that we begin by making the errors observable, as this PR does. Afterward, we can consider how to provide both options.

Sure, you are of course right. I think I misread the intention of this PR.

_ = SetSelectedValueAsync(value, force: true); ... here the task is discarded.

OK, for everyone's information we established in our discussion on the team that we should never discard tasks as this swallows exceptions silently. I am working on a PR that will introduce a global exception handler for all exceptions caught in .AndForget().

Updated PR

Thanks a lot!


add logseq-AISearch plugin

Submit a new Plugin to Marketplace
Plugin Github repo URL: https://github.com/chiimagnus/logseq-AIsearch
Github releases checklist

[x] a legal package.json file.
[x] a valid CI workflow build action for Github releases. (theme plugin for this).
[x] a release which includes a release zip pkg from a successful build.
[x] a clear README file, ideally with an image or gif showcase. (For more friendly to users, it is recommended to have English version description).
[x] a license in the LICENSE file.

EN：I am just a noob currently, could I delete the forked repo ?
ZH：我目前还是个新手，不知道能不能删除从logseq/marketplace fork过来的项目？


Plugin alive?

This plugin is deprecated?

The plugin is only updated as needed for compatibility fixes, otherwise it's active. Currently a new version with support for product variants is in the works though.


Remove embedding_dim parameter in ImageEmbedder examples

What does this PR do?
What

Removed embedding_dim parameter in the ImageEmbedder README example
Removed embedding_dim parameter in the ImageEmbedder code example
Searched for all other references to embedding_dim usgae -- Only other one is in a unit test, which should stay

Why

Reference: #653
According to code warning, embedding_dim should only be used if the user fine-tunes after. That is not done in these examples, and probably shouldn't anyway since that's a bit out of scope for the simple example.

Fixes # (issue)
Before submitting

[x] Was this discussed/approved via a Github issue? (no need for typos and docs improvements) -- #653
[x] Did you read the contributor guideline, Pull Request section?
[x] Did you make sure your PR does only one thing, instead of bundling different changes together?
[x] Did you make sure to update the documentation with your changes?
[ ] Did you write any new necessary tests? [not needed for typos/docs]
[ ] Did you verify new and existing tests pass locally with your changes?
[ ] If you made a notable change (that affects users), did you update the CHANGELOG?

PR review

[x] Is this pull request ready for review? (if not, please submit in draft mode)

Anyone in the community is free to review the PR once the tests have passed.
If we didn't discuss your PR in Github issues there's a high chance it will not be merged.
Did you have fun?
Make sure you had fun coding 🙃

Uh oh. I now realize that you may need to flatten that embedding for that resnet example. Because IIRC, resnet returns a 2048x7x7 output. Will put into draft mode for now, and take it out of draft when ready with a test result.

I found a potential error. If you run without embedding_dim assigned, it takes the last layer of the backbone. That's not always flattened. For example, in Resnet101, it's 2048x7x7. That's not compatible with embedding applications without flattening.
I'll close this PR for now and discuss this in a separate issue.

Discussion migrated to:
https://github.com/PyTorchLightning/lightning-flash/issues/656


Add "back to top" link at the end of every section.

With the table of contents, you can easily search for what you're looking for. You can also use the alt/⌘ + left arrow to go back to the previous section and search using the word search ctrl + f.
This is a good method, but I tried going to the table of contents again and I had to use the scrollbar. It's not a big deal using it, but since you have the cursor hovering over the list, you have to move the cursor to the scrollbar and then drag it to the top.
It will be easier if you had a "Back to top" button at the end of each section (just the sections, not sub-sections).
The button could be something like ⬆ back to top, linking to the table of contents (Contents).
This is a minimum recommendation and it doesn't affect reality, but it's just a recommendation I think it could be better in my opinion, while I was navigating through the list.

The list grew a lot since its onset, it does makes sense to have this navigational option. I'll be working on this 🙂

Ok
Em sáb, 4 de jul de 2020 19:25, Mahadi Xion<EMAIL_ADDRESS>escreveu:

The list grew a lot since its onset, it does makes sense to have this
navigational option. I'll be working on this 🙂
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/mhxion/awesome-discord-communities/issues/17#issuecomment-653818763,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AOJBT7TIRY5P2MB2CWYDZ3DRZ6T4RANCNFSM4OQPAALA
.

Hi! is someone working on this? i wouldn't mind doing it

Hi! is someone working on this? i wouldn't mind doing it

Hello @dkaiser014. I think no one is working on this, so it'd be a nice contribution. Though let's wait for mhxion to decide whether to do it or not (as I see this issue was added to the milestone "Smooth Exploration").

Hello @dkaiser014. I think no one is working on this, so it'd be a nice contribution. Though let's wait for mhxion to decide whether to do it or not (as I see this issue was added to the milestone "Smooth Exploration").

@dkaiser014 Hello, thanks for your interest. I'll start working on it soon, I'll likely adopt the navigation style from best-of, I like their simple ^ icon. I have got a few more communities to wrap up. If you still want to work on it, feel free to do so, you can show your navigation styles by opening up a draft PR, and we can discuss there.

@dkaiser014 Hello, thanks for your interest. I'll start working on it soon, I'll likely adopt the navigation style from best-of, I like their simple ^ icon. I have got a few more communities to wrap up. If you still want to work on it, feel free to do so, you can show your navigation styles by opening up a draft PR, and we can discuss there.

I checked out the navigation style from best-of and it's pretty clean, I like it, I'll open a PR asap, thanks :smile:

I checked out the navigation style from best-of and it's pretty clean, I like it, I'll open a PR asap, thanks :smile:


A few issues

Non-docker! Just copied the PHP files and went.
If you're on signup.php , and you click the "TOS" (should be ToS I believe) -> it redirects back to login.php, making the ToS unreadable.
(I know "The page you are looking for does not exist. " even when you're able to access the ToS but still, just saying)
On signout, PHP message: PHP Warning:  Undefined array key "redirect" in Uploady/logout.php on line 9
Also "Could not instantiate mail function. " on signup (i don't have emailing setup) but the point is, that is Not something that should be public facing. That's something that should be shown to an admin, not a member of the public trying to sign up. No logged error occurred so I would not have known of the issue if I didn't test it
Then after not verifying email and signing in, trying to upload an image, error.
PHP Warning:  fopen(/REDACTED.jpg):
Failed to open stream: Permission denied in Uploady/vendor/farisc0de/phpfileuploading/src/Upload.php on line 748
PHP Fatal error:  Uncaught TypeError: stream_set_timeout():
Argument #1 ($stream) must be of type resource, false given in Uploady/vendor/farisc0de/phpfileuploading/src/Upload.php:751

fopen is trying to upload to the root directory .. ? /img.jpg , an absolute path, instead of the relative Uploady directory, or more specifically inside the uploads folder?
Line 748: $fp = fopen($this->upload_folder['folder_path'] . "/" . $filename, 'w');
configuration: define("UPLOAD_FOLDER", "uploads");
Maybe my configuration is to blame because it isnt /var/www/blah/blah/uploads , but still the Uploads.php file acted like this variable $this->upload_folder['folder_path'] was completely empty
Thanks for your time and effort! I'm really enjoying what you've created, if I have time I may try and contribute.

Thank you so much for reporting this, for the first part I fixed the issue in the last commit, the terms page was not whitelisted.
I am looking into the second part as it is a weird behavior and should not happen.

Thank you so much for reporting this, for the first part I fixed the issue in the last commit, the terms page was not whitelisted.
I am looking into the second part as it is a weird behavior and should not happen.

Awesome! I'll have to try it out again, and yeah I may be able to spend some time to find out why as well but recently my heads been in another project

For the second part can try to deploy using the steps in this video, and let me know what happens:
https://youtu.be/NTtFekrDna4

Yeah, this issue is fixed.
Sidenote:
I tried to install Uploady, using the latest version on github and ran into this error(on install.php) when improper mysql user/password was set I ran into this error
PHP Fatal error:  Uncaught Error: Call to a member function prepare() on null in Uploady/src/Uploady/Database.php:121
Is this a big deal? No, not really. But a check , to return a error message instead of a PHP fatal error is ideal! E.g. when a bad username/password , tell us as such "Bad user/pass!" or "No database exists!" etc etc!

Thats a good idea, I might Implement an error handler to change this message.


Adding HCA Galaxy Instance to list of Analysis Portals

Hey @NoopDog. Added you as a reviewer. Feel free to add other reviewers as you see fit.

Hey @NoopDog , any comments on the results of the 'Codacy/PR Quality Review'? The failures don't really make sense to me. I followed the format of the other files in the same directory. I'm also not familiar with some of the terms (e.g. 'setext').
Can you provide examples of how I might resolve these issues?
Should I also be adding someone else as a reviewer or assignee?
Thanks!

Will take a look @matthewspeir

Hi @matthewspeir, I reviewed the Codacy failures from your PR and have created a ticket to update the default Codacy settings (#570).
Specifically:

Front matter should be excluded from certain Codacy checks.
Header formatting should default to atx, not setext.

Thanks! I appreciate it.


Load stored cursors

After entities preloaded (see #190) we will load stored cursors (see Cursor.schema) and link preloaded entities to cursor datasets. Cursors can contain entities loaded to other nodes/processes so we will load their immutable copies (and set special flag).

Note: Cursors should be attached to certain node/process.
TODO: add special field to Cursor.schema


Change visibilty from private to protected so

client can be extended

@mikefox so i guess in that case you can just put final before class declaration because class is no extendable in any way because apiClient is private


feat: test forked contributor PR

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


Opera: spinning loading indicator

Using Socket.IO 0.8.6.
Opera/9.80 (Windows NT 6.1; U; en) Presto/2.8.131 Version/11.10
(Opera 11.10 on Windows 7) falls back to jsonp-polling and triggers the never-ending loading indicator.
Plus, the socket seems to die after initial connection.
My chat application will populate the user list but wont send out any messages.
FlashSocket also fails to connect on Opera 11.10 with Flash 11 installed.

Having the same issue with Opera, Socket will initially open connection and construct a history. However send events fail to fire from the client side.
The page appears to be continuously loading...

I have the same issue in Opera.
It's because currently sio use jsonp for Opera, even when you host it on the subdomain of your main site. This can be fixed for subdomain, but require adding messaging between sio and main-site context for Opera. Other browsers doesn't require such behavior for cross-domain in one subdomain space.

I mean, to fix this issue, instead of jsonp, should be used cross-subdomain AJAX. But in Opera it requires additional tricks with document/window.postMessage

Still having this issue, on 0.8.7... can somebody come up with a patch? Needing it :(


Write a doc that explains that PandA is both a detector and a trigger generator

The construction of PandA in here is cause of confusion, a document to explain our choices, the outcomes and how to use what is there would be very beneficial.

Bumping this from 1.0 as I think the flyscanning parts will not be ready and will change soon after


Add wantsApp flag for filling apps but not enforce presence.

I want to be able to have ctx.app in the plugins but not enforcing its presence.
I have actions that may or may not require an app.
Is there a different way to do that?

I definitely like this more than just making it optional all the time. I'm curious if @markpundsack has any thoughts on this since he wanted similar functionality

hrm. Thinking about it a bit more, I think this would be better done by just adding a flag instead of this, such as how it is done here: https://github.com/heroku/heroku-git/blob/master/commands/git/remote.js
the reason is because it would look to the user very strange if a command acted differently based on the directory you were in. I think it's better to optionally be able to set the app name via a flag, but not to allow it to be inferred. For commands where the app name is required, this is okay since the command simply won't work without being able to infer the app.

I liked the idea of inferred but not mandatory. But I could understand this. I made it a flag for now.

Couple of points. If you add -a, you should consider adding -r as well, since a lot of people use --remote production or equivalent to refer to their apps. One nice thing about wantsApp could be that it abstracts that away from the plugin writer. Otherwise it's quite likely the plugin writer will forget and lead to inconsistent UX. The git plugin can do it because it's actually creating the remote as part of the command. Likewise, assuming there's no existing remote, inferred apps aren't an issue.
To Jeff's point, it can be confusing if someone leaves out the -a intentionally, but happens to be in a directory that has an app and gets the wrong result. For this reason, I've re-written my plugin to have separate commands, with and without apps. It makes the namespace a little more complicate but I expect it will lead to more consistent UX.
Side note, but I don't like when help includes -a for some commands and not others. If you've got needsApp: true perhaps we should include -a and -r as options in the help. This would have the side effect of documenting -r as a feature.
For example, the default help output is:
Usage: heroku pipelines:create [NAME]

   -s, --stage STAGE   # stage of first app in pipeline

But in reality, the syntax is more like:
Usage: heroku pipelines:create (--app APP | --remote REMOTE) [--stage STAGE] [NAME]

   -a, --app APP   # the Heroku app to use
   -r, --remote REMOTE   # the git remote of the Heroku app to use
   -s, --stage STAGE   # stage of first app in pipeline

yeah Mark nailed it there. I'm not sure what you're commands look like @ys but for this: https://github.com/heroku/heroku-event-log we decided it made sense to actually have different commands for using it with the app context and a global context. And yes, we need to add that to the help. I created #46 to track.

I have a command that can take an app for scoping more the output.
I wanted to use the git remote but won't then and require the -a flag if needed.
It is a special case as those are not the usual heroku apps.
Let's close this and assume developpers needs app or not for now and review in the future.

reopening since this came up for a use-case @bjeanes mentioned


Remove curly braces from proto rpcs

This is the most common syntax for declaring proto rpcs

One sec, a new proto file to update...


[Chapter 3] Pandas datatype

In chapter 3 on page 86 (also in the github repo MNIST), one has code
from sklearn.datasets import fetch_openml
mnist = fetch_openml('mnist_784', version=1)
X, y = mnist["data"], mnist["target"]

This works well but the next step, namely
some_digit  = X[0]
Throws an error
>>> some_digit = X[0]
Traceback (most recent call last):
  File "/home/<user>/.local/lib/python3.8/site-packages/pandas/core/indexes/base.py", line 3080, in get_loc
    return self._engine.get_loc(casted_key)
  File "pandas/_libs/index.pyx", line 70, in pandas._libs.index.IndexEngine.get_loc
  File "pandas/_libs/index.pyx", line 101, in pandas._libs.index.IndexEngine.get_loc
  File "pandas/_libs/hashtable_class_helper.pxi", line 4554, in pandas._libs.hashtable.PyObjectHashTable.get_item
  File "pandas/_libs/hashtable_class_helper.pxi", line 4562, in pandas._libs.hashtable.PyObjectHashTable.get_item
KeyError: 0

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/home/<user>/.local/lib/python3.8/site-packages/pandas/core/frame.py", line 3024, in __getitem__
    indexer = self.columns.get_loc(key)
  File "/home/<user>/.local/lib/python3.8/site-packages/pandas/core/indexes/base.py", line 3082, in get_loc
    raise KeyError(key) from err
KeyError: 0

Having up to date python, and the packages involved I was super confused why this is the case. I realised i can remedy this by instead setting
some_digit = X.values[0,:]

This turns it into array sure, I have to reshape it right after anyway so its fine. The reason I am writing this is because i then executed the same code that failed for me on google colab and there it just works, any idea what could be causing this ?
Thank you

I had the same problem. I found out that it depends on the version of scikit-learn. fetch_openml has an optional argument as_frame which used to default to False, making the function return a Numpy array. However, since scikit-learn version 0.24, the default value for as_frame is 'auto'.
(Source)

I had the same problem. I found out that it depends on the version of scikit-learn. fetch_openml has an optional argument as_frame which used to default to False, making the function return a Numpy array. However, since scikit-learn version 0.24, the default value for as_frame is 'auto'.
(Source)

Yes ! You got it, thank you !!

In chapter 3 on page 86 (also in the github repo MNIST), one has code
from sklearn.datasets import fetch_openml
mnist = fetch_openml('mnist_784', version=1)
X, y = mnist["data"], mnist["target"]

This works well but the next step, namely some_digit = X[0] Throws an error
>>> some_digit = X[0]
Traceback (most recent call last):
  File "/home/<user>/.local/lib/python3.8/site-packages/pandas/core/indexes/base.py", line 3080, in get_loc
    return self._engine.get_loc(casted_key)
  File "pandas/_libs/index.pyx", line 70, in pandas._libs.index.IndexEngine.get_loc
  File "pandas/_libs/index.pyx", line 101, in pandas._libs.index.IndexEngine.get_loc
  File "pandas/_libs/hashtable_class_helper.pxi", line 4554, in pandas._libs.hashtable.PyObjectHashTable.get_item
  File "pandas/_libs/hashtable_class_helper.pxi", line 4562, in pandas._libs.hashtable.PyObjectHashTable.get_item
KeyError: 0

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/home/<user>/.local/lib/python3.8/site-packages/pandas/core/frame.py", line 3024, in __getitem__
    indexer = self.columns.get_loc(key)
  File "/home/<user>/.local/lib/python3.8/site-packages/pandas/core/indexes/base.py", line 3082, in get_loc
    raise KeyError(key) from err
KeyError: 0

Having up to date python, and the packages involved I was super confused why this is the case. I realised i can remedy this by instead setting
some_digit = X.values[0,:]

This turns it into array sure, I have to reshape it right after anyway so its fine. The reason I am writing this is because i then executed the same code that failed for me on google colab and there it just works, any idea what could be causing this ?
Thank you

thanks this solved my headache


Reload older Graphs

Hi! I am not sure, if it is the correct treat…
Following problem occurs: I am not able to reload any older graphs, which I have safed on my device (in the demo as in the beta version). The screen shows my "Nothing to Display yet!"

@PatrickSchre could you send me an example to<EMAIL_ADDRESS>


mkDerivation version from VERSION file appends a dash (-) to derivation path

Describe the bug
Setting the value of version field of mkDerivation by reading from a file using builtins.readFile results with the derivation path appended with -.
Steps To Reproduce
Create a short derivation:
der = pkgs.stdenv.mkDerivation rec {
  pname = "der";
  # version = "v1.0";
  version = builtins.readFile ./VERSION;

  src = ./.;

  installPhase = ''
    echo -n "${pname}-${version}" >> $out
  '';
};

And a VERSION file:
v1.0

Run nix build && readlink result
I have tested with following permutations of the version string for both the file and the string literal:

v1.0
v1.0.0
1.0
1.0.0
1
v1

Expected behavior
The path link should be the same if I use the version = "v1.0" or the readFile method.
Screenshots
Result file path when running version of string literal:
/nix/store/q0bf4laaf3j35znz1cyilf9xgqvr5pv0-der-v1.0
/nix/store/zgbxywn1ads6p9nqrcr54allpb2qj630-der-1.0
/nix/store/sr0hzmgjkqibrp10dlbd8dwbwrzq0v62-der-1.0.0
/nix/store/hf7y1cfix21ls6dya1l2s0a73mpc2q2c-der-v1.0.0
/nix/store/ai1w3n50xnv27rw3pppq3vzq30k1yqs2-der-v1
/nix/store/140nckimbd27ap4byapi8pq56msjfngn-der-1

Result file path when running version from file:
/nix/store/0hzdfdyjq2vj7xx1x3q5n00h7d2w0zhs-der-v1.0-
/nix/store/sf72iyfqxqim8knkmgdmraxn5g9scba4-der-1.0-
/nix/store/l5lcg4jkv145gz2wlnjw423pg2mi48yi-der-1.0.0-
/nix/store/zvn5v2lc2bzz7yfn1h9s3gxijwj6ad67-der-v1.0.0-
/nix/store/ghqs7sn6wryfxd354nbv8gs281kd1lsg-der-v1-
/nix/store/q9knabik58a66bgiqfj7xbmqs1f6y1yc-der-1-

Additional context
Notify maintainers
Metadata
[user@system:~]$ nix-shell -p nix-info --run "nix-info -m"
 - system: `"x86_64-linux"`
 - host os: `Linux 6.5.3, NixOS, 23.05 (Stoat), 23.05.20230917.5d017a8`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.17.0`
 - channels(matej): `"nixpkgs"`
 - nixpkgs: `/home/matej/.nix-defexpr/channels/nixpkgs`

Is it possible that the file contains a newline that gets replaced with a dash during sanitization?

Is it possible that the VERSION file contains a newline that gets replaced with a dash during sanitization?

Yes, I did not think of that, since I used echo -n "v1.0" > VERSION to create the file. From then I used my editor to modify and test the file.
Using cat -A VERSION when creating the file I get:
v1.0%

And when just saving it in my editor (nvim) I get:
v1.0$

So nvim in my configuration adds line feed (LF) character when saved, so it does not show as an extra line. I guess that is what gets converted to -.

Thanks for the info, looks like lib.fileContents is just the function I was looking for (interesting that the example matches as well). Therefore the readFile works as intended. I will be closing this issue.


Add Numeric Patterns | Python

All Code Files Have Been Successfully Added

All Code Files Have Been Successfully Added


Rancher Server High Availability Update

I tried rancher half a year ago and immediately fell in love with what rancher was and where it was heading. Fast forward to today and I was hoping on a little more progress on the high availability setup.
I have read the existing guide you have on: http://docs.rancher.com/rancher/installing-rancher/installing-server/multi-nodes/
And besides the setup work (I don't really mind), this just externalises safety concerns to a self run MYSQL, Redis, Zookeeper environment. unless you manually maintain a HA cluster of each of those yourself.
A way nicer solution would be to run these as containers on each of the Rancher servers. Making them all aware of each other and with constant replication/mirroring.

Gimme a week, you'll get your wish :)

@5an1ty I'll update this issue when we publish our new HA setup, but we fully managed everything except the DB.  I'm sure we'll manage the DB too eventually, but just not right now.

@ibuildthecloud amazing! Seriously, I'm so ready to start using Rancher in production!
Have you given any consideration to other DB software btw? I'm thinking RethinkDB or Cassandra, something with HA concerns built in.
I'm wondering, could I set up two RancherOS servers both running rancher server. And run some kind of HA mysql setup on the both of them as docker images?
On a side note, SSL support for the rancher servers is on the way as well right?
I've been hyped about rancher for so long, I just can't wait :smile:!

+1 for the picture

@ibuildthecloud looking forward to the new release as we are trying to migrate from Docker Cloud.
Is there an ETA? :+1:

End of the month.

@ibuildthecloud any documentation on the new HA setup?  I was just going through the steps on the site until I saw this post. :)

We'll actually have it out with our v1.0.1 release. Stay tuned!

@deniseschannon Sure about that? When will be the v1.0.1 release?

@cuiyz Today's Rancher meetup covers HA and so this will definitely be in v1.0.1. We're hoping to push out 1.0.1 in the next week.

@deniseschannon if you could also let us know when http://docs.rancher.com/rancher/installing-rancher/installing-server/multi-nodes/ is fully updated for HA, most appreciated!

I have gone through the video https://www.youtube.com/watch?v=hwhxXwT6zlw, looks great.
I am also waiting for the latest released v1.0.1.
By the way, if I try to build latest rancher/server image  by myself, any instructions for it?

Tests pass in v1.0.1-rc5, thanks @ibuildthecloud !

@flaccid @SydOps As soon as v1.0.1 ships, the docs link will be updated. If you follow our announcements category in our Forums, you will receive a note about the latest release and the link to the docs will be in those release notes. If you really can't wait, you can look at my docs PR

I'm all subscribed up :) thanks again, we are just very eager on this one!

Are there any plans/is it technically possible to have the HA mysql-server and load-balancer within the rancher cluster/nodes/hosts?
Right now we are using rancher to manage all of our containers and when we deploy a repplicated database, we do so within rancher. The requirement to have the mysql-database outsite of rancher feels a little bit odd to me :)

@GameScripting This is definitely on the radar and possible, we would like Rancher to orchestrate it's own HA database within the System Stack.
I don't think it is officially on the roadmap. Could you open a new issue to further discuss (we don't actively monitor closed issues)?

Any progress with this? Is there any chance that rancher's mysql will become part of the rancher installer, ie - if i don't already have an existing MySQL cluster that it would help me spin up a mysql galera cluster, or at least some good instructions / installer script on how to do it properly for best rancher's operation?
as of right now i can see it achievable this way only:

install mysql server
install rancher with external mysql support
from rancher - install mysql gallera cluster
stop rancher server
copy db from standalone mysql ( installed in step.1 ) to galera cluster
remove rancher
re-install rancher with new cattle connection string for mysql cluster
follow High Availability menu to generate installer scripts that will be then deployed on additional nodes

is there a better / easier / more correct / more reliable way of getting this done on a new cluster deployment?
Thank you.


PopulateMap conflicts with FindOptions parameter

Describe the bug
The line:
https://github.com/mikro-orm/mikro-orm/blob/master/packages/core/src/entity/EntityRepository.ts#L41
... conflicts with:
https://github.com/mikro-orm/mikro-orm/blob/master/packages/core/src/EntityManager.ts#L89
... as you can also set an object (PopulateMap) as populate as well:
https://github.com/mikro-orm/mikro-orm/blob/master/packages/core/src/typings.ts#L261 -> https://github.com/mikro-orm/mikro-orm/blob/master/packages/core/src/typings.ts#L259.
Therefore you can cause some confusion as it doesn't populate anything because it thinks it is an options object. The workaround is to wrap the populate in an options object: find({ ...where... }, { populate: { ...populatemap... }}).
I can only come up with these (non-)fixes:

possible breaking change: remove an overload? Or: remove the PopulateMap (which I like: type safety!)?
ugly code by adding a check whether the object contains the key populate and/or orderBy (breaks entities that have a  property with these names).

Stack trace
...

To Reproduce
See above.
Expected behavior
The find methods should determine the type of argument properly.
Additional context
All find options with the overload P | Find*Options<T, P> have this issue.
Versions

Dependency
Version

mikro-orm
4.0.7

So what exactly is wrong? I don't see any example or stack trace or something, which makes the report quite cryptic :D

The workaround is to wrap the populate in an options object: find({ ...where... }, { populate: { ...populatemap... }}).

That is not a workaround, this is intended usage.

You can use find like this:
find({...where...}, ["prop1", "prop2"]) but typing also allows you to use find({...where...}, {prop1: true, prop2: true}). And the line https://github.com/mikro-orm/mikro-orm/blob/master/packages/core/src/EntityManager.ts#L89 checks if the second argument is an object and then assumes that it is an FindOptions object while it is an PopulateMap object.

Again, this is intended, you cannot use PopulateMap directly like this, you need to wrap it in FindOptions. And I don't think there is a way around this - the typings are already too complex, I don't plan to do additional BCs now, and doing the key check is fragile.


Thumbnails: Carbon Svelte & Angular

Description
Carbon react thumbnails needed to close PR #659
Storybook:  https://carbon-components-svelte.onrender.com/components/

[x] breakpoint
[x] button-set
[x] clickable-tile
[x] composed-modal
[x] context-menu
[x] expandable-tile
[x] fluid form(should I just use the form svg again?)
[x] image-loader
[x] inline-notification
[x] local-storage
[x] ordered-list
[x] password-input
[x] recursive-list
[x] selectable-tile
[x] skeleton-placeholder
[x] skeleton-text
[x] toast-notification
[x] tooltip-icon
[x] truncate
[x] unordered-list

Carbon react thumbnails needed to close PR #667
Storybook:  https://carbon-components-svelte.onrender.com/components/

[x] tooltip-icon
[x] icon
[x] input
[x] list
[x] radio
[x] table
[x] time-picker-select
[x] context-menu

Hey team! Please add your planning poker estimate with ZenHub @aubrey-oneal @kingtraceyj

@andreancardona
In some cases I made new thumbnail illustrations but in some cases I reused the react ones here. Even if I resused them they're still saved here in this zipped folder.
For Angular time picker select, there seems to be no difference between time picker and time picker select... in fact, the Angluar time picker looks broken. So we're using the same thumbnail illustrations for time-picker and time-picker select... also the same illustration we're using in React.
thumbs.zip


Clarify link to the 'profile' feature

I noticed that this seemed a little unclear when reading the release notes for 2.13.

Close this?

@pmorie closing but feel free to reopen if you want this changed


Wrong color on inverted teal button

Light colors are different from dark colors. Check the css variables. This is for legibility and not a bug


Update FTS checks

Nice, should we make this update for all of the impersonation rules?

i think so yeah


Java error causing MC to crash: A fatal error has been detected by the Java.

MC keeps crashing and complaining about heap dump problems or something.
hs_err_pid4308.log

Thank you for the report!
Please submit this issue over at the Mojang bug tracker. Please search for existing reports first; in case you do not find any, create a new report and let us know about the issue number here (e.g. MC-123456). The Mojang team will take the first look. If an OpenJDK bug is identified, the Mojang team will contact the Microsoft Build of OpenJDK team to address the issue.


@testitem does not run

Followup from: https://discourse.julialang.org/t/prerelease-of-new-testing-framework-and-test-run-ui-in-vs-code/86355/10?u=lmiq
The “play” button not doing anything in this package, which is only the template plus the tests: GitHub - lmiq/TestTests.jl
I’m on Linux Mint 21 x86 - with Julia 1.8.0.
There is no output at all, as the figure above shows, the spinning stuff just keeps spinning.
There is nothing particular about the Julia extension configuration (I think I didn't change anything).

To try to reproduce the problem, do:
git clone https://github.com/lmiq/TestTests.jl
cd TestTests.jl
code .

VSCode will open. Wait for the tests to appear at the Erlenmeyer tab, and click play.

I see the same thing.

Hm, so it all works on my Windows system with this repo... So we'll have to dig a bit :)
Here are some ideas:

Could you package the entire folder as it is locally on your hard drive and share? In particular, is there a Manifest.toml in the package root folder? I see in your status bar that the project TestTests.jl is active, how did you activate that?
Do you have anything configured for Julia: Executable Path? If yes, could you share it?
How is Julia installed, and in particular how did you put julia on the PATH on your system?

My best guess is that something goes haywire when the extension tries to start the test process already, i.e. maybe it doesn't even ever start, or something like that. At least in theory, that output panel you can open with that button should just show all and every output from the test process, so the fact that it doesn't show anything makes me think that we somehow fail to launch it already...
If either of you has the ability to run the entire Julia extension under the debugger, I could also give you some more pointers on things to check.

Ah, another question: do you have a startup.jl?

Ah, and I totally forgot: there is also an output channel for the test stuff that might show more. I doubt it, but you could check. Ctrl+Shift+U, and then there should be one called "Julia Testserver".

Could you package the entire folder as it is locally on your hard drive and share? In particular, is there a Manifest.toml in the package root folder? I see in your status bar that the project TestTests.jl is active, how did you activate that?

I can reproduce the error cloning the repo again from scratch, so that repo, in that sense, is complete to reproduce the problem.
The activation of the environment there happened after VSCode asked me to activate it, but I suspected of that and tried without activating it as well, and the result is the same.

Do you have anything configured for Julia: Executable Path? If yes, could you share it?

No, only julia, and it was installed with juliaup.
leandro@pitico:~% which julia
/home/leandro/.juliaup/bin/julia

And it is in the path by the default juliaup addition to .bashrc.

Ah, another question: do you have a startup.jl?

I have, but I removed it now and nothing changed.

Ctrl+Shift+U, and then there should be one called "Julia Testserver".

Not there. But in the
Log (Window) this appears:
[2022-08-27 17:45:11.104] [renderer1] [error] spawn julia ENOENT: Error: spawn julia ENOENT
    at Process.ChildProcess._handle.onexit (node:internal/child_process:282:19)
    at onErrorNT (node:internal/child_process:477:16)
    at processTicksAndRejections (node:internal/process/task_queues:83:21)

And this is the only error message that appears upon clicking on the Play button of the test.

Ah, that suggests that it is related to spawning Julia! So just to be double sure:

This whole output panel doesn't show up for you? Or is there just no content?

The panel is there, but not the content:

If either of you has the ability to run the entire Julia extension under the debugger,

If you need this, let me know, I won't be able to do it now, but during the week we can work on that.

If you need this, let me know

Thanks, much appreciated!
I'm prepping a new build of the extension that would send a crash report with more details if it can't spawn the test server. My hope is that that would have enough information in it that we don't have to go down that route. But if that doesn't work, I might come back to your offer :) I'll ping you here as soon as this new extension build is on the insider channel of the extension.

Ok, I've pushed an insider build out. @lmiq and @carstenbauer could you try to uninstall the regular extension and the install the Julia Insider one?
It should a) show a bit more output and errors and b) send crash reports that hopefully will help.

Here it goes what I get. First, what appears in the interface:

Now the messages in the Output panel of each section:
Nothing at: Tasks, Extensions, Julia Notebook Kernels, Julia Test Server, Julia Language Server Trace

Julia Language Server

Juliaup configuration is locked by another process, waiting for it to unlock.
  Activating project at `~/.vscode/extensions/julialang.language-julia-insider-1.7.7/scripts/environments/languageserver/v1.8`
[ Info: Starting the Julia Language Server
[ Info: Symbol server store is at '/home/leandro/.config/Code/User/globalStorage/julialang.language-julia-insider/symbolstorev5'.
[ Info: Starting LS at<PHONE_NUMBER>
[ Info: All cache files downloaded.
[ Info: Received new data from Julia Symbol Server.

Log (Edit sessions):
[2022-08-28 08:54:57.944] [editsessions] [info] Skipping registering edit sessions actions as edit sessions are currently disabled. Set workbench.experimental.editSessions.enabled to enable edit sessions.

Log (Window):
[2022-08-28 08:54:59.955] [renderer1] [error] [Extension Host] (node:505641) DeprecationWarning: uuidv4() is deprecated. Use v4() from the uuid module instead.
(Use `code --trace-deprecation ...` to show where the warning was created)

Log (Main)
[2022-08-28 08:54:56.838] [main] [info] update#setState idle
[2022-08-28 08:54:58.128] [main] [info] Starting extension host with pid 505641 (fork() took 11 ms).
[2022-08-28 08:55:26.850] [main] [info] update#setState checking for updates
[2022-08-28 08:55:27.086] [main] [info] update#setState idle

Log (Extension Host)
[2022-08-28 08:54:58.817] [exthost] [info] Extension host with pid 505641 started
[2022-08-28 08:54:58.817] [exthost] [info] Skipping acquiring lock for /home/leandro/.config/Code/User/workspaceStorage/a84d09ffe692b1fbd58e9fb9cc983ebd.
[2022-08-28 08:54:58.949] [exthost] [info] ExtensionService#_doActivateExtension vscode.microsoft-authentication, startup: false, activationEvent: 'onAuthenticationRequest:microsoft'
[2022-08-28 08:54:58.968] [exthost] [info] ExtensionService#_doActivateExtension vscode.debug-auto-launch, startup: true, activationEvent: '*'
[2022-08-28 08:54:58.971] [exthost] [info] ExtensionService#_doActivateExtension vscode.git-base, startup: true, activationEvent: '*', root cause: vscode.git
[2022-08-28 08:54:58.975] [exthost] [info] ExtensionService#_doActivateExtension vscode.ipynb, startup: true, activationEvent: '*'
[2022-08-28 08:54:58.995] [exthost] [info] ExtensionService#_doActivateExtension vscodevim.vim, startup: true, activationEvent: '*'
[2022-08-28 08:54:59.059] [exthost] [info] ExtensionService#_doActivateExtension julialang.language-julia-insider, startup: true, activationEvent: 'workspaceContains:Project.toml'
[2022-08-28 08:54:59.940] [exthost] [info] ExtensionService#_doActivateExtension vscode.git, startup: true, activationEvent: '*'
[2022-08-28 08:55:00.065] [exthost] [info] ExtensionService#_doActivateExtension vscode.github, startup: true, activationEvent: '*'
[2022-08-28 08:55:00.185] [exthost] [info] ExtensionService#_doActivateExtension vscode.github-authentication, startup: false, activationEvent: 'onAuthenticationRequest:github'
[2022-08-28 08:55:00.380] [exthost] [info] Eager extensions activated
[2022-08-28 08:55:00.399] [exthost] [info] ExtensionService#_doActivateExtension vscode.emmet, startup: false, activationEvent: 'onStartupFinished'
[2022-08-28 08:55:00.406] [exthost] [info] ExtensionService#_doActivateExtension vscode.merge-conflict, startup: false, activationEvent: 'onStartupFinished'

Log (Shared)
[2022-08-28 08:54:59.081] [sharedprocess] [info] Starting worker process with pid 505675 (type: fileWatcher, window: 1).
[2022-08-28 08:54:59.407] [sharedprocess] [info] Deleted from disk julialang.language-julia /home/leandro/.vscode/extensions/julialang.language-julia-1.7.6

Log (Settings sync)
[2022-08-28 08:54:58.244] [settingssync] [info] Using settings sync service https://vscode-sync.trafficmanager.net/
[2022-08-28 08:54:58.244] [settingssync] [info] Auto Sync is disabled.

When I cancel the test execution, this appears:

I get this when I click "Play" on the test after starting the debugger (maybe just an environment issue?)

Also got these errors after a restart of VSCode:
ERROR: LoadError: IOError: connect: no such file or directory (ENOENT)
Stacktrace:
 [1] wait_connected(x::Base.PipeEndpoint)
   @ Sockets ~/.julia/juliaup/julia-1.8.0+0.x64/share/julia/stdlib/v1.8/Sockets/src/Sockets.jl:529
 [2] connect
   @ ~/.julia/juliaup/julia-1.8.0+0.x64/share/julia/stdlib/v1.8/Sockets/src/Sockets.jl:564 [inlined]
 [3] connect
   @ ~/.julia/juliaup/julia-1.8.0+0.x64/share/julia/stdlib/v1.8/Sockets/src/PipeServer.jl:103 [inlined]
 [4] serve(args::String; is_dev::Bool, crashreporting_pipename::String)
   @ VSCodeServer ~/.vscode/extensions/julialang.language-julia-insider-1.7.7/scripts/packages/VSCodeServer/src/VSCodeServer.jl:110
 [5] top-level scope
   @ ~/.vscode/extensions/julialang.language-julia-insider-1.7.7/scripts/terminalserver/terminalserver.jl:39
in expression starting at /home/leandro/.vscode/extensions/julialang.language-julia-insider-1.7.7/scripts/terminalserver/terminalserver.jl:14
julia>
 *  History restored

ERROR: LoadError: IOError: connect: no such file or directory (ENOENT)
Stacktrace:
 [1] wait_connected(x::Base.PipeEndpoint)
   @ Sockets ~/.julia/juliaup/julia-1.8.0+0.x64/share/julia/stdlib/v1.8/Sockets/src/Sockets.jl:529
 [2] connect
   @ ~/.julia/juliaup/julia-1.8.0+0.x64/share/julia/stdlib/v1.8/Sockets/src/Sockets.jl:564 [inlined]
 [3] connect
   @ ~/.julia/juliaup/julia-1.8.0+0.x64/share/julia/stdlib/v1.8/Sockets/src/PipeServer.jl:103 [inlined]
 [4] serve(args::String; is_dev::Bool, crashreporting_pipename::String)
   @ VSCodeServer ~/.vscode/extensions/julialang.language-julia-insider-1.7.7/scripts/packages/VSCodeServer/src/VSCodeServer.jl:110
 [5] top-level scope
   @ ~/.vscode/extensions/julialang.language-julia-insider-1.7.7/scripts/terminalserver/terminalserver.jl:39
in expression starting at /home/leandro/.vscode/extensions/julialang.language-julia-insider-1.7.7/scripts/terminalserver/terminalserver.jl:14
julia>

Alright, this was super helpful, and I think I know what is going on and I also think I fixed. Turns out, the root cause is actually a bug entirely unrelated to testing that makes it that the extension will not detect juliaup properly on non Windows systems, and then also has problems spawning Julia when the launch command is just julia. I merged a fix that should just fix this for testing on master and just pushed out an insider build. @lmiq if you could retest your scenario with build 1.7.8 of the extension that would be great!
https://github.com/julia-vscode/julia-vscode/pull/3032 is a more thorough fix for the Juliaup integration bug. I'm waiting for @pfitzseb to review that before I merge it because it is going to affect a lot more scenarios than this preview test release.
Thanks for the fantastic bug report :)

No, it does not run :-(.
I don't get those error messages, though. Just when trying to launch the debugger, I get this:
[2022-08-29 07:47:05.736] [renderer1] [error] The "path" argument must be of type string. Received undefined: TypeError: The "path" argument must be of type string. Received undefined
    at new NodeError (node:internal/errors:371:5)
    at validateString (node:internal/validators:119:11)
    at basename (node:path:1309:5)
    at f.<anonymous> (/home/leandro/.vscode/extensions/julialang.language-julia-insider-1.7.8/src/debugger/juliaDebug.ts:260:22)
    at Generator.next (<anonymous>)
    at a (/home/leandro/.vscode/extensions/julialang.language-julia-insider-1.7.8/src/debugger/debugProtocol.ts:209:90)
    at processTicksAndRejections (node:internal/process/task_queues:96:5)

Ah, on Julia Testserver output I got:
/bin/sh: 1: julia: not found

Probably you already know that, but the tests work if I change the path on the extension settings to the full /home/leandro/.juliaup/bin/julia path.

@lmiq sorry that I disappeared, but I'm back now and my goal is to fix this for good now.
One quick question: I assume starting a Julia REPL with Julia: Start REPL works just fine on your system, even if you don't configure an explicit path for Julia, right?

, even if you don't configure an explicit path for Julia, right?

Yes, it always worked.

@lmiq I pushed another insider build out, v1.7.9. It won't fix anything but has more diagnostics. Could you give that one a try? Make sure that you don't have anything configured as your Julia binary, i.e. let the extension auto-find everything. And then there should be a new output channel named just "Julia", and that should show (after the extension has started) some on how the extension found a Julia binary. Could you post that info here? Thanks, in particular for being so patient with this!

I get:

and:

I removed everything from my .bashrc to avoid confusion.
Strangely, launching with julia works both in bash and sh, from a terminal.

Now I removed the julia from the executable configuration, and left it blank, and it worked:

@lmiq so the situation is that

if you leave the Julia: Executable Path setting empty it all works
if you have a value of julia in there it still does not work, right?

Did you ever have a situation where the setting was empty and things did not work? Or did you always have julia in there as a setting?

I removed everything from my .bashrc to avoid confusion.

What exactly did you remove there? Were there any Juliaup code changes in that file? If so, I don't think anything will work if you remove that...

if you leave the Julia: Executable Path setting empty it all works

Yes.

if you have a value of julia in there it still does not work, right?

Yes.

Did you ever have a situation where the setting was empty and things did not work? Or did you always have julia in there as a setting?

No, I always had julia there (not  that I remember changing that).

What exactly did you remove there? Were there any Juliaup code changes in that file? If so, I don't think anything will work if you remove that...

There was, but juliaup also modified the ~/.profile, thus the changes that it made to .bashrc  were redundant. (I discovered that when I erased the .bashrc content and was surprised that julia was still in the path).

What does which julia show? and which juliaup?

Sorry, I was lecturing:
leandro@m3g:~/Drive/Disciplinas/qf531% which julia
/home/leandro/.juliaup/bin/julia
leandro@m3g:~/Drive/Disciplinas/qf531% which juliaup
/home/leandro/.juliaup/bin/juliaup

Alright, I just pushed a new build (1.7.10) to the insider channel. @lmiq could you try that one again? I think I did find a bug that would explain everything you have observed and hopefully have fixed that now. With build 1.7.10 everything should work, i.e. the situation with an empty exec path setting and with just julia in there.

Yes, that solved the problem!

Hurray! @lmiq thanks so much for helping me figure this out, fantastic bug reports and follow ups like yours here are just invaluable.


Store parameters of crowdsales in a local file for Invest page

An attacker can send a user to a legit website with a fraudulent contract. Crowdsale addresses now in GET parameters in URL and it's easy to commit fraud for the attacker.
One solution to mitigate the problem is to store parameters of the crowdsale in a configuration file. I propose to store them in local structure of an instance of ICO Wizard, e.g. using this technique https://stackoverflow.com/questions/37066758/how-can-i-use-a-config-file-in-react
If a file with config is present, the app should use parameters from the file even GET parameters are used.
After implementation of the feature add a section about configuration to README.md file

I believe, this local structure will work for user, who created the instance of ICO.
But we can't transfer it to any investor by client-side.
will looking for another solution.

Yes, this is how it is planned. If you want to use this feature you have to deploy on your instance.
One instance = one crowdsale.

@igorbarinov Ah, ok. And owner of the instance will manually change this config after crowdsale creation. Will implement.


CI on windows is flaky

https://github.com/dart-lang/native/actions/runs/9375003716/job/25812303307

@dcharkes Probably a varargs error:
java.lang.ArrayIndexOutOfBoundsException: Index -467468285 out of bounds for length 128
	at java.base/java.lang.Character.valueOf(Character.java:7952)

Somehow a wrong integer is passed to a char which is Uint16 in Java.


[stable/fluent-bit] Fluent Bit v0.11.13

Changes

This is a bug fix release over 0.11 series that includes the following changes:

Core
Environment: fix insertions of variables with extra strings.
Hash Table: implement chaining to avoid collisions.
Parser: release resources on init if a parser fails (avoid crash).

Please sign the CLA @MaxPresman

/ok-to-test

Now obsolete.


directoryTree.py

Following parameters affect the output of this function:
1) -d", "--dir : this is the base directory from which to print/search sub-directories
2) -m or --max-depth :  this parameter tells the maxmimum depth of sub-directories to explore
3) -e or --extensions : this parameter makes function to print only files with given extension
4) -s or --search : this parameter takes a filename as input and if the given file is found then prints it in orange colour
5) --onlyDir : This is a boolean variable which makes it print only directories in tree

Part of issue: https://github.com/Ishaan28malik/Hacktoberfest-2020/issues/1202


Sidekick Release Candidate

This PR has been auto-generated from https://github.com/adobe/helix-sidekick/.

https://sidekick-rc-7aace49--helix-website--adobe.hlx3.page/

Changes in this release:

https://github.com/adobe/helix-sidekick/pull/248


docopt.php

docopt creates beautiful command-line interfaces. Command line argument parser, uses documentation to specify options.
https://github.com/docopt/docopt.php

Thanks for the suggestion.


docs: Add CONTRIBUTING.md

I will update the README in a follow-up PR. This is semantically stacked on #548 as otherwise some of the statement in here are not true.


Two or more GTM containers

@harlan-zw hi!
I may have missed it somewhere, although I've gone through the documentation completely.
Can you please tell me if it is possible to add two or more GTM containers?
If so, how do I use them?
In brief - I need to use different gtm-id on different url's. And the GTM script should be loaded immediately, by default

@konstantin-karlovich-unbiased-co-uk Can you provide some more technical guidelines around how you'd normally implement this? Do you rename the dataLayer object?
Nuxt Scripts supports loading the same script multiple times by modifying the key, however, it does not support modifying the dataLayer window key.
const { dataLayer, $script } = useScriptGoogleTagManager({
  id: 'G-TR58L0EF8P',
})

const { dataLayer: dataLayer2, $script: $script2 } = useScriptGoogleTagManager({
  key: 'gtm2',
  id: 'G-1234567890',
})

@huang-julien, @flashdesignory do you have any thoughts on being able to set the dataLayer key? It seems quite difficult to do with the TPC templating.

Would it help if we'd accept a dataLayer name, in addition to the id here?
https://github.com/GoogleChromeLabs/third-party-capital/blob/main/src/third-parties/google-analytics/data.json#L15

Seems reasonable if we're doing that for id currently

I did this example, but the container was connected only during the call of the tracking method, which is not quite suitable for me

I'm not too sure what you mean, both scripts will start loading by default once Nuxt is partially hydrated. GTM is designed to handle this as events are batched to be sent one the script is loaded and the page is idle.

@harlan-zw - something like this should work:
https://github.com/GoogleChromeLabs/third-party-capital/pull/52

You should use the globals if you want to load the script immediately.
export default defineNuxtConfig({
  scripts: {
    registry: {
      googleAnalytics: {
        id: 'YOUR_ID'
      }
    }
  }
})

Then in your component, you should be able to do
const { gtag} = useNuxtApp().$scripts.googleAnalytics
// gtag(...)

We'll improve the docs around this.
The issue as raised was about allowing you to embed multiple GTM / GA containers without conflict so we'll close this once https://github.com/nuxt/scripts/pull/163 is available in a release.


How to modify the state in the onLeftButtonPress?

How to modify the state in the onLeftButtonPress?Because I need to click to do animation, show or hide me is stored in the state
`
_getRoute(component) {
    var com = new component();
    return {
        component: component,
        title: com.getNavTitle(),
        passProps: { myProp: 'foo' },
        leftButtonIcon: com.getNavLeft().icon,
        onLeftButtonPress: com.getNavLeft().onPress,
        interactivePopGestureEnabled: true
    };
}`

`getNavLeft() {
    return {
        icon: require('../Images/wo_de.png'),
        onPress: () => {
            console.log(this);

            this.setState({leftShow: true});

            Animated.timing(          // Uses easing functions
                this.state.leftWidthAnim,    // The value to drive
                {toValue: 0}          // Configuration
            ).start();
        }

    };
}`

@facebook-github-bot stack-overflow

Hey @a289459798 and thanks for posting this! @charpeni tells me this issue looks like a question that would be best asked on StackOverflow. StackOverflow is amazing for Q&A: it has a reputation system, voting, the ability to mark a question as answered. Because of the reputation system it is likely the community will see and answer your question there. This also helps us use the GitHub bug tracker for bugs only. Will close this as this is really a question that should be asked on SO.


add --context option

Currently i am using kubectl to deploy stuff. With --context i select the cluster+authentication to use.
I would like to be able to to the same with helm.
Currently, for actions on different clusters, i need to set the current context again and again or create manually maintained .kube/config files and point to them with KUBECONFIG.

I started exploring this issue last week. Looks like we should be able to do it.

@damoon I am not following what you want here. Are you saying you want helm to use the kubectl context or you want helm to have its own context flag?

Per the conversation in slack from back then, the ask is that we make it possible to point to a specific context that is declared inside of the Kubernetes context configuration. And we do that by adding a --context STRING option. (Correct me if I'm wrong, @damoon)
Helm uses the Kube config file at $KUBECONFIG to get its context, and it then authenticates to the API server using the appropriate credentials. But right now, it only uses the default context.

https://github.com/kubernetes/helm/issues/1127#issuecomment-246529122 exactly describes my use case.
I have access to three kubernetes clusters. When i tried to use helm instead of kubectl directly, it involved a lot of manual work to set the cluster to use. i could have used mulitple kubeconfig files (and manually maintained/sync those on changes) or tried to remember to set and reset the default each time i wanted helm to use a different cluster. Both are not nice options and kubectl already found a solution with --context.


soc: arm: atmel: sam0:  Correct GCLK2 config

This commit addresses an issue where the GCLK2 divider is incorrectly
set to 31.  The correct divider is 32 which yields a frequency of
1024 Hz.  Referring to section 15.8.4 of the datasheet, the correct
configuration of the GCLK2 divider is GENCTRL.DIVSEL = 1 and
GENDIV.DIV = 4.

Hi @sslupsky the change LGTM and it makes the code match the comment.
Looks like the build is failing - are you missing a #include?

@nzmichaelh I am not sure what is causing that build error.  That macro (SOC_ATMEL_SAM0_GCLK2_PRESCALER) is defined in soc.h which is included in samd2x.c.
Ok, I think I see the issue.  That particular error message is being generated for a SAMR21 device.  That is weird since the change I made only applied to the samd.

Yeah, it appears cmake builds samd2x.c when building for samr:
'''
zephyr_sources_ifdef(CONFIG_SOC_SERIES_SAMR21 soc_samd2x.c)
'''
I do not have a SAMR board to test with so I am not sure I should make any changes to that code.

Yeah, it appears cmake builds samd2x.c when building for samr:
'''
zephyr_sources_ifdef(CONFIG_SOC_SERIES_SAMR21 soc_samd2x.c)
'''
I do not have a SAMR board to test with so I am not sure I should make any changes to that code.

SAMR21 is a SIP (SAMD21 + AT85RF233). I think you can enable the change for that SoC too.


bnb.4bits error: "ValueError: Blockwise quantization only supports 16/32-bit floats, but got torch.uint8"

I get the following error when I try to use backend.quantization_scheme=bnb and backend.quantization_config.load_in_4bit=true: ValueError: Blockwise quantization only supports 16/32-bit floats, but got torch.uint8.
I was trying to test with model NousResearch/Llama-2-7b-chat-hf.
I am using the recent version (commit hash: 93f5bbc) of optimum-benchmark.
Here I attach the config and detail log below:
Config
defaults:
  - backend: pytorch # default backend
  - launcher: process # default launcher
  - benchmark: inference # default benchmark
  - experiment # inheriting experiment schema
  - _self_ # for hydra 1.1 compatibility
  - override hydra/job_logging: colorlog # colorful logging
  - override hydra/hydra_logging: colorlog # colorful logging

experiment_name: llama-2-7b_bnb4bits

backend:
  quantization_config:
    load_in_4bit: true
  quantization_scheme: bnb
  torch_dtype: bfloat16 #float16
  device: cuda
  device_ids: 0
  no_weights: true
  model: NousResearch/Llama-2-7b-chat-hf #meta-llama/Llama-2-7b-hf

#launcher: # this will make multiprocessing error
#  device_isolation: true

benchmark:
  input_shapes:
    batch_size: 1
    sequence_length: 256
  new_tokens: 256

# hydra/cli specific settings
hydra:
  run:
    # where to store run results
    dir: runs/${experiment_name}
  sweep:
    # where to store sweep results
    dir: sweeps/${experiment_name}
  job:
    # change working directory to the run directory
    chdir: true
    env_set:
      # set environment variable OVERRIDE_BENCHMARKS to 1
      # to not skip benchmarks that have been run before
      OVERRIDE_BENCHMARKS: 1

Detail log
ubuntu@gpu-1:$ HYDRA_FULL_ERROR=1 optimum-benchmark --config-dir examples --config-name llama-2-7b_bnb4bits
[2024-04-02 16:44:13,648][inference][WARNING] - `new_tokens` is deprecated. Use `max_new_tokens` and `min_new_tokens` instead. Setting `max_new_tokens` and `min_new_tokens` to `new_tokens`.
[2024-04-02 16:44:13,653][launcher][INFO] - ََAllocating process launcher
[2024-04-02 16:44:13,654][process][INFO] - 	+ Setting multiprocessing start method to spawn.
[2024-04-02 16:44:13,658][process][INFO] - 	+ Launched worker process(es) with PID(s): [4022977]
[PROC-0][2024-04-02 16:44:17,034][backend][INFO] - َAllocating pytorch backend
[PROC-0][2024-04-02 16:44:17,034][backend][INFO] - 	+ Setting random seed to 42
tokenizer_config.json: 100%|█████████████████████████████████████████████████████████████| 746/746 [00:00<00:00, 3.09MB/s]
config.json: 100%|███████████████████████████████████████████████████████████████████████| 583/583 [00:00<00:00, 2.63MB/s]
tokenizer.model: 100%|█████████████████████████████████████████████████████████████████| 500k/500k [00:00<00:00, 20.1MB/s]
tokenizer.json: 100%|████████████████████████████████████████████████████████████████| 1.84M/1.84M [00:00<00:00, 2.08MB/s]
added_tokens.json: 100%|████████████████████████████████████████████████████████████████| 21.0/21.0 [00:00<00:00, 148kB/s]
special_tokens_map.json: 100%|███████████████████████████████████████████████████████████| 435/435 [00:00<00:00, 2.91MB/s]
generation_config.json: 100%|█████████████████████████████████████████████████████████████| 179/179 [00:00<00:00, 997kB/s]
/usr/local/lib/python3.10/dist-packages/transformers/generation/configuration_utils.py:492: UserWarning: `do_sample` is set to `False`. However, `temperature` is set to `0.9` -- this flag is only used in sample-based generation modes. You should set `do_sample=True` or unset `temperature`. This was detected when initializing the generation config instance, which means the corresponding file may hold incorrect parameterization and should be fixed.
  warnings.warn(
/usr/local/lib/python3.10/dist-packages/transformers/generation/configuration_utils.py:497: UserWarning: `do_sample` is set to `False`. However, `top_p` is set to `0.6` -- this flag is only used in sample-based generation modes. You should set `do_sample=True` or unset `top_p`. This was detected when initializing the generation config instance, which means the corresponding file may hold incorrect parameterization and should be fixed.
  warnings.warn(
/usr/local/lib/python3.10/dist-packages/transformers/generation/configuration_utils.py:492: UserWarning: `do_sample` is set to `False`. However, `temperature` is set to `0.9` -- this flag is only used in sample-based generation modes. You should set `do_sample=True` or unset `temperature`.
  warnings.warn(
/usr/local/lib/python3.10/dist-packages/transformers/generation/configuration_utils.py:497: UserWarning: `do_sample` is set to `False`. However, `top_p` is set to `0.6` -- this flag is only used in sample-based generation modes. You should set `do_sample=True` or unset `top_p`.
  warnings.warn(
[PROC-0][2024-04-02 16:44:27,158][pytorch][INFO] - 	+ Using AutoModel class AutoModelForCausalLM
[PROC-0][2024-04-02 16:44:27,158][pytorch][INFO] - 	+ Processing quantization config
[PROC-0][2024-04-02 16:44:27,158][pytorch][INFO] - 	+ Processing BitsAndBytes config
[PROC-0][2024-04-02 16:44:27,159][pytorch][INFO] - 	+ Creating backend temporary directory
[PROC-0][2024-04-02 16:44:27,159][pytorch][INFO] - 	+ Loading model with random weights
[PROC-0][2024-04-02 16:44:27,160][pytorch][INFO] - 	+ Creating no weights model
[PROC-0][2024-04-02 16:44:27,160][pytorch][INFO] - 	+ Creating no weights model directory
[PROC-0][2024-04-02 16:44:27,161][pytorch][INFO] - 	+ Creating no weights model state dict
[PROC-0][2024-04-02 16:44:27,163][pytorch][INFO] - 	+ Saving no weights model safetensors
[PROC-0][2024-04-02 16:44:27,164][pytorch][INFO] - 	+ Adding quantization config to no weights model's pretrained config
[PROC-0][2024-04-02 16:44:27,164][pytorch][INFO] - 	+ Saving no weights model pretrained config
[PROC-0][2024-04-02 16:44:27,166][pytorch][INFO] - 	+ Loading no weights AutoModel
[PROC-0][2024-04-02 16:44:27,166][pytorch][INFO] - 	+ Loading Quantized model
/usr/local/lib/python3.10/dist-packages/transformers/quantizers/auto.py:159: UserWarning: You passed `quantization_config` or equivalent parameters to `from_pretrained` but the model you're loading already has a `quantization_config` attribute. The `quantization_config` from the model will be used.
  warnings.warn(warning_msg)
A.dtype = torch.float16
A.dtype = torch.uint8
[PROC-0][2024-04-02 16:44:30,465][experiment][ERROR] - Error during backend allocation: Blockwise quantization only supports 16/32-bit floats, but got torch.uint8
[2024-04-02 16:44:31,473][experiment][ERROR] - Error during experiment launching:

-- Process 0 terminated with the following error:
Traceback (most recent call last):
  File "/home/ubuntu/.local/lib/python3.10/site-packages/torch/multiprocessing/spawn.py", line 74, in _wrap
    fn(i, *args)
  File "/data/gmkim/optimum-benchmark/optimum_benchmark/launchers/process/launcher.py", line 58, in entrypoint
    worker_output = worker(*worker_args)
  File "/data/gmkim/optimum-benchmark/optimum_benchmark/experiment.py", line 68, in run
    raise e
  File "/data/gmkim/optimum-benchmark/optimum_benchmark/experiment.py", line 65, in run
    backend: Backend = backend_factory(backend_config)
  File "/data/gmkim/optimum-benchmark/optimum_benchmark/backends/pytorch/backend.py", line 81, in __init__
    self.load_model_with_no_weights()
  File "/data/gmkim/optimum-benchmark/optimum_benchmark/backends/pytorch/backend.py", line 243, in load_model_with_no_weights
    self.load_model_from_pretrained()
  File "/data/gmkim/optimum-benchmark/optimum_benchmark/backends/pytorch/backend.py", line 183, in load_model_from_pretrained
    self.pretrained_model = self.automodel_class.from_pretrained(
  File "/usr/local/lib/python3.10/dist-packages/transformers/models/auto/auto_factory.py", line 563, in from_pretrained
    return model_class.from_pretrained(
  File "/usr/local/lib/python3.10/dist-packages/transformers/modeling_utils.py", line 3589, in from_pretrained
    dispatch_model(model, **device_map_kwargs)
  File "/home/ubuntu/.local/lib/python3.10/site-packages/accelerate/big_modeling.py", line 396, in dispatch_model
    attach_align_device_hook_on_blocks(
  File "/home/ubuntu/.local/lib/python3.10/site-packages/accelerate/hooks.py", line 517, in attach_align_device_hook_on_blocks
    add_hook_to_module(module, hook)
  File "/home/ubuntu/.local/lib/python3.10/site-packages/accelerate/hooks.py", line 156, in add_hook_to_module
    module = hook.init_hook(module)
  File "/home/ubuntu/.local/lib/python3.10/site-packages/accelerate/hooks.py", line 254, in init_hook
    set_module_tensor_to_device(module, name, self.execution_device)
  File "/home/ubuntu/.local/lib/python3.10/site-packages/accelerate/utils/modeling.py", line 339, in set_module_tensor_to_device
    new_value = param_cls(new_value, requires_grad=old_value.requires_grad).to(device)
  File "/usr/local/lib/python3.10/dist-packages/bitsandbytes/nn/modules.py", line 313, in to
    return self._quantize(device)
  File "/usr/local/lib/python3.10/dist-packages/bitsandbytes/nn/modules.py", line 280, in _quantize
    w_4bit, quant_state = bnb.functional.quantize_4bit(
  File "/usr/local/lib/python3.10/dist-packages/bitsandbytes/functional.py", line 1011, in quantize_4bit
    raise ValueError(f"Blockwise quantization only supports 16/32-bit floats, but got {A.dtype}")
ValueError: Blockwise quantization only supports 16/32-bit floats, but got torch.uint8

Error executing job with overrides: []
Traceback (most recent call last):
  File "/usr/local/bin/optimum-benchmark", line 8, in <module>
    sys.exit(benchmark_cli())
  File "/usr/local/lib/python3.10/dist-packages/hydra/main.py", line 94, in decorated_main
    _run_hydra(
  File "/usr/local/lib/python3.10/dist-packages/hydra/_internal/utils.py", line 394, in _run_hydra
    _run_app(
  File "/usr/local/lib/python3.10/dist-packages/hydra/_internal/utils.py", line 457, in _run_app
    run_and_report(
  File "/usr/local/lib/python3.10/dist-packages/hydra/_internal/utils.py", line 223, in run_and_report
    raise ex
  File "/usr/local/lib/python3.10/dist-packages/hydra/_internal/utils.py", line 220, in run_and_report
    return func()
  File "/usr/local/lib/python3.10/dist-packages/hydra/_internal/utils.py", line 458, in <lambda>
    lambda: hydra.run(
  File "/usr/local/lib/python3.10/dist-packages/hydra/_internal/hydra.py", line 132, in run
    _ = ret.return_value
  File "/usr/local/lib/python3.10/dist-packages/hydra/core/utils.py", line 260, in return_value
    raise self._return_value
  File "/usr/local/lib/python3.10/dist-packages/hydra/core/utils.py", line 186, in run_job
    ret.return_value = task_function(task_cfg)
  File "/data/gmkim/optimum-benchmark/optimum_benchmark/cli.py", line 63, in benchmark_cli
    benchmark_report: BenchmarkReport = launch(experiment_config=experiment_config)
  File "/data/gmkim/optimum-benchmark/optimum_benchmark/experiment.py", line 153, in launch
    raise e
  File "/data/gmkim/optimum-benchmark/optimum_benchmark/experiment.py", line 148, in launch
    output = launcher.launch(run, benchmark_config, backend_config)
  File "/data/gmkim/optimum-benchmark/optimum_benchmark/launchers/process/launcher.py", line 42, in launch
    while not process_context.join():
  File "/home/ubuntu/.local/lib/python3.10/site-packages/torch/multiprocessing/spawn.py", line 163, in join
    raise ProcessRaisedException(msg, error_index, failed_process.pid)
torch.multiprocessing.spawn.ProcessRaisedException:

-- Process 0 terminated with the following error:
Traceback (most recent call last):
  File "/home/ubuntu/.local/lib/python3.10/site-packages/torch/multiprocessing/spawn.py", line 74, in _wrap
    fn(i, *args)
  File "/data/gmkim/optimum-benchmark/optimum_benchmark/launchers/process/launcher.py", line 58, in entrypoint
    worker_output = worker(*worker_args)
  File "/data/gmkim/optimum-benchmark/optimum_benchmark/experiment.py", line 68, in run
    raise e
  File "/data/gmkim/optimum-benchmark/optimum_benchmark/experiment.py", line 65, in run
    backend: Backend = backend_factory(backend_config)
  File "/data/gmkim/optimum-benchmark/optimum_benchmark/backends/pytorch/backend.py", line 81, in __init__
    self.load_model_with_no_weights()
  File "/data/gmkim/optimum-benchmark/optimum_benchmark/backends/pytorch/backend.py", line 243, in load_model_with_no_weights
    self.load_model_from_pretrained()
  File "/data/gmkim/optimum-benchmark/optimum_benchmark/backends/pytorch/backend.py", line 183, in load_model_from_pretrained
    self.pretrained_model = self.automodel_class.from_pretrained(
  File "/usr/local/lib/python3.10/dist-packages/transformers/models/auto/auto_factory.py", line 563, in from_pretrained
    return model_class.from_pretrained(
  File "/usr/local/lib/python3.10/dist-packages/transformers/modeling_utils.py", line 3589, in from_pretrained
    dispatch_model(model, **device_map_kwargs)
  File "/home/ubuntu/.local/lib/python3.10/site-packages/accelerate/big_modeling.py", line 396, in dispatch_model
    attach_align_device_hook_on_blocks(
  File "/home/ubuntu/.local/lib/python3.10/site-packages/accelerate/hooks.py", line 517, in attach_align_device_hook_on_blocks
    add_hook_to_module(module, hook)
  File "/home/ubuntu/.local/lib/python3.10/site-packages/accelerate/hooks.py", line 156, in add_hook_to_module
    module = hook.init_hook(module)
  File "/home/ubuntu/.local/lib/python3.10/site-packages/accelerate/hooks.py", line 254, in init_hook
    set_module_tensor_to_device(module, name, self.execution_device)
  File "/home/ubuntu/.local/lib/python3.10/site-packages/accelerate/utils/modeling.py", line 339, in set_module_tensor_to_device
    new_value = param_cls(new_value, requires_grad=old_value.requires_grad).to(device)
  File "/usr/local/lib/python3.10/dist-packages/bitsandbytes/nn/modules.py", line 313, in to
    return self._quantize(device)
  File "/usr/local/lib/python3.10/dist-packages/bitsandbytes/nn/modules.py", line 280, in _quantize
    w_4bit, quant_state = bnb.functional.quantize_4bit(
  File "/usr/local/lib/python3.10/dist-packages/bitsandbytes/functional.py", line 1011, in quantize_4bit
    raise ValueError(f"Blockwise quantization only supports 16/32-bit floats, but got {A.dtype}")
ValueError: Blockwise quantization only supports 16/32-bit floats, but got torch.uint8

Hi, I just ran your configuration and it works fine so the issue might be related to the packages you have installed
bnb has been added lately to the continuously tested configs https://github.com/huggingface/optimum-benchmark/blob/main/tests/configs/bnb.yaml.
I would suggest updating your packages or using docker for a clean environment:
make build_docker_cuda
make run_docker_cuda
pip install -e .

Using docker for a clean environemnt resolve the issue.
Thanks for the solution. Closing the issue.


Fix panic in felix flushHostIPUpdates

Description

Related issues/PRs
fixes https://github.com/projectcalico/calico/issues/9373

Todos

[ ] Tests
[ ] Documentation
[ ] Release note

Release Note

Fix panic in  felix flushHostIPUpdates

Reminder for the reviewer
Make sure that this PR has the correct labels and milestone set.
Every PR needs one docs-* label.

docs-pr-required: This change requires a change to the documentation that has not been completed yet.
docs-completed: This change has all necessary documentation completed.
docs-not-required: This change has no user-facing impact and requires no docs.

Every PR needs one release-note-* label.

release-note-required: This PR has user-facing changes. Most PRs should have this label.
release-note-not-required: This PR has no user-facing changes.

Other optional labels:

cherry-pick-candidate: This PR should be cherry-picked to an earlier release. For bug fixes only.
needs-operator-pr: This PR is related to install and requires a corresponding change to the operator.

/sem-approve

@caseydavenport I've not spent time to find the root cause. If we want to do that then we need to spend sometime to try to reproduce the issue. Given that the issue happened in a dual stack cluster, it might be that IPv6 is enabled, but ipv6 address is missing.

It may be that there is an ipv6 address on the Calico startup, but then it is missing. when the ipv6 address is missing, I think updating it to an empty string is ok.

@cyclinder it seems the CI execution is not triggered.  Can you please try pushing a dummy commit to trigger it.

/sem-approve

@cyclinder Thanks again for the fix. I merged and cherry picked this fix to v3.29 and v3.28 since we are going to release v3.29.1 patch release on Monday.


Update to Godot 4.3

updates godot-cpp to godot-4.3-stable branch
various fixes to make this codebase compatible with new changes

You also need to update the Godot version used for unit tests in the CI.

Almost, you forgot to update the version in the github actions as well.


update gisce/react-formiga-table to v1.3.0-alpha.3

Automated changes by create-pull-request GitHub action

:tada: This PR is included in version 2.10.0-alpha.2 :tada:
The release is available on:

npm package (@alpha dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This PR is included in version 2.11.0-alpha.1 :tada:
The release is available on:

npm package (@alpha dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This PR is included in version 2.14.0-alpha.1 :tada:
The release is available on:

npm package (@alpha dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This PR is included in version 2.15.0-alpha.1 :tada:
The release is available on:

npm package (@alpha dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Vulnerability fix

Merge branch 'master' into develop
Upgrading jackson databind to <IP_ADDRESS>
Changing to StdDateFormat since ISO8601DateFormat is deprecated.

https://bugs.openjdk.java.net/browse/JDK-8212233


Regression: Kprove hangs instead of crashing

Test file:
module TEST
    imports MAP
    imports BOOL

    syntax Foo ::= "a" | "b" | "c"
 // ------------------------------
    rule <k> a => b ... </k>

endmodule

module TEST-SPEC
    imports TEST

    claim <k> (a ~> _ => .) ... </k>

endmodule

Commit https://github.com/kframework/kore/commit/ed422630f9383b2774f1ec8ea04eee86ea0afe1e changed the behavior of running kprove on this test case.
In order to reproduce this behavior I create a makefile with the following lines and run make:
all:
	rm -rf *-kompiled .kprove*
	kompile --main-module TEST --backend haskell test.k
	kprovex test.k --spec-module TEST-SPEC --debug

Prior to this commit, the kfrontend code crashed on a pattern match error shown in https://github.com/kframework/k/issues/2245 and I'm expecting this crash to continue to happen. The actual behavior seems to hang sometime before kore is printed. I also found that adding --depth 0 to the last command causes the pattern match crash to happen.

I added this test case to the k repo with the --depth 0 option to get it to complete. Once this regression is resolved in the haskell backend, we should remove this option from the test. I made this change in this pull request here: https://github.com/kframework/k/pull/2279 Once this is resolved, let's merge this PR so that we can create a regression test for this.

I'm going to record my progress on the issue here in order to provide a clear report of my progress but also to document the debugging process for other members of the Haskell backend team.

I managed to reproduce both the looping behavior and the --depth 0 behavior on the current kore master.
I ran kprovex with --debugger to start the kore-repl. I observed that taking one single step (with the step) command induces the looping behavior.
I restarted the kore-repl and I switched on the logging for DebugAttemptEquation entries with log [DebugAttemptEquation] stderr. This is to make sure that it isn't looping when applying equations. When stepping, I noticed that after a few log entries it stopped printing anything, suggesting that it's looping in some specific point in the simplifier.
I restarted the kore-repl and I switched on the logging for all log entries: log debug [] stderr. I noticed that it kept printing the following log entries:

kore-repl: [188419768] Debug (DebugSubstitutionSimplifier):
    (InfoReachability) while checking the implication:
    (DebugSubstitutionSimplifier) while simplifying substitution:
    Non-\bottom result
kore-repl: [188422090] Debug (DebugSubstitutionSimplifier):
    (InfoReachability) while checking the implication:
    Simplifying substitution

This suggests that it's looping in the substitution simplifier, inside the CheckImplication transition. I believe I should continue by adding traces in that part of the code, to figure out which substitution that is.
The relationship between the commit where the regression appeared and this behavior is still unclear to me.